Method and user equipment for activating access stratum after detach unavailable period

Abstract

According to one embodiment of the present specification, an operation method of a user equipment (UE) is provided. The method can include triggering a tracking area update (TAU) procedure when an unavailability period ends and a discontinuous coverage maximum time offset timer expires, starting a first timer when the UE includes unavailability information but does not include start of the unavailability period information in a tracking area update request message at completion of the TAU procedure, and activating an access stratum (AS) procedure after leaving the unavailability period.

Description

Technical Field

[0001] This manual relates to 3GPP wireless communication systems. Background Technology

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

[0003] The SAE (Self-Enhancing Engineering) work, already implemented based on 3GPP SA WG2, relates to network technology research aimed at determining network architecture and supporting mobility between heterogeneous networks consistent with the LTE mission of 3GPP PTS GRAN, and is one of the most important recent standardization issues for 3GPP. The SAE is a task for developing 3GPP systems to support various IP-based radio access technologies, and has been implemented with the aim of optimizing packet-based systems to minimize transmission latency while achieving improved data transmission capabilities.

[0004] The Evolved Packet System (EPS) higher-level reference model defined in 3GPP SA WG2 includes non-roaming and roaming scenarios with various conditions, and for details, refer to 3GPP standard documents TS 23.401 and TS 23.402. A brief reconfiguration has been performed based on the EPS higher-level reference model. Figure 1 Network configuration.

[0005] Figure 1 The configuration of an evolved mobile communication network is shown.

[0006] The Evolved Packet Core (EPC) can include a variety of components. Figure 1 Examples of some of the aforementioned components are shown: Serving Gateway (S-GW) 52, Packet Data Network Gateway (PDN GW) 53, Mobility Management Entity (MME) 51, Serving General Packet Radio Service (GPRS) Support Node (SGSN), and Enhanced Packet Data Gateway (ePDG).

[0007] The S-GW 52 is an element that operates at the boundary point between the Radio Access Network (RAN) and the core network, and has the function of maintaining the data path between the eNodeB 22 and the PDN GW 53. Furthermore, if a terminal (or User Equipment (UE)) moves within an area served by the eNodeB 22, the S-GW 52 acts as a local mobility anchor. 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 via the S-GW 52. Additionally, the S-GW 52 can act as a mobility anchor in the case of another 3GPP network (i.e., a RAN defined before 3GPP Release 8, such as UTRAN or Global System for Mobile Communications (GSM) (GERAN) / Enhanced Data Rate Global Evolution (EDGE) radio access network).

[0008] The PDN GW (or P-GW) 53 corresponds to the termination point of the data interface toward the packet data network. The PDN GW 53 supports policy enforcement features, packet filtering, and charging support. Furthermore, the PDN GW (or P-GW) 53 can act as an anchor point for mobility management in both 3GPP and non-3GPP networks (e.g., unreliable networks such as Interconnected Wireless LAN (I-WLAN) and Code Division Multiple Access (CDMA) networks, or reliable networks such as WiMax).

[0009] exist Figure 1 In the network configuration, S-GW 52 and PDN GW 53 are already illustrated as standalone gateways, but these two gateways can be implemented using a single gateway configuration option.

[0010] The MME 51 is a component used to perform access functions for terminal-to-network connections, as well as signaling and control functions to support network resource allocation, tracking, paging, roaming, handover, etc. The MME 51 controls control plane functions related to subscriber and session management. The MME 51 manages numerous eNodeBs 22 and performs routine signaling for selecting a gateway to handover to another 2G / 3G network. Furthermore, the MME 51 performs functions such as security procedures, terminal-to-network session processing, and idle terminal location management.

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

[0012] ePDG serves as a secure node for unreliable non-3GPP networks (such as I-WLAN and Wi-Fi hotspots).

[0013] For reference Figure 1 As described, an IP-enabled terminal (or UE) can access an IP service network (e.g., IMS) provided by a service provider (e.g., an operator) via various elements within the EPC that are 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 the 3GPP system, the conceptual link connecting two functions existing in different functional entities of E-UTRAN and EPC is called a reference point. Table 1 below defines... Figure 1 The reference points shown are as follows. In addition to the reference points shown in the examples in Table 1, various other reference points may exist depending on the network configuration.

[0015] [Table 1]

[0016]

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

[0018] This specification presents a method for performing a Tracking Area Update (TAU) procedure after an unavailability period has ended.

[0019] According to one embodiment of this specification, an operation method for a user equipment (UE) is proposed. The method includes: triggering a Tracking Area Update (TAU) procedure when an unavailability period ends and a timer for the discontinuous coverage maximum time offset expires; if the UE includes unavailability information in a tracking area update request message but not information about the start of the unavailability period, then starting a first timer upon completion of the TAU procedure; and activating the Access Stratum (AS) after exiting the unavailability period.

[0020] According to one embodiment of this specification, a user equipment (UE) is also provided. The UE may include: a transceiver unit; and a processor for controlling the transceiver unit and performing operations.

[0021] The operations performed by the processor may include: triggering a TAU procedure when the unavailability period ends and the maximum time offset timer for discontinuous coverage expires; starting a first timer when the TAU procedure is completed if the UE contains unavailability information but not the start information of the unavailability period in the TAU request message; and activating the AS layer after leaving the unavailability period.

[0022] According to one embodiment of this specification, a chipset installed in the UE is also provided. The chipset includes: at least one processor; and at least one memory capable of storing instructions and electrically connected to the processor.

[0023] When the instruction is executed by the processor, the chipset may perform the following operations: triggering a TAU process when the unavailability period ends and the discontinuous coverage maximum time offset timer expires; if the UE contains unavailability information in the TAU request message but not the start information of the unavailability period, then starting a first timer when the TAU process is completed; and activating the AS layer after leaving the unavailability period.

[0024] According to one embodiment of this specification, a non-volatile computer-readable storage medium recording instructions is also provided. The instructions are executable by one or more processors installed in the device to cause the processors to perform the following operations: triggering a TAU procedure when the unavailability period ends and the maximum time offset timer for discontinuous coverage expires; starting a first timer when the TAU procedure completes if the UE includes unavailability information in the TAU request message but not the start information of the unavailability period; and activating the AS layer after the unavailability period ends.

