Method and ue for avoiding unnecessary action for connection establishment

Abstract

A method of resuming a connection in a UE and a corresponding UE are disclosed. The method comprises sending an RRC resume request to a network node to initiate an RRC connection resume procedure, starting a timer for the RRC connection resume procedure, wherein expiry of the timer stops the RRC connection resume procedure for the UE, and stopping the timer upon one of: the UE receiving a suspend message, and the UE receiving a release message.

Description

[0001] This application is a divisional application of PCT patent application No. 201980021256.1, entitled "Method and UE for Establishing Connections to Avoid Unnecessary Actions," which was filed with the International Bureau on March 8, 2019, and entered the Chinese national phase on September 22, 2020. Technical Field

[0002] Specific embodiments relate to the field of avoiding unnecessary actions against user equipment; and more specifically, to methods and apparatus for avoiding unnecessary actions against user equipment during recovery in 5G radio. Background Technology

[0003] The Radio Resource Control (RRC) connection restoration process in LTE requires a pause mechanism to properly halt the process. In LTE Release 13, a mechanism was introduced for the network to pause the User Equipment (UE) in a paused state similar to RRC_IDLE, but with the difference being that the UE stores either the Access Stratum (AS) context or the RRC context. This makes it possible to reduce signaling when the UE becomes active again by restoring the RRC connection without having to rebuild it from scratch as before. Reduced signaling can have several benefits, such as reduced latency (e.g., for smartphones accessing the internet), and reduced signaling leads to reduced battery consumption for machine-type devices that transmit little data.

[0004] Version 13 solution is based on the UE sending an RRCConnectionResumeRequest message to the network and receiving an RRCConnectionResume from the network in response. The RRCConnectionResume is not encrypted, but is protected for integrity.

[0005] In LTE Release 13 and NR, as part of the 5G NR standardization work in 3GPP, it has been determined that NR should support the RRC_INACTIVE state with attributes similar to the paused state in LTE Release 13. RRC_INACTIVE differs slightly from this late state in that it is a separate RRC state, rather than being part of RRC IDLE as in LTE. Furthermore, it remains RRC INACTIVE when the core network (CN) / radio access network (RAN) connection using the Next Generation (NG) or N2 interface is paused in LTE.

[0006] Figure 1The transitions between example states in NR are illustrated. The attributes of RRC IDLE include: UE-specific discontinuous reception (DRX) configured by the upper layer; UE-controlled mobility based on network configuration; UE monitoring of the paging channel for CN paging using 5G-S-TMSI (e.g., 5G System Architecture Evolution (SAE) - Temporary Mobile Subscriber Identity); UE performing neighbor cell measurements, cell selection, and cell reselection; and UE acquiring system information. The attributes of RRC INACTIVE include: UE-specific DRX configured by the upper layer or by the RRC layer; UE-controlled mobility based on network configuration; UE storing AS context; UE monitoring of the paging channel for CN paging using 5G-S-TMSI and RAN paging using I-RNTI (e.g., Inactive Radio Network Temporary Identifier); performing neighbor cell measurements, cell selection, and cell reselection; periodically performing RAN-based notification area updates when moving out of the RAN-based notification area; and acquiring system information. The attributes of RRC CONNECTED include: UE storing AS context; transmitting unicast data to / from the UE; UE configuring UE-specific DRX at lower layers; using one or more secondary cells (SCells) to support carrier aggregation with secondary primary cells (SpCells) to increase bandwidth for UEs; using secondary cell groups (SCGs) to support dual connectivity (DC) UEs with aggregation with primary cell groups (MCGs) to increase bandwidth; network-controlled mobility, i.e., handover within NR and to / from E-UTRAN. Additionally, the attributes of RRC CONNECTED include: UE monitoring paging channels; monitoring control channels associated with shared data channels to determine if data has been scheduled for them; providing channel quality and feedback information; performing neighbor cell measurements and measurement reports; and acquiring system information.

[0007] In LTE, the current mechanism involves the UE verifying messages from the network before encryption begins. However, in LTE, there are now additional messages sent from the network to the UE that are used to initiate or resume encrypted RRC signaling. These messages are integrity-protected but not encrypted. The following excerpts from the 3GPP LTE RRC specification TS 36.331v15.0.0 illustrate how the UE verifies the integrity of these messages at the RRC level. As can be seen in all cases, the UE RRC will query the lower layer (e.g., Packet Data Convergence Protocol (PDCP)) upon receiving a message to verify its integrity. If the message is verified, the UE RRC layer configures the lower layer to apply encryption and integrity protection to all subsequent messages.

[0008] Figure 2 and Figure 3This illustrates an example recovery process failure due to poor downlink / uplink radio conditions. Regarding T300 failure handling in LTE, there is a failure timer T300 that starts when the UE performs an establishment or recovery procedure. The purpose of the failure timer is to stop the procedure if the UE does not receive any valid response from the network. For example, a situation may have arisen where the UE does not receive any valid response due to downlink problems in receiving the response message, or even due to uplink problems. This prevents the UE from getting stuck waiting for a message from the network that will never arrive. Then, timer T300 stops when the UE receives a valid message, or it times out. In the latter case, the UE performs some action and notifies the upper layer.

[0009] The following excerpt from 3GPP TS 36.331 provides additional context. The UE initiates this procedure when the upper layer requests to establish or restore an RRC connection while the UE is in RRC_IDLE. Except for NB-IoT, when initiating this procedure, the UE should:

[0010] 1> If SystemInformationBlockType2 includes ac-BarringPerPLMN-List, and ac-BarringPerPLMN-List contains AC-BarringPerPLMN entries with plmn-IdentityIndex corresponding to the PLMN selected at the upper level (see TS 23.122

[11] , TS 24.301

[35] ):

[0011] 2> Select the AC-BarringPerPLMN entry that has the plmn-IdentityIndex corresponding to the PLMN selected above;

[0012] 2> In the remainder of this process, the selected AC-BarringPerPLMN entry (i.e., the presence or absence of the access prohibition parameter in the entry) is used, regardless of the common access prohibition parameters included in SystemInformationBlockType2;

[0013] 1> Otherwise

[0014] 2> In the remainder of this process, the public access prohibition parameters included in SystemInformationBlockType2 (i.e., the presence or absence of these parameters) are used;

[0015] 1> If SystemInformationBlockType2 contains acdc-BarringPerPLMN-List, and acdc-BarringPerPLMN-List contains ACDC-BarringPerPLMN entries with plmn-IdentityIndex corresponding to the PLMN selected above (see TS 23.122

[11] , TS 24.301

[35] ):

[0016] 2> Select the ACDC-BarringPerPLMN entry that has a plmn-IdentityIndex corresponding to the PLMN selected above;

[0017] 2> In the remainder of this process, the selected ACDC-BarringPerPLMN entry (i.e., the presence or absence of the access prohibition parameter in the entry) is used, regardless of the acdc-BarringForCommon parameter included in SystemInformationBlockType2;

[0018] 1> Otherwise:

[0019] 2> In the remainder of this process, an ACDC prohibition check is performed using acdc-BarringForCommon (i.e., the presence or absence of these parameters) included in SystemInformationBlockType2;

[0020] 1> If the upper layer indicates that the RRC connection conforms to EAB (see TS 24.301

[35] ):

[0021] 2> If the result of the EAB check specified in 5.3.3.12 is that access to the cell is prohibited:

[0022] 3> Use a pause indicator to notify the upper layer that establishing or restoring an RRC connection has failed, and notify the upper layer that EAB is applicable. At this point, the process ends.

[0023] 1> If the upper layer indicates that the RRC connection conforms to ACDC (see TS 24.301

[35] ), then SystemInformationBlockType2 contains BarringPerACDC-CategoryList, and acdc-HPLMNonly indicates that ACDC applies to the UE:

[0024] 2> If BarringPerACDC-CategoryList contains BarringPerACDC-Category entries corresponding to the ACDC category selected above:

[0025] 3> Select the BarringPerA CDC-Category entry that corresponds to the ACDC category selected above;

[0026] 2> Otherwise:

[0027] 3> Select the last BarringPerA CDC-Category entry in the BarringPerA CDC-CategoryList;

[0028] 2> Stop timer T308 (if it is running);

[0029] 2> Use T308 as "Tbarring" and acdc-BarringConfig in BarringPerA CDC-Category as "ACDC prohibition parameter" to perform the access prohibition check specified in 5.3.3.13;

[0030] 2> If access to the cell is blocked:

[0031] 3> Use a pause indication to notify the upper layer that establishing or restoring an RRC connection has failed, and notify the upper layer that access is prohibited due to ACDC. At this point, the process ends.

[0032] 1> Otherwise, if the UE is establishing an RRC connection for a mobile-terminated call:

[0033] 2> If timer T302 is running:

[0034] 3> Use a pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile termination call is applicable. At this point, the process ends.

[0035] 1> Otherwise, if the UE is establishing an RRC connection for an emergency call:

[0036] 2> If SystemInformationBlockType2 includes ac-BarringInfo:

[0037] 3> If ac-BarringForEmergency is set to TRUE:

[0038] 4> If the UE has one or more access classes (stored on the USIM) and its value is in the range 11..15, the value is valid for the UE according to TS 22.011

[10] and TS 23.122

[11] :

[0039] Note 1: AC 12, 13, and 14 are valid only in this country, and AC 11 and 15 are valid only in HPLM / EHPLMN.

[0040] 5> If ac-BarringInfo includes ac-BarringForMO-Data, and for all of these valid access classes of the UE, the corresponding bit in ac-BarringForSpeciaMC contained in ac-BarringForMO-Data is set to 1:

[0041] 6> It is believed that access to the cell is prohibited;

[0042] 4> Otherwise:

[0043] 5> It is believed that access to the cell is prohibited;

[0044] 2> If access to the cell is blocked:

[0045] 3> Use a pause indicator to notify the upper layer that establishing or restoring an RRC connection has failed; at this point, the process ends.

[0046] 1> Otherwise, if the UE is establishing an RRC connection for a mobile-initiated call:

[0047] 2> Use T303 as "Tbarring" and ac-BarringForMO-Data as "AC prohibition parameter" to perform the access prohibition check specified in 5.3.3.11;

[0048] 2> If access to the cell is blocked:

[0049] 3> If SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

[0050] 4> Use the pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile-initiated call is applicable. At this point, the process ends.

[0051] 3> Otherwise (SystemInformationBlockType2 does not include ac-BarringForCSFB, and the UE supports CS fallback):

[0052] 4> If timer T306 is not running, then start T306 with the timer value of T303;

[0053] 4> Use the pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for mobile-initiated calls and mobile-initiated CS fallbacks is applicable. At this point, the process ends.

[0054] 1> Otherwise, if the UE is initiating signaling to establish an RRC connection for mobility:

[0055] 2> Use T305 as "Tbarring" and ac-BarringForMO-Signalling as "AC prohibition parameter" to perform the access prohibition check specified in 5.3.3.11;

[0056] 2> If access to the cell is blocked:

[0057] 3> Use a pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile-initiated signaling is applicable. At this point, the process ends.

[0058] 1> Otherwise, if the UE is initiating a CS backoff to establish an RRC connection for mobile:

[0059] 2> If SystemInformationBlockType2 includes ac-BarringForCSFB:

[0060] 3> Use T306 as "Tbarring" and ac-BarringForCSFB as "AC prohibition parameter" to perform the access prohibition check specified in 5.3.3.11;

[0061] 3> If access to the cell is blocked:

