Method and apparatus for recovering UE behavior at request rejection

Abstract

Systems and methods related to wireless device behavior after rejecting a recovery request triggered by a Radio Access Network (RAN)-based Notification Area Update (RNAU) or when cell reselection is performed during recovery are disclosed herein. In some embodiments, a method of operation of a wireless device includes transmitting a radio resource control (RRC) recovery request to a radio access network (RAN) node; receiving an RRC recovery rejection message including a wait timer value from the RAN node in response to the RRC recovery request; starting a waiting timer initialized with the waiting timer value; discarding the at least one security key; and transmitting a second RRC recovery request when the waiting timer has expired. Corresponding embodiments of a wireless device are also disclosed.

Description

[0001] Divisional application

[0002] This application is a divisional application of a patent application with application number 201980031069.1, application date May 3, 2019, and invention name “Method and device for UE behavior when recovery request is rejected”.

[0003] Related technologies

[0004] This application claims the benefit of Provisional Patent Application No. 62 / 669,822, filed May 10, 2018, the entire disclosure of which is incorporated herein by reference. Technical Field

[0005] The present disclosure relates to restoring a connection in a cellular communication system, and more particularly, to User Equipment (UE) behavior associated with restoring a connection in a cellular communication system. Background Art

[0006] Radio Resource Control (RRC) Connection Recovery in Long Term Evolution (LTE)

[0007] In the 3rd Generation Partnership Project (3GPP) LTE standard Release 13, a mechanism was introduced for a user equipment (UE) to be suspended by the network in a suspended state similar to RRC_IDLE, but with the difference that the UE stores the access stratum (AS) context or RRC context. This makes it possible to reduce signaling when the UE becomes active again by resuming the RRC connection instead of establishing the RRC connection from scratch. Reducing signaling can have several benefits, namely, reduced latency (e.g., for smartphones accessing the Internet) and reduced signaling (resulting in reduced battery consumption for machine-type devices that send little data).

[0008] The Release 13 solution is based on having the UE send an RRCConnectionResumeRequest message to the network and, in response, receive an RRCConnectionResume from the network. The RRCConnectionResume is not encrypted but integrity protected.

[0009] RRC_INACTIVE in New Radio (NR) and possibly in LTE Release 15

[0010] As part of the fifth generation (5G) NR standardization work in 3GPP, it has been decided that NR should support an RRC_INACTIVE state with similar characteristics to the suspended state in LTE Release 13. The RRC_INACTIVE state has slightly different characteristics from the LTE state because it is a separate RRC state, rather than being part of RRC_IDLE as in LTE. In addition, the core network (CN) / radio access network (RAN) connection (NG or N2 interface) is maintained for RRC_INACTIVE, while the connection is suspended in LTE.

[0011] Figure 1 is a flow chart showing possible state transitions between NRs. Figure 1 The characteristics of the state depicted in are as follows:

[0012] RRC_IDLE:

[0013] -UE-specific discontinuous reception (DRX) can be configured by upper layers;

[0014] - UE controlled mobility based on network configuration;

[0015] -UE:

[0016] ■ Monitoring the paging channel for CN paging using the 5G-System Architecture Evolution Temporary Mobile Subscriber Identity (S-TMSI);

[0017] ■Perform neighbor cell measurements and cell (re)selection;

[0018] ■Get system information.

[0019] RRC_INACTIVE:

[0020] -UE-specific DRX can be configured by upper layers or by the RRC layer;

[0021] - UE controlled mobility based on network configuration;

[0022] -UE stores the AS context;

[0023] -UE:

[0024] ■ Monitoring the paging channel for CN paging using 5G-S-TMSI and RAN paging using the Inactive Radio Network Temporary Identifier (I-RNTI);

[0025] ■Perform neighbor cell measurements and cell (re)selection;

[0026] ■Perform RAN-based notification area updates periodically and upon moving out of the RAN-based notification area;

[0027] ■Get system information.

[0028] RRC_CONNECTED:

[0029] -UE stores the AS context;

[0030] -Transmit unicast data to / from UE;

[0031] - At low layers, the UE may be configured with UE-specific DRX;

[0032] - For UEs supporting carrier aggregation (CA), use one or more

[0033] Secondary cells (SCells) to increase bandwidth;

[0034] -For UEs supporting dual connectivity (DC), a secondary cell group (SCG) is aggregated with the primary cell group (MCG) to increase bandwidth;

[0035] - Network controlled mobility, i.e., within NR and handover to / from Evolved Universal Terrestrial RAN (E-UTRAN);

[0037] -UE:

[0038] ■Monitor the paging channel;

[0039] ■ monitoring a control channel associated with a shared data channel to determine whether data is scheduled for the UE;

[0040] ■Provide channel quality and feedback information;

[0041] ■Perform neighbor cell measurements and measurement reporting;

[0042] ■Get system information.

[0043] Current recovery process

[0044] For a UE in RRC_INACTIVE state, the RRC connection recovery procedure needs to be performed in the following cases:

[0045] -When the UE is responding to RAN paging,

[0046] -When the UE has uplink (UL) data to send,

[0047] - when the UE needs to perform Non-Access Stratum (NAS) signalling, or

[0048] - When the UE needs to perform AS signaling (e.g. Radio Notification Area Update (RNAU) due to periodic timeout or due to mobility). Note that RNAU is sometimes also called RAN-based Notification Area Update.

[0049] In all the above cases, the UE shall initiate the resume procedure as described below. Depending on the reason for the resumption, different cause values ​​shall be used in the ResumeRequest message.

[0050] The purpose of this procedure is to restore the RRC connection, including restoring the Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB) or performing a RAN-based Notification Area (RNA) Update (i.e., RNAU). Figures 2 to 6 The recovery process is depicted and described below.

[0051]

[0052]

[0053]

[0054] Summary of the invention

[0055] Disclosed herein are systems and methods related to wireless device (e.g., user equipment (UE)) behavior upon cell reselection after rejection of a recovery request triggered by a Notification Area Update RNAU based on a Radio Access Network RAN ​​or during recovery. In some embodiments, a method of operating a wireless device in a cellular communication system includes: sending a Radio Resource Control (RRC) recovery request triggered by RNAU to a RAN node; and receiving an RRC recovery rejection message including a waiting timer value from the RAN node in response to the RRC recovery request. The method also includes: starting a waiting timer initialized with the waiting timer value; and sending the RNAU when the waiting timer has expired.

[0056] In some embodiments, the method further comprises: monitoring RAN paging and core network CN paging while the waiting timer is running. In some embodiments, the method further comprises: responding to the RAN paging or CN paging when the RAN paging or CN paging is received while the waiting timer is running.

[0057] In some embodiments, the RNAU is a periodic RNAU. In some other embodiments, the RNAU is due to mobility.

[0058] An embodiment of a wireless device for a cellular communication system is also disclosed. In some embodiments, a wireless device for a cellular communication system is adapted to: send an RRC recovery request triggered by an RNAU to a RAN node; and in response to the RRC recovery request, receive an RRC recovery reject message including a wait timer value from the RAN node. The wireless device is further adapted to: start a wait timer initialized with the wait timer value; and send the RNAU when the wait timer has expired.

[0059] In some embodiments, the wireless device is further adapted to monitor RAN paging and CN paging while the waiting timer is running. In some embodiments, the wireless device is further adapted to respond to the RAN paging or CN paging when the RAN paging or CN paging is received while the waiting timer is running.

[0060] In some embodiments, the RNAU is a periodic RNAU. In some other embodiments, the RNAU is due to mobility.

[0061] In some embodiments, a wireless device for a cellular communication system includes a radio front-end circuit and a processing circuit associated with the radio front-end circuit. The processing circuit is configured to cause the wireless device to perform the following operations: send an RRC recovery request triggered by RNAU to a RAN node; and receive an RRC recovery rejection message including a waiting timer value from the RAN node in response to the RRC recovery request. The processing circuit is also configured to cause the wireless device to: start a waiting timer initialized with the waiting timer value; and send the RNAU when the waiting timer has expired.

