Method and user equipment for performing reconstruction procedure

By monitoring the integrity check failure indication and entering RRC_IDLE mode, the infinite loop problem that UEs may have in LTE and NR is solved, ensuring that UEs take consistent action when encountering failures, and improving network predictability and stability.

CN118945896APending Publication Date: 2024-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411359031.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-11-01
Filing Date
2019-08-29
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In LTE and NR, after receiving the integrity check failure indication, the UE may cause infinite loops or unpredictable behavior, especially during reconstruction, which causes the UE to get stuck on the same cell, and the existing specifications are ambiguity, resulting in different The UE takes different actions.

Method used

By monitoring the integrity check failure indication received from the lower layer, enter the RRC_IDLE operation mode, indicate the connection failure to the upper layer, and trigger the recovery process, ensuring that the UE takes consistent actions when encountering the integrity verification failure, avoid false base station actions, and Perform cell selection or reselect if necessary.

Benefits of technology

解决了UE在完整性检查失败后可能出现的无限循环问题,确保了UE在遇到故障时能够预测性地采取行动,避免卡在同一小区,提高了网络的可预测性和稳定性。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945896A_ABST
    Figure CN118945896A_ABST
Patent Text Reader

Abstract

Embodiments described herein relate to a method and apparatus for performing a reconstruction process. A method in user equipment comprises: receiving a reestablishment message; upon receiving the reestablishment message, monitoring an indication of an integrity check failure received from a lower layer, where the indication relates to a first message or a second message received by the UE after transmitting the reestablishment request; in response to an indication that the integrity check fails, performing an action upon entering the RRCIDLE mode of operation; indicating connection failure to a higher layer; and based on the indication, triggering a recovery process over the upper layer.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments described herein relate to methods and apparatus for performing a reconstruction process. Background Art

[0002] In general, all terms used herein will be interpreted according to their common meaning in the relevant technical field, unless clearly given and / or implied different meanings in the context in which it is used. All references to one / an / element, equipment, assembly, part, step, etc. are openly interpreted as referring to at least one instance of this element, equipment, assembly, part, step, etc., unless clearly pointed out otherwise. The steps of any method disclosed herein are not necessarily performed in the exact order disclosed, unless a certain step is clearly described as after or before another step, and / or it is implied that a certain step must be after or before another step. Where appropriate, any of any features in the embodiments disclosed herein may be applied to any other embodiment. Similarly, any of any advantages in the embodiments may be applied to any other embodiment, and vice versa. Other purposes, features and advantages of the attached embodiments will be clear from the following description.

[0003] Reestablishment process in LTE In LTE, according to 3GPP TS 36.331, the re-establishment procedure is triggered under different failure detection situations, including when the UE is in RRC_CONNECTED and receives an indication from lower layers that integrity verification of signalling radio bearer SRB1 or SRB2 has failed. This is shown in the following excerpt from 36.331: ***start extract************************************************* 5.3.7.2 Startup The UE shall initiate this procedure only when AS security has been activated or only for NB-IoT UEs that support RRC connection reestablishment for control plane CIoTEPS optimization. The UE initiates this procedure when one of the following conditions is met: 1> When a radio link failure is detected, according to 5.3.11; or 1> When the switch fails, follow 5.3.5.6; or 1> When mobility on the E-UTRA side fails, according to 5.4.3.5; or 1> when an indication is received from the lower layer that the integrity check of SRB1 or SRB2 has failed; or 1> When RRC connection reconfiguration fails, according to 5.3.5.5; or 1> When RRC connection reconfiguration fails, according to TS38.331[82,5.3.5.5]. ***Finish extract**************************************************

[0004] Definition from the above excerpt: AS = Access Layer NB-IoT = Narrowband Internet of Things RRC = Radio Resource Control CIoT EPS = Consumer IoT Evolved Packet System E-UTRA = Evolved Universal Terrestrial Radio Access When the received message is an RRCConnectionReconfiguration message, an indication from a lower layer that integrity verification of signaling radio bearer SRB1 or SRB2 has failed may be sent.

[0005] Another relevant aspect is that once reestablishment is initiated, the UE sends an RRCConnectionReestablishmentRequest on SRB0 (i.e., without encryption and integrity protection), in which case it typically receives an RRCConnectionReestablishment in response on SRB0 (i.e., without encryption and integrity protection), and after starting security, sends an RRCConnectionReestablishmentComplete message on SRB1. This is as shown in Fig.10 The following signaling flow from 36.331 is shown in FIG.

[0006] Another related aspect to mention is that since the RRCConnectionReestablishment message, so the UE relies on the first RRCConnectionReconfiguration message after the re-establishment procedure (the message on SRB1, i.e., the integrity-protected and encrypted message) to recover DRBs and SRBs (except SRB0 and SRB1).

[0007] Reconstruction process in NR Some aspects may be enhanced to speed up failure recovery in situations such as handover failures. Some of these aspects are as follows: -RRCReestablishment on SRB1: Before submitting MSG3 to lower layers, there may be no fundamental reason why the UE cannot reestablish the Packet Data Convergence Protocol (PDCP) for SRB1 and resume SRB1 in the downlink (DL). This will make it possible to use SRB1 instead of SRB0 for MSG4, which in turn will make it possible to send a subsequent RRC reconfiguration message together with MSG4 or directly instead of waiting for the UE response in MSG5. This will save the round trip time to reestablish the data radio bearer (DRB).

[0008] -RRCSetup in response to RRCReestablishmentRequest: If the Radio Access Network (RAN) cannot reestablish the UE context, for example, the cell is not ready during a handover failure, it is possible to support faster Non-Access Stratum (NAS) recovery in the RAN. This can be done by the network sending an RRC Connection Setup message (instead of RRC Reestablishment Reject) over SRB0, which can be used to start a normal RRC Connection Setup.

[0009] - Remove RRCReestablishmentReject: Due to the fallback procedure, this message may no longer be needed. If the UE attempts to reestablish in a cell where the DRB is not ready or the network cannot reestablish, the network may send an RRCSetup message. In the scenario of cell overload, the network may just wait for the failure timer T301 to expire so that the user equipment (UE) enters RRC_IDLE and performs access before trying again.

[0010] Fig.11 The reconstruction process in NR adopting these aspects is described.

[0011] In step 1, the UE reestablishes the connection in order to provide the UE identity (physical cell identity (PCI) + cell radio network temporary identifier (C-RNTI)) to the base station (e.g., gNB) where the reestablishment trigger occurs.

[0012] In step 2, if the UE context is not available locally, the gNB requests the previous serving gNB to provide the UE context data.

[0013] In step 3, the previous serving gNB provides UE context data.

[0014] In step 4 / 4a, the gNB continues to reestablish the RRC connection. This message is sent on SRB1.

[0015] In step 5 / 5a, while the re-establishment process is in progress, the gNB may perform reconfiguration in order to re-establish SRB2 and DRB.

[0016] In step 6, the gNB provides the forwarding address if loss of DL user data buffered in the previous serving gNB should be prevented.

[0017] In step 7 / 8, the gNB performs path switching.

[0018] In step 9, the gNB triggers the release of UE resources at the previous serving gNB.

[0019] Integrity protection of messages in LTE and NR In Long Term Evolution (LTE) and NR, integrity protection of messages is performed in the PDCP by calculating the Message Authentication Code-Integrity (MAC-I) contained in the Packet Data Convergence Protocol (PDCP) header in the network and UE. The MAC-I is a security checksum calculated using an integrity protection algorithm. When the receiver receives a PDCP packet, it calculates and verifies the MAC-I using the same inputs and algorithms as the transmitter, so that each side can be authenticated. MAC-I derivation is specified in TS 33.401 and TS 33.501 for EPS and 5G System (5GS), respectively, but the only difference is which algorithms are applied. For LTE connected to the EPC or 5GC, the algorithms used are defined in TS 33.401, while for NR, the algorithms used are defined in 33.501. Unlike the MAC-I, which is contained in and verified by the PDCP layer, the security token is contained and verified at the RRC layer.

