METHOD AND DEVICE FOR PERFORMING COMMUNICATION IN WIRELESS COMMUNICATION SYSTEM

Abstract

A method of a user equipment (UE) in a wireless communication system includes: transmitting, to a core entity, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); receiving, from the core entity, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and transmitting, to the core entity, a security mode complete message including the UE radio capability ID information.

Claims

1. A method of a user equipment (UE) in a wireless communication system, the method comprising: transmitting, to a core entity, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); receiving, from the core entity, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and transmitting, to the core entity, a security mode complete message including the UE radio capability ID information.

2. The method of claim 1, wherein the receiving of the security mode command message comprises receiving, from the core entity, the security mode command message, based on information for a UE radio capability ID available in the core entity.

3. The method of claim 1, wherein the UE radio capability information comprises bit information indicating that the UE supports the UE radio capability ID.

4. The method of claim 2, wherein the information for the UE radio capability ID available in the core entity indicates that the UE radio capability ID available in the core entity does not exist.

5. The method of claim 1, wherein the core entity comprises a mobility management entity (MME), and wherein the MME comprises an entity that is a handover target.

6. A method of a core entity in a wireless communication system, the method comprising: receiving, from a user equipment (UE), a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); transmitting, to the UE, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and receiving, from the UE, a security mode complete message including the UE radio capability ID information.

7. The method of claim 6, wherein the transmitting of the security mode command message comprises transmitting, to the UE, the security mode command message, based on information for a UE radio capability ID available in the core entity.

8. The method of claim 6, wherein the UE radio capability information comprises bit information indicating that the UE supports the UE radio capability ID.

9. The method of claim 7, wherein the information for the UE radio capability ID available in the core entity indicates that the UE radio capability ID available in the core entity does not exist.

10. The method of claim 6, wherein the core entity comprises a mobility management entity (MME), and wherein the MME comprises an entity that is a handover target.

11. A user equipment (UE) in a wireless communication system, the UE comprising: a transceiver; and at least one processor configured to: transmit, to a core entity via the transceiver, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); receive, from the core entity via the transceiver, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and transmit, to the core entity via the transceiver, a security mode complete message including the UE radio capability ID information.

12. The UE of claim 11, wherein the at least one processor is further configured to receive, from the core entity via the transceiver, the security mode command message, based on information for a UE radio capability ID available in the core entity.

13. The UE of claim 11, wherein the UE radio capability information comprises bit information indicating that the UE supports the UE radio capability ID.

14. The UE of claim 12, wherein the information for the UE radio capability ID available in the core entity indicates that the UE radio capability ID available in the core entity does not exist.

15. The UE of claim 11, wherein the core entity comprises a mobility management entity (MME), and wherein the MME comprises an entity that is a handover target.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG. 1 is a diagram for describing an environment in which a 5th generation (5G) network and a 4th generation (4G) network coexist, according to an embodiment of the disclosure.

[0020] FIG. 2 is a diagram for describing an environment in which a 5G network and a 4G network coexist, according to another embodiment of the disclosure.

[0021] FIG. 3 is a diagram for describing a method of transmitting user equipment (UE) radio information when a UE is handed over from a 5G system to a 4G system, in an environment in which the 5G system and a long-term evolution (LTE) system coexist, according to an embodiment of the disclosure.

[0022] FIG. 4 is a diagram for describing a method of transmitting UE radio information when a UE is handed over from a 4G system to a 5G system, in an environment in which the 5G system and the 4G system coexist, according to an embodiment.

[0023] FIG. 5 is a diagram for describing a non access stratum (NAS) message information processing and communicating method in a 5G network environment, according to an embodiment of the disclosure.

[0024] FIG. 6 is a diagram for describing an NAS message information processing and communicating method in a 5G network environment, according to an embodiment of the disclosure.

[0025] FIG. 7 is a block diagram of a structure of a UE, according to an embodiment.

[0026] FIG. 8 is a block diagram of a structure of a network entity, according to an embodiment.

[0027] FIG. 9 is a diagram for describing an environment in which a 5G network and a 4G network coexist, according to an embodiment of the disclosure.

[0028] FIG. 10 is a diagram for describing an NAS message information processing and communicating method in a 5G network environment, according to an embodiment of the disclosure.

[0029] FIG. 11 is a flowchart for describing an operation method of a UE, according to an embodiment of the disclosure.

[0030] FIG. 12 is a diagram for describing an operation method of a core entity, according to an embodiment of the disclosure.

DETAILED DESCRIPTION

[0031] According to an embodiment of the disclosure, a method of a core entity in a wireless communication system, includes: receiving, from a user equipment (UE), a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); transmitting, to the UE, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and receiving, from the UE, a security mode complete message including the UE radio capability ID information.

[0032] According to an embodiment of the disclosure, a method of a user equipment (UE) in a wireless communication system, includes: transmitting, to a core entity, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); receiving, from the core entity, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and transmitting, to the core entity, a security mode complete message including the UE radio capability ID information.

[0033] According to an embodiment of the disclosure, a user equipment (UE) in a wireless communication system includes: a transceiver; and at least one processor configured to: transmit, to a core entity via the transceiver, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); receive, from the core entity via the transceiver, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and transmit, to the core entity via the transceiver, a security mode complete message including the UE radio capability ID information.

[0034] According to an embodiment of the disclosure, a core entity in a wireless communication system includes: a transceiver; and at least one processor configured to: receive, from a user equipment (UE) through the transceiver, a tracking area update (TAU) request message including UE radio capability information associated with a UE radio capability identity (ID); transmit, to the UE through the transceiver, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information; and receive, from the UE through the transceiver, a security mode complete message including the UE radio capability ID information.

[0035] Hereinafter, exemplary embodiments of the disclosure will be described in detail with reference to the accompanying drawings. Here, it should be noted that like reference numerals denote like elements in the accompanying drawings. Also, detailed descriptions about known functions and configurations that may blur the gist of the disclosure will be omitted.

[0036] While describing embodiments in the present specification, descriptions of technical contents that are well known in the technical field to which the disclosure belongs and are not directly related to the disclosure will be omitted. By omitting the unnecessary description, the gist of the disclosure may be more clearly conveyed without obscuring the subject matter.

[0037] For the same reasons, components may be exaggerated, omitted, or schematically illustrated in drawings for clarity. Also, the size of each component does not completely reflect the actual size. In the drawings, like reference numerals denote like elements.

[0038] Advantages and features of one or more embodiments of the disclosure and methods of accomplishing the same may be understood more readily by reference to the following detailed description of the embodiments of the disclosure and the accompanying drawings. In this regard, embodiments of the disclosure may have different forms and should not be construed as being limited to the descriptions set forth herein. Rather, these embodiments are provided so that the disclosure will be thorough and complete and will fully convey the concept of the present embodiments of the disclosure to one of ordinary skill in the art. Throughout the specification, like reference numerals denote like elements.

[0039] Also, terms for identifying access nodes, terms denoting network entities, terms denoting messages, terms denoting interfaces between network entities, terms denoting various types of identification information, etc. used herein are exemplified for convenience of description. Thus, the terms used in the disclosure are not limited and other terms denoting targets having the same technical meanings may be used.

[0040] Hereinafter, for convenience of descriptions, the disclosure uses terms and names defined in the standards for a 5th generation (5G) or long-term evolution (LTE) system. However, the disclosure is not limited by such terms and names, and may be equally applied to systems conforming to other standards.