[0062] In some embodiments, the processing circuit is further configured to cause the wireless device to monitor RAN paging and CN paging while the waiting timer is running. In some embodiments, the processing circuit is further configured to cause the wireless device to respond to the RAN paging or CN paging when the RAN paging or CN paging is received while the waiting timer is running.

[0063] In some embodiments, the RNAU is a periodic RNAU. In some other embodiments, the RNAU is due to mobility.

[0064] In some embodiments, a method of operating a wireless device in a cellular communication system includes: sending an RRC recovery request to a RAN node; and receiving an RRC recovery reject message including a wait timer value from the RAN node in response to the RRC recovery request. The method also includes: starting a wait timer initialized with the wait timer value; and performing a cell reselection to a target cell while the wait timer is running. The method also includes: after performing the cell reselection to the target cell while the wait timer is running, re-initiating a pending access stratum (AS) layer process in the target cell.

[0065] In some embodiments, the method further comprises: determining whether an upper layer event has occurred. Re-initiating a pending AS layer process in the target cell comprises: if an upper layer event has occurred, re-initiating the pending AS layer process in the target cell. In some embodiments, the method further comprises: if an upper layer event has occurred, discarding the pending AS layer process. In some embodiments, the upper layer event is mobile originated data or mobile originated signaling.

[0066] In some embodiments, the pending AS layer process is an RNAU process.

[0067] In some embodiments, a wireless device for a cellular communication system is adapted to: send an RRC resume request to a RAN node; and receive an RRC resume reject message including a wait timer value from the RAN node in response to the RRC resume request. The wireless device is further adapted to: start a wait timer initialized with the wait timer value; and perform a cell reselection to a target cell while the wait timer is running. The wireless device is further adapted to: re-initiate a pending access stratum (AS) layer procedure in the target cell after performing the cell reselection to the target cell while the wait timer is running.

[0068] In some embodiments, a wireless device for a cellular communication system includes a radio front-end circuit and a processing circuit associated with the radio front-end circuit. The processing circuit is configured to cause the wireless device to: send an RRC recovery request to a RAN node; and in response to the RRC recovery request, receive an RRC recovery rejection message including a wait timer value from the RAN node. The processing circuit is also configured to cause the wireless device to: start a wait timer initialized with the wait timer value; and perform cell reselection to a target cell while the wait timer is running. The processing circuit is also configured to cause the wireless device to: re-initiate a pending access layer AS layer process in the target cell after performing the cell reselection to the target cell while the wait timer is running.

[0069] In some embodiments, a method of operating a wireless device in a cellular communication system includes: sending an RRC recovery request to a RAN node; starting a timer; and performing a cell reselection to a target cell while the timer is running. The method also includes: after performing the cell reselection to the target cell while the timer is running, re-initiating a pending AS layer process in the target cell.

[0070] In some embodiments, the timer is a timer started after initiation of an RRC recovery procedure during which the RRC recovery request is sent.

[0071] In some embodiments, the method further comprises: determining whether an upper layer event has occurred. Re-initiating a pending AS layer process in the target cell comprises: if an upper layer event has occurred, re-initiating the pending AS layer process in the target cell. In some embodiments, the method further comprises: if an upper layer event has occurred, discarding the pending AS layer process. In some embodiments, the upper layer event is mobile originated data or mobile originated signaling.

[0072] In some embodiments, the pending AS layer process is an RNAU process.

[0073] In some embodiments, a wireless device for a cellular communication system is adapted to: send an RRC recovery request to a RAN node; start a timer; and perform cell reselection to a target cell while the timer is running. The wireless device is further adapted to: re-initiate a pending AS layer process in the target cell after performing the cell reselection to the target cell while the timer is running.

[0074] In some embodiments, a wireless device for a cellular communication system includes a radio front-end circuit and a processing circuit associated with the radio front-end circuit. The processing circuit is configured to cause the wireless device to: send an RRC recovery request to a RAN node; start a timer; and perform a cell reselection to a target cell while the timer is running. The processing circuit is also configured to cause the wireless device to be further adapted to: re-initiate a pending AS layer process in the target cell after performing the cell reselection to the target cell while the timer is running. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0076] Figure 1is a flow chart showing possible state transitions in 3rd Generation Partnership Project (3GPP) New Radio (NR);

[0077] Figure 2 is a diagram of a successful radio resource control (RRC) connection recovery;

[0078] Figure 3 is a diagram of a successful RRC connection recovery falling back to an RRC connection establishment;

[0079] Figure 4 is a diagram of a successful RRC connection recovery and subsequent network release;

[0080] Figure 5 is an illustration of a successful RRC connection recovery and subsequent network suspension;

[0081] Figure 6 is a diagram of an RRC connection recovery rejected by the network;

[0082] Figure 7 Operation of a user equipment (UE) and a radio access network (RAN) node (e.g., a base station) according to some embodiments of the present disclosure is illustrated, wherein the UE considers a RAN-based Notification Area Update (RNAU) that triggers a network-rejected RRC connection recovery as pending until a wait timer has expired and sends the pending RNAU when the wait timer has expired;

[0083] Figure 8 Operation of a UE and a RAN node (e.g., a base station) according to some embodiments of the present disclosure is illustrated, wherein the UE performs cell reselection during a waiting period after receiving an RRC reject in response to an RRC resume request, and a suspended access stratum (AS) procedure may be re-initiated in a new cell;

[0084] Fig. 9 Operations of a UE and a RAN node (e.g., a base station) according to some embodiments of the present disclosure are illustrated, wherein the UE performs cell reselection after sending an RRC recovery request triggered by the AS layer but before receiving a response from the network, and the AS procedure may be re-initiated in a new cell;

[0085] Fig.10 shows an example of a wireless network in which embodiments of the present disclosure may be implemented;

[0086] Fig.11 A wireless communication system represented as a fifth generation (5G) network architecture including core network functions (NFs) is shown, wherein the interaction between any two NFs is represented by point-to-point reference points / interfaces;

[0087] Fig.12Figure 5 shows a 5G network architecture that uses a service-based interface between NFs in the control plane instead of Fig.11 Point-to-point reference points / interfaces used in the 5G network architecture;

[0088] Fig.13 An example of a UE in which embodiments of the present disclosure may be implemented is shown;

[0089] Fig.14 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized;

[0090] Fig.15 An example communication system is shown in which embodiments of the present disclosure may be implemented;

[0091] Fig.16 Shows Fig.15 Example implementations of UE, base station and host computer; and

[0092] Figures 17 to 20 It is shown in Fig.15 and Fig.16 Flow chart of a method implemented in a communication system. DETAILED DESCRIPTION

[0093] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and show the best mode of practicing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts not particularly proposed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0094] Certain challenges currently exist with radio resource control (RRC) recovery, particularly in 3rd Generation Partnership Project (3GPP) New Radio (NR), but may also exist in other types of networks, such as 3GPP Long Term Evolution (LTE) networks implementing Release 15 or higher of the LTE specification. As described above, a number of events can occur that can cause the recovery process to fail. In particular, the following can occur:

[0095] 1. The user equipment (UE) performs cell reselection before receiving the Resume message (while timer T319 is running); and

[0096] 2. The UE receives the rejection message and starts the waiting timer T302.

[0097] For case 1, it is currently stated that the UE will perform another RRC recovery procedure in the target cell. The problem is that there may be situations where the recovery conditions are different in the target cell, in which case re-initiating the recovery procedure will not work. Example situations include:

[0098] • The UE enters a new Tracking Area (TA) that is not on the TA list that the UE is currently configured with. In this case, the RRC recovery procedure may fail because the UE needs to perform Non-Access Stratum (NAS) signaling to update the TA list instead.

[0099] ●The UE enters a cell that is prohibited from access by the NAS layer (e.g., a prohibited TA). In this case, RRC recovery may also fail or cause other problems.

[0100] For case 2, it is currently stated that the UE should notify higher layers (in the case where the recovery is triggered by higher layers); however, if the recovery is triggered by the RRC (Access Stratum (AS)) layer, it is undefined what the UE should do. A specific issue that needs to be addressed here is what happens when the UE performs a cell reselection.