[0020] The following is an excerpt from the 5G security specification used to derive the MAC-I (see section D.3.1.1 in 3GPP TS 33.501): ***start extract************************************************* D.3.1.1 Input and output The input parameters of the integrity algorithm are a 128-bit integrity key called KEY, a 32-bit COUNT, a 5-bit bearer identity called BEARER, a 1-bit transmission direction (i.e., DIRECTION), and the message itself (i.e., MESSAGE). The DIRECTION bit for the uplink should be 0, and the DIRECTION bit for the downlink should be 1. The bit length of MESSAGE is LENGTH.

[0021] Fig.12 The use of integrity algorithm NIA to authenticate the integrity of the message is shown.

[0022] Based on these input parameters, the sender uses the integrity algorithm NIA to calculate a 32-bit message authentication code (MAC-I / NAS-MAC). The message authentication code is then appended to the message when it is sent. For the integrity protection algorithm, the receiver calculates the expected message authentication code (XMAC-I / XNAS-MAC) on the received message in the same way as the sender calculates its message authentication code on the sent message, and verifies the data integrity of the message by comparing it with the received message authentication code (i.e., MAC-I / NAS-MAC). ***Finish extract**************************************************

[0023] There are some challenges. There are different problems in LTE and NR, which fundamentally depends on whether the RRC Reestablishment type message or re-establishment message (e.g., RRCReestablishment in NR or RRCConnectionReestablishment in LTE) is sent on SRB0 as in LTE (i.e., unprotected and unencrypted) or on SRB1 as in NR (i.e., encrypted and integrity protected).

[0024] In the LTE case, since this message is sent on SRB0, the UE relies on the first RRCConnectionReconfiguration message sent on SRB1 after completing the reestablishment process to restore the SRBs and DRBs. However, after the reestablishment process, once a message such as RRCConnectionReconfiguration message, the lower layers may indicate that the integrity protection failed. However, according to the LTE specification, the UE should trigger the re-establishment again. The problem is that this may lead to an infinite loop, because upon failure, the UE may not perform cell selection / reselection, so that the UE may be stuck on the same cell where the failure occurred. Note that this may be particularly problematic if the integrity protection failure is caused by non-radio related problems, i.e. the UE will probably not change cells when these multiple failures occur.

[0025] In the NR case, the RRCReestablishment message is sent over SRB1 (i.e., integrity protected and encrypted). Therefore, the network can multiplex the RRCReconfiguration message and the RRCReestablishment message. And, since the RRCReestablishment is sent over SRB1, the integrity verification may fail. There is currently ambiguity in the specification regarding the UE action after detecting an integrity verification failure.

[0026] According to subclause 5.3.7.2 in NR RRC (3GPP TS 38.331), once an indication of integrity check failure on SRB1 or SRB2 is received from the lower layer, the UE shall initiate the reestablishment procedure. Since the RRCReestablishment message is sent on SRB1, according to this situation, once a prompt of integrity check failure is received from the lower layer when receiving the RRCReestablishment message, the UE shall initiate the reestablishment again, as shown below: ***start extract************************************************* 5.3.7RRC Connection Reestablishment 5.3.7.1 General See Fig.13a and 13b . The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED with security activated may initiate this procedure in order to continue the RRC connection. According to section 5.3.3.4, the connection re-establishment is successful if the network is able to find and verify a valid UE context, or if the UE context cannot be retrieved and the network responds with RRCSetup. If AS security is not activated, the UE does not initiate this procedure and moves directly to RRC_IDLE.

[0027] The network applies this process as follows: - When AS security has been activated and the network has retrieved or verified the UE context: - Reactivate AS security without changing the algorithm; -Rebuild and restore SRB1; -When the UE is re-establishing an RRC connection and the network is unable to retrieve or verify the UE context: -Discard the stored AS context and release all RBs; - Fall back to establish a new RRC connection.

[0028] 5.3.7.2 Startup The UE initiates this process when one of the following conditions is met: 1> When a radio link failure is detected at the MCG, according to 5.3.10; or 1> when reconfiguring for MCG synchronization failure, according to subclause 5.3.5.8.3; or 1> When mobility fails on the NR side, according to subclause 5.4.3.5; or 1> when an indication is received from the lower layer that the integrity check of SRB1 or SRB2 has failed; or 1> When RRC connection reconfiguration fails, according to subclause 5.3.5.8.2. … ***Finish extract**************************************************

[0029] However, according to subclause 5.3.7.5 of NR RRC (38.331), upon entering RRC_IDLE, the UE shall perform the actions specified in 5.3.11 with the release cause being 'other', as shown below: ***start extract*************************************************** 5.3.7.5UE receives RRCReestablishment The UE shall: 1> Stop timer T301; 1> Treat the current cell as PCell; 1>nextHopChainingCount value indicated in the RRCReestablishment message; 1>Based on the current K gNB Or NH updates K using the stored nextHopChainingCount value gNB Keys, as specified in TS 33.501

[11] ; 1> Export the K associated with the previously configured encryption algorithm RRCenc Key, K RRCint , K UPint Key and K UPenc Keys, as specified in TS 33.501

[11] ; 1> Request the lower layer to use the previously configured algorithm and K RRCintThe key is used to verify the integrity protection of the RRCReestablishment message; 1> If the integrity protection check of the RRCReestablishment message fails, then: 2> Once in RRC_IDLE, the actions specified in 5.3.11 are performed, and the release reason is 'other', whereupon the process ends; 1> Configure the lower layer to immediately use the previously configured algorithm and K RRCint The integrity protection shall be activated using the key, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE (including the message indicating successful completion of the procedure); 1> Configure the lower layer to immediately use the previously configured algorithm, K RRCenc Key and K UPenc The encryption key is used to apply encryption, that is, encryption should be applied to all subsequent messages received and sent by the UE (including messages used to indicate successful completion of the procedure); 1> Submit the RRCReestablishmentComplete message to the lower layer for transmission; 1>The process ends. ***Finish extract***************************************************

[0030] Such ambiguity in the specification may result in different actions being taken for different UEs, thereby resulting in unpredictable behavior such that appropriate network actions may not be taken consistently across different UEs. In particular, if a UE performs re-establishment again after receiving an integrity protection check failure on a message such as RRCReestablishment from lower layers, the UE may always be stuck in the same cell which may be considered a failure.

[0031] Another issue with the second possible ambiguous action in NR is that the access stratum indicates to upper layers a release cause of 'other' which may result in the UE not doing anything, when in fact a failure has occurred for the UE that was previously in RRC_CONNECTED.

[0032] In summary, the proposed solution solves the following problems: - Ambiguity in the actions that the UE should perform upon receiving an indication of an integrity check failure, such as an RRCReestablishment upon receiving the first message (e.g., an RRCReconfiguration type message) after an RRCReestablishment; - After detecting a failure, indications from lower layers do not result in the UE taking any action except some passive actions (e.g., transitioning to RRC_IDLE and CM-IDLE).

[0033] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Various embodiments are presented herein for solving one or more of the problems disclosed herein. Summary of the invention

[0035] According to certain embodiments, a method performed by a UE to perform a reestablishment procedure is disclosed, the method comprising: receiving a reconstruction message; upon receiving the re-establishment message, monitoring an indication of an integrity check failure received from a lower layer, wherein the indication relates to a first message or a second message received by the UE after transmitting the re-establishment request; In response to the indication of an integrity check failure, performing actions upon entering the RRC_IDLE mode of operation; indicating a connection failure to an upper layer; and Based on this indication, the upper layer triggers the recovery process.

