CN117999850A

CN117999850A - Parameter update for connection recovery attempts

Info

Publication number: CN117999850A
Application number: CN202180102599.8A
Authority: CN
Inventors: S·H·特蒂南; J-P·科斯基南; 吴春丽
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2021-09-24
Filing date: 2021-09-24
Publication date: 2024-05-07
Also published as: WO2023044822A1

Abstract

Example embodiments of the present disclosure relate to apparatuses, methods, devices, and computer-readable storage media for parameter updating for connection recovery attempts. In an example embodiment, a terminal device in an inactive mode obtains one or more updated parameters by updating one or more current configuration parameters based on an update mode. The terminal device in the inactive mode initiates a connection recovery attempt using one or more updated parameters.

Description

Parameter update for connection recovery attempts

Technical Field

Example embodiments of the present disclosure relate generally to the field of communications and, in particular, relate to an apparatus, method, device, and computer-readable storage medium for parameter updating for connection recovery attempts.

Background

Three Small Data Transmission (SDT) types are defined in third generation partnership project (3 GPP) release 17 (REL 17), including SDT based on 4-step Random Access Channel (RACH) (4-step RA SDT), SDT based on 2-step RACH (2-step RA SDT), and Physical Uplink Shared Channel (PUSCH) transmission based on configuration grants (CG-SDT). In a 4-step RA SDT, the SDT payload may be transmitted by a User Equipment (UE) using message 3 (Msg 3) (PUSCH). In a two-step RA SDT, the SDT payload may be sent by the UE using a message a (MsgA) PUSCH. In CG-SDT, if the UE has a valid Timing Advance (TA), the PUSCH resources based on configuration grant type 1 may be used by the UE to send the SDT payload, e.g., without a random access procedure.

During or after the SDT procedure, the UE may initiate a new SDT procedure or a recovery procedure, e.g., after the RRCReject message that SDT or non-SDT data arrives during the SDT procedure. The main problem in this respect is the security problem due to reusing the input parameters used to calculate resumeMAC-I in a Common Control Channel (CCCH) message to initiate a new SDT procedure or recovery procedure.

Disclosure of Invention

In general, example embodiments of the present disclosure provide apparatus, methods, devices, and computer-readable storage media for parameter updating for connection recovery attempts.

In a first aspect, a terminal device is provided, the terminal device comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the terminal device to obtain one or more updated parameters in the inactive mode by updating one or more current configuration parameters based on the update mode. The terminal device is further caused to initiate a connection recovery attempt using the one or more updated parameters in the inactive mode.

In a second aspect, a network device is provided that includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the network device to determine an update mode for one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt. The network device is caused to send an indication of an update mode for one or more current configuration parameters to the terminal device. The network device is further caused to detect a connection recovery attempt from the terminal device using one or more updated parameters generated by updating the one or more parameters based on the update pattern.

In a third aspect, a method is provided. In the method, a terminal device in an inactive mode obtains one or more updated parameters by updating one or more current configuration parameters based on an update mode. The terminal device in the inactive mode initiates a connection recovery attempt using one or more updated parameters.

In a fourth aspect, a method is provided. In the method, the network device determines an update mode of one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt. The network device sends an indication of an update mode for one or more current configuration parameters to the terminal device. The network device detects a connection recovery attempt from the terminal device using one or more updated parameters generated by updating one or more parameters based on the update pattern.

In a fifth aspect, there is provided an apparatus comprising means for performing the method according to the third or fourth aspect.

In a sixth aspect, a computer readable storage medium is provided, the computer readable storage medium including program instructions stored thereon. The instructions, when executed by a processor of a device, cause the device to perform a method according to the third or fourth aspect.

It should be understood that the summary is not intended to identify key or essential features of the example embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Some example embodiments will now be described with reference to the accompanying drawings, in which:

FIG. 1 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

FIG. 2 illustrates a flowchart of an example method according to some example embodiments of the present disclosure;

FIG. 3 illustrates a flowchart of an example method according to some other example embodiments of the present disclosure;

FIG. 4 illustrates an example process for connection restoration according to some example embodiments of the present disclosure; and

Fig. 5 illustrates a simplified block diagram of an apparatus suitable for implementing example embodiments of the present disclosure.

The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements.

Detailed Description

Principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these example embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and practicing the present disclosure without placing any limitation on the scope of the present disclosure. The disclosure described herein may be implemented in a variety of ways other than those described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. Communication may involve the transmission and/or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information over the air. In some example embodiments, the UE may be configured to send and/or receive information without direct human interaction. For example, the UE may transmit information to the base station according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network side.

Examples of UEs include, but are not limited to, smartphones, wireless enabled tablet computers, notebook embedded devices (LEEs), notebook mounted devices (LMEs), wireless Customer Premise Equipment (CPE), sensors, metering devices, personal wearable devices (such as watches), and/or communication-capable vehicles. For purposes of discussion, some example embodiments will be described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure.

As used herein, the term "network device" refers to a device via which services can be provided to terminal devices in a communication network. For example, the network device may include a base station. As used herein, the term "base station" (BS) refers to a network device via which services may be provided to terminal devices in a communication network. A base station may comprise any suitable device via which a terminal device or UE may access a communication network. Examples of base stations include relays, access Points (APs), transmission points (TRPs), node bs (nodebs or NB), evolved nodebs (eNodeB or eNB), new Radio (NR) nodebs (gNB), remote radio modules (RRU), radio Headers (RH), remote Radio Heads (RRH), low power nodes (such as femto, pico), etc.