[0101] Certain aspects of the present disclosure and embodiments thereof can provide solutions to these or other challenges. Aspects disclosed herein introduce a new mechanism in the UE to handle the case where recovery fails in one cell and reselects to another cell. The solution covers the case when cell reselection occurs while timer T319 is running, as well as the case when cell reselection occurs after the UE has received a rejection message and timer T302 is running.

[0102] If the initial recovery is triggered by the AS layer (RRC), the UE shall first check whether any NAS layer events occurred due to cell reselection or during the time leading to cell reselection.

[0103] 1. If an upper layer event has occurred, the UE shall discard any pending AS level recovery (e.g., Radio Access Network (RAN) based Notification Area Update (RNAU)) and trigger a new AS level recovery based on the upper layer trigger.

[0104] 2. If the upper layer event has not occurred, the UE shall re-initiate AS level recovery in the target cell.

[0105] Possible upper-level events may include:

[0106] ●Arrival of uplink (UL) data,

[0107] The arrival of NAS signalling (e.g. UE NAS re-registration due to mobility), or

[0108] ●UE responds to Core Network (CN) or RAN paging.

[0109] If the initial recovery is triggered by upper layers, the UE will inform the upper layers that it cannot recover the connection when reselecting the cell. This will trigger the upper layers to re-trigger the recovery, resulting in similar behavior to case 2 above.

[0110] Certain embodiments may provide one or more of the following technical advantages. By using the proposed solution, it is possible to ensure that NAS or upper layer mechanisms always take precedence over AS-initiated recovery. This can avoid error situations such as the following:

[0111] ●UE performs recovery in an area where it is not allowed to access;

[0112] • The UE performs AS recovery (eg RNAU) in an area outside the UE CN registration area.

[0113] Avoiding these error conditions is beneficial because it will avoid service interruption and prevent unauthorized access to network resources.

[0114] The aspects disclosed herein are generally described as actions performed by an RRC_INACTIVE UE in NR. It should be understood that the present invention is also applicable to additional situations, such as:

[0115] All previous cases where the procedures take place in LTE and not in NR (for the case of LTE RRC_INACTIVE UE);

[0116] ●Inter-Radio Access Technology (RAT) procedures in RRC_INACTIVE, for example, between LTE and NR connected to the same CN (5G Core Network).

[0117] A more detailed description of some specific embodiments of the present disclosure is now provided.

[0118] 1UE behavior when receiving RRC Resume Reject

[0119] It has been agreed in 3GPP that after sending an RRC recovery request, the UE may receive an RRC reject with a waiting timer and remain in RRC_INACTIVE.

[0120] After receiving RRC Reject, the UE needs to contact the network via Resume when the waiting timer expires and after cell reselection while the waiting timer is running. In the latest version of TP for connection control, this is reflected by the following "For Future Study (FFS)" item related to the reception of RRC Reject.

[0121] ●Editor's note: How to deal with rejection is a matter for future research.

[0122] ● Editor's note: Additional UE actions after receiving RRC Reject (e.g. T380 processing, SRB1 suspension, etc.) are for future study

[0123] This description addresses these and other FFS items. For example, actions are suggested for different situations (e.g., mobility RNAU, periodic RNAU, UL data, tracking area update, etc.) at cell reselection while the wait timer is running, and actions are suggested when the wait timer expires.

[0124] In the current TP regarding connection control in NR, the following is currently captured regarding the reception of the RRC reject message:

[0125]

[0126] As in LTE, the current version of the text proposal for connection control ("TP") assumes at least the case where UL data and registration area updates are modeled as high-layer requests to RRC. Then, as shown above, after receiving RRCReject in response to an upper-layer triggered RRCResumeRequest (UL data or registration area update), the UE notifies the upper layer that the RRC connection recovery failed so that the upper layer can keep the process pending until the waiting timer expires or cell reselection is performed. The processing of the waiting timer T302 is then handled by the AS, and after expiration, the AS notifies the upper layer that the RRC recovery request can be triggered again.

[0127] By notifying the upper layer that the UE has been rejected, the upper layer can re-initiate the resumption when the waiting timer T302 has expired. In this case, no pending RRC resumption request is required.

[0128] In NR, in addition to the case where the higher layer requests recovery, the AS layer can also request recovery in the following cases:

[0129] ● Recovery is triggered by "periodic RNAU rejected", with a wait time, and

[0130] ●Recovery is triggered by "mobility RNAU rejected" with a waiting time.

[0131] 1.1 Periodic RNAU

[0132] Periodic RNAU is triggered when the periodic RNAU timer (T380) expires, and the value of the periodic RNAU timer (T380) can be provided in the RRC release message with pause configuration. The network expects periodic RNAU so that in the event that the UE leaves, the network knows whether to clean up the UE context on the network side. However, since the RRC rejection is sent on SRB0, the UE cannot determine whether the network has been notified because a given node can send a rejection without retrieving and / or updating the UE context. Therefore, one solution is to treat the periodic RNAU as pending and send the periodic RNAU when the waiting timer expires. In the case that the UE has left, this may delay the network from cleaning up the UE context instead of being rejected by another node. However, considering that the waiting timer value is short (less than one minute), it is not a big problem for the network to wait longer for the periodic RNAU; and even if the network does not wait longer, the network context will be synchronized anyway once the UE performs the RNAU.

[0133] 1.2 Mobility RNAU

[0134] Mobility RNAU is triggered when the UE enters a new cell that does not belong to its configured RAN-based Notification Area (RNA). The network should be notified of this event so that the network knows the cells in which the UE should be paged effectively. However, if the UE enters a new RNA and attempts to perform an RNA update, and if the network rejects the request with a wait timer, the UE will most likely not be reachable via RAN paging while the wait timer is running. However, in general this will be a very rare case and the network should try to prioritize RNA updates. If the UE also continues to listen to RAN paging, the RAN nodes that failed to page the UE in the RNA may page in the surrounding areas. The UE will also listen to CN paging.

[0135] 1.3 Summary

[0136] Summarizing the aspects of Sections 1.1 and 1.2 above:

[0137] • Upon receiving an RRC Reject with a waiting time in response to an RRC Resume Request triggered by RNAU (periodic or mobility), the UE starts the waiting timer.

[0138] • After receiving an RRC Reject with a waiting time in response to an RRC Recovery Request triggered by an RNAU (periodic or mobility), the UE sends a pending RNAU after the waiting timer (in the same cell) expires.

[0139] • During the waiting period, the UE shall continue to monitor RAN and CN paging and respond if the UE is paged.

[0140] Figure 7 Operation of a UE and a RAN node (e.g., a base station, such as a NR base station (gNB)) according to at least some aspects of the above embodiments is shown. As shown, the UE sends an RRC recovery request triggered by an RNAU (periodic or mobility) (step 700). The RAN node receives the RRC recovery request and, in response, sends an RRC reject with a wait time to the UE (step 702). After receiving the RRC reject message with a wait time, the UE starts a wait timer set to the wait time included in the RRC reject (step 704). While the wait timer is running, the UE considers the RNAU pending. In some embodiments, while the wait timer is running (i.e., during the wait period), the UE continues to monitor RAN and CN paging and responds if paged (step 706). When the wait timer expires, the UE sends a pending RNAU to the RAN node (step 708). In other words, the UE again attempts the RRC connection recovery triggered by the pending RNAU, and assuming that the RRC connection recovery is successful, the UE sends the RNAU to the network.

[0141] 2 UE behavior during cell reselection while T302 (waiting time) is running

[0142] In LTE, a waiting timer is provided to the UE in RRC reject as a way to avoid subsequent attempts in case of cell overload. Therefore, on cell reselection, the waiting timer is stopped and the UE should be able to access the cell again if the cell is not barred for other reasons.

[0143] In LTE, the recovery request is modeled as a request from the upper layer to the AS layer. When an RRC Reject with a waiting time is received in response to an RRC recovery request, the UE notifies the upper layer and starts the waiting timer. When the waiting timer expires or when a cell reselection occurs, the upper layer is notified of barring alleviation. The upper layer can then re-trigger any pending recovery request to the AS.