[0025] Furthermore, the method or operation may also include: if the first timer is not running, and the UE contains unavailability information but not the start information of the unavailability period in the TAU request message, then when the TAU process is completed, the non-access stratum (NAS) signaling connection is released locally; the step of entering a registered state; the TAU request message may contain unavailability information but not the start information of the unavailability period; the step of sending the TAU request message containing unavailability information but not the start information of the unavailability period.

[0026] When the maximum time offset value for discontinuous coverage has been stored, and the most recently received Tracking Area Update Accept message contains an end of unavailability report bit, and this bit is set to "UE needs to report end of unavailability period", when the UE returns after leaving the coverage area due to discontinuous coverage, a random value less than or equal to the stored maximum time offset value can be set for the PLMN and satellite E-UTRAN access, and the corresponding timer can be started.

[0027] Based on the disclosure in this specification, a Tracking Area Update (TAU) process is also provided. Attached Figure Description

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

[0029] Figure 2 This is a schematic diagram illustrating the main node functions of a typical E-UTRAN and a typical EPC.

[0030] Figure 3 This is a schematic diagram showing the structure of the Radio Interface Protocol in the control plane between the UE and the eNodeB.

[0031] Figure 4 This is another schematic diagram showing the wireless interface protocol structure in the user plane between the terminal and the base station.

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

[0033] Figure 6 This is a diagram illustrating the connection process in the Radio Resource Control (RRC) layer.

[0034] Figure 7 This is a schematic diagram illustrating the TAU (Tracking Area Update) process.

[0035] Figure 8 This is a schematic flowchart illustrating a process according to an embodiment of this specification.

[0036] Figure 9 This is a block diagram illustrating a terminal structure according to an embodiment of this specification.

[0037] Figure 10This is a block diagram showing the structure of a processor that implements the contents disclosed in this specification. Detailed Implementation

[0038] While the present invention is described in light of UMTS (Universal Mobile Telecommunications System) and EPC (Evolved Packet Core), it is not limited to these communication systems. Rather, it can be applied to all communication systems and methods to which the technical spirit of the present invention is applicable.

[0039] The technical terms used herein are intended to describe specific embodiments only and should not be construed as limiting the invention. Furthermore, unless otherwise defined, the technical terms used herein should be interpreted in the sense of having a meaning commonly understood by those skilled in the art, and should not be interpreted too broadly or too narrowly. Additionally, technical terms used herein that are determined not to properly represent the spirit of the invention should be replaced or understood by such technical terms as would be correctly understood by those skilled in the art. Moreover, general terms used herein should be interpreted as defined in their dictionary context, and should not be interpreted in an overly narrow manner.

[0040] Unless the meaning of the singular is clearly different from that of the plural in the context, the singular expressions in this specification include the meaning of the plural. In the following description, the terms "include" or "have" may indicate the presence of a feature, number, step, operation, component, part, or 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 combination thereof.

[0041] The terms "first" and "second" are used for descriptive purposes regarding various components, and these components are not limited by the terms "first" and "second". The terms "first" and "second" are used only to distinguish one component from another. For example, a first component may be referred to as a second component without departing from the scope of the invention.

[0042] What will be understood is that when a component or layer is referred to as "connected to" or "coupled to" another component or layer, the one component or layer can be directly connected to or coupled to the other component or layer, or there may be intermediate components or layers. Conversely, when a component is referred to as "directly connected to" or "directly coupled to" another component or layer, there are no intermediate components or layers.

[0043] In the following description, exemplary embodiments of the invention will be described in more detail with reference to the accompanying drawings. In describing the invention, for ease of understanding, the same reference numerals are used throughout the drawings to denote the same components, and repeated descriptions of the same components will be omitted. Detailed descriptions relating to well-known techniques that are determined to obscure the gist of the invention will be omitted. The drawings are provided merely to facilitate understanding of the spirit of the invention and should not be considered as limiting the invention. It should be understood that the spirit of the invention can be extended to modifications, substitutions, or equivalents beyond those shown in the drawings.

[0044] In the accompanying drawings, a user equipment (UE) is shown, for example. The UE can also be represented as a terminal or mobile device (ME). The UE can be a laptop computer, mobile phone, PDA, smartphone, multimedia device, or other portable device, or it can be a fixed device such as a PC or in-vehicle equipment.

[0045] Definition of terminology

[0046] For better understanding, the terminology used herein is briefly defined before proceeding to the detailed description of the invention with reference to the accompanying drawings.

[0047] UMTS stands for Universal Mobile Telecommunications System and refers to the third generation of mobile communication networks.

[0048] UE / MS: User Equipment / Mobile Station, referring to terminal equipment.

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

[0050] EPS stands for Evolved Packet System and refers to mobile communication systems including UE, access networks including LTE, and EPC.

[0051] PDN (Public Data Network): A separate network in which service-providing servers reside.

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

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

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

[0055] PCRF (Policy and Charging Rules Function): An EPS network node that executes policy decisions for dynamically applying per-service-flow-differentiable QoS and charging policies.

[0056] APN (Access Point Name): The name of the access point provided by the UE and managed by the network; that is, a string used to represent a PDN or distinguish one PDN from another. The service or network (PDN) requested for access is accessed through the corresponding P-GW, and the APN is a predefined name in the network that can discover the P-GW (e.g., internet.mnc012.mcc345.gprs).

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

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

[0059] eNodeB: An EPS (Evolved Packet System) base station installed outdoors. In terms of cell coverage size, an eNodeB corresponds to a macro cell.

[0060] (e)NodeB: Together it represents NodeB and eNodeB.

[0061] MME: Represents the Mobility Management Entity and plays a role in controlling each entity in EPS to provide mobility and sessions for UE.

[0062] Session: The path used for data transmission. The unit of a session may include a PDN, a bearer, and IP flows of units corresponding to the overall target network (units of APN or PDN), units distinguished by QoS (units of the bearer), and units of destination IP addresses.