[0041] In other words, while describing the embodiments of the disclosure in detail, a main target is a communication standard defined by 3 GPP, but an important gist of the disclosure may be applied, with a slight modification, to other communication systems having a similar technical background, within a range not greatly departing from the scope of the disclosure, and the applicability would be determined by one of ordinary skill in the art.

[0042] FIG. 1 is a diagram for describing an environment in which a 5th generation (5G) network and a 4th generation (4G) network coexist, according to an embodiment of the disclosure.

[0043] A 5G network system according to an embodiment of the disclosure may include a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), a 5G radio access network (RAN), a user data management (UDM), and a policy control function (PFC), but this is only an example and entities included in the 5G network system are not limited thereto. According to another embodiment, the 5G network system may also include an authentication server function (AUSF) and an authentication, authorization, and accounting (AAA) for authentication of the entities.

[0044] Meanwhile, an N3 interworking function (N3IWF) exists for a case where a user equipment (UE) communicates through a non 3GPP access, and when the non 3GPP access is used, session management may be processed through the UE, the non 3GPP access, the N3IWF, and the SMF and may be controlled by the SMF, and mobility management may be processed through the UE, the non 3GPP access, the N3IWF, and the AMF and may be controlled by the AMF.

[0045] In an embodiment of the disclosure, it is assumed that 5G and 4G systems coexist. In 4G, a mobility management entity (MME) in charge of mobility management and session management may be in charge of controlling communication of the UE. In 5G, mobility management and session management entities may be separated into the AMF and the SMF. Meanwhile, a stand alone deployment structure performing communication only with 5G communication entities for 5G communication, and a non stand alone deployment structure using 4G and 5G entities for the 5G communication may also be considered.

[0046] As shown in FIG. 1, a deployment may be possible, in which, when the UE communicates with a network, the UE uses an evolved node B (eNB) for control and uses a 5G entity as a core network. In this case, in a non access stratum (NAS) that is a layer 3, the UE and the AMF are in charge of the mobility management and the UE and the SMF are in charge of the session management, whereas an access stratum (AS) that is a layer 2 is transmitted through the UE and the eNB, and thus there is a need for a method of generating and managing security context accordingly. In this regard, the disclosure describes security context generation, management, and protocol exchange applicable to such a deployment situation.

[0047] In the disclosure, a UE may perform general EUTRAN communication via the eNB and the MME, and perform data communication via a serving gateway and a public data network (PDN) gateway, in relation to 4G. Meanwhile, a HSS may be present and thus subscription information regarding the UE, UE-related security key information, and the like may be transmitted.

[0048] A communication network to which the disclosure is applied is a network in which 5G and 4G coexist, but the disclosure may be applied to another system when the same concept is applied to the other system, within the scope apprehended by one of ordinary skill in the art.

[0049] FIG. 1 relates to a scenario that may occur when the UE moves from 5G to 4G or is moved due to handover or mobility. In other words, the UE moves from 5G to 4G, the AMF of 5G supports radio access-related information, and the LTE MME also supports the radio access-related information.

[0050] In other words, the UE moves from a network having the 5G AMF supporting the radio access-related information to the 4G LTE MME supporting the radio access-related information, and it is unable for the UE, MME, and the AMF to verify whether the other has valid radio access-related information.

[0051] FIG. 2 relates to a scenario that may occur when a UE moves from 4G to 5G or is moved due to handover or mobility. In other words, the UE moves from 4G to 5G, and an AMF of 5G may or may not support radio access-related information, and an MME of 4G may or may not support the radio access-related information.

[0052] That is, the UE moves from a network having the 4G MME supporting the radio access-related information to a network having the 5G AMF supporting the radio access-related information, and it is unable for the UE, MME, and the AMF to verify whether the other has valid radio access-related information.

[0053] FIG. 3 is a diagram for describing a method of transmitting UE radio information when a UE is handed over from a 5G system to a 4G system, in an environment in which the 5G system and an LTE system coexist, according to an embodiment of the disclosure.

[0054] In operation 301, a UE 101 may transmit a registration request to an AMF.

[0055] Here, when the UE supports transmitting of UE radio information (for example, UE radio capability information identity (ID)), the UE may transmit a registration request non access stratum (NAS) message including the UE radio information ID (for example, a UE radio capability ID).

[0056] For example, a UE radio capability ID information information element (IE) may be configured as Table 1 below while including a part of a UE radio capability ID information value as an IE.

[0057] The UE radio capability ID information may be a manufacturer ID, such as an ID assigned by each manufacturer to a product, according to an embodiment. According to another embodiment, the UE radio capability ID information may be network assigned or public land mobile network (PLMN) assigned UE radio information related to a PLMN assigned already as the UE accessed a network, or a PLMN assigned UE radio capability information.

[0058] In operation 311, a source 5G RAN 103 may transmit a handover required message to a (the?) source AMF 111.

[0059] Here, the UE radio information (for example, the UE radio capability information ID) may be transmitted from the source 5G RAN 103 to the source AMF 111.

[0060] In operation 313, the source AMF 111 may transmit a forward relocation request message to a target MME 183. Here, the source AMF 111 may transmit the UE radio information (for example, the UE radio capability information ID) received from the UE 101 by including the same to the forward relocation request message.

[0061] In operation 315, the target MME 183 may verify whether there is UE radio capability information in which the network knows about the UE 101, based on the UE radio capability information transmitted from the UE 101. In other words, when the network already has information about the UE 101, for example, it may be verified whether the network has UE radio capability information, UE manufacturer ID, or UE radio information transmitted by the UE 101. Also, when the network has the information about the UE 101, it may be verified whether information the network has regarding the UE 101 matches information transmitted by the UE.

[0062] Also, in operation 315, the source AMF 111 may generate network assigned PLMN associated UE radio information (for example, network assigned UE radio information, PLMN assigned UE radio information, or PLMN assigned UE radio capability ID information IE) and assign the same to the UE. Such an operation may be performed when information the target MME 183 has and information the UE 101 has do not match each other, or the target MME 183 is to assign the PLMN assigned UE radio information to the UE 101.

[0063] For example, the PLMN assigned UE radio capability ID information IE may be configured as Table 2 below while including a part of a PLMN assigned UE radio capability ID information value as an IE.

[0064] In operation 317, the target MME 183 may transmit a handover request message to a target eNB 181. The handover request message may include a parameter (IE) including the PLMN assigned UE radio capability ID information described above, and parameters related to the UE radio capability information ID and UE radio capability.

[0065] In operation 319, the target eNB 181 may generate a transparent container. An IE, i.e., a parameter or information, included in the transparent container is information used by a radio resource control (RRC) message or included in the RRC message thereafter, and may include the PLMN assigned UE radio capability ID information.

[0066] In operation 321, the target eNB 181 transmits a handover request acknowledgement message to the target MME 183, and at this time, the transparent container generated in operation 319 may be transmitted while including the PLMN assigned UE radio capability ID information.

[0067] Then, in operation 323, the target MME 183 may transmit a forward relocation response message to the source AMF 111.

[0068] In operation 325, the source AMF 111 transmits a handover command to the source 5G RAN 103, and at this time, the transparent container generated in operation 319 may be transmitted.

