Method for processing forbidden tais list information element and user equipment

Abstract

The present disclosure provides methods and user equipment handling forbidden TAI list information elements. Examples are described regarding user equipment (UE) handling of forbidden tracking area identifier (TAI) list information elements (IEs) in an evolved packet system (EPS) service accept message in mobile communications. A user equipment (UE) sends a control plane service request message to an EPS network node of a wireless network. In response, the UE receives a service accept message from the EPS network node. The service accept message includes either or both of: (i) a list of "Forbidden Tracking Areas for Roaming" information elements (IEs) containing one or more forbidden TAIs; and (ii) a list of "Forbidden Tracking Areas for Area Provision of Service" IEs containing one or more forbidden TAIs.

Description

[0001] Cross-references to related applications

[0002] This invention claims priority to U.S. Provisional Patent Application No. 63 / 345,451, filed May 25, 2022, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This invention relates generally to mobile communications, and more specifically, to an information element (IE) in a user equipment (UE) processing an Evolved Packet System (EPS) Service Acceptance (SERVICEACCEPT) message in mobile communications, which is a list of tracking area identifiers (TAIs). Background Technology

[0004] Unless otherwise stated in this invention, the solutions described in this section are not prior art to the claims listed below, and are not acknowledged as prior art by virtue of their inclusion in this section.

[0005] In wireless communications such as those under the 3rd Generation Partnership Project (3GPP) standards, including 5th Generation (5G) New Radio (NR) and 4th Generation (4G) EPS, the service request process can still be considered complete (e.g., after a Security Mode Command message or an instruction from a lower layer regarding the establishment of a user plane radio bearer) even if the service request can be successfully completed. In Evolved Universal Mobile Telecommunications System (UMTS) Radio Access Network (E-UTRAN) access, the network may need to provide the UE with a list of prohibited TAIs even if the service request can be successfully completed. This can happen if the cell where the UE is camped is broadcasting multiple tracking area codes (TACs) for the public land mobile network (PLMN) to select / register, and the network detects that some TAIs (each TAI includes the corresponding TAC plus the corresponding PLMN identifier (ID)) are prohibited for the UE (e.g., for roaming or for providing service to a specific area), while other broadcast TAIs are not prohibited.

[0006] Regarding the service request procedure, the UE needs to invoke the service request procedure when one or more conditions are met. One condition is that, in EPS Mobility Management (EMM)-IDLE mode, the UE receives a paging request from the network using a Serving Temporary Mobility Subscriber Identity (S-TMSI) with a core network (CN) domain indicator set to "PS" (Packet Switched). As an implementation option, a multi-Universal Subscriber Identity Module (MUSIM) UE is allowed to not respond to the paging based on information available in the paging message (e.g., voice service indication). Another condition is that, in EMM-IDLE mode, the UE has user data to be sent. Yet another condition is that, in EMM-IDLE mode, the UE has pending uplink signaling. However, given the above situations, one issue is that, when the UE must be provided with a blocked TAI list IE, the network should have a path to provide the blocked TAI list IE to the UE when the service request procedure completes successfully. Another issue is that when a prohibited TAI list IE is received in a Service Acceptance (SERVICE ACCEPT) message from the network, the UE may lack guidelines for processing or responding to the prohibited TAI list IE. Therefore, a solution is needed for the UE to handle prohibited TAI list IEs in EPSSERVICE ACCEPT messages during mobile communications. Summary of the Invention

[0007] The following overview is illustrative only and is not intended to be limiting in any way. That is, it is provided to introduce the concept, key points, benefits, and advantages of the novel and non-obvious techniques described in this invention. Selected implementations are further described in the detailed description below. Therefore, the following overview is not intended to identify essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0008] One object of the present invention is to provide solutions, concepts, designs, systems, methods, and apparatus related to the blocking TAI list IE in EPS SERVICE ACCEPT messages during mobile communications by a UE. It is believed that by implementing one or more of the proposed solutions described in this invention, the aforementioned problems can be avoided or mitigated.

[0009] In one aspect, the method may include a processor of an apparatus (e.g., a UE) sending a Control Plane Service Request (CPS) message to an EPS network node of a wireless network. Responsibly, the method may also include the processor receiving a Service Accept message from the EPS network node. The Service Accept message may include any one or both of the following: (i) a list of "No Tracking Areas for Roaming" IEs containing one or more prohibited TAIs; and (ii) a list of "No Tracking Areas for Area Services" IEs containing one or more prohibited TAIs.

[0010] In another aspect, a method may include a processor of an apparatus (e.g., a UE) sending a CONTROL PLANE SERVICE REQUEST message to an EPS network node of a wireless network. Responsibly, the method may also include the processor receiving a message from the EPS network node during a service process. This message may include any one or both of the following: (i) a list of "No Tracking Areas for Roaming"; and (ii) a list of "No Tracking Areas for Service in Areas".

[0011] In another aspect, an apparatus may include a transceiver and a processor coupled to the transceiver. The transceiver may be configured for wireless communication. The processor may send a CONTROL PLANESERVICE REQUEST message to an EPS network node of a wireless network via the transceiver. Responsibly, in response to the sending, the processor may receive a SERVICE ACCEPT message from the EPS network node via the transceiver. The SERVICE ACCEPT message may include any one or both of the following: (i) one or more prohibited TAIs in the "Do Not Tracking Zones for Roaming" IE list; and (ii) one or more prohibited TAIs in the "Do Not Tracking Zones for Area Services" IE list.

[0012] In another aspect, an apparatus may include a transceiver and a processor coupled to the transceiver. The transceiver may be configured to perform wireless communication. The processor may send a CONTROLPLANE SERVICE REQUEST message via the transceiver to an EPS network node of a wireless network. Responsively, the processor may receive a message via the transceiver from the EPS network node during a service process. The message may include any one or both of the following: (i) a list of "no-tracking zones for roaming"; and (ii) a list of "no-tracking zones for providing service to a zone".

[0013] It is worth noting that while the description provided in this invention may be within the context of certain radio access technologies, networks, and network topologies (e.g., 5th Generation System (5GS) and 4G EPS mobile networks), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of wireless and wired communication technologies, networks, and network topologies (e.g., but not limited to Ethernet, Universal Terrestrial Radio Access Network (UTRAN), E-UTRAN, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS) / Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network (GERAN), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Industrial IoT (IoT), Narrow Band Internet of Things (NB-IoT), and any networking technologies developed in the future). Therefore, the scope of this invention is not limited to the examples described herein. Attached Figure Description

