User equipment, operation method thereof and semiconductor chipset

Abstract

The invention relates to user equipment, an operation method thereof and a semiconductor chip set. According to one embodiment of the present specification, an operation method of a user device is provided. The method may comprise: a step of transmitting a tracking area update request message; and a step of receiving a response message. If the response message is a tracking area update accept message and the message includes radio access technology utilization control information, the RAT utilization control information may be directed at the current public land mobile network and its equivalent PLMN. The method can also comprise the following step: if the tracking area update request message contains information about RAT utilization control support, the response message is a tracking area update acceptance message, and the acceptance message does not contain RAT utilization control information, deleting the stored RAT utilization control information.

Description

Technical Field

[0001] This specification relates to a 3GPP wireless communication system. Background Art

[0002] In 3GPP, which establishes technical standards for mobile communication systems, in order to deal with fourth-generation communications and several related forums and new technologies, research on Long Term Evolution / System Architecture Evolution (LTE / SAE) technology has been started since late 2004 as part of efforts to optimize and improve the performance of 3GPP technologies.

[0003] SAE, already being implemented by 3GPP SA WG2, is a study related to network technologies aimed at determining network structures and supporting mobility between heterogeneous networks consistent with the LTE mission of 3GPP STRAN, and is one of the most important recent standardization issues of 3GPP. SAE is a mission to evolve the 3GPP system into one that supports various IP-based radio access technologies, and is being implemented with the goal of developing an optimized packet-based system that minimizes transmission delay while improving data transmission capabilities.

[0004] The Evolved Packet System (EPS) higher layer reference model defined in 3GPP SA WG2 includes non-roaming cases and roaming cases with various scenarios, and for details thereof, reference can be made to 3GPP standard documents TS23.401 and TS23.402. The EPS higher layer reference model has been briefly reconfigured. Figure 1 network configuration.

[0005] Figure 1 Shown is the configuration of an evolved mobile communication network.

[0006] The Evolved Packet Core (EPC) may include various elements. Figure 1 A serving gateway (S-GW) 52, a packet data network gateway (PDN GW) 53, a mobility management entity (MME) 51, a serving general packet radio service (GPRS) support node (SGSN), and an enhanced packet data gateway (ePDG) corresponding to some of the various elements are illustrated.

[0007] The S-GW 52 is an element operating at the boundary point between the radio access network (RAN) and the core network, and has the function of maintaining a data path between the eNodeB 22 and the PDN GW 53. In addition, if a terminal (or user equipment (UE)) moves within the area served by the eNodeB 22, the S-GW 52 functions as a local mobility anchor point. That is, for mobility within the E-UTRAN (i.e., the Universal Mobile Telecommunications System (Evolved UMTS) Terrestrial Radio Access Network defined after 3GPP Release 8), data packets can be routed through the S-GW 52. In addition, the S-GW 52 can also function as a mobility anchor point in the case of another 3GPP network (i.e., a RAN defined before 3GPP Release 8, such as the UTRAN or the Global System for Mobile Communications (GSM) (GERAN) / Enhanced Data Rates for Global Evolution (EDGE) radio access network).

[0008] The PDN GW (or P-GW) 53 corresponds to the termination point of the data interface towards the packet data network. The PDN GW 53 can support policy enforcement features, packet filtering, charging support, etc. In addition, the PDN GW (or P-GW) 53 can serve as an anchor point for mobility management in both 3GPP networks and non-3GPP networks (e.g., unreliable networks such as Interworking Wireless Local Area Network (I-WLAN), Code Division Multiple Access (CDMA) networks, or reliable networks such as WiMax).

[0009] exist Figure 1 In the network configuration of FIG, the S-GW 52 and the PDN GW 53 have been illustrated as independent gateways, but both gateways may be implemented according to a single gateway configuration option.

[0010] The MME 51 is an element that performs signaling and control functions for connecting terminals to the network and for supporting network resource allocation, tracking, paging, roaming, handover, and the like. The MME 51 controls control plane functions related to subscriber and session management. The MME 51 manages many eNodeBs 22 and performs conventional signaling for selecting a gateway for handover to another 2G / 3G network. Furthermore, the MME 51 performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.

[0011] The SGSN handles all packet data such as mobility management and authentication for users accessing different 3GPP networks (eg, GPRS networks and UTRAN / GERAN).

[0012] The ePDG acts as a security node for unreliable non-3GPP networks (eg, I-WLAN and Wi-Fi hotspots).

[0013] As reference Figure 1 As described, a terminal (or UE) with IP capabilities can access an IP service network (eg, IMS) provided by a service provider (eg, operator) via various elements within the EPC based on non-3GPP access and 3GPP access.

[0014] also, Figure 1 Various reference points (e.g., S1-U and S1-MME) are shown. In 3GPP systems, a conceptual link connecting two functions present in different functional entities of E-UTRAN and EPC is called a reference point. Table 1 below defines Figure 1 In addition to the reference points shown in the example of Table 1, various reference points may exist depending on the network configuration.

[0015] [Table 1]

[0016]

[0017] exist Figure 1 Among the reference points shown, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides user plane control and mobility support between the PDN GW and the trusted non-3GPP access. S2b is a reference point that provides user plane mobility support and control between the PDN GW and the ePDG. Summary of the Invention

[0018] The disclosure of this specification aims to provide a method and user equipment for deleting RAT (Radio Access Technology) utilization control information.

[0019] According to one embodiment of the present specification, a method for operating a user equipment (UE) is provided, which may include: sending a tracking area update request message; and receiving a response message.

[0020] When the response message is a tracking area update accept message and the message includes radio access technology (RAT) utilization control information, the RAT utilization control information may be applicable to the current public land mobile network (PLMN) and its equivalent PLMN.

[0021] If the tracking area update request message includes information about support of a RAT utilization control, and the response message is a tracking area update accept message, but the message does not include RAT utilization control information, the method may further include a step of deleting the stored RAT utilization control information.

[0022] According to one embodiment of the present specification, a user equipment (UE) is further provided. The UE may include: a transceiver; and a processor for controlling the transceiver and performing operations. The operations performed by the processor may include:

[0023] Send a tracking area update request message;

[0024] Receive response message;

[0025] If the response message is a Tracking Area Update Accept message and the message contains RAT Utilization Control Information, the information applies to the current PLMN and its equivalent PLMNs;

[0026] If the tracking area update request message includes information about RAT utilization control support, and the response message is a tracking area update accept message, and the message does not include RAT utilization control information, the stored RAT utilization control information is deleted.

[0027] According to one embodiment of this specification, a chipset for the UE is also provided. The chipset may include:

[0028] at least one processor; and

[0029] At least one memory operatively connected to the processor and configured to store instructions.

[0030] When the instructions are executed by the processor, the chipset may perform the following operations:

[0031] Send a tracking area update request message;

[0032] Receive response message;

[0033] If the response message is a Tracking Area Update Accept message and the message contains RAT Utilization Control Information, the information applies to the current PLMN and its equivalent PLMNs;

[0034] If the tracking area update request message includes information about RAT utilization control support, and the response message is a tracking area update accept message, but the message does not include RAT utilization control information, the stored RAT utilization control information is deleted.

[0035] According to one embodiment of the present specification, a non-volatile computer-readable storage medium having recorded thereon instructions is also provided. The instructions can be executed by one or more processors installed in a device, causing the processors to perform the following operations:

[0036] Send a tracking area update request message;

[0037] Receive response message;

[0038] If the response message is a Tracking Area Update Accept message and contains RAT Utilization Control Information, the information applies to the current PLMN and its equivalent PLMNs;

[0039] If the tracking area update request message includes information about RAT utilization control support, and the response message is a tracking area update accept message, but the message does not include RAT utilization control information, the stored RAT utilization control information is deleted.

[0040] The method or operation may further comprise the following steps:

[0041] If the tracking area update accept message includes RAT utilization control information, the information is stored together with the PLMN identity of the current PLMN in a list of PLMNs with associated RAT restrictions.

[0042] If the UE is switched off, the method or operation may further include: retaining the stored PLMN list so that it can be continued to be used after the device is switched on.

[0043] If the USIM (Universal Subscriber Identity Module) in the UE is removed, the stored PLMN list may be deleted.

[0044] The response message is a tracking area update reject message, and the tracking area update reject message includes RAT utilization control information. If the message successfully passes the integrity check, the information can be stored together with the identifier of the current PLMN in the PLMN list associated with the RAT restriction.

[0045] The method or operation may further include replacing previously stored RAT utilization control information associated with the current PLMN with the new RAT utilization control information.

[0046] If the response message is a tracking area update reject message, the message may further include information indicating that there are no suitable cells available in the tracking area.

[0047] According to the disclosure of this specification, the UE can delete the RAT utilization control information. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 It is a structural diagram demonstrating the structure of an evolutionary mobile communication network.

[0049] Figure 2 FIG2 is a schematic diagram schematically showing the functions of main nodes of a general E-UTRAN and a typical EPC.

[0050] Figure 3 It is a schematic diagram showing the structure of the radio interface protocol (Radio Interface Protocol) in the control plane between the UE and the eNodeB.

[0051] Figure 4 is another schematic diagram showing the radio interface protocol structure in the user plane between a terminal and a base station.

[0052] Figure 5 is a flowchart showing a random access procedure in 3GPP LTE.

[0053] Figure 6 This is a diagram showing the connection process in the radio resource control (RRC) layer.

[0054] Figure 7 It is a schematic diagram showing the TAU (Tracking Area Update) procedure.

[0055] Figure 8 is a schematic flow chart showing a process according to an embodiment of the present specification.

[0056] Figure 9 is a block diagram showing a terminal structure according to an embodiment of this specification.

[0057] Figure 10 This is a block diagram showing the structure of a processor that implements the contents disclosed in this specification. DETAILED DESCRIPTION

[0058] The present invention is described with reference to UMTS (Universal Mobile Telecommunications System) and EPC (Evolved Packet Core), but is not limited to these communication systems, but rather is applicable to all communication systems and methods to which the technical spirit of the present invention can be applied.

[0059] The technical terms used herein are used to only describe specific embodiments, and should not be construed as limiting the present invention. In addition, unless defined otherwise, the technical terms used herein should be construed as having the implication commonly understood by those skilled in the art, and should not be interpreted too wide or too narrow. In addition, the technical terms used herein, that are determined to not correctly represent the spirit of the present invention should be replaced or understood by such technical terms as can be correctly understood by those skilled in the art. In addition, the general terms used herein should be interpreted in the context as defined in the dictionary, and should not be interpreted in an overly narrow manner.

[0060] Unless the meaning of the singular is clearly different from the meaning of the plural in the context, the expressions in the singular in this specification include the meaning of the plural. In the following description, the term "include" or "have" may indicate the presence of a feature, number, step, operation, component, part, or a combination thereof described in the specification, and may not exclude the presence or addition of another feature, another number, another step, another operation, another component, another part, or a combination thereof.

[0061] The terms "first" and "second" are used for the purpose of description of various components, and these components are not limited by the terms "first" and "second". The terms "first" and "second" are only used to distinguish one component from another component. For example, a first component can be referred to as a second component without departing from the scope of the present invention.

[0062] It will be understood that when an element or layer is referred to as being “connected to” or “coupled to” another element or layer, the element or layer can be directly connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly connected to” or “directly coupled to” another element or layer, there are no intervening elements or layers.

[0063] Hereinafter, exemplary embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, for ease of understanding, the same reference numerals are used to represent the same components throughout the accompanying drawings, and repeated descriptions of the same components will be omitted. Detailed descriptions related to known technologies that are determined to make the subject matter of the present invention unclear will be omitted. The accompanying drawings are provided only to make the spirit of the present invention easy to understand and should not be considered to limit the present invention. It should be understood that the spirit of the present invention can be extended to modifications, replacements, or equivalents thereof in addition to those shown in the accompanying drawings.

[0064] In the accompanying drawings, for example, a user equipment (UE) is shown. UE may also be denoted as a terminal or mobile equipment (ME). UE may be a laptop computer, mobile phone, PDA, smart phone, multimedia device, or other portable device, or may be a fixed device such as a PC or vehicle-mounted device.