[0069] Then, in operation 327, the source 5G RAN 103 may transmit, to the UE 101, the handover command including the PLMN assigned UE radio capability ID information.

[0070] Next, in operation 331, the UE 101 may transmit handover confirmation to the target eNB 181.

[0071] In operation 333, the target eNB 181 may identify radio information capability information. Accordingly, the target eNB 181 may verify whether information the 5G RAN has and information the UE has match each other.

[0072] In operation 335, the target eNB 181 may transmit a handover notify message to the target MME 183.

[0073] In operation 341, the target MME 183 may transmit a security mode command message to the UE 101.

[0074] In operation 343, the UE 101 may transmit, to the target MME 183 a security mode complete message including a UE radio capability information IE or a UE radio information-related IE.

[0075] Then, in operation 351, the UE 101 may transmit, to the target MME 183, a tracking area update (TAU) request message including a UE radio capability IE. Here, the included UE radio capability information may be the PLMN assigned UE radio capability ID information included in the UE 101. According to another embodiment, UE radio access capability information included in the UE may be a UE radio capability ID.

[0076] FIG. 4 is a diagram for describing a method of transmitting UE radio information when a UE is handed over from a 4G system to a 5G system, in an environment in which the 5G system and the 4G system coexist, according to an embodiment.

[0077] In operation 401, the UE 101 is accessed to the source eNB 181 as an attach request is transmitted. As another example, the UE 101 may be already accessed to 4G in a connected state, and transmit a TAU request. Here, when the UE 101 supports transmitting of UE radio information (for example, a UE radio capability information ID), the UE 101 may transmit an attach request NAS message or TAU NAS message including the UE radio information ID (for example, a UE radio capability ID).

[0078] For example, a UE radio capability ID information IE may be configured as Table 3 below while including a part of a UE radio capability ID information value as an IE.

[0079] The UE radio capability ID information may be a manufacturer ID, such as an ID assigned by each manufacturer to a product, according to an embodiment. According to another embodiment, the UE radio capability ID information may be network assigned or PLMN assigned UE radio information related to a PLMN already assigned as the UE accessed a network, or PLMN assigned UE radio capability information.

[0080] In operation 411, the source eNB 181 may transmit a handover required message to the source MME 183.

[0081] Here, the UE radio information (for example, the UE radio capability information ID) may be transmitted from the source eNB 181 to the source MME 183.

[0082] In operation 413, the source MME 183 may transmit a forward relocation request message to the target AMF 111. Here, the source MME 183 may transmit the forward relocation request message including the UE radio information (for example, the UE radio capability information ID) received from the UE 101.

[0083] In operation 415, the target AMF 111 may verify whether the UE radio capability information transmitted from the UE 101 corresponds to the UE radio capability information in which the network knows about the UE. In other words, when the network already has information about the UE, for example, the target AMF 111 may verify whether the network has UE radio capability information, UE manufacturer ID, or UE radio information transmitted by the UE. Also, when it is verified that the network has the information about the UE 101, the target AMF 111 may verify whether the information the network has regarding the UE 101 matches the information transmitted by the UE.

[0084] Also, in operation 415, the target AMF 111 may generate network assigned PLMN associated UE radio information (for example, network assigned UE radio information, PLMN assigned UE radio information, or PLMN assigned UE radio capability ID information IE) and assign the same to the UE. Such a case may occur when information the AMF has and information the UE has do not match each other or when the AMF is to assign the PLMN assigned UE radio information to the UE.

[0085] For example, the PLMN assigned UE radio capability ID information IE may be configured as Table 4 below while including a part of a PLMN assigned UE radio capability ID information value as an IE.

[0086] In operation 417, a handover request message may be transmitted from the target AMF 111 to the target 5G RAN 103. The handover request message may include an IE, i.e., a parameter, including the PLMN assigned UE radio capability ID information described above, and parameters related to the UE radio capability information ID and UE radio capability.

[0087] In operation 419, the target 5G RAN 103 may generate a transparent container. The transparent container may include the PLMN assigned UE radio capability ID information as information used by an RRC message thereafter.

[0088] In operation 421, the target 5G RAN 103 may transmit a handover request acknowledgement message to the target AMF 111, and at this time, the transparent container including the PLMN assigned UE radio capability ID information generated in operation 419 may be transmitted.

[0089] In operation 423, the target AMF 111 may transmit a forward relocation response message to the source MME 183.

[0090] In operation 425, the source MME 183 transmits a handover command to the source eNB 181, and at this time, the transparent container generated in operation 419 may be transmitted.

[0091] Then, in operation 427, the handover command including the PLMN assigned UE radio capability ID information may be transmitted from the source eNB 181 to the UE 101.

[0092] Next, in operation 431, the UE 101 may transmit handover confirmation to the target 5G RAN 103.

[0093] In operation 433, the target 5G RAN 103 may identify radio information capability information. This is to check whether information the target 5G RAN 103 has matches information the UE has.

[0094] In operation 435, the target 5G RAN 103 may transmit a handover notify message to the target AMF 111.

[0095] Then, in operation 451, the UE 101 may transmit, to the target AMF 111, a registration request including a UE radio capability IE. Here, the included UE radio capability information may be the PLMN assigned UE radio capability ID information included in the UE. According to another embodiment, the UE radio capability information may be UE radio access capability information, i.e., UE radio capability ID, included in the UE 101.

[0096] FIG. 5 is a diagram for describing an NAS message information processing and communicating method in a 5G network environment, according to an embodiment of the disclosure.

[0097] In operation 501, the UE 101 is communicating with an AMF 111-2 and an SMF in a 5G network.

[0098] In operation 511, the UE 101 may perform a TAU request by moving from the 5G network to a 4G network. Here, the UE 101 transmits TAU to an MME and notifies a network whether UE network capability supports UE radio information.

[0099] In Table 5 below, the UE 101 may transmit radio access-related information by using a UE network capability IE included in a TAU request message.

TABLE-US-00001 TABLE 5 TAU Request Message Information Type/ IEI Element Reference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security M V ½ header type header type 9.3.1 Tracking area Message type M V 1 update 9.8 request message identity EPS update EPS update M V ½ type type 9.9.3.14 NAS key set NAS key set M V ½ identifier identifier 9.9.3.21 Old GUTI EPS mobile M LV 12  identity 9.9.3.12 B- Non-current NAS key set O TV 1 native NAS identifier key set 9.9.3.21 identifier   8- GPRS Ciphering key O TV 1 ciphering key Sequence sequence number number 9.9.3.4a 19 Old P-TMSI P-TMSI O TV 4 signature signature 9.9.3.26 50 Aditional EPS mobile O TLV 13  GUTI identity 9.9.3.12 55 Nonce.sub.UE Nonce 9.9.3.25 O TV 5 58 UE network UE network O TLV 4-15 capability capability 9.9.3.34 52 Last visited Tracking area O TV 6 registered identity TAI 9.9.3.32   5C DRX DRX parameter O TV 3 parameter 9.9.3.8

[0100] As shown in Table 6 below, a bit for notifying UE radio capability-related information may be added to the UE network capability IE so as to notify that there is capability to transmit the UE radio capability-related information.

[0101] In other words, the UE 101 may transmit the UE radio capability-related information (for example, information for notifying that the UE is capable of providing UE radio capability ID-related information to a network or a UE radio capability ID support indication) by including the same to the TAU request transmitted by the UE 101 to the network.