[0063] PDN connection: The connection from UE to PDN, that is, the association (connection) between the UE represented by its IP address and the PDN represented by its APN. This refers to the connection used to form a session between entities in the core network (UE-PDN GW).

[0064] UE context: Information related to the context of a UE used to manage the UE in the network, i.e., context information consisting of UE ID, mobility (e.g., current location), and session attributes (QoS or priority).

[0065] OMA DM (Open Mobile Alliance Device Management): Protocols designed to manage mobile devices such as mobile phones, PDAs, or laptops, and to perform functions such as device configuration, firmware upgrades, and bug reporting.

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

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

[0068] The present disclosure is described below with reference to the accompanying drawings.

[0069] The contents disclosed in this specification will be described below with reference to the accompanying drawings.

[0070] Within 3GPP, which established the technical standards for mobile communication systems, research on Long Term Evolution / System Architecture Evolution (LTE / SAE) technology began in late 2004 as part of efforts to optimize and improve the performance of 3GPP technologies in order to handle fourth-generation communications and several related forums and new technologies.

[0071] The SAE (Self-Enhancing Engineering) work, already implemented based on 3GPP SA WG2, relates to network technology research aimed at determining network architecture and supporting mobility between heterogeneous networks consistent with the LTE mission of 3GPP PTS GRAN, and is one of the most important recent standardization issues for 3GPP. The SAE is a task for developing 3GPP systems to support various IP-based radio access technologies, and has been implemented with the aim of optimizing packet-based systems to minimize transmission latency while achieving improved data transmission capabilities.

[0072] The Evolved Packet System (EPS) higher-level reference model defined in 3GPP SA WG2 includes non-roaming and roaming scenarios with various conditions, and for details, refer to 3GPP standard documents TS 23.401 and TS 23.402. A brief reconfiguration has been performed based on the EPS higher-level reference model. Figure 1 Network configuration.

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

[0074] like Figure 2As shown, the eNodeB 20 can perform functions such as routing to the gateway while an RRC connection is active, scheduling and transmitting paging messages, scheduling and transmitting broadcast channels (BCH), dynamically allocating resources to the UE in the uplink and downlink, configuring and providing measurements for the eNodeB 20, controlling radio bearers, controlling radio admissions, and controlling connection mobility. The EPC can perform functions such as generating paging messages, managing LTE_IDLE states, encrypting the user plane, controlling EPS bearers, and encrypting and protecting the integrity of NAS signaling.

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

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

[0077] Protocol layers can be classified into Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3) based on the three lower layers of the Open Systems Interconnection (OSI) reference model, which is widely known in communication systems.

[0078] The following describes Figure 3 The radio protocols of the control plane shown Figure 4 The user plane layer of radio protocols.

[0079] The Physical Layer (PHY) (i.e., Layer 1) uses physical channels to provide information delivery services. The PHY layer connects to the Media Access Control (MAC) layer, which is located in higher layers, via a transport channel, and data is transmitted between the MAC layer and the PHY layer through this transport channel. Furthermore, data is transmitted between different PHY layers (i.e., between the PHY layers on the sending and receiving sides).

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

[0081] According to 3GPP LTE, the physical channels existing in the physical layer on the transmitting and receiving sides can be divided into the Physical Downlink Shared Channel (PDSCH) and the Physical Uplink Shared Channel (PUSCH), i.e., the data channel, as well as the Physical Downlink Control Channel (PDCCH), the Physical Control Format Indicator Channel (PCFICH), the Physical Hybrid ARQ Indicator Channel (PHICH), and the Physical Uplink Control Channel (PUCCH), i.e., the control channel.

[0082] The PCFICH transmitted in the first OFDM symbol of a subframe carries a Control Format Indicator (CFI) relating to the number of OFDM symbols used to transmit the control channel within that subframe (i.e., the size of the control area). The wireless device first receives the CFI on the PCFICH and then monitors the PDCCH.

[0083] Unlike PDCCH, PCFICH is transmitted through the fixed PCFICH resources of the subframe without the need for blind decoding.

[0084] The PHICH carries positive acknowledgment (ACK) / negative acknowledgment (NACK) signals for uplink (UL) Hybrid Automatic Repeat Request (HARQ). ACK / NACK signals are transmitted on the PHICH for UL data transmitted by the radio device on the PUSCH.

[0085] The Physical Broadcast Channel (PBCH) is transmitted in the first four OFDM symbols of the second time slot of the first subframe of the radio frame. The PBCH carries system information necessary for communication between the radio device and the eNodeB, and the system information transmitted via the PBCH is called the Master Information Block (MIB). Conversely, the system information transmitted on the PDSCH indicated by the PDCCH is called the System Information Block (SIB).

[0086] 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), PCH paging information, DL-SCH system information, resource allocation of higher-layer control messages (such as random access responses) transmitted on the PDCCH, a set of transmit power control commands for multiple UEs within a specific UE group, and activation of Voice over Internet Protocol (VoIP). Multiple PDCCHs can be transmitted within a control area, and UEs can monitor multiple PDCCHs. PDCCHs are transmitted on a control channel element (CCE) or an aggregation of multiple consecutive CCEs. A CCE is a logical allocation unit used to provide coding rates to the PDCCH based on the state of the radio channel. A CCE corresponds to multiple resource element groups. The format of the PDCCH and the number of bits in a possible PDCCH are determined by the relationship between the number of CCEs and the coding rates provided by these CCEs.

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

[0088] The second layer contains several sublayers. First, the Media Access Control (MAC) layer maps various logical channels to various transport channels and also serves as a logical channel multiplexing layer for mapping multiple logical channels to a single transport channel. The MAC layer connects to the Radio Link Control (RLC) layer (i.e., higher layers) via logical channels. Based on the type of information transmitted, logical channels are essentially divided into control channels, which transmit information for the control plane, and traffic channels, which transmit information for the user plane.

[0089] The second layer, the RLC layer, is used to control the data size appropriate for data received from higher layers and transmitted through lower layers in the radio department by segmenting and concatenating data. Furthermore, to guarantee the 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 retransmissions via the Automatic Repeat Request (ARQ) function to ensure reliable data transmission.

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

