Wireless communication method and user equipment and network entity for wireless communication

By determining the appropriate NAS count value in the EPS security context between the UE and the network entity, the signaling and security issues caused by the NAS count value configuration when the UE changes from the wireless system to the EPS in a wireless communication system are solved, ensuring that Smooth switching between systems and mobility management, improving communication security and stability.

CN118945653APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411332946.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-06-10
Filing Date
2020-06-11
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In wireless communication systems, when the UE changes from the wireless system to the EPS, there are unexpected problems in the configuration of the NAS count value, resulting in security and mobility management problems caused by signaling optimization, especially in handover and idle mode mobility TAU request failure or security issues may result.

Method used

When generating the mapped EPS security context, the appropriate uplink and downlink NAS count values ​​are determined and set by UE and network entities to ensure consistency and validity when the count values ​​change between systems, avoiding setting to zero to prevent Unexpected issue.

Benefits of technology

It solves signaling failure and security problems caused by inconsistent NAS count values ​​between UE and MME, ensures smooth handover and mobility management between systems, and improves communication security and stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945653A_ABST
    Figure CN118945653A_ABST
Patent Text Reader

Abstract

The disclosure relates to a wireless communication method and a user equipment and a network entity for wireless communication. In one aspect, the present disclosure includes a method, apparatus, and computer readable medium for wireless communication to configure a NAS count value for a mapped EPS security context associated with an inter-system change of a UE from a 5G system to an EPS. The aspect may include generating, by the UE, a mapped EPS security context associated with an inter-system change of the UE from the 5G system to the EPS, where the mapped EPS security context includes security parameters created based on a 5G security context for the 5G system, the security parameters enabling security-related communications between the UE and a network entity; determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the UE, a NAS message to the network entity, the NAS message including the UL NAS count value of the mapped EPS security context.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This invention patent application is a divisional application of the invention patent application with international application number PCT / US2020 / 037272, international application date June 11, 2020, application number 202080041786.5 entering the Chinese national phase, and name “Evolved Packet System (EPS) Mobility Configuration for Non-Access Stratum (NAS) Counting from Wireless Systems”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 860,109, filed on June 11, 2019, entitled “NAS COUNT CONFIGURATION FOR 5G SYSTEM TO EPS MOBILITY,” and U.S. Patent Application No. 16 / 897,978, filed on June 10, 2020, entitled “EVOLVED PACKET SYSTEM (EPS) MOBILITY CONFIGURATION FROM WIRELESS SYSTEM,” both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to communication systems, and more particularly to configuration of non-access stratum (NAS) count values ​​of mapped EPS security contexts associated with an inter-system change of a user equipment (UE) from a wireless system to an evolved packet system (EPS). The present disclosure relates more particularly to wireless communication methods and user equipment and network entities for wireless communication. Background Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0007] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0008] According to an example, a method for wireless communication is provided. The method includes: generating, by a user equipment (UE), a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an evolved packet system (EPS), wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; determining an uplink (UL) non-access stratum (NAS) count value and a downlink (DL) NAS count value for the mapped EPS security context; and transmitting, by the UE to the network entity, a NAS message, the NAS message including the UL NAS count value of the mapped EPS security context.

[0009] In a further example, an apparatus for wireless communication is provided, the apparatus comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. This aspect may include the one or more processors being configured to execute instructions to perform the following operations: generating, by the UE, a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; determining an UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the UE to the network entity, a NAS message, the NAS message including the UL NAS count value of the mapped EPS security context.

[0010] On the other hand, an apparatus for wireless communication is provided, comprising: a device for generating, by a UE, a mapped EPS security context associated with an inter-system change of the UE from a wireless system to EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; a device for determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and a device for transmitting, by the UE, a NAS message to the network entity, the NAS message including the UL NAS count value of the mapped EPS security context.

[0011] On the other hand, a non-transitory computer-readable medium comprising one or more processors is provided, the one or more processors executing: code for generating, by a UE, a mapped EPS security context associated with an inter-system change of the UE from a wireless system to EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; code for determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and code for transmitting, by the UE, a NAS message to the network entity, the NAS message including the UL NAS count value of the mapped EPS security context.

[0012] In another example, a method for wireless communication includes: generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0013] In a further example, an apparatus for wireless communication is provided, the apparatus comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. This aspect may include the one or more processors being configured to execute instructions to perform the following operations: generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context comprises security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0014] On the other hand, an apparatus for wireless communication is provided, comprising: a device for generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; a device for determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and a device for transmitting, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0015] On the other hand, a non-transitory computer-readable medium comprising one or more processors is provided, the one or more processors executing: code for generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; code for determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and code for transmitting, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0016] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a diagram illustrating an example of a wireless communication system and access network in accordance with certain aspects of the present specification.

[0018] Figure 2A is a diagram illustrating an example of a first frame according to certain aspects of the present specification.

[0019] Figure 2B is a diagram illustrating an example of DL channels within a subframe in accordance with certain aspects of the present disclosure.

[0020] Figure 2C is a diagram illustrating an example of a DL channel within a second frame in accordance with certain aspects of the present disclosure.

[0021] Figure 2D is a diagram illustrating an example of a DL channel within a UL channel within a subframe in accordance with certain aspects of the present disclosure.

[0022] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network in accordance with certain aspects of the present specification.