[0102] Table 6 is an example of notifying that UE radio capability (for example, UE radio capability ID) may be provided in the UE network capability IE.

TABLE-US-00002 TABLE 6 UE Network Capability IE 8 7 6 5 4 3 2 1 UE network capability IEI octet 1  Length of UE network capability contents octet 2  EEA0 128-EEA1 128-EEA2 128-EEA3 EEA4 EEA5 EEA6 EEA7 octet 3  EIA0 128-EIA1 128-EIA2 128-EIA3 EIA4 EIA5 EIA6 EIA7 octet 4  UEA0 UEA1 UEA2 UEA3 UEA4 UEA5 UEA6 UEA7 octet 5* UCS2 UIA1 UIA2 UIA3 UIA4 UIA5 UIA6 UIA7 octet 6* ProSe-dd ProSe H.245-ASH ACC-CSFB LPP LCS 1 × SR VCC NF octet 7* ePCO HC-CP CloT ERw/oPDN S1-U data UP CloT CP CloT Prose-relay ProSe-dc octet 8* 15 bearers SGC N1mode DCNR CP backoff RestrictEC V2X PC5 multipleDRB octet 9* 0 0 0 0 0 0 0 Radio info octet Spare 10*-15*

[0103] Among parameter information of the UE network capability IE, the UE radio information indicates whether a function of providing UE radio information of Table 7, for example, information about the UE radio capability ID, is performed, and accordingly, a value of the UE radio information of Table 7 and interpretation of the value are as below.

TABLE-US-00003 TABLE 7 UE Radio Information IE radio information Bit 0 Radio info not support 1 Radio info suppot

[0104] In operation 521, an MME may transmit a security mode command message to the UE 101.

[0105] In operation 523, the UE 101 may transmit the UE radio capability ID-related information while transmitting a security mode complete message to the MME.

TABLE-US-00004 TABLE 8 Security Mode Complete Message Information Type/ IEI Element Reference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security M V ½ header type header type 9.3.1 Security mode Message type M V  1 complete message 9.8 identity 23 IMEISV Mobile identity O TLV 11 9.9.2.3 79 Replayed Replayed INAS O TLV-E 3-n NAS message message container container 9.9.3.51 UE radio capability info

[0106] UE radio capability information of Table 9 is the UE radio capability information transmitted from the UE 101 to the MME, and may be coded and interpreted as below as the UE radio capability ID-related information.

[0107] In operation 535, the UE 101 may transmit a TAU accept message to the MME while transmitting PLMN assigned UE radio information, UE radio information indication, cause information, and the like.

[0108] The MME may determine whether the MME has UE-related information and whether the information is valid, regarding information transmitted by the UE 101 to the MME.

[0109] When the information is not valid as a result of the determination or when the MME is capable of providing, to the UE, PLMN assigned UE radio-related information (for example, PLMN assigned UE radio ID-related information), the MME may generate new information. As another example, when the information is not valid as the result of the determination or when the MME is capable of generating the PLMN assigned UE radio-related information (for example, the PLMN assigned UE radio ID-related information) or providing, to the UE, the related information that has been stored, the MME may provide the PLMN assigned UE radio-related information (for example, the PLMN assigned UE radio ID-related information) by including the same to the TAU accept message transmitted by the MME to the UE. Information included in the TAU accept message is as Table 10 below.

TABLE-US-00005 TABLE 10 TAU Accept Message Information Type/ IEI Element Reference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security M V ½ header type header type 9.3.1 Tracking area Message type M V 1 update accept 9.8 message identity EPS update EPS update M V ½ result resuit 9.9.3.13 Spare half Spare half M V ½ octet octet 9.9.2.9   5A T3412 value GPRS timer O TV 2 9.9.3.16 50 GUTI EPS mobile O TLV 13  identity 9.9.3.12 54 TAI list Tracking area O TLV 8-98 identity list 9.9.3.33 57 EPS bearer EPS bearer O TLV 4 context status context status 9.9.2.1 13 Location area Location area O TV 6 identification identification 9.9.2.2 23 MS identity Mobile identity O TLV 7-10 9.9.2.3 53 EMM cause EMM cause O TV 2 9.9.3.9 Radio info Radio info Radio info indi Radio info indi

[0110] Also, information about radio information may be coded and interpreted as Tables 11 and 12 below. For example, the radio information may include the PLMN assigned UE radio capability information (for example, the PLMN assigned UE radio capability ID information).

[0111] As another example, the radio information may include the UE radio capability information (for example, the UE radio capability ID information) as in Tables 13 and 14. In other words, the UE radio capability information may be a value transmitted by the UE or a value assigned to the UE while the UE 101 moves from a source network to a target network (for example, a 4G network) via handover or mobility.

[0112] A part of a radio information value of radio-related information included in Table 11 may be coded and interpreted as Table 12 below. In other words, a part of a value of the PLMN assigned UE radio capability of the PLMN assigned UE radio capability IE may be coded and interpreted as Table 12 below.

TABLE-US-00006 TABLE 12 Part of Value of Radio Information, i.e., Part of Value of PLMN Assigned UE Radio Capability IE PLMN assigned UE Radio capability information value (octet 3 to octet n) PLMN assigned UE Radio capability information.

[0113]

[0114] The radio information value of the radio-related information included in Table 13 may be coded and interpreted as Table 14 below.

TABLE-US-00007 TABLE 14 Radio Information Value UE Radio capability information value (octet 3 to octet n) UE Radio capability information.

[0115] Radio information indication may be notified from the MME to the UE 101 via the TAU accept message. The radio information indication according to an embodiment may indicate whether the network is able to support the UE radio capability-related information (for example, the UE radio capability ID-related information) of the UE. Such radio access information indication is coded as Table 15 and interpreted as Table 16 below.

TABLE-US-00008 TABLE 15 Radio Information Indication IE 8 7 6 5 4 3 2 1 radio information indi IEI 0 0 0 Radio octet 1 spare info

TABLE-US-00009 TABLE 16 Value of Radio Information Indication IE and Interpretation of Value radio information indi (octet 1) Bit 1 0 Radio info not support 1 Radio info suppot

[0116] Also, when an error is generated, the generation of error may be notified to the UE 101 through an error code of the TAU accept message. As shown in FIG. 17, the UE 101 may identify a cause of the error through the error code, i.e., an error cause, included in a message transmitted by the MME.

[0117] Also, the MME may delete previous radio access-related information regarding the UE and store updated information.