[0144] For NR, it is recommended to apply the same behavior for any resumption request triggered by upper layers (e.g. mo-data, mo-signaling). Only upper layers know whether upper layer procedures should continue after cell reselection (e.g. at NAS level, the UE may be barred from accessing the target cell). Therefore, this means that when cell reselection is performed while the waiting timer is running, after receiving an RRC reject with waiting time in response to an RRC resumption request triggered by upper layers, the RAN layer informs the upper layers that the barring is relieved.

[0145] 2.1 Mobile or Periodic RNAU

[0146] For a recovery request triggered by the AS layer (e.g., RNAU), the AS layer is responsible for handling the case where the cell is reselected while the waiting timer is running. This means that if the upper layer procedure is not triggered (e.g., due to cell reselection or during the waiting time), the AS layer should consider the AS layer procedure pending and should re-initiate it after the cell reselection. This means that after a cell reselection while the waiting timer is running, assuming that no upper layer events (e.g., mo-data, mo-signaling) have occurred, the UE will re-initiate any pending AS layer procedures (e.g., RNAU) in the new cell.

[0147] In the case where some upper layer events have occurred, it is recommended that after cell reselection while the waiting timer is running, the UE discards any pending AS layer procedures (e.g., RNAU) if an upper layer event has occurred (e.g., mo-data, mo-signaling).

[0148] Figure 8 Operations of a UE and a RAN node (e.g., a base station, such as a gNB) according to at least some aspects of the above embodiments are illustrated. As shown, the UE sends an RRC resume request (step 800). The RAN node receives the RRC resume request and, in response, sends an RRC reject with a wait time to the UE (step 802). Upon receiving the RRC reject message with a wait time, the UE starts a wait timer set to the wait time included in the RRC reject (step 804). While the wait timer is running, the UE performs a cell reselection to a new (i.e., target) cell (step 806). After performing a cell reselection to a new cell while the wait timer is running, the UE may re-initiate a pending AS layer process (e.g., RNAU) in the new cell. More specifically, in some embodiments, the UE determines whether an upper layer event has occurred (e.g., mo-data, mo-signaling) (step 808). If the upper layer event has not occurred (e.g., mo-data, mo-signaling), the UE re-initiates a pending AS layer process in the new cell (step 810). In contrast, if an upper layer event has occurred, the UE discards the pending AS layer procedure (812).

[0149] 3 UE behavior when performing cell reselection while T319 is running (before the UE receives any response message to the recovery)

[0150] Currently, in case of cell reselection while T319 is running, the following UE behavior is defined:

[0151]

[0152] The problem with this behavior is that it does not take into account that the resume can be triggered by NAS or upper layers or by cell reselection. Instead, the following behavior is suggested.

[0153] In the case where the recovery is triggered by the upper layer, after the cell is reselected during T319 is running, the AS layer in the UE notifies the upper layer of the recovery failure. Optionally, the UE can provide the reason for the recovery failure to the upper layer (for example, cell reselection). In this way, the upper layer can re-initiate the recovery process in the target cell. The upper layer may change during this process. For example, if the upper layer process is the initial mobile originated data, if the target cell does not belong to the current UE CN registration area, the upper layer process can be changed to mobile originated signaling (UE CN registration area update). It may also happen that the NAS layer chooses not to re-initiate the recovery in the target cell; for example, if the UE is not allowed to access the target cell (for example, area prohibition (Area Forbidden) has been configured at the NAS level).

[0154] In the case where recovery is triggered by AS level (e.g. RNAU), the following UE behavior is recommended. If the upper layer procedure is not triggered (e.g. due to cell reselection or during cell reselection), the AS layer considers the AS layer procedure pending and should be re-initiated after cell reselection. This means that after cell reselection while T319 is running, the UE re-initiates any pending AS layer procedure (e.g. RNAU) in the new cell assuming that no upper layer events have occurred (e.g. mo-data, mo-signaling). In the case where some upper layer events have occurred, it is recommended that the UE discards any pending AS layer procedure (e.g. RNAU) after cell reselection while T319 is running if an upper layer event has occurred (e.g. mo-data, mo-signaling).

[0155] Fig. 9Operations of a UE and a RAN node (e.g., a base station such as a gNB) according to at least some aspects of the above embodiments are illustrated. As shown, the UE sends an RRC recovery request (step 900) and starts a timer (e.g., timer T319) (step 902). In this example, the RRC recovery request is triggered by the AS level (e.g., by an AS level process such as an RNAU process). Timer T319 is a timer that is started when the RRC connection recovery process is initiated. While the timer is running, the UE performs cell reselection to a new cell (i.e., a target cell) (step 904). In other words, before receiving a response (e.g., RRC recovery or RRC rejection) from the RAN node, the UE performs cell reselection to the new cell. After performing cell reselection while the timer is running, the UE can re-initiate a pending AS layer process (e.g., RNAU) in the new cell. More specifically, in some embodiments, the UE determines whether an upper layer event has occurred (e.g., mo-data, mo-signaling) (step 906). If no upper layer event occurs (eg, mo-data, mo-signaling), the UE re-initiates the pending AS layer process in the new cell (step 908). Conversely, if an upper layer event has occurred, the UE discards the pending AS layer process (910).

[0156] 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 Fig.10 For simplicity, Fig.10 The wireless network of FIG. 1 depicts only network 1006, network nodes 1060 and 1060B, and wireless devices (WD) 1010, 1010B, and 1010C. In practice, the wireless network may further include any additional units suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, network node 1060 and WD 1010 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0157] A wireless network may include and / or be connected to 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 second, third, fourth, fifth generation (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.

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

[0159] The network node 1060 and the WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In various 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 over a wired or wireless connection.

[0160] As used herein, a network node refers to a device that is capable of, configured to, arranged to, 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 a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio APs), base stations (BSs) (e.g., radio base stations, node Bs, enhanced or evolved node Bs (eNBs), and gNBs). Base stations can be classified based on the amount of coverage provided by the base station (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 also referred to as a remote radio head (RRH)). Such an RRU 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). Other 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 (such as mobile switching centers (MSC), mobility management entities (MME)), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (such as evolved serving mobile positioning center (E-SMLC)) and / or minimization of drive tests (MDT). As another example, a 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 to, arranged to, and / or operable to enable a wireless device to access a wireless network and / or provide access to a wireless network to a wireless device or provide a certain service to a wireless device that has accessed a wireless network.

[0161] exist Fig.10 In the embodiment, the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig.10The network node 1060 shown in the example wireless network of can represent a device including a combination of hardware components illustrated, but other embodiments can include network nodes having different combinations of components. It should 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 1060 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 a single illustrated component (for example, the device readable medium 1080 may include multiple separate hard drives and multiple random access memory (RAM) modules).