[0065] Definition of terms

[0066] For better understanding, the terms used herein are briefly defined before turning to the detailed description of the present invention with reference to the accompanying drawings.

[0067] UMTS: stands for Universal Mobile Telecommunications System and refers to the third generation mobile communication network.

[0068] UE / MS: User Equipment / Mobile Station, meaning terminal equipment.

[0069] EPC: stands for Evolved Packet Core and refers to the core network that supports Long Term Evolution (LTE) networks, an evolved version of UMTS.

[0070] EPS: stands for Evolved Packet System and means a mobile communication system including UE, access networks including LTE, and EPC.

[0071] PDN (Public Data Network): An independent network in which service providing servers are located.

[0072] PDN connection: a connection from a UE to a PDN, that is, an association (connection) between a UE represented by an IP address and a PDN represented by an APN (Access Point Name).

[0073] PDN-GW (Packet Data Network Gateway): A network node of an EPS network that performs functions such as UE IP address allocation, packet screening and filtering, and charging data collection.

[0074] Serving GW (Serving Gateway): A network node of the EPS network that performs functions such as mobility anchor, packet routing, idle mode packet buffering, and triggering MME to paging UEs.

[0075] PCRF (Policy and Charging Rules Function): an EPS network node that performs policy decisions for dynamically applying QoS and charging policies that are differentiated per service flow.

[0076] APN (Access Point Name): The name of an access point managed by the network and provided from the UE, that is, a string used to identify a PDN or distinguish one PDN from another. Access to the requested service or network (PDN) passes through the corresponding P-GW, and the APN is a name predefined in the network that enables discovery of the P-GW (for example, internet.mnc012.mcc345.gprs).

[0077] TEID (Tunnel Endpoint Identifier): The endpoint ID of a tunnel configured between nodes in a network. TEID is configured per sector for each UE's bearer.

[0078] NodeB: A UMTS network base station. NodeBs are installed outdoors and correspond to macrocells in terms of cell coverage size.

[0079] eNodeB: EPS (Evolved Packet System) base station and is installed outdoors. The eNodeB corresponds to a macro cell in terms of cell coverage size.

[0080] (e)NodeB: collectively represents NodeB and eNodeB.

[0081] MME: stands for Mobility Management Entity and plays a role in controlling each entity in EPS to provide mobility and sessions for UEs.

[0082] Session: A path for data transmission. A session unit may include a PDN, a bearer, and an IP flow corresponding to a unit of the overall target network (APN or PDN), a unit differentiated by QoS therein (bearer unit), and a unit of the destination IP address.

[0083] PDN connection: A connection from a UE to a PDN, i.e., an association (connection) between a UE represented by an IP address and a PDN represented by an APN. This means a connection between entities in the core network (UE-PDN GW) used to form a session.

[0084] UE context: information related to the context of the UE used to manage the UE in the network, ie, context information consisting of UE id, mobility (eg, current location), and session attributes (QoS or priority).

[0085] OMA DM (Open Mobile Alliance Device Management): A protocol designed for managing mobile devices such as mobile phones, PDAs, or laptop computers, and performs functions such as device configuration, firmware upgrades, and error reporting.

[0086] OAM (Operations Administration and Maintenance): refers to a set of network management functions that display network faults and provide capability information, diagnostics and data.

[0087] NAS Configuration MO (Configuration Object): An MO (Management Object) used to configure parameters associated with NAS functions in the UE.

[0088] Hereinafter, the present disclosure is described with reference to the accompanying drawings.

[0089] The disclosure of this specification will be described below with reference to the accompanying drawings.

[0090] In 3GPP, which establishes technical standards for mobile communication systems, in order to deal with fourth-generation communications and several related forums and new technologies, research on Long Term Evolution / System Architecture Evolution (LTE / SAE) technology has been started since late 2004 as part of efforts to optimize and improve the performance of 3GPP technologies.

[0091] SAE, already being implemented by 3GPP SA WG2, is a study related to network technologies aimed at determining network structures and supporting mobility between heterogeneous networks consistent with the LTE mission of 3GPP STRAN, and is one of the most important recent standardization issues of 3GPP. SAE is a mission to evolve the 3GPP system into one that supports various IP-based radio access technologies, and is being implemented with the goal of developing an optimized packet-based system that minimizes transmission delay while improving data transmission capabilities.

[0092] The Evolved Packet System (EPS) higher layer reference model defined in 3GPP SA WG2 includes non-roaming cases and roaming cases with various scenarios, and for details thereof, reference can be made to 3GPP standard documents TS23.401 and TS23.402. The EPS higher layer reference model has been briefly reconfigured. Figure 1 network configuration.

[0093] Figure 2 is an exemplary diagram illustrating the architecture of a public E-UTRAN and a public EPC.

[0094] like Figure 2 As shown, the eNodeB 20 can perform functions such as routing to the gateway while the RRC connection is activated, scheduling and transmission of paging messages, scheduling and transmission of broadcast channels (BCHs), dynamic allocation of resources to UEs in uplink and downlink, configuration and provision of measurements for the eNodeB 20, control of radio bearers, radio admission control, and connection mobility control. The EPC can perform functions such as generation of paging, management of the LTE_IDLE state, encryption of the user plane, control of EPS bearers, and encryption and integrity protection of NAS signaling.

[0095] Figure 3 is an exemplary diagram showing the structure of a radio interface protocol in a control plane between a UE and an eNodeB, and Figure 4 is another exemplary diagram showing the structure of a radio interface protocol in a control plane between a UE and an eNodeB.

[0096] The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol horizontally includes a physical layer, a data link layer, and a network layer, and is divided into a user plane for transmission of information and a control plane for transmission of control signals (or signaling).

[0097] The protocol layers may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on three lower layers of an Open Systems Interconnection (OSI) reference model widely known in communication systems.

[0098] Described below Figure 3 The control plane radio protocols shown and Figure 4 The layer of the radio protocol in the user plane.