TABLE-US-00010 TABLE 17 EMM Error Cause Cause value (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 IMSI unknown in HSS 0 0 0 0 0 0 1 1 Illegal UE 0 0 0 0 0 1 0 1 IMEI not accepted 0 0 0 0 0 1 1 0 Illegal ME 0 0 0 0 0 1 1 1 EPS services not allowed 0 0 0 0 1 0 0 0 EPS services and non-EPS services not allowed 0 0 0 0 1 0 0 1 UE identity cannot be derived by the network 0 0 0 0 1 0 1 0 Implicitly detached 0 0 0 0 1 0 1 1 PLMN not allowed 0 0 0 0 1 1 0 0 Tracking Area not allowed 0 0 0 0 1 1 0 1 Roaming not allowed in this tracking area 0 1 1 0 0 0 1 1 Information element non-existent or not implemented 0 1 1 0 0 1 0 0 Conditional IE error 0 1 1 0 0 1 0 1 Message not compatible with the protocol state 0 1 1 0 0 1 1 1 Radio info mismatch 0 1 1 0 1 1 1 1 Protocol error, unspecified

[0118] FIG. 6 is a diagram for describing an NAS message information processing and communicating method in a 5G network environment, according to an embodiment of the disclosure.

[0119] In operation 601, the UE 101 may perform communication with an AMF and the SMF in a 5G network.

[0120] In operation 611, the UE 101 may perform a TAU request by moving from the 5G network to a 4G network. Here, the UE may transmit a TAU request message to the MME while notifying the network of whether the UE supports UE radio information by setting of a bit value in a UE network capability IE.

[0121] The UE 101 may transmit radio access-related information by using the UE network capability IE included in the TAU request message, as in Table 18 below.

TABLE-US-00011 TABLE 18 TAU Request Message Information Type/ IEI Element Rreference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security M V ½ header type header type 9.3.1 Tracking area Message type M V 1 update 9.8 request message identity EPS update EPS update M V ½ type type 9.9.3.14 NAS key set NAS key set M V ½ identifier identifier 9.9.3.21 Old GUTI EPS mobile M LV 12  identity 9.9.3.12 B- Non-current NAS key set O TV 1 native NAS identifier key set 9.9.3.21 identifier   8- GPRS Ciphering key O TV 1 ciphering key sequence sequence number number 9.9.3.4a 19 Old P-TMSI P-TMSI O TV 4 signature signature 9.9.3.26 50 Additional EPS mobile O TLV 13  GUTI identity 9.9.3.12 55 Nonce.sub.UE Nonce O TV 5 9.9.3.25 58 UE network UE network O TLV 4-15 capability capability 9.9.3.34 52 Last visited Tracking area O TV 6 registered identity TAI 9.9.3.32   5C DRX DRX parameter O TV 3 parameter 9.9.3.8

[0122] As in Table 19 below, a bit for notifying UE radio capability-related information may be added to the UE network capability IE so as to notify that there is capability to transmit the UE radio capability-related information through the UE network capability IE.

[0123] In other words, the UE may transmit the UE radio capability-related information (for example, information for notifying that the UE is capable of providing UE radio capability ID-related information to the network or a UE radio capability ID support indication) by including the same to the TAU request transmitted by the UE to the network.

[0124] Table 19 shows an example of the UE network capability IE providing UE radio capability (for example, UE radio capability ID).

TABLE-US-00012 TABLE 19 UE Network Capability IEI 8 7 6 5 4 3 2 1 UE network capability IEI octet 1  Length of UE network capability contents octet 2  EEA0 128-EEA1 128-EEA2 128-EEA3 EEA4 EEA5 EEA6 EEA7 octet 3  EIA0 128-EIA1 128-EIA2 128-EIA3 EIA4 EIA5 EIA6 EIA7 octet 4  UEA0 UEA1 UEA2 UEA3 UEA4 UEA5 UEA6 UEA7 octet 5  UCS2 UIA1 UIA2 UIA3 UIA4 UIA5 UIA6 UIA7 octet 6  ProSe-dd ProSe H.245-ASH ACC-CSFB LPP LCS 1 × SR VCC NF octet 7* ePCO HC-CP CloT ERw/oPDN S1-U data UP CloT CP CloT Prose-relay ProSe-dc octet 8* 15 bearers SGC N1mode DCNR CP backoff RestrictEC V2X PC5 multipleDRB octet 9* 0 0 0 0 0 0 0 Radio info octet Spare 10*-15*

[0125] The UE radio information in the UE network capability IE may be coded and interpreted as Table 20 below.

TABLE-US-00013 TABLE 20 UE Radio Information of UE Network Capability IE (Value thereof and Interpretation of the Value) radio information Bit 0 Radio info not support 1 Radio info suppot

[0126] In operation 621, the MME may transmit a security mode command message to the UE 101.

[0127] In operation 623, the UE 101 may transmit, to the MME, a security mode complete message including the UE radio capability ID-related information.

TABLE-US-00014 TABLE 21 Security Mode Complete Message Information Type/ IEI Element Reference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security M V ½ header type header type 9.3.1 Security mode Message type M V 1 complete message 9.8 identity 23 IMEISV Mobile identity O TLV 11  9.9.2.3 79 Replayed NAS Replayed NAS O TLV-E 3-n message message container container 9.9.3.51 UE radio capability info

[0128] Meanwhile, Table 22 relates to information related to the UE radio capability information transmitted through the security mode complete message. This is the UE radio capability information transmitted from the UE 101 to the MME, and for example, may include UE radio capability ID-related information.

[0129] In operation 635, the MME may transmit a TAU accept message to the UE 101 while transmitting PLMN assigned UE radio information, UE radio information indication, cause information, and the like.

[0130] The MME determines whether the MME has UE-related information and whether the information is valid, regarding information transmitted by the UE 101 to the MME. When the information is not valid as a result of the determination or when the MME is capable of providing, to the UE, PLMN assigned UE radio-related information (for example, PLMN assigned UE radio ID-related information), the MME may generate new information. As another example, when the information is not valid as the result of the determination or when the MME is capable of providing, to the UE, the PLMN assigned UE radio-related information (for example, the PLMN assigned UE radio ID-related information), the MME may transmit the PLMN assigned UE radio-related information (for example, the PLMN assigned UE radio ID-related information) by including the same to the TAU accept message transmitted by the MME to the UE 101, as in Table 23 below.

TABLE-US-00015 TABLE 23 TAU Accept Message Information Type/ IEI Element Reference Presence Format Length Protocol Protocol M V ½ discriminator discriminator 9.2 Security Security header M V ½ header type type 9.3.1 Tracking area Message type M V 1 update accept 9.8 message identity EPS update EPS update M V ½ result result 9.9.3.13 Spare half Spare half M V ½ octet octet 9.9.2.9   5A T3412 value GPRS timer O TV 2 9.9.3.16 50 GUTI EPS mobile O TLV 13  identity 9.9.3.12 54 TAI list Tracking area O TLV 8-98 identity list 9.9.3.33 57 EPS bearer EPS bearer O TLV 4 context status context status 9.9.2.1 13 Location area Location area O TV 6 identification identification 9.9.2.2 23 MS identity Mobile identity O TLV 7-10 9.9.2.3 53 EMM cause EMM cause O TV 2 9.9.3.9 UE radio info UE Radio info Radio info indi Radio info indi

[0131] Also, information about UE radio information may be coded and interpreted as Table 24 below. An example of such radio information may include UE radio capability information (for example, UE radio capability ID information).

[0132] A UE radio capability information value of radio-related information may be coded and interpreted as below.

TABLE-US-00016 TABLE 25 UE Radio Capability Information Value UE Radio capability information value (octet 3 to octet n) UE Radio capability information.

[0133] The MME may notify the UE of radio information indication via the TAU accept message. Such radio information indication may indicate whether the network is able to support the UE radio capability-related information (for example, the UE radio capability ID-related information) of the UE.

[0134] Such radio access information indication may be coded as Table 26 and interpreted as Table 27 below.

TABLE-US-00017 TABLE 26 Radio Information Indication IE 8 7 6 5 4 3 2 1 radio information indi IEI 0 0 0 Radio info octet 1 spare

TABLE-US-00018 TABLE 27 Value of Radio Information Indication IE and Interpretation of Value radio information indi (octet 1) Bit 1 0 Radio info not support 1 Radio info suppot

[0135] Also, when an error is generated, the MME may notify the UE 101 of the generation of error through an error code of the TAU accept message. Also, the MME may delete previous radio access-related information regarding the UE and store updated information.

TABLE-US-00019 TABLE 28 EMM Error Cause Cause value (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 IMSI unknown in HSS 0 0 0 0 0 0 1 1 Illegal UE 0 0 0 0 0 1 0 1 IMEI not accepted 0 0 0 0 0 1 1 0 Illegal ME 0 0 0 0 0 1 1 1 EPS services not allowed 0 0 0 0 1 0 0 0 EPS services and non-EPS services not allowed 0 0 0 0 1 0 0 1 UE identity cannot be derived by the network 0 0 0 0 1 0 1 0 Implicitly detached 0 0 0 0 1 0 1 1 PLMN not allowed 0 0 0 0 1 1 0 0 Tracking Area not allowed 0 0 0 0 1 1 0 1 Roaming not allowed in this tracking area 0 1 1 0 0 0 1 1 Information element non-existent or not implemented 0 1 1 0 0 1 0 0 Conditional IE error 0 1 1 0 0 1 0 1 Message not compatible with the protocol state 0 1 1 0 0 1 1 1 Radio info mismatch 0 1 1 0 1 1 1 1 Protocol error, unspecified

[0136] FIG. 7 is a block diagram of a structure of a UE 700, according to an embodiment.

[0137] Referring to FIG. 7, the UE 700 may include a transceiver 710, a processor 720, and a memory 730. The transceiver 710, the processor 720, and the memory 730 may operate according to a communication method of a UE described above. However, the components of the UE 700 are not limited thereto. For example, the UE 700 may include fewer or more components (for example, a network interface controller (NIC)) than those described above. In addition, the transceiver 710, the processor 720, and the memory 730 may be implemented as a single chip.

[0138] The transceiver 710 may transmit or receive a signal to or from a network entity (for example, an MME). Here, the signal may include at least one message described above with reference to FIGS. 1 through 6. In this regard, the transceiver may include a radio frequency (RF) transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver and components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0139] Also, the transceiver may receive and output, to the processor 720, a signal through a wireless channel, and transmit a signal output from the processor 720 through the wireless channel.

[0140] The processor 720 is hardware for driving software for processing radio access information regarding the UE 700 while the UE 700 performs handover, and for example, one or more central processing units (CPUs) may be included in the processor 720. The processor 720 may drive software stored in the memory 730, and at this time, the software may include a radio access information management module and a handover module including one or more instructions. The handover module may process handover-related data generated while the UE moves to a different network. Also, the radio access information management module may process UE information, such as capability information of the UE, or network status information, such as an error cause or the like. The handover module and the radio access information management module may be manufactured as separate chips distinguished from the processor 720.

[0141] The memory 730 may store software and data required for operations of the UE 700. Also, the memory 730 may store control information or data included in a signal obtained by the UE. The memory may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0142] FIG. 8 is a block diagram of a structure of a network entity 800, according to an embodiment.