[0014] The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this invention. The drawings illustrate implementations of the invention and, together with the description, serve to explain the principles of the invention. It will be understood that the drawings are not necessarily to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concept of the invention.

[0015] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes according to the present invention can be implemented.

[0016] Figure 2 This is a block diagram of an example communication system according to an implementation of the present invention.

[0017] Figure 3 This is a flowchart of an example process according to an implementation of the present invention.

[0018] Figure 4This is a flowchart of another example process according to an implementation of the present invention. Detailed Implementation

[0019] This invention discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. The invention can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of the invention thorough and complete, and to fully convey the scope of the invention to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0020] Overview

[0021] Implementations of the present invention relate to various techniques, methods, schemes, and / or solutions related to the prohibited TAI list IE in the EPS SERVICE ACCEPT message during mobile communication by the UE. According to the present invention, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of these possible solutions may be implemented in one combination or another.

[0022] Figure 1 An example network environment 100 is shown in which various solutions and schemes according to the present invention can be implemented. Figures 2 to 4 Examples of implementations of various proposed solutions in the network environment 100 according to the present invention are illustrated. (Refer to...) Figures 1 to 4 The following descriptions of the various proposed solutions are provided.

[0023] Reference Figure 1Network environment 100 may include UE 110 and wireless network 120, which may include 5GS (and optionally, EPS). Depending on channel conditions, availability, and / or other factors, UE 110 may wirelessly communicate with wireless network 120 via one or more terrestrial network nodes (e.g., base stations such as eNB, gNB, and / or transmission / reception point (TRP)) and / or one or more non-terrestrial network nodes (e.g., satellite). For simplicity and without limiting the scope of the invention, UE 110 may be associated with or communicate with cell 130 corresponding to terrestrial network node 125 (e.g., gNB, eNB, or TRP) and / or non-terrestrial network node 128 (e.g., satellite) of wireless network 120. In network environment 100, UE 110 and wireless network 120 may implement various schemes according to the present invention relating to the prohibited TAI list IE in the EPS SERVICE ACCEPT message during UE processing of mobile communications, as described below. It is worth noting that although the various proposed solutions may be described individually or separately below, in actual implementation, each of the proposed solutions may be used individually or separately. Optionally, some or all of the proposed solutions may be used in combination.

[0024] According to the first proposed embodiment of the invention, the wireless network 120 may include one or more lists in a message other than a service accept / reject message sent to and received by the UE 110 during a service process (e.g., in a security mode command message). The one or more lists may include, for example, a "No Tracking Areas for Roaming" list and / or a "No Tracking Areas for Service in Areas" list. In the proposed embodiment, in a message other than a service accept / reject message, the UE 110 receives one or more prohibited TAIs for the "No Tracking Areas for Roaming" list in that message during a service process (e.g., in a security mode command message), and if the UE 110 is operating in satellite E-UTRAN access, it may store one or more TAIs included in that message in the "No Tracking Areas for Roaming" list if they have not already been stored. Furthermore, the UE 110 may remove one or more TAIs from the stored TAI list (if it exists). Under the proposed scheme, if UE 110 receives one or more prohibited TAIs for the "Prohibited Tracking Areas for Service to Areas" list in a message other than the SERVICE ACCEPT / REJECT message during a service procedure (e.g., in a SECURITY MODE COMMAND message), and UE 110 is operating in satellite E-UTRAN access, then UE 110 can store one or more TAIs included in the message into the "Prohibited Tracking Areas for Service to Areas" list if they have not already been stored. Furthermore, UE 110 can remove one or more TAIs from the stored TAI list (if it exists).

[0025] Under the second proposed embodiment of the invention, UE 110 may use EPS services optimized with control plane Cellular Internet of Things (CIoT) EPS. For example, upon receiving a control plane service request (CONTROL PLANESERVICE REQUEST) message with a control plane service type indicating "mobility termination request," after completing the EMM common procedures, the Mobility Management Entity (MME) of the wireless network 120 may send a SERVICE ACCEPT message if at least one of a plurality of conditions is met. The first condition may be that the MME needs to perform EPS bearer context state synchronization for the following: (i) the EPS bearer context associated with the control plane-only indication; or (ii) the EPS bearer context indication is not associated with the control plane-only when there is no downlink user data to be transmitted via the user plane and UE 110 does not set the "Active" flag in the control plane service type IE to 1. The second condition may be that the control plane data backoff time for UE 110 is stored in the MME, and the MME decides to deactivate congestion control in order to transmit user data via the control plane. The third condition could be that the MME needs to provide the UE 110 with a list of "No Tracking Areas for Roaming" IEs that contain one or more prohibited TAIs, or a list of "No Tracking Areas for Service in the Area" IEs that contain one or more prohibited TAIs, or a list of both IEs that contain one or more prohibited TAIs.

[0026] Under the proposed second scheme, the MME can perform one or more additional operations. For example, the MME can initiate the transmission of user data via control plane procedures or any other NAS signaling procedures. Optionally or additionally, if UE 110 supports and the wireless network 120 requires, the MME can initiate the establishment of one or more user plane radio bearers. Optionally or additionally, in the presence of pending downlink signaling, the MME can send NAS signaling messages to UE 110 that are unrelated to EMM common procedures.

[0027] Under the third proposed embodiment of the invention, upon receiving a CONTROL PLANE SERVICE REQUEST message with a control plane service type indicating a "mobility origination request," and after completing EMM common procedures (if any), if the MME needs to provide the UE 110 with a list of "Do Not Track For Roaming" IEs containing one or more prohibited TAIs, or a list of "Do Not Track For Areas" IEs containing one or more prohibited TAIs, or a list of both IEs containing one or more prohibited TAIs, or if the MME needs to perform EPS bearer context state synchronization, the MME may send a SERVICE ACCEPT message. For example, the MME may send a SERVICE ACCEPT message for an EPS bearer context associated only with a control plane indication. Optionally, when there is no downlink user data to be transmitted via the user plane and the UE 110 does not set the "active" flag in the control plane service type IE to 1, the MME may only send a SERVICE ACCEPT message for an EPS bearer context not associated with the control plane.