As used herein, the term "circuitry" may refer to one or more or all of the following:

(a) Hardware-only circuit implementations (such as implementations in analog and/or digital circuitry only), and

(B) A combination of hardware circuitry and software, such as (as applicable):

(i) Combination of analog and/or digital hardware circuit(s) and software/firmware, and

(Ii) Any portion of the hardware processor(s) (including digital signal processor (s)), software, and memory(s) having software that work together to cause a device (such as a mobile phone or server) to perform various functions, and

(C) Hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware)

The operation is performed, but when the software is not required to perform the operation, the software may not exist.

This definition of circuitry applies to all uses of that term in this application, including in any claims. As a further example, as used in this disclosure, the term circuitry also encompasses hardware-only circuits or processors (or multiple processors) or portions of hardware circuits or processes and their attendant software and/or firmware implementations. For example, and if applicable to the particular claim elements, the term circuitry also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station.

As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "comprising" and variants thereof should be understood as open-ended terms, meaning "including, but not limited to. The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other explicit and implicit definitions may be included below.

As used herein, the terms "first," "second," and the like may be used to describe various elements, which should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

As described above, the UE may initiate a new SDT procedure or a recovery procedure, e.g., after a RRCReject message of SDT or non-SDT data arrival during the SDT procedure or after the occurrence of a cell reselection during the SDT procedure. In Common Control Channel (CCCH) based methods, a new SDT procedure is initiated after an event (e.g., following a RRCReject message that SDT or non-SDT data arrives during the SDT procedure or a cell reselection during the SDT procedure). Dedicated Control Channel (DCCH) based methods of non-SDT data arrival can only indicate non-SDT data arrival during SDT, but cannot overcome other SDT process termination, e.g., due to RRCReject. This is because, in DCCH-based methods, non-SDT data arrival is indicated during SDT using a newly defined RRC message through DCCH logical channels. Thus, an option for supporting CCCH-based methods would be preferred, as it can support different scenarios.

The main problem with CCCH based methods is the safety issue. For example, in the first SDT message, the UE may have sent data that is protected with the generated key. When the Network (NW) responds, for example with RRCReject, or non-SDT data is present in the UE buffer, initiating a new SDT procedure with the same key will pose a security threat in case the Packet Data Convergence Protocol (PDCP) entity of the Data Radio Bearer (DRB) whose data has been sent will be re-established.

In addition, RRCResumeRequest messages also present a security threat in that the generated resumeMAC-I will remain until the input parameters used to generate resumeMAC-I are changed. To avoid replay attacks, reuse of resumeMAC-I should be avoided. The input parameters for calculating resumeMAC-I may include KEY (KEY), PDCP COUNT (PDCP COUNT), MESSAGE (MESSAGE), DIRECTION (DIRECTION), and BEARER (BEARER). Any change in the input parameters is sufficient to produce a different resumeMAC-I and avoid its reuse.

However, changing the parameters necessarily means blind decoding on the NW side. Furthermore, updating or counting only one of these parameters (e.g., in ascending order) by the UE may be vulnerable.

Example embodiments of the present disclosure provide a scheme for parameter update for connection recovery attempts, such as resumeMAC-I in RRCResumeRequest. With this scheme, the network device configures an update mode of one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt. For example, when the terminal device is released from a CONNECTED mode (such as rrc_connected mode) to an INACTIVE mode (such as rrc_inactive mode), the network device may send an indication of the update mode to the terminal device. As another example, the update mode of the one or more current configuration parameters to be used by the terminal device in the inactive mode to initiate the connection recovery attempt may be predefined (e.g., in a technical specification). As another example, the update mode of the first set of one or more current configuration parameters to be used by the terminal device in the inactive mode to initiate a connection recovery attempt may be configured by the network device, while the update mode of the second set of one or more current configuration parameters to be used by the terminal device in the inactive mode to initiate a connection recovery attempt may be predefined (e.g., in a technical specification).

Thus, based on the update mode, the terminal device determines how the current configuration parameters should be updated (e.g., for SDT or non-SDT) when a connection recovery attempt is needed. The terminal device initiates a connection recovery attempt using one or more updated parameters obtained by updating one or more current configuration parameters based on the update mode.

For example, the configuration of the update mode will facilitate the network device due to less blind decoding. When the network device configures how to update the input parameters, the network device may perform less blind detection to determine the input parameters for the updated resumeMAC-I. Furthermore, the configuration of the update mode brings security. Since the update mode of the input parameters is configured by the network device and provided to the terminal device, it is difficult for an attacker to infer how the terminal device performs the update of the input parameters at the time of the recovery attempt.

FIG. 1 illustrates an example environment 100 in which example embodiments of the present disclosure may be implemented.

The environment 100, which may be part of a communication network, includes a network device 110 and a terminal device 120 that may communicate with each other. It should be understood that two devices are shown in environment 100 for illustrative purposes only and are not intended to suggest any limitation as to the scope of the disclosure. In some example embodiments, environment 100 may include any suitable number of network devices and terminal devices.