[0099] The physical layer (PHY) (i.e., layer 1) provides information transmission services using physical channels. The PHY layer is connected to the medium access control (MAC) layer arranged in a higher layer through a transmission channel, and data is transmitted between the MAC layer and the PHY layer through the transmission channel. In addition, data is transmitted between different PHY layers (i.e., PHY layers on the sender side and the receiver side) through the PHY layer.

[0100] A physical channel consists of multiple subframes on the time axis and multiple subcarriers on the frequency axis. Here, one subframe consists of multiple symbols and multiple subcarriers on the time axis. One subframe consists of multiple resource blocks, and one resource block consists of multiple symbols and multiple subcarriers. The transmission time interval (TTI) (i.e., the unit time during which data is transmitted) is 1 ms corresponding to one subframe.

[0101] According to 3GPP LTE, physical channels existing in the physical layer of the transmitting side and the receiving side can be divided into a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH), that is, data channels, and a physical downlink control channel (PDCCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), and a physical uplink control channel (PUCCH), that is, control channels.

[0102] The PCFICH, sent in the first OFDM symbol of a subframe, carries a control format indicator (CFI) related to the number of OFDM symbols used to send control channels within the subframe (i.e., the size of the control region). A wireless device first receives the CFI on the PCFICH and then monitors the PDCCH.

[0103] Unlike the PDCCH, the PCFICH is transmitted through fixed PCFICH resources in a subframe without using blind decoding.

[0104] The PHICH carries acknowledgement (ACK) / negative acknowledgement (NACK) signals for uplink (UL) hybrid automatic repeat request (HARQ). ACK / NACK signals for UL data on the PUSCH transmitted by a wireless device are sent on the PHICH.

[0105] The Physical Broadcast Channel (PBCH) is transmitted in the first four OFDM symbols of the second slot of the first subframe of a radio frame. The PBCH carries system information necessary for wireless devices to communicate with the eNodeB, and the system information transmitted on the PBCH is called a Master Information Block (MIB). In contrast, the system information transmitted on the PDSCH indicated by the PDCCH is called a System Information Block (SIB).

[0106] The PDCCH can carry resource allocation and transmission format of the downlink shared channel (DL-SCH), information on resource allocation of the uplink shared channel (UL-SCH), paging information of the PCH, system information of the DL-SCH, resource allocation of higher-layer control messages (such as random access responses) sent on the PDSCH, a set of transmit power control commands for multiple UEs within a specific UE group, and activation of the Internet Voice Protocol (VoIP). Multiple PDCCHs can be sent within the control region, and the UE can monitor multiple PDCCHs. The PDCCH is sent on one control channel element (CCE) or an aggregation of multiple consecutive CCEs. CCE is a logical allocation unit used to provide a coding rate to the PDCCH according to the state of the radio channel. CCE corresponds to multiple resource element groups. The format of the PDCCH and the number of possible PDCCH bits are determined by the relationship between the number of CCEs and the coding rate provided by these CCEs.

[0107] The control information transmitted via the PDCCH is called downlink control information (DCI). DCI may include PDSCH resource allocations (also known as downlink (DL) grants), PUSCH resource allocations (also known as uplink (UL) grants), a set of transmit power control commands for multiple UEs within a specific UE group, and / or activation of Voice over Internet Protocol (VoIP).

[0108] There are several layers in the second layer. First, the medium access control (MAC) layer is used to map various logical channels to various transport channels, and also plays a role in logical channel multiplexing for mapping multiple logical channels to one transport channel. The MAC layer is connected to the radio link control (RLC) layer (i.e., a higher layer) through logical channels. Depending on the type of information being transmitted, logical channels are basically divided into control channels, through which control plane information is transmitted, and traffic channels, through which user plane information is transmitted.

[0109] The RLC layer, the second layer, is responsible for controlling the data size of data received from higher layers in the radio section by segmenting and concatenating the data, which is then transmitted via the lower layers. Furthermore, to ensure various types of QoS required for radio bearers, the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). Specifically, AM RLC performs retransmission functions through an Automatic Repeat Request (ARQ) function for reliable data transmission.

[0110] The second layer, the Packet Data Convergence Protocol (PDCP) layer, performs header compression to reduce the size of IP packet headers, which contain relatively large and unnecessary control information. This allows for efficient transmission of IP packets, such as IPv4 or IPv6, over radios with limited bandwidth. This improves transmission efficiency over the radio because only necessary information is transmitted in the data header. Furthermore, in LTE systems, the PDCP layer also performs security functions. These include encryption to prevent data from being intercepted by third parties and integrity protection to prevent data manipulation by third parties.

[0111] The Radio Resource Control (RRC) layer at the highest level of the third layer is defined only in the control plane and is responsible for controlling logical channels, transport channels, and physical channels related to the configuration, reconfiguration, and release of radio bearers (RBs). Here, RBs refer to services provided by the second layer to transmit data between the UE and the E-UTRAN.

[0112] If an RRC connection exists between the RRC layer of the UE and the RRC layer of the wireless network, the UE is in the RRC_CONNECTED state. If not, the UE is in the RRC_IDLE state.

[0113] The following describes the RRC state and RRC connection method of the UE. The RRC state means whether the RRC layer of the UE has been logically connected to the RRC layer of the E-UTRAN. If the RRC layer of the UE is logically connected to the RRC layer of the E-UTRAN, the RRC state is called the RRC_CONNECTED state. If the RRC layer of the UE is not logically connected to the RRC layer of the E-UTRAN, the RRC state is called the RRC_IDLE state. Because the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can detect the presence of the UE in the cell unit and thus effectively control the UE. On the contrary, if the UE is in the RRC_IDLE state, the E-UTRAN cannot detect the presence of the UE and manages the core network in the tracking area (TA) unit (i.e., an area unit larger than a cell). That is, the presence of the UE in the RRC_IDLE state is checked only in the area unit larger than the cell. In such a case, the UE needs to transition to the RRC_CONNECTED state in order to be provided with public mobile communication services such as voice or data. Each TA is categorized by a Tracking Area Identity (TAI). A UE can configure a TAI through a Tracking Area Code (TAC), which is information broadcast by a cell.