[0028] Under the third proposed scheme, the MME can perform one or more additional operations. For example, the MME can initiate the release of the NAS signaling connection upon receiving an indication from the EPS Session Management (ESM) layer, unless the MME has pending additional downlink user data or signaling. Optionally or additionally, if there is downlink user data to be transmitted via the user plane or the UE 110 has set the "Active" flag in the control plane service type IE to 1, the MME can initiate the establishment of one or more user plane radio bearers. Optionally or additionally, if downlink user data is to be transmitted via the control plane, the MME can send an ESM data transfer message to the UE 110. Optionally or additionally, if downlink signaling is pending, the MME can send a NAS signaling message to the UE 110 that is unrelated to the EMM common procedures. Optionally or additionally, if the NAS security mode control procedure is not initiated, and if the MME does not send the SERVICE ACCEPT message as described above to perform EPS bearer context state synchronization, and if the MME does not initiate any of the procedures described above, the MME may send the SERVICE ACCEPT message to complete the service request procedure. It is worth noting that if the MME decides to activate congestion control for transmitting user data via the control plane, the MME may initiate the establishment of one or more user plane radio bearers.

[0029] According to the fourth proposed embodiment of the invention, upon receiving a Control Plane Service Request (CONTROLPLANE SERVICE REQUEST) message with a Control Plane Service Type indicating "Mobile Origin Request" and an "Active" flag set to 1 in the Control Plane Service Type IE, if the MME accepts the request, the MME may initiate the establishment of all active EPS bearer contexts for the SGi Packet Data Network (PDN) connection established without a control plane-only indication. Alternatively, upon receiving a CONTROL PLANE SERVICE REQUEST message with a Control Plane Service Type indicating "Mobile Origin Request" and an "Active" flag set to 1 in the Control Plane Service Type IE, if the MME does not accept the request, the MME may send a SERVICE ACCEPT message to complete the service request process. It is noteworthy that, in deciding whether to accept a request to establish one or more user plane bearers, in addition to the UE 110's local policies and preferred CIoT network behavior, the MME may also consider the maximum number of user plane radio bearers supported by the UE 110. If the MME accepts the request, all SGi PDN connections can be considered established without a control plane-only indication. It is also worth noting that a UE in NB-S1 mode can support up to two user plane radio bearers.

[0030] Under the fifth proposed embodiment of the invention, upon receiving a CONTROL PLANE SERVICE REQUEST message with a control plane service type indicating a "mobility origination request" and without an ESM message container IE, the MME can continue in some manner after completing the EMM common procedures (if any). For example, if the MME needs to perform EPS bearer context state synchronization for an EPS bearer context associated with a control plane-only indication or for an EPS bearer context not associated with a control plane-only indication, without downlink user data to be transmitted via the user plane, the MME can send a SERVICE ACCEPT message.

[0031] Under the fifth recommended scheme, the MME can perform one or more additional operations. For example, if downlink user data is to be transmitted via the user plane, the MME can initiate the establishment of the user plane radio bearer. Optionally or additionally, if downlink user data is to be transmitted via the control plane, the MME can send an ESM DATA TRANSPORT message to UE 110. Optionally or additionally, if downlink signaling is pending, the MME can send a NAS signaling message to UE 110 that is not related to the EMM common procedures. Optionally or additionally, if no NAS security mode control procedure is initiated, if the MME does not send the SERVICE ACCEPT message as described above to perform EPS bearer context state synchronization, and if the MME does not initiate any of the above procedures, the MME can send a SERVICE ACCEPT message to complete the service request procedure.

[0032] Under the sixth proposed embodiment of the invention, if the MUSIM UE (e.g., UE 110) does not include a paging restriction IE in the CONTROLPLANE SERVICE REQUEST message, the MME may delete any stored paging restrictions for that UE and stop restricting paging.

[0033] According to the seventh proposed embodiment of the invention, when a MUSIM UE (e.g., UE 110) sets the request type to "NAS signaling connection release" or "paging rejection" in the UE request type IE of the CONTROL PLANESERVICE REQUEST message, and if the UE requests a paging restriction by including a paging restriction IE, then if the MME accepts the paging restriction, the MME can include an EPS additional request result IE in the SERVICE ACCEPT message and set the paging restriction decision to "paging restriction accepted". The MME can also store the UE's paging restrictions and enforce these restrictions during paging. Optionally, if the MME rejects the paging restriction, the MME can include an EPS additional request result IE in the SERVICE ACCEPT message and set the paging restriction decision to "paging restriction rejected". The MME can also discard received paging restrictions. Furthermore, the MME can delete any stored paging restrictions for the UE and stop restricting paging. Additionally, the MME can initiate the release of the NAS signaling connection after the service request process is completed. In NB-S1 mode, under some of the schemes proposed above, when the MME needs to initiate the establishment of one or more user plane radio bearers, the MME can check whether UE110 can support the establishment of additional user plane radio bearers based on the multiple data radio bearer (DRB) support indicated by UE110 in the UE network capability IE.

[0034] Under some of the proposed schemes, when the EPS bearer context state IE is included in the CONTROL PLANE SERVICE REQUEST message, the wireless network 120 can locally deactivate all those EPS bearer contexts that are active on the network side but indicated as inactive by UE 110 (without peering signaling between the wireless network 120 and UE 110). When the default EPS bearer context is marked as inactive in the EPS bearer context state IE included in the CONTROL PLANE SERVICE REQUEST message, and when this default bearer is not associated with UE 110's last PDN connection in the MME, the MME can locally deactivate all EPS bearer contexts associated with the PDN connection having the default EPS bearer context without peering ESM signaling to UE 110. When the default bearer is associated with the last remaining PDN connection of UE 110 in the MME, and when UE 110 and MME support EMM-REGISTERED without PDN connection, the MME can locally deactivate all EPS bearer contexts associated with the PDN connection having the default EPS bearer context without peer-to-peer ESM signaling to UE 110.