Communications in environment 100 may conform to any suitable communications standard or protocol that already exists or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), long Term Evolution (LTE), LTE-advanced (LTE-a), fifth generation (5G) New Radio (NR), wireless fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employ any suitable communications technology including, for example, multiple Input Multiple Output (MIMO), orthogonal Frequency Division Multiplexing (OFDM), time Division Multiplexing (TDM), frequency Division Multiplexing (FDM), code Division Multiplexing (CDM), bluetooth, zigbee, and Machine Type Communications (MTC), enhanced mobile broadband (eMBB), large-scale machine type communications (mMTC), ultra-reliable low latency communications (URLLC), carrier Aggregation (CA), dual Connectivity (DC), and new radio unlicensed (NR-U) technologies.

In the environment 100, the terminal device 120 may transmit SDT data and non-SDT data. In the context of the present disclosure, non-SDT data refers to data on Data Radio Bearers (DRBs) or Signaling Radio Bearers (SRBs) that are not configured for SDT. When the terminal device 120 is in an INACTIVE state (such as rrc_inactive mode), the terminal device 120 may initiate a connection recovery attempt. For example, if non-SDT data arrives or cell reselection is to be performed during an SDT procedure, if the SDT procedure is rejected by the network device 110, if an SDT failure timer expires, or if the Radio Link Control (RLC) entity reaches a configured maximum number of retransmissions, the terminal device 120 may initiate a connection recovery attempt.

In various example embodiments of the present disclosure, network device 110 configures an update mode of one or more current configuration parameters to be used by terminal device 120 in an inactive mode to initiate a connection recovery attempt. Thus, the terminal device 120 in the inactive mode obtains one or more updated parameters by updating one or more current configuration parameters based on the update mode and initiates a connection recovery attempt using the one or more updated parameters.

Fig. 2 illustrates a flowchart of an example method 200 according to some example embodiments of the present disclosure. The method 200 may be implemented by the terminal device 120. For discussion purposes, the method 200 will be described with reference to FIG. 1.

At block 205, terminal device 120 receives an indication of an update mode of one or more current configuration parameters from network device 110 to be used in an INACTIVE mode (such as an rrc_inactive mode) to initiate a connection recovery attempt. For example, the parameters may include input parameters (KEY, PDCP COUNT, MESSAGE DIRECTION, BEARER) that have been configured by the network device 110 and have a certain value to generate resumeMAC-I, for example. The current values of these parameters may be indicated in advance by network device 110 or may be specified or predefined. For example, by default, these values may be binary "1", or these values may be some other value indicated in SRB 0. The indication of the update mode transmitted from the network device 110 to the terminal device 120 may indicate the update mode. This may mean, for example, that an update pattern is provided by the network device 110 to the terminal device 120.

In some example embodiments, an update pattern to be used to generate one or more parameters of resumeMAC-I is provided. Thus, in some embodiments, the parameter(s) may include currently configured and/or unconfigured parameters. Thus, embodiments described herein may additionally or alternatively be used to update the currently unconfigured parameter(s).

The update pattern may be associated with any suitable characteristic of the currently configured parameters for the connection recovery attempt. For example, the update pattern may include a step size for updating a corresponding one of the parameters. Thus, the terminal device 120 can change the corresponding parameters in steps. Alternatively or additionally, the update mode may comprise an order for updating the parameters such that the terminal device 120 updates the parameters one after the other in order. Alternatively or additionally, the update mode may comprise an identification of one or more parameters to inform the terminal device 120 which parameters are to be updated. For example, the update mode may indicate that one of the parameters (e.g., PDCP COUNT for resumeMAC-I generation) is to be updated.

While in a CONNECTED mode (such as an rrc_connected mode), the terminal device 120 may receive an indication of an update mode from the network device 110. For example, terminal device 120 may receive a release message from network device 110 to release terminal device 120 from the connected mode to the inactive mode. The release message may include an indication of an update mode of one or more current configuration parameters.

Block 205 in fig. 2 is optional. In some example embodiments, the update pattern may be predefined (e.g., in a technical specification). In some other example embodiments, the update pattern for the first set of one or more current configuration parameters used to initiate the connection recovery attempt may be configured by the network device 110, while the update pattern for the second set of one or more current configuration parameters used to initiate the connection recovery attempt may be predefined (e.g., in a technical specification).

At block 210, while in the inactive mode, the terminal device 120 obtains one or more updated parameters by updating one or more current configuration parameters based on the update mode. For example, if one of the update mode indication parameters (e.g., PDCP COUNT for resumeMAC-I generation) is to be updated based on the step size, the terminal device 120 may increase or decrease the one of the parameters by the indicated step size. As another example, if the update mode indicates an order of a plurality of parameters, the terminal device 120 may update one of the parameters at a time in the indicated order.

When a connection recovery attempt is required, the terminal device 120 may determine updated parameters. For example, if non-SDT data arrives at an uplink data buffer at the terminal device 120, or cell reselection is to be performed during an SDT procedure, if the SDT procedure is rejected by the network device 110, if the SDT failure timer expires, or if the RLC entity reaches a configured maximum number of retransmissions, the terminal device 120 may obtain updated parameters based on the update mode. Thus, CCCH-based retries may support more use cases including SDT rejection, non-SDT data arrival, cell reselection, etc.

At block 215, the terminal device 120 in the inactive mode initiates a connection recovery attempt using one or more updated parameters. For example, the terminal device 120 generates a connection recovery request using one or more updated parameters and initiates a connection recovery attempt with the connection recovery request. The connection restoration request may include resumeMAC-I generated based on one or more updated parameters.