[0036] The monitoring step may include monitoring an indication of a possible integrity check failure indication from a lower layer upon receiving a reestablishment message, regarding SRB1 or SRB2. The reestablishment message may include an RRCReestablishement type message. According to certain embodiments, the reestablishment message may be an RRCReestablishement message in NR, or an RRCConnectionReestablishement message in LTE, or any other message having the purpose of reestablishing a connection in response to a reestablishment request.

[0037] According to certain embodiments, the first message includes a message for reestablishing the connection in response to a reestablishment request transmitted by the UE and / or a message transmitted by the network after receiving the reestablishment request and protected by integrity. For example, the first message may include an RRCReestablishement type message sent on SRB1, such as an RRCReestablishement message in NR, or an RRCConnectionReestablishement message in LTE, or any message (such as RRC Release) that may be sent by the network after an RRCReestablishementRequest type message and protected by integrity.

[0038] According to certain embodiments, the second message includes a message that is integrity protected and transmitted by the network after transmitting a message to reestablish the connection in response to a reestablishment request transmitted by the UE. For example, the second message may include an RRCReconfiguration type message, such as an RRCReconfiguration message in NR, or an RRCConnectionReconfiguration message in LTE, or any message that is integrity protected and may be sent by the network after an RRCReestablishement type message (such as RRC Release), etc.

[0039] According to certain embodiments, upon leaving RRC_CONNECTED or RRC_INACTIVE to enter RRC IDLE, for example in case of a failure detected in LTE, the UE performs actions.

[0040] The lower layer may include a PDCP layer. The upper layer may include a non-access layer.

[0041] According to certain embodiments, the recovery procedure may be a NAS recovery procedure defined in NAS, which is triggered upon receipt of a failure indication and / or transition to RRC_IDLE with a suitable release cause (which may be a failure indication such as 'RRC Connection Failure'). NAS recovery in this context may be interpreted as a Registration Area Update (or equivalently, such as a Tracking Area Update).

[0042] According to certain embodiments, the recovery procedure may be a NAS recovery procedure defined in NAS, which is triggered upon receipt of a failure indication and / or transition to RRC_IDLE with an appropriate release cause (which may be a more specific failure indication, such as the RRC connection failed due to security or integrity failure, and for which the specific recovery procedure may be attempted before potentially using a more general and more robust recovery procedure). NAS recovery in this context may be interpreted as, for example, starting another SR procedure. The specific NAS recovery procedure may be lighter and / or less signaling intensive than the more general and more robust NAS recovery procedure. The more general and more robust NAS recovery procedure may be triggered (only) when the specific recovery procedure fails. The more general and more robust NAS recovery procedure in this context may be interpreted as a Registration Area Update (or equivalently, such as a Tracking Area Update).

[0043] According to some embodiments, once the integrity verification fails, the UE triggers the reestablishment process, but it has different protection mechanisms to avoid actions of fake base stations, such as: The counter is defined in such a way that the UE is only allowed to reestablish in the same cell X times; • Perform cell selection / reselection to another RAT, another frequency and / or another cell after X times.

[0044] Perform NAS recovery and enter IDLE after X times.

[0045] According to certain embodiments, a user equipment (UE) configured to perform a reestablishment procedure is disclosed. The UE may include suitable hardware (eg, processing circuitry) as disclosed herein, thereby enabling the UE to perform any of the methods disclosed herein.

[0046] According to certain embodiments, a method performed by a network node to perform a reestablishment procedure is disclosed. The method includes sending a reestablishment method to a UE. The method further includes receiving an indication of an integrity check failure from the UE. In response, the network node monitors UE actions according to expected behavior.

[0047] According to certain embodiments, a network node configured to perform a reestablishment process is disclosed. The network node may include suitable hardware (e.g., processing circuitry) as disclosed herein, thereby enabling the network node to perform any method disclosed herein. The network node may be any suitable node for performing reestablishment messaging with a UE.

[0048] Certain embodiments may provide one or more of the following technical advantages. First, by resolving ambiguity, different UEs will have predictable behavior. Therefore, in case of failure, the network can monitor the UE actions according to the expected behavior defined in the RRC specification. Second, due to the failure indication to the upper layer, the UE should perform recovery procedures, and in the event of a malicious base station attempting to perform a denial of service (DoS) attack, the UE will not be stuck in the same cell and keep trying to reestablish and / or connect therein.

[0049] Another advantage is when the reestablishment message (e.g., RRCReestablishment type message) is not integrity protected and the UE relies on the first RRC Reconfiguration to recover the DRBs and SRBs. In this case, if the integrity verification of the message fails after the RRC Reestablishment, the UE performs a recovery procedure and enters IDLE instead of attempting multiple subsequent RRC Reestablishment procedures that will be considered failed. Certain embodiments may provide all or some of these technical advantages, or may not provide any of these technical advantages. Based on the present disclosure, those skilled in the art may readily appreciate additional technical advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1illustrates a wireless network according to some embodiments; Figure 2 illustrates a user device according to some embodiments; Figure 3 illustrates a virtualized environment according to some embodiments; Figure 4 illustrates a telecommunications network connected to a host computer via an intermediate network according to some embodiments; Figure 5 illustrates a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments; Figure 6 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Figure 7 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Figure 8 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Fig. 9 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Fig.10 A signaling diagram is illustrated; Fig.11 illustrates the reconstruction process in NR employing certain aspects; Fig.12 The diagram illustrates the use of the integrity algorithm NIA to authenticate the integrity of the message; Fig.13a and 13b RRC connection re-establishment is illustrated. DETAILED DESCRIPTION

[0051] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided merely by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the draft "Change Request" provided in the Appendix.

[0052] According to a first embodiment, a possible implementation of the method is shown in the form of changes to the NR RRC specification (38.331). It should be understood that these changes are for illustrative purposes. Other terms and / or standard sections may be used without departing from the scope of the present disclosure or the functionality of the embodiments. ***start extract**************************************************

[0053] 5.3.7.2 Startup The UE initiates this process when one of the following conditions is met: 1> When a radio link failure is detected at the MCG, according to 5.3.10; or 1> when reconfiguring for MCG synchronization failure, according to subclause 5.3.5.8.3; or 1> When mobility fails on the NR side, according to subclause 5.4.3.5; or 1> When receiving an indication from the lower layer that the integrity check of SRB1 or SRB2 has failed, Unless in RRCReestablishment message or the first RRCReconfiguration message after the RRCReestablishment message Integrity check failure detected on ;or 1> When RRC connection reconfiguration fails, according to subclause 5.3.5.8.2.

[0054] Before initiating this procedure, the UE shall ensure that it has a valid and up-to-date Basic system information.

[0055] Once the procedure is initiated, the UE shall: 1> Stop timer T310 (if running); 1> Stop timer T304 (if running); 1>Start timer T311; 1>Suspend all RBs except SRB0; 1>Reset MAC; 1> Release the MCG SCell (if configured), according to subclause 5.3.5.5.8; 1> Release the current dedicated ServingCell configuration; and 1>Apply to the corresponding Physical Layer Specified in the specification Default L1 parameters values, except for parameters for which values ​​are provided in SIB1; 1> Release delayBudgetReportingConfig (if configured) and stop timer T3xx (if running); 1>Applied in 9.2. 2 The default MAC Cell Group configuration specified in x1; 1> As in TS 38.304[21 ,5.2.6 ] as specified in the , cell selection is performed according to the cell selection procedure. ***Finish extract**************************************************

[0056] Next change: ***start extract************************************************** 5.3.7.5UE receives RRCReestablishment The UE shall: 1> Stop timer T301; 1> Treat the current cell as PCell; 1>nextHopChainingCount value indicated in the RRCReestablishment message; 1>Based on the current K gNB Or NH uses the stored nextHopChainingCount value to update K gNB Keys, as specified in TS 33.501