[0035] According to the eighth proposed embodiment of the invention, when the EPS bearer context state IE is included in the CONTROL PLANE SERVICE REQUEST and the MME decides to respond with a SERVICE ACCEPT message, the MME may include the EPS bearer context state IE, which indicates which EPS bearer contexts are active in the MME, except in cases where no EPS bearer context exists on the network side. Additionally, when the MME needs to initiate EPS bearer context state synchronization, if the EPS bearer context state IE is not included in the CONTROL PLANE SERVICE REQUEST message, the MME may also include the EPS bearer context state IE in the SERVICE ACCEPT message. Furthermore, when the MME sends a SERVICE ACCEPT message upon receiving a CONTROL PLANE SERVICE REQUEST message carrying an ESM DATA TRANSPORT message, the MME may include the T3448 value IE in the SERVICE ACCEPT message if one or more conditions are met. One such condition may be that the release auxiliary indication IE is set in the message to "no further uplink and downlink data transmissions are expected after the uplink data transmission". Another condition could be that UE 110 has indicated support for the control plane data backoff timer. Yet another condition could be that the MME decides to activate congestion control for transmitting user data via the control plane. Under the proposed scheme, if the MME sends a SERVICE ACCEPT message and decides to deactivate congestion control for transmitting user data via the control plane, the MME can delete the stored control plane data backoff time for that UE. Furthermore, the MME may not include the timer T3448 value IE in the SERVICE ACCEPT message.

[0036] Under some of the proposed schemes, if the EPS bearer context state (IE) is included in the CONTROL PLANE SERVICE REQUEST message or if the MME needs to initiate EPS bearer context state synchronization, the MME can consider the service request process to have been successfully completed when it sends the SERVICE ACCEPT message. If the EPS bearer context state (IE) is not included in the CONTROL PLANE SERVICE REQUEST message and the MME does not need to initiate EPS bearer context state synchronization, the MME can consider the service request process to have been successfully completed under one or more of the following conditions: The first condition could be when the MME successfully completes the NAS security mode control process. The second condition could be when the MME receives an indication from the lower layer that a user plane has been established when radio bearer establishment is required. The third scenario is that upon receiving the CONTROL PLANE SERVICE REQUEST message and completing the EMM common procedure (if any), and if the CONTROL PLANE SERVICE REQUEST message has been successfully integrity-checked and the ESM message container or NAS message container (if applicable) in the CONTROL PLANE SERVICE REQUEST message has been successfully decrypted, no radio bearer establishment is required, and the MME has pending downlink user data or signaling unrelated to the EMM common procedure. The fourth scenario is that upon sending the SERVICE ACCEPT message or upon deciding to initiate the release of the NAS signaling connection, if the CONTROL PLANE SERVICE REQUEST message has been successfully integrity-checked and the ESM message container or NAS message container (if applicable) in the CONTROL PLANE SERVICE REQUEST message has been successfully decrypted, no radio bearer establishment is required, and the MME does not have any pending downlink user data or signaling. Under the proposed scheme, if the MME considers the service request procedure to have been successfully completed, the MME can forward the contents of the ESM message container IE (if any) to the ESM layer. Additionally, the MME can forward the contents of the NAS message container IE (if any).

[0037] Under some of the proposed schemes, UE 110 may consider the receipt of any of the following as a successful completion of the procedure: (i) a SECURITY MODE COMMAND message; (ii) a security-protected EMM message that is different from the SERVICE REJECT message and not related to the common EMM procedure; (iii) a security-protected ESM message; and (iv) an indication from a lower layer that a user plane radio bearer has been established. Upon successful completion of the procedure, UE 110 may reset the service request attempt counter, and UE 110 may stop timer T3417 and enter the EMM-REGISTERED state. It is worth noting that the security-protected EMM message may be, for example, a SERVICE ACCEPT message, and the ESM message may be an ESM DATATRANSPORT message.

[0038] In some of the proposed solutions, UE 110 may consider an indication from a lower layer that a user plane radio bearer has been established as a successful completion of the process. Alternatively, UE 110 may consider receiving a SERVICE ACCEPT message as a successful completion of the process without establishing a user plane radio bearer. In both cases, UE 110 may reset the service request attempt counter, stop timer T3417, and enter the EMM-REGISTERED state. In some of the proposed solutions, UE 110 may also consider an indication from a lower layer that a radio resource control (RRC) connection has been released as a successful completion of the process. Furthermore, UE 110 may reset the service request attempt counter, stop timer T3417, and enter the EMM-REGISTERED state. In some of the proposed solutions, UE 110 may consider an indication from a lower layer that an RRC connection has been released as an abnormal condition and may follow the procedures described above.

[0039] Under the ninth proposed scheme according to the present invention, when the MUSIM UE (e.g., UE 110) in the CONTROL PLANE SERVICE REQUEST message sets the request type to "NAS signaling connection release" or "paging rejection" in the UE request type IE, the UE can consider receiving the SERVICE ACCEPT message as a successful completion of the process. Additionally, the UE can reset the service request attempt counter, stop timer T3417, enter the EMM-REGISTERED state, and not locally deactivate the EPS bearer context.

[0040] Under the tenth proposed embodiment of the present invention, UE 110 may consider the receipt of the SERVICE ACCEPT message as a successful completion of the process. Furthermore, UE 110 may reset the service request attempt counter, stop timer T3417, and enter the EMM-REGISTERED state.

[0041] Under some of the proposed schemes, when the MME needs to initiate EPS bearer context state synchronization or provide UE 110 with a list of "No Tracking Areas for Roaming" IEs containing one or more prohibited TAIs or a list of "No Tracking Areas for Area Services" IEs containing one or more prohibited TAIs, UE 110 can still receive the "Service Acceptance" message even after UE 110 receives a "SECURITY MODE COMMAND" message or an indication from a lower layer that a user plane radio bearer has been established and the service request procedure has been successfully completed. Upon receiving the SECURITY MODE COMMAND message or an indication from a lower layer that a user plane radio bearer has been established, UE 110 can start timer T3449. Upon receiving a security-protected EMM message or a security-protected ESM message unrelated to EMM common procedures, UE 110 can stop timer T3449. If UE 110 receives a SERVICE ACCEPT message while timer T3449 is running, UE 110 can process the SERVICE ACCEPT message and stop timer T3449. If UE 110 is not in the EMM-SERVICE-REQUEST-INITIATED state and timer T3449 is not running, the reception of the SERVICE ACCEPT message can be considered a protocol error, and UE 110 can return an EMMSTATUS message or reply with an EMM STATUS message. Otherwise, UE 110 can process the SERVICE ACCEPT message.

[0042] Under some of the proposed schemes, when UE 110 processes the SERVICE ACCEPT message and considers the EPS bearer context state IE included in that message, UE 110 can locally deactivate all EPS bearer contexts that are active in UE 110 but indicated as inactive by the MME (without peering signaling between UE 110 and the MME). If the default EPS bearer context is marked as inactive in the EPS bearer context state IE included in the SERVICE ACCEPT message, and this default bearer is not associated with the last remaining PDN connection in UE 110, UE 110 can locally deactivate all EPS bearer contexts associated with the PDN connection having the default EPS bearer context without peering ESM signaling to the MME. When the default bearer is associated with the last remaining PDN connection of UE 110 in the MME, and UE 110 and the MME support EMM-REGISTERED without PDN connection, UE 110 can locally deactivate all EPS bearer contexts associated with the PDN connection having the default EPS bearer context without peer ESM signaling to the MME.