[0091] The Radio Resource Control (RRC) layer at the highest level of Layer 3 is defined only in the control plane and is responsible for controlling logical, transport, and physical channels related to the configuration, reconfiguration, and release of Radio Bearers (RBs). Here, RB refers to the service provided by Layer 2 for transmitting data between the UE and the E-UTRAN.

[0092] If an RRC connection exists between the UE's RRC layer and the RRC layer of the wireless network, the UE is in the RRC_CONNECTED state. If no connection exists, the UE is in the RRC_IDLE state.

[0093] The following describes the UE's RRC state and RRC connection method. The RRC state refers to whether the UE's RRC layer is logically connected to the E-UTRAN's RRC layer. If the UE's RRC layer is logically connected to the E-UTRAN's RRC layer, the RRC state is called the RRC_CONNECTED state. If the UE's RRC layer is not logically connected to the E-UTRAN's RRC layer, the RRC state is called the RRC_IDLE state. Because a UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can detect the UE's presence in the cell cell and thus effectively control the UE. Conversely, if the UE is in the RRC_IDLE state, the E-UTRAN cannot detect the UE's presence and manage the core network in the Tracking Area (TA) cell (i.e., a region cell larger than the cell). In other words, the presence of a UE in only the RRC_IDLE state is checked in a region cell larger than the cell. In such a case, the UE needs to transition to the RRC_CONNECTED state to provide public mobile communication services, such as voice or data. Each Tracking Area Identity (TAI) is classified. The UE can configure the TAI using the Tracking Area Code (TAC) (i.e., information broadcast by the cell).

[0094] When a user first powers on 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. Afterward, the UE remains in the RRC_IDLE state. A UE in the RRC_IDLE state may (re)select a cell if necessary and check system information or paging information. This process is called camping. When a UE in the RRC_IDLE state needs to establish an RRC connection, the UE establishes an RRC connection with the E-UTRAN's RRC layer through the RRC connection procedure and transitions to the RRC_CONNECTED state. The situations in which a UE in the RRC_IDLE state needs to establish an RRC connection include several scenarios. These scenarios may include, for example, situations where UL data needs to be sent due to reasons such as a user making a call attempt, and situations where a response message needs to be sent in response to a paging message received from the E-UTRAN.

[0095] The Non-Access Layer (NAS) layer, located above the RRC layer, performs functions such as session management and mobility management.

[0096] The following is a detailed description Figure 3 The NAS layer is shown.

[0097] Evolved Session Management (ESM), belonging to the NAS layer, performs functions such as managing default bearers and dedicated bearers, and is responsible for controlling the PS services required by the UE to use from the network. 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 access network. Here, the network allocates an IP address available to the UE, enabling the UE to use the data services and QoS of the default bearer. LTE supports two types of bearers: bearers with Guaranteed Bit Rate (GBR) QoS characteristics that guarantee a specific bandwidth for data transmission and reception, and non-GBR bearers with QoS characteristics that provide optimal performance without guaranteeing bandwidth. Default bearers are assigned as non-GBR bearers, and dedicated bearers can be assigned as bearers with either GBR or non-GBR QoS characteristics.

[0098] In the network, the 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 Aggregated Maximum Bit Rate (AMBR).

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

[0100] Random access processing is used for UE 10 to obtain UL synchronization with the base station (i.e., eNodeB 20) or to be assigned UL radio resources.

[0101] UE 10 receives the root index and Physical Random Access Channel (PRACH) configuration index from eNodeB 20. Sixty-four candidate random access preambles, defined by the Zadoff-Chu (ZC) sequence, exist in each cell. The root index is a logical index used by the UE to generate these 64 candidate random access preambles.

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

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

[0104] Having received the random access preamble, eNodeB 20 sends a random access response (RAR) to UE 10. The random access response is detected in two steps. First, UE 10 detects the PDCCH masked with a random access RNTI (RA-RNTI). UE 10 receives the random access response within a Media Access Control (MAC) Protocol Data Unit (PDU) on the PDSCH indicated by the detected PDCCH.

[0105] Figure 6 The example illustrates connection processing in the Radio Resource Control (RRC) layer.

[0106] Figure 6 The RRC state depends on the presence or absence of an RRC connection. The RRC state indicates whether the entity of the RRC layer of UE 10 is logically connected to the entity of the RRC layer of eNodeB 20, and if so, the RRC state is called the RRC connected state; otherwise, the RRC state is called the RRC idle state.

[0107] 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 thus effectively control UE 10. Conversely, in the idle state, UE 10 is not aware of the eNodeB 20 and is managed by the core network on a tracking area larger than the cell. This tracking area is a set of cells. That is, the presence of UE 10 in the idle state is only known on a larger area basis, and the UE should switch to the connected state to receive typical mobile communication services such as voice or data services.

[0108] When a user connects to UE 10, UE 10 searches for a suitable cell and remains in an idle state within that cell. When needed, UE 10 establishes an RRC connection with eNodeB 20 at the RRC layer through the RRC connection procedure and transitions to an RRC connected state.

[0109] There are many situations in which a UE in an idle state needs to establish an RRC connection, such as when a user attempts to make a call, when uplink data transmission is required, or when a message is sent in response to a paging message received from EUTRAN.

[0110] To enable an idle UE 10 to establish an RRC connection with eNodeB 20, UE 10 needs to perform the RRC connection procedure described above. The RRC connection procedure typically involves the processing of UE 10 sending an RRC connection request message to eNodeB 20, the processing of eNodeB 20 sending an RRC connection establishment message to UE 10, and the processing of UE 10 sending an RRC connection establishment complete message to eNodeB 20. (Refer to...) Figure 6 These processes will be described in more detail.

[0111] 1) When an idle UE 10 attempts to establish an RRC connection, for example, to attempt to make a call or send data or to respond to a paging from eNodeB 20, it sends an RRC connection request message to eNodeB 20.

[0112] 2) When an RRC connection message is received from UE 10, if there are sufficient radio resources, eNodeB 20 accepts the RRC connection request from UE 10 and sends a response message, i.e., an RRC connection establishment message, to UE 10.

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