[0114] When the user first turns on the power of the UE, the UE first searches for an appropriate cell, establishes an RRC connection in the corresponding cell, and registers information about the UE with the core network. Thereafter, the UE stays in the RRC_IDLE state. The UE in the RRC_IDLE state (re)selects a cell when necessary and checks system information or paging information. This process is called camping. When the UE in the RRC_IDLE state needs to establish an RRC connection, the UE establishes an RRC connection with the RRC layer of the E-UTRAN through the RRC connection process and transfers to the RRC_CONNECTED state. The situations in which the UE in the RRC_IDLE state needs to establish an RRC connection include multiple situations. The multiple situations may include, for example, situations in which UL data needs to be sent due to reasons such as a call attempt made by a user and situations in which a response message needs to be sent in response to a paging message received from the E-UTRAN.

[0115] A non-access stratum (NAS) layer placed above the RRC layer performs functions such as session management and mobility management.

[0116] The following describes in detail Figure 3 The NAS layer is shown.

[0117] The Evolved Session Management (ESM) belonging to the NAS layer performs functions such as the management of the default bearer and the management of the dedicated bearer, and the ESM is responsible for the control required for the UE to use the PS service from the network. The default bearer resources have the following characteristics: they are allocated by the network when the UE first accesses a specific packet data network (PDN) or accesses the network. Here, the network allocates an IP address that can be used for the UE so that the UE can use the data service and QoS of the default bearer. LTE supports two types of bearers: a bearer with a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for the transmission and reception of data, and a non-GBR bearer with a best-effort QoS characteristic without guaranteeing bandwidth. The default bearer is designated as a non-GBR bearer, and the dedicated bearer can be designated as a bearer with GBR QoS characteristics or non-GBR QoS characteristics.

[0118] In the network, a bearer assigned to a UE is called an Evolved Packet Service (EPS) bearer. When assigning an EPS bearer, the network assigns an ID. This is called the EPS bearer ID. An EPS bearer has QoS characteristics of maximum bit rate (MBR) and guaranteed bit rate (GBR) or aggregate maximum bit rate (AMBR).

[0119] Figure 5 This is a flowchart illustrating a random access process in 3GPP LTE.

[0120] The random access process is used for the UE 10 to acquire UL synchronization with the base station (ie, the eNodeB 20 ) or to be assigned UL radio resources.

[0121] UE 10 receives a root index and a physical random access channel (PRACH) configuration index from eNodeB 20. 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence exist in each cell. The root index is a logical index used by the UE to generate the 64 candidate random access preambles.

[0122] The transmission of the random access preamble is limited to specific time and frequency resources in each cell. The PRACH configuration index indicates the preamble format and the specific subframe in which the random access preamble can be transmitted.

[0123] The UE 10 sends a randomly selected random access preamble to the eNodeB 20. Here, the UE 10 selects one of the 64 candidate random access preambles. In addition, the UE selects a subframe corresponding to the PRACH configuration index. The UE 10 sends the selected random access preamble in the selected subframe.

[0124] The eNodeB 20, having received the random access preamble, sends a random access response (RAR) to the UE 10. The random access response is detected in two steps. First, the UE 10 detects the PDCCH masked with the random access RNTI (RA-RNTI). The UE 10 receives the random access response in a medium access control (MAC) protocol data unit (PDU) on the PDSCH indicated by the detected PDCCH.

[0125] Figure 6 The connection processing in the radio resource control (RRC) layer is illustrated.

[0126] Figure 6 1 shows an RRC state depending on whether an RRC connection exists. The RRC state indicates whether an entity of the RRC layer of the UE 10 is logically connected to an entity of the RRC layer of the eNodeB 20, and if so, the RRC state is called an RRC connected state, and if not, the RRC state is called an RRC idle state.

[0127] In the connected state, UE 10 has an RRC connection, so the E-UTRAN can be aware of the UE's presence on a cell-by-cell basis and can effectively control UE 10. In contrast, UE 10 in the idle state is unaware of the eNodeB 20 and is managed by the core network based on a tracking area that is larger than a cell. A tracking area is a collection of cells. That is, the presence of UE 10 in the idle state is only known on a larger area basis, and the UE must switch to the connected state to receive typical mobile communication services such as voice or data services.

[0128] When a user turns on UE 10, UE 10 searches for a suitable cell and stays in an idle state in the cell. UE 10 establishes an RRC connection with the RRC layer of eNodeB 20 through an RRC connection procedure when necessary and transitions to an RRC connected state.

[0129] There are many situations where a UE staying in the idle state needs to establish an RRC connection, for example when a user attempts a call or when uplink data transmission is required, or when sending a message in response to receiving a paging message from the EUTRAN.

[0130] In order for the idle UE 10 to establish an RRC connection with the eNodeB 20, the UE 10 needs to perform the RRC connection procedure as described above. The RRC connection procedure generally occurs with a process in which the UE 10 sends an RRC connection request message to the eNodeB 20, a process in which the eNodeB 20 sends an RRC connection establishment message to the UE 10, and a process in which the UE 10 sends an RRC connection establishment complete message to the eNodeB 20. Figure 6 These processes are described in more detail.

[0131] 1) An idle UE 10 sends an RRC connection request message to the eNodeB 20 when attempting to establish an RRC connection, for example, in order to attempt a call or send data or to respond to a paging from the eNodeB 20 .

[0132] 2) When receiving the RRC connection message from UE 10 , if there are sufficient radio resources, eNodeB 20 accepts the RRC connection request from UE 10 , and eNodeB 20 sends a response message, ie, an RRC connection establishment message, to UE 10 .

[0133] 3) Upon receiving the RRC connection setup message, UE 10 sends an RRC connection setup complete message to eNodeB 20. If UE 10 successfully sends the RRC connection setup message, UE 10 establishes an RRC connection with eNodeB 20 and switches to the RRC connected state.

[0134] Figure 7 An exemplary Tracking Area Update (TAU) process is shown. The process may include the following steps:

[0135] 1) In idle mode, the user equipment (UE) 100 moves into the coverage of the target eNodeB 200b and therefore determines to initiate a Tracking Area Update (TAU) procedure.