[0023] Figure 4 is a diagram illustrating an example of a handover procedure for a UE from a wireless system to an EPS in accordance with certain aspects of the present specification.

[0024] Figure 5is a diagram illustrating an example of idle mode mobility for a UE from a wireless system to an EPS, in accordance with certain aspects of the present specification.

[0025] Figure 6 1 is a flow chart of a wireless communication method in which a UE configures a NAS count value of a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an EPS in accordance with certain aspects of the present disclosure.

[0026] Figure 7 1 is a flow chart of a wireless communication method in which a network entity configures a NAS count value of a mapped EPS security context associated with an inter-system change of a UE from a wireless system to an EPS according to certain aspects of the present disclosure.

[0027] Figure 8 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus according to certain aspects of the present specification.

[0028] Fig. 9 is a diagram illustrating an example of a hardware implementation for a device employing a processing system in accordance with certain aspects of the present description.

[0029] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus according to certain aspects of the present specification.

[0030] Fig.11 is a diagram illustrating an example of a hardware implementation for a device employing a processing system in accordance with certain aspects of the present description. DETAILED DESCRIPTION

[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software may be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0034] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, these functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0035] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0036] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a backhaul link 184. Base stations 102 may perform one or more of the following functions, among other functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other over a backhaul link 134 (eg, an X2 interface) directly or indirectly (eg, through EPC 160 or core network 190). Backhaul link 134 may be wired or wireless.

[0037] Base stations 102 may communicate wirelessly with UE 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved B node (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. These communication links may be through one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth for each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0038] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0039] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0040] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0041] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

[0042] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0043] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0044] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0045] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0046] Refer again Figure 1 In certain aspects, the UE 104 can be configured to operate a configuration component 198. For example, as further described herein, the configuration component 198 can: generate a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; determine a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmit, by the UE to the network entity, a NAS message, the NAS message including the UL NAS count value of the mapped EPS security context.

[0047] In certain aspects, the AMF 192 may be configured to operate a configuration component 199. For example, as further described herein, the configuration component 199 may: generate, by the network entity, a mapped EPS security context associated with a request for an inter-system change of the UE from the wireless system to the EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and the second network entity; determine a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmit, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0048] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0049] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2D An example of slot configuration 0 with 14 symbols per slot and parameter design μ=0 is provided, with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0050] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0051] like Figure 2A As explained in the illustration, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0052] Figure 2B An example of various DL channels within a subframe of an explanation frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth, as well as the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0053] As in Figure 2C As illustrated in FIG, some REs carry DM-RSs for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. Although not shown, the UE may transmit a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0054] Figure 2D An example of various UL channels within a subframe of an illustration frame. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0055] Figure 33 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0056] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0057] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0058] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0059] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0060] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0061] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0062] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0063] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 198 combined aspects.

[0064] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 199 combined aspects.

[0065] The described features generally relate to configuration of NAS count values ​​for a mapped EPS security context associated with an inter-system change of a UE from a wireless system (e.g., a 5G system) to EPS. For example, in mobility from a wireless system to EPS, the UE and / or an access and mobility management function (AMF) creates a mapped EPS security context. When generating the mapped EPS security context, the UE and the AMF set the uplink and downlink NAS counts to zero. However, setting the uplink and downlink NAS counts to zero has unintended problems caused by legacy mobility management entity (MME) behavior or signaling optimization introduced in wireless system to EPS mobility.

[0066] In one aspect, if the UE sends the first uplink NAS message with uplink NAS count = 0 using the mapped EPS security context, the MME will not accept the uplink NAS message because the MME does not expect NAS count = 0 for uplink NAS messages in UE mobility. This problem can occur in both handover from the wireless system to EPS and in idle mode mobility from the wireless system to EPS. For the former case, the first uplink NAS message from the UE to the MME protected with the mapped EPS security context is a Tracking Area Update (TAU) Request; for the latter case, the first uplink NAS message from the UE to the MME protected with the mapped EPS security context is a TAU Completion.

[0067] In one example, after completing the handover of the wireless system to EPS, the UE sends a TAU request with uplink NAS count = 0 to update its location. This may cause the TAU request to fail at the MME because the MME did not expect a TAU request with uplink NAS count = 0, i.e., the NAS count in the TAU request is not greater than the NAS count stored in the mapped EPS security context in the MME. Similarly, even if the TAU request is accepted at the MME, the MME sends a TAU accept with downlink NAS count = 0 to the UE. This may also cause the UE to discard the TAU accept because the UE did not expect a downlink NAS message with DL NAS count = 0, because in the mapped EPS security context, the UE expected a downlink NAS count greater than the stored downlink NAS count.

[0068] In another example, in idle mode mobility from wireless system to EPS, the UE sends a TAU request protected using the current NAS security context. For integrity protection of the TAU request, the UE uses the UL NAS count of the NAS security context. This also introduces similar issues as handover from wireless system to EPS: MME sends TAU Accept with DL NAS count = 0; UE sends TAU Complete with UL NAS count = 0.

[0069] Furthermore, setting the NAS count in the mapped EPS security context to zero introduces a more serious security issue in idle mode mobility from the wireless system to the EPS. In idle mode mobility from the wireless system to the EPS, there are scenarios where the UE and the network need to set up AS security. For example, if the "Active Flag" is set in the TAU Request message or the MME chooses to establish a radio bearer when there is pending downlink UP data or pending downlink signaling, the radio bearer will be established as part of the TAU procedure and K eNB If there is no subsequent NAS SMC, the uplink NAS count of the TAU request message sent from the UE to the MME is used as the K using the KDF. eNB Refresh parameters in derivation. The integrity of TAU requests can be protected.