[11] ; 1>Derive the K associated with the previously configured cipheringAlgorithm RRCenc and K UPenc Keys, as specified in TS 33.501

[11] ; 1>Derive K associated with the previously configured integrityProtAlgorithm RRCint and K UPint Keys, as specified in TS 33.501

[11] .

[0057] 1> Request the lower layer to use the previously configured algorithm and K RRCint Key to verify Integrity protection of RRCReestablishment message; 1> If the integrity protection check of the RRCReestablishment message fails; or 1> If after the RRCReestablishment message fails, the lower layer indicates the first RRCReconfiguration performs integrity protection check, then: 2> Once in RRC_IDLE, perform the actions specified in 5.3.11, and the release reason is ' RRC Connection Failure Other', whereby the process ends; 1> Configure the lower layer to immediately use the previously configured algorithm and K RRCintThe integrity protection of SRB1 shall be restored using the key, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE (including messages indicating successful completion of the procedure); 1> Configure the lower layer to immediately use the previously configured algorithm, K RRCen c key to recover the ciphering of SRB1, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE (including messages indicating successful completion of the procedure); 1> Submit the RRCReestablishmentComplete message to the lower layer for transmission; 1>The process ends. ***Finish extract**************************************************

[0058] According to a second embodiment, a possible implementation of the method is shown in the form of changes to the NR RRC specification (38.331). It should be understood that these changes are for illustrative purposes. Other terms and / or standard sections may be used without departing from the scope of the present disclosure or the functionality of the embodiments. ***start extract**************************************************

[0059] 5.3.7.2 Startup The UE initiates this process when one of the following conditions is met: 1> When a radio link failure is detected at the MCG, according to 5.3.10; or 1> when reconfiguring for MCG synchronization failure, according to subclause 5.3.5.8.3; or 1> When mobility fails on the NR side, according to subclause 5.4.3.5; or 1> When receiving an indication from the lower layer that the integrity check of SRB1 or SRB2 has failed, Unless in RRCReestablishment message or the first RRCReconfiguration message after the RRCReestablishment message Integrity check failure detected on ;or 1> When RRC connection reconfiguration fails, according to subclause 5.3.5.8.2.

[0060] Before initiating this procedure, the UE shall ensure that it has a valid and up-to-date Basic system information.

[0061] Once the procedure is initiated, the UE shall: 1> Stop timer T310 (if running); 1> Stop timer T304 (if running); 1>Start timer T311; 1>Suspend all RBs except SRB0; 1>Reset MAC; 1> Release the MCG SCell (if configured), according to subclause 5.3.5.5.8; 1> Release the current dedicated ServingCell configuration; and 1>Apply to the corresponding Physical Layer Specified in the specification Default L1 parameters values, except for parameters for which values ​​are provided in SIB1; 1> Release delayBudgetReportingConfig (if configured) and stop timer T3xx (if running); 1>Applied in 9.2. 2 The default MAC Cell Group configuration specified in x1; 1> As in TS38.304[21 ,5.2.6 ] as specified in the , cell selection is performed according to the cell selection procedure. ***Finish extract**************************************************

[0062] Next change: ***start extract************************************************** 5.3.7.5UE receives RRCReestablishment The UE shall: 1> Treat the current cell as PCell; 1>nextHopChainingCount value indicated in the RRCReestablishment message; 1>Based on the current K gNB Or NH uses the stored nextHopChainingCount value to update K gNB Keys, as specified in TS 33.501

[11] ; 1>Derive the K associated with the previously configured cipheringAlgorithm RRCenc and K UPencKeys, as specified in TS 33.501

[11] ; 1>Derive K associated with the previously configured integrityProtAlgorithm RRCint and K UPint Keys, as specified in TS 33.501

[11] .

[0063] 1> Request the lower layer to use the previously configured algorithm and K RRCint Key to verify Integrity protection of RRCReestablishment message; 1> If the integrity protection check of the RRCReestablishment message fails, then: 2> Once in RRC_IDLE, perform the actions specified in 5.3.11, and the release reason is ' RRC ConnectionFailure Other', whereby the process ends; 1> Stop timer T301; 1> Configure the lower layer to immediately use the previously configured algorithm and K RRCint The integrity protection of SRB1 shall be restored using the key, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE (including messages indicating successful completion of the procedure); 1> Configure the lower layer to immediately use the previously configured algorithm, K RRCen c key to recover the ciphering of SRB1, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE (including messages indicating successful completion of the procedure); 1> Submit the RRCReestablishmentComplete message to the lower layer for transmission; 1>The process ends. [...] 5.3.7.7 T301 expires, integrity check from lower layer fails while T301 is running, or the selected cell is no longer suitable The UE shall: 1> If timer T301 expires; or 1> If the selected cell becomes no longer suitable according to the cell selection criteria specified in TS 38.304

[21] : 1> If the lower layer indicates that the integrity check fails when T301 is running, then: 2> Once entering RRC_IDLE, perform the actions specified in 5.3.11, and the release reason is 'RRC connection failure'. ***Finish extract**************************************************

[0065] Some embodiments described in the present disclosure may also be implemented in the LTE RRC specification (3GPP TS36.331). The proposed changes are as follows. It should be understood that these changes are for illustrative purposes. Other terms and / or standard sections may be used without departing from the scope of the present disclosure or the functionality of the embodiments. ***start extract**************************************************

[0066] 5.3.7.2 Startup The UE shall initiate this procedure only when AS security has been activated or only for NB-IoT UEs that support RRC connection reestablishment for control plane CIoT EPS optimization. The UE initiates this procedure when one of the following conditions is met: 1> When a radio link failure is detected, according to 5.3.11; or 1> When the switch fails, follow 5.3.5.6; or 1> When mobility on the E-UTRA side fails, according to 5.4.3.5; or 1> When receiving an indication from the lower layer that the integrity check of SRB1 or SRB2 has failed , upon receiving Except the first message after the RRCConnectionReestablishment message ;or 1> When RRC connection reconfiguration fails, according to 5.3.5.5; or 1> When RRC connection reconfiguration fails, according to TS38.331[82,5.3.5.5].

[0067] Once the procedure is initiated, the UE shall: 1> Stop timer T310 (if running); 1> Stop timer T312 (if running); 1> Stop timer T313 (if running); 1> Stop timer T307 (if running); 1> Start timer T311; 1> Stop timer T370 (if running); 1>Release uplinkDataCompression (if configured); 1> Suspend all RBs except SRB0, including RBs configured with NR PDCP; 1>Reset MAC; 1> Release the MCG SCell (if configured), according to 5.3.10.3a; 1> Apply the default physical channel configuration specified in 9.2.4; 1> For MCG, except for NB-IoT, the default semi-persistent scheduling configuration specified in 9.2.3 applies; 1> For MCG, the default MAC master configuration specified in 9.2.2 is applied; 1> Release powerPrefIndicationConfig (if configured) and stop timer T340 (if running); 1> Release reportProximityConfig (if configured) and clear any associated proximity reporting timer; 1>Release obtainLocationConfig (if configured); 1> Release idc-Config (if configured); 1>Release sps-AssistanceInfoReport (if configured); 1>Release measSubframePatternPCell (if configured); 1> Release the entire SCG configuration (if configured), except for the DRB configuration (such as configured by drb-ToAddModListSCG); 1> If EN-DC is configured, then: 2> Perform EN-DC release as specified in TS 38.331 [82, 5.3.5.10]; 1> Release the naics-Info of PCell (if configured); 1> If connected as RN and configured with RN subframe configuration, then: 2> Release RN subframe configuration; 1> Release the LWA configuration (if configured), as described in 5.6.14.3; 1> Release the LWIP configuration (if configured), as described in 5.6.17.3; 1> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running); 1> Perform cell selection according to the cell selection procedure specified in TS 36.304 [4]; 1> Release bw-PreferenceIndicationTimer (if configured) and stop timer T341 (if running); 1> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running); 1> Release ailc-BitConfig (if configured); […] 5.3.7.x Integrity check from lower layers fails for the first message received after RRCConnectionReestablishment The UE shall: 1> Upon receiving an integrity check failure indication from lower layers for the first message received after RRCConnectionReestablishment: 2> Upon entering RRC_IDLE, perform the actions as specified in 5.3.11, with the release cause being 'RRC connection failure'. ***Finish extract**************************************************