[0062] 4> Use the pause indicator to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile-initiated CS fallback is applicable due to ac-BarringForCSFB. At this point, the process ends.

[0063] 2> Otherwise:

[0064] 3> Use T306 as "Tbarring" and ac-BarringForMO-Data as "AC prohibition parameter" to perform the access prohibition check specified in 5.3.3.11;

[0065] 3> If access to the cell is blocked:

[0066] 4> If timer T303 is not running, then start T303 with the timer value of T306;

[0067] 4> Use the pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that due to ac-BarringForMO-Data, access prohibition is applicable for mobile-initiated CS backoff and mobile-initiated calls. At this point, the process ends.

[0068] 1> Otherwise, if the UE is establishing an RRC connection for a mobile-initiated MMTEL voice, mobile-initiated MMTEL video, mobile-initiated SMSoIP, or mobile-initiated SMS:

[0069] 2> If the UE is establishing an RRC connection for MMTEL voice for mobile, and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

[0070] 2> If the UE is initiating an MMTEL video RRC connection for mobile, and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

[0071] 2> If the UE is initiating an SMS SoIP or SMS connection for mobile to establish an RRC connection, and SystemInformationBlockType2 includes ac-BarringSkipForSMS:

[0072] 3> It is believed that access to the community is not prohibited;

[0073] 2> Otherwise:

[0074] 3> If the establishmentCause received from a higher layer is set to mo-Signalling (including cases where mo-Signalling is replaced with highPriorityAccess according to 3GPP TS 24.301

[35] or mo-Signalling is replaced with mo-VoiceCall according to sub-clause 5.3.3.3):

[0075] 4> Use T305 as “Tbarring” and ac-BarringForMO-Signalling as “AC prohibition parameter” to perform the access prohibition check specified in 5.3.3.11;

[0076] 4> If access to the cell is blocked:

[0077] 5> Use a pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile-initiated signaling is applicable. At this point, the process ends.

[0078] 3> If the establishmentCause received from a higher layer is set to mo-Data (including cases where mo-Data is replaced with highPriorityAccess according to 3GPPTS 24.301

[35] or mo-Data is replaced with mo-VoiceCall according to sub-clause 5.3.3.3):

[0079] 4> Use T303 as "Tbarring" and ac-BarringForMO-Data as "AC prohibition parameter" to perform the access prohibition check specified in 5.3.3.11;

[0080] 4> If access to the cell is blocked:

[0081] 5> If SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

[0082] 6> Use the pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for the mobile-initiated call is applicable. At this point, the process ends.

[0083] 5> Otherwise (SystemInformationBlockType2 does not include ac-BarringForCSFB, and the UE supports CS fallback):

[0084] 6> If timer T306 is not running, then start T306 with the timer value of T303;

[0085] 6> Use the pause indication to notify the upper layer that the establishment or restoration of the RRC connection has failed, and notify the upper layer that the access ban for mobile-initiated calls and mobile-initiated CS fallbacks is applicable. At this point, the process ends.

[0086] 1> If the UE is restoring an RRC connection:

[0087] 2> According to 5.3.10.3a, release the MCG SCell (if it is configured);

[0088] 2> Release powerPrefIndicationConfig (if configured) and stop timer T340 (if running);

[0089] 2> Release reportProximityConfig and clear any associated proximity status report timers;

[0090] 2> Release obtainLocationConfig (if it has been configured);

[0091] 2> Release idc-Config (if it has been configured);

[0092] 2> Release measSubframePatternPCell (if configured);

[0093] 2> Release the entire SCG configuration (if configured), except for the DRB configuration (configured by drb-ToAddModListSCG);

[0094] 2> Release naics-Info for PCell (if configured);

[0095] 2> Release the LWA configuration (if it is configured), as described in 5.6.14.3;

[0096] 2> Release the LWIP configuration (if it is configured), as described in 5.6.17.3;

[0097] 2> Release bw-PreferenceIndicationTimer (if configured) and stop timer T341 (if it is running);

[0098] 2> Release delayBudgetReportingConfig (if configured) and stop.

[0099] Timer T342 (if it is running);

[0100] 1> Apply the default physical channel configuration specified in section 9.2.4;

[0101] 1> Apply the default semi-permanent scheduling configuration specified in section 9.2.3;

[0102] 1> Apply the default MAC master configuration specified in section 9.2.2;

[0103] 1> Apply the CCCH configuration specified in section 9.1.1.2;

[0104] 1> Use the timeAlignmentTimerCommon included in SystemInformationBlockType2;

[0105] 1> Start timer T300;

[0106] 1> If the UE is restoring an RRC connection:

[0107] 2> Initiate the transmission of the RRCConnectionResumeRequest message according to 5.3.3.3a;

[0108] 1> Otherwise:

[0109] 2> If already stored, discard the UE AS context and resumeIdentity;

[0110] 2> Initiate the transmission of the RRCConnectionRequest message according to 5.3.3.3;

[0111] Note 2: When initiating the connection establishment process, the UE does not need to ensure that it maintains the latest system information applicable only to UEs in the RRC_IDLE state. However, the UE needs to perform system information acquisition during cell reselection.

[0112] On the other hand, for NB-IoT, when this process is initiated, according to 3GPP TS 36.331, the UE should perform the following actions:

[0113] 1> If the UE is initiating or resuming an abnormal data RRC connection for mobile; or

[0114] 1> If the UE is initiating or resuming an RRC connection for mobile data; or

[0115] 1> If the UE is establishing or resuming an RRC connection for latency-tolerant access; or

[0116] 1> If the UE is initiating signaling to establish or restore an RRC connection for mobile purposes;

[0117] 2> Perform the access prohibition check as specified in 5.3.3.14;

[0118] 2> If access to the cell is blocked:

[0119] 3> Use a pause indicator to notify the upper layer that establishing or restoring an RRC connection has failed, and notify the upper layer that access prohibition is applicable. At this point, the process ends.

[0120] 1> Apply the default physical channel configuration specified in section 9.2.4;

[0121] 1> Apply the default MAC master configuration specified in section 9.2.2;

[0122] 1> Apply the CCCH configuration specified in section 9.1.1.2;

[0123] 1> Start timer T300;

[0124] 1> If the UE is establishing an RRC connection:

[0125] 2> Initiate the transmission of the RRCConnectionRequest message according to 5.3.3.3;

[0126] 1> Otherwise, if the UE is restoring an RRC connection:

[0127] 2> Initiate the transmission of the RRCConnectionResumeRequest message according to 5.3.3.3a;

[0128] Note 3: When initiating a connection establishment or recovery procedure, the UE is not required to ensure that it maintains the latest system information applicable only to UEs in the RRC_IDLE state. However, the UE needs to perform system information acquisition during cell reselection.

[0129] Prior to this, lower-layer signaling is used to allocate C-RNTI. The following excerpt from 3GPP TS 36.321[6] provides additional context. When the UE receives the RRCConnectionSetup message, the UE should:

[0130] 1> If RRCConnectionSetup is received in response to RRCConnectionResumeRequest:

[0131] 2> Discard the stored UE AS context and resumeIdentity;

[0132] 2> Indicate to the upper layer that the RRC connection restoration has been rolled back;

[0133] 1> Based on the received radioResourceConfigDedicated and in accordance with the provisions of 5.3.10, perform the radio resource configuration procedure;

[0134] 1> If already stored, discard cell reselection priority information provided by idleModeMobilityControlInfo or inherited from another RAT;

[0135] 1> If already stored, discard the dedicated offset provided by redirectedCarrierOffsetDedicated;

[0136] 1> Stop timer T300;

[0137] 1> Stop timer T302 (if it is running);

[0138] 1> Stop timer T303 (if it is running);

[0139] 1> Stop timer T305 (if it is running);

[0140] 1> Stop timer T306 (if it is running);

[0141] 1> Stop timer T308 (if it is running);

[0142] 1> Perform the actions specified in 5.3.3.7;

[0143] 1> Stop timer T320 (if it is running);

[0144] 1> Stop timer T350 (if it is running);

[0145] 1> Perform the actions specified in 5.6.12.4;

[0146] 1> Release rclwi-Configuration as specified in 5.6.16.2 (if it is configured);

[0147] 1> Stop timer T360 (if it is running);

[0148] 1> Stop timer T322 (if it is running);

[0149] 1> Enter RRC_CONNECTED;

[0150] 1> Stop the cell reselection process;

[0151] 1> Treat the current cell as a PCell;

[0152] 1> Set the content of the RRCConnectionSetupComplete message as follows:

[0153] 2> If RRCConnectionSetup is received in response to RRCConnectionResumeRequest:

[0154] 3> If the upper layer provides S-TMSI:

[0155] 4> Set s-TMSI to the value received from the upper layer;

[0156] 2> Set selectedPLMN-Identity to the PLMN selected from the PLMNs included in the plmn-IdentityList of SystemInformationBlockType1 (or SystemInformationBlockType1-NB in ​​NB-IoT) in the upper layer (see TS 23.122

[11] , TS 24.301

[35] );

[0157] 2> If the upper layer provides a "registered MME", include and set the registered MME as follows:

[0158] 3> If the PLMN identifier of the "Registered MME" is different from the PLMN selected at the upper level:

[0159] 4> Include plmnIdentity in registeredMME and set it to the value of the PLMN identifier received from the upper layer in the "Registered MME";

[0160] 3> Set mmegi and mmec to the values ​​received from the upper layer;

[0161] 2> If the upper layer provides a "registered MME":

[0162] 3> Include gummei-Type and set gummei-Type to the value provided by the upper layer;

[0163] 2> If the UE supports CIoT EPS optimization:

[0164] 3> Includes attachWithoutPDN-Connectivity (if received from the upper layer);

[0165] 3> Includes up-CIoT-EPS-Optimisation (if received from the upper layer);

[0166] 3> In addition to NB-IoT, this includes cp-CIoT-EPS-Optimisation (if received from the upper layer);

[0167] 2> If used as an RN connection:

[0168] 3> Includes rn-SubframeConfigReq;

[0169] 2> Set dedicatedInfoNAS to include information received from the upper layer;

[0170] 2> Besides NB-IoT:

[0171] 3> If the UE has available radio link failure or handover failure information in the VarRLF-Report, and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report:

[0172] 4> Includes rlf-InfoAvailable;

[0173] 3> If the UE has measurements with MBSFN records available for E-UTRA, and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport:

[0174] 4> Includes logMeasAvailableMBSFN;

[0175] 3> Otherwise, if the UE has recorded measurements available for E-UTRA, and if the RPLMN is included in the plmn-IdentityList stored in the VarLogMeasReport:

[0176] 4> Includes logMeasAvailable;

[0177] 3> If the UE has available connection establishment failure information in VarConnEstFailReport, and if RPLMN equals the plmn-Identity stored in VarConnEstFailReport:

[0178] 4>Include connEstFailInfoAvailable;

[0179] 3> Include mobilityState and set it to the mobility state that the UE was in before entering the RRC_CONNECTED state (as specified in TS 36.304[4]);

[0180] 3> If the UE supports storing mobility history information, and the UE has available mobility history information in VarMobilityHistoryReport:

[0181] 4> Includes MobilityHistoryAvail;

[0182] 2> If a DCN-ID value is received from the upper layer (see TS 23.401

[41] ), then the dcn-ID is included;

[0183] 2> If the UE requires a UL gap during continuous uplink transmission:

[0184] 3> Includes ue-CE-NeedULGaps;

[0185] 2> Submit the RRCConnectionSetupComplete message to the lower layer for transmission; at this point, the process ends.