[0070] In addition, if you need to derive K for the above scenario eNB , then in K eNB The uplink NAS count of the 5G NAS security context is used in the derivation. However, this may result in the UE and MME deriving the same K eNB Twice, because the uplink NAS count in the mapped EPS security context is set to zero and incremented for each uplink NAS message sent by the UE.

[0071] For example, in one aspect, the present disclosure includes a method, apparatus, and computer-readable medium for wireless communication, the method, apparatus, and computer-readable medium being used to configure a NAS count value of a mapped EPS security context associated with an inter-system change of a UE from a wireless system to an EPS. This aspect may include: generating, by a UE, a mapped EPS security context associated with an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes a security parameter created based on a security context for the wireless system, the security parameter enabling security-related communications between the UE and a network entity; determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the UE to the network entity, a NAS message, the NAS message including the UL NAS count value of the mapped EPS security context.

[0072] In another example, on the one hand, the present disclosure includes a method, apparatus, and computer-readable medium for wireless communication, which are used to perform the following operations: generating, by a first network entity, a mapped EPS security context associated with receiving a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and the network entity; determining a UL NAS count value and a DL NAS count value for the mapped EPS security context; and transmitting, by the first network entity to a second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value.

[0073] Figure 4 FIG. 4 is a diagram illustrating an example of a handover procedure for a UE from a wireless system to an EPS. For example, the UE may communicate with Figure 1 The gNB / ng-eNB / eNB may be similar or identical to the base station 102, the AMF may be similar or identical to the AMF 192, and the MME may be similar or identical to the MME 162.

[0074] On the one hand, in step 1, the gNB / ng-eNB sends a handover required message to the AMF, including the identity of the UE and the security capabilities of the UE. In step 2, when the source AMF performs the handover procedure to the EPC, after checking the access authority and security capabilities of the UE, the source AMF prepares the UE context, which includes the mapped EPS security context for the target MME.

[0075] To construct the mapped EPS security context, the source AMF uses K AMF Key derivation K' ASMEand the current downlink NAS count for the current security context, and then increments its stored downlink NAS count value by one. The source AMF selects the EPS NAS algorithm identifier (which it stores) to be used in the target MME for ciphering and integrity protection upon interworking handover to EPS. In an example, the AMF may generate a mapped EPS security context associated with a request for an intersystem change of the UE from the wireless system to EPS. The mapped EPS security context includes security parameters created based on the security context for the wireless system, which enable security-related communications between the UE and network entities. The AMF may further determine the DL NAS count value for the mapped EPS security context.

[0076] In some aspects, the legacy target MME expects to receive the selected EPS NAS algorithm identifier from the source AMF via N26, because the target MME considers the source AMF to be another MME. The source AMF therefore supplies the EPS NAS security algorithm identifier to be used in the interworking handover to EPS to the UE in the NAS SMC in the radio access. The target MME may reselect a different EPS NAS algorithm to be used with the UE by running a NAS SMC in a subsequent tracking area update procedure.

[0077] In step 3, the source AMF sends the UE security context (including the new K ASME ', eKSI, uplink and downlink EPS NAS counts, UE EPS security capabilities, selected EPS NAS algorithm identifier) ​​are passed to the target MME in the Forward Relocation Request message. The UE NR security capabilities may also be sent by the source AMF. In step 4, when the target MME receives the Forward Relocation Request message from the source AMF, the target MME then uses the received EPS NAS security algorithm identifier as input from the received K ASME 'The EPS NAS key (i.e., K NASenc and K NASint ) for use in EPC. The target MME needs to include the {NH, NCC=2} pair and UE security capabilities in the S1 Handover Request message to the target LTE eNB. The UE security capabilities include the UE EPS security capabilities received from the source AMF.

[0078] In step 5, upon receiving the S1 Handover Request from the target MME, the target LTE eNB selects the AS security algorithm according to the UE EPS security capabilities and calculates the KeNB to be used for the UE and continues. The target LTE eNB then sends the selected AS security algorithm to the target MME in the Target to Source Transparent Container in the S1 Handover Request Acknowledgement message. In step 6, the target MME includes the Target to Source Transparent Container received from the target LTE eNB in ​​the Forward Relocation Response message sent to the source AMF. In step 7, the source AMF includes the Target to Source Transparent Container and the KeNB in ​​step 2 in the KeNB. ASME ’ The 8 LSBs of the downlink NAS count value used in the derivation are included in the handover command sent to the source gNB / ng-eNB.

[0079] In step 8, the source gNB / ng-eNB includes the target-to-source transparent container and the 8 LSBs of the downlink NAS count value in the handover command sent to the UE. Upon receiving the handover command message, the UE estimates the downlink NAS count value using the 8 LSBs of the received downlink NAS count value and its stored downlink NAS count value. The UE may ensure that the estimated downlink NAS count value is greater than the stored downlink NAS count value. The UE may then use the estimated downlink NAS count value to derive the mapped EPS security context, i.e., from K AMF Export K ASME ', as described in clause 8.6.1. After derivation, the UE may set the downlink NAS count value in the NAS security context to the received downlink NAS count value.

[0080] In step 9, eKSI is used for the newly derived K ASME The UE may also derive the EPS NAS key (i.e., K) using the EPS NAS security algorithm identifier stored in the ME and supplied to the UE by the AMF in the NAS SMC in earlier radio access. NASenc and K NASint ), as done by the MME in step 4. The UE may also use 2 32 -1 as the value of the uplink NAS count parameter from K ASME ' and the uplink NAS count to derive the initial K eNBFor example, the UE may generate a mapped EPS security context associated with an inter-system change of the UE from a wireless system to the EPS. The mapped EPS security context includes security parameters created based on the security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity. The UE may further determine a UL NAS count value and a DL NAS count value for the mapped EPS security context.