[0068] Figure 1 A wireless network in accordance with some embodiments is illustrated.

[0069] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 1 For simplicity, Figure 1 The wireless network of FIG. 1 depicts only the network 106, the network nodes 160 and 160b, and the WDs 110, 110b, and 110c. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. In the illustrated components, the network node 160 and the wireless device (WD) 110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access by the wireless device and / or use of services provided by or via the wireless network.

[0070] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0071] The network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0072] The network node 160 and the WD 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired connection or via a wireless connection.

[0073] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, and evolved nodes (eNBs)). Base stations may be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as, MSR BS), network controllers (such as, radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME, O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC) and / or MDT. As another example, the network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged and / or operable to enable and / or provide a wireless device with access to a wireless network or provide a certain service to a wireless device that has access to a wireless network.

[0074] exist Figure 1 In the embodiment, the network node 160 includes a processing circuit 170, a device readable medium 180, an interface 190, an auxiliary device 184, a power supply 186, a power circuit 187, and an antenna 162. Figure 1The network node 160 illustrated in the example wireless network of may represent a device including the illustrated combination of hardware components, but other embodiments may include network nodes with different combinations of components. It is to be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up the single illustrated component (for example, the device readable medium 180 may include multiple separate hard drives and multiple RAM modules).

[0075] Similarly, the network node 160 may be composed of multiple physically separate components (e.g., NodeB components and RNC components and BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single separate network node in some instances. In some embodiments, the network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be replicated (e.g., separate device-readable storage media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). The network node 160 may also include multiple sets of various illustrated components for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 160 .

[0076] The processing circuit 170 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 170 may include, for example, processing information obtained by the processing circuit 170 by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making determinations as a result of the processing.

[0077] The processing circuitry 170 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or any other suitable computing device, resource, or combination of encoded logic, software, and / or hardware operable to provide network node 160 functionality alone or in conjunction with other network node 160 components (such as device readable medium 180). For example, the processing circuitry 170 may execute instructions stored in the device readable medium 180 or in a memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 170 may include a system on a chip (SOC).

[0078] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.

[0079] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 170 executing instructions stored on a memory or device-readable medium 180 within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 970 (such as in a hardwired manner) without executing instructions stored on a separate or discrete device-readable medium. In any of those embodiments, processing circuitry 170 can be configured to perform the described functionality, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuitry 170 or to other components of network node 160, but are enjoyed by network node 160 as a whole, and / or generally by end users and wireless networks.

[0080] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by processing circuit 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that are executable by processing circuit 170 and utilized by network node 160. Device-readable medium 180 may be used to store any computations performed by processing circuit 170 and / or any data received via interface 190. In some embodiments, processing circuit 170 and device-readable medium 180 may be considered integrated.

[0081] Interface 190 is used in wired or wireless communication of signaling and / or data between network node 160, network 106 and / or WD 110. As illustrated, interface 190 includes (one or more) ports / (one or more) terminals 194 to send and receive data to and from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuit 192, which may be coupled to antenna 162, or may be part of antenna 162 in some embodiments. Radio front-end circuit 192 includes filter 198 and amplifier 196. Radio front-end circuit 192 may be connected to antenna 162 and processing circuit 170. Radio front-end circuit may be configured to adjust the signal transmitted between antenna 162 and processing circuit 170. Radio front-end circuit 192 may receive digital data to be sent out to other network nodes or WDs via a wireless connection. Radio front-end circuit 192 may convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 198 and / or amplifier 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect the radio signal, which is then converted into digital data by radio front end circuit 192. The digital data may be passed to processing circuit 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0082] In certain alternative embodiments, the network node 160 may not include a separate radio front end circuit 192, and instead, the processing circuit 170 may include the radio front end circuit and may be connected to the antenna 162 without the separate radio front end circuit 192. Similarly, in some embodiments, all or some of the RF transceiver circuit 172 may be considered part of the interface 190. In still other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front end circuit 192, and the RF transceiver circuit 172 as part of a radio unit (not shown), and the interface 190 may communicate with the baseband processing circuit 174, which is part of the digital unit (not shown).

[0083] Antenna 162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuit 190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sectored or flat panel antennas operable to transmit / receive, for example, radio signals between 2 gigahertz (GHz) and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sectored antennas may be used to transmit / receive radio signals from devices within a specific area, and flat panel antennas may be line-of-sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port.

[0084] Antenna 162, interface 190 and / or processing circuit 170 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190 and / or processing circuit 170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data and / or signal may be transmitted to a wireless device, another network node and / or any other network equipment.

[0085] The power circuit 187 may include or be coupled to a power management circuit, and is configured to supply power to the components of the network node 160 for performing the functionality described herein. The power circuit 187 may receive power from the power supply 186. The power supply 186 and / or the power circuit 187 may be configured to provide power to the various components of the network node 160 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 186 may be included in the power circuit 187 and / or the network node 160, or external to it. For example, the network node 160 may be connected to an external power source (e.g., an electrical outlet) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit 187. As another example, the power supply 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated in the power circuit 187. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.

[0086] Alternative embodiments of network node 160 may include, in addition to Figure 1 , which may be responsible for providing certain aspects of the functionality of the network node, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 160 may include a user interface device to allow information to be input into the network node 160 and to allow information to be output from the network node 160. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 160.

[0087] As used herein, a wireless device (WD) refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air to transmit and / or receive wireless signals. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from a network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted equipment (LMEs), smart devices, wireless customer premises equipment (CPEs), wireless terminal devices installed on vehicles, etc. WDs may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, and in this case may be referred to as D2D communication devices. As another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or a network node. In this case, a WD may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in a 3GPP context. As a specific example, a WD may be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD may represent a vehicle or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation. A WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

[0088] As shown, wireless device 110 includes antenna 111, interface 114, processing circuit 120, device readable medium 130, user interface device 132, auxiliary device 134, power supply 136 and power circuit 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMax, or Bluetooth wireless technology, just to mention a few examples. These wireless technologies can be integrated into chips or chipsets that are the same or different from other components in WD 110.

[0089] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 114. In some alternative embodiments, antenna 111 may be separated from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114, and / or processing circuit 120 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 911 may be considered an interface.

