Paging conflict with 5GMM specific procedures or service request procedures

Abstract

If a UE receives a paging or notification message while a 5GMM-specific procedure or service request procedure initiated by the User Equipment (UE) is in progress, the UE may buffer the paging or notification message. To buffer the paging or notification message, the UE may remember the pending mobile station call transaction and retry the registration or request procedure using Access Class 0 (=MT_acc) if the ongoing UE-initiated 5GMM-specific procedure or service request procedure fails due to access prohibition. If the network receives a 5GMM-specific procedure or service request procedure while an MT transaction (i.e., a paging message with access type set to 3GPP access or a notification message indicating 3GPP access via non-3GPP access with access type) is in progress, the network may complete the incoming MT transaction and remember the pending mobile station call transaction, and continue the pending mobile station call transaction once the MO transaction is completed.

Description

Technical Field

[0001] This application relates in its entirety to wireless communication systems, including handling paging and notifications while a 5GMM-specific process or service request process is in progress. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include 3GPP Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to by the industry organization as WiMAX; and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In the fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes and NR nodes (also known as next-generation node B or g NodeB (gNB)).

[0003] The RAN uses Radio Access Technology (RAT) to communicate between RAN nodes and UEs. The RAN can include Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provides access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal System for Mobile Communications (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT, and NG-RAN implements the 5G RAT. In some deployments, E-UTRAN may also implement the 5G RAT.

[0004] 5G NR frequency bands can be divided into two distinct frequency ranges. Frequency range 1 (FR1) may include bands operating below 6 GHz, some of which are available for previous standards and can potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include bands from 24.25 GHz to 52.6 GHz. The bands in the millimeter wave (mmWave) range of FR2 may have a smaller range than those in FR1 but potentially higher available bandwidth. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may vary over time or in different regions. Attached Figure Description

[0005] To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0006] Figure 1 This is a simplified signal flow diagram for a scenario where the notification process is ignored when the parallel 3GPP MO data service request / registration request process fails.

[0007] Figure 2 This is a simplified signal flow diagram for a scenario where the paging process is ignored when the parallel 3GPP MO data service request / registration request process fails.

[0008] Figure 3 This is a simplified signaling flow diagram of a scenario where MT transactions (e.g., notifications (domain = 3GPP)) are missed due to congestion at the gNB.

[0009] Figure 4 An embodiment for preventing reference is shown. Figure 1 and Figure 2 The signal flow diagram describes the method for handling MT transaction failures.

[0010] Figure 5 A flowchart is shown of a method for a UE to perform buffering of paging messages or notification messages when a 5GMM-specific process is occurring, according to one embodiment.

[0011] Figure 6 An embodiment for preventing reference is shown. Figure 3 The signal flow diagram describes the method for handling MT transaction failures.

[0012] Figure 7 A flowchart is shown of a method for preventing network nodes from missing notification messages and paging messages, according to one embodiment.

[0013] Figure 8 A system according to one implementation is shown.

[0014] Figure 9 An infrastructure setup according to one implementation scheme is shown.

[0015] Figure 10 A platform based on one implementation scheme is shown.

[0016] Figure 11 An apparatus according to one embodiment is shown.

[0017] Figure 12 An exemplary interface according to one implementation is shown.

[0018] Figure 13 The components according to one implementation are shown. Detailed Implementation

[0019] One goal of network communications is to provide reliable service where little or no notification or paging of Mobile-Terminated (MT) transactions is missed. It is crucial that the UE properly handles network transactions to create a reliable experience. For example, if a user equipment (UE) has an incoming call, it is expected that the network will appropriately deliver the call to the UE.

[0020] However, several scenarios exist where transactions such as incoming calls can fail due to conflicting conditions. This article outlines three scenarios that can cause such transaction failures. These failures can occur when paging or notifications for 5GSM (Fifth Generation System) services are missed due to UE-initiated 5GMM (Fifth Generation Mobility Management) specific procedures or service request procedures, especially when the network is experiencing high load or congestion. Conflicts between paging or notifications and 5GMM specific procedures or service request procedures can lead to failure or omission of mobile station called (MT) transactions.

[0021] The embodiments described herein depict systems, apparatus, and methods for correcting these transaction failures. In some embodiments, the UE may buffer paging messages or notification messages until an ongoing 5GMM-specific procedure or service request procedure is completed. If the 5GMM-specific procedure or service request procedure is successful, the UE may ignore the paging message or notification message. If the 5GMM-specific procedure or service request procedure fails, the UE may initiate a 5GMM-specific procedure or service request procedure to handle the paging message or notification message. In some embodiments, whenever a paging procedure is initiated or a notification message has been sent to the UE, the network node may continue with the registration request or service request.

[0022] 5GMM-specific procedures can be: 1) Initiated by the UE and used, for example, to register with the network and establish a 5GMM context for 5GS services to update the UE's location / parameters: Registration. 2) Initiated by the UE or the network and used to deregister from the network and release the 5GMM context for 5GS services: Deregistration. 3) Initiated by the UE and used to deregister from the network and release the 5GMM context for 5GS services: Emergency Call Inactivity Procedure. The UE can use the Service Request Procedure to request the establishment of a secure connection to the AMF. The Service Request Procedure can also be used to activate a user plane connection for an established PDU session.

[0023] The various operations will be described sequentially as a plurality of discrete operations in a manner most conducive to understanding this disclosure. However, the order of description should not be construed as implying that these operations necessarily depend on a specific order. In particular, these operations do not necessarily need to be performed in the order of presentation.

[0024] Additional details and examples are provided with reference to the following accompanying drawings. Embodiments of this disclosure can be understood with reference to the drawings, wherein similar components are consistently represented by similar numbers. Components of the embodiments of the invention disclosed herein, as generally described and illustrated in the accompanying drawings, can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of embodiments of the systems and methods of this disclosure is not intended to limit the scope of this disclosure as protected by the claims, but rather represents only possible embodiments.

[0025] Figure 1 This is a simplified signaling flow diagram 100 for a scenario where the notification process fails via non-3GPP access. The notification process can be used by the network to request the UE to re-establish the Packet Data Unit (PDU) session using user plane resources by sending a notification message on non-3GPP access, or to deliver downlink signaling associated with 3GPP access on 3GPP access. The signaling flow diagram 100 illustrates the UE Non-Access Stratum (NAS), UE Access Stratum (AS), network nodes (e.g., gNB), Access and Mobility Management Functions (AMF), and non-3GPP (N3GPP) access networks (e.g., Wi-Fi).

[0026] In this scenario, the UE pre-occupies and registers on both 3GPP and non-3GPP access modes on the same 5G Public Land Mobile Network (PLMN). Furthermore, in this scenario, the 3GPP access mode is in an idle state, while the non-3GPP access mode is in a connected state.

[0027] As shown in the figure, the UE initiates a UE-initiated 5GMM-specific procedure or service request procedure 104 with access class 7 (=MO_data). Although the illustrated embodiment shows the 5GMM-specific procedure or service request procedure with access class 7 (=MO_data), the failure explained with reference to this figure can occur for any UE-initiated 5GMM-specific procedure or service request procedure with access classes other than 0 and 2 on 3GPP access in idle mode. As part of the UE-initiated 5GMM-specific procedure or service request procedure, UE-NAS sends a 106 setup request message to UE-AS.

[0028] The network can initiate a notification process by sending notification message 110 to the UE. As shown in the figure, in some cases, this can lead to a conflict state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives a notification. As shown in the figure, in this scenario, the UE receives a notification with access type = 3GPP in a non-3GPP access state before moving to a connected state in the 3GPP domain.

[0029] According to the current method for handling such conflicts, the UE ignores the 108 notification due to an ongoing 5GMM-specific procedure or service request procedure. If a paging message is received on a 3GPP access or a notification message indicating 3GPP access is received via a non-3GPP access, and a 5GMM-specific procedure or service request procedure is in progress on the 3GPP access (which is considered a Mobile Origin (MO) activity in terms of access prohibition), the UE currently ignores the paging or notification message because responding to the paging or notification would result in the same already ongoing procedure.