[0162] Similarly, the network node 1060 may include multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In some cases where the network node 1060 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between several network nodes. For example, a single RNC may control multiple Node Bs. In this case, each unique Node B and RNC pair may be considered a separate network node in some cases. In some embodiments, the network node 1060 may be configured to support multiple RATs. In such an embodiment, some components may be replicated (e.g., separate device-readable media 1080 for different RATs), while some components may be reused (e.g., the same antenna 1062 may be shared by RATs). The network node 1060 may also include multiple groups of various illustrated components for different wireless technologies (e.g., GSM, wideband code division multiple access (WCDMA), LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into the network node 1060. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .

[0163] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as provided by the network node. These operations performed by the processing circuit 1070 may include: processing information obtained by the processing circuit 1070, such as 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 a determination as a result of the processing.

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

[0165] In some embodiments, processing circuitry 1070 may include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074. In some embodiments, RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on the same chip or chipset, board, or unit.

[0166] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 1070 executing instructions stored on a device-readable medium 1080 or a memory within the processing circuit 1070. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1070 without the need to execute instructions stored on a separate or separate device-readable medium, such as in a hard-wired manner. In any of these embodiments, the processing circuit 1070 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit 1070 or other components of the network node 1060, but are enjoyed by the network node 1060 as a whole and / or generally by end users and wireless networks.

[0167] Device-readable medium 1080 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, 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 storage device that stores information, data, and / or instructions that may be used by processing circuit 1070. Device-readable medium 1080 may store any suitable instructions, data, or information, including computer programs; software; applications including one or more of logic, rules, code, tables, etc.; and / or other instructions that are executable by processing circuit 1070 and utilized by network node 1060. Device-readable medium 1080 may be used to store any computations performed by processing circuit 1070 and / or any data received via interface 1090. In some embodiments, processing circuit 1070 and device-readable medium 1080 may be considered integrated.

[0168] Interface 1090 is used in wired or wireless communication of signaling and / or data between network node 1060, network 1006 and / or WD 1010. As shown, interface 1090 includes port / terminal 1094 to send and receive data to and from network 1006 on wired connection, for example. Interface 1090 also includes radio front-end circuit 1092 that can be coupled to antenna 1062 or as a part of antenna 1062 in some embodiments. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 can be connected to antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can be configured to adjust the signal transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can receive digital data to be sent to other network nodes or WD via wireless connection. Radio front-end circuit 1092 can use the combination of filter 1098 and / or amplifier 1096 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1092. The digital data may be passed to processing circuit 1070. In other embodiments, interface 1090 may include different components and / or different combinations of components.

[0169] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, but rather, the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without the separate radio front end circuit 1092. Similarly, in some embodiments, all or some of the RF transceiver circuit 1072 may be considered part of the interface 1090. In other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a wireless unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074, which is part of the digital unit (not shown).

[0170] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuit 1092 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 gigahertz (GHz) and 66GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as multiple input multiple output (MIMO). In some embodiments, antenna 1062 may be separated from network node 1060 and may be connected to network node 1060 via an interface or port.

[0171] Antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a WD, another network node and / or any other network device. Similarly, antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a WD, another network node and / or any other network device.

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

[0173] Alternative embodiments of network node 1060 may include Fig.10 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of a network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1060 may include a user interface device to allow information to be input into network node 1060 and to allow information to be output from network node 1060. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for network node 1060.

[0174] As used herein, WD refers to a device that can, is configured to, is arranged to and / or is operable to wirelessly communicate with a network node and / or other WD. Unless otherwise specified, the term WD can be used interchangeably with 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 send and / or receive wireless signals. In some embodiments, WD may be configured to send and / or receive information without direct human interaction. For example, WD may be designed to send information to the network according to a predetermined schedule when triggered by an internal or external event or in response to a request from the 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, tablet computers, laptop computers, laptop computer built-in devices (LEEs), laptop computer mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication (e.g., by implementing 3GPP standards for sidelink communication), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as a machine-type communication (MTC) device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0175] like Fig.10As shown, WD 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036, and power supply circuit 1037. WD 1010 can include multiple groups of one or more of the components shown for different wireless technologies supported by WD 1010 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, or Bluetooth wireless technologies, to name a few). These wireless technologies can be integrated into the same or different chips or chipsets as other components in WD 1010.

[0176] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 1014. In some alternative embodiments, antenna 1011 may be separated from WD 1010 and may be connected to WD 1010 via an interface or port. Antenna 1011, interface 1014, and / or processing circuit 1020 may be configured to perform any receiving or transmitting operation described herein as being performed by 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 1011 may be considered as an interface.

[0177] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020, and is configured to adjust the signal transmitted between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or as part of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered as part of the interface 1014. The radio front-end circuit 1012 may receive digital data sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect the radio signal, which is then converted into digital data by radio front end circuit 1012. The digital data may be passed to processing circuit 1020. In other embodiments, interface 1014 may include different components and / or different combinations of components.

[0178] The processing circuit 1020 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, an FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic, which is operable to provide WD 1010 functionality alone or in combination with other WD 1010 components (e.g., device readable medium 1030). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 1020 may execute instructions stored in the device readable medium 1030 or in a memory within the processing circuit 1020 to provide functionality disclosed herein.

[0179] As shown, the processing circuit 1020 includes one or more of the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of the WD 1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into one chip or chipset, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In yet another alternative embodiment, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 1022 may be part of interface 1014. RF transceiver circuit 1022 may condition RF signals for processing circuit 1020.

[0180] In some embodiments, some or all of the functions described herein as being performed by a WD or UE may be provided by a processing circuit 1020 that executes instructions stored on a device-readable medium 1030, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020 without the need to execute instructions stored on a separate or separate device-readable storage medium, such as in a hard-wired manner. In any of these specific embodiments, the processing circuit 1020 may be configured to perform the described functions, regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits 1020 or other components of WD1010, but are enjoyed by WD 1010 and / or end users and wireless networks as a whole.

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

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

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

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

[0185] In some embodiments, the power supply 1036 may take the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. The WD 1010 may also include a power circuit 1037 for transmitting power from the power supply 1036 to various parts of the WD 1010, which require power from the power supply 1036 to perform any function described or indicated herein. In some embodiments, the power circuit 1037 may include a power management circuit. The power circuit 1037 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 1010 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cable). In some embodiments, the power circuit 1037 may also be operable to transfer power from an external power source to the power supply 1036. This may be used, for example, to charge the power supply 1036. The power circuit 1037 may perform any formatting, conversion, or other modifications to the power from the power supply 1036 so that the power is suitable for the corresponding components to which the power of the WD 1010 is supplied.

[0186] Fig.11 A wireless communication system is shown represented as a 5G network architecture comprising core network functions (NFs), where the interaction between any two NFs is represented by point-to-point reference points / interfaces. Fig.11 can be considered as Fig.10 A specific implementation of system 1000.

[0187] From the access side, Fig.11 The 5G network architecture shown includes multiple UEs connected to the RAN or Access Network (AN) and the Access and Mobility Management Function (AMF). Typically, the RAN (AN) includes base stations such as eNBs or gNBs or similar. From the CN side, Fig.11 The 5G core NF shown in the figure includes a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM), an AMF, a session management function (SMF), a policy control function (PCF), and an application function (AF).

[0188] The reference point representation of the 5G network architecture is used to develop detailed call flows in the normalization standardization. The N1 reference point is defined to carry signaling between the UE and the AMF. The reference points for connecting between the AN and the AMF and between the AN and the UPF are defined as N2 and N3, respectively. There is a reference point N11 between the AMF and the SMF, which means that the SMF is at least partially controlled by the AMF. N4 is used by the SMF and the UPF, so the UPF can be set using the control signal generated by the SMF, and the UPF can report its status to the SMF. Accordingly, N9 is a reference point for connections between different UPFs, and N14 is a reference point for connections between different AMFs. Because the PCF applies policies to the AMF and SMP, respectively, N15 and N7 are defined. N12 is required for the AMF to perform authentication of the UE. N8 and N10 are defined because the AMF and SMF need the UE's subscription data.

[0189] The 5G core network is designed to separate the user plane and the control plane. The user plane carries user services, while the control plane carries signaling in the network. Fig.11 In the NF, UPF is in the user plane, while all other NFs (i.e., AMF, SMF, PCF, AF, AUSF, and UDM) are in the control plane. Separating the user plane and the control plane ensures that the resources of each plane are scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. In this architecture, for certain applications that require low latency, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network.

[0190] The core 5G network architecture includes modular functions. For example, AMF and SMF are independent functions in the control plane. Separating AMF and SMF allows independent evolution and scaling. Fig.11 As shown in Figure 1, other control plane functions (such as PCF and AUSF) can be separated. The modular functional design enables the 5G core network to flexibly support various services.

[0191] Each NF interacts directly with another NF. Messages can be routed from one NF to another using intermediate functions. In the control plane, a set of interactions between two NFs is defined as a service so that the set of interactions can be reused. The service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0192] Fig.12 A 5G network architecture is shown that uses a service-based interface between NFs in the control plane instead of Fig.11 Point-to-point reference points / interfaces used in the 5G network architecture. Fig.11The NF described corresponds to Fig.12 The services provided by NF to other authorized NFs can be exposed to the authorized NF through a service-based interface. Fig.12 In the NF, the service-based interface is indicated by the letter "N" followed by the name of the NF, such as Namf is used for the service-based interface of AMF, Nsmf is used for the service-based interface of SMF, etc. Fig.12 The Network Exposure Function (NEF) and Network Repository Function (NRF) in Fig.11 However, it should be clarified that although not shown in Fig.11 Explicitly indicated in Fig.11 All NFs depicted in the figure can be used with Fig.12 The NEF and NRF interact.