[0081] In step 10, the UE sends a handover complete message to the target LTE eNB. The UE may use the newly created mapped EPS security context to encrypt the message and protect the integrity of the message. In step 11, the target LTE eNB notifies the target MME via a handover notification message.

[0082] Figure 5 FIG. 5 is a diagram illustrating an example of idle mode mobility for a UE from a wireless system to an EPS. For example, a UE may communicate with Figure 1 The gNB / ng-eNB / eNB may be similar or identical to the base station 102, the AMF may be similar or identical to the AMF 192, and the MME may be similar or identical to the MME 162.

[0083] In step 1, the UE initiates the TAU procedure by sending a TAU request with a mapped EPS GUTI derived from the GUTI and its EPS security capabilities to the MME. The mapped EPS GUTI contains information of the AMF with the latest UE context in the wireless network.

[0084] The UE protects the integrity of the TAU request message using the current NAS security context identified by the GUTI used to derive the mapped EPS GUTI. More precisely, the UE may compute the NAS MAC for the TAU request as it does for NAS messages over 3GPP access. The NAS uplink count used for integrity protection of the TAU request may use the same value as the NAS uplink count. This therefore results in an increase in the NAS uplink count value stored in the NAS count pair associated with the 3GPP access. The corresponding ngKSI value for the security context is included in the eKSI parameter of the TAU request message.

[0085] In step 2, upon receiving the TAU Request, the MME obtains the AMF address from the mapped EPS GUTI value. In step 3, the MME forwards the complete TAU Request message including the eKSI, NAS-MAC and the mapped EPS GUTI in a Context Request message.

[0086] In step 4, the AMF may use the eKSI value field to identify the NAS security context and use it to validate the TAU request message as if it were a NAS message received over 3GPP access. In an example, the AMF may generate a mapped EPS security context associated with receiving a request for an inter-system change of the UE from the wireless system to the EPS. The mapped EPS security context includes security parameters created based on the security context for the wireless system, which enables security-related communications between the UE and the network entity. The AMF may further determine a UL NAS count value and a DL NAS count value for the mapped EPS security context.

[0087] In step 5, if the verification is successful, the AMF may derive the mapped EPS NAS security context. The AMF may set the EPS NAS algorithms to those indicated to the UE earlier in the NAS SMC. The AMF may include the mapped EPS NAS security context in the context response message it sends to the MME. The AMF may never pass security parameters to entities outside the wireless system.

[0088] In step 6, the UE may derive the mapped EPS NAS security context. The UE may select the EPS algorithms using those received in an earlier NASSMC from the AMF. The UE may immediately activate the mapped EPS security context and prepare it for processing the TAU Accept message in step 7. For example, the UE may generate a mapped EPS security context associated with an inter-system change of the UE from a wireless system to EPS. The mapped EPS security context includes security parameters created based on the security context for the wireless system, which enables security-related communications between the UE and network entities. The UE may further determine an UL NAS count value and a DL NAS count value for the mapped EPS security context.

[0089] In step 7, the MME compares the UE security algorithm with its configured list after it receives the context response message. If an algorithm change is required, the MME may select the NAS algorithm with the highest priority and present in the UE security capabilities from its configured list and initiate a NAS SMC to the UE. Otherwise, steps 8-10 may be skipped. In steps 8-10, the MME and the UE perform a NAS SMC to derive new NAS keys using the new algorithm. For example, in step 8, the MME transmits a NAS SMC corresponding to the selected EPS algorithm. In step 9, the UE may derive new NAS keys based on the selected algorithm in the NAS SMC. In step 10, the UE may transmit a NAS SMP after deriving the NAS keys. In step 11, the MME completes the procedure with a TAU Accept message. In step 12, the UE transmits a TAU Complete message to the MME.

[0090] Figure 6 600 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104; device 902 / 82'; processing system 914, which may include memory 360 and may be the entire UE 104 or a component of UE 104 (such as TX processor 368, RX processor 356 and / or controller processor 359)).

[0091] At 602, method 600 includes generating, by a user equipment (UE), a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an evolved packet system (EPS), wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity. In an aspect, configuration component 198 (e.g., in conjunction with processor 359 / 904, memory 360 / 906, and generation component 240) may generate a mapped EPS security context associated with an inter-system change of the UE 104 from the wireless system to the EPS. The mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE 104 and a network entity (e.g., MME 132). Thus, the UE 104 and / or configuration component 198 (e.g., in conjunction with the controller / processor 359 (which may include the memory 360), the processor 912 (which may include the memory 916, the modem 940, the TX processor 368, and the transceiver 902)) may define a device for generating, by the UE, a mapped EPS security context associated with an inter-system change of the UE from a wireless system to EPS, wherein the mapped EPS security context includes security parameters created based on the security context for the wireless system, which security parameters enable security-related communications between the UE and a network entity.