[0030] However, this method can cause the notification request to fail. For example, as shown in the figure, during connection establishment for a 5GMM-specific procedure, a lower layer may instruct that access prohibition applies to all access categories except categories 0 and 2. Access category prohibition can occur due to high load or congestion on the network. Due to this access category prohibition, the UE-AS may send a rejection message 112. If, during connection establishment for an MO 5GMM-specific procedure or service request procedure, a lower layer instructs that access prohibition applies to all access categories except categories 0 and 2, and the access attempt is not associated with access category 0 (= MT_acc) or 2, the UE aborts the ongoing 5GMM-specific procedure or service request procedure.

[0031] The UE will not re-trigger the ongoing 5GMM-specific process until a lower layer instructs a reduction in the prohibition of the access attempt and its associated access class.

[0032] Furthermore, although access categories 0 (MT access) and 2 (emergency access) are allowed, the UE will not retry the 114 mobile station called transaction (e.g., notification or paging), causing the MT transaction to fail. Therefore, the UE will not respond to MT paging or notifications (i.e., incoming calls), even if the MT transaction associated with notification message 110 is not prohibited (e.g., MT call access is not prohibited). This will cause high-priority mobile station called activity triggered in paging or notification to fail, even if that activity would be prohibited by access (e.g., access category 0 (MT access)). Therefore, notification message 110 is missed because the 5GMM-specific procedure is prohibited.

[0033] Figure 2 This is a simplified signal flow diagram 200 for a scenario where the paging process fails. A failure can occur if a paging request is received on the 3GPP access while a 5GMM-specific procedure or service request procedure is in progress on the 3GPP access. The UE-NAS, UE-AS, gNB, and AMF are shown in this signal flow diagram 200. In this scenario, the UE is pre-occupied and registered on the 5G PLMN 202 and is in an idle state.

[0034] As shown in the figure, the UE initiates a UE-initiated 5GMM-specific procedure or service request procedure 204 with access class 7 (=MO_data). Although the illustrated embodiment shows the 5GMM-specific procedure or service request procedure with access class 7 (=MO_data), the failure explained with reference to this figure can occur for any UE-initiated 5GMM-specific procedure or service request procedure with access classes other than 0 and 2 on 3GPP access in idle mode. As part of the UE-initiated 5GMM-specific procedure or service request procedure, UE-NAS sends a 206 setup request message to UE-AS.

[0035] The network can initiate a paging procedure 208 by sending a paging message to the UE. As shown in the figure, in some cases, this can lead to a contention state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives a paging message. As shown in the figure, in this scenario, the UE receives a paging message due to a contention condition before moving to a connected state in the 3GPP domain.

[0036] According to current methods for handling such conflicts, the UE ignores paging 212 when it anticipates moving to a connected state due to an ongoing 5GMM-specific procedure or service request procedure. However, this method can lead to paging omissions. For example, as shown, during connection establishment for a 5GMM-specific procedure, a lower layer may instruct an access ban to apply to all access categories except categories 0 and 2. Access class bans can occur due to high load or congestion on the network. Due to this access class ban, the UE-AS may send a rejection message 210. If, during connection establishment for an MO 5GMM-specific procedure or service request procedure, a lower layer instructs an access ban to apply to all access categories except categories 0 and 2, and the access attempt is not associated with access category 0 (= MT_acc) or 2, the UE aborts the ongoing 5GMM-specific procedure or service request procedure.

[0037] Although access categories 0 (MT access) and 2 (emergency access) are allowed, the UE will not retry the 214 mobile station called transaction (e.g., a transaction associated with paging), causing the MT transaction to fail. Therefore, the UE will not respond to MT paging (i.e., incoming calls), even though the MT transaction associated with the MT paging (i.e., paging procedure 208) may not be prohibited (e.g., MT call access is not prohibited). This will cause the high-priority mobile station called activity triggered in the paging to fail, even though the activity would be prohibited by access (e.g., access category 0 (MT access)). Therefore, the paging message is missed due to the prohibition of 5GMM-specific procedures, resulting in the MT transaction failure.

[0038] Figure 3 This is a simplified signaling flow diagram 300 for a scenario where MT transactions (e.g., notifications (domain = 3GPP)) are missed due to congestion at the gNB. In this scenario, similar to... Figure 1 The notification was missed. In this case, no access occurs. Instead, the gNB rejects the connection request due to high load or congestion. The UE-NAS, UE-AS, gNB, AMF, and N3GPP are shown in the signaling flow diagram 300. Although the illustrated implementation shows a notification message, a similar failure can occur when a paging message is sent.

[0039] In this scenario, the UE pre-claims and registers 302 on both 3GPP and non-3GPP access modes on the same 5G Public Land Mobile Network (PLMN). Furthermore, in this scenario, the 3GPP access mode is in an idle state, while the non-3GPP access mode is in a connected state.

[0040] As shown in the figure, the UE can initiate a UE-initiated 5GMM-specific procedure or service request procedure 304 with access class 7 (=MO_data). Although the illustrated embodiment shows the 5GMM-specific procedure or service request procedure with access class 7 (=MO_data), the failure explained with reference to this figure can occur for any UE-initiated 5GMM-specific procedure or service request procedure with access classes other than 0 and 2 on 3GPP access in idle mode. As part of the UE-initiated 5GMM-specific procedure or service request procedure, UE-NAS sends a 306 setup request message to UE-AS.

[0041] The network can initiate notification procedure 308 by sending a notification message to the UE. As shown in the figure, in some cases, this can lead to a conflict state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives a notification. As shown in the figure, in this scenario, the UE receives a notification with access type = 3GPP in a non-3GPP access state before moving to the connected state in the 3GPP domain.

[0042] According to the current method for handling such conflicts, the UE ignores the 310 notification due to an ongoing 5GMM-specific procedure or service request procedure. According to the current method, if a paging message is received on a 3GPP access or a notification message indicating 3GPP access of the access type is received via a non-3GPP access, and a 5GMM-specific procedure or service request procedure on the 3GPP access is in progress (which is considered Mobile Origin (MO) activity in relation to access prohibition), the UE currently ignores the paging or notification message because responding to the paging or notification would result in the same already ongoing procedure.

[0043] This method can cause the notification request to fail. For example, the UE can continue connection establishment by transmitting RRC setup request 312 using an access category other than category 0 (=MT_acc). Instead of the MT access category, the illustrated implementation is sending a mobile data request. However, due to the notification, the network expects the UE to initiate a 5GMM-specific procedure or service request procedure with access category 0 (=MT_acc), thus prioritizing the processing of MT transactions. The network is unaware that the notification has been ignored.

[0044] If the gNB is experiencing high load or congestion, the network may reject the 314RRC connection establishment because the requested access class is not class 0 (=MT_acc). Additionally, although access classes 0 (MT access) and 2 (emergency access) are allowed, the UE will not retry the mobile station call transaction, causing the MT transaction to fail.

[0045] Although the illustrated implementation specifies a notification process, similar failures can occur for the paging process. If the network has already initiated the paging process and received a registration request message, high load or congestion can cause the network to reject the registration request, resulting in the paging process failing and being ignored.

[0046] Figure 4 A method for preventing reference is shown. Figure 1 and Figure 2 Signal flow diagram 400 describes the method for handling MT transaction failures. Signal flow diagram 400 prevents notification messages and paging messages from being missed due to access restrictions and conflicting conditions with UE-initiated 5GMM-specific procedures or service request procedures. UE-NAS, UE-AS, gNB, AMF, and N3GPP are shown in this signal flow diagram 400.

[0047] In the illustrated implementation, the UE pre-claims and registers 402 on both 3GPP and non-3GPP access modes on the same 5G PLMN. Furthermore, the 3GPP access mode is in an idle state, while the non-3GPP access mode is in a connected state. Although paging can occur when the UE pre-claims and registers 402 on the 5G PLMN and is in an idle state without non-3GPP access, for simplicity, refer to... Figure 4 Discuss both the notification and paging processes.