[0143] Referring to FIG. 8, the network entity 800 may include a transceiver 810, a processor 820, and a memory 830. The network entity 800 may be any one of the MME, the AMF, the eNB, and the 5G RAN described above with reference to FIGS. 1 through 6. The transceiver 810, the processor 820, and the memory 830 may operate according to a communication method of any one of the MME, the AMF, the eNB, and the 5G RAN described above. However, the components of the network entity 800 are not limited thereto. For example, the network entity 800 may include fewer or more components (for example, an NIC) than those described above. In addition, the transceiver 810, the processor 820, and the memory 830 may be implemented as a single chip.

[0144] The transceiver 810 may transmit or receive a signal to or from another network entity or a UE. Here, the signal may include at least one message described above with reference to FIGS. 1 through 6. In this regard, the transceiver may include an RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver and components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0145] Also, the transceiver may receive and output, to the processor 820, a signal through a wireless channel, and transmit a signal output from the processor 820 through the wireless channel.

[0146] The processor 820 is hardware for driving software for processing radio access information regarding a UE while the UE performs handover, and for example, one or more CPUs may be included in the processor 820. The processor 820 may drive software stored in the memory 830, and at this time, the software may include a radio access information management module and a handover module including one or more instructions. The handover module may process handover-related data generated while the UE moves to a different network. Also, the radio access information management module may process network status information, such as an error cause or the like, or capability information of the UE. The handover module and the radio access information management module may be manufactured as separate chips distinguished from the processor 820.

[0147] The memory 830 may store software and data required for operations of the network entity 800. Also, the memory 830 may store control information or data included in a signal obtained from the UE. The memory 830 may be a storage medium, such as ROM, RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0148] A UE may move from an LTE network, i.e., an MME, which does not support UE radio information, i.e., UE radio capability ID-related function, to an AMF of a network in which the UE supports UE radio information, i.e., UE radio capability ID, of 5G.

[0149] When a UE moves from a network that does not support UE radio information to a network that supports UE radio information, i.e., UE radio capability ID, as shown in FIG. 9, following operations of FIG. 10 may be possible.

[0150] In other words, despite that the UE supports a function of providing information about the UE radio capability ID, the LTE network to which the UE has previously accessed does not support such a function, and thus the UE needs to move to a 5G network providing the function and use the function by activating the function again.

[0151] In operation 1001, the UE has moved from an LTE MME network to a network including the AMF 111, in a handover or idle mode state.

[0152] In operation 1003, radio capability-related information of the UE is transmitted via context transfer from a source MME to the target AMF 111. Because the MME does not support the UE radio capability ID, the radio capability-related information of the UE is transmitted from the MME to the AMF 111 in full information. In other words, such information is radio access-related parameters. The information may be transmitted from the source MME to the target AMF upon a request from the target AMF to the source MME. Also, according to an embodiment, the source MME may perform the context transfer to the target AMF.

[0153] As such, the target AMF 111 has received, from the source MME, full radio capability regarding the UE.

[0154] In operation 1011, the UE transmits a registration request to the target AMF 111. Here, despite that the UE is able to provide the UE radio information, for example, the UE radio capability ID, the UE does not provide such information. This is because, despite that the UE has moved from the network including the MME incapable of providing the UE radio capability ID to the AMF 111 capable of providing the UE radio capability ID, the UE does not have information thereof.

[0155] Alternatively, it is unable to verify whether a radio access capability ID provided by the UE and a radio access capability ID included in the network match each other.

[0156] In operation 2021, the AMF transmits, to the UE, an ID request message with a PEI as an ID.

[0157] In operation 1023, the UE transmits an ID response message to the AMF while notifying the AMF of tracking area code (TAC) information required for a radio access capability operation. Alternatively, the UE may transmit the ID response message to the AMF while transmitting UE radio information or UE radio capability ID.

[0158] In operation 1031, the AMF 111 transmits a registration access message to the UE 101.

[0159] In operation 1041, the UE transmits a registration complete message to the AMF.