[0186] Following the scenario described above where C-RNTI is allocated using lower signaling, when the UE receives the RRCConnectionResume message, the UE should:

[0187] 1> Stop timer T300;

[0188] 1> Restore the PDCP state and re-establish PDCP entities for SRB2 and all DRBs;

[0189] 1> If drb-ContinueROHC is included:

[0190] 2> Indicate to the lower layer that the stored UE AS context has been used and drb-ContinueROHC has been configured;

[0191] 2> Continue with the header compression protocol context for DRBs configured with header compression protocols;

[0192] 1> Otherwise:

[0193] 2> Indicate to the lower layer that the stored UE AS context has been used;

[0194] 2> Reset the header compression protocol context for DRBs configured with header compression protocols;

[0195] 1> Discard the stored UE AS context and resumeIdentity;

[0196] 1> Based on the received radioResourceConfigDedicated and in accordance with the provisions of 5.3.10, perform the radio resource configuration procedure;

[0197] 1> If the received RRCConnectionResume message includes sk-Counter:

[0198] 2> Perform the key update procedure specified in TS 38.331 [82, 5.3.5.7];

[0199] 1> If the received RRCConnectionResume message includes nr-RadioBearerConfig:

[0200] 2> Implement the radio bearer configuration specified in TS 38.331 [82, 5.3.5.5];

[0201] 1> If the received RRCConnectionResume message includes nr-RadioBearerConfigS:

[0202] 2> Implement the radio bearer configuration specified in TS 38.331 [82, 5.3.5.5];

[0203] 1> Restore SRB2 and all DRBs;

[0204] 1> If already stored, discard cell reselection priority information provided by idleModeMobilityControlInfo or inherited from another RAT;

[0205] 1> If already stored, discard the dedicated offset provided by redirectedCarrierOffsetDedicated;

[0206] 1> If the RRCConnectionResume message includes measConfig:

[0207] 2> Perform the measurement configuration procedure specified in 5.5.2;

[0208] 1> Stop timer T302 (if it is running);

[0209] 1> Stop timer T303 (if it is running);

[0210] 1> Stop timer T305 (if it is running);

[0211] 1> Stop timer T306 (if it is running);

[0212] 1> Stop timer T308 (if it is running);

[0213] 1> Perform the actions specified in 5.3.3.7;

[0214] 1> Stop timer T320 (if it is running);

[0215] 1> Stop timer T350 (if it is running);

[0216] 1> Perform the actions specified in 5.6.12.4;

[0217] 1> Stop timer T360 (if it is running);

[0218] 1> Stop timer T322 (if it is running);

[0219] 1> As specified in TS 33.401

[32] , the nextHopChainingCount value indicated in the RRCConnectionResume message is used, based on the current K eNB Associated K ASME Key to update K eNB Key;

[0220] 1> Store the nextHopChainingCount value;

[0221] 1> As specified in TS 33.401

[32] , derive K associated with the previously configured integrity algorithm. RRCint Key;

[0222] 1> Use the previously configured algorithm and K RRCint The key is used to request the lower layer to verify the integrity protection of the RRCConnectionResume message;

[0223] 1> If the integrity protection check of the RRCConnectionResume message fails:

[0224] 2> Perform the actions specified in 5.3.12 when leaving RRC_CONNECTED.

[0225] The release reason is "other," and the process ends at this point.

[0226] 1> As specified in TS 33.401

[32] , derive K associated with the previously configured encryption algorithm. RRCenc Key and K UPenc Key;

[0227] 1> Configure the lower layer to use the previously configured algorithm and K. RRCint The key immediately restores integrity protection; that is, integrity protection should be applied to all subsequent messages received and sent by the UE.

[0228] 1> Configure the lower layer to restore encryption and apply the encryption algorithm, K RRCenc Key and K UPenc The key, i.e., the encryption configuration, should be applied to all subsequent messages received and sent by the UE;

[0229] 1> Enter RRC_CONNECTED;

[0230] 1> Indicate to the upper layer that the suspended RRC connection has been restored;

[0231] 1> Stop the cell reselection process;

[0232] 1> Treat the current cell as a PCell;

[0233] 1> Set the content of the RRCConnectionResumeComplete message as follows:

[0234] 2> Set selectedPLMN-Identity to the PLMN selected by the upper layer from the PLMNs included in plmn-IdentityList in SystemInformationBlockType1 (see TS 23.122

[11] , TS 24.301

[35] );

[0235] 2> Set dedicatedInfoNAS to include information received from the upper layer;

[0236] 2> Besides NB-IoT:

[0237] 3> If the UE has available radio link failure or handover failure information in the VarRLF-Report, and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report:

[0238] 4> Includes rlf-InfoAvailable;

[0239] 3> If the UE has measurements with MBSFN records available for E-UTRA, and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport:

[0240] 4> Includes logMeasAvailableMBSFN;

[0241] 3> Otherwise, if the UE has recorded measurements available for E-UTRA, and if the RPLMN is included in the plmn-IdentityList stored in the VarLogMeasReport:

[0242] 4> Includes logMeasAvailable;

[0243] 3> If the UE has available connection establishment failure information in VarConnEstFailReport, and if RPLMN equals the plmn-Identity stored in VarConnEstFailReport:

[0244] 4>Include connEstFailInfoAvailable;

[0245] 3> Include mobilityState and set it to the mobility state that the UE was in before entering the RRC_CONNECTED state (as specified in TS 36.304[4]);

[0246] 3> If the UE supports storing mobility history information, and the UE has available mobility history information in VarMobilityHistoryReport:

[0247] 4> Includes MobilityHistoryAvail;

[0248] 1> Submit the RRCConnectionResumeComplete message to the lower layer for transmission;

[0249] 1> The process is now complete.

[0250] When resuming the process after T300 expires, the UE should:

[0251] 1> If timer T300 expires:

[0252] 2> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0253] 2> If the UE is an NB-IoT UE:

[0254] 3> If SystemInformationBlockType2-NB includes connEstFailOffset:

[0255] 4> When performing cell selection and reselection according to TS 36.304[4], connEstFailOffset is used for the parameter Qoffset for the relevant cell. temp ;

[0256] 3> Otherwise:

[0257] 4> When performing cell selection and reselection according to TS 36.304[4], an infinite value is used for the parameter Qoffset for the relevant cell. temp ;

[0258] Note 0: For NB-IoT, the number of times the UE detects T300 expiration on the same cell before applying connEstFailOffset and the amount of time the UE applies connEstFailOffset before removing the offset from the cell assessment depend on the UE implementation.

[0259] 2> Otherwise, if the UE supports the temporary Qoffset for RRC connection establishment failure, and the T300 has expired consecutively for connEstFailCount times on the same cell including txFailParams in SystemInformationBlockType2:

[0260] 3> During the period indicated by connEstFailOffsetValidity:

[0261] 4> When cell selection and reselection are performed according to TS 36.304[4] and TS 25.304

[40] , connEstFailOffset is used for the parameter Qoffset for the relevant cell. temp ;

[0262] Note 1: When performing cell selection, if no suitable or acceptable cell is found, should the use of connEstFailOffset for the relevant cell be stopped during connEstFailOffsetValidity? temp It depends on the UE implementation.

[0263] 2> In addition to NB-IoT, by setting the VarConnEstFailReport field as follows, the following connection establishment failure information will be stored in VarConnEstFailReport:

[0264] 3> Clear the information included in VarConnEstFailReport (if it exists);

[0265] 3> Set the plmn-Identity to the PLMN selected by the upper layer from the PLMN included in the plmn-IdentityList in SystemInformationBlockType1 (see TS 23.122

[11] , TS 24.301

[35] );

[0266] 3> Set failedCellId to the global cell identifier of the cell where connection establishment failure was detected;

[0267] 3> Configure measResultFailedCell to include the RSRP and RSRQ (if available) of the cell that detected the connection establishment failure, based on the measurements collected until the UE detected the failure;

[0268] 3> If available, set measResultFailedCell (in descending order of sorting criteria used for cell reselection) to include neighboring cell measurements for a maximum of the following numbers of neighboring cells: 6 co-frequency neighbors and 3 inter-frequency neighbors per frequency, and 3 inter-RAT neighbors per frequency / frequency group (GERAN) per RAT, including the neighboring cell measurements as follows:

[0269] 4> For each included neighbor cell, include available optional fields;

[0270] Note 2: UE includes the latest results of available measurements performed in accordance with the performance requirements specified in TS 36.133

[16] , such as those used for cell reselection assessment.

[0271] 3> If detailed location information is available, set the content of locationInfo as follows:

[0272] 4> Includes locationCoordinates;

[0273] 4> Include Horizontal Velocity (if available);

[0274] 3> Set numberOfPreamblesSent to indicate the number of preambles sent by the MAC for a failed random access procedure;

[0275] 3> Set contentionDetected to indicate whether contention resolution was unsuccessful for at least one of the preambles sent for a failed random access procedure, as specified in TS 36.321[6];

[0276] 3> Set maxTxPowerReached to indicate whether the maximum power level is used for the last transmitted preamble, see TS 36.321[6];

[0277] 2> Use a pause indicator to notify the upper layer that establishing or restoring an RRC connection has failed, at which point the process ends.

[0278] 48 hours after a failure is detected, the UE can discard the connection establishment failure information when the power is turned off or the connection is disconnected, that is, release the UE variable VarConnEstFailReport.

[0279] Several challenges exist. In NR, it has been agreed that when an RRC connection is restored (i.e., transitioning from RRC_INACTIVE state to RRC_CONNECTED), the UE should start a timer similar to that used in T300. Whether this timer is the same one used when the UE is performing RRC connection establishment (i.e., transitioning from RRC_IDLE to RRC_CONNECTED) is not yet agreed upon.

[0280] Furthermore, an agreement has been reached on the following aspects regarding the NR RRC, which differs from the LTE RRC.

[0281] First, in NR RRC, the recovery message used to restore the connection, which the network can send in response to a UE attempting to restore the connection, will be encrypted. This differs from the current LTE specification, where the corresponding RRCConnectionResume message is not encrypted.

[0282] Secondly Figure 4 The example RRCSuspend message in the recovery process is shown. In NR RRC, the network can respond to a ResumeRequest from a UE with a pause message, which immediately commands the UE to return to the RRC_INACTIVE state. Furthermore, this message is encrypted. In LTE, it is not possible to directly send a pause message to a UE attempting to resume a connection.

[0283] at last, Figure 5 The example RRC Resume Message is shown in the NR recovery process. In NR RRC, the network can respond to a Resume Request from a UE with a release message, which immediately commands the UE to return to the RRC_IDLE state. Furthermore, this message is encrypted. In LTE, it is not possible to directly send a release message to a UE attempting to resume connection.

[0284] Due to the above differences, the following issues occur when processing timers used for NR RRC recovery.

[0285] First, because the messages received by the UE in response are encrypted in all the above cases, the UE cannot read the messages if it cannot decode them. For this reason, the timer cannot be stopped in this situation. This could happen, for example, if the network and the UE lose synchronization (e.g., the network and the UE do not agree on what state the UE is in).

[0286] Secondly, since the UE can receive more messages in response to the ResumeRequest in NR, it is not enough to stop the timer only when a recovery message is received, as is the case in LTE, because the timer will continue to run if the network does not respond with a recovery message.

[0287] Finally, in both of the above scenarios, the timer will continue to run even if the UE has been released to IDLE, suspended to INACTIVE, or has abandoned the RRC recovery process for receiving messages that may not be decryptable. This, in turn, means that the UE will trigger an action when the timer expires when it is not needed; that is, the action for the timer expiration should only be executed while the UE is still in its state of waiting for a network response. Summary of the Invention