[0048] As shown in the figure, the UE can initiate a UE-initiated 5GMM-specific procedure or service request procedure 404 with, for example, access class 7 (=MO_data). Although the illustrated embodiment shows a 5GMM-specific procedure or service request procedure with access class 7 (=MO_data), the method explained with reference to the figure can occur for any UE-initiated 5GMM-specific procedure or service request procedure on 3GPP access in idle mode with access classes other than 0 and 2. As part of the UE-initiated 5GMM-specific procedure or service request procedure, UE-NAS sends a 406 setup request message to UE-AS.

[0049] The following discussion covers both cases where the UE receives notification message 408 or paging message 416. Although both types of messages are discussed, it is likely that only one of these messages will be received when a 5GMM-specific procedure or service request procedure is in progress. Therefore, notification message 408 and paging message are shown with dashed lines and both are labeled as the second signal in signal flow diagram 400.

[0050] The network can initiate a notification process by sending notification message 408 to the UE. As shown in the figure, in some cases, this can lead to a conflict state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives the notification. As shown in the figure, in this scenario, the UE receives notification message 408 with access type = 3GPP in a non-3GPP access state before moving to the connected state in the 3GPP domain.

[0051] Similarly, the network can initiate a paging procedure by sending paging message 416 to the UE. As shown in the figure, in some cases, this can lead to a contention state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives paging message 416. As shown in the figure, in this scenario, the UE receives paging message 416 due to a contention condition before moving to a connected state in the 3GPP domain.

[0052] and Figure 1 and Figure 2 In contrast, in the signal flow diagram 400, if a paging message 416 is received on a 3GPP access or a notification message 408 indicating 3GPP access is received via a non-3GPP access while a 5GMM-specific procedure or service request procedure initiated by a UE on a 3GPP access is in progress, then in the case where the ongoing 5GMM-specific procedure or service request procedure initiated by a UE on a 3GPP access fails due to an indication that access attempts are prohibited for all access categories except categories 0 and 2, the UE remembers the pending mobile station call transaction, and the pending mobile station call transaction operates as a pending MT transaction with access category 0 (=MT_acc).

[0053] For example, as shown in the figure, the UE buffers paging / notification messages 410 until the ongoing 5GMM-specific procedure or service request procedure succeeds or fails. If the 5GMM-specific procedure or service request procedure succeeds, the UE can simply ignore the paging message 416 or notification message because a connection has been established. However, the 5GMM-specific procedure or service request procedure may fail. For example, during connection establishment for a 5GMM-specific procedure, a lower layer may instruct an access ban to apply to all access categories except categories 0 and 2. Access class bans can occur due to high load or congestion on the network. Due to this access class ban, the UE-AS may send a rejection message 412.

[0054] When paging message 416 or notification message 408 has been buffered, the UE can remember the MT transaction and initiate 414 a 5GMM-specific procedure or service request procedure with access class 0 (=MT_acc). Since the access class is set to 0 (=MT_acc), access class prohibition will not prevent this second 5GMM-specific procedure or service request procedure from continuing.

[0055] For example, this anomaly can occur when a paging message 416 with an access type set to 3GPP access is received while a UE-initiated 5GMM-specific procedure or service request procedure is in progress. The UE can continue the 5GMM-specific procedure or service request procedure. If the lower layer indicates that the access attempt is prohibited, the UE can handle the pending paging message 416. Otherwise, once the lower layer confirms that the signaling connection has been successfully established, the UE can ignore the paging.

[0056] Similarly, another abnormal situation may occur if, while a 5GMM-specific procedure or service request procedure initiated by a UE on a 3GPP access is in progress, a notification message 408 indicating 3GPP access with the specified access type is received via a non-3GPP access. The UE may continue with the 5GMM-specific procedure or service request procedure. If, for these procedures, the lower layer indicates that the access attempt is prohibited, the UE should handle the pending notification message 408. Otherwise, once the lower layer confirms the successful establishment of the signaling connection, the UE may ignore the notification message 408.

[0057] In other words, if a 5GMM procedure that was not initiated with access class 0 (=MT_acc) fails due to a lower-layer indication that access prohibition applies to all access classes except classes 0 and 2, and if the UE has buffered paging or notification messages, the UE should retry the registration or service request procedure using access class 0 (=MT_acc).

[0058] Figure 5A flowchart illustrates a method 500 for a UE to perform buffering of paging or notification messages while a 5GMM-specific procedure is in progress. In block 502, method 500 initiates a first 5GMM-specific procedure or service request procedure. In block 504, while the first 5GMM-specific procedure or service request procedure is in progress, method 500 receives a message whose access type is set to 3GPP (3rd Generation Partnership Project) access. In block 506, method 500 buffers the message until the first 5GMM-specific procedure or service request procedure ends. In block 508, if the first 5GMM-specific procedure or service request procedure fails due to a lower-layer indication that the access attempt is denied, method 500 initiates a second 5GMM-specific procedure or service request procedure with an access category that was not denied. In block 510, if the first 5GMM-specific procedure or service request succeeds, method 500 ignores the message.

[0059] Figure 6 A method for preventing reference is shown. Figure 3 Signal flow diagram 600 describes a method for MT transaction failure. In this case, no access occurs. Instead, the gNB rejects the connection request due to high load or congestion. The UE-NAS, UE-AS, gNB, AMF, and N3GPP are shown in this signal flow diagram 600. Although the illustrated implementation shows a notification message, a similar failure can occur when a paging message is sent.

[0060] In this scenario, the UE pre-claims and registers 602 on both 3GPP and non-3GPP access modes on the same 5G Public Land Mobile Network (PLMN). Furthermore, in this scenario, the 3GPP access mode is in an idle state, while the non-3GPP access mode is in a connected state.

[0061] As shown in the figure, the UE can initiate a UE-initiated 5GMM-specific procedure or service request procedure 604 with access class 7 (=MO_data). Although the illustrated embodiment shows a 5GMM-specific procedure or service request procedure with access class 7 (=MO_data), the method explained with reference to the figure can occur for any UE-initiated 5GMM-specific procedure or service request procedure with access classes other than 0 and 2 on 3GPP access in idle mode. As part of the UE-initiated 5GMM-specific procedure or service request procedure, UE-NAS sends a 606 setup request message to UE-AS.

[0062] The network can initiate a notification process by sending notification message 608 to the UE. As shown in the figure, in some cases, this can lead to a conflict state when a 5GMM-specific procedure or service request procedure initiated by the UE is still pending and the UE receives a notification. As shown in the figure, in this scenario, the UE receives a notification with access type = 3GPP in a non-3GPP access state before moving to the connected state in the 3GPP domain.

[0063] Due to ongoing 5GMM-specific procedures or service request procedures and the absence of access prohibition, the UE can ignore notification 610. The UE can continue connection establishment by transmitting RRC setup request 612 using an access category that is not category 0 (=MT_acc).

[0064] In this implementation, the network receives a registration request message while T3565 is running. T3565 is a timer started when a notification process instructing a pending MT transaction is initiated. In other words, T3565 indicates that the network is waiting for a response to the notification message. In this case, the network should continue the registration process (instead of ignoring the notification message) and continue the pending MT transaction upon completion of the registration process (i.e., the network initiates an MT call via establishing a signaling connection). In the illustrated implementation, the network handles the request 614 by transmitting an RRC setup message 616 and receiving an RRC setup complete message 618.

[0065] In other words, if the network has already initiated an MT transaction (i.e., has sent a paging message or notification message), the network (gNB and AMF) can continue with received registration-requests or service-requests triggered by an access class other than Access Class 0 (=MT_acc), instead of ignoring the MT transaction. When the registration request or service request process is completed, the network can continue to pending the MT transaction (i.e., the network initiated the MT transaction via establishing a signaling connection).