[0043] According to the eleventh proposed embodiment of the present invention, when UE 110 processes a SERVICE ACCEPT message, receives one or more prohibited TAIs from the list of "Prohibited Tracking Areas for Roaming" IEs in the SERVICE ACCEPT message, and UE 110 is operating in satellite E-UTRAN access, UE 110 can store the TAIs included in the IE (if not already stored) into the "Prohibited Tracking Areas for Roaming" list. Additionally, UE 110 can remove TAIs from the stored TAI list (if it exists). In the proposed embodiment, when UE 110 processes a SERVICE ACCEPT message, receives one or more prohibited TAIs from the list of "Prohibited Tracking Areas for Area Service" IEs in the SERVICE ACCEPT message, and UE 110 is operating in satellite E-UTRAN access, UE 110 can store the TAIs included in the IE (if not already stored) into the "Prohibited Tracking Areas for Area Service" list. Furthermore, UE 110 can remove TAIs from the stored TAI list (if it exists). If the received SERVICE ACCEPT message contains the T3448 value IE, the UE may perform certain operations, including: (a) stopping timer T3448 if it is running; (b) treating the transmission of user data via the control plane as successful; and (c) starting timer T3448 with the value provided in the T3448 value IE.

[0044] It is worth noting that when UE 110 is using EPS service with control plane CIoT EPS optimization, if the T3448 value IE exists in the SERVICE ACCEPT message and this value indicates that the timer is zero or disabled, UE 110 can treat this as an abnormal situation and continue as if the T3448 value IE did not exist. Furthermore, if UE 110 in EMM-IDLE mode initiates a service request procedure by sending a CONTROL PLANE SERVICE REQUEST message, and the SERVICE ACCEPT message does not include the T3448 value IE, and if timer T3448 is running, UE 110 can stop timer T3448.

[0045] In view of the above, certain important features of the various proposed solutions according to the present invention will be highlighted below.

[0046] In one aspect, when the EPS network device (e.g., network node 125) receives a CONTROL PLANESERVICE REQUEST message from UE 110, and if the EPS network device determines that it needs to provide UE 110 with a list of “Do Not Track Areas for Roaming” containing one or more prohibited TAIs, a list of “Do Not Track Areas for Service in Areas” containing one or more prohibited TAIs, or both, the EPS network device may send a SERVICE ACCEPT message to UE 110.

[0047] In one aspect, when a SERVICE ACCEPT message is received from radio network 120, the message includes one or more prohibited TAIs from the "No Tracking Areas for Roaming" IE list, one or more prohibited TAIs from the "No Tracking Areas for Area Service" IE list, or both, and UE 110 can process the received SERVICE ACCEPT message while UE 110 determines that timer T3449 is still running. Furthermore, in response to one or more predefined criteria being met, UE 110 can store the received TAI value (if not already stored) in one or more prohibited TAIs from the "No Tracking Areas for Roaming" IE list, or in one or more prohibited TAIs from the "No Tracking Areas for Area Service" IE list. In some implementations, one of the one or more predefined criteria may be that UE 110 processes the received IE when it determines that UE 110 is operating in a satellite E-UTRAN access cell. In some implementations, one of the one or more predefined criteria may be that UE 110 determines that the satellite E-UTRAN access cell in which UE 110 is operating is broadcasting multiple TAC values ​​of the selected PLMN.

[0048] In one aspect, when an EPS network device (e.g., network node 125) receives a CONTROL PLANESERVICE REQUEST message from UE 110, and in response to the network device determining that it needs to provide UE 110 with one or more prohibited TAIs from the "No Tracking Areas for Roaming" list or one or more prohibited TAIs from the "No Tracking Areas for Service in a Region" list, the EPS network device may include the "No Tracking Areas for Roaming" list, the "No Tracking Areas for Service in a Region" list, or both, in a message (e.g., a SECURITY MODE COMMAND message) sent by the EPS network device to UE 110 during the service process.

[0049] In one aspect, during a service process, when UE 110 receives a message from radio network 120 that includes a list of "No Tracking Areas for Roaming," a list of "No Tracking Areas for Service in a Region," or both, and while timer T3449 is still running, UE 110 can process the received message. Furthermore, in response to one or more predefined criteria being met, UE 110 can store the received TAI value (if not already stored) in one or more prohibited TAIs in the "No Tracking Areas for Roaming" IE list, or in one or more prohibited TAIs in the "No Tracking Areas for Service in a Region" IE list. In some implementations, one of the one or more predefined criteria may be that UE 110 processes the received IE when it determines that UE 110 is operating in a satellite E-UTRAN access cell. In some implementations, one of the one or more predefined criteria may be that UE 110 determines that the satellite E-UTRAN access cell in which UE 110 is operating is broadcasting multiple TAC values ​​of the selected PLMN.

[0050] Illustrative Implementation

[0051] Figure 2 An example communication system 200 having at least example apparatus 210 and example apparatus 220 according to an embodiment of the present invention is illustrated. Each of apparatus 210 and apparatus 220 can perform various functions to implement the schemes, techniques, processes, and methods described in this invention relating to the prohibited TAI list IE in the EPS SERVICE ACCEPT message of a UE in mobile communications, including the various schemes described above with respect to the various proposed designs, concepts, schemes, systems, and methods including network environment 100, as well as the processes described below.

[0052] Each of devices 210 and 220 may be part of an electronic device, which may be a network device or UE (e.g., UE 110), such as a portable or mobile device, a wearable device, a vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of devices 210 and 220 may be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet computer, laptop computer, or notebook computer. Each of devices 210 and 220 may also be part of a machine-type device, which may be a device such as a fixed or stationary device, a home appliance, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of devices 210 and 220 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, device 210 and / or device 220 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IP network.