[0288] To address the aforementioned issues in existing solutions, a method and user equipment (UE) are disclosed for avoiding unnecessary actions during connection establishment by using a timer to stop connection establishment at certain events. This disclosure enables the UE to be stopped when the recovery process expires and also prevents the UE from continuing to wait for a response from the network or performing unnecessary actions after the recovery process has expired.

[0289] Several embodiments are described in this disclosure. According to an embodiment of the method, a method for establishing a connection in a user equipment (UE) includes sending a request to a network node to initiate connection establishment. The method further includes: starting a timer for connection establishment when sending the request to the network node, wherein the timer's expiration stops connection establishment for the UE. The method further includes: stopping the timer to stop connection establishment when the UE receives a pause message or a release message, or when the UE performs a cell reselection procedure while the timer is running.

[0290] In one embodiment, connection establishment can be a recovery process, an establishment process, or early data transmission.

[0291] In one embodiment, the method further includes: stopping the timer to stop connection establishment after the UE receives the release message, and then delaying the following actions that the UE should perform after receiving the release message for a period of time. In another embodiment, the method further includes: storing cell information at the UE when the release message includes mobility control information. In yet another embodiment, the method further includes: applying cell information from system information when the release message does not include mobility control information.

[0292] In one embodiment, the method further includes: stopping a timer to halt connection establishment in response to the UE receiving a pause message, delaying subsequent actions that the UE should perform after receiving the pause message for a period of time, instructing the upper layer to pause the connection establishment, and configuring the lower layer to pause integrity protection. In one embodiment, the period of time is 60ms.

[0293] In one embodiment, the method further includes: while the timer is running and the UE is performing cell reselection, after stopping the timer to stop connection establishment, resetting the MAC, releasing the MAC configuration, and notifying the upper layer that the connection establishment failed.

[0294] According to an embodiment of the UE, the UE for connection establishment includes at least one processing circuit and at least one memory storing processor-executable instructions. When executed by the processing circuit, the processor-executable instructions cause the user equipment to send a request to a network node to initiate connection establishment. When sending the request to the network node, a timer for establishing the connection is started, wherein the connection establishment stops upon expiration of the timer, and the timer is stopped upon receiving a pause message or a release message to stop connection establishment. In one embodiment, the UE can stop the timer to stop connection establishment while the timer is running and a cell reselection process is being performed.

[0295] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Various embodiments are presented herein to address one or more problems disclosed herein.

[0296] Some embodiments may provide one or more of the following technical advantages. The methods disclosed in this disclosure can provide a security mechanism that stops the UE when the connection establishment expires by using a timer. The method can configure the timer to stop the UE while the UE is performing some action while the timer is running. The method can also configure the timer to stop the UE when the UE receives a return message from a network node. Thus, the method can prevent the UE from generating additional signaling in the network when it is not needed.

[0297] Specific embodiments provide a comprehensive timer that can be used for connection establishment in both LTE and NR. In specific embodiments, this timer can stop the UE for certain events to avoid unnecessary actions that should not be performed during the expiring connection establishment. Specific embodiments also conserve UE battery and improve resource efficiency in the network by stopping the UE during connection establishment at appropriate times. Specific embodiments include a method to prevent erroneous messages from occurring when the UE is trapped in an infinite loop waiting for a response from the network.

[0298] Various other features and advantages will become apparent to those skilled in the art from the following detailed description and accompanying drawings. Some embodiments may lack the described advantages, or have some or all of them. Attached Figure Description

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

[0300] Figure 1 An example state transition of user equipment in the new radio (NR) is shown;

[0301] Figure 2 An example recovery process failure caused by poor downlink radio conditions is shown;

[0302] Figure 3 An example recovery process failure caused by poor uplink radio conditions is shown;

[0303] Figure 4 This illustrates an example RRC connection recovery process when the network responds with a release message;

[0304] Figure 5 This illustrates an example RRC connection recovery process when the network responds with a pause message;

[0305] Figure 6 An example wireless network according to certain embodiments is shown;

[0306] Figure 7 An example user device according to certain embodiments is shown;

[0307] Figure 8 An example virtualization environment according to certain embodiments is shown;

[0308] Figure 9 An example telecommunications network is shown that is connected to a host computer via an intermediate network according to certain embodiments;

[0309] Figure 10 An example host computer is shown that communicates with a user equipment via a base station through a partial wireless connection according to certain embodiments;

[0310] Figure 11 Example methods implemented in a communication system including a host computer, a base station, and a user equipment, according to certain embodiments, are shown.

[0311] Figure 12 Another example method implemented in a communication system including a host computer, a base station, and a user equipment, according to certain embodiments, is shown;

[0312] Figure 13 This illustrates yet another example method implemented in a communication system including a host computer, a base station, and a user equipment, according to certain embodiments;

[0313] Figure 14 This illustrates yet another example method implemented in a communication system including a host computer, a base station, and a user equipment, according to certain embodiments;

[0314] Figure 15 A flowchart of a method in a user equipment according to certain embodiments is shown;

[0315] Figure 16 A block diagram of an exemplary user device according to certain embodiments is shown. Detailed Implementation

[0316] Traditional timers may not be suitable for certain unfavorable downlink / uplink transmissions in LTE or most events in NR. In such cases, the traditional timer will continue to run even if the UE may have changed to another state. Therefore, specific embodiments of this disclosure propose a method that provides a failure timer to stop the recovery process when the UE receives a message from the network, when the UE performs certain actions while the timer is running, or when the timer is about to expire. The failure timer of this disclosure is introduced to prevent the UE from performing unnecessary processes when the failure timer expires.

[0317] By utilizing a failure timer during the recovery process, the UE can be stopped when it receives a valid message from the network, such as an establishment message, rejection message, release message, or pause message. This allows the UE to stop waiting for the recovery process and change to the corresponding state based on the received message without generating further signaling. In certain embodiments, the failure timer can also stop the UE if it is performing certain actions while the failure timer is running (e.g., detection of integrity check failure from the lower layer, cell reselection, or connection establishment abort). This solution also enables the failure timer to stop the recovery process for a limited time period, thus preventing the UE from waiting for a response from the network when the network is suffering from poor downlink / uplink transmission.

[0318] This document presents various embodiments that address one or more of the problems disclosed herein. Some embodiments may provide one or more of the following technical advantages. For example, by using a timer triggered by the above-described scenario, it is beneficial to avoid the UE performing unnecessary processes when the timer expires, which would generate more signaling in the network, consume more UE battery, and cause unnecessary interference. Some embodiments may not provide these advantages, or may provide some or all of these advantages, and other technical advantages will be apparent to those skilled in the art.

[0319] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0320] Generally, unless a different meaning is explicitly given and / or implied from the context of the use of the term, all terms used herein shall be interpreted according to their ordinary meaning in the relevant art. Unless otherwise expressly stated, all references to “an element, device, component, apparatus, step, etc.” shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or it is implied that a step must occur after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Further objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0321] In some embodiments, the term "UE" is used without limitation. A UE as used herein can be any type of wireless device capable of communicating with a network node or another UE via radio signals. A UE can also be a radio communication device, a target device, a device-to-device (D2D) UE, a machine-type UE, or a UE capable of machine-to-machine (M2M) communication, a sensor equipped with a UE, an iPad, a tablet computer, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter, or a client terminal equipment (CPE), etc.

[0322] Furthermore, in some embodiments, the generic term "network node" is used. It can be any type of network node, including radio network nodes such as base stations, radio base stations, base transceivers, base station controllers, network controllers, multi-standard radio BSs, gNBs, NR BSs, evolved Node Bs (eNBs), Node Bs, multi-cell / multicast coordination entities (MCEs), relay nodes, access points, radio access points, remote radio units (RRUs), remote radio heads (RRHs), multi-standard BSs (also known as MSR BSs), core network nodes (e.g., MMEs, SON nodes, coordination nodes, location nodes, MDT nodes, etc.), or even external nodes (e.g., third-party nodes, external nodes of the current network). The network node may also include test equipment.

[0323] The term "signaling" as used herein can include any of the following: higher-level signaling (e.g., via Radio Resource Control (RRC), etc.), lower-level signaling (e.g., via physical control channels or broadcast channels), or a combination thereof. Signaling can be implicit or explicit. Signaling can also be unicast, multicast, or broadcast. Signaling can also be directed directly to another node or via a third node to another node.

[0324] Specific embodiments are based on the introduction of a new mechanism for stopping a failed timer T. In addition to the existing practice of stopping timer T in LTE, the timer is also stopped in the following events: when the UE performs a recovery procedure, i.e., when the UE has sent a ResumeRequest message; for example, when the UE receives a pause message; when the UE receives a release message; and when the UE detects an integrity protection verification error in a lower layer (e.g., the PDCP layer) while timer T is running.

[0325] Furthermore, if a failure timer T, independent of the timer T300 used for RRC connection re-establishment, is introduced, timer T can also be stopped during the UE's recovery process in the following events: for example, when the UE receives an RRCConnectionSetup message, when the UE receives an RRCReject message, and when the UE performs cell reselection while timer T is running. The events listed above are not exhaustive, and it should be understood that other situations may occur that could stop timer T.

[0326] Specific embodiments of this disclosure are implemented in the 38.331NR RRC specification. According to a first embodiment of the method, the recovery process is triggered when an RRCResumeRequest or RRCRequest is sent and a single timer T300 is defined during the recovery process. When the UE receives the RRCSuspend message, for example, as specified in 5.3.14.3, the UE can:

[0327] 1> From the moment the RRCSuspend message is received, or optionally, when the lower layer indicates that the reception of the RRCSuspend message has been successfully confirmed (whichever is earlier), the subsequent actions defined in this sub-clause shall be delayed by X ms.

[0328] 1> If the RRCSuspend message includes idleModeMobilityControlInfo:

[0329] 2> Stores cell reselection priority information provided by idleModeMobilityControlInfo;

[0330] 2> If t320 is included:

[0331] 3> Start timer T320 and set the timer value according to the value of t320;

[0332] 1> Otherwise:

[0333] 2> Cell reselection priority information broadcast in the application system information;

[0334] 1> Store the following information provided by the network: resumeIdentity, nextHopChainingCount, ran-PagingCycle, and ran-NotificationAreaInfo;

[0335] 1> Rebuild RLC entities for all SRBs and DRBs;

[0336] 1> Unless an RRCSuspend message is received in response to an RRCResumeRequest:

[0337] 2> Store the UE AS context (including the current RRC configuration, the current security context, the PDCP status including the ROHC status, the C-RNTI used in the source PCell, the cellIdentity of the source PCell, and the physical cell identifier);

[0338] 1> Suspend all SRBs and DRBs except SRB0;

[0339] 1> Start timer T380 and set the timer value to periodic-RNA U-timer;

[0340] 1> Indicate to the upper layer that the RRC connection is paused;

[0341] 1> Configure the lower layer to pause integrity protection and encryption;

[0342] 1> Enter RRC_INACTIVE and execute the procedure specified in TS 38.304

[21] .

[0343] In some embodiments, the value of X can be configurable. In some embodiments, in LTE, the value of X can be 60ms. In some embodiments, the above configuration of the UE can be applied to the setup process or to early data transmission for establishing a connection.

[0344] When the UE receives the RRCRelease message, for example, as specified in 5.3.8.3, the UE can:

[0345] 1> Discard any stored UE AS context and I-RNTI;