[0092] At 604, method 600 includes determining an uplink (UL) non-access stratum (NAS) count value and a downlink (DL) NAS count value for the mapped EPS security context. In one aspect, configuration component 198 (e.g., in conjunction with processor 359 / 904, memory 360 / 906, and determining component 242) may determine the UL NAS count value and the DL NAS count value for the mapped EPS security context. As such, UE 104 and / or configuration component 198 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processor 912 (which may include memory 916, modem 940, TX processor 368, and transceiver 902)) may define means for determining the UL NAS count value and the DL NAS count value for the mapped EPS security context.

[0093] At 606, method 600 includes transmitting, by the UE to a network entity, a NAS message including a UL NAS count value for the mapped EPS security context. In one aspect, configuration component 198 (e.g., in conjunction with processor 359 / 904, memory 360 / 906, TX processor 368, and transceiver 910) may transmit a NAS message to a network entity, the NAS message including a UL NAS count value for the mapped EPS security context. As such, UE 104 and / or configuration component 198 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processor 912 (which may include memory 916, modem 940, TX processor 368, and transceiver 902)) may define means for transmitting a NAS message to a network entity, the NAS message including a UL NAS count value for the mapped EPS security context.

[0094] In an example, determining the UL NAS count value for the mapped EPS security context further includes setting the UL NAS count value to the UL NAS count value of the security context. And determining the DL NAS count value for the mapped EPS security context further includes setting the DL NAS count value to the DL NAS count value of the security context.

[0095] In another example, determining the UL NAS count value for the mapped EPS security context further includes resetting the UL NAS count value to 0. And determining the DL NAS count value for the mapped EPS security context further includes resetting the DL NAS count value to 0. For example, the method 600 may include incrementing the UL NAS count value by 1 upon resetting the UL NAS count value to 0, and transmitting the NAS message to the network entity further includes transmitting the NAS message with the UL NAS count value to the network entity.

[0096] In an example, the inter-system change of the UE from the wireless system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS. For example, the method 600 may include the configuration component 198 receiving a handover command at the UE 104 in response to the handover procedure of the UE from the wireless system to the EPS, the handover command including security parameters for generating the mapped EPS security context; and wherein generating the mapped EPS security context further includes generating the mapped EPS security context based on the handover command. In an example, receiving the handover command further includes receiving the handover command from an access mobility and management function (AMF).

[0097] In an example, the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS. For example, the method 600 may include transmitting, by the UE to the network entity, a tracking area update (TAU) request, the TAU request including a previous UL NAS count value of the security context; and wherein generating the mapped EPS security context further includes generating the mapped EPS security context after transmitting the TAU request.