[0114] Figure 7 An exemplary Tracking Area Update (TAU) procedure is shown. This procedure may include the following steps:

[0115] 1) In idle mode, user equipment (UE) 100 moves to the coverage area of ​​target eNodeB 200b. Therefore, it is determined to initiate the Tracking Area Update (TAU) procedure.

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

[0117] 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 to be the responsible MME. The target eNodeB 200b transmits the TAU request message to the target MME 510b. During this process, it is assumed that the Serving Gateway (S-GW) 520 remains unchanged.

[0118] 4-5) Subsequently, the target MME 510b sends a UE context request message (e.g., ContextRequest) to the source MME 510a and receives a context response message (e.g., Context Response) from the source MME 510a to obtain information related to the PDN connection and EPS bearer information.

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

[0120] 7) After obtaining the context information, the target MME 510b sends a context acknowledgment message (e.g., Context Acknowledge) to the source MME 510a.

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

[0122] (9-11) Subsequently, the S-GW 520 sends a bearer modification request message to the PDN gateway (PDN-GW) 530 as needed. The 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 the S-GW 520.

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

[0124] 13) Then, the target MME 510b sends a location update request message (e.g., UpdateLocation Request) to the HSS 590.

[0125] 14-15) Subsequently, HSS 590 sends a location cancellation message (e.g., Cancel Location) to source MME 510a, and source MME 510a returns a location cancellation confirmation message (e.g., Cancel Location Ack) to HSS 590.

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

[0127] 17-18) Next, the target MME 510b sends a TAU Accept message (e.g., TAU Accept) to the UE 100 via the target eNodeB 200b, and the UE 100 sends a TAU Complete message (e.g., TAUComplete) to the target MME 510b as needed.

[0128] Tables 2 through 9 below show the message types used in each processing step.

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

[0130] [Table 2]

[0131]

[0132] The EPC update type information element shown in Table 2 above may contain the following bit fields.

[0133] [Table 3]

[0134]

[0135] Meanwhile, the aforementioned context request message may contain the information elements shown in Table 4 below.

[0136] [Table 4]

[0137]

[0138] Meanwhile, the context response message can contain the information elements shown in Table 5 below.

[0139] [Table 5]

[0140]

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

[0142] [Table 6]

[0143]

[0144] The bearer context information contained in the PDN connection information in the context response can include the information shown in Table 7 below.

[0145] [Table 7]

[0146]

[0147] The messages received by the AU can contain the information shown in Table 8 below.

[0148] [Table 8]

[0149]

[0150] 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, there is an extended T3412 value that allows TAUs to be performed at longer intervals. This extended T3412 value can be set by the MME or stored in the HSS 540 as user subscription information.

[0151] <Disclosure of this instruction manual>

[0152] Figure 8 This is a schematic flowchart illustrating a process according to an embodiment of this specification.

[0153] like Figure 8As shown, when the unavailability period ends and the discontinuous coverage maximum time offset timer expires, the user equipment (UE) may trigger the Tracking Area Update (TAU) procedure (S110).

[0154] If the UE contains unavailability information in the tracking area update request message, but does not contain the start of the unavailability period, then the UE can start the first timer (S120) when the TAU procedure is completed.

[0155] In addition, after the unavailability period ends, the UE can activate the access stratum (AS) (S130).

[0156] If the first timer does not run, and the UE contains unavailability information in the TAU request message but not the start information of the unavailability period, then when the TAU process is completed, the UE can release the Non-Access Stratum (NAS) signaling connection locally and enter the registered state.

[0157] The TAU request message may contain unavailability information, but not information about the start of the unavailability period.

[0158] The UE may also perform the following steps: send the TAU request message, which contains unavailability information but does not contain information on the start of the unavailability period.

[0159] If the maximum time offset value of discontinuous coverage has been stored, and the last received Tracking Area Update Accept message contains an end of unavailabilityreport bit, and this bit is set to "UE needs to report end of unavailability period", then if the UE leaves the coverage area due to discontinuous coverage and then returns to the coverage area, the UE can set a random value less than or equal to the stored maximum time offset value of discontinuous coverage for the PLMN and its satellite E-UTRAN access, and start the corresponding timer.

[0160] <Summary of Examples in this Manual>

[0161] I. Support for enhanced discontinuous coverage

[0162] When a user equipment (UE) and the network support enhanced discontinuous coverage, and the UE completes registration via satellite E-UTRAN access, the UE can provide unavailability information to the network during the Tracking Area Update (TAU) process. This unavailability information may include (if known) the duration of the unavailability period and (if known) the start time of the unavailability period.

[0163] Support for enhanced discontinuous coverage can be negotiated during the Attach or TAU process. The Mobility Management Entity (MME) can take into account the duration of the unavailability period provided by the UE when determining the duration of the unavailability period. If the UE provides the start time of the unavailability period, the MME can also use this information to determine the start point of the unavailability period. The MME can send the duration of the unavailability period, the start time, or both to the UE in a TRACKING AREA UPDATE ACCEPT message or an ATTACH ACCEPT message.

[0164] If the UE provides unavailability information during the last TAU ​​procedure, the MME may consider the UE unreachable until the UE re-registers for normal service and does not provide unavailability information again. If the UE does not provide start information for the unavailability period, the MME may consider the time when it receives the TAU request message from the UE as the start time of the unavailability period.

[0165] The MME can determine the values ​​of the periodic TAU timer (T3412), extended idle mode DRX period parameters, and PSM mode setting parameters provided to the UE based on available information such as the maximum time offset of discontinuous coverage, the duration of the unavailable period, and the start time.

[0166] After the TAU procedure, in which the UE provides unavailability information but does not provide the start time of the unavailability period, is completed, the MME can release the NAS signaling connection.

[0167] If the UE has stored the maximum time offset value for discontinuous coverage, it can set a random maximum time offset value for discontinuous coverage that is less than or equal to the stored value for the current PLMN and its satellite E-UTRAN access, and determine a time point that is the UE's expected time of losing satellite coverage minus the maximum time offset value. Subsequently, the UE can send a TAU request message to the MME to indicate the start of unavailability.