[0136] 2) Subsequently, the UE 100 sends a TAU request message to the target eNodeB 200b.

[0137] 3) Next, the target eNodeB 200b determines a responsible MME (Mobility Management Entity). For example, it can be assumed that the target MME 510b is determined as the responsible MME. The target eNodeB 200b transmits a TAU request message to the target MME 510b. During this process, it is assumed that the serving gateway (S-GW) 520 has not changed.

[0138] 4-5) Subsequently, the target MME 510b sends a UE context request message (eg, ContextRequest) to the source MME 510a and receives a context response message (eg, ContextResponse) from the source MME 510a to obtain information associated with the PDN connection and EPS bearer related information.

[0139] 6) Subsequently, an authentication / security process is performed between the UE 100 and the target MME 510 b , and a security verification process is performed between the target MME 510 b and the Home Subscriber Server (HSS) 590 .

[0140] 7) After acquiring the context information, the target MME 510b sends a context confirmation message (eg, Context Acknowledge) to the source MME 510a.

[0141] 8) Since the S-GW 520 is not replaced during this TAU process, the target MME 510b sends a bearer modification request message (eg, Modify Bearer Request) to the S-GW 520 instead of a session creation request message (eg, Create Session Request).

[0142] 9-11) Subsequently, S-GW 520 sends a bearer modification request message to PDN gateway (PDN-GW) 530 as needed. PDN-GW 530 performs the IP-CAN session modification procedure as needed and returns a bearer modification response message (e.g., Modify Bearer Response) to S-GW 520.

[0143] 12) Subsequently, the S-GW 520 sends a bearer modification response message to the target MME 510b.

[0144] 13) The target MME 510b then sends a location update request message (eg, UpdateLocation Request) to the HSS 590 .

[0145] 14-15) Subsequently, the HSS 590 sends a location cancellation message (eg, Cancel Location) to the source MME 510a , and the source MME 510a returns a location cancellation confirmation message (eg, CancelLocation Ack) to the HSS 590 .

[0146] 16) Subsequently, the HSS 590 sends a location update confirmation message (eg, UpdateLocation Ack) to the target MME 510b.

[0147] 17-18) Next, the target MME 510b sends a TAU accept message (eg, TAU Accept) to the UE 100 via the target eNodeB 200b, and the UE 100 sends a TAU complete message (eg, TAU Complete) to the target MME 510b as needed.

[0148] Tables 2 to 9 below show the message types used in various processing procedures.

[0149] The TAU request message may include one or more information elements shown in Table 2.

[0150] [Table 2]

[0151]

[0152]

[0153] The EPC update type information element shown in Table 2 in the above table may include the following bit fields.

[0154] [Table 3]

[0155]

[0156] At the same time, the above context request message may include the information elements shown in Table 4 below.

[0157] [Table 4]

[0158]

[0159] At the same time, the above context request message may include the information elements shown in Table 5 below.

[0160] [Table 5]

[0161]

[0162]

[0163] The PDN connection information in the context response message may include the information elements shown in Table 6 below.

[0164] [Table 6]

[0165]

[0166] The bearer context information included in the PDN connection information in the context response may include the information shown in Table 7 below.

[0167] [Table 7]

[0168]

[0169]

[0170] The AU acceptance message may include the information shown in Table 8 below.

[0171] [Table 8]

[0172] information illustrate TAU accepts message identifiers Message Identifier TAU Results Indicates the result of the update, such as success or failure T3412 timer value Timer value for periodic TAU T3402 timer value Timer that starts when TAU fails T3412 extended timer value T3412 extension value used to further extend the periodic TAU

[0173] In Table 8 above, the T3412 value is the timer value that allows UE 100 to periodically perform Tracking Area Updates (TAUs). To reduce the network load caused by periodic TAUs, an extended T3412 value exists that allows TAUs to be performed at a longer period. This extended T3412 value can be set by the MME or stored in HSS 540 as user subscription information.

[0174] <Disclosure of this Specification>

[0175] Figure 8 is a schematic flow chart showing a process according to an embodiment of the present specification.

[0176] See also Figure 8 , the UE may send a request message (S110). The request message may be a tracking area update request message.

[0177] Next, the UE may receive a response message (S120).

[0178] When the response message is a tracking area update accept message and the accept message includes radio access technology (RAT) utilization control information, the RAT utilization control information may be used for the current PLMN (public land mobile network) and its equivalent PLMN.

[0179] The UE may delete the stored RAT utilization control information (S130). Specifically, if the tracking area update request message includes information on support of a RAT utilization control, and the response message is a tracking area update accept message, but the accept message does not include the RAT utilization control information, the UE may delete the stored RAT utilization control information.

[0180] When the tracking area update accept message includes the RAT utilization control information, the UE may store the RAT utilization control information together with the PLMN identity of the current PLMN in a list of PLMNs with associated RAT restrictions.

[0181] If the UE is in a switched-off state, the UE may retain the stored list for use after being switched on again.

[0182] When a USIM (Universal Subscriber Identity Module) in the UE is removed, the UE may delete the stored list.

[0183] When the response message is a tracking area update reject message, and the reject message includes RAT utilization control information and successfully passes the integrity check, the UE may store the RAT utilization control information together with the PLMN identifier of the current PLMN in the PLMN list associated with the RAT restriction.

[0184] The UE may also replace previously stored RAT utilization control information associated with the current PLMN with the new RAT utilization control information.

[0185] When the response message is a tracking area update reject message, the reject message may include information indicating that no suitable cells are available in the tracking area.

[0186] <Summary of Examples in This Specification>

[0187] I. EPS-based UE control of RAT usage

[0188] The network operator may restrict user access to specific RATs. To this end, the network may send a RAT utilization control information element (RATutilization control IE) to the UE via an Attach Accept, Attach Reject, Network-initiated Detach Request, Tracking Area Update Accept, or Tracking Area Update Reject message to provide RAT utilization control information about the current PLMN or the current PLMN and its equivalent PLMN.