In some example embodiments, the connection restoration request may be used to initiate a connection restoration process. In this case, for example, after the SDT procedure has been rejected, or after non-SDT data arrives or cell reselections during the SDT procedure, the terminal device 120 may not perform the SDT procedure with updated resumeMAC-I, but only perform the non-SDT procedure (e.g., a conventional RRC recovery procedure). Based on the updated resumeMAC-I, the network device 110 may infer that the terminal device 120 has previously performed SDT and may trigger a change in the parameter KEY of the SDT data bearer (such as SDT DRB) or other bearers when the connection is restored. The network device 110 may also trigger PDCP entity(s) re-establishment of the SDT DRB because these entities have used the key for the data at the time of the previous SDT transmission. Thus, upon completion of the connection recovery procedure, the terminal device 120 may receive an indication of the changed value of KEY from the network device 110.

In some other example embodiments, the connection restoration request may be used to initiate a new SDT procedure. For example, the terminal device 120 may perform the new SDT procedure using the updated resumeMAC-I. In some example embodiments, for parameter COUNT, in addition to updating the parameter COUNT of the connection recovery attempt based on the configured update pattern (which is one of the current configuration parameters), the terminal device 120 may also update the parameter COUNT of the SDT data bearer based on the configured update pattern. For example, the terminal device 120 may update not only the COUNT value for resumeMAC-I generation, but also the COUNT value of the data bearer(s) that are using the SDT procedure. This may avoid an attacker deducing how many attempts have been made by the terminal device 120 in case the COUNT value of the data bearer(s) will be increased as usual.

In some example embodiments, terminal device 120 may receive an indication from network device 110 whether one or more current configuration parameters are allowed to be updated. The indication may be received in a connection rejection message, such as an RRC rejection message. If the update is allowed, the terminal device 120 updates the parameters based on the update mode. If the update is disabled, the terminal device 120 may enter an idle mode from an inactive mode.

In some example embodiments, the number of parameter updates may be limited by the number of connection recovery attempts. For example, the terminal device 120 may enter an idle mode from an inactive mode if the number of connection recovery attempts initiated by updating one or more current configuration parameters is above a threshold number. In some example embodiments, the maximum number of recovery attempts may be pre-specified. According to the specification, the terminal device 120 can know how many restoration attempts are allowed to be performed by updating the input parameters. In some other example embodiments, the maximum number of recovery attempts may be configured by network device 110 and sent to terminal device 120.

Fig. 3 illustrates a flowchart of an example method 300 according to some example embodiments of the present disclosure. The method 300 may be implemented by the network device 110. For discussion purposes, the method 300 will be described with reference to FIG. 1.

At block 305, the network device 110 determines an update mode for one or more current configuration parameters to be used by the terminal device 120 in an inactive mode to initiate a connection recovery attempt. For example, the network device 110 may configure which input parameters (KEY, PDCP COUNT, MESSAGE DIRECTION, BEARER) the UE will update and which step size to utilize. In some example embodiments, network device 110 may configure the order in which the input parameters need to be updated by terminal device 120. In some example embodiments, it may be specified that one of the parameters (e.g., PDCP COUNT for resumeMAC-I generation) is updated while the update mode is configured by the network device 110.

At block 310, network device 110 sends an indication of an update mode of one or more current configuration parameters to terminal device 120. For example, after releasing the terminal device 120 to an INACTIVE mode, such as an rrc_inactive mode, the network device 110 may send an indication of how the input parameters of resumeMAC-I are to be updated by the terminal device 120 to generate a new resumeMAC-I (for SDT or non-SDT) for the connection recovery attempt.

At block 315, network device 110 detects a connection recovery attempt from terminal device 120 using one or more updated parameters generated by updating one or more parameters based on the update pattern. For example, network device 110 may use one or more updated parameters to detect a connection recovery request from terminal device 120. The connection restoration request may include resumeMAC-I generated based on one or more updated parameters.

In some example embodiments, the terminal device 120 may not perform the SDT procedure with the updated resumeMAC-I, but only perform the non-SDT procedure (such as a conventional RRC recovery procedure), e.g., after the SDT procedure has been rejected, or upon non-SDT data arrival or cell reselection during the SDT procedure. Based on the updated resumeMAC-I, the network device 110 may infer that the terminal device 120 has previously performed SDT. In this case, when the connection is restored, the network device 110 may trigger a key change of the SDT DRBs and a re-establishment of the PDCP entity(s) (because these DRBs have already used the keys for the data at the time of SDT transmission). For example, after the connection recovery procedure initiated by the terminal device 120 is completed, the network device 110 may send an indication of the changed value of the key of the bearer, including the SDT DRB or other bearer, to the terminal device 120.

In some example embodiments, network device 110 may configure how many recovery attempts terminal device 120 may perform by updating the input parameters. After the maximum number of recovery attempts have been performed, the terminal device 120 may enter an idle mode.

In some example embodiments, the network device 110 may indicate to the terminal device 120 whether the input parameters should be updated. In case the input parameter update is not allowed, the terminal device 120 may enter an idle mode. The indication may be sent in a connection rejection message, such as an RRC rejection message.

All of the operations and features described above with reference to fig. 1 and 2 are equally applicable to the method 300 at the network device 110 and have similar effects. Details will be omitted for the sake of simplicity.

Fig. 4 illustrates an example process 400 for connection restoration according to some example embodiments of the disclosure. In this example, terminal device 120 is implemented by UE 405 and network device 110 is implemented by gNB 410.