[0053] In some embodiments, each of devices 210 and 220 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction-set computing (CISC) processors, or one or more reduced instruction-set computing (RISC) processors. In the various embodiments described above, each of devices 210 and 220 may be implemented in or as a network device or UE. Each of devices 210 and 220 may include... Figure 2 At least some of the components shown are, for example, processor 212 and processor 222, respectively. Each of devices 210 and 220 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of the present invention, and therefore, such components of devices 210 and 220 are neither... Figure 2 As shown in the image, it is not described below for the sake of simplicity and brevity.

[0054] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "processor" is used herein to refer to processors 212 and 222, according to the invention, in some embodiments each of processors 212 and 222 may include multiple processors, while in other implementations each may include a single processor. In another aspect, each of processors 212 and 222 may be implemented as hardware (and optionally firmware) having electronic components including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to achieve a specific purpose according to the invention. In other words, in at least some implementations, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including tasks related to the UE processing the prohibited TAI list IE in the EPS SERVICE ACCEPT message in mobile communications according to various implementations of the invention.

[0055] In some embodiments, device 210 may further include a transceiver 216 coupled to processor 212. Transceiver 216 is capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 216 is capable of wirelessly communicating with different types of wireless networks using different radio access technologies (RATs). In some embodiments, transceiver 216 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 220 may further include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 226 is capable of wirelessly communicating with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 226 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0056] In some embodiments, device 210 may further include memory 214 coupled to and accessible by processor 212 and capable of storing data therein. In some embodiments, device 220 may further include memory 224 coupled to and accessible by processor 222 and capable of storing data therein. Each of memory 214 and memory 224 may include a type of random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memory 214 and memory 224 may include a read-only memory (ROM) type such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of memories 214 and 224 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory. Alternatively or additionally, each of memories 214 and 224 may include a UICC.

[0057] Each of devices 210 and 220 may be a communication entity capable of communicating with each other using various schemes proposed according to the present invention. For illustrative and non-limiting purposes, a description of the capabilities of device 210 as a UE (e.g., UE 110) and device 220 as a network node (e.g., terrestrial network node 125 or non-terrestrial network node 128) of a wireless network (e.g., wireless network 120) is provided below.

[0058] Under certain proposed embodiments of the present invention regarding the prohibited TAI list IE in the EPS SERVICE ACCEPT message for UE processing of mobile communications, the processor 212 implemented in UE 110 or the device 210 implemented as UE 110 may send a control plane service request message to the EPS network node (e.g., device 220) of the wireless network (e.g., wireless network 120) via transceiver 216. Additionally, the processor 212 may, in response to this transmission, receive a SERVICE ACCEPT message from the EPS network node via transceiver 216. The SERVICE ACCEPT message may include any one or both of the following: (i) a list of "No Tracking Areas for Roaming" IEs containing one or more prohibited TAIs; and (ii) a list of "No Tracking Areas for Area Services" IEs containing one or more prohibited TAIs.

[0059] In some implementations, upon receiving a SERVICE ACCEPT message, if the EPS network node determines that it needs to provide device 210 with any one or both of the following: (a) a list of “Do Not Tracking Areas for Roaming” containing one or more prohibited TAIs; and (b) a list of “Do Not Tracking Areas for Service in Areas” containing one or more prohibited TAIs.

[0060] In some implementations, the processor 212 may also process the received SERVICE ACCEPT message in response to determining that the T3449 timer is still running.

[0061] In some embodiments, processor 212 may also, in response to determining that at least one of one or more predefined criteria has been met, store in memory 214 one or more TAI values, either from a list of "No Tracking Areas for Roaming" IEs containing one or more prohibited TAIs and a list of "No Tracking Areas for Service in the Area" IEs containing one or more prohibited TAIs. In some embodiments, at least one of the one or more predefined criteria may include processing one or more received IEs while determining that device 210 is operating in a satellite E-UTRAN access cell. Optionally, at least one of the one or more predefined criteria may include determining that the satellite E-UTRAN access cell in which device 210 is operating is broadcasting multiple TAC values ​​of a selected PLMN.

[0062] In other proposed embodiments of the present invention regarding the prohibited tracking area (TAI) list IE in the EPS SERVICE ACCEPT message during UE processing of mobile communications, the processor 212 of the device 210 implemented in or implemented as UE 110 can send a CONTROLPLANE SERVICE REQUEST message to the EPS network node (e.g., device 220) of the wireless network (e.g., wireless network 120) via transceiver 216. Furthermore, the processor 212 can receive a message from the EPS network node via transceiver 216 during the service process in response to this transmission. The message may include any one or both of the following: (i) a "prohibited tracking area for roaming" list; and (ii) a "prohibited tracking area for providing service to a region" list.

[0063] In some implementations, the message may include a SECURITY MODE COMMAND message.

[0064] In some implementations, upon receiving a message, if the EPS network node determines that it needs to provide the UE with one or both of the following: (a) a “banned tracking areas for roaming” list containing one or more prohibited TAIs; and (b) a “banned tracking areas for providing services to areas” list containing one or more prohibited TAIs.

[0065] In some implementations, processor 212 may also process received messages in response to determining that timer T3449 is still running.

[0066] In some embodiments, processor 212 may also, in response to determining that at least one of one or more predefined criteria has been met, store in memory 214 one or more TAI values, including one or more of a "No Tracking Areas for Roaming" list containing one or more prohibited TAIs and a "No Tracking Areas for Service in the Area" list containing one or more prohibited TAIs. In some embodiments, at least one of the one or more predefined criteria may include processing one or more received IEs while determining that device 210 is operating in a satellite E-UTRAN access cell. Alternatively, at least one of the one or more predefined criteria may include determining that the satellite E-UTRAN access cell in which device 210 is operating is broadcasting multiple TAC values ​​of the selected PLMN.

[0067] Exemplary process

[0068] Figure 3An exemplary process 300 according to an implementation of the present invention is shown. Process 300 may represent aspects of implementing the various proposed designs, concepts, schemes, systems, and methods described above, whether partially or completely, including those described above. More specifically, process 300 may represent an aspect of proposed concepts and schemes relating to the UE's handling of the prohibited TAI list IE in the EPS SERVICEACCEPT message during mobile communications. Process 300 may include one or more operations, actions, or functions as shown in one or more of blocks 310 and 320. Although illustrated as discrete blocks, the individual blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 300 may be... Figure 3 The process can be executed in the order shown, or alternatively in a different order. Furthermore, one or more blocks / sub-blocks of process 300 can be executed iteratively. Process 300 can be implemented by or within devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 300 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., a network node of a network (e.g., wireless network 120) or a base station (e.g., terrestrial network node 125 or non-terrestrial network node 128)). Process 300 may begin at block 310.