[0090] As shown, the interface 114 includes a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 includes one or more filters 118 and an amplifier 116. The radio front-end circuit 114 is connected to the antenna 111 and the processing circuit 120, and is configured to adjust the signal transmitted between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to or part of the antenna 111. In some embodiments, the WD 110 may not include a separate radio front-end circuit 112; instead, the processing circuit 120 may include a radio front-end circuit and may be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered as part of the interface 114. The radio front-end circuit 112 may receive digital data to be sent out to other network nodes or WDs via a wireless connection. The radio front-end circuit 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via the antenna 111. Similarly, when data is received, antenna 111 may collect radio signals, which are then converted into digital data by radio front end circuit 112. The digital data may be passed to processing circuit 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0091] The processing circuit 120 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of coded logic, software, and / or hardware operable to be provided alone or in conjunction with other WD 110 components (such as, device readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 120 may execute instructions stored in the device readable medium 130 or in a memory within the processing circuit 120 to provide the functionality disclosed herein.

[0092] As shown, the processing circuit 120 includes one or more of the following: RF transceiver circuit 122, baseband processing circuit 124, and application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of WD 110 may include a SOC. In some embodiments, the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 124 and the application processing circuit 126 may be combined into one chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 122 and the baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In yet other alternative embodiments, part or all of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 122 may be part of interface 114 . RF transceiver circuitry 122 may condition RF signals for processing circuitry 120 .

[0093] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by processing circuit 120 executing instructions stored on device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuit 120 (such as, in a hardwired manner) without executing instructions stored on a separate or discrete device-readable storage medium. In any of those specific embodiments, processing circuit 120 can be configured to perform the described functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuit 120 or to other components of WD 110, but are enjoyed by WD 110 as a whole, and / or generally by end users and wireless networks.

[0094] Processing circuit 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being performed by WD. Such operations as performed by processing circuit 120 may include, for example, processing information obtained by processing circuit 120 by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 110, and / or performing one or more operations based on the obtained information or the converted information, and making determinations as a result of the processing.

[0095] Device-readable medium 130 may be operable to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by processing circuit 120. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by processing circuit 120. In some embodiments, processing circuit 120 and device-readable medium 130 may be considered integrated.

[0096] The user interface device 132 may provide a component that allows for human users to interact with the WD 110. Such interactions may have a variety of forms, such as visual, auditory, tactile, etc. The user interface device 132 may be operable to generate output to the user and allow the user to provide input to the WD 110. The type of interaction may vary depending on the type of user interface device 132 installed in the WD 110. For example, if the WD 110 is a smart phone, the interaction may be performed via a touch screen; if the WD 110 is a smart meter, the interaction may be performed by providing a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 132 may include an input interface, device, and circuit, as well as an output interface, device, and circuit. The user interface device 132 is configured to allow information to be input into the WD 110, and is connected to the processing circuit 120 to allow the processing circuit 120 to process the input information. The user interface device 132 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a universal serial bus (USB) port, or other input circuits. The user interface device 132 is also configured to allow information to be output from the WD 110 and to allow the processing circuit 120 to output information from the WD 110. The user interface device 132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 132, the WD 110 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0097] Auxiliary device 134 is operable to provide more specific functionality that may not normally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and types of components of auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0098] In some embodiments, the power supply 136 may take the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., an electrical socket), a photovoltaic device, or a power cell. The WD 110 may also include a power circuit 137 for delivering power from the power supply 136 to various parts of the WD 110, which require power from the power supply 136 to implement any functionality described or indicated herein. In some embodiments, the power circuit 137 may include a power management circuit. The power circuit 137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 110 may be connected to an external power source (such as an electrical socket) via an input circuit or interface (such as a power cable). In some embodiments, the power circuit 137 may also be operable to deliver power from an external power source to the power supply 136. For example, this can be used for charging the power supply 136. The power circuit 137 may perform any formatting, conversion, or other modifications to the power from the power supply 136 so that the power is suitable for the corresponding components of the WD 110 to which the power is supplied.

[0099] Figure 2 A user equipment according to some embodiments is illustrated.

[0100] Figure 2 An embodiment of a UE according to various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device that is intended to be sold to or operated by a human user, but the device may not be, or may not be, initially associated with a specific human user. A UE may also include any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE that is not intended to be sold to or operated by a human user. Figure 2 The UE 200 illustrated in FIG. 1 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 2 It is a UE, but the components discussed in this article are also applicable to WD, and vice versa.

[0101] exist Figure 2In the embodiment, UE 200 includes a processor 201, which is operably coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connection interface 211, a memory 215 including a random access memory (RAM) 217, a read-only memory (ROM) 219 and a storage medium 221, a communication subsystem 231, a power supply 213 and / or any other components or any combination thereof. The storage medium 221 includes an operating system 223, an application 225 and data 227. In other embodiments, the storage medium 221 may include other similar types of information. Some UEs may utilize Figure 2 All of the components shown in the , or only a subset of the components may be utilized. The degree of integration between components may vary from one UE to another UE. In addition, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0102] exist Figure 2 In the embodiment of the present invention, the processor 201 can be configured to process computer instructions and data. The processor 201 can be configured to implement any sequential state machine operable to execute machine instructions stored in a memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored programs, general-purpose processors (such as, microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the above. For example, the processor 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0103] In the depicted embodiment, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to the UE 200 and output from the UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 200 may be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0104] exist Figure 2 In the embodiment of the present invention, the RF interface 209 can be configured to provide a communication interface to the RF components (such as transmitters, receivers and antennas). The network connection interface 211 can be configured to provide a communication interface to the network 243a. The network 243a can cover wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunication networks, another similar network or any combination thereof. For example, the network 243a can include a WiFi network. The network connection interface 211 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately alternatively.

[0105] RAM 217 can be configured to interface with processor 201 via bus 202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processor 201. For example, ROM 219 can be configured to store unchanged low-level system code or data of basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup or reception of keystrokes from a keyboard. Storage medium 221 can be configured to include memory, such as RAM, ROM, programmable ROM (PROM), erasable programmable system memory (EPROM), electrically erasable programmable system memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium 221 can be configured to include operating system 223, application 225 (such as, web browser application, widget or gadget engine or another application) and data file 227. The storage medium 221 may store any of a variety of operating systems or combinations of operating systems for use by the UE 200 .

[0106] The storage medium 221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory or any combination thereof. The storage medium 221 may allow the UE 200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article (such as an article utilizing a communication system) may be tangibly embodied in the storage medium 221, which may include a device-readable medium.

[0107] exist Figure 2In the embodiment of the present invention, the processor 201 may be configured to communicate with the network 243b using the communication subsystem 231. The network 243a and the network 243b may be the same network or multiple networks or different networks or multiple networks. The communication subsystem 231 may be configured to include one or more transceivers for communicating with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers for communicating with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (such as another WD, UE or base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 233 and / or a receiver 235 to respectively implement the transmitter or receiver functionality (e.g., frequency allocation, etc.) suitable for the RAN link. In addition, the transmitter 233 and the receiver 235 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0108] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function or any combination thereof. For example, the communication subsystem 231 may include cellular communication, WiFi communication, Bluetooth communication and GPS communication. The network 243b may cover wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 243b may be a cellular network, a WiFi network and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0109] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 200, or may be divided across multiple components of the UE 200. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 231 may be configured to include any of the components described herein. In addition, the processor 201 may be configured to communicate with any of such components via the bus 202. In another example, any of such components may be represented by program instructions stored in a memory, which perform the corresponding functions described herein when executed by the processor 201. In another example, any functionality of such components may be divided between the processor 201 and the communication subsystem 231. In another example, any non-computationally intensive functions of such components may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0110] Figure 3 A virtualized environment is illustrated in accordance with some embodiments.

[0111] Figure 3 is a schematic block diagram illustrating a virtualized environment 300 in which functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and involves an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0112] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. Additionally, in embodiments where the virtual node is not a radio access node, or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0113] Functionality may be implemented by one or more applications 320 (alternatively they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Applications 320 run in a virtualized environment 300 that provides hardware 330 including processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360, whereby applications 320 may operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0114] The virtualized environment 300 includes a general or special purpose network hardware device 330, which includes a collection of one or more processors or processing circuits 360, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 390-1, which may be a non-persistent memory for temporarily storing software or instructions 395 executed by the processing circuit 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also known as network interface cards), which include a physical network interface 380. Each hardware device may also include a non-transitory, permanent, machine-readable storage medium 390-2 in which instructions and / or software 395 executable by the processing circuit 360 are stored. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also known as hypervisors), software for executing virtual machines 340, and software that allows them to perform the functions, features, and / or benefits described in conjunction with some of the embodiments described herein.