[0168] If the UE has stored the maximum time offset value for discontinuous coverage, and the "Unavailability End Report Bit" in the Unavailability Setting Information Element (IE) of the most recent TAU ​​Accept message is set to "UE needs to report the end of the unavailability period", then when the UE returns after leaving the coverage area due to discontinuous coverage, the UE can set a random offset value less than or equal to the stored value based on the PLMN and satellite E-UTRAN access combination, and start the corresponding timer.

[0169] During this timer's operation, the UE should not initiate any NAS signaling under the satellite E-UTRAN access and PLMN combination unless one of the following occurs: the UE receives a paging message, has pending emergency services, is establishing an emergency PDN connection, is performing an emergency service fallback procedure, enters a new TA, or is permitted to use abnormal data reporting and needs to send relevant user data. In such cases, the UE should stop the discontinuous coverage maximum time offset timer and initiate NAS signaling.

[0170] If the MME sets the unavailability end report bit to "Do not require UE to report the end of unavailability" in the unavailability settings IE, then when the UE returns to the TAI coverage area in the TAI list, the UE does not need to trigger the TAU procedure at the end of the unavailability period.

[0171] However, if the MME does not provide an unavailability setting IE, or sets the bit to "requires UE to report the end of unavailability", then the UE should trigger the TAU procedure when the unavailability period ends and the discontinuous coverage maximum time offset timer expires.

[0172] When an unavailability period is activated due to discontinuous coverage, all NAS timers, except for the following timers, should be stopped and related processes terminated:

[0173] T3412, T3324, T3346, T3396, T3444, T3445, T3447, T3448

[0174] Arbitrary backoff timers (T3245, T3247)

[0175] A timer (T) that controls the periodic search for HPLMN, EHPLMN (if an EHPLMN list exists), or a PLMN with higher priority.

[0176] A timer (TSENSE) controls the periodic search of the PLMN to meet the operator's signal level threshold.

[0177] Other timers: TD, TE, TH

[0178] and timer instances associated with entries in the "List of PLMNs Not Allowed to Operate at Current UE Location".

[0179] The UE can also reset the attach attempt counter, TAU attempt counter, and service request attempt counter, and disable the access stratum (AS).

[0180] When the UE provides unavailability information through the TAU procedure without providing the start time of the unavailability period, the UE can disable the access layer and enter the EMM-REGISTERED state after successfully completing the procedure.

[0181] Conversely, if the UE provides a start time for the unavailability period, the UE can only disable the access layer and enter the EMM-REGISTERED state after the unavailability period begins.

[0182] When the UE exits the unavailable period, if the AS layer is currently disabled, the UE can activate the AS layer and execute the TAU procedure.

[0183] II. Release of NAS signaling connection

[0184] The signaling process for releasing a NAS signaling connection is initiated by the network.

[0185] In S1 mode, when the RRC connection is released, the UE can enter EMM-IDLE mode and see that the NAS signaling connection has been released.

[0186] If the UE is configured in eCall-only mode:

[0187] If the released NAS signaling connection was established for eCall via IMS, the UE can start timer T3444;

[0188] If the released NAS signaling connection was established by initiating a call to a non-urgent MSISDN or URI specified by the HPLMMN for testing or terminal reset services, the UE may start timer T3445.

[0189] When the NAS signaling connection is released, the UE may start the SGC timer (T3447) based on the available service gap time value under the following conditions:

[0190] The UE supports the SGC function, and the service gap timer value can be used by the UE and is not 0;

[0191] The released NAS signaling connection was established for the motion initiation request to transmit uplink data.

[0192] If the UE receives "delay waiting time" information from the lower layer without performing an attachment, tracking area update, or service request process, the UE can ignore the "delay waiting time".

[0193] To allow the network to release the NAS signaling connection, the UE can start timer T3440 in the following situations:

[0194] a) When the UE receives an EMM cause value of #11, #12, #13, #14 (not applicable to the service request process), #15, #25, #31, #35, #42 or #78;

[0195] a1) When the UE receives the SERVICE REJECT message;

[0196] b) In the following cases:

[0197] The UE receives a Tracking Area Update Acceptance Message that does not contain a UE Radio Capability ID Deletion Indication IE;

[0198] The UE did not set the "active" flag in the TRACKING AREA UPDATE REQUEST message;

[0199] The UE did not set the "signalling active" flag in the TRACKING AREA UPDATE REQUEST message;

[0200] The TAU or joint TAU ​​procedure is initiated in EMM-IDLE mode, or the UE sets the request type to "NAS signaling connection release" in the UE request type IE in the TAU request, and the "NAS signaling connection release" flag is set to supported in the EPS network function support IE of the TAU acceptance message.

[0201] No user plane radio bearer was established;

[0202] b1) If the UE includes unavailability information in the TAU request but does not include the start information of the unavailability period, then when the TAU process is completed;

[0203] c) The UE receives a DETACH ACCEPT message and sets the separation type to "IMSI separation" in the DETACH REQUEST message, while the user plane radio bearer is not established;

[0204] d) The UE receives the TRACKING AREA UPDATE REJECT message and meets any of the following conditions:

[0205] The EMM cause value is #9 or #10, and the UE has no pending CS fallback emergency call, CS fallback call, 1xCS fallback emergency call or 1xCS fallback call;

[0206] The reason value is #40, and the TAU process was not triggered due to receiving a CS fallback or 1xCS fallback paging, and there are no such calls pending.

[0207] e) The UE receives a service rejection message for a service request, a control plane service request, or an extended service request set to "S1 bearer packet service", with an EMM reason value of #9, #10, or #40;

[0208] f) The UE receives an EMM reason value of #3, #6, #7 or #8, or receives an authentication rejection message;

[0209] g) The UE receives a service denial message with an EMM reason value of #39, and it initiates an extended service request in EMM-IDLE mode without establishing a user plane radio bearer;

[0210] h) The UE receives a service rejection, service acceptance, access acceptance, or TAU acceptance message containing a control plane data backoff timer;