[0069] At 310, process 300 may include a processor 212 of device 210, implemented in UE 110 or as UE 110, sending a CONTROL PLANE SERVICE REQUEST message via transceiver 216 to an EPS network node (e.g., device 220) of a wireless network (e.g., wireless network 120). Process 300 may proceed from 310 to 320.

[0070] At 320, process 300 may include processor 212 receiving a SERVICE ACCEPT message in response to transmission from the EPS network node via transceiver 216. The SERVICE ACCEPT message may include any or both of the following: (i) a list of "Do Not Tracking Zones for Roaming" IEs containing one or more TAIs; and (ii) a list of "Do Not Tracking Zones for Area Services" IEs containing one or more TAIs.

[0071] In some implementations, upon receiving a SERVICE ACCEPT message, process 300 may include processor 212 receiving the SERVICE ACCEPT message from the EPS network node if the EPS network node determines that it needs to provide device 210 with any one or both of the following: (a) a “No Tracking Areas for Roaming” list containing one or more prohibited TAIs; and (b) a “No Tracking Areas for Service to Areas” list containing one or more prohibited TAIs.

[0072] In some implementations, process 300 may also include processor 212 in response to determining that timer T3449 is still running to process the received SERVICE ACCEPT message.

[0073] In some embodiments, process 300 may further include processor 212 storing in memory 214 one or more TAI values, in response to determining that at least one of one or more predefined criteria has been met, a list of "No Tracking Areas for Roaming" IEs containing one or more prohibited TAIs and a list of "No Tracking Areas for Service in the Area" IEs containing one or more prohibited TAIs. In some embodiments, at least one of the one or more predefined criteria may include processing one or more received IEs while determining that device 210 is operating in a satellite E-UTRAN access cell. Alternatively, at least one of the one or more predefined criteria may include determining that the satellite E-UTRAN access cell in which device 210 is operating is broadcasting multiple TAC values ​​of the selected PLMN.

[0074] Figure 4 An exemplary process 400 according to an implementation of the present invention is shown. Process 400 may represent aspects of implementing the various proposed designs, concepts, schemes, systems, and methods described above, whether partially or completely, including those described above. More specifically, process 400 may represent an aspect of proposed concepts and schemes relating to the UE's processing of the prohibited TAI list IE in the EPS SERVICE ACCEPT message in mobile communications. Process 400 may include one or more operations, actions, or functions as shown in one or more of blocks 410 and 420. Although illustrated as discrete blocks, the individual blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 400 may be... Figure 4The process can be executed in the order shown, or alternatively in a different order. Furthermore, one or more blocks / sub-blocks of process 400 can be executed iteratively. Process 400 can be implemented by or within devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 400 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., a network node of a network (e.g., wireless network 120) or a base station (e.g., terrestrial network node 125 or non-terrestrial network node 128)). Process 400 may begin at block 410.

[0075] At 410, process 400 may include a processor 212 of device 210, implemented in UE 110 or as UE 110, sending a CONTROL PLANE SERVICE REQUEST message via transceiver 216 to an EPS network node (e.g., device 220) of a wireless network (e.g., wireless network 120). Process 400 may proceed from 410 to 420.

[0076] At 420, process 400 may include processor 212 receiving a message from the EPS network node via transceiver 216 during the service process in response to the transmission. The message may include any one or both of the following: (i) a list of "no-tracking areas for roaming"; and (ii) a list of "no-tracking areas for providing service to areas".

[0077] In some implementations, the message may include a SECURITY MODE COMMAND message.

[0078] In some implementations, when receiving a message, process 400 may include processor 212 receiving a message from the EPS network node if the EPS network node determines that it needs to provide the UE with one or both of the following: (a) a “No Tracking Areas for Roaming” list containing one or more prohibited TAIs; and (b) a “No Tracking Areas for Service in Areas” list containing one or more prohibited TAIs.

[0079] In some implementations, process 400 may also include processor 212 in response to determining that timer T3449 is still running to process the received message.

[0080] In some embodiments, process 400 may further include processor 212 storing in memory 214 one or more TAI values ​​of one or more prohibited TAIs from a list of "prohibited tracking areas for roaming" and a list of one or more prohibited TAIs from a list of "prohibited tracking areas for service to the area". In some embodiments, at least one of the one or more predefined criteria may include processing one or more received IEs while determining that device 210 is operating in a satellite E-UTRAN access cell. Alternatively, at least one of the one or more predefined criteria may include determining that the satellite E-UTRAN access cell in which device 210 is operating is broadcasting multiple TAC values ​​of a selected PLMN.

[0081] Additional notes

[0082] The subject matter described in this invention sometimes illustrates different components contained within or connected to different other components. It should be understood that the described architecture is merely an example, and many other architectures can actually achieve the same functionality. In a conceptual sense, any arrangement of components that achieve the same function is effectively “associated” to achieve the desired functionality. Therefore, any two components combined in this invention to achieve a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific examples of operably coupled include, but are not limited to, physically matchable and / or physically interacting components and / or wirelessly interactable and / or logically interactable components.

[0083] Furthermore, regarding the use of virtually any plural and / or singular terms in this invention, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly described in this invention.

[0084] Furthermore, those skilled in the art will understand that, in general, the terminology used in this invention, particularly in the appended claims, such as the body of the appended claims, is typically intended as “open-ended” terms. For example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” and the term “including” should be interpreted as “including but not limited to.” Those skilled in the art will further understand that if a specific number of introduced claim statements are desired, such an intent will be explicitly stated in the claims, and without such a statement, such an intent does not exist. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of such phrases should not be construed as implying that a claim statement introduced by the indefinite article "a (a, an)" limits any particular claim containing such an introduced claim statement to only one implementation of such a statement, even when the same claim includes the introductory phrase "one or more" or "at least one," and indefinite articles such as "a (a, an)," for example, "a (a, an)" should be interpreted as meaning "at least one" or "one or more"; this also applies to the use of explicit texts introducing claim statements. Furthermore, even if the specific number of introduced claims is explicitly listed, those skilled in the art will recognize that such a list should be interpreted as meaning at least the number listed; for example, a bare list of "two lists" without other modifiers means at least two lists, or two or more lists. Moreover, in those cases, the convention is similar to "at least one of A, B, and C, etc." Generally, in the conventional sense understood by those skilled in the art, the use of such a construct, such as "a system having at least one of A, B, and C," will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc., in those cases where the convention is similar to "at least one of A, B, or C." Generally, this construct is intended for use in the conventional sense understood by those skilled in the art; for example, "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together. Those skilled in the art will further understand that any extractive words and / or phrases that actually present two or more alternative terms, whether in the specification, claims, or drawings, should be understood to cover the possibility of including one of the terms, any one or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B."