[0066] For example, in the event of an anomaly where a notification message is transmitted while T3513 is running and the network receives a registration request message, the network can continue the registration process and continue pending MT transactions upon completion of the process. Similarly, in the event of an anomaly where a paging message is transmitted while T3513 is running and the network receives a registration request message, the network can continue the registration process and continue pending MT transactions upon completion of the process. T3513 is a timer started when a paging process indicating pending MT transactions is initiated. In other words, T3513 indicates that the network is waiting for a response to the paging message.

[0067] For example, in the event of an anomaly where a notification message is transmitted while the T3565 is running and the network receives a registration request message or service request message, the network can continue the registration process and continue pending MT transactions upon completion of the process. Similarly, in the event of an anomaly where a paging message is transmitted while the T3565 is running and the network receives a registration request message or service request message, the network can continue the registration process or service request process and continue pending MT transactions upon completion of the process. The T3565 is a timer started when a notification process (where field = 3GPP) indicating pending MT transactions is initiated. In other words, the T3565 indicates that the network is waiting for a response to the notification message.

[0068] Figure 7 A flowchart 700 illustrates a method for preventing missed notifications and paging messages for network nodes. In block 702, method 700 receives a request message from user equipment (UE) while an active timer indicating a pending mobile station called (MT) transaction exists. In block 704, method 700 continues the process associated with the request message while the active timer is running, even if the request message is associated with an access class that may be denied during high load or congestion. In block 706, method 700 continues the MT transaction upon completion of the process.

[0069] Figure 8 Exemplary architectures of system 800 for networks according to various implementations are shown. The following description is provided for an example system 800 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0070] like Figure 8As shown, system 800 includes UE 822 and UE 820. In this example, UE 822 and UE 820 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablet computers, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashboard mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine electronic control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or “smart” appliances, MTC devices, M2M, IoT devices, etc.

[0071] In some implementations, UE 822 and / or UE 820 may be IoT UEs, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices via PLMN, ProSe, or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. An IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0072] UE 822 and UE 820 can be configured to connect to an access node or radio access node (shown as (R)AN 808), for example, through communication coupling. In implementations, (R)AN 808 can be an NG RAN or SG RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to (R)AN 808 operating in an NR or SG system, and the term "E-UTRAN," etc., can refer to (R)AN 808 operating in an LTE or 4G system. UE 822 and UE 820 utilize connections (or channels) (shown as connection 804 and connection 802, respectively), each of which includes a physical communication interface or layer (discussed in further detail below).

[0073] In this embodiment, connection 804 and connection 802 are air interfaces for communication coupling and can be consistent with cellular communication protocols, such as GSM, CDMA network protocols, PTT, POC, UMTS, 3GPP LTE, SG, NR, and / or any other communication protocols discussed herein. In this implementation, UE 822 and UE 820 can also directly exchange communication data via ProSe interface 810. ProSe interface 810 may alternatively be referred to as sidelink (SL) interface 810 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0074] UE 820 is shown configured to access AP 812 (also known as a "WLAN node", "WLAN", "WLAN terminal", "WT", etc.) via connection 824. Connection 824 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 812 will include Wireless Fibre. Router. In this embodiment, AP 812 may connect to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 820, (R)AN 808, and AP 812 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 820 in RRC_CONNECTED being configured by RAN node 814 or RAN node 816 to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 820 using WLAN radio resources (e.g., connection 824) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 824. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0075] (R)AN 808 may include one or more AN nodes, such as RAN node 814 and RAN node 816, that enable connection 804 and connection 802. As used herein, the terms “access node,” “access point,” etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms “NG RAN node,” etc., can refer to a RAN node (e.g., gNB) operating in an NR or SG system, while the terms “E-UT RAN node,” etc., can refer to a RAN node (e.g., eNB) operating in an LTE or 4G system 800. According to various implementation schemes, RAN node 814 or RAN node 816 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity or higher bandwidth compared to macro cells.

[0076] In some implementations, all or some of the RAN nodes in RAN node 814 or RAN node 816 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 814 or RAN node 816); MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 814 or RAN node 816); or “lower PHY” partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes. This virtualization framework allows the idle processor cores of RAN node 814 or RAN node 816 to execute other virtualized applications. In some specific implementations, each RAN node can represent a virtualized application via a different F1 interface. Figure 8(Not shown) Individual gNB-DUs connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio head units or RFEMs, and the gNB-CU may be operated by a server (not shown) located in (R)AN 808 or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of RAN node 814 or RAN node 816 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol termination to UE 822 and UE 820 and is connected to the SGC via the NG interface (discussed below). In V2X scenarios, one or more of RAN nodes 814 or RAN node 816 may be an RSU or act as an RSU.

[0077] The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. An RSU can operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively or in addition to this, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications and other cellular communication services. Alternatively or in addition to this, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0078] RAN node 814 and / or RAN node 816 may terminate the air interface protocol and may be the first point of contact for UE 822 and UE 820. In some implementations, RAN node 814 and / or RAN node 816 may perform various logical functions of (R)AN 808, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0079] In the implementation, UE 822 and UE 820 may be configured to communicate with each other or with any one of RAN nodes 814 and / or RAN node 816 on a multi-carrier communication channel using OFDM communication signals, according to various communication technologies such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0080] In some implementations, the downlink resource grid can be used for downlink transmissions from RAN node 814 and / or RAN node 816 to UE 822 and UE 820, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0081] According to various implementations, UE 822 and UE 820 and RAN node 814 and / or RAN node 816 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0082] To operate in unlicensed spectrum, UE 822 and UE 820, along with RAN node 814 and / or RAN node 816, may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 822 and UE 820, along with RAN node 814 or RAN node 816, may perform one or more known medium sensing and / or carrier sensing operations before transmitting in the unlicensed spectrum to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied. The medium / carrier sensing operations may be performed according to a Talk-After-Listen (LBT) protocol.

[0083] LBT is a mechanism that equipment (e.g., UE 822 and UE 820, RAN node 814 or RAN node 816, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with a predefined or configured threshold.

[0084] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 822, AP812, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between the X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0085] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0086] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides PCCs for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require the UE to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0087] The PDSCH carries user data and higher-layer signaling to UE 822 and UE 820. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 822 and UE 820 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 820 within the cell) can be performed at either RAN node 814 or RAN node 816 based on channel quality information fed back from either UE 822 or UE 820. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each of UE 822 and UE 820.

[0088] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8) can exist.

[0089] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0090] RAN node 814 or RAN node 816 may be configured to communicate with each other via interface 830. In implementations where system 800 is an LTE system (e.g., when CN 806 is an EPC), interface 830 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes connected to the EPC (e.g., two or more eNBs, etc.), and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U may provide flow control mechanisms for user packets transmitted via the X2 interface and may be used to transmit information about the delivery of user data between eNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-order delivery of PDCP PDUs from the SeNB to the UE 822 for user data; information about PDCP PDUs not delivered to the UE 822; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. The X2-C provides LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0091] In implementations where system 800 is an SG or NR system (e.g., when CN 806 is an SGC), interface 830 may be an Xn interface. The Xn interface is defined between two or more RAN nodes connected to the SGC (e.g., two or more gNBs, etc.), between a RAN node 814 (e.g., a gNB) connected to the SGC and an eNB, and / or between two eNBs connected to the 5GC (e.g., CN 806). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 822 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more RAN nodes 814 or RAN nodes 816. Mobility support may include context transfer from the old (source) serving RAN node 814 to the new (destination) serving RAN node 816, and control of the user plane tunnel between the old (source) serving RAN node 814 and the new (destination) serving RAN node 816. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0092] (R)AN 808 is illustrated as being communicatively coupled to the core network—in this embodiment, communicatively coupled to CN 806. CN 806 may include one or more network elements 832 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 822 and UE 820) connected to CN 806 via (R)AN 808. Components of CN 806 may be implemented in a single physical node or in separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instantiation of CN 806 may be referred to as a network slice, and a logical instantiation of a portion of CN 806 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0093] Generally, application server 818 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 818 can also be configured to support one or more communication services for UE 822 and UE 820 via EPC (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.). Application server 818 can communicate with CN 806 through IP communication interface 836.