[0211] i) The UE receives an EMM cause value of #22 containing the value T3346, and T3346 is not 0 and is not disabled;

[0212] j) The UE receives the service acceptance message and sets the type to "NAS signaling connection release" or "paging rejection" in the UE request type IE of the extended service request or control plane service request;

[0213] k) The UE receives a service acceptance message and sets the service type to "mobility termination request" in the control plane service request, with the active flag set to 0. No user plane radio bearer is established, and the service request is initiated in EMM-IDLE.

[0214] l) The UE receives the DETACH ACCEPT message and sets the separation type to "EPS separation" or "joint EPS / IMSI separation" in the DETACH REQUEST;

[0215] m) When the UE receives a DETACH REQUEST message with the separation type "reattachment required", it is after the DETACH process is completed.

[0216] When the T3440 timer expires:

[0217] In cases a, a1, b, b1, c, f, h, i, j, l, the UE should release the NAS signaling connection locally.

[0218] In scenarios d and e, the UE can locally release the NAS signaling connection and initiate the attach procedure;

[0219] In scenario m, the UE should locally release the NAS signaling connection and initiate the attach procedure.

[0220] In the following cases:

[0221] In scenarios b, c, and g, if the lower layer indicates that a user plane radio bearer has been established, the UE can stop T3440 and send uplink signaling or user data through the existing NAS connection. If a PDN connection is established for an emergency call or emergency bearer service, the UE should send signaling through the existing NAS connection.

[0222] In cases b, c, g, and j, if a DETACH REQUEST is received, the UE should stop T3440 and respond to the DETACH initiated by the network.

[0223] In scenarios b, j, and k, if the upper layer requests to send NAS signaling unrelated to the emergency bearer, the UE should wait for T3440 to time out or be stopped before releasing the connection locally; if the upper layer requests to establish an emergency call or PDN connection, the UE should stop T3440 and release the NAS connection locally.

[0224] In an optional implementation, when an ESM data transmission message is received, the UE can reset and restart the T3440;

[0225] When a downlink NAS transmission or downlink general NAS transmission message is received, if the UE is in the EMM-REGISTERED state without a PDN connection, T3440 should be stopped and uplink signaling should be sent using the existing NAS connection.

[0226] When receiving ACTIVATE / MODIFY / DEACTIVATE EPS BEARER CONTEXT requests, downlink NAS transmissions, or general NAS transmissions, if control plane CIoT optimization is used, T3440 should be stopped and signaling should be sent.

[0227] If the current TAI is detected to be not in the TAI list, T3440 should be stopped when TAU or combined TAU begins.

[0228] In case c:

[0229] If the upper layer requests to send NAS signaling unrelated to the emergency bearer, the UE should wait for T3440 to time out or stop before releasing the connection;

[0230] If the upper layer requests to establish a PDN connection for emergency bearer services, the T3440 should be stopped and the NAS connection released.

[0231] In cases d and e:

[0232] If the lower layer indicates that the RRC connection has been released, the UE should stop T3440 and execute a new access procedure;

[0233] If the upper layer requests the establishment of an emergency bearer PDN connection, the UE can stop T3440 and release the connection.

[0234] In cases a and f:

[0235] If the upper layer requests the establishment of an emergency bearer PDN connection, the T3440 should be stopped and the NAS connection released.

[0236] In case g:

[0237] If the upper layer requests to send NAS signaling unrelated to the emergency bearer, the UE can wait for T3440 to time out or stop before releasing the connection;

[0238] If the upper layer requests to establish an emergency CS call or PDN connection, the T3440 should be stopped and the connection released.

[0239] In case h:

[0240] If the lower layer indicates that the user plane radio bearer has been established, or the upper layer requests NAS signaling to send non-ESM data transmission, the UE can stop T3440;

[0241] Otherwise, ESM data transmission messages must not be sent before T3440 expires or is terminated.

[0242] In EMM-CONNECTED mode, if the UE enters the EMM-SERVICE-REQUEST-INITIATED state after receiving the CS SERVICE NOTIFICATION message, T3440 should be stopped.

[0243] In S101 mode, if the cdma2000® HRPD radio access connection is released, the UE should enter EMM-IDLE mode and recognize that the S101 mode NAS signaling connection has been released.

[0244] When the UE enters the EMM-DEREGISTERED.PLMN-SEARCH or EMM-REGISTERED state and the T3440 is not running, the UE can locally release the NAS signaling connection.

[0245] If T3440 is not running, and the UE includes unavailability information in the TAU request but does not include the start time of the unavailability period, then when the TAU process is completed, the UE can locally release the NAS signaling connection and enter the EMM-REGISTERED.NO-CELL-AVAILABLE state.

[0246] Figure 9 This is a block diagram illustrating the configuration of a terminal according to an embodiment of the present disclosure.

[0247] UE 100 includes a memory 1010, a processor 1020, a transceiver 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 user identification module (SIM) card, and one or more antennas.

[0248] Processor 1020 may be configured to implement the functions, processes, and / or methods described herein. Layers of the wireless interface protocol may be implemented in processor 1020. Processor 1020 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. Processor 1020 may be an application processor (AP). 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 processor 1020 may be the SNAPDRAGON™ series processors manufactured by Qualcomm, the EXYNOS™ series processors manufactured by Samsung, the A-series processors manufactured by Apple, the HELIO™ series processors manufactured by MediaTek, the ATOM™ series processors manufactured by Intel, or corresponding next-generation processors.

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

[0250] Memory 1010 is operatively coupled to processor 1020 and stores various information for operating processor 1010. Memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and / or other storage devices. When embodiments are implemented in software, the techniques described herein can be implemented in modules (e.g., processes, functions, etc.) that perform the functions described herein. Modules may be stored in memory 1010 and executed by processor 1020. Memory 1010 may be implemented within processor 1020. Alternatively, memory 1010 may be implemented outside of processor 1020 and communicatively coupled to processor 1020 by various means known in the art.

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

[0252] Speaker 1042 outputs sound-related results processed by processor 1020. Microphone 1052 receives sound-related input used by processor 1020.