[0098] Figure 7 700 is a flow chart of a wireless communication method. The method may be performed by a network entity (e.g., AMF 192; device 902 / 82'; processing system 914, which may include memory 376 and may be the entire AMF 192 or a component of AMF 192 (such as TX processor 316, RX processor 370 and / or controller processor 375)).

[0099] At 702, method 700 includes generating, by a network entity, a mapped EPS security context associated with receiving a request for an inter-system change of a user equipment (UE) from a wireless system to an evolved packet system (EPS), wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and the network entity. In one aspect, configuration component 199 (e.g., in conjunction with processor 375 / 1104, memory 376 / 1106, and generation component 241) may generate a mapped EPS security context associated with receiving a request for an inter-system change of a UE 104 from a wireless system to an EPS. The mapped EPS security context includes security parameters created based on a 5G security context for the wireless system, the security parameters enabling security-related communications between the UE 104 and a network entity (e.g., AMF 192). Thus, the network entity 102 and / or the configuration component 199 (e.g., in conjunction with the controller / processor 376 (which may include the memory 376), the processor 1112 (which may include the memory 1106, the RX processor 370, and the transceiver 1110)) may define a device for generating, by the network entity, a mapped EPS security context associated with receiving a request for an inter-system change of the UE from a wireless system to EPS, wherein the mapped EPS security context includes security parameters created based on the security context for the wireless system, which security parameters enable security-related communications between the UE and the network entity.

[0100] At 704, method 700 includes determining an uplink (UL) non-access stratum (NAS) count value and a downlink (DL) NAS count value for the mapped EPS security context. In one aspect, configuration component 199 (e.g., in conjunction with processor 375 / 904, memory 376 / 906, and determining component 243) may determine the UL NAS count value and the DL NAS count value for the mapped EPS security context. As such, network entity 102 and / or configuration component 199 (e.g., in conjunction with controller / processor 375 (which may include memory 376), processor 1112 (which may include memory 1106, RX processor 370, and transceiver 1110)) may define means for determining the UL NAS count value and the DL NAS count value for the mapped EPS security context.

[0101] At 706, method 700 includes transmitting, by the first network entity to the second network entity, the mapped EPS security context with the UL NAS count value and the DL NAS count value. In one aspect, configuration component 199 (e.g., in conjunction with processor 375 / 1104, memory 376 / 1106, TX processor 316, and transceiver 1110) may transmit the mapped EPS security context with the UL NAS count value and the DL NAS count value to the second network entity. As such, network entity 102 and / or configuration component 199 (e.g., in conjunction with controller / processor 375 (which may include memory 376), processor 1112 (which may include memory 1106, RX processor 370, and transceiver 1110)) may define means for transmitting the mapped EPS security context with the UL NAS count value and the DL NAS count value to the second network entity.

[0102] In an example, determining the UL NAS count value for the mapped EPS security context further includes setting the UL NAS count value to the UL NAS count value of the security context. And determining the DL NAS count value for the mapped EPS security context further includes setting the DL NAS count value to the DL NAS count value of the security context.

[0103] In an example, determining the UL NAS count value for the mapped EPS security context further includes resetting the UL NAS count value to 0. And determining the DL NAS count value for the mapped EPS security context further includes resetting the DL NAS count value to 0. The DL NAS count and Figure 6 The UL NAS count of the UE in is similarly incremented by 1.

[0104] In an example, the inter-system change of the UE from the wireless system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS. For example, the method 700 may include receiving a handover required message at a first network entity in response to initiation of a handover backhaul of the UE from the wireless system to the EPS, the handover required message including one or more security capabilities of the UE, and wherein generating the mapped EPS security context further includes generating the mapped EPS security context based on the handover required message.

[0105] In an example, the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS. For example, the method 700 may include receiving, by the first network entity, a tracking area update (TAU) request forwarded from the second network entity, the TAU request being transmitted by the UE and including a previous UL NAS count value of the security context; and wherein generating the mapped EPS security context further includes generating the mapped EPS security context based on receiving the TAU request.

[0106] In an example, the first network entity corresponds to an Access and Mobility Management Function (AMF).

[0107] In an example, the second network entity corresponds to a Mobility Management Entity (MME).

[0108] Figure 8 800 is a conceptual data flow diagram illustrating data flow between different devices / components in an example device 802. The device can be a UE 104 and / or a network entity (e.g., AMF 192). The device includes a component 804 that receives a signal from a remote device 850. The device includes a component 806 that generates a mapped EPS security context associated with an inter-system change of the UE from a wireless system (e.g., a 5G system) to EPS (e.g., as described in conjunction with blocks 602 and 702). The device includes a component 808 that determines a UL / DL NAS count value for the mapped EPS security context (e.g., as described in conjunction with blocks 604 in conjunction with 704). The device includes a component 810 that transmits the mapped EPS security context (e.g., as described in conjunction with blocks 606 and 706).

[0109] The apparatus may include executing Figure 6 and 7 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 6 and 7 Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0110] Fig. 9900 is an illustration of an example of a hardware implementation of a device 802' employing a processing system 914. The processing system 914 may be implemented with a bus architecture generally represented by a bus 924. Depending on the specific application of the processing system 914 and the overall design constraints, the bus 924 may include any number of interconnecting buses and bridges. The bus 924 links together various circuits including one or more processors and / or hardware components (represented by the processor 904, components 804, 806, 808, and computer readable media / memory 906). The bus 924 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0111] The processing system 914 may be coupled to the transceiver 910. The transceiver 910 is coupled to one or more antennas 920. The transceiver 910 provides a means for communicating with various other devices via a transmission medium. The transceiver 910 receives signals from one or more antennas 920, extracts information from the received signals, and provides the extracted information to the processing system 914 (specifically, the receiving component 804). In addition, the transceiver 910 receives information from the processing system 914 (specifically, the transmission component 810), and generates a signal to be applied to the one or more antennas 920 based on the received information. The processing system 914 includes a processor 904 coupled to a computer-readable medium / memory 906. The processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 906. The software, when executed by the processor 904, causes the processing system 914 to perform the various functions described above for any particular device. The computer-readable medium / memory 906 may also be used to store data manipulated by the processor 904 when executing the software. The processing system 914 further includes at least one of the components 804, 806, 808. These components may be software components running in the processor 904, software components residing / stored in the computer-readable medium / memory 906, one or more hardware components coupled to the processor 904, or some combination thereof. The processing system 914 may be a component of the base station 310 and may include the memory 376 and / or at least one of the following: the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 914 may be the entire base station (e.g., see Figure 3 310). The processing system 914 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 914 may be the entire UE (e.g., see Figure 3 of 350).

[0112] In one configuration, an apparatus 802 / 802' for wireless communication includes means for generating, by a network entity, a mapped EPS security context in response to receiving a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and the network entity; means for determining a DL NAS count value for the mapped EPS security context, wherein the DL NAS count value is incremented by 1 from a previous DL NAS count value of the security context without being reset; and means for transmitting, by the network entity, the mapped EPS security context with the DL NAS count value to the UE after receiving the request for an inter-system change of the UE from the wireless system to the EPS. The aforementioned means may be one or more of the aforementioned components of the apparatus 802 and / or the processing system 914 of the apparatus 802' configured to perform the functions recited by the aforementioned means. As described above, the processing system 914 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0113] In one configuration, an apparatus 802 / 802' for wireless communication includes means for generating, by a UE, a mapped EPS security context in response to an inter-system change of the UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; means for determining an UL NAS count value for the mapped EPS security context, wherein the UL NAS count value is incremented by 1 from a previous UL NAS count value of the security context without being reset; and means for transmitting, by the UE, the mapped EPS security context with the UL NAS count value to the network entity after the inter-system change of the UE from the wireless system to the EPS. The aforementioned means may be one or more of the aforementioned components of the apparatus 802 and / or the processing system 914 of the apparatus 802' configured to perform the functions recited by the aforementioned means. As described above, the processing system 914 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0114] Fig.101 is a conceptual data flow diagram 1000 illustrating data flow between different devices / components in an example device 1002. The device can be a UE 104 and / or a network entity (e.g., AMF 192). The device includes a component 1004 that receives a signal from a remote device 1050. The device includes a component 1006 that generates a mapped EPS security context associated with an inter-system change of the UE from a wireless system to EPS (e.g., as described in conjunction with blocks 602 and 702). The device includes a component 1008 that determines a UL / DL NAS count value for the mapped EPS security context (e.g., as described in conjunction with blocks 604 and 704). The device includes a component 1010 that transmits the mapped EPS security context (e.g., as described in conjunction with blocks 606 and 706).