[0094] In this implementation, CN 806 may be an SGC, and (R)AN 116 may be connected to CN 806 via NG interface 834. In this implementation, NG interface 834 may be divided into two parts: an NG user plane (NG-U) interface 826, which carries traffic data between RAN node 814 or RAN node 816 and the UPF; and an S1 control plane (NG-C) interface 828, which is the signaling interface between RAN node 814 or RAN node 816 and the AMF.

[0095] In one implementation, CN 806 may be an SG CN, while in other implementations, CN 806 may be an EPC. When CN 806 is an EPC, (R)AN 116 may be connected to CN 806 via S1 interface 834. In one implementation, S1 interface 834 may be divided into two parts: an S1 user plane (S1-U) interface 826, which carries traffic data between RAN node 814 or RAN node 816 and the S-GW; and an S1-MME interface 828, which is the signaling interface between RAN node 814 or RAN node 816 and the MME.

[0096] Figure 9 Examples of infrastructure equipment 900 according to various implementation schemes are shown. Infrastructure equipment 900 may be implemented as a base station, radio head unit, RAN node, AN, application server, and / or any other element / device discussed herein. In other examples, infrastructure equipment 900 may be in or implemented by a UE.

[0097] Infrastructure equipment 900 includes application circuitry 902, baseband circuitry 904, one or more radio front-end modules 906 (RFEM), memory circuitry 908, a power management integrated circuit (shown as PMIC 910), a power tee circuitry 912, network controller circuitry 914, a network interface connector 920, satellite positioning circuitry 916, and user interface circuitry 918. In some embodiments, infrastructure equipment 900 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be individually included in more than one device for CRAN, vBBU, or other similar implementations. Application circuitry 902 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: low-dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I... 2The application circuitry 902 may include a C or general-purpose programmable serial interface module, a real-time clock (RTC), timer-counters (including interval timers and watchdog timers), general-purpose input / output (I / O or IO), a memory card controller (such as a Secure Digital (SD) Multimedia Card (MMC) or similar), a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuitry 902 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure apparatus 900. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0098] The processor of application circuit 902 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuit 902 may include or may be a dedicated processor / controller for operation according to the various embodiments herein. For example, the processor of application circuit 902 may include one or more Intel processors. or Processor; Advanced MicroDevices (AMD) Processor, Accelerated Processing Unit (APU) or Processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, the infrastructure equipment 900 may not utilize application circuitry 902, but may instead include a dedicated processor / controller to process, for example, IP data received from an EPC or 5GC.

[0099] In some embodiments, application circuitry 902 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. These hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, programmable processing devices may be one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 902 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such implementations, the circuitry of application circuitry 902 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs). Baseband circuitry 904 may be implemented, for example, as a solderable substrate including one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0100] User interface circuitry 918 may include one or more user interfaces designed to enable a user to interact with infrastructure equipment 900 or peripheral component interfaces, wherein the peripheral component interfaces are designed to enable peripheral components to interact with infrastructure equipment 900. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power interfaces, etc.

[0101] Radio front-end module 906 may include a millimeter-wave (mmWave) radio front-end module (RFEM) and one or more submillimeter-wave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-millimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In another embodiment, both millimeter-wave and submillimeter-wave radio functions may be implemented in the same physical radio front-end module 906 that combines both millimeter-wave and submillimeter-wave antennas.

[0102] The memory circuitry 908 may include one or more of the following: volatile memory, including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as "flash memory"), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may be combined with other components. and A three-dimensional (3D) XPOINT memory. The memory circuit 908 can be implemented as one or more of the following: a solder-in packaged integrated circuit, a socket memory module, and an insert memory card.

[0103] The PMIC 910 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 912 can provide power drawn from the network cable to provide both power and data connectivity to the infrastructure equipment 900 using a single cable.

[0104] Network controller circuitry 914 can provide connectivity to the network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol. Network connectivity can be provided to / from infrastructure equipment 900 via a physical connection via network interface connector 920, which can be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuitry 914 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, network controller circuitry 914 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0105] Positioning circuit 916 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the U.S. Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler orbit chart and satellite integrated radio positioning (DORIS), etc.). Positioning circuit 916 includes various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) for facilitating OTA communication to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, positioning circuit 916 may include a micro-technology (micro PNT) IC for positioning, navigation, and timing, which performs position tracking / estimation using a master timing clock in the absence of GNSS assistance. The positioning circuit 916 may also be part of or interact with the baseband circuit 904 and / or the radio front-end module 906 to communicate with nodes and components of the positioning network. The positioning circuit 916 may also provide location data and / or time data to the application circuit 902, which may use the data to synchronize operations with various infrastructures, etc. Figure 9 The components shown can communicate with each other using interface circuitry, which may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCix), PCI Express (PCie), or any number of other technologies. The bus / IX may be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems, such as I... 2 Interfaces include C-type interface, SPI interface, point-to-point interface, and power bus, etc.

[0106] Figure 10 Examples of platform 1000 according to various embodiments are shown. In embodiments, computer platform 1000 may be adapted to function as a UE, application server, and / or any other element / device discussed herein. Platform 1000 may include any combination of the components shown in the examples. Components of platform 1000 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted in computer platform 1000, or may be implemented as components otherwise integrated within the chassis of a larger system. Figure 10The block diagram is intended to show a high-level view of the components of the computer platform 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific embodiments.

[0107] Application circuit 1002 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: LDO, interrupt controller, serial interface (such as SPI), I / O, etc. 2 The application circuit 1002 includes a C or general-purpose programmable serial interface module, an RTC, timer-counters (including interval timers and watchdog timers), general-purpose I / O, a memory card controller (such as an SD MMC or similar), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 1002 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on platform 1000. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0108] The processor of application circuit 1002 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, application circuit 1002 may include or may be a dedicated processor / controller for operation according to various embodiments herein.

[0109] For example, the processor of application circuit 1002 may include a processor based on... Architecture Core TM processors, such as Quark TM Atom TM i3, i5, i7 or MCU-level processors, or available from Another such processor from the Corporation. The processor for application circuit 1002 may also be one or more of the following: Advanced Micro Devices (AMD). Processor or Accelerated Processing Unit (APU); from Inc.'s AS-A9 processor, from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments OpenMultimedia Applications Platform(OMAP) TM Processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some specific implementations, application circuitry 1002 may be part of a system-on-a-chip (SoC), where application circuitry 1002 and other components are formed as a single integrated circuit or a single package, such as... company( Edison Corporation TM Or Galileo TM SoC board.

[0110] In addition to or alternatively, application circuit 1002 may include circuitry such as, but not limited to, one or more of, the following: field-programmable devices (FPDs), such as FPGAs; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuit 1002 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such embodiments, the circuitry of application circuit 1002 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs).

[0111] The baseband circuit 1004 may be implemented, for example, as a soldered substrate, which includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0112] The radio front-end module 1006 may include a millimeter-wave (mmWave) radio front-end module (RFEM) and one or more submillimeter-wave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-millimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In another embodiment, both millimeter-wave and submillimeter-wave radio functions may be implemented in the same physical radio front-end module 1006 that combines both millimeter-wave and submillimeter-wave antennas.