[0193] Fig.11 and 12 Some of the characteristics of the NFs shown in can be described in the following way. AMF provides UE-based authentication, authorization, mobility management, etc. Even UEs using multiple access technologies are basically connected to a single AMF because the AMF is independent of the access technology. SMF is responsible for session management and assigns IP addresses to UEs. It also selects and controls the UPF for data transmission. If the UE has multiple sessions, different SMFs can be assigned to each session to manage these sessions individually, and different functions may be provided per session. AF provides information about packet flows to the PCF responsible for policy control in order to support quality of service (QoS). Based on this information, the PCF determines policies on mobility and session management so that the AMF and SMF can operate normally. AUSF supports authentication functions for UEs or similar devices, and therefore stores data for authentication of UEs or similar devices, while UDM stores subscription data for UEs. The data network (DN) (which is not part of the 5G core network) provides Internet access or operator services and similar services.

[0194] NFs can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on a suitable platform (e.g., cloud infrastructure).

[0195] Fig.13One embodiment of a UE in accordance with various aspects described herein is shown. 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. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE1300 may be any UE identified by 3GPP, including a NB-IoT UE, an MTC UE, and / or an enhanced MTC (eMTC) UE. As Fig.13 As shown, UE 1300 is an example of a WD that is configured to communicate according to one or more communication standards promulgated by 3GPP (e.g., 3GPP's GSM, UMTS, LTE and / or 5G standards). As mentioned above, the terms WD and UE can be used interchangeably. Therefore, although Fig.13 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0196] exist Fig.13 In the embodiment, UE 1300 includes a processing circuit 1301 operatively coupled to an input / output interface 1305, an RF interface 1309, a network connection interface 1311, a memory 1315 (including RAM 1317, ROM 1319, and storage medium 1321, etc.), a communication subsystem 1331, a power supply 1333, and / or any other components, or any combination thereof. Storage medium 1321 includes an operating system 1323, an application 1325, and data 1327. In other embodiments, storage medium 1321 may include other similar types of information. Some UEs may utilize Fig.13 All components shown, or only a subset of these components. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0197] exist Fig.13, processing circuit 1301 may be configured to process computer instructions and data. Processing circuit 1301 may be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as one or more hardware-implemented state machines (e.g., in the form of discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or DSPs) and appropriate software; or any combination of the above. For example, processing circuit 1301 may include two CPUs. Data may be information in a form suitable for use by a computer.

[0198] In the depicted embodiment, the input / output interface 1305 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1300 may be configured to use an output device via the input / output interface 1305. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1300 or to provide output from the UE 1300. 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 1300 may be configured to use an input device via the input / output interface 1305 to allow a user to capture information into the UE 1300. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, 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, an optical 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 an optical sensor.

[0199] exist Fig.13In the embodiment of the present invention, the RF interface 1309 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface 1311 can be configured to provide a communication interface to the network 1343A. The network 1343A can cover wired and / or wireless networks, such as LAN, WAN, computer network, wireless network, telecommunication network, another similar network, or any combination thereof. For example, the network 1343A can include a Wi-Fi network. The network connection interface 1311 can be configured to include a receiver and transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (e.g., Ethernet, Transmission Control Protocol (TCP) / IP, Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), etc.). The network connection interface 1311 can implement receiver and transmitter functions 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 instead.

[0200] RAM 1317 may be configured to be connected to processing circuit 1301 via bus 1302 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 1319 may be configured to provide computer instructions or data to processing circuit 1301. For example, ROM 1319 may be configured to store unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, or keystrokes received from a keyboard) stored in non-volatile memory. Storage medium 1321 may be configured to include memory such as RAM, ROM, programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 1321 may be configured to include operating system 1323; application 1325 such as a web browser application, a widget or gadget engine, or another application; and data file 1327. The storage medium 1321 may store any one of various operating systems or a combination of operating systems for use by the UE 1300 .

[0201] The storage medium 1321 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 (e.g., a subscriber identity module (SIM) or a removable user identity (RUIM) module), other memory, or any combination thereof. The storage medium 1321 may allow the UE 1300 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 1321, which may include a device-readable medium.

[0202] exist Fig.13 In the embodiment of the present invention, the processing circuit 1301 may be configured to communicate with the network 1343B using the communication subsystem 1331. The network 1343A and the network 1343B may be the same network or different networks. The communication subsystem 1331 may be configured to include one or more transceivers for communicating with the network 1343B. For example, the communication subsystem 1331 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE or base station of RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.7, code division multiple access (CDMA), WCDMA, GSM, LTE, universal terrestrial RAN (UTRAN), WiMax, etc.). Each transceiver may include a transmitter 1333 and / or a receiver 1335 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 1333 and the receiver 1335 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0203] In the illustrated embodiment, the communication functions of the communication subsystem 1331 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 location), another similar communication function, or any combination thereof. For example, the communication subsystem 1331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1343B may include a wired and / or wireless network, such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1343B may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1313 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1300.

[0204] The features, benefits and / or functions described herein may be implemented in one of the components of UE 1300, or may be divided between multiple components of UE 1300. 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 1331 may be configured to include any component described herein. In addition, the processing circuit 1301 may be configured to communicate with any such component via a bus 1302. In another example, any such component may be represented by a program instruction stored in a memory, which performs the corresponding function described herein when executed by the processing circuit 1301. In another example, the function of any such component may be divided between the processing circuit 1301 and the communication subsystem 1331. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0205] Fig.14 1400 is a schematic block diagram illustrating a virtualized environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, 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 relates to an implementation in which at least a portion of the functions are 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).

[0206] 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 1400 hosted by one or more hardware nodes 1430. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), then the network nodes may be fully virtualized.

[0207] These functions may be implemented by one or more applications 1420 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement certain features, functions, and / or benefits of some embodiments disclosed herein. The applications 1420 run in a virtualized environment 1400, which provides hardware 1430 including processing circuitry 1460 and memory 1490. The memory 1490 contains instructions 1495 executable by the processing circuitry 1460, whereby the applications 1420 are operable to provide one or more features, benefits, and / or functions disclosed herein.

[0208] The virtualized environment 1400 includes general-purpose or special-purpose network hardware devices 1430, which include a set of one or more processors or processing circuits 1460, which may be commercial off-the-shelf (COTS) processors, special-purpose ASICs, or any other type of processing circuit including digital or analog hardware components or special-purpose processors. Each hardware device 1430 may include a memory 1490-1, which may be a non-persistent memory for temporarily storing instructions 1495 or software executed by the processing circuit 1460. Each hardware device 1430 may include one or more network interface controllers (NICs) 1470 (also known as network interface cards), which include a physical network interface 1480. Each hardware device 1430 may also include a non-transitory persistent machine-readable storage medium 1490-2 in which software 1495 and / or instructions executable by the processing circuit 1460 are stored. The software 1495 may include any type of software including software for instantiating one or more virtualization layers 1450 (also referred to as hypervisors), software for executing virtual machines 1440, and software that enables them to perform the functions, features and / or benefits associated with some of the embodiments described herein.

[0209] The virtual machine 1440 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1450 or a system hypervisor. Different embodiments of the instance of the virtual device 1420 can be implemented on one or more virtual machines 1440, and the implementation can take different approaches.

[0210] During operation, processing circuitry 1460 executes software 1495 to instantiate a hypervisor or virtualization layer 1450, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1450 may present to virtual machines 1440 a virtual operating platform that appears to be networked hardware.

[0211] like Fig.14 As shown, hardware 1430 can be an independent network node with common or specific components. Hardware 1430 can include antenna 14225, and some functions can be implemented through virtualization. Alternatively, hardware 1430 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), in which many hardware nodes work together and are managed via management and orchestration (MANO) 14100 that supervises the lifecycle management of application 1420, etc.

[0212] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and CPEs.