[0085] As will be understood from the foregoing, various embodiments of the invention have been described for illustrative purposes, and various modifications may be made without departing from the scope and spirit of the invention. Therefore, the various implementations disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the appended claims.

Claims

1. A method for processing a list of prohibited tracking area identifiers in an Evolved Packet System Service Acceptance message, the method comprising: Send a control plane service request message to the evolved packet service (EPS) network node of the wireless network; as well as In response to the sending, a service acceptance message is received from the EPS network node; The service acceptance message includes any one or both of the following: A list of "Do Not Tracking Zones for Roaming" information elements (IE) containing one or more Do Not Tracking Zone Identifiers (TAIs); as well as A list of "Do Not Track Zones" in Internet Explorer that includes one or more regions that prohibit TAI.

2. The method according to claim 1, wherein, The receiving service acceptance message includes receiving the service acceptance message from the EPS network node when the EPS network node determines that it needs to provide the user equipment with any one or both of the following: A list of "No Tracking Zones for Roaming" containing one or more TAIs; and A list of "No Tracking Areas that provide services to the area" containing one or more TAIs.

3. The method according to claim 1, further comprising: In response to determining that the T3449 timer is still running, the received service accept message is processed.

4. The method according to claim 1, further comprising: In response to determining that at least one of one or more predefined criteria has been met, store one or more TAI values ​​of one or more of the "Do Not Track in Roaming" IE list and one or more of the "Do Not Track in Areas" IE list.

5. The method according to claim 4, wherein, The at least one of the predefined criteria includes processing one or more received IEs when it is determined that the user equipment is operating in a Satellite Evolution Universal Mobile Telecommunications System (UMTS) Radio Access Network (E-UTRAN) access cell.

6. The method according to claim 4, wherein, The at least one of the one or more predefined criteria includes: determining that the satellite evolution universal mobile communication system (UMTS) radio access network (E-UTRAN) access cell in which the user equipment is operating is broadcasting multiple tracking area code (TAC) values ​​for a selected public terrestrial mobile network (PLMN).

7. A method for processing a list of prohibited tracking area identifiers in an Evolved Packet System Service Accept message, the method comprising: Send a control plane service request message to the evolved packet service (EPS) network node of the wireless network; as well as In response to the sending, a security mode command message is received from the EPS network node during the service process. The security mode command message includes any one or both of the following: List of "No Tracking Zones for Roaming"; as well as List of "Do Not Track Areas for Services Provided to Areas".

8. The method according to claim 7, wherein, Receiving the message includes receiving the message from the EPS network node if the EPS network node determines that it needs to provide one or both of the following to the user equipment: A list of "No Tracking Zones for Roaming" containing one or more No Tracking Zone Identifiers (TAIs); and A list of "No Tracking Areas that provide services to the area" containing one or more TAIs.

9. The method according to claim 7, further comprising: In response to determining that the T3449 timer is still running, the received message is processed.

10. The method according to claim 7, further comprising: In response to determining that at least one of one or more predefined criteria has been met, store one or more TAI values ​​of one or more prohibited TAIs from the "No Tracking Areas for Roaming" list and one or more prohibited TAIs from the "No Tracking Areas for Service in the Area" list.

11. The method according to claim 10, wherein, The at least one of the predefined criteria includes processing one or more received information elements (IEs) when it is determined that the user equipment is operating in a UMTS Radio Access Network (E-UTRAN) access cell.

12. The method according to claim 10, wherein, The at least one of the one or more predefined criteria includes: determining that the satellite evolution universal mobile communication system (UMTS) radio access network (E-UTRAN) access cell in which the user equipment is operating is broadcasting multiple tracking area code (TAC) values ​​for a selected public terrestrial mobile network (PLMN).

13. An apparatus for processing a list of prohibited tracking area identifiers information elements in an Evolved Packet System Service Acceptance message, implemented in a User Equipment (UE), the apparatus comprising: Transceiver configured for wireless communication; as well as A processor, coupled to the transceiver and configured to perform operations via the transceiver, the operations including: Sending control plane service request messages to Evolved Packet Service (EPS) network nodes of wireless networks; and In response to the sending, a message is received from the EPS network node, wherein the message includes a service acceptance message or a security mode command message; The message includes any one or both of the following: A list of "Do Not Tracking Zones for Roaming" information elements for Internet Explorer that contain one or more Do Not Tracking Zone Identifiers (TAIs); and A list of "Do Not Track Zones" in Internet Explorer that includes one or more regions that prohibit TAI.

14. The apparatus according to claim 13, wherein, The message reception includes receiving the message from the EPS network node when the EPS network node determines that it needs to provide the UE with any one or both of the following: A list of "No Tracking Zones for Roaming" containing one or more TAIs; and A list of "No Tracking Areas that provide services to the area" containing one or more TAIs.

15. The apparatus according to claim 13, wherein, The processor is also configured to perform operations including the following: In response to determining that the T3449 timer is still running, the received message is processed.

16. The apparatus according to claim 13, wherein, The processor is also configured to perform operations including the following: In response to determining that at least one of one or more predefined criteria has been met, store one or more TAI values ​​of one or more of the "Do Not Track in Roaming" IE list and one or more of the "Do Not Track in Areas" IE list.

17. The apparatus according to claim 16, wherein, The at least one of the predefined criteria includes processing one or more received IEs when it is determined that the UE is operating in a Satellite Evolution Universal Mobile Telecommunications System (UMTS) Radio Access Network (E-UTRAN) access cell.

18. The apparatus according to claim 16, wherein, The at least one of the one or more predefined criteria includes: determining that the Satellite Evolution Universal Mobile Telecommunications System (UMTS) Radio Access Network (E-UTRAN) access cell in which the UE is operating is broadcasting multiple Tracking Area Code (TAC) values ​​for a selected Public Terrestrial Mobile Network (PLMN).

19. A non-volatile computer-readable storage medium storing program instructions and data that, when executed by a processor of an apparatus processing an Evolved Packet System Service Acceptance Message (EPS IF ...

Images