[0113] The memory circuit 1008 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 1008 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SD RAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 1008 may be developed according to the Joint Electronic Equipment Committee (JEDEC) design based on low-power double data rate (LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 1008 may be implemented as one or more of the following: solder-in packaged integrated circuit, single-die package (SDP), dual-die package (DDP), or quad-die package (Q17P), socket memory module, dual in-line memory module (DIMM) including micro DIMM or mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 1008 may be an on-chip memory or register associated with the application circuit 1002. To provide persistent storage for information such as data, applications, operating systems, etc., the memory circuit 1008 may include one or more mass storage devices, which may include, in particular, solid-state drives (SSDDs), hard disk drives (HDDs), miniature HDDs, resistance-changing memory, phase-change memory, holographic memory, or chemical memory. For example, the computer platform 1000 may be integrated with... and 3D XPOINT memory.

[0114] The removable memory 1026 may include devices, circuitry, enclosures / housings, ports, or sockets for coupling portable data storage devices to the platform 1000. These portable data storage devices can be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, Micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical discs, external HDDs, etc.

[0115] Platform 1000 may also include interface circuitry (not shown) for connecting external devices to platform 1000. External devices connected to platform 1000 via this interface circuitry include sensor 1022 and electromechanical components (shown as EMC 1024), as well as a removable memory device coupled to removable memory 1026.

[0116] Sensor 1022 includes devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, and / or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0117] EMC 1024 includes devices, modules, or subsystems intended to enable platform 1000 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, EMC 1024 can be configured to generate messages / signaling and send messages / signaling to other components of platform 1000 to indicate the current state of EMC 1024. Examples of EMC 1024 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, propellers, pawls, clamps, hooks, and / or other similar electromechanical components. In embodiments, platform 1000 is configured to operate one or more EMC 1024s based on one or more captured events and / or commands or control signals received from a service provider and / or various clients. In some specific implementations, the interface circuitry connects platform 1000 to positioning circuitry 1016. Positioning circuit 1016 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) may include the US GPS, Russia's GLONASS, the EU's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.). Positioning circuit 1016 includes various hardware components (e.g., hardware devices for facilitating OTA communication, such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, positioning circuit 1016 may include a miniature PNT IC that performs position tracking / estimation using a master timing clock without GNSS assistance. Positioning circuit 1016 may also be part of or interact with baseband circuitry 1004 and / or radio front-end module 1006 to communicate with nodes and components of the positioning network. The positioning circuit 1016 can also provide location data and / or time data to the application circuit 1002, which can use the data to synchronize operations with various infrastructures (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0118] In some implementations, this interface circuitry can connect platform 1000 to a near-field communication circuitry (shown as NFC circuitry 1012). NFC circuitry 1012 is configured to provide contactless short-range communication based on a radio frequency identification (RFID) standard, where a magnetic field sensor is used to enable communication between NFC circuitry 1012 and NFC-enabled devices (e.g., “NFC contact points”) external to platform 1000. NFC circuitry 1012 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to NFC circuitry 1012 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals may power passive NFC tags (e.g., microchips embedded in stickers or wristbands) to transmit stored data to NFC circuitry 1012, or initiate data transfer between NFC circuitry 1012 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) located near platform 1000.

[0119] The driving circuit 1018 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1000. The driving circuit 1018 may include various drivers that allow other components of the platform 1000 to interact with or control various input / output (I / O) devices that may exist within or be connected to the platform. For example, the driving circuit 1018 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 1000; a sensor driver for acquiring sensor readings of the sensor 1022 and controlling and allowing access to the sensor 1022; an EMC driver for acquiring the actuator position of the EMC 1024 and / or controlling and allowing access to the EMC 1024; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0120] A power management integrated circuit (shown as PMIC 1010) (also referred to as a "power management circuit") manages the power supplied to various components of platform 1000. Specifically, relative to baseband circuit 1004, PMIC 1010 controls power selection, voltage scaling, battery charging, or DC-DC conversion. PMIC 1010 is typically included when platform 1000 can be powered by battery 1014, for example, when the device is included in a UE.

[0121] In some implementations, the PMIC 1010 can be controlled or otherwise integrated into various power-saving mechanisms of the platform 1000. For example, if the platform 1000 is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the platform 1000 can power down for short intervals to conserve power. If there is no data service activity for an extended period, the platform 1000 can transition to the RRC_Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 1000 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network and then power down again. The platform 1000 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0122] Battery 1014 can power platform 1000, but in some examples, platform 1000 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 1014 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, battery 1014 may be a typical lead-acid automotive battery.

[0123] In some implementations, battery 1014 may be a "smart battery," which includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in platform 1000 to track the state of charge (SoCh) of battery 1014. The BMS can be used to monitor other parameters of battery 1014, such as the state of health (SoH) and state of function (SoF) of battery 1014, to provide fault prediction. The BMS can transmit information about battery 1014 to application circuitry 1002 or other components of platform 1000. The BMS may also include an analog-to-digital converter (ADC) that allows application circuitry 1002 to directly monitor the voltage of battery 1014 or the current from battery 1014. Battery parameters can be used to determine actions that platform 1000 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0124] A power block coupled to the power grid or other power source can be coupled to the BMS to charge the battery 1014. In some examples, a wireless power receiver can replace the power block to wirelessly acquire power, for example, via a loop antenna in the computer platform 1000. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuitry chosen may depend on the size of the battery 1014 and therefore on the required current. Charging can be performed using the aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Radio Power Alliance, or the Rezence charging standard published by the Radio Power Alliance.

[0125] User interface circuitry 1020 includes various input / output (I / O) devices present within or connected to platform 1000, and includes one or more user interfaces designed to enable user interaction with platform 1000 and / or peripheral component interfaces designed to enable interaction with peripheral components of platform 1000. User interface circuitry 1020 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual device for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, particularly one or more simple visual outputs / indicators (such as binary status indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of platform 1000. The output device circuitry may also include speakers or other audio transmitting devices, printers, etc. In some embodiments, sensor 1022 may be used as input device circuitry (e.g., image capture devices, motion capture devices, etc.) and one or more EMCs may be used as output device circuitry (e.g., actuators for providing haptic feedback, etc.). In another example, NFC circuitry may be included for reading electronic tags and / or connecting to another NFC-enabled device, the NFC circuitry including an NFC controller and processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0126] Although not shown, components of Platform 1000 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be a proprietary bus / IX, for example, used in a SoC-based system. Other bus / IX systems, such as I... 2 Interfaces include C-type interface, SPI interface, point-to-point interface, and power bus, etc.

[0127] Figure 11 Example components of device 1100 according to some embodiments are shown. In some embodiments, device 1100 may include at least application circuitry 1106, baseband circuitry 1104, radio frequency (RF) circuitry (shown as RF circuitry 1102), front-end module (FEM) circuitry (shown as FEM circuitry 1132), one or more antennas 1130, and power management circuitry (PMC) (shown as PMC 1134) coupled together as shown. Components of the illustrated device 1100 may be included in a UE or RAN node. In some embodiments, device 1100 may include fewer components (e.g., the RAN node may not utilize application circuitry 1106, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 1100 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the following components may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0128] Application circuitry 1106 may include one or more application processors. For example, application circuitry 1106 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 1100. In some embodiments, the processor of application circuitry 1106 may process IP data packets received from the EPC.

[0129] Baseband circuit 1104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1104 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 1102 and generate baseband signals for the transmit signal path of RF circuit 1102. Baseband circuit 1104 may interact with application circuitry 1106 to generate and process baseband signals and control the operation of RF circuit 1102. For example, in some embodiments, baseband circuit 1104 may include a third-generation (3G) baseband processor (3G baseband processor 1108), a fourth-generation (4G) baseband processor (4G baseband processor 1110), a fifth-generation (5G) baseband processor (5G baseband processor 1112), or other existing, under development, or future generations of baseband processors 1114 (e.g., second-generation (2G), sixth-generation (6G), etc.). Baseband circuitry 1104 (e.g., one or more baseband processors in a baseband processor suite) can handle various radio control functions capable of communicating with one or more radio networks via RF circuitry 1102. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in memory 1120 and may be executed via a central processing unit (CPU 1116). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1104 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1104 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0130] In some embodiments, the baseband circuit 1104 may include a digital signal processor (DSP), such as one or more audio DSPs 1118. The one or more audio DSPs 1118 may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuit may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1104 and the application circuit 1106 may be implemented together, for example, on a system-on-a-chip (SoC).

[0131] In some implementations, baseband circuit 1104 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1104 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 1104 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0132] RF circuit 1102 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1102 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1102 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 1132 and providing a baseband signal to baseband circuit 1104. RF circuit 1102 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1104 and providing an RF output signal for transmission to FEM circuit 1132.