[0160] In operation 1051, the AMF transmits a configuration update command message to the UE. Here, the AMF may assign a PLMN assigned UE radio capability ID to the UE.

[0161] In operation 1053, the UE transmits a configuration update complete message to the AMF.

[0162] An embodiment is possible via various methods.

[0163] Embodiment 1) A method of providing the UE radio capability ID together when the UE transmits the registration request of operation 1003 to the target AMF 111.

[0164] Procedures for such a method are as follows.

[0165] Method 1-1) When the UE transmits the registration request to the AMF, a manufacturer ID assigned by a manufacturer of the UE when the UE radio capability ID included in the UE is provided is provided as a UE radio capability ID. Method 1-2) Another method is about providing the PLMN assigned UE radio capability ID to the AMF, in a case where there is the PLMN assigned UE radio capability ID assigned from the network when the UE is to provide the UE radio capability ID in the UE and the UE is to transmit the registration request to the AMF, as the UE has accessed the network and the PLMN.

[0166] Embodiment 2) A method of providing, by the UE, the UE radio capability ID to the AMF as the AMF requests the UE to provide the UE radio capability ID.

[0167] Procedures for such a method are as follows.

[0168] The procedures are related to a case where there is no full UE radio capability received by the AMF via the context transfer in operation 1003 or no UE radio capability ID provided by the UE to the AMF in operation 1011, or where the UE radio capability-related information does not match according to verification by the AMF.

[0169] Method 2-1) The AMF requests the UE to provide the UE radio information or UE radio capability ID, and receives a response thereto.

[0170] In this regard, the AMF may perform operation 1031 by transmitting the registration access message while transmitting indication of requesting the UE radio information, i.e., the UE radio capability ID.

[0171] Alternatively, the AMF may perform operation 1031 by transmitting the registration access message while notifying that the UE radio information, i.e., the UE radio capability ID, does not match, and for example, notify an error cause that the UE radio capability ID does not match.

[0172] Also, the AMF may configure and transmit PLMN assigned UE radio information, i.e., the PLMN assigned UE radio capability ID.

[0173] Method 2-2) The AMF requests the UE to provide the UE radio information or UE radio capability ID, and receives the response thereto.

[0174] The AMF may perform operation 1031 by transmitting the registration access message while transmitting indication of requesting the UE radio information, i.e., the UE radio capability ID.

[0175] Alternatively, the AMF may perform operation 1031 by transmitting the registration access message while notifying, via indication, that the UE radio information, i.e., the UE radio capability ID, does not match or that the UE radio information, i.e., the UE radio capability ID, is required.

[0176] Then, upon receiving the response, the AMF may configure and transmit the PLMN assigned UE radio information, i.e., the PLMN assigned UE radio capability ID.

[0177] Method 2-3) The AMF requests the UE to provide the UE radio information or UE radio capability ID, and receives the response thereto.

[0178] In this regard, the AMF needs to perform following operations before transmitting the registration access message in operation 1031.

[0179] In operation 2021, the AMF transmits, to the UE, the ID request message with the PEI as the ID.

[0180] In operation 1023, the UE transmits the ID response message to the AMF while notifying the AMF of TAC information required for the radio access capability operation. Alternatively, the UE may transmit the ID response message to the AMF while transmitting the UE radio information or UE radio capability ID.

[0181] Embodiment 3) A method of providing, by the AM, the radio capability ID to the UE.

[0182] Procedures for such a method are as follows.

[0183] The UE transmits the registration request to the AMF in operation 1011. Here, the UE may also transmit the UE radio capability ID. The UE radio capability ID may be the PLMN assigned radio capability ID received by the UE from the network, or a manufacturer UE radio capability ID assigned by the manufacturer. Alternatively, because the UE has moved from the MME that does not support the corresponding function, the UE may not provide the UE radio capability ID to the AMF 111 despite that the UE has a function of providing the radio information, such as the UE radio capability ID.

[0184] Method 3-1) There is the UE radio capability ID received from the UE and the UE radio capability ID is the same as full UE radio capability information.

[0185] Method 3-1-1)

[0186] In operation 1031, in a case where the AMF 111 has received the full UE radio capability information regarding the UE from the MME in operation 1003, i.e., via the context transfer, when there is the UE radio capability ID received from the UE through the registration request in operation 1011,

[0187] the AMF 111 may compare information regarding the UE radio capability ID, i.e., the UE radio capability-related information regarding the UE, with the full radio capability information received from the MME via the context transfer, and when they are the same, store the UE radio capability ID received from the UE, and use the UE radio capability ID afterwards.

[0188] Alternatively, according to an embodiment,

[0189] Method 3-1-2)

[0190] In operation 1031, in a case where the AMF 111 has received the full UE radio capability information regarding the UE from the MME in operation 1003, i.e., via the context transfer, when there is the UE radio capability ID received from the UE through the registration request in operation 1011,

[0191] the AMF 111 may compare information regarding the UE radio capability ID, i.e., the UE radio capability-related information regarding the UE, with the full radio capability information received from the MME via the context transfer, and when they are the same, store the UE radio capability ID received from the UE, use the UE radio capability ID afterwards, and transmit the PLMN assigned UE radio capability ID assigned by the AMF to the UE.

[0192] Method 3-2) There is no UE radio capability ID but is the same as the full radio capability information based on comparison.

[0193] In operation 1031,

[0194] when the AMF 111 has received the full UE radio capability information regarding the UE from the MME in operation 1003, i.e., via the context transfer, the UE has accessed the AMF 111 before and thus the AMF 111 has information regarding the UE (for example, an ID of 5G-GUTI regarding the UE) or information regarding the UE radio capability ID,

[0195] there is no UE radio capability ID received from the UE via the registration request in operation 1011, and

[0196] the full radio capability information received from the MME via the context transfer and the radio capability-related information of the UE are the same information based on comparison,

[0197] Method 3-2-1) the AMF notifies the UE of the UE radio capability ID stored in the AMF in operation 1031.

[0198] Alternatively,

[0199] Method 3-2-2) In operation 1031, the AMF may synchronize pieces of information the UE and the network have by assigning the PLMN assigned UE radio capability ID newly assigned by the AMF to the UE and transmitting the same.

[0200] Method 3-3) There is no UE radio capability ID or even when there is the UE radio capability ID, the UE radio capability ID is different from the full radio capability information based on comparison.

[0201] Method 3-3-1) when the full radio capability information received from the MME via the context transfer and the radio capability-related information of the UE are different information based on comparison,

[0202] the AMF generates the PLMN assigned UE radio capability ID and notifies the same to the UE, in operation 1031. According to an embodiment, upon receiving the registration complete message from the UE as a response, the AMF stores the PLMN assigned UE radio information, i.e., the PLMN assigned UE radio capability ID information.

[0203] Method 3-3-2) In operation 1031, when the UE has accessed the AMF and thus the AMF has the information regarding the UE, but the there is no UE radio information received from the UE, which corresponds to the full UE radio capability received from the source MME by the AMF, for example, there is no UE radio capability ID information or UE radio information corresponding to the full UE radio capability received from the source MME by the AMF,

[0204] the AMF may transmit the PLMN assigned UE radio capability ID corresponding to the UE, in operation 1031. Method 4) A configuration update command is used.