[0346] 1> Stop timer T300 (if it is running);

[0347] 1> From the moment the RRCRelease message is received, or optionally, when the lower layer indicates that the reception of the RRCRelease message has been successfully confirmed (whichever is earlier), the subsequent actions defined in this sub-clause shall be delayed by X ms.

[0348] 1> If the RRCRelease message includes idleModeMobilityControlInfo:

[0349] 2> Stores cell reselection priority information provided by idleModeMobilityControlInfo;

[0350] 2> If t320 is included:

[0351] 3> Start timer T320 and set the timer value according to the value of t320;

[0352] 1> Otherwise:

[0353] 2> Cell reselection priority information broadcast in the application system information;

[0354] 1> When entering RRC_IDLE, perform the actions specified in 5.3.11.

[0355] In some embodiments, the value of X can be configurable. In some embodiments, in LTE, the value of X can be 60ms. In some embodiments, the RRCRelease procedure can support a mechanism equivalent to loadBalancingTA URequired. In some embodiments, the RRCRelease procedure can be triggered by different release reasons and can be associated with different actions.

[0356] When a recovery procedure is triggered when T300 expires or when an integrity check from a lower layer fails while T300 is running (e.g., as specified in 5.3.13.5 when T300 expires or when an integrity check from a lower layer fails while T300 is running), the UE may:

[0357] 1> If timer T300 expires or an integrity check from the lower layer fails while T300 is running:

[0358] 2> Stop timer T300 (if it is running);

[0359] 2> Discard the stored UE AS context and resumeIdentity;

[0360] 2> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs:

[0361] 2> The upper layer is notified that the RRC connection restoration failed, and the process ends at this point.

[0362] In some embodiments, T319 may be the same as T300. In some embodiments, the above configuration of the UE may be applied to the setup process or to early data transmission for establishing a connection.

[0363] Table 1 below shows timers T300 and T302 of this disclosure implemented in the recovery process as specified in 7.1.1 according to certain embodiments.

[0364] Table 1

[0365]

[0366] According to a second embodiment of the method, such as in 5.2.2, T300 is triggered during the recovery process when an RRCRequest is sent, and T319 is triggered when an RRCConnectionResumeRequest is sent. In the second embodiment, an additional step may be to select whether to initiate T300 or T319. Furthermore, even in LTE, the UE is able to receive RRCReject or RRCSetup in response to an RRCConnectionResumeRequest or RRCConnectionRequest. Apart from being a completely new process for NR, defining the two timers T300 and T319 in each embodiment of this disclosure requires possible changes. Therefore, the specific embodiments shown in this disclosure include certain parts equivalent to 5.2.1, which are entirely new due to the new NR process. In some embodiments, T300 or T319 may be applied to early data transmission to establish a connection.

[0367] When the UE receives the RRCSuspend message, for example, when the UE receives the RRCSuspend message as specified in 5.3.14.3, the UE can:

[0368] 1> From the moment the RRCSuspend message is received, or optionally, when the lower layer indicates that the reception of the RRCSuspend message has been successfully confirmed (whichever is earlier), the subsequent actions defined in this sub-clause shall be delayed by X ms;

[0369] 1> Stop timer T300 or T319 (if it is running);

[0370] 1> If the RRCSuspend message includes idleModeMobilityControlIn; fo:

[0371] 2> Stores cell reselection priority information provided by idleModeMobilityControlInfo;

[0372] 2> If t320 is included:

[0373] 3> Start timer T320 and set the timer value according to the value of t320;

[0374] 1> Otherwise:

[0375] 2> Cell reselection priority information broadcast in the application system information;

[0376] 1> Store the following information provided by the network: resumeIdentity, nextHopChainingCount, ran-PagingCycle, and ran-NotificationAreaInfo;

[0377] 1> Rebuild RLC entities for all SRBs and DRBs;

[0378] 1> Unless an RRCSuspend message is received in response to an RRCResumeRequest:

[0379] 2> Store the UE AS context (including the current RRC configuration, the current security context, the PDCP status including the ROHC status, the C-RNTI used in the source PCell, the cellIdentity of the source PCell, and the physical cell identifier);

[0380] 1> Suspend all SRBs and DRBs except SRB0;

[0381] 1> Start timer T380 and set the timer value to periodic-RNAU-timer;

[0382] 1> Indicate to the upper layer that the RRC connection is paused;

[0383] 1> Configure the lower layer to pause integrity protection and encryption;

[0384] 1> Enter RRC_INACTIVE and execute the procedure specified in TS 38.304

[21] .

[0385] In some embodiments, the value of X can be configurable. In some embodiments, in LTE, the value of X can be 60ms.

[0386] When the UE receives the RRCRelease message, for example, as specified in 5.3.8.3, the UE can:

[0387] 1> Discard any stored UE AS context and I-RNTI;

[0388] 1> Stop timer T300 or T319 (if it is running);

[0389] 1> From the moment the RRCRelease message is received, or optionally, when the lower layer indicates that the reception of the RRCRelease message has been successfully confirmed (whichever is earlier), the subsequent actions defined in this sub-clause shall be delayed by X ms;

[0390] 1> If the RRCRelease message includes idleModeMobilityControlInfo:

[0391] 2> Stores cell reselection priority information provided by idleModeMobilityControlInfo;

[0392] 2> If t320 is included:

[0393] 3> Start timer T320 and set the timer value according to the value of t320;

[0394] 1> Otherwise:

[0395] 2> Cell reselection priority information broadcast in the application system information;

[0396] 1> When entering RRC_IDLE, perform the actions specified in 5.3.11.

[0397] In some embodiments, the value of X can be configurable. In some embodiments, in LTE, the value of X can be 60ms. In some embodiments, the RRCRelease procedure can support a mechanism equivalent to loadBalancingTA URequired. In some embodiments, the RRCRelease procedure can be triggered by different release reasons and can be associated with different actions.

[0398] According to a third embodiment of the method, a specific embodiment illustrates an implementation of the NR equivalent to the existing LTE response, but taking into account the possibility of defining two different timers T300 and T319. When the UE receives the RRCSetup message, for example, as specified in 5.3.3.4, the UE can:

[0399] 1> If RRCSetup is received in response to RRCResumeRequest:

[0400] 2> Discard the stored UE AS context and I-RNTI;

[0401] 2> Indicate to the upper layer that the RRC connection restoration has been rolled back;

[0402] 1> Based on the received masterCellGroup and in accordance with the provisions of 5.3.5.5, perform the cell group configuration process;

[0403] 1> Based on the received radioBearerConfig and in accordance with the provisions of 5.3.5.6, perform the radio bearer configuration process;

[0404] 1> If already stored, discard cell reselection priority information provided by idleModeMobilityControlInfo or inherited from another RAT;

[0405] 1> Stop timer T300 or T319 (if it is running);

[0406] 1> Stop timer T320 (if it is running);

[0407] 1> Enter RRC_CONNECTED;

[0408] 1> Stop the cell reselection process;

[0409] 1> Treat the current cell as a PCell;

[0410] 1> Set the content of the RRCSetupComplete message as follows:

[0411] 2> If RRCConnectionSetup is received in response to RRCResumeRequest:

[0412] 3> If the upper layer provides 5G-S-TMSI:

[0413] 4> Set ng-5G-S-TMSI to the value received from the upper layer;

[0414] 2> Set selectedPLMN-Identity to the PLMN selected from the PLMNs included in plmn-IdentityList in SystemInformationBlockType1 (TS 24.501

[23] );

[0415] 2> If the upper layer provides a "registered AMF":

[0416] 3> Include and set the registeredAMF as follows:

[0417] 4> If the PLMN identifier of the "Registered AMF" is different from the PLMN selected by the upper layer:

[0418] 5> Include plmnIdentity in registeredAMF and set it to the value of the PLMN identifier received from the upper layer in the "Registered AMF";

[0419] 4> Set amf-Region, αmf-SetId, and αmf-Pointer to the values ​​received from the upper layer;

[0420] 3> Include guami-Type and set guami-Type to the value provided by the upper layer;

[0421] 2> If the upper layer provides one or more S-NSSAI (see TS 23.003

[20] ):

[0422] 3> Include s-nssai-list and set its contents to the values ​​provided by the upper layer;

[0423] 2> Set dedicatedInfoNAS to include information received from the upper layer;

[0424] 2> Submit the RRCSetupComplete message to the lower layer for transmission, at which point the process ends.

[0425] In some embodiments, idleModeMobilityControlInfo can also be applied to a UE entering RRC_INACTIVE. In this case, the name of the information element (IE) can be changed. In some embodiments, UE actions related to the access control timer can be defined. The access control timer can be equivalent to T302, T303, T305, T306, and T308 in LTE. For example, if a given timer is not running, the upper layer is notified. In some embodiments, guami-Type can also be determined to be included and set in the above conditions.

[0426] When T300 or T319 expires, for example as specified in 5.3.3.6, the UE may:

[0427] 1> If timer T300 or T300X expires:

[0428] 2> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0429] 2> Notify the upper layer that the RRC connection establishment failed, at which point the process ends.

[0430] When the UE receives an RRCReject message, for example, as specified in 5.3.15, the UE can:

[0431] 1> Stop timer T300 or T300X;

[0432] 1> Reset the MAC address and release the MAC configuration;

[0433] 1> Start timer T302 and set the timer value to waitTime;

[0434] 1> Notify the upper layer of the failure to establish an RRC connection and related access control information. At this point, the process ends.

[0435] In some embodiments, RRCReject may include redirection information and / or frequency / RAT repricing information. In some embodiments, certain access control-related information may be notified to higher layers.

[0436] When T319 is about to expire or when the UE receives an integrity check failure from the lower layer while T319 is running, for example as specified in 5.3.13.5, the UE can:

[0437] 1> If T300X expires or an integrity check from the lower layer fails while timer T300X is running:

[0438] 2> Stop timer T300X (if it is running);

[0439] 2> Discard the stored UE AS context and resumeIdentity;

[0440] 2> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0441] 2> The upper layer is notified that the RRC connection restoration failed, and the process ends at this point.

[0442] In some embodiments, T319 may be the same as T300.

[0443] When a UE performs cell reselection while T300 is running, for example during the recovery process specified in 5.3.3.5, the UE may:

[0444] 1> If cell reselection occurs while T300 is running:

[0445] 2> If timer T300 is running:

[0446] 3> Stop timer T300;

[0447] 3> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0448] 3> Notify the upper layer that establishing or restoring an RRC connection has failed.

[0449] In some embodiments, cell reselection actions may need to be defined for other timers (e.g., access control timers equivalent to T302, T303, T305, T306, and T308 in LTE). In some embodiments, the above configuration of the UE can be applied to the setup process or to early data transmission for establishing a connection.

[0450] When a UE performs cell reselection while T300 or T319 is running, for example during the recovery process specified in 5.3.3.5, the UE may:

[0451] 1> If cell reselection occurs while T300 or T300X is running:

[0452] 2> If timer T300 is running:

[0453] 3> Stop timer T300;

[0454] 3> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0455] 3> Notify the upper layer that establishing or restoring an RRC connection failed;

[0456] 2> Otherwise, if timer T300X is running:

[0457] 3> Stop timer T300X;

[0458] 3> Reset the MAC, release the MAC configuration, and re-establish the RLC for all existing RBs;

[0459] 3> Notify the upper layer that establishing or restoring an RRC connection has failed.

[0460] In some embodiments, cell reselection actions may need to be defined for other timers (e.g., access control timers equivalent to T302, T303, T305, T306, and T308 in LTE). In some embodiments, the above configuration of the UE can be applied to the setup process or to early data transmission for establishing a connection.