[0115] The virtual machines 340 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of the virtual device 320 may be implemented on one or more of the virtual machines 340, and the implementation may be performed in different ways.

[0116] During operation, processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present to virtual machines 340 a virtual operating platform that appears to be networked hardware.

[0117] like Figure 3As shown in , hardware 330 can be an independent network node with common or specific components. Hardware 330 may include antenna 3225, and some functions may be implemented via virtualization. Alternatively, hardware 330 may be part of a larger hardware cluster (e.g., such as in a data center or wireless customer premises equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which also oversees the lifecycle management of application 320.

[0118] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and wireless customer premises equipment.

[0119] In the context of NFV, virtual machines 340 may be software implementations of physical machines that execute programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340 and the portion of hardware 330 on which it executes (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines in virtual machines 340) form a separate virtual network element (VNE).

[0120] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to Figure 3 Application 320.

[0121] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware nodes 330 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.

[0122] In some embodiments, some signaling may be accomplished using a control system 3230 , which may alternatively be used for communications between the hardware node 330 and the radio unit 3200 .

[0123] Figure 4 A telecommunications network is illustrated connected to a host computer via an intermediary network in accordance with some embodiments.

[0124] refer to Figure 4, showing a communication system according to an embodiment. The communication system shown includes a telecommunications network 410, such as a 3GPP type cellular network, which includes an access network 411 such as a radio access network, and a core network 414. The access network 411 includes a plurality of base stations 412a, 412b, 412c, such as Node B, eNB, gNB or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to the core network 414 via a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is configured to be wirelessly connected to the corresponding base station 412c or to be paged by the corresponding base station 412c. A second UE 492 in the coverage area 413a is wirelessly connectable to the corresponding base station 412a. Although multiple UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to situations where a unique UE is in the coverage area or where a unique UE is connecting to the corresponding base station 412.

[0125] The telecommunications network 410 itself is connected to a host computer 430, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 430 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 421 and 422 between the telecommunications network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430, or may proceed via an optional intermediate network 420. The intermediate network 420 may be one or a combination of more than one of a public, private, or managed network; the intermediate network 420, if any, may be a backbone network or the Internet; in particular, the intermediate network 420 may include two or more sub-networks (not shown).

[0126] Figure 4The communication system as a whole enables connectivity between connected UEs 491, 492 and a host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450 using the access network 411, the core network 414, any intermediate networks 420, and possibly additional infrastructure (not shown) as intermediaries. The OTT connection 450 may be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of uplink and downlink communications. For example, the base station 412 may not or need not be informed of the past routing of incoming downlink communications having data originating from the host computer 430 to be forwarded (e.g., handed over) to the connected UE 491. Similarly, the base station 412 does not need to know the future routing of outgoing uplink communications originating from the UE 491 toward the host computer 430.

[0127] Figure 5 A host computer is shown communicating with a user device over a partially wireless connection via a base station in accordance with some embodiments.

[0128] According to the embodiment, reference will now be made to Figure 5 Describe the example implementation of the UE, base station and host computer discussed in the previous paragraph. In the communication system 500, the host computer 510 includes hardware 515, which includes a communication interface 516, which is configured to establish and maintain a wired or wireless connection of the interface of different communication devices of the communication system 500. The host computer 510 also includes a processing circuit 518, which may have storage and / or processing capabilities. In particular, the processing circuit 518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 510 also includes software 511, which is stored in the host computer 510 or accessible by the host computer 510 and executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to remote users, such as UE 530 connected via an OTT connection 550 terminating at the UE 530 and the host computer 510. In providing services to remote users, the host application 512 may provide user data transmitted using the OTT connection 550 .

[0129] The communication system 500 also includes a base station 520, which is provided in the telecommunication system and includes hardware 525, enabling it to communicate with the host computer 510 and with the UE 530. The hardware 525 may include a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 500, and for establishing and maintaining connections with devices located in the coverage area ( Figure 5 The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Figure 5 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 525 of the base station 520 also includes processing circuitry 528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 520 also has software 521 stored internally or accessible via an external connection.

[0130] The communication system 500 also includes the UE 530 already mentioned. Its hardware 535 may include a radio interface 537, which is configured to establish and maintain a wireless connection 570 with a base station serving the coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 also includes a processing circuit 538, which may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 530 also includes software 531, which is stored in the UE 530 or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to human or non-human users via the UE 530 with the support of the host computer 510. In the host computer 510, the executing host application 512 can communicate with the executing client application 532 via an OTT connection 550 terminated at the UE 530 and the host computer 510. When providing services to users, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0131] Notice, Figure 5 The host computer 510, base station 520 and UE 530 shown in FIG. 5 may be respectively equivalent to Figure 4The host computer 430, one of the base stations 412a, 412b, 412c and one of the UEs 491, 492. That is, the internal workings of these entities can be as follows Figure 5 shown, and independently, the surrounding network topology can be Figure 4 network topology.

[0132] exist Figure 5 In the figure, OTT connection 550 has been abstractly drawn to illustrate the communication between host computer 510 and user equipment 530 via base station 520, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to be hidden from UE 530 or from the service provider operating host computer 510, or from both. When OTT connection 550 is active, the network infrastructure can further make decisions by which it dynamically changes the route (e.g., based on network reconfiguration or load balancing considerations).

[0133] The wireless connection 570 between the UE 530 and the base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 530 using the OTT connection 550, in which the wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments can improve latency and power consumption, and thereby provide benefits such as reduced user waiting time, better responsiveness, and extended battery life.

[0134] For the purpose of monitoring data rate, latency and other factors improved by one or more embodiments, a measurement process may be provided. There may also be optional network functionality for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510 or in the software 531 and hardware 535 of the UE 530, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 550 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or by providing the values ​​of other physical quantities from which the software 511, 531 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 520 and may be unknown or imperceptible to the base station 520. Such processes and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling, thereby facilitating host computer 510 measurements of throughput, propagation time, latency, etc. The measurements may be accomplished by software 511 and 531 using OTT connection 550 to cause the transmission of messages, particularly empty or "dummy" messages, while it monitors propagation time, errors, etc.

[0135] Figure 6 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is illustrated.

[0136] Figure 6 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 4 and Figure 5 To simplify this disclosure, only the Figure 6 . In step 610, the host computer provides user data. In sub-action 611 of step 610 (which may be optional), the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission that carries the user data to the UE. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0137] Figure 7A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is illustrated.

[0138] Figure 7 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 4 and Figure 5 To simplify this disclosure, only the Figure 7 . In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission that carries the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0139] Figure 8 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is illustrated.

[0140] Figure 8 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 4 and Figure 5 To simplify this disclosure, only the Figure 8 . In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (which may be optional), the UE reacts to the received input data provided by the host computer and executes the client application that provides user data. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, in sub-step 830 (which may be optional), the UE initiates transmission of the user data to the host computer. In step 840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0141] Fig. 9 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is illustrated.

[0142] Fig. 9is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 4 and Figure 5 To simplify this disclosure, only the Fig. 9 In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0143] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuits and other digital hardware, the processing circuits may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, the memory may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding functions according to one or more embodiments of the present disclosure. Example

[0144] Group A Embodiment 1. A method performed by a wireless device to perform a reestablishment process, the method comprising: -Receive reconstruction messages; - Possible integrity check failure detected; - indicate integrity check failure to upper layers; and - Trigger the recovery process.

[0145] 2. The method of any of the previous embodiments, further comprising: - provide user data; and - Forwarding user data to a host computer via transmission to a base station.