As shown, at 415, the UE 405 is in a connected mode. At 420, the gNB 410 sends RRCRELEASE with suspendConfig to the UE 405, the suspendConfig containing an SDT configuration including an update mode for resumeMAC-I input parameters. At 425, the UE 405 performs SDT initiation. At 430, the UE 405 initiates an SDT restoration attempt using resumeMAC-I. At 435, the non-SDT data arrives in a buffer at the UE 405. Alternatively, at 440, the UE 405 receives an SDT rejection from the gNB 410. At 445, the UE 405 triggers a new recovery procedure (SDT or non-SDT). At 450, the UE 405 updates resumeMAC-I input parameters based on the configured update mode and generates a new resumeMAC-I. At 455, the UE 405 initiates a recovery attempt with the new resomeMAC-I.

Fig. 5 is a simplified block diagram of an apparatus 500 suitable for implementing example embodiments of the present disclosure.

As shown, the device 500 includes a processor 510, a memory 520 coupled to the processor 510, a communication module 530 coupled to the processor 510, and a communication interface (not shown) coupled to the communication module 530. Memory 520 stores at least program 540. The communication module 530 is used for bi-directional communication, for example via multiple antennas. The communication interface may represent any interface necessary for communication.

The program 540 is assumed to include program instructions that, when executed by the associated processor 510, enable the apparatus 500 to operate in accordance with example embodiments of the present disclosure, as discussed herein with reference to fig. 1-4. The example embodiments herein may be implemented by computer software executable by the processor 510 of the device 500, or by hardware, or by a combination of software and hardware. The processor 510 may be configured to implement various example embodiments of the present disclosure.

Memory 520 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples. Although only one memory 520 is shown in device 500, there may be multiple memory modules physically distinct in device 500. Processor 510 may be of any type suitable to the local technology network and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a Digital Signal Processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. The device 500 may have multiple processors, such as an application specific integrated circuit chip that is temporally subject to a clock that synchronizes the main processor.

When device 500 is acting as terminal device 120, processor 510 and communication module 530 may cooperate to implement method 200 as described above with reference to fig. 1-2. When device 500 acts as network device 110, processor 510 and communication module 530 may cooperate to implement method 300 as described above with reference to fig. 1-3. All of the operations and features as described above with reference to fig. 1-4 are equally applicable to the apparatus 500 and have similar effects. Details will be omitted for the sake of simplicity.

In general, the various example embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the example embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises computer executable instructions, such as those included in program modules, that are executed in a device on a target real or virtual processor to perform the method 200 or 300 or process 400 as described above with reference to fig. 1-4. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various example embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions of program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote memory storage media.

Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote computer or server.

In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device, or processor to perform the various processes and operations described above. Examples of the carrier include a signal, a computer-readable medium.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Moreover, although operations are described in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while the above discussion contains several specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features specific to particular example embodiments. Certain features that are described in the context of separate example embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple exemplary embodiments separately or in any suitable subcombination.

Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Various example embodiments of these techniques have been described. In addition to or as an alternative to the above, the following embodiments are described. The features described in any of the examples below may be used with any of the other examples described herein.

In some aspects, a terminal device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the terminal device to: in the inactive mode, obtaining one or more updated parameters by updating one or more current configuration parameters based on the update mode; and in an inactive mode, initiating a connection recovery attempt using one or more updated parameters.

In some example embodiments, the terminal device is further caused to receive an indication of the update mode from the network device.

In some example embodiments, the one or more updated parameters are obtained in response to at least one of: arrival of non-small data transfer data during a small data transfer process; cell reselection during small data transmission procedures; refusing the small data transmission process; expiration of the small data transmission failure timer; or the radio link control entity reaches the configured maximum number of retransmissions.

In some example embodiments, the terminal device is caused to initiate the connection recovery attempt using one or more updated parameters by: generating a connection restoration request using the one or more updated parameters; and initiating a connection recovery attempt with the connection recovery request.

In some example embodiments, the connection restoration request includes resumeMAC-I generated based on one or more updated parameters.

In some example embodiments, the terminal device is caused to initiate the connection recovery attempt by: a connection recovery procedure is initiated with a connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a key of the bearer, and the terminal device is further caused to: an indication of the changed value of the carried key is received from the network device in response to completion of the connection recovery procedure.

In some example embodiments, the terminal device is caused to initiate the connection recovery attempt by: a new small data transfer procedure is initiated with a connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a count of connection recovery attempts, and the terminal device is further caused to: the count of small data transfer data bearers is updated using an update mode.

In some example embodiments, the indication of the update mode is received by the terminal device in the connected mode in a release message to release the terminal device from the connected mode to the inactive mode.

In some example embodiments, the update mode includes at least one of: a step size for updating a corresponding parameter of the one or more current configuration parameters; an order for updating one or more current configuration parameters; or an identification of one or more current configuration parameters.

In some example embodiments, the terminal device is caused to obtain one or more updated parameters by: receiving an indication from the network device of whether one or more current configuration parameters are allowed to be updated; and in response to the one or more current configuration parameters being allowed to be updated, updating the one or more current configuration parameters based on the update mode to obtain one or more updated parameters.

In some example embodiments, the terminal device is further caused to: an idle mode is entered from an inactive mode in response to one or more current configuration parameters being prohibited from updating.

In some example embodiments, an indication of whether one or more current configuration parameters are allowed to be updated is received in a connection rejection message.

In some example embodiments, the terminal device is further caused to: the idle mode is entered from the inactive mode in response to a number of connection recovery attempts initiated by updating one or more current configuration parameters being above a threshold number.