[0115] The apparatus may include executing Figure 6 and 7 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 6 and 7 Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0116] Fig.11 1 is a diagram 1100 illustrating an example of a hardware implementation of a device 1002' employing a processing system 1114. The processing system 1114 may be implemented with a bus architecture generally represented by a bus 1124. Depending on the specific application of the processing system 1114 and the overall design constraints, the bus 1124 may include any number of interconnecting buses and bridges. The bus 1124 links various circuits together, including one or more processors and / or hardware components (represented by the processor 1104, components 1004, 1006, 1008, and computer readable medium / memory 1106). The bus 1124 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0117] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other devices over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, the transmitting component 1010) and generates signals to be applied to the one or more antennas 1120 based on the received information. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described above for any particular device. The computer-readable medium / memory 1106 may also be used to store data that is manipulated by the processor 1104 when executing software. The processing system 1114 further includes at least one of the components 1004, 1006, 1008. These components may be software components that run in the processor 1104, software components that reside / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 may be a component of the base station 310 and may include the memory 376 and / or at least one of the following: the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1114 may be the entire base station (e.g., see Figure 3 310). The processing system 1114 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 1114 may be the entire UE (e.g., see Figure 3 of 350).

[0118] In one configuration, the device 1002 / 802' for wireless communication includes means for generating, by a network entity, a mapped EPS security context in response to receiving a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and the network entity; means for determining a DLNAS count value for the mapped EPS security context, wherein the DL NAS count value is incremented by 1 from a previous DL NAS count value of the security context without being reset; and means for transmitting, by the network entity, the mapped EPS security context with the DL NAS count value to the UE after receiving the request for an inter-system change of the UE from the wireless system to the EPS. The aforementioned means may be one or more of the aforementioned components of the device 1002 and / or the processing system 1114 of the device 1002' configured to perform the functions recited by the aforementioned means. As described above, the processing system 1114 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0119] In one configuration, the apparatus 1002 / 802' for wireless communication includes means for generating, by a UE, a mapped EPS security context in response to an inter-system change of the UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; means for determining an UL NAS count value for the mapped EPS security context, wherein the UL NAS count value is incremented by 1 from a previous UL NAS count value of the security context without being reset; and means for transmitting, by the UE, the mapped EPS security context with the UL NAS count value to the network entity after the inter-system change of the UE from the wireless system to the EPS. The aforementioned means may be one or more of the aforementioned components of the apparatus 1002 and / or the processing system 1114 of the apparatus 1002' configured to perform the functions recited by the aforementioned means. As described above, the processing system 1114 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0120] For example, in one aspect, the present disclosure includes a method, apparatus, and computer-readable medium for wireless communication, the method, apparatus, and computer-readable medium being used to configure a NAS count value of a mapped EPS security context associated with an inter-system change of a UE from a wireless system to an EPS. This aspect may include: generating, by a UE, a mapped EPS security context associated with an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes a security parameter created based on a security context for the wireless system, the security parameter enabling security-related communications between the UE and a network entity; determining a UL NAS count value for the mapped EPS security context; and transmitting, by the UE to the network entity, a NAS message including a UL NAS count value of the mapped EPS security context.

[0121] In another example, on the one hand, the present disclosure includes a method, apparatus, and computer-readable medium for wireless communication, which are used to perform the following operations: generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a UE from a wireless system to an EPS, wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; determining a DL NAS count value for the mapped EPS security context; and transmitting, by the first network entity to the second network entity, the mapped EPS security context with the DL NAS count value.

[0122] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0123] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recorded in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

Claims

1. A wireless communication method, comprising: generating, by a user equipment, UE, a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an evolved packet system, EPS, wherein the mapped EPS security context comprises security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; Determining an uplink UL non-access stratum NAS count value and a downlink DL NAS count value for the mapped EPS security context; as well as A NAS message is transmitted by the UE to the network entity, wherein the NAS message includes the UL NAS count value of the mapped EPS security context.

2. The method of claim 1 , wherein determining the UL NAS count value and the DL NAS count value for the mapped EPS security context further comprises setting the UL NAS count value to the UL NAS count value of the security context; and determining the DL NAS count value for the mapped EPS security context further comprises setting the DL NAS count value to the DL NAS count value of the security context.

3. The method of claim 1 , wherein determining the UL NAS count value and the DL NAS count value for the mapped EPS security context further comprises resetting the UL NAS count value to 0; and determining the DL NAS count value for the mapped EPS security context further comprises resetting the DL NAS count value to 0.

4. The method of claim 3, further comprising: When resetting the UL NAS count value to 0, incrementing the UL NAS count value by 1; and The transmitting the NAS message to the network entity further comprises transmitting the NAS message with the UL NAS count value to the network entity. 5 . The method of claim 1 , wherein the inter-system change of the UE from the wireless system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS.