[0189] In addition, when performing PLMN selection, the UE should not consider any PLMN and RAT combination with RAT restrictions as a candidate PLMN.

[0190] The UE may store the received RAT utilization control information together with the PLMN identity of the current PLMN in a "PLMN list with associated RAT restrictions". This list may be used by 5GMM, EMM, GMM and MM.

[0191] When the UE is powered off (switch off), the UE may retain the stored list so as to continue using it after it is powered on again (switch on).

[0192] When the USIM (Universal Subscriber Identity Module) is removed, the UE may delete the stored list.

[0193] The number of entries that a UE can store in the "PLMN list with associated RAT restrictions" depends on the specific implementation, but can be at least one or more.

[0194] II. When the network accepts the tracking area update procedure

[0195] When the UE indicates support of RAT utilization control in the Tracking Area Update Request message and the network decides to apply RAT utilization control, the MME shall include the RAT utilization control information element (RAT utilization control IE) in the Tracking Area Update Accept message.

[0196] The MME may not indicate "E-UTRAN is restricted in the current PLMN" in the RAT Utilization Control IE.

[0197] If the TRACKING AREAUPDATE ACCEPT message contains the RAT Utilization Control IE, the UE shall store the received RAT Utilization Control information and, if there is already stored information, replace the previously stored content with the newly received RAT Utilization Control information.

[0198] Conversely, if the UE indicates support for RAT Utilization Control in the Tracking Area Update Request message and the Tracking Area Update Accept message does not include the RAT Utilization Control IE, the UE should delete the stored RAT Utilization Control information (if any) and may regard all RATs as unrestricted.

[0199] III. When the network rejects the tracking area update process

[0200] When the UE indicates support for RAT utilization control information and initiates an Attach Request, and the network decides to apply access technology control to the current RAT, the MME shall set the EMM cause value in the Tracking Area Update Reject message to #15 (no suitable cell in the tracking area) and include the RAT utilization control information element (RAT utilization control IE) in the Tracking Area Update Reject message.

[0201] When the RAT Utilization Control IE is present in the TRACKING AREA UPDATE REJECT message and the TRACKING AREA UPDATE REJECT message has successfully passed the integrity check by the NAS layer, the UE shall store the received RAT Utilization Control information together with the PLMN identity of the current PLMN in the "list of PLMNs with associated RAT restrictions" and may replace the previously stored information associated with the current PLMN with the newly received RAT Utilization Control information if it exists.

[0202] IV. When the network rejects the attach process

[0203] When the UE indicates support for RAT utilization control information and initiates an Attach Request, and the network decides to apply access technology control to the current RAT, the MME shall set the EMM cause value to #15 (no suitable cell in the tracking area) in the Attach Reject message and include the RAT utilization control information element (RATutilization control IE) in the Attach Reject message.

[0204] When the RAT Utilization Control IE is present in the ATTACH REJECT message and the ATTACH REJECT message has successfully passed the integrity check by the NAS layer, the UE shall store the received RAT Utilization Control information together with the PLMN identity of the current PLMN in the "list of PLMNs with associated RAT restrictions" and may replace the previously stored information associated with the current PLMN with the newly received RAT Utilization Control information if there is any.

[0205] Figure 9 is a block diagram illustrating a configuration of a terminal according to one embodiment of the present disclosure.

[0206] UE 100 includes a memory 1010, a processor 1020, a transmission / reception unit 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042 and a microphone 1052, a subscriber identity module (SIM) card, and one or more antennas.

[0207] The processor 1020 may be configured to implement the functions, processes, and / or methods described herein. The layers of the wireless interface protocol may be implemented in the processor 1020. The processor 1020 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor 1020 may be an application processor (AP). The processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Examples of the processor 1020 may be a SNAPDRAGON™ series processor manufactured by Qualcomm, an EXYNOS™ series processor manufactured by Samsung, an A series processor manufactured by Apple, a HELIO™ series processor manufactured by MediaTek, an ATOM™ series processor manufactured by INTEL, or corresponding next-generation processors.

[0208] Power management module 1091 manages power to processor 1020 and / or transceiver 1031. Battery 1092 supplies power to power management module 1091. Display 1041 outputs results processed by processor 1020. Input unit 1053 receives input for use by processor 1020. Input 1053 may be displayed on display 1041. A SIM card is an integrated circuit used to securely store an International Mobile Subscriber Identity (IMSI) and related keys, which are used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Contact information can be stored on many SIM cards.

[0209] The memory 1010 is operably coupled to the processor 1020 and stores various information used to operate the processor 610. The memory 1010 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiments are implemented in software, the techniques described herein may be implemented in modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in the memory 1010 and executed by the processor 1020. The memory 1010 may be implemented within the processor 1020. Alternatively, the memory 1010 may be implemented outside the processor 1020 and may be communicatively coupled to the processor 1020 by various means known in the art.

[0210] The transmit / receive unit 1031 is operably coupled to the processor 1020 and transmits and / or receives wireless signals. The transmit / receive unit 1031 includes a transmit unit and a receive unit. The transmit / receive unit 1031 may include a baseband circuit for processing radio frequency signals. The transmit / receive unit controls one or more antennas to transmit and / or receive wireless signals. The processor 1020 transmits instruction information to the transmit / receive unit 1031 to transmit a wireless signal, such as a voice communication data, to initiate communication. The antenna is used to transmit and receive wireless signals. When a wireless signal is received, the transmit / receive unit 1031 can transmit the signal and convert the signal to baseband for processing by the processor 1020. The processed signal can be converted into audible or readable information output via the speaker 1042.

[0211] The speaker 1042 outputs sound-related results processed by the processor 1020. The microphone 1052 receives sound-related input used by the processor 1020.

[0212] The user inputs command information, such as a phone number, by pressing (or touching) a button of the input unit 1053 or by voice activation using the microphone 1052. The processor 1020 receives this command information and performs an appropriate function, such as dialing a phone number. Operation data may be retrieved from the SIM card or the memory 1010. In addition, the processor 1020 may display the command information or driving information on the display 1041 for user recognition and convenience.

[0213] Figure 10 A block diagram showing the configuration of a processor in which the present disclosure is implemented is shown.