[0461] Table 2 below shows timers T300, T319, and T302 of this disclosure implemented in the recovery process specified in 7.1.1 according to certain embodiments.

[0462] Table 2

[0463]

[0464] Figure 6 According to certain embodiments, these are example wireless networks according to certain embodiments. While the subject matter described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein pertain to wireless networks (e.g., Figure 6 The example wireless network shown is described below. For simplicity, Figure 6 The wireless network depicted only includes network 606, network nodes 660 and 660b, and WD 610, 610b, and 610c. In practice, the wireless network may also include any additional elements adapted to support communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the illustrated components, network node 660 and wireless device (WD) 610 are depicted in additional detail. In some embodiments, network node 660 may be... Figure 9 The base station is further depicted in the diagram. In some embodiments, the wireless device 610 may be in... Figure 7 , 9 User equipment further illustrated in sections -14 and -16. Wireless device 610 can perform actions regarding... Figure 15 The method described. A wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0465] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems, and / or interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Therefore, specific embodiments of a wireless communication network can implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, and / or ZigBee standards.

[0466] Network 606 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

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

[0468] As used herein, a network node refers to a device that is capable of, configured, positioned, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, NodeBs, and evolved NodeBs (eNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, based on their transmit power levels), and thus they may also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay host node that controls a relay. A network node may also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes referred to as a remote radio headend (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A portion of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), network controllers (such as a radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network for wireless devices, or to provide some service to wireless devices already connected to the wireless network.

[0469] exist Figure 6 In this network node 660, processing circuitry 670, device-readable medium 680, interface 690, auxiliary equipment 684, power supply 686, power supply circuitry 687, and antenna 662 are included. Although Figure 6The network node 660 shown in the example wireless network can represent a device including a combination of the illustrated hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of network node 660 are depicted as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 680 may include multiple separate hard disk drives and multiple RAM modules).

[0470] Similarly, network node 660 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own respective components. In some scenarios where network node 660 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node 660 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 680 for different RATs), and some components may be reused (e.g., the same antenna 662 may be shared by the RATs). Network node 660 may also include multiple sets of various illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 660. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 660.

[0471] Processing circuitry 670 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by processing circuitry 670 may include processing information acquired by processing circuitry 670 by: for example, converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0472] Processing circuitry 670 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide network node 660 functionality, either alone or in combination with other network node 660 components (e.g., device-readable medium 680). For example, processing circuitry 670 may execute instructions stored in device-readable medium 680 or in memory within processing circuitry 670. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 670 may include a system-on-a-chip (SoC).

[0473] In some embodiments, the processing circuitry 670 may include one or more of a radio frequency (RF) transceiver circuitry 672 and a baseband processing circuitry 674. In some embodiments, the RF transceiver circuitry 672 and the baseband processing circuitry 674 may be located on separate chipsets, boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 672 and the baseband processing circuitry 674 may be located on the same chip or chipset, board, or unit group.

[0474] In some 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 processing circuitry 670, which executes instructions stored on device-readable medium 680 or memory within processing circuitry 670. In alternative embodiments, some or all of the functions may be provided by processing circuitry 670, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 670 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 670 or other components of network node 660, but are enjoyed as a whole by network node 660 and / or generally by end users and the wireless network.

[0475] Device-readable medium 680 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry 670. Device-readable medium 680 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 executable by processing circuitry 670 and usable by network node 660. Device-readable medium 680 may be used to store any calculations performed by processing circuitry 670 and / or any data received via interface 690. In some embodiments, processing circuitry 670 and device-readable medium 680 may be considered integrated.

[0476] Interface 690 is used for wired or wireless communication of signaling and / or data between network node 660, network 606, and / or WD 610. As shown, interface 690 includes a port / terminal 694 for sending and receiving data to and from network 606, for example, via a wired connection. Interface 690 also includes radio front-end circuitry 692, which may be coupled to antenna 662, or in some embodiments, is part of antenna 662. Radio front-end circuitry 692 includes a filter 698 and an amplifier 696. Radio front-end circuitry 692 may be connected to antenna 662 and processing circuitry 670. Radio front-end circuitry 692 may be configured to modulate the signal used for communication between antenna 662 and processing circuitry 670. Radio front-end circuitry 692 may receive digital data that will be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 692 may use a combination of filter 698 and / or amplifier 696 to convert the digital data into a radio signal with suitable channel and bandwidth parameters. The radio signal can then be transmitted via antenna 662. Similarly, when receiving data, antenna 662 can collect radio signals, which are then converted into digital data by radio front-end circuitry 692. The digital data can then be passed to processing circuitry 670. In other embodiments, the interface may include different components and / or different combinations of components.

[0477] In some alternative embodiments, network node 660 may not include a separate radio front-end circuitry 692. Instead, processing circuitry 670 may include radio front-end circuitry and may be connected to antenna 662 without requiring a separate radio front-end circuitry 692. Similarly, in some embodiments, all or some of RF transceiver circuitry 672 may be considered part of interface 690. In other embodiments, interface 690 may include one or more ports or terminals 694, radio front-end circuitry 692, and RF transceiver circuitry 672 (as part of a radio unit (not shown),) and interface 690 may communicate with baseband processing circuitry 674 (which is part of a digital unit (not shown)).

[0478] Antenna 662 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 662 may be coupled to radio front-end circuitry 690 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 662 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals to / from devices within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 662 may be detachable from network node 660 and may be connected to network node 660 via an interface or port.

[0479] Antenna 662, interface 690, and / or processing circuitry 670 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 662, interface 690, and / or processing circuitry 670 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0480] Power supply circuit 687 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 660 to perform the functions described herein. Power supply circuit 687 may receive power from power source 686. Power source 686 and / or power supply circuit 687 may be configured to provide power to various components of network node 660 in a manner suitable for the individual components (e.g., at the voltage and current levels required by each respective component). Power source 686 may be included in or outside power supply circuit 687 and / or network node 660. For example, network node 660 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a cable, thereby supplying power to power supply circuit 687. As another example, power source 686 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 687. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0481] Alternative embodiments of network node 660 may include more than Figure 6 Additional components of the components shown may be responsible for providing certain aspects of the functionality of the network node (including any of the functions described herein and / or any functionality required to support the subject matter described herein). For example, network node 660 may include a user interface device to allow information to be input into and output from network node 660. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 660.

[0482] As used herein, a wireless device (WD) means a device capable of, configured to, arranged to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD may be used interchangeably with user equipment (UE) herein. In some embodiments, wireless device 810 may be in… Figure 7 and 9User equipment further described in -16. Wireless transmission may include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, the WD may be configured to send and / or receive information without direct human interaction. For example, the WD may be designed to send information to the network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, 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, portable computers, portable embedded devices (LEEs), portable installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), in-vehicle wireless terminal equipment, etc. The WD may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, and in this case may be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, a 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, the WD can be a machine-to-machine (M2M) device, and in the 3GPP context, it can be referred to as a machine-type communication (MTC) device. As a specific example, a WD can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machines, or household or personal devices (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As described above, a WD can represent a wirelessly connected endpoint, in which case the device can be referred to as a wireless terminal. Furthermore, as described above, a WD can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0483] As shown in the figure, the wireless device 610 includes an antenna 611, an interface 614, processing circuitry 620, a device-readable medium 630, a user interface device 632, auxiliary devices 634, a power supply 636, and a power supply circuit 637. WD 610 may include one or more of the components shown for various wireless technologies supported by WD 610 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within WD 610.

[0484] Antenna 611 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 614. In some alternative embodiments, antenna 611 may be separate from WD 610 and may be connected to WD 610 via an interface or port. Antenna 611, interface 614, and / or processing circuitry 620 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 611 may be considered as an interface.

[0485] As shown, interface 614 includes radio front-end circuitry 612 and antenna 611. Radio front-end circuitry 612 includes one or more filters 618 and amplifiers 616. Radio front-end circuitry 614 is connected to antenna 611 and processing circuitry 620 and is configured to modulate the signal transmitted between antenna 611 and processing circuitry 620. Radio front-end circuitry 612 may be coupled to antenna 611 or be part of antenna 611. In some alternative embodiments, WD 610 may not include a separate radio front-end circuitry 612; instead, processing circuitry 620 may include radio front-end circuitry and may be connected to antenna 611. Similarly, in some embodiments, some or all of RF transceiver circuitry 622 may be considered part of interface 614. Radio front-end circuitry 612 can receive digital data that will be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 612 can use a combination of filters 618 and / or amplifiers 616 to convert digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 611. Similarly, when receiving data, antenna 611 can collect radio signals, which are then converted into digital data by radio front-end circuitry 612. The digital data can then be passed to processing circuitry 620. In other embodiments, the interface may include different components and / or different combinations of components.

[0486] Processing circuitry 620 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide WD 610 functionality, either alone or in combination with other WD 610 components (e.g., device-readable medium 630). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 620 may execute instructions stored in device-readable medium 630 or in memory within processing circuitry 620 to provide the functionality disclosed herein.

[0487] As shown in the figure, the processing circuit 620 includes one or more of an RF transceiver circuit 622, a baseband processing circuit 624, and an application processing circuit 626. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 620 of the WD 610 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 622, the baseband processing circuit 624, and the application processing circuit 626 may be on a separate chip or chipset. In alternative embodiments, a portion or all of the baseband processing circuit 624 and the application processing circuit 626 may be combined into a single chip or chipset, and the RF transceiver circuit 622 may be on a separate chip or chipset. In further alternative embodiments, a portion or all of the RF transceiver circuit 622 and the baseband processing circuit 624 may be on the same chip or chipset, and the application processing circuit 626 may be on a separate chip or chipset. In other alternative embodiments, a portion or all of the RF transceiver circuit 622, the baseband processing circuit 624, and the application processing circuit 626 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 622 may be part of the interface 614. The RF transceiver circuit 622 may modulate the RF signal for use by the processing circuit 620.

[0488] In some embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuitry 620, which executes instructions stored on device-readable medium 630, which in some embodiments may be computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 620, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of these particular embodiments, processing circuitry 620 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 620 or other components of WD 610, but are enjoyed as a whole by WD 610 and / or generally by end users and wireless networks.

[0489] Processing circuitry 620 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. These operations performed by processing circuitry 620 may include processing information acquired by processing circuitry 620 by, for example, converting the acquired information into other information, comparing the acquired or converted information with information stored by WD 610, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0490] Device-readable medium 630 is operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 620. Device-readable medium 630 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device storing information, data, and / or instructions usable by processing circuitry 620. In some embodiments, processing circuitry 620 and device-readable medium 630 may be considered integrated.

[0491] User interface device 632 can provide components that allow a human user to interact with WD 610. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 632 is operable to produce output to the user and allow the user to provide input to WD 610. The type of interaction can vary depending on the type of user interface device 632 installed in WD 610. For example, if WD 610 is a smartphone, interaction can be via a touchscreen; if WD 610 is a smart meter, interaction can be via a screen providing usage (e.g., the number of gallons used) or a speaker providing audible alarms (e.g., if smoke is detected). User interface device 632 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 632 is configured to allow information to be input into WD 610 and is connected to processing circuitry 620 to allow processing circuitry 620 to process the input information. User interface device 632 can include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 632 is also configured to allow information output from WD 610 and to allow processing circuitry 620 to output information from WD 610. User interface device 632 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of user interface device 632, WD 610 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0492] The auxiliary device 634 is operable to provide more specific functions that may not typically be performed by the WD. This may include dedicated sensors for measurements for various purposes, interfaces for other types of communication such as wired communication, etc. The components included and the types of the auxiliary device 634 may vary depending on the embodiment and / or scenario.