In some example embodiments, the terminal device is further caused to: an indication of a threshold number is received from a network device.

In some aspects, a network device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the network device to: determining an update mode of one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt; transmitting an indication of an update mode for one or more current configuration parameters to a terminal device; and detecting a connection recovery attempt from the terminal device using the one or more updated parameters generated by updating the one or more parameters based on the update pattern.

In some example embodiments, the network device is caused to detect a connection recovery attempt by: a connection restoration request from the terminal device is detected using the one or more updated parameters.

In some example embodiments, the one or more current configuration parameters include a key of the bearer, and the network device is further caused to: in response to completion of a connection recovery procedure initiated by the terminal device with the connection recovery request, sending to the terminal device an indication of the changed value of the key for the bearer that the one or more current configuration parameters include the key for the bearer, and the network device is further caused to: in response to completion of a connection recovery procedure initiated by the terminal device with the connection recovery request, an indication of the changed value of the carried key is transmitted to the terminal device.

In some example embodiments, the network device is further caused to: an indication is sent to the terminal device whether one or more current configuration parameters are allowed to be updated.

In some example embodiments, an indication of whether one or more current configuration parameters are allowed to be updated is sent in a connection rejection message.

In some example embodiments, the network device is further caused to: an indication of a threshold number of connection recovery attempts initiated by updating one or more current configuration parameters is sent to the terminal device.

In some aspects, a method comprises: obtaining, by a terminal device in an inactive mode, one or more updated parameters by updating one or more current configuration parameters based on an update mode; and initiating, by the terminal device in the inactive mode, a connection recovery attempt using the one or more updated parameters.

In some example embodiments, the method further comprises: an indication of an update mode is received from a network device.

In some example embodiments, initiating a connection recovery attempt using one or more updated parameters includes: generating a connection restoration request using the one or more updated parameters; and initiating a connection recovery attempt with the connection recovery request.

In some example embodiments, initiating the connection recovery attempt includes: a connection recovery procedure is initiated with a connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a key of the bearer, and the method further comprises: an indication of the changed value of the carried key is received from the network device in response to completion of the connection recovery procedure.

In some example embodiments, initiating the connection recovery attempt includes: a new small data transfer procedure is initiated with a connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a count of connection recovery attempts, and the method further comprises: the count of small data transfer data bearers is updated using an update mode.

In some example embodiments, obtaining one or more updated parameters includes: receiving an indication from the network device of whether one or more current configuration parameters are allowed to be updated; and in response to the one or more current configuration parameters being allowed to be updated, updating the one or more current configuration parameters based on the update mode to obtain one or more updated parameters.

In some example embodiments, the method further comprises: an idle mode is entered from an inactive mode in response to one or more current configuration parameters being prohibited from updating.

In some example embodiments, the method further comprises: the idle mode is entered from the inactive mode in response to a number of connection recovery attempts initiated by updating one or more current configuration parameters being above a threshold number.

In some example embodiments, the method further comprises: an indication of a threshold number is received from a network device.

In some aspects, a method comprises: determining, by the network device, an update mode of one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt; transmitting, by the network device, an indication of an update mode for one or more current configuration parameters to the terminal device; and detecting, by the network device, a connection recovery attempt from the terminal device using one or more updated parameters generated by updating the one or more parameters based on the update pattern.

In some example embodiments, detecting a connection recovery attempt includes: a connection restoration request from the terminal device is detected using the one or more updated parameters.

In some example embodiments, the one or more current configuration parameters include a key for the bearer, and the method further comprises: in response to completion of a connection recovery procedure initiated by the terminal device with the connection recovery request, an indication of the changed value of the key for the bearer is sent to the terminal device.

In some example embodiments, the method further comprises: an indication is sent to the terminal device whether one or more current configuration parameters are allowed to be updated.

In some example embodiments, the method further comprises: an indication of a threshold number of connection recovery attempts initiated by updating one or more current configuration parameters is sent to the terminal device.

In some aspects, an apparatus comprises: means for obtaining, by a terminal device in an inactive mode, one or more updated parameters by updating one or more current configuration parameters based on an update mode; and means for initiating, by the terminal device in the inactive mode, a connection recovery attempt using the one or more updated parameters.

In some example embodiments, the apparatus further comprises: means for receiving an indication of an update mode from a network device.

In some example embodiments, the means for initiating a connection recovery attempt using one or more updated parameters comprises: means for generating a connection restoration request using the one or more updated parameters; and means for initiating a connection recovery attempt with the connection recovery request.

In some example embodiments, the means for initiating a connection recovery attempt comprises: means for initiating a connection recovery procedure with the connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a key of the bearer, and the apparatus further comprises: means for receiving an indication of the changed value of the carried key from the network device in response to completion of the connection recovery procedure.

In some example embodiments, the means for initiating a connection recovery attempt comprises: means for initiating a new small data transfer procedure with the connection recovery request to initiate a connection recovery attempt.

In some example embodiments, the one or more current configuration parameters include a count of connection recovery attempts, and the apparatus further comprises: means for updating the count of small data transfer data bearers using the update mode.

In some example embodiments, the means for obtaining one or more updated parameters comprises: means for receiving an indication from the network device of whether one or more current configuration parameters are allowed to be updated; and means for updating the one or more current configuration parameters based on the update mode to obtain one or more updated parameters in response to the one or more current configuration parameters being allowed to be updated.