[0146] Group B Example 3. A method performed by a base station to perform a reestablishment process, the method comprising: - Sending a reestablishment message to the wireless device; - receiving an indication from the wireless device that the integrity check failed; and -Monitor UE actions according to expected behavior.

[0147] 4. The method of any of the previous embodiments, further comprising: - obtain user data; and -Forward user data to a host computer or wireless device.

[0148] Group C Example 5. A wireless device for performing a reestablishment process, the wireless device comprising: - a processing circuit configured to perform any of the steps of any of the embodiments of Group A; and - A power circuit configured to provide power to the wireless device.

[0149] 6. A base station for performing a reestablishment process, the base station comprising: - a processing circuit configured to perform any of the steps of any of the embodiments of Group B; and - A power circuit configured to provide power to the wireless device.

[0150] 7. A user equipment (UE) for performing a reestablishment procedure, the UE comprising: - an antenna configured to send and receive wireless signals; - a radio front end circuit coupled to the antenna and the processing circuit and configured to condition signals communicated between the antenna and the processing circuit; - a processing circuit configured to perform any step of any embodiment of Group A; - an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry; - an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and - A battery connected to the processing circuit and configured to power the UE.

[0151] 8. A communication system comprising a host computer, the host computer comprising: - processing circuitry configured to provide user data; and - A communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE); wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any steps of any of the embodiments in Group B.

[0152] 9. The communication system of the previous embodiment further includes a base station.

[0153] 10. The communication system of the first two embodiments further comprises a UE, wherein the UE is configured to communicate with the base station.

[0154] 11. The communication system of the first three embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and - the UE comprises a processing circuitry configured to execute a client application associated with the host application.

[0155] 12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - at the host computer, providing user data; and - At a host computer, initiating transmission carrying user data to a UE via a cellular network comprising a base station, wherein the base station performs any steps of any of the embodiments in Group B.

[0156] 13. The method of the previous embodiment further comprises: transmitting user data at the base station.

[0157] 14. The method of the preceding two embodiments, wherein the user data is provided by executing a host application at a host computer, the method further comprising executing a client application associated with the host application at the UE.

[0158] 15. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the first three embodiments.

[0159] 16. A communication system comprising a host computer, the host computer comprising: - processing circuitry configured to provide user data; and - a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), - wherein the UE comprises a radio interface and a processing circuit, these components of the UE are configured to perform any steps of any of the embodiments in Group A.

[0160] 17. The communication system of the preceding embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0161] 18. The communication system of the first two embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and - the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0162] 19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - at the host computer, providing user data; and - At a host computer, initiating transmission carrying user data to a UE via a cellular network including a base station, wherein the UE performs any steps of any of the embodiments in Group A.

[0163] 20. The method of the previous embodiment further comprises: at the UE, receiving user data from the base station.

[0164] 21. A communication system comprising a host computer, the host computer comprising: - A communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and a processing circuit, the processing circuit of the UE being configured to perform any steps of any of the embodiments of Group A.

[0165] 22. The communication system of the previous embodiment further includes a UE.

[0166] 23. The communication system of the previous two embodiments, further comprising a base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0167] 24. The communication system of the first three embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application; and - The processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0168] 25. The communication system of the first four embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application, thereby providing the request data; and - the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0169] 26. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - At a host computer, receiving user data transmitted from a UE to a base station, wherein the UE performs any steps of any of the embodiments in Group A.

[0170] 27. The method of the previous embodiment further comprises: at the UE, providing the user data to the base station.

[0171] 28. The method of the first two embodiments further comprises: - at the UE, executing a client application, thereby providing user data to be transmitted; and - At the host computer, executing a host application associated with the client application.

[0172] 29. The method of the first three embodiments further comprises: - At the UE, executing a client application; and - at the UE, receiving input data of the client application, wherein the input data is provided at the host computer by executing a host application associated with the client application, - wherein user data to be transmitted is provided by the client application in response to the input data.

[0173] 30. A communication system comprising a host computer, the host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any steps of any embodiment of Group B.

[0174] 31. The communication system of the previous embodiment further includes a base station.

[0175] 32. The communication system of the first two embodiments further comprises a UE, wherein the UE is configured to communicate with the base station.

[0176] 33. The communication system of the first three embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application; - The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.

[0177] 34. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - receiving, at a host computer, from a base station user data originating from a transmission received by the base station from a UE, wherein the UE performs any steps of any of the embodiments in Group A.

[0178] 35. The method of the previous embodiment further comprises: receiving user data from the UE at the base station.

[0179] 36. The method of the preceding two embodiments, further comprising: at the base station, initiating transmission of the received user data to a host computer.

[0180] abbreviation At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, the above use shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listing(s). 1x RTT CDMA2000 1x Radio Transmission Technology 3GPP Third Generation Partnership Project 5G Fifth Generation AS Access Layer ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Composition CCCH SDU Common Control Channel SDU CDMA Code Division Multiple Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec / No CPICH received energy per chip divided by the power density in the frequency band CQI Channel Quality Information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) E-SMLC Evolved Serving Mobile Location Center ECGI Evolved CGI eNB E-UTRAN Node B ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS needs further study GERAN GSM EDGE Radio Access Network gNB Base station in NR (corresponding to eNB in ​​LTE) GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HO Switchover HSPA High Speed ​​Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long Term Evolution MAC Media Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimized Drive Test MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NAS Non-Access Stratum NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System OTDOA observed time difference of arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power; or Reference Signal Received Power RSRQ Reference Signal Received Quality; or Reference Symbol Received Quality RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDU Service Data Unit SFN System Frame Number SGW Service Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self-Optimizing Network SS Sync Signal SSS Auxiliary Sync Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS three-level synchronization signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Area Network

Claims

1. A method performed by a user equipment UE communicating with a network to perform a reestablishment procedure, the method comprising: receiving a reconstruction message; upon receiving the re-establishment message, monitoring for an indication of an integrity check failure received from a lower layer, wherein the indication relates to a first message or a second message received by the UE after transmitting the re-establishment request; In response to said indication of said integrity check failure, upon entering into an RRC_IDLE mode of operation, performing an action: indicating a connection failure to an upper layer; as well as Based on the indication, the upper layer triggers a recovery process.

2. The method of claim 1, wherein: The re-establishment message includes a message for re-establishing a connection in response to the re-establishment request transmitted by the UE.

3. The method according to claim 1 or 2, wherein: The first message includes a message for reestablishing a connection in response to the reestablishment request transmitted by the UE and / or an integrity-protected message transmitted by the network after receiving the reestablishment request.

4. A method as claimed in any preceding claim, wherein: The second message comprises an integrity protected message transmitted by the network after transmitting a message to reestablish a connection in response to the reestablishment request transmitted by the UE.

5. A method as claimed in any preceding claim, wherein: The steps of receiving, monitoring, executing and indicating are performed by the first layer in the radio protocol architecture stack.

6. A method as claimed in any preceding claim, wherein: The recovery process includes a non-access layer NAS recovery process.

7. The method of claim 6, wherein: The recovery process includes a registration area update.

8. The method according to any one of claims 1 to 5, wherein: The recovery process includes a process including a protection mechanism for avoiding actions of false base stations.

9. A method as claimed in any preceding claim, wherein The connection failure is caused by the integrity check failure.

10. A user equipment (UE) communicating with a network to perform a reestablishment procedure, the UE comprising a processing circuit, the processing circuit being configured to: receiving a reconstruction message; Upon receipt of the reestablishment message, monitoring for an indication of integrity check failure received from a lower layer, wherein: The indication relates to a first message or a second message received by the UE after transmitting a re-establishment request; In response to said indication of said integrity check failure, upon entering into an RRC_IDLE mode of operation, performing an action: indicating a connection failure to an upper layer; as well as Based on the indication, the upper layer triggers a recovery process.