[0493] In some embodiments, power supply 636 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. WD 610 may also include power circuitry 637 for supplying power from power supply 636 to various parts of WD 610 that require power from power supply 636 to perform any function described or indicated herein. In some embodiments, power circuitry 637 may include power management circuitry. Power circuitry 637 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 610 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry 637 may also be operable to supply power from an external power source to power supply 636. For example, this may be used for charging power supply 636. Power circuitry 637 may perform any formatting, conversion, or other modifications on the power from power supply 636 to suit the power supply for the various components of the powered WD 610.

[0494] Figure 7 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, "User Equipment" or "UE" may not necessarily have the meaning of a "user" in the sense of a human user who owns and / or operates the associated equipment. Alternatively, a UE may refer to a device intended for sale to or operated by a human user but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may also include any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs not intended for sale to or operated by human users. Figure 7 As shown, UE 700 is an example of a WD configured for communication according to one or more communication standards (e.g., 3GPP's GSM, UMTS, LTE, and / or 5G standards) published by the 3rd Generation Partnership Project (3GPP). In some embodiments, user equipment 700 may be in Figure 16 The user equipment is further described below. As mentioned earlier, the terms WD and UE are used interchangeably. Therefore, although Figure 7 This is for UE, but the components discussed in this article also apply to WD, and vice versa.

[0495] exist Figure 7In this embodiment, UE 700 includes processing circuitry 701 operatively coupled to an input / output interface 705, a radio frequency (RF) interface 709, a network connectivity interface 711, a memory 715 including random access memory (RAM) 717, read-only memory (ROM) 719, and a storage medium 721, a communication subsystem 731, a power supply 733, and / or any other component, or any combination thereof. The storage medium 721 includes an operating system 723, application programs 725, and data 727. In other embodiments, the storage medium 721 may include other similar types of information. Some UEs may use... Figure 7 This refers to all components shown, or only a subset of those components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0497] In the depicted embodiments, the input / output interface 705 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 700 can be configured to use an output device via the input / output interface 705. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 700. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 700 can be configured to use an input device via the input / output interface 705 to allow a user to capture information into the UE 700. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a touchpad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, other similar sensors, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0498] exist Figure 7 In this configuration, RF interface 709 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 711 can be configured to provide a communication interface to network 743a. Network 743a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 743a may include a Wi-Fi network. Network connectivity interface 711 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network connectivity interface 711 can implement receiver and transmitter functions suitable for the communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0499] RAM 717 can be configured to interface with processing circuitry 701 via bus 702 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 719 can be configured to provide computer instructions or data to processing circuitry 701. For example, ROM 719 can be configured to store invariant low-level system code or data for basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard. Storage medium 721 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable magnetic tape cassette, or flash drive. In one example, storage medium 721 can be configured to include operating system 723, application 725 such as a web browser application, widget or utility engine or another application, and data file 727. Storage medium 721 can store any one or a combination of various operating systems for use by UE 700.

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

[0501] exist Figure 7In this embodiment, processing circuitry 701 can be configured to communicate with network 743b using communication subsystem 731. Networks 743a and 743b can be one or more of the same networks or one or more different networks. Communication subsystem 731 can be configured to include one or more transceivers for communicating with network 743b. For example, communication subsystem 731 can be configured to include one or more remote transceivers for communicating with another device (e.g., another WD, UE) or a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 733 and / or receiver 735 to implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for the RAN link, respectively. Furthermore, the transmitter 733 and receiver 735 of each transceiver can share circuit components, software, or firmware, or alternatively, they can be implemented separately.

[0502] In the illustrated embodiment, the communication functions of the communication subsystem 731 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as the use of a Global Positioning System (GPS) for determining location), another similar communication function, or any combination thereof. For example, the communication subsystem 731 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 743b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 743b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 713 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 700.

[0503] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 700 or divided among multiple components of UE 700. Furthermore, 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 731 may be configured to include any of the components described herein. Additionally, the processing circuitry 701 may be configured to communicate with any such component via bus 702. In another example, any such component may be represented by program instructions stored in memory, which, when executed by the processing circuitry 701, perform the corresponding functions described herein. In yet another example, the functionality of any such component may be divided between the processing circuitry 701 and the communication subsystem 731. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0504] Figure 8 An example virtualization environment according to certain embodiments is shown. Figure 8 This is a schematic block diagram illustrating a virtualized environment 800, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating virtual versions of devices or equipment, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication equipment) or components thereof, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0505] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 800 hosted on one or more hardware nodes 830. Furthermore, in embodiments where the virtual node is not a radio access node or does not require a radio connection (e.g., a core network node), the network node may be fully virtualized in this case.

[0506] These functionalities can be implemented by one or more applications 820 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), one or more applications 820 being operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Applications 820 run in a virtualization environment 800, which provides hardware 830 including processing circuitry 860 and memory 890. Memory 890 contains instructions 895 executable by the processing circuitry 860, thereby enabling application 820 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0507] The virtualization environment 800 includes general-purpose or special-purpose network hardware devices 830, which include one or more processors or processing circuitry 860, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 890-1, which may be non-permanent memory for temporarily storing instructions 895 or software executed by the processing circuitry 860. Each hardware device may include one or more network interface controllers (NICs) 870, also referred to as network interface cards, which include physical network interfaces 880. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 890-2 in which software 895 and / or instructions executable by the processing circuitry 860 are stored. Software 895 may include any type of software, including software for instantiating one or more virtualization layers 850 (also referred to as hypervisors), software for executing virtual machines 840, and software that allows them to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0508] Virtual machine 840 includes virtual processing, virtual memory, virtual networking or interface, and virtual storage, and can be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of instances of virtual device 820 may be implemented on one or more of virtual machines 840, and the implementation may be made in different ways.

[0509] During operation, the processing circuitry 860 executes software 895 to instantiate a hypervisor or virtualization layer 850, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 850 can present a virtual operating platform, which appears to the virtual machine 840 as networked hardware.

[0510] like Figure 8As shown, hardware 830 can be a standalone network node with general or specific components. Hardware 830 may include antenna 8225 and may implement some functions through virtualization. Alternatively, hardware 830 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and coordination (MANO) 8100, which oversees the lifecycle management of application 820, and so on.

[0511] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises.

[0512] In the context of NFV, virtual machine 840 can be a software implementation of a physical machine, and its programs run as if they were running on a physical, non-virtualized machine. Each virtual machine 840, along with the portion of hardware 830 that executes that virtual machine (which can be hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in virtual machine 840), forms a separate virtual network element (VNE).

[0513] Still within the context of NFV, Virtual Network Functions (VNFs) are responsible for handling specific network functions running in one or more virtual machines 840 on top of the hardware network infrastructure 830, and correspond to... Figure 8 Application 820 in the text.

[0514] In some embodiments, each of the one or more radio units 8200, including one or more transmitters 8220 and one or more receivers 8210, may be coupled to one or more antennas 8225. The radio unit 8200 may communicate directly with the hardware node 830 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide a radio-capable virtual node, such as a radio access node or base station.

[0515] In some embodiments, the control system 8230 may be used to implement some signaling, and the control system 8230 may alternatively be used for communication between the hardware node 830 and the radio unit 8200.

[0516] Figure 9 An example telecommunications network is shown, according to certain embodiments, connected to a host computer via an intermediate network. (Refer to...) Figure 9According to an embodiment, the communication system includes a telecommunications network 910 (e.g., a 3GPP-type cellular network), which includes an access network 911 (e.g., a radio access network) and a core network 914. The access network 911 includes multiple base stations 912a, 912b, and 912c (e.g., NB, eNB, gNB, or other types of wireless access points), each defining a corresponding coverage area 913a, 913b, or 913c. Each base station 912a, 912b, or 912c can be connected to the core network 914 via a wired or wireless connection 915. In some embodiments, base stations 912a, 912b, and 912c can be network nodes as described herein. A first UE 991 located in coverage area 913c is configured to wirelessly connect to or be paged by the corresponding base station 912c. A second UE 992 in coverage area 913a can wirelessly connect to the corresponding base station 912a. Although multiple UEs 991, 992 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 912. In some embodiments, the multiple UEs 991, 992 can be as follows relative to... Figure 16 The user equipment described.

[0517] Telecommunication network 910 is connected to host computer 930, which may be implemented as a standalone server, a cloud-based server, a distributed server, or as a processing resource within a server cluster. Host computer 930 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 921 and 922 between telecommunications network 910 and host computer 930 may extend directly from core network 914 to host computer 930, or may be made via optional intermediate network 920. Intermediate network 920 may be one or more of public, private, or bearer networks; intermediate network 920 (if present) may be a backbone network or the Internet; specifically, intermediate network 920 may include two or more subnetworks (not shown).

[0518] Figure 9The communication system as a whole realizes the connection between the connected UEs 991 and 992 and the host computer 930. This connection can be described as an over-the-top (OTT) connection 950. The host computer 930 and the connected UEs 991 and 992 are configured to transmit data and / or signaling via the OTT connection 950 using access network 911, core network 914, any intermediate network 920, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 950 can be transparent in the sense that the participating communication devices traversed by the OTT connection 950 are unaware of the routes of uplink and downlink communications. For example, it may not be necessary to notify the base station 912 of past routes of input downlink communications with data originating from the host computer 930 to be forwarded (e.g., handed over) to the connected UE 991. Similarly, the base station 912 does not need to be aware of future routes of output uplink communications originating from the UE 991 to the host computer 930.

[0519] Figure 10 An example host computer is shown that communicates with a user equipment via a base station through a partially wireless connection according to some embodiments. Reference will now be made to... Figure 10 This section describes example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In the communication system 1000, the host computer 1010 includes hardware 1015, which includes a communication interface 1016 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1000. The host computer 1010 also includes processing circuitry 1018, which may have storage and / or processing capabilities. Specifically, the processing circuitry 1018 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 1010 also includes software 1011, which is stored in or accessible by the host computer 1010 and executable by the processing circuitry 1018. The software 1011 includes a host application 1012. Host application 1012 is operable to provide services to a remote user (e.g., UE 1030), which is connected via an OTT connection 1050 terminated at both UE 1030 and host computer 1010. When providing services to the remote user, host application 1012 can provide user data transmitted using the OTT connection 1050.

[0520] The communication system 1000 also includes a base station 1020 provided in a telecommunications system. The base station 1020 includes hardware 1025 enabling it to communicate with a host computer 1010 and a UE 1030. In some embodiments, the base station 1020 may be a network node as described herein. Hardware 1025 may include: a communication interface 1026 for establishing and maintaining wired or wireless connections to interfaces with different communication devices of the communication system 1000; and a radio interface 1027 for establishing and maintaining connections with at least the coverage area served by the base station 1020. Figure 10 The UE 1030 (not shown in the image) has a wireless connection 1070. The communication interface 1026 can be configured to facilitate a connection 1060 to the host computer 1010. The connection 1060 can be direct, or it can be via the core network of the telecommunications system (…). Figure 10 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1025 of base station 1020 also includes processing circuitry 1028, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. Base station 1020 also has software 1021 stored internally or accessible via an external connection.