In some example embodiments, the apparatus further comprises: means for entering an idle mode from an inactive mode in response to one or more current configuration parameters being prohibited from updating.

In some example embodiments, the apparatus further comprises: means for entering an idle mode from an inactive mode in response to a number of connection recovery attempts initiated by updating one or more current configuration parameters being above a threshold number.

In some example embodiments, the apparatus further comprises: means for receiving an indication of a threshold number from a network device.

In some aspects, an apparatus comprises: means for determining an update mode of one or more current configuration parameters to be used by a terminal device in an inactive mode to initiate a connection recovery attempt; means for sending an indication of an update mode for one or more current configuration parameters to the terminal device; and means for detecting a connection recovery attempt from the terminal device using the one or more updated parameters generated by updating the one or more parameters based on the update pattern.

In some example embodiments, the means for detecting a connection recovery attempt comprises: means for detecting a connection recovery request from the terminal device using the one or more updated parameters.

In some example embodiments, the one or more current configuration parameters include a key of the bearer, and the apparatus further comprises: means for sending an indication of the changed value of the key for the bearer to the terminal device in response to completion of a connection recovery procedure initiated by the terminal device with the connection recovery request.

In some example embodiments, the apparatus further comprises: means for sending an indication to the terminal device of whether one or more current configuration parameters are allowed to be updated.

In some example embodiments, the apparatus further comprises: means for sending an indication of a threshold number of connection recovery attempts initiated by updating one or more current configuration parameters to the terminal device.

In some aspects, a computer-readable storage medium includes program instructions stored thereon that, when executed by a processor of a device, cause the device to perform a method according to some example embodiments of the present disclosure.

Claims

1. A terminal device, comprising:

at least one processor; and

At least one memory including computer program code;

The at least one memory and the computer program code are configured to, with the at least one processor, cause the terminal device to:

In the inactive mode, obtaining one or more updated parameters by updating one or more current configuration parameters based on the update mode; and

In the inactive mode, a connection recovery attempt is initiated using the one or more updated parameters.

2. A terminal device according to claim 1, wherein the terminal device is further caused to:

An indication of the update mode is received from a network device.

3. The terminal device of claim 1 or 2, wherein the one or more updated parameters are obtained in response to at least one of:

Arrival of non-small data transfer data during a small data transfer process;

cell reselection during the small data transmission procedure;

refusing the small data transmission process;

expiration of the small data transmission failure timer; or (b)

The radio link control entity reaches the configured maximum number of retransmissions.

4. A terminal device according to any of claims 1 to 3, wherein the terminal device is caused to initiate the connection recovery attempt using the one or more updated parameters by:

generating a connection restoration request using the one or more updated parameters; and

The connection recovery attempt is initiated with the connection recovery request.

5. The terminal device of claim 4, wherein the connection recovery request comprises: resumeMAC-I generated based on the one or more updated parameters.

6. A terminal device according to claim 4 or 5, wherein the terminal device is caused to initiate the connection recovery attempt by:

A connection recovery procedure is initiated with the connection recovery request to initiate the connection recovery attempt.

7. The terminal device of claim 6, wherein the one or more current configuration parameters include a key of a bearer, and the terminal device is further caused to:

An indication of the changed value of the key of the bearer is received from the network device in response to completion of the connection recovery procedure.

8. A terminal device according to claim 4 or 5, wherein the terminal device is caused to initiate the connection recovery attempt by:

A new small data transfer process is initiated with the connection recovery request to initiate the connection recovery attempt.

9. The terminal device of claim 8, wherein the one or more current configuration parameters include a count of the connection recovery attempts, and the terminal device is further caused to:

the update mode is used to update the count of small data transfer data bearers.

10. The terminal device according to any of claims 1 to 9, wherein the indication of the update mode is received by the terminal device in a connected mode in a release message to release the terminal device from the connected mode to the inactive mode.

11. The terminal device according to any of claims 1 to 10, wherein the update mode comprises at least one of:

a step size for updating a corresponding parameter of the one or more current configuration parameters;

an order for updating the one or more current configuration parameters; or (b)

An identification of the one or more current configuration parameters.

12. A terminal device according to any of claims 1 to 11, wherein the terminal device is caused to obtain the one or more updated parameters by:

receiving an indication from the network device of whether the one or more current configuration parameters are allowed to be updated; and

In response to the one or more current configuration parameters being allowed to be updated, the one or more current configuration parameters are updated based on the update mode to obtain the one or more updated parameters.

13. A terminal device according to claim 12, wherein the terminal device is further caused to:

an idle mode is entered from the inactive mode in response to the one or more current configuration parameters being prohibited from updating.

14. The terminal device according to claim 12 or 13, wherein the indication of whether the one or more current configuration parameters are allowed to be updated is received in a connection rejection message.

15. The terminal device of any of claims 1 to 14, wherein the terminal device is further caused to:

an idle mode is entered from the inactive mode in response to a number of connection recovery attempts initiated by updating the one or more current configuration parameters being above a threshold number.

16. The terminal device of claim 15, wherein the terminal device is further caused to:

the threshold number of indications are received from the network device.

17. A network device, comprising:

at least one processor; and

At least one memory including computer program code;

The at least one memory and the computer program code are configured to, with the at least one processor, cause the network device to:

Determining an update mode for one or more current configuration parameters to be used by a terminal device in an inactive mode to initiate a connection recovery attempt;

Transmitting an indication of the update mode for the one or more current configuration parameters to the terminal device; and