[0253] Users input command information, such as phone numbers, for example, by pressing (or touching) a button on input unit 1053 or by activating voice using microphone 1052. Processor 1020 receives these command information and performs appropriate functions, such as dialing a phone number. Operational data can be retrieved from SIM card or memory 1010. Furthermore, processor 1020 can display command information or drive information on display 1041 for user identification and convenience.

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

[0255] For reference Figure 10As can be seen, the processor 1020 implementing this 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. Furthermore, although not shown, the processor 1020 may include more circuits. Each circuit may include multiple transceivers.

[0256] The first circuit 1020-1 can trigger the Tracking Area Update (TAU) process of the user equipment (UE) when the unavailability period ends and the discontinuous coverage maximum time offset timer expires.

[0257] The second circuit 1020-2 can start the first timer when the UE contains unavailability information in the tracking area update request message, but does not contain the start of the unavailability period, and the tracking area update process has been completed.

[0258] The third circuit 1020-3 can activate the access layer (AS) after the UE has exited the unavailable period.

[0259] 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), CPU (Central Processing Unit), or GPU (Graphics Processing Unit).

[0260] The processor can be installed on the UE.

[0261] While preferred embodiments have been described by way of example, the disclosure of this specification is not limited to these specific embodiments, but can be modified, altered or improved in various forms within the spirit and scope of this specification and the claims.

[0262] 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 described steps. Some steps may occur in a different order than the steps described above or simultaneously. Furthermore, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and may include other steps, or one or more steps in the flowchart may be deleted without affecting the scope of the claims.

[0263] The claims described herein can be combined in various ways. For example, the technical features of the method claims in this specification can be combined to implement an apparatus, and the technical features of the apparatus claims in this specification can be combined to implement an apparatus. Furthermore, the technical features of the method claims and the apparatus claims can be combined to implement an apparatus, and the technical features of the method claims and the apparatus claims can be combined to implement an apparatus.

Claims

1. A method for operating a user equipment, comprising: Receive unavailability settings, the unavailability settings including an unavailability period end report bit, the unavailability period end report bit being set to "user equipment needs to report the end of the unavailability period" or "user equipment does not need to report the end of the unavailability period"; When the unavailability period ends and the unavailability period end report bit is set to "User Equipment needs to report the end of unavailability period", the tracking area update process is triggered, wherein the discontinuous coverage maximum time offset timer has expired; If the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then timer T3440 is started when the tracking area update process is completed; If the T3440 timer does not run when the user equipment enters the first state of EMM-DEREGISTERED and PLMN-SEARCH or the second state of EMM-REGISTERED and PLMN-SEARCH, then the non-access stratum signaling connection is locally released; and After the unavailability period ends, the access layer is activated.

2. The method of operating the user equipment according to claim 1 further includes: If the T3440 timer is not running and if the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, the non-access stratum signaling connection is locally released when the tracking area update process is completed.

3. The method for operating the user equipment according to claim 2 further includes: If the T3440 timer is not running and if the tracking area update request message contains the unavailability information, but if the tracking area update request message does not contain the start information of the unavailability period, then the system enters the registration state when the tracking area update process is completed.

4. The method of operating the user equipment according to claim 1, further comprising: Send a tracking area update request message that contains information about unavailability but does not contain information about the start of the unavailability period.

5. A user equipment, comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and used to store instructions. When the instruction is executed by the at least one processor, the following operations are performed: Receive unavailability settings, the unavailability settings including an unavailability period end report bit, the unavailability period end report bit being set to "user equipment needs to report the end of the unavailability period" or "user equipment does not need to report the end of the unavailability period"; When the unavailability period ends and the unavailability period end report bit is set to "User Equipment needs to report the end of unavailability period", the tracking area update process is triggered, wherein the discontinuous coverage maximum time offset timer has expired; If the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then timer T3440 is started when the tracking area update process is completed. If the T3440 timer does not run when the user equipment enters the first state of EMM-DEREGISTERED and PLMN-SEARCH or the second state of EMM-REGISTERED and PLMN-SEARCH, then the non-access stratum signaling connection is locally released; and After the unavailability period ends, the access layer is activated.

6. The user equipment according to claim 5, wherein, The operation also includes: If the T3440 timer is not running and if the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then the non-access stratum signaling connection is locally released when the tracking area update process is completed.

7. The user equipment according to claim 5, wherein, The operation also includes: If the T3440 timer is not running and if the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then the system enters the registration state when the tracking area update process is completed.

8. The user equipment according to claim 5, wherein, The operation also includes: Send a tracking area update request message that contains information about unavailability but does not contain information about the start of the unavailability period.

9. A semiconductor chipset, comprising: At least one processor; as well as At least one memory, capable of storing instructions and electrically connected to the at least one processor, When the instruction is executed by the at least one processor, the following operations are performed: Receive unavailability settings, the unavailability settings including an unavailability period end report bit, the unavailability period end report bit being set to "user equipment needs to report the end of the unavailability period" or "user equipment does not need to report the end of the unavailability period"; When the unavailability period ends and the unavailability period end report bit is set to "User Equipment needs to report the end of unavailability period", the tracking area update process is triggered, wherein the discontinuous coverage maximum time offset timer has expired; If the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then timer T3440 is started when the tracking area update process is completed; If the T3440 timer does not run when the user equipment enters the first state of EMM-DEREGISTERED and PLMN-SEARCH or the second state of EMM-REGISTERED and PLMN-SEARCH, then the non-access stratum signaling connection is locally released; and After the unavailability period ends, the access layer is activated.

10. The semiconductor chipset according to claim 9, wherein, The operation also includes: If the T3440 timer is not running and the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, the non-access stratum signaling connection is locally released when the tracking area update process is completed.

11. The semiconductor chipset according to claim 9, wherein, The operation also includes: If the T3440 timer is not running and if the tracking area update request message contains unavailability information, but if the tracking area update request message does not contain start information for the unavailability period, then the system enters the registration state when the tracking area update process is completed.

12. The semiconductor chipset according to claim 9, wherein, The operation also includes: Send a tracking area update request message that contains information about unavailability but does not contain information about the start of the unavailability period.

Images