6. The method of claim 5, further comprising: receiving, in response to the handover procedure of the UE from the wireless system to the EPS, a handover command at the UE, the handover command including the security parameters for generating the mapped EPS security context; and Wherein generating the mapped EPS security context further comprises generating the mapped EPS security context based on the handover command.

7. The method of claim 6, wherein receiving the handover command further comprises receiving the handover command from an access mobility and management function (AMF).

8. The method of claim 1, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS.

9. The method of claim 8, further comprising: Transmitting, by the UE, a tracking area update TAU request to the network entity, the TAU request including the UL NAS count value of the security context; and Wherein generating the mapped EPS security context further comprises generating the mapped EPS security context after transmitting the TAU request.

10. The method of claim 1, wherein the network entity corresponds to a Mobility Management Entity (MME).

11. A wireless communication method, comprising: generating, by a first network entity, a mapped EPS security context associated with a request for an inter-system change of a user equipment UE from a wireless system to an evolved packet system EPS, wherein the mapped EPS security context comprises security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; Determining a downlink DL non-access stratum NAS count value and an uplink UL NAS count value for the mapped EPS security context; as well as The mapped EPS security context with the DL NAS count value is transmitted by the first network entity to the second network entity.

12. The method of claim 11, wherein determining the UL NAS count value and the DL NAS count value for the mapped EPS security context further comprises setting the UL NAS count value and the DL NAS count value to the UL NAS count value and the DL NAS count value of the security context.

13. The method of claim 11, wherein determining the UL NAS count value and the DL NAS count value for the mapped EPS security context further comprises resetting the UL NAS count value to zero.

14. The method of claim 11, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS.

15. The method of claim 14, further comprising: In response to initiation of the handover procedure of the UE from the wireless system to the EPS, receiving, at the first network entity, a handover required message, the handover required message including one or more security capabilities of the UE; and The generating the mapped EPS security context further comprises generating the mapped EPS security context based on the handover required message.

16. The method of claim 11, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS.

17. The method of claim 16, further comprising: receiving, by the first network entity, a tracking area update TAU request forwarded from the second network entity, the TAU request being transmitted by the UE and including a previous UL NAS count value of the security context; and Wherein generating the mapped EPS security context further comprises generating the mapped EPS security context based on receiving the TAU request.

18. The method according to claim 11, wherein the first network entity corresponds to an access and mobility management function (AMF).

19. The method of claim 11, wherein the second network entity corresponds to a Mobility Management Entity (MME).

20. A user equipment UE for wireless communication, comprising: Transceiver; a memory configured to store instructions; as well as one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to execute the instructions for: generating a mapped EPS security context associated with an inter-system change of the UE from a wireless system to an Evolved Packet System (EPS), wherein the mapped EPS security context includes security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a network entity; Determining an uplink UL non-access stratum NAS count value and a downlink DL NAS count value for the mapped EPS security context; as well as A NAS message is transmitted to the network entity, the NAS message including the UL NAS count value of the mapped EPS security context.

21. The UE of claim 20, wherein the one or more processors configured to determine the UL NAS count value and the DL NAS count value for the mapped EPS security context are further configured to set the UL NAS count value to the UL NAS count value of the security context; and determining the DL NAS count value for the mapped EPS security context further includes setting the DL NAS count value to the DL NAS count value of the security context.

22. The UE of claim 20, wherein the one or more processors configured to determine the UL NAS count value and the DL NAS count value for the mapped EPS security context are further configured to reset the UL NAS count value to 0; and determining the DL NAS count value for the mapped EPS security context further includes resetting the DL NAS count value to 0.

23. The UE of claim 22, wherein the one or more processors are configured to: incrementing the UL NAS count value by 1 upon resetting the UL NAS count value to 0; and Wherein the one or more processors configured to transmit the NAS message to the network entity are further configured to transmit the NAS message with the UL NAS count value to the network entity.

24. The UE of claim 20, wherein the inter-system change of the UE from the system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS.

25. The UE of claim 20, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS.

26. A network entity for wireless communication, comprising: Transceiver; a memory configured to store instructions; as well as one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to execute the instructions for: generating a mapped EPS security context associated with a request for an inter-system change of a user equipment UE from a wireless system to an evolved packet system EPS, wherein the mapped EPS security context comprises security parameters created based on a security context for the wireless system, the security parameters enabling security-related communications between the UE and a second network entity; Determining a downlink DL non-access stratum NAS count value and an uplink UL NAS count value for the mapped EPS security context; as well as The mapped EPS security context with the DL NAS count value is transmitted to the second network entity.

27. The network entity of claim 26, wherein the one or more processors configured to determine the UL NAS count value and the DL NAS count value for the mapped EPS security context are further configured to set the UL NAS count value and the DL NAS count value to the UL NAS count value and the DL NAS count value of the 5G security context.

28. The network entity of claim 26, wherein the one or more processors configured to determine the UL NAS count value and the DL NAS count value for the mapped EPS security context are further configured to reset the UL NAS count value to zero.

29. The network entity of claim 26, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to a handover procedure of the UE from the wireless system to the EPS.

30. The network entity of claim 26, wherein the inter-system change of the UE from the wireless system to the EPS corresponds to idle mode mobility of the UE from the wireless system to the EPS.