The connection recovery attempt from the terminal device is detected using one or more updated parameters generated by updating the one or more parameters based on the update pattern.

18. The network device of claim 17, wherein the network device is caused to detect the connection recovery attempt by:

A connection restoration request from the terminal device is detected using the one or more updated parameters.

19. The network device of claim 18, wherein the connection recovery request comprises: resumeMAC-I generated based on the one or more updated parameters.

20. The network device of claim 18 or 19, wherein the one or more current configuration parameters include a key of a bearer, and the network device is further caused to:

An indication of the changed value of the key for the bearer is sent to the terminal device in response to completion of a connection recovery procedure initiated by the terminal device with the connection recovery request.

21. The network device of any of claims 17 to 20, wherein the update mode comprises at least one of:

an order for updating the one or more current configuration parameters; or (b)

An identification of the one or more current configuration parameters.

22. The network device of any of claims 17 to 21, wherein the network device is further caused to:

and sending an indication to the terminal device of whether the one or more current configuration parameters are allowed to be updated.

23. The network device of claim 22, wherein the indication of whether the one or more current configuration parameters are allowed to be updated is sent in a connection rejection message.

24. The network device of any of claims 17 to 23, wherein the network device is further caused to:

An indication of a threshold number of connection recovery attempts initiated by updating the one or more current configuration parameters is sent to the terminal device.

25. A method, comprising:

Obtaining, by a terminal device in an inactive mode, one or more updated parameters by updating one or more current configuration parameters based on an update mode; and

A connection recovery attempt is initiated by the terminal device in the inactive mode using the one or more updated parameters.

26. The method of claim 25, further comprising:

An indication of the update mode is received from a network device.

27. The method of claim 25 or 26, wherein the one or more updated parameters are obtained in response to at least one of:

Arrival of non-small data transfer data during a small data transfer process;

cell reselection during the small data transmission procedure;

refusing the small data transmission process;

expiration of the small data transmission failure timer; or (b)

28. The method of any of claims 25-27, wherein using the one or more updated parameters to initiate the connection recovery attempt comprises:

29. The method of claim 28, wherein the connection recovery request includes: resumeMAC-I generated based on the one or more updated parameters.

30. The method of claim 28 or 29, wherein initiating the connection recovery attempt comprises:

31. The method of claim 30, wherein the one or more current configuration parameters include a key of a bearer, and the method further comprises:

32. The method of claim 28 or 29, wherein initiating the connection recovery attempt comprises:

33. The method of claim 32, wherein the one or more current configuration parameters include a count of the connection recovery attempts, and the method further comprises:

34. A method according to any of claims 26 to 33, wherein the indication of the update mode is received by the terminal device in a connected mode in a release message to release the terminal device from the connected mode to the inactive mode.

35. The method of any of claims 26 to 34, wherein the update pattern comprises at least one of:

an order for updating the one or more current configuration parameters; or (b)

An identification of the one or more current configuration parameters.

36. The method of any one of claims 26-35, wherein obtaining the one or more updated parameters comprises:

37. The method of claim 36, further comprising:

38. The method of claim 36 or 37, wherein the indication of whether the one or more current configuration parameters are allowed to be updated is received in a connection rejection message.

39. The method of any of claims 26 to 38, further comprising:

40. The method of claim 39, further comprising:

the threshold number of indications are received from the network device.

41. A method, comprising:

determining, by the network device, an update mode of one or more current configuration parameters to be used by the terminal device in an inactive mode to initiate a connection recovery attempt;

transmitting, by the network device, an indication of the update mode for the one or more current configuration parameters to the terminal device; and

The connection recovery attempt from the terminal device is detected by the network device using one or more updated parameters generated by updating the one or more parameters based on the update pattern.

42. The method of claim 41, wherein detecting the connection recovery attempt comprises:

43. The method of claim 42, wherein the connection recovery request includes: resumeMAC-I generated based on the one or more updated parameters.

44. The method of claim 42 or 43, wherein the one or more current configuration parameters include a key for a bearer, and the method further comprises:

45. The method of any of claims 41 to 44, wherein the update pattern comprises at least one of:

an order for updating the one or more current configuration parameters; or (b)

An identification of the one or more current configuration parameters.

46. The method of any one of claims 41 to 45, further comprising:

47. The method of claim 46, wherein the indication of whether the one or more current configuration parameters are allowed to be updated is sent in a connection rejection message.

48. The method of any one of claims 41 to 47, further comprising:

An indication of a threshold number of connection recovery attempts initiated by updating the one or more current configuration parameters is transmitted to the terminal device.

49. An apparatus, comprising:

means for obtaining one or more updated parameters by updating one or more current configuration parameters based on the update mode in the inactive mode; and

Means for initiating a connection recovery attempt using the one or more updated parameters in the inactive mode.

50. An apparatus, comprising:

Means for determining an update mode for one or more current configuration parameters to be used by a terminal device in an inactive mode to initiate a connection recovery attempt;

means for sending an indication of the update mode for the one or more current configuration parameters to the terminal device; and

Means for detecting the connection recovery attempt from the terminal device using one or more updated parameters generated by updating the one or more parameters based on the update pattern.

51. A computer readable storage medium comprising program instructions stored thereon, which when executed by a processor of a device, cause the device to perform the method of any of claims 25 to 40.

52. A computer readable storage medium comprising program instructions stored thereon, which when executed by a processor of a device, cause the device to perform the method of any of claims 41 to 48.