[0133] In some embodiments, the receive signal path of RF circuit 1102 may include mixer circuit 1122, amplifier circuit 1124, and filter circuit 1126. In some embodiments, the transmit signal path of RF circuit 1102 may include filter circuit 1126 and mixer circuit 1122. RF circuit 1102 may also include synthesizer circuit 1128 for synthesizing frequencies used by mixer circuit 1122 for both the receive and transmit signal paths. In some embodiments, mixer circuit 1122 for the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1132 based on the synthesized frequency provided by synthesizer circuit 1128. Amplifier circuit 1124 may be configured to amplify the down-converted signal, and filter circuit 1126 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1104 for further processing. In some implementations, although not required, the output baseband signal may be a zero-frequency baseband signal. In some implementations, the mixer circuit 1122 of the receiving signal path may include a passive mixer, but the scope of the implementations is not limited in this respect.

[0134] In some implementations, the mixer circuit 1122 of the transmit signal path may be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1128 to generate an RF output signal for the FEM circuit 1132. The baseband signal may be provided by the baseband circuit 1104 and may be filtered by the filter circuit 1126.

[0135] In some embodiments, the mixer circuit 1122 for the receive signal path and the mixer circuit 1122 for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 1122 for the receive signal path and the mixer circuit 1122 for the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1122 for the receive signal path and the mixer circuit 1122 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1122 for the receive signal path and the mixer circuit 1122 for the transmit signal path may be configured for superheterodyne operation.

[0136] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1102 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1104 may include a digital baseband interface for communicating with the RF circuit 1102.

[0137] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0138] In some implementations, synthesizer circuit 1128 may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1128 may be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0139] Synthesizer circuit 1128 can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1122 of RF circuit 1102. In some embodiments, synthesizer circuit 1128 may be a fractional N / N+1 synthesizer.

[0140] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1104 or the application circuit 1106 (such as an application processor) according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1106.

[0141] The synthesizer circuit 1128 of the RF circuit 1102 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0142] In some embodiments, synthesizer circuitry 1128 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 1102 may include an IQ / polarity converter.

[0143] FEM circuit 1132 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1130, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1102 for further processing. FEM circuit 1132 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1102 for transmission by one or more of the one or more antennas 1130. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1102, only in FEM circuit 1132, or in both RF circuit 1102 and FEM circuit 1132.

[0144] In some embodiments, FEM circuit 1132 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 1132 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 1132 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 1102). The transmit signal path of FEM circuit 1132 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 1102), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more antennas in the one or more antennas 1130).

[0145] In some implementations, the PMC 1134 manages the power supplied to the baseband circuitry 1104. Specifically, the PMC 1134 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1134 is typically included when the device 1100 is capable of being battery powered, for example, when the device 1100 is included in a UE. The PMC 1134 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0146] Figure 11 PMC 1134 is shown coupled only to baseband circuit 1104. However, in other embodiments, PMC 1134 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuit 1106, RF circuit 1102, or FEM circuit 1132) and perform similar power management operations for these components.

[0147] In some implementations, the PMC 1134 may control various power-saving mechanisms of device 1100 or otherwise become part of such mechanisms. For example, if device 1100 is in the RRC_Connected state, where it remains connected to the RAN node as it expects to receive traffic immediately, it may enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 1100 may be powered down for short intervals, thereby saving power.

[0148] If there is no data traffic activity during the extended period, device 1100 may transition to the RRC_Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1100 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 1100 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.

[0149] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0150] The processors of application circuit 1106 and baseband circuit 1104 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuit 1104 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 1106 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include the radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include the media access control (MAC) layer, radio link control (RLC) layer, and packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0151] Figure 12 An exemplary interface 1200 of a baseband circuit according to some embodiments is shown. As discussed above, Figure 11 The baseband circuit 1104 may include a 3G baseband processor 1108, a 4G baseband processor 1110, a 5G baseband processor 1112, other baseband processors 1114, a CPU 1116, and a memory 1120 used by the processors. As shown, each processor may include a corresponding memory interface 1202 for sending / receiving data to / from the memory 1120.

[0152] Baseband circuit 1104 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 1204 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 1104); application circuit interface 1206 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1104); and application circuit interface 1206 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1104). Figure 11 Application circuit 1106 (interface for sending / receiving data); RF circuit interface 1208 (e.g., for sending / receiving data to / from...). Figure 11 The RF circuit 1102 is an interface for transmitting / receiving data; the wireless hardware connection interface 1210 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) (low power consumption) Interface for sending / receiving data to / from components and other communication components); and power management interface 1212 (e.g., an interface for sending / receiving power or control signals to / from PMC 1134).

[0153] Figure 13 This is a block diagram illustrating a component 1300, according to some exemplary embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of executing any or more of the methods discussed herein. Specifically, Figure 13 A schematic diagram of hardware resource 1302 is shown, which includes one or more processors 1306 (or processor cores), one or more memory / storage devices 1314, and one or more communication resources 1324, each of which is communicatively coupled via bus 1316. For implementations utilizing node virtualization (e.g., NFV), an executable hypervisor 1322 can be used to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1302.

[0154] Processor 1306 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1308 and processor 1310.

[0155] The memory / storage device 1314 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1314 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0156] Communication resource 1324 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1304 or one or more databases 1320 via network 1318. For example, communication resource 1324 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g.) (low power consumption) Components and other communication components.

[0157] Instruction 1312 may include software, programs, applications, applets, or other executable code for causing at least one processor in processor 1306 to perform any or more of the methods discussed herein. Instruction 1312 may reside wholly or partially within at least one of processors 1306 (e.g., within the processor's cache memory), memory / storage device 1314, or any suitable combination thereof. Furthermore, any portion of instruction 1312 may be transferred from peripheral device 1304 or database 1320 to hardware resource 1302. Therefore, the memory of processor 1306, memory / storage device 1314, peripheral device 1304, and database 1320 are examples of computer-readable and machine-readable media.

[0158] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0159] Example Section

[0160] The following examples relate to other implementation schemes.

[0161] Example 1. A method for a user equipment (UE), the method comprising: initiating a first 5GMM-specific procedure or service request procedure; while the first 5GMM-specific procedure or service request procedure is in progress, receiving a message having an access type set to 3GPP access; buffering the message until the first 5GMM-specific procedure or service request procedure ends; and if the first 5GMM-specific procedure or service request procedure fails due to a lower layer indicating that the access attempt is prohibited, initiating a second 5GMM-specific procedure or service request procedure having an access class that is not prohibited from handling the message.

[0162] Example 2. The method according to Example 1, wherein the access category of the second 5GMM specific process or service request process is access category 0 (= Mobile station called (MT) access).

[0163] Example 3. According to the method of Example 1, the method further includes: if the first 5GMM specific process or service request is successful, then the message is ignored.

[0164] Example 4. The method according to Example 1, wherein if these lower-layer indication access prohibition applies to all access categories other than categories 0 and 2 and the first 5GMM-specific procedure or service request procedure is set to a category other than 0 or 2, then the first 5GMM-specific procedure or service request procedure is prohibited.

[0165] Example 5. The method according to Example 1, wherein the message includes a received paging message having the access type set to 3GPP access.

[0166] Example 6. The method according to Example 1, wherein the message includes a notification message received via a non-3GPP access that indicates the 3GPP access type.

[0167] Example 7. According to the method of Example 1, the method further includes: if the first 5GMM specific process or service request process is successful, then the MT transaction associated with the message continues.

[0168] Example 8. A user equipment (UE) comprising: a baseband processing unit; and a memory storing instructions that, when executed by the baseband processing unit, configure the UE to: initiate a first 5GMM-specific procedure or service request procedure; while the first 5GMM-specific procedure or service request procedure is in progress, receive a message having an access type set to 3GPP access; buffer the received message until the first 5GMM-specific procedure or service request procedure ends; and if the first 5GMM-specific procedure or service request procedure fails due to a lower-layer indication that the access attempt is prohibited, initiate a second 5GMM-specific procedure or service request procedure having an access class that is not prohibited from handling the message.