[0213] In the context of NFV, a virtual machine 1440 may be a software implementation of a physical program that runs the program as if they were executed on a physical, non-virtualized machine. Each virtual machine 1440 and the portion of the hardware 1430 that executes the virtual machine 1440 (whether hardware dedicated to the virtual machine 1440 and / or hardware shared by the virtual machine 1440 with other virtual machines 1440) form a separate virtual network element (VNE).

[0214] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions in one or more virtual machines 1440 running on top of the hardware network infrastructure 1430 and interacting with Fig.14 Corresponding to application 1420 in.

[0215] In some embodiments, one or more radio units 14200, each including one or more transmitters 14220 and one or more receivers 14210, may be coupled to one or more antennas 14225. The radio units 14200 may communicate directly with the hardware nodes 1430 via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities for virtual nodes, such as radio access nodes or base stations.

[0216] In some embodiments, some signaling may be accomplished using a control system 14230 , which may alternatively be used for communications between the hardware node 1430 and the radio unit 14200 .

[0217] refer to Fig.15 According to an embodiment, a communication system includes a telecommunication network 1510 such as a 3GPP type cellular network, which includes an access network 1511 such as a radio access network and a core network 1514. The access network 1511 includes a plurality of base stations 1512A, 1512B, 1512C, such as Node Bs, eNBs, gNBs or other types of wireless APs, each defining a corresponding coverage area 1513A, 1513B, 1513C. Each base station 1512A, 1512B, 1512C may be connected to the core network 1514 via a wired or wireless connection 1515. A first UE 1591 located in the coverage area 1513C is configured to be wirelessly connected to or paged by the corresponding base station 1512C. A second UE 1592 in the coverage area 1513A may be wirelessly connected to the corresponding base station 1512A. Although multiple UEs 1591 , 1592 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to the corresponding base station 1512 .

[0218] The telecommunications network 1510 itself is connected to a host computer 1530, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1530 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 1521 and 1522 between the telecommunications network 1510 and the host computer 1530 may extend directly from the core network 1514 to the host computer 1530, or may be via an optional intermediate network 1520. The intermediate network 1520 may be one of a public, private, or managed network, or a combination of multiple thereof; the intermediate network 1520 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1520 may include two or more sub-networks (not shown).

[0219] Overall, Fig.15The communication system implements a connection between the connected UE 1591, 1592 and the host computer 1530. The connection can be described as an Over-the-Top (OTT) connection 1550. The host computer 1530 and the connected UE 1591, 1592 are configured to use the access network 1511, the core network 1514, any intermediate network 1520, and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 1550. The OTT connection 1550 can be transparent because the participating communication devices through which the OTT connection 1550 passes are unaware of the routing of uplink and downlink communications. For example, the past routing of the incoming downlink communication, which has data originating from the host computer 1530 to be forwarded (e.g., handed over) to the connected UE 1591, may not be notified or need not be notified to the base station 1512. Similarly, base station 1512 need not be aware of the future routing of outgoing uplink communications originating from UE 1591 toward host computer 1530 .

[0220] According to one embodiment, reference will now be made to Fig.16 Describe the example implementations of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system 1600, the host computer 1610 includes hardware 1615, which includes a communication interface 1616 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 1600. The host computer 1610 also includes a processing circuit 1618, which may have storage and / or processing capabilities. In particular, the processing circuit 1618 may include one or more programmable processors, ASICs, FPGAs, or a combination of these items (not shown) suitable for executing instructions. The host computer 1610 also includes software 1611, which is stored in the host computer 1610 or can be accessed by the host computer 1610 and can be executed by the processing circuit 1618. Software 1611 includes a host application 1612. The host application 1612 is operable to provide services to a remote user, such as a UE 1630 connected via an OTT connection 1650 terminating at the UE 1630 and the host computer 1610. In providing services to the remote user, the host application 1612 may provide user data sent using the OTT connection 1650.

[0221] The communication system 1600 also includes a base station 1620, which is provided in the telecommunication system and includes hardware 1625 that enables it to communicate with the host computer 1610 and with the UE 1630. The hardware 1625 may include a communication interface 1626 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1600, and for establishing and maintaining connections with the base stations 1620 located in the coverage area ( Fig.16 The communication interface 1626 may be configured to facilitate a connection 1660 to the host computer 1610. The connection 1660 may be direct or may be through a core network (eg, a telecommunications system) of the telecommunications system. Fig.10 1620) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1625 of the base station 1620 also includes processing circuitry 1628, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these items (not shown) adapted to execute instructions. The base station 1620 also has software 1621 stored internally or accessible via an external connection.

[0222] The communication system 1600 also includes the UE 1630 already mentioned. The hardware 1635 of the UE 1630 may include a radio interface 1637, which is configured to establish and maintain a wireless connection 1670 with a base station serving the coverage area where the UE 1630 is currently located. The hardware 1635 of the UE 1630 also includes a processing circuit 1638, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these items (not shown) suitable for executing instructions. The UE 1630 also includes software 1631 stored in the UE 1630 or accessible by the UE 1630 and executable by the processing circuit 1638. The software 1631 includes a client application 1632. The client application 1632 is operable to provide services to human or non-human users via the UE 1630 with the support of the host computer 1610. In the host computer 1610, the executing host application 1012 can communicate with the executing client application 1632 via the OTT connection 1650 that terminates at the UE 1630 and the host computer 1610. In providing services to users, the client application 1632 can receive request data from the host application 1012 and provide user data in response to the request data. The OTT connection 1650 can transmit both the request data and the user data. The client application 1632 can interact with the user to generate user data provided by the user.

[0223] Notice, Fig.16The host computer 1610, base station 1620 and UE 1630 shown can be respectively Fig.15 The host computer 1530, one of the base stations 1512AA, 1512B, 1512C, and one of the UEs 1591, 1592 may be similar or identical. That is, the internal working principles of these entities may be as follows: Fig.16 As shown, independently, the surrounding network topology can be Fig.15 The surrounding network topology.

[0224] exist Fig.16 16, an OTT connection 1650 has been abstractly drawn to illustrate communications between a host computer 1610 and a UE 1630 via a base station 1620, without explicit reference to any intermediate devices and the exact routing of messages via those devices. The network infrastructure may determine the routing, which may be configured to hide the routing from the UE 1630 or from the service provider operating the host computer 1610, or both. When the OTT connection 1650 is active, the network infrastructure may further make decisions according to which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0225] The wireless connection 1670 between the UE 1630 and the base station 1620 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 1630 using the OTT connection 1650 (where the wireless connection 1670 forms the last segment).

[0226] The measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1650 between the host computer 1610 and the UE 1630. The measurement process and / or network function for reconfiguring the OTT connection 1650 may be implemented in the software 1611 and hardware 1615 of the host computer 1610 or in the software 1631 and hardware 1635 of the UE 1630, or in both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1650 passes; the sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software 1611, 1631 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 1650 may include message formats, retransmission settings, preferred routes, etc. The reconfiguration does not need to affect the base station 1620, and it may be unknown or imperceptible to the base station 1620. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 1610 to measure throughput, propagation time, latency, etc. The measurements may be achieved because the software 1611, 1631 causes messages, particularly empty or "dummy" messages, to be sent using the OTT connection 1650 during its monitoring of propagation time, errors, etc.

[0227] Fig.17 is a flow chart showing 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 Fig.15 and Fig.16 For simplicity of this disclosure, this section only includes Fig.17 . In step 1710, the host computer provides user data. In sub-step 1711 of step 1710 (which may be optional), the host computer provides the user data by executing a host application. In step 1720, the host computer initiates a transmission to the UE carrying the user data. In step 1730 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0228] Fig.18 is a flow chart showing 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 Fig.15 and Fig.16 For simplicity of this disclosure, this section only includes Fig.18 . In step 1810 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 1820, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout this disclosure, the transmission may be via a base station. In step 1830 (which may be optional), the UE receives the user data carried in the transmission.