[0205] While transmitting the configuration update command from the AMF to the UE, the PLMN assigned UE radio capability ID and PLMN assigned UE radio capability ID deletion indication are configured and transmitted.

[0206] Upon receiving the same, the UE deletes the UE radio capability ID for a corresponding PLMN, i.e., the previously assigned PLMN assigned UE radio capability ID, and transmits the configuration update complete message to the AMF.

[0207] In other words, operations are performed as follows.

[0208] In operation 1031,

[0209] when the AMF 111 has received the full UE radio capability information regarding the UE from the MME in operation 1003, i.e., via the context transfer, the UE has accessed the AMF 111 before and thus the AMF 111 has the information regarding the UE (for example, the ID of 5G-GUTI regarding the UE) or information regarding the UE radio capability ID,

[0210] there is no UE radio capability ID received from the UE via the registration request in operation 1011, and

[0211] the full radio capability information received from the MME via the context transfer and the radio capability-related information of the UE are the same information based on comparison,

[0212] the AMF 111 transmits the registration access message to the UE 101-1 as in operation 1031.

[0213] As in operation 1041, the UE transmits the registration complete message to the AMF.

[0214] As in operation 1051, the AMF transmits the configuration update command message to the UE. Here, the AMF may assign the PLMN assigned UE radio capability ID to the UE.

[0215] As in operation 1053, the UE transmits the configuration update complete message to the AMF.

[0216] According to an embodiment, provided is a method by which a UE performs communication in a wireless communication system, including: transmitting, by the UE, a TAU request message including UE capability information to a target network entity that is a handover target; receiving, from the target network entity, a request message regarding a UE capability ID; transmitting information about the UE capability ID to the target network entity; and receiving a TAU complete message from the target network entity as radio access information regarding the UE is updated in the target network entity, based on the UE capability ID.

[0217] FIG. 11 is a flowchart for describing an operation method of a UE, according to an embodiment of the disclosure.

[0218] In operation 1102, the UE may transmit, to a core entity, a TAU request message including UE radio capability information associated with a UE radio capability ID. The core entity may include an MME, and the MME may include an entity that is a handover target. For example, when the UE is handed over from a 5G network to a 4G network, the UE may transmit, to the MME, the TAU request message including the UE radio capability information.

[0219] In detail, the UE radio capability information may include bit information indicating that the UE is capable of providing the UE radio capability ID. For example, when the bit information has a value of 1, the UE radio capability information may indicate that the UE is capable of providing the radio capability ID. When the bit information has a value of 0, the UE radio capability information may indicate that the UE is incapable of providing the radio capability ID. While being handed over to the 4G network, the UE may transmit the TAU request message including information indicating that the UE is capable of providing the radio capability ID to the MME.

[0220] In operation 1104, the UE may receive, from the core entity, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information. The core entity may request the UE for the UE radio capability ID information, based on the UE radio capability information included in the TAU request message. In detail, the core entity may request the UE for the UE radio capability ID information when the UE radio capability information indicates that the UE is capable of providing the radio capability ID information, based on the bit information included in the UE radio capability information.

[0221] Also, the UE may receive, from the core entity, a security mode message based on information for a UE radio capability ID available in the core entity. In detail, the core entity may request the UE for the UE radio capability ID information when the information regarding the radio capability ID available in the core entity indicates that there is no radio capability ID available in the core entity.

[0222] According to an embodiment, the UE may receive the security mode message from the core entity when the UE is capable of providing the radio capability ID information and there is no radio capability ID available in the core entity.

[0223] In operation 1106, the UE may transmit, to the core entity, a security mode complete message including the UE radio capability ID information, in response to the security mode command message. Then, the UE may receive a TAU complete message from the core entity.

[0224] FIG. 12 is a diagram for describing an operation method of a core entity, according to an embodiment of the disclosure.

[0225] In operation 1202, the core entity may receive, from a UE, a TAU request message including UE radio capability information associated with a UE radio capability ID. The core entity may include an MME, and the MME may include an entity that is a handover target. For example, when the UE is handed over from a 5G network to a 4G network, the MME may receive, from the UE, the TAU request message including the UE radio capability information.

[0226] In detail, the UE radio capability information may include bit information indicating that the UE is capable of providing the UE radio capability ID. For example, when the bit information has a value of 1, the UE radio capability information may indicate that the UE is capable of providing the radio capability ID. When the bit information has a value of 0, the UE radio capability information may indicate that the UE is incapable of providing the radio capability ID. While the UE is handed over to the 4G network, the MME may receive, from the UE, the TAU request message including information indicating that the UE is capable of providing the radio capability ID to the MME.

[0227] In operation 1204, the core entity may transmit, to the UE, a security mode command message for requesting UE radio capability ID information, based on the UE radio capability information. The core entity may request the UE for the UE radio capability ID information, based on the UE radio capability information included in the TAU request message. In detail, the core entity may request the UE for the UE radio capability ID information when the UE radio capability information indicates that the UE is capable of providing the radio capability ID information, based on the bit information included in the UE radio capability information.

[0228] Also, the core entity may transmit, to the UE, a security mode message based on information for a UE radio capability ID available in the core entity. In detail, the core entity may request the UE for the UE radio capability ID information when the information regarding the radio capability ID available in the core entity indicates that there is no radio capability ID available in the core entity.

[0229] According to an embodiment, the core entity may transmit the security mode message to the UE when the UE is capable of providing the radio capability ID information and there is no radio capability ID available in the core entity.

[0230] In operation 1206, the core entity may receive, from the UE, a security mode complete message including the UE radio capability ID information. Then, the core entity may transmit a TAU complete message to the UE.

[0231] According to an embodiment of the disclosure, a UE in a wireless communication system includes: a transceiver; and at least one processor configured to: transmit, to a core entity via the transceiver, a TAU request message including UE radio capability information associated with a UE radio capability ID; receive, from the core entity via the transceiver, a security mode command message based on the UE radio capability information; and transmit, to the core entity via the transceiver, a security mode complete message including the UE radio capability ID information.

[0232] According to an embodiment, the at least one processor may be further configured to receive, from the core entity via the transceiver, the security mode command message, based on information for a UE radio capability ID available in the core entity.

[0233] According to an embodiment, the UE radio capability information may include bit information indicating that the UE supports the UE radio capability ID.

[0234] According to an embodiment, the information for the UE radio capability ID available in the core entity may indicate that the UE radio capability ID available in the core entity does not exist.

[0235] According to an embodiment, the core entity may include an MME, wherein the MME may include an entity that is a handover target.

[0236] According to an embodiment of the disclosure, a core entity in a wireless communication system includes: a transceiver; and at least one processor configured to: receive, from a UE through the transceiver, a TAU request message including UE radio capability information associated with a UE radio capability ID; transmit, to the UE through the transceiver, a security mode command message based on the UE radio capability information; and receive, from the UE through the transceiver, a security mode complete message including the UE radio capability ID information. According to specific embodiments of the disclosure, components included in the disclosure are described in the singular or plural forms according to proposed specific embodiments. However, the singular or plural form is appropriately selected for convenience of explanation and the disclosure is not limited thereto. As such, an element expressed in a plural form may also be configured as a single element, and an element expressed in a singular form may also be configured as plural elements.

[0237] Meanwhile, specific embodiments have been described in the detailed description of the disclosure, but various modifications may be possible without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be limited to the embodiments described above, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.