[0214] If you will refer to Figure 10 As can be seen, the processor 1020 implementing the present disclosure may include multiple circuits to implement the proposed functions, processes and / or methods described herein. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3. In addition, although not shown, the processor 1020 may include more circuits. Each circuit may include multiple transceivers.

[0215] The first circuit 1020 - 1 can send a request message, which may be a tracking area update request message.

[0216] The second circuit 1020 - 2 is capable of receiving a response message.

[0217] When the response message is a tracking area update accept message, and the tracking area update accept message includes radio access technology (RAT) utilization control information, the RAT utilization control information may be used for a current PLMN (public land mobile network) and its equivalent PLMN.

[0218] The third circuit 1020-3 is capable of deleting the RAT utilization control information. Specifically, if the tracking area update request message includes information on whether RAT utilization control is supported, and the response message is a tracking area update accept message, and the tracking area update accept message does not include the RAT utilization control information, the stored RAT utilization control information may be deleted.

[0219] The processor 1020 may be referred to as an ASIC (Application Specific Integrated Circuit) or an AP (Application Processor), and may include at least one DSP (Digital Signal Processor), a CPU (Central Processing Unit), or a GPU (Graphics Processing Unit).

[0220] The processor may be installed on a UE.

[0221] Although preferred embodiments have been exemplarily described, the disclosure of this specification is not limited to these specific embodiments, but may be modified, changed, or improved in various forms within the spirit of this specification and the scope of the claims.

[0222] In the exemplary system described above, the method is described as a series of steps or blocks according to the flowchart, but is not limited to the order of the steps described. Some steps may occur in a different order than the above steps or simultaneously. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the rights.

[0223] The claims described herein may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a device. Furthermore, the technical features of the method claims of this specification may be combined with the technical features of the device claims to implement a device, and the technical features of the method claims of this specification may be combined with the technical features of the device claims to implement a device.

Claims

1. A method for operating a user equipment, comprising the following steps: Send a tracking area update request message; Receive a response message, where If the response message is a tracking area update accept message, and the tracking area update accept message includes radio access technology utilization control information, the radio access technology utilization control information is applicable to the current public land mobile network and its equivalent public land mobile network; as well as If the tracking area update request message includes information about wireless access technology utilization control support, and the response message is a tracking area update accept message, and the tracking area update accept message does not include the wireless access technology utilization control information, the stored wireless access technology utilization control information is deleted.

2. The method according to claim 1, further comprising the steps of: If the tracking area update accept message includes the radio access technology utilization control information, the radio access technology utilization control information is stored together with the public land mobile network identifier of the current public land mobile network in a public land mobile network list associated with radio access technology restrictions.

3. The method according to claim 2, further comprising the steps of: If the user device is turned off, the stored list is kept so that it can be used even after the device is turned back on.

4. The method according to claim 2, further comprising the steps of: If the universal subscriber identity module is removed from the user equipment, the stored list is deleted.

5. The method according to claim 1, further comprising the steps of: If the response message is a tracking area update reject message, the tracking area update reject message includes radio access technology utilization control information, and if the tracking area update reject message successfully passes the integrity check, the radio access technology utilization control information is stored together with the public land mobile network identifier of the current public land mobile network in the public land mobile network list associated with radio access technology restrictions.

6. The method according to claim 5, further comprising the steps of: The stored radio access technology utilization control information associated with the current public land mobile network is replaced with the new radio access technology utilization control information.

7. The method according to claim 1, wherein: If the response message is a tracking area update reject message, the tracking area update reject message includes information indicating that there is no suitable cell in the tracking area.

8. A user equipment comprising: Receiving and dispatching department; as well as a processor for controlling the transceiver unit and performing operations, The operations performed by the processor include the following steps: Send a tracking area update request message; receiving a response message, wherein if the response message is a tracking area update accept message and the tracking area update accept message includes radio access technology utilization control information, the radio access technology utilization control information is applicable to the current public land mobile network and its equivalent public land mobile network; as well as If the tracking area update request message includes information about wireless access technology utilization control support, and the response message is a tracking area update accept message, and the tracking area update accept message does not include wireless access technology utilization control information, the stored wireless access technology utilization control information is deleted.

9. The user equipment according to claim 8, wherein the operations further comprise: If the tracking area update accept message includes the radio access technology utilization control information, the radio access technology utilization control information is stored together with the public land mobile network identifier of the current public land mobile network in a public land mobile network list associated with radio access technology restrictions.

10. The user equipment according to claim 8, wherein the operation further comprises the following steps: If the user device is turned off, the stored list is retained so that it can be continued to be used after the device is turned back on.

11. The user equipment according to claim 8, wherein the operation further comprises the following steps: If the universal subscriber identity module is removed from the user equipment, the stored list is deleted.

12. The user equipment according to claim 8, wherein the operation further comprises the following steps: If the response message is a tracking area update reject message, the tracking area update reject message includes radio access technology utilization control information, and if the tracking area update reject message successfully passes the integrity check, the radio access technology utilization control information is stored together with the public land mobile network identifier of the current public land mobile network in the public land mobile network list associated with radio access technology restrictions.

13. The user equipment according to claim 8, wherein the operation further comprises the following steps: The stored radio access technology utilization control information associated with the current public land mobile network is replaced with the new radio access technology utilization control information.

14. The user equipment according to claim 8, wherein: If the response message is a tracking area update reject message, the tracking area update reject message includes information indicating that there is no suitable cell in the tracking area.

15. A semiconductor chipset comprising: at least one processor; as well as at least one memory storing instructions and electrically operably connected to the at least one processor and, When the instruction is executed by the at least one processor, the operations performed include the following steps: Send a tracking area update request message; receiving a response message, wherein if the response message is a tracking area update accept message and the message includes radio access technology utilization control information, the radio access technology utilization control information is applicable to the current public land mobile network and its equivalent public land mobile network; and If the tracking area update request message includes information about wireless access technology utilization control support, and the response message is a tracking area update accept message, and the tracking area update accept message does not include wireless access technology utilization control information, the stored wireless access technology utilization control information is deleted.

Images