[0229] Fig.19 is a flow chart showing 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 Fig.15 and Fig.16 For simplicity of this disclosure, this section only includes Fig.19 . In step 1910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1920, the UE provides user data. In sub-step 1921 (which may be optional) of step 1920, the UE provides user data by executing a client application. In sub-step 1911 (which may be optional) of step 1910, the UE executes a client application that provides user data in response to received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in sub-step 1930 (which may be optional). In step 1940 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0230] Fig. 20 is a flow chart showing 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 Fig.15 and Fig.16 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section are included. Fig. 20 In step 2010 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0231] 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 that may include one or more microprocessors or microcontrollers and other digital hardware that may include DSPs, dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. The program codes stored in the memory include 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 embodiments, the processing circuit may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0232] The term "unit" may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc. as described herein.

[0233] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over subsequent listings.

[0234] ●2G Second Generation

[0235] ●3G Third Generation

[0236] ●3GPP Third Generation Partnership Project

[0237] ●4G Fourth Generation

[0238] 5G fifth generation

[0239] ●AC

[0240] AF application function

[0241] ●AMF access and mobility management function

[0242] ●AN access network

[0243] ●AP Access Point

[0244] ●AS access layer

[0245] ●ASIC Application-Specific Integrated Circuit

[0246] ●ATM Asynchronous Transfer Mode

[0247] ●AUSF authentication server function

[0248] BS Base Station

[0249] ●BSC Base Station Controller

[0250] ●BTS Base Transceiver Station

[0251] ●Carrier aggregation

[0252] ●CD

[0253] ●CDMA Code Division Multiple Access

[0254] CN Core Network

[0255] ●COTS Commercial Off-the-Shelf

[0256] ●CPE

[0257] ●CPU Central Processing Unit

[0258] ●D2D device to device

[0259] ●DAS Distributed Antenna System

[0260] ●DC dual connection

[0261] ●DIMM Dual In-line Memory Module

[0262] ●DN Data Network

[0263] ●DRB Data Radio Bearer

[0264] ●DRX Discontinuous Reception

[0265] ●DSP Digital Signal Processor

[0266] ●DVD Digital Video Disc

[0267] ●EEPROM Electrically Erasable Programmable Read-Only Memory

[0268] ●eMTC Enhanced Machine Type Communication

[0269] ●eNB Enhanced or Evolved Node B

[0270] ●EPROM Erasable Programmable Read Only Memory

[0271] ●E-SMLC Evolved Service Mobile Location Center

[0272] ●E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0273] ●FFS needs further study

[0274] ●FPGA Field Programmable Gate Array

[0275] GHz Gigahertz

[0276] ●gNB New Radio Base Station

[0277] GPS

[0278] ●GSM Global System for Mobile Communications

[0279] ●HDDS holographic digital data storage

[0280] ●HD-DVD High-density digital versatile disc

[0281] I / O input and output

[0282] IoT

[0283] IP Internet Protocol

[0284] ●I-RNTI Inactive Radio Network Temporary Identifier

[0285] LAN

[0286] ●LEE laptop embedded device

[0287] ●LME laptop installation equipment

[0288] LTE Long Term Evolution

[0289] ●M2M Machine to Machine

[0290] ●MANO management and orchestration

[0291] ●MCE Multi-cell / Multicast Coordination Entity

[0292] ●MCG Master Cell Group

[0293] ●MDT Minimized Drive Test

[0294] MIMO Multiple Input Multiple Output

[0295] ●MME Mobility Management Entity

[0296] ●MSC Mobile Switching Center

[0297] ●MSR Multi-Standard Radio

[0298] ●MTC Machine Type Communication

[0299] NAS Non-Access Stratum

[0300] NB-IoT Narrowband Internet of Things

[0301] ●NEF network exposure function

[0302] NF Network Function

[0303] ●NFV Network Function Virtualization

[0304] NIC Network Interface Controller

[0305] NR New Radio

[0306] NRF network repository function

[0307] NSSF network slice selection function

[0308] O&M Operation and Maintenance

[0309] OSS Operation Support System

[0310] ●OTT Over the Top

[0311] PCF policy control function

[0312] ●PDA Personal Digital Assistant

[0313] ●PROM Programmable Read Only Memory

[0314] ●PSTN Public Switched Telephone Network

[0315] QoS Quality of Service

[0316] ●RAID Redundant Array of Independent Disks

[0317] RAM Random Access Memory

[0318] RAN Radio Access Network

[0319] ●RAT Radio Access Technology

[0320] RF

[0321] ●RNA Notification Area based on Radio Access Network

[0322] ●RNAU Radio Access Network-based Notification Area Update

[0323] ●RNC Radio Network Controller

[0324] ●ROM Read Only Memory

[0325] ●RRC Radio Resource Control

[0326] ●RRH Remote Radio Head

[0327] ●RRU Remote Radio Unit

[0328] ●RTT Round Trip Time

[0329] ●RUIM Removable User Identity

[0330] ●SCell auxiliary cell

[0331] ●SCG Secondary Cell Group

[0332] ●SDRAM Synchronous Dynamic Random Access Memory

[0333] ●SIM Subscriber Identity Module

[0334] ●SMF session management function

[0335] ●SOC System on Chip

[0336] ●SON self-organizing network

[0337] ●SONET Synchronous Optical Network

[0338] ●SpCell dedicated cell

[0339] ●SRB Signaling Radio Bearer

[0340] ●S-TMSI System Architecture Evolution Temporary Mobile Subscriber Identity

[0341] ●TA tracking area

[0342] ●TCP Transmission Control Protocol

[0343] ●TP Text Proposal

[0344] ●UDM unified data management

[0345] UE User Equipment

[0346] UL Uplink

[0347] ●UMTS Universal Mobile Telecommunications System

[0348] ●USB Universal Serial Bus

[0349] ●UTRAN Universal Terrestrial Radio Access Network

[0350] ●V2I Vehicle to Infrastructure

[0351] ●V2V vehicle to vehicle

[0352] ●V2X: Vehicle to Everything

[0353] ●VMM Virtual Machine Monitor

[0354] ●VNE Virtual Network Element

[0355] ●VNF Virtual Network Function

[0356] ●VoIP Voice over Internet Protocol

[0357] WAN

[0358] ●WCDMA Wideband Code Division Multiple Access

[0359] ●WD Wireless Devices

[0360] ●WiMax Worldwide Interoperability for Microwave Access

[0361] ●WLAN Wireless Local Area Network

[0362] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method for operating a wireless device in a cellular communication system, the method comprising: sending a radio resource control (RRC) resume request to a radio access network (RAN) node; receiving, in response to the RRC resume request, an RRC resume reject message including a wait timer value from the RAN node; Starting a wait timer initialized with the wait timer value; discarding at least one security key; and A second RRC resumption request is sent when the waiting timer has expired.

2. The method according to claim 1, further comprising: Determine whether the upper-level event has occurred; as well as If the upper layer event has occurred, the pending access stratum (AS) layer process is re-initiated in the target cell.

3. The method according to claim 2, further comprising: If the upper layer event has occurred, the pending AS layer process is discarded.

4. The method according to claim 2, wherein: The upper layer event is mobile originated data or mobile originated signaling.

5. The method according to claim 2, wherein: The pending AS layer procedure is based on the RAN Notification Area Update (RNAU) procedure.

6. A wireless device for a cellular communication system, the wireless device comprising: Radio front-end circuits; as well as processing circuitry associated with the radio front end circuitry, the processing circuitry being configured to cause the wireless device to: sending a radio resource control (RRC) resume request to a radio access network (RAN) node; receiving, in response to the RRC resume request, an RRC resume reject message including a wait timer value from the RAN node; Starting a wait timer initialized with the wait timer value; discarding at least one security key; and A second RRC resumption request is sent when the waiting timer has expired.

7. The wireless device according to claim 6, wherein: The processing circuit is further configured to cause the wireless device to: Determine whether the upper level event has occurred; and If the upper layer event has occurred, the pending access stratum (AS) layer process is re-initiated in the target cell.

8. The wireless device according to claim 7, wherein: The processing circuit is further configured to cause the wireless device to discard the pending AS layer process if the upper layer event has occurred.

9. The wireless device according to claim 7, wherein: The upper layer event is mobile originated data or mobile originated signaling.

10. The wireless device of claim 7, wherein: The pending AS layer procedure is based on the RAN Notification Area Update (RNAU) procedure.

Images