[0169] Example 9. The UE according to Example 8, wherein the access category of the second 5GMM specific procedure or service request procedure is category 0 (= Mobile station called (MT) access).

[0170] Example 10. The UE according to Example 8, wherein these instructions further configure the UE to ignore the message if the first 5GMM specific procedure or service request is successful.

[0171] Example 11. The UE according to Example 8, wherein if these lower layer indication access prohibition applies to all access categories other than categories 0 and 2 and the first 5GMM specific procedure or service request procedure is set to a category other than 0 or 2, then the first 5GMM specific procedure or service request procedure is prohibited.

[0172] Example 12. The UE according to Example 8, wherein the message includes a received paging message having the access type set to the 3GPP access.

[0173] Example 13. The UE according to Example 8, wherein the message includes a notification message received via a non-3GPP access that indicates the 3GPP access type.

[0174] Example 14. The UE according to Example 8, wherein these instructions further configure the UE to continue the MT transaction associated with the received message if the first 5GMM specific procedure or service request procedure is successful.

[0175] Example 15. A method for a network node, the method comprising: receiving a request message from a user equipment (UE) when an active timer indicating a pending mobile station called (MT) transaction exists; continuing a process associated with the request message while the active timer is running; and continuing the MT transaction upon completion of the process.

[0176] Example 16. The method according to Example 15, wherein the activity timer starts when a paging process is initiated or a notification message has been sent to the UE.

[0177] Example 17. The method according to Example 15, wherein the request message is a registration request.

[0178] Example 18. The method according to Example 15, wherein the request message is a service request.

[0179] Example 19. The method according to Example 18, wherein the request message is triggered using an access category that is not used for MT access.

[0180] Example 20. The method according to Example 15, further comprising: continuing the pending MT transaction after completing the registration request or service request.

[0181] Example 21 may include an apparatus comprising one or more elements for performing any of the methods described or associated with any of the above embodiments or any other methods or processes described herein.

[0182] Example 22 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of any of the methods or processes described or associated with any of the above embodiments or any other methods or processes described herein.

[0183] Example 23 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the methods described or associated with any of the above embodiments or any other methods or processes described herein.

[0184] Example 24 may include any of the methods, techniques, or processes described or associated with any of the above examples, or any part or component thereof.

[0185] Embodiment 52C may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described in or associated with any of the above embodiments.

[0186] Example 26 may include any of the signals or parts or components described or associated with any of the above examples.

[0187] Example 27 may include any datagram, packet, frame, segment, protocol data unit (PDU) or message or part or component thereof described or associated with any of the above examples, or other content described in this disclosure.

[0188] Example 28 may include any of the data-encoded signals or parts thereof described or associated with any of the above examples, or other content described in this disclosure.

[0189] Example 29 may include signals or parts thereof encoded as datagrams, packets, frames, segments, PDUs or messages as described or associated with any of the above examples, or other content described in this disclosure.

[0190] Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0191] Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0192] Example 32 may include signals in a wireless network as shown and described herein.

[0193] Example 33 may include methods for communicating in a wireless network as shown and described herein.

[0194] Example 34 may include a system for providing wireless communication as shown and described herein.

[0195] Example 35 may include a device for providing wireless communication as shown and described herein.

[0196] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0197] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical components for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0198] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in another implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0199] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0200] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for a user equipment (UE), the method comprising: initiating a first Fifth Generation Mobility Management (5GMM)-specific procedure or service request procedure; while the first 5GMM-specific procedure or service request procedure is in progress, receiving a message with an access type set to a Third Generation Partnership Project (3GPP) access; buffering the message until the first 5GMM-specific procedure or service request procedure ends; and if the first 5GMM-specific procedure or service request procedure fails due to a lower layer indication of barring access attempts, initiating a second 5GMM-specific procedure or service request procedure with an access category that does not bar handling of the message.

2. The method of claim 1, wherein the access category of the second 5GMM-specific procedure or service request procedure is Access Category 0 = Mobile Terminated (MT) access. ignoring the message if the first 5GMM-specific procedure or service request is successful.

3. The method of claim 1, further comprising:

4. The method of claim 1, wherein the first 5GMM-specific procedure or service request procedure is barred if the lower layer indicates that access barring applies to all access categories except categories 0 and 2 and the first 5GMM-specific procedure or service request procedure is set to a category other than 0 or 2.

5. The method of claim 1, wherein the message comprises a paging message received with the access type set to the 3GPP access.

6. The method of claim 1, wherein the message comprises a notification message received via a non-3GPP access with the access type indicating the 3GPP access. continuing with an MT transaction associated with the message if the first 5GMM-specific procedure or service request procedure is successful.

7. The method of claim 1, further comprising:

8. A user equipment (UE), the UE comprising: a baseband processing unit; and a memory storing instructions that, when executed by the baseband processing unit, configure the UE to: initiate a first Fifth Generation Mobility Management (5GMM)-specific procedure or service request procedure; while the first 5GMM-specific procedure or service request procedure is in progress, receive a message with an access type set to a Third Generation Partnership Project (3GPP) access; buffer the received message until the first 5GMM-specific procedure or service request procedure ends; and if the first 5GMM-specific procedure or service request procedure fails due to a lower layer indication of barring access attempts, initiate a second 5GMM-specific procedure or service request procedure with an access category that does not bar handling of the message.

9. The UE of claim 8, wherein the access category of the second 5GMM-specific procedure or service request procedure is category 0 = Mobile Terminated (MT) access.

10. The UE of claim 8, wherein the instructions further configure the UE to ignore the message if the first 5GMM-specific procedure or service request is successful. ​ ​ ​ 11. The UE of claim 8, wherein the first 5GMM specific procedure or service request procedure is barred if the lower layers indicate that barring of access applies to all access categories except categories 0 and 2 and the first 5GMM specific procedure or service request procedure is set to a category other than 0 or 2.

12. The UE of claim 8, wherein the message comprises a paging message received with the access type set to the 3GPP access.

13. The UE of claim 8, wherein the message comprises a notification message received via a non-3GPP access with the access type indicating the 3GPP access.

14. The UE of claim 8, wherein the instructions further configure the UE to, if the first 5GMM specific procedure or service request procedure is successful, continue with an MT transaction associated with the received message.

15. A computer-readable storage medium comprising instructions that, when executed by a user equipment (UE), cause the UE to: initiate a first Fifth Generation Mobility Management (5GMM) specific procedure or service request procedure; receive a message with an access type set to a Third Generation Partnership Project (3GPP) access while the first 5GMM specific procedure or service request procedure is ongoing; buffer the message until the first 5GMM specific procedure or service request procedure ends; and if the first 5GMM specific procedure or service request procedure fails due to lower layers indicating barring of access attempts, initiate a second 5GMM specific procedure or service request procedure with an access category that is not barred from handling the message.

16. The computer-readable storage medium of claim 15, wherein the access category of the second 5GMM specific procedure or service request procedure is access category 0 = Mobile Terminated (MT) access.

17. The computer-readable storage medium of claim 15, wherein the instructions, when executed by the UE, further cause the UE to, if the first 5GMM specific procedure or service request is successful, ignore the message.

18. The computer-readable storage medium of claim 15, wherein the first 5GMM specific procedure or service request procedure is barred if the lower layers indicate that barring of access applies to all access categories except categories 0 and 2 and the first 5GMM specific procedure or service request procedure is set to a category other than 0 or 2.

19. The computer-readable storage medium of claim 15, wherein the message comprises a paging message received with the access type set to the 3GPP access.

20. The computer-readable storage medium of claim 15, wherein the message comprises a notification message received via a non-3GPP access with the access type indicating the 3GPP access. ​ ​ ​ ​ ​ 21. The computer-readable storage medium of claim 15, the instructions of which, when executed by the UE, further cause the UE to continue an MT transaction associated with the message if the first 5GMM-specific procedure or service request procedure is successful.

Images