[0521] The communication system 1000 also includes the previously mentioned UE 1030. In some embodiments, the UE 1030 may be as follows relative to... Figure 11-13The user equipment described in section 16. Its hardware 1035 may include a radio interface 1037 configured to establish and maintain a wireless connection 1070 with a base station serving the coverage area currently occupied by the UE 1030. The hardware 1035 of the UE 1030 also includes processing circuitry 1038, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 1030 also includes software 1031, which is stored in or accessible by the UE 1030 and executable by the processing circuitry 1038. The software 1031 includes a client application 1032. The client application 1032 is operable to provide services to human or non-human users via the UE 1030 with the support of a host computer 1010. In the host computer 1010, a host application 1012 executing may communicate with the client application 1032 via an OTT connection 1050 terminated at the UE 1030 and the host computer 1010. When providing services to a user, client application 1032 can receive request data from host application 1012 and provide user data in response to the request data. OTT connection 1050 can transmit both the request data and the user data. Client application 1032 can interact with the user to generate the user data it provides.

[0522] Notice, Figure 10 The host computer 1010, base station 1020, and UE 1030 shown can be respectively connected to Figure 9 The host computer 930, base stations 912a, 912b, and 912c, and UEs 991 and 992 are similar to or identical to each other. That is to say, the internal workings of these entities can be as follows: Figure 10 As shown, and independently, the surrounding network topology can be Figure 9 The network topology.

[0523] exist Figure 10 The OTT connection 1050 has been abstractly depicted to illustrate communication between the host computer 1010 and the UE 1030 via base station 1020, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine this route, which can be configured to be hidden from the UE 1030, the service provider operating the host computer 1010, or both. While the OTT connection 1050 is active, the network infrastructure can also make decisions to dynamically change the route (e.g., based on load balancing considerations or network reconfiguration).

[0524] The wireless connection 1070 between UE 1030 and base station 1020 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE 1030 using OTT connection 1050, wherein wireless connection 1070 forms the final segment of OTT connection 1050. More specifically, the teachings of these embodiments can improve data rates, latency, and power consumption, thereby providing benefits such as reduced user wait time, better responsiveness, less interference, and extended battery life.

[0525] For the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments, a measurement process may be provided. Optional network functions may also be available for reconfiguring the OTT connection 1050 between the host computer 1010 and the UE 1030 in response to changes in measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 1050 may be implemented using software 1011 and hardware 1015 of the host computer 1010, or software 1031 and hardware 1035 of the UE 1030, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 1050 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software 1011, 1031 can use to calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1050 may include message formatting, retransmission settings, preferred routing, etc.; this reconfiguration does not need to affect the base station 1020, and it may be unknown or imperceptible to the base station 1020. Such processes and functions may be known and practiced in the art. In a particular embodiment, measurement may involve proprietary UE signaling that facilitates the host computer 1010 to measure throughput, propagation time, latency, etc. This measurement may be implemented as follows: software 1011 and 1031 enable the use of the OTT connection 1050 to send messages (specifically, empty messages or "fake" messages) while monitoring propagation time, errors, etc.

[0526] Figure 11 Example methods implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments, are shown. More specifically, Figure 11 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 9 and Figure 10 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 11The diagram is referenced. In step 1110, the host computer provides user data. In sub-step 1111 of step 1110 (which may be optional), the host computer provides user data by executing a host application. In step 1120, the host computer initiates a transmission carrying user data to the UE. In step 1130 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0527] Figure 12 Example methods implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments, are shown. More specifically, Figure 12 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 9 and Figure 10 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 12 The diagram is referenced. In step 1210 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1220, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be via a base station. In step 1230 (which may be optional), the UE receives the user data carried in the transmission.

[0528] Figure 13 Further example methods implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments, are shown. More specifically, Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 9 and Figure 10 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 13The diagram is referenced. In step 1310 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data. In sub-step 1321 of step 1320 (which may be optional), the UE provides user data by executing a client application. In sub-step 1311 of step 1310 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 1330 (which may be optional). In step 1340 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0529] Figure 14 Another example method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments, is shown. More specifically, Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE (User Equipment), which may be a reference... Figure 9 and Figure 10 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 14 The diagram is referenced. In step 1410 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1420 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1430 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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

[0531] Figure 15 This is a flowchart of a method performed at a user equipment according to certain embodiments. Method 1500 begins at step 1510, wherein the UE sends a request to a network node to initiate connection establishment. In some embodiments, connection establishment may be a recovery process, an establishment process, or early data transmission.

[0532] In step 1520, the UE starts a timer for establishing a connection. In some embodiments, the UE may start the timer when sending a request to the network node. In some embodiments, the expiration of the timer may stop the connection establishment.

[0533] In step 1530, the UE stops the timer to halt connection establishment when it receives a pause message or release message, or when a cell reselection procedure is being performed while the timer is running. In some embodiments, the timer can be configured to stop connection establishment for certain events.

[0534] In some embodiments, the method may further include: in response to stopping a timer when the UE receives a release message, delaying an action to be performed by the UE after receiving the release message for a period of time. When the UE receives a release message including mobility control information, the UE may also store cell information. On the other hand, when the UE receives a release message without mobility control information, the UE may also apply cell information from system information. In some embodiments, the method may further include: after stopping the timer when the UE receives a pause message, instructing the upper layer to pause connection establishment, and configuring the lower layer to pause integrity protection. In some embodiments, this action may be delayed by 60 ms.

[0535] In some embodiments, the method may further include: stopping the timer in response to the UE performing a cell reselection process while the timer is running, resetting the MAC, releasing the MAC configuration, and notifying the upper layer that the connection establishment has failed.

[0536] Figure 16 This is a schematic block diagram of an exemplary user equipment according to certain embodiments. User equipment 1600 can be used in a wireless network (e.g., Figure 6 In the wireless network shown. User equipment 1600 can be in a wireless device or network node (e.g., Figure 6 This is implemented in the wireless device 610 or network node 660 shown. User equipment 1600 is operable to execute the reference... Figure 15 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 15 The method is not necessarily performed solely by user equipment 1600. At least some operations of the method may be performed by one or more other entities.

[0537] User equipment 1600 may include processing circuitry (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). In some embodiments, the processing circuitry of user equipment 1600 may be... Figure 6 The processing circuit 620 is shown. In some embodiments, the processing circuit of the user equipment 1600 may be... Figure 7 The processor 701 shown. The processing circuitry can be configured to execute functions stored in memory. Figure 7 The program code in the illustrated memory 715 may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage device, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more technologies described herein. In some embodiments, processing circuitry may be used to cause the transmitting unit 1610, the starting unit 1620, and the stopping unit 1630, as well as any other suitable unit of the user equipment 1600, to perform corresponding functions according to one or more embodiments of this disclosure, such as transmitters and receivers.

[0538] like Figure 16 As shown, user equipment 1600 includes a sending unit 1610, an initiation unit 1620, and a stopping unit 1630. The sending unit 1610 can be configured to send a request to a network node to initiate connection establishment. In some embodiments, connection establishment may be a recovery process, an establishment process, or early data transmission.

[0539] The initiation unit 1620 can be configured to start a timer for connection establishment. In some embodiments, the initiation unit 1620 can start the timer when the sending unit 1610 sends a request to the network node. In some embodiments, the expiration of the timer can stop connection establishment.

[0540] The stop unit 1630 can be configured to stop connection establishment upon receiving a pause message or release message, or while a cell reselection process is being performed during timer operation. In some embodiments, the timer can be configured to stop connection establishment for certain events.

[0541] In some embodiments, UE 1600 may also delay the action to be performed by UE 1600 after receiving a release message by a certain time period in response to stopping the timer upon receiving the release message. When UE 1600 receives a release message including mobility control information, UE 1600 may also store cell information. On the other hand, when UE 1600 receives a release message without mobility control information, UE 1600 may also apply cell information from system information. In some embodiments, UE 1600 may further include: after stopping the timer upon receiving a pause message, instructing the upper layer to pause connection establishment, and configuring the lower layer to pause integrity protection. In some embodiments, this action may be delayed by 60 ms.

[0542] In some embodiments, the UE 1600 may also stop the timer, reset the MAC, release the MAC configuration, and notify the upper layer of connection establishment failure in response to the timer being executed while the timer is running and the cell reselection process is being performed.

[0543] The term “unit” can have a conventional meaning in the field of electronic products, electrical equipment and / or electronic devices, and can include, for example, electrical and / or electronic circuits, devices, modules, processors, receivers, transmitters, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc. (such as those described herein).

[0544] According to various embodiments, the advantage of the features described herein is that a timer is provided to protect the UE from errors while waiting for a response from the network. The timer can stop connection establishment for certain events or finite time periods to prevent the UE from getting stuck in connection establishment. Another advantage is that the timer can prevent the UE from performing unnecessary actions after the connection establishment expires, which can further improve resource efficiency in the network and limit UE battery consumption and potential interference.

[0545] While the processes in the accompanying drawings may illustrate a particular sequence of operations performed in certain embodiments of the invention, it should be understood that such sequence is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0546] While the invention has been described with reference to several embodiments, those skilled in the art will recognize that the invention is not limited to the described embodiments, but can be implemented using modifications and variations within the spirit and scope of the appended claims. This description is therefore to be considered illustrative rather than restrictive.

Claims

1. A method for restoring connection in a user equipment (UE), the method comprising: Send a Radio Resource Control (RRC) recovery request to the network node to initiate the RRC connection recovery process; Start a timer for the RRC connection recovery procedure, wherein the expiration of the timer stops the RRC connection recovery procedure for the UE; and The timer is stopped under one of the following conditions: The UE receives a pause message; and The UE receives a release message.

2. The method according to claim 1, further comprising: In response to stopping the timer after the UE receives the release message, the action to be performed by the UE after receiving the release message is delayed for a first time period.

3. The method according to claim 1, further comprising: When the release message includes mobility control information, cell information is stored at the UE.

4. The method according to claim 1, further comprising: When the release message does not include mobility control information, the cell information in the application system information is used.

5. The method according to claim 2, wherein, The first time period is 60ms.

6. The method according to claim 1, further comprising: In response to the UE receiving a pause message, the timer is stopped: The action that the UE is to perform after receiving the pause message is delayed for a first time period; Instruct the upper layer to pause the RRC connection restoration process; and Configure the lower layer to suspend integrity protection.

7. The method according to claim 6, wherein, The first time period is 60ms.

8. A user equipment (UE) for restoring connection, the UE comprising: Processing circuitry; as well as A memory storing instructions that, when executed by the processing circuitry, cause the UE to: Send a Radio Resource Control (RRC) recovery request to the network node to initiate the RRC connection recovery process; Start a timer for the RRC connection recovery process, wherein the RRC connection recovery process stops upon the expiration of the timer; and The timer is stopped under one of the following conditions: Received a pause message; and Release notification received.

9. The UE according to claim 8, wherein, The instruction also causes the UE to stop the timer upon receiving the release message, and delays the action to be performed by the UE after receiving the release message for a first time period.

10. The UE according to claim 8, wherein, The instruction also causes the UE to store cell information when the release message includes mobility control information.

11. The UE according to claim 8, wherein the instruction further causes the UE to apply cell information in the system information when the release message does not include mobility control information.

12. The UE according to claim 9, wherein, The first time period is 60ms.

13. The UE according to claim 8, wherein, The instruction also causes the UE to stop the timer in response to receiving a pause message: The action that the UE is to perform after receiving the pause message is delayed for a first time period; Instruct the upper layer to pause the RRC connection restoration process; and Configure the lower layer to suspend integrity protection.

14. The UE according to claim 13, wherein, The first time period is 60ms.

Images