CN114679919B

CN114679919B - Configuration method and device

Info

Publication number: CN114679919B
Application number: CN202080062554.8A
Authority: CN
Inventors: 徐小英; 曾清海; 戴明增; 黄曲芳; 娄崇; 陈雁
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-09-30
Filing date: 2020-02-14
Publication date: 2024-05-03
Anticipated expiration: 2040-02-14
Also published as: US20220225465A1; EP4030809A1; WO2021062974A1; EP4030809A4; CN114679919A; WO2021062797A1

Abstract

The embodiment of the application provides a configuration method and a configuration device, wherein network equipment can carry configuration parameters distributed for a terminal in an inactive state in RRC connection release information when the terminal is indicated to enter the inactive state from the connection state through the RRC connection release information, namely the terminal receives Radio Resource Control (RRC) connection release information sent by the network equipment, and the RRC connection release information comprises first information for indicating target configuration parameters; therefore, the terminal can enter the inactive state according to the RRC connection release message, and the context parameters of the inactive state are determined according to the first information, wherein the context parameters of the inactive state comprise target configuration parameters, or the context parameters of the inactive state comprise parameters except the target configuration parameters in the context parameters of the terminal, and the target configuration parameters are configuration parameters suitable for the terminal in the inactive state, so that the configuration parameters are reasonably distributed for the terminal in the inactive state.

Description

Configuration method and device

The present application claims priority from international patent application filed in China patent office, application number PCT/CN2019/109722, application name "configuration method and apparatus", 30, 09, 2019, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a configuration method and apparatus.

Background

In an LTE network, from the perspective of an access network, the states of a terminal can be divided into three states, namely a connected (connected) state, an inactive (inactive) state, and an idle (idle) state. The connection state is a state that the terminal completes connection establishment between the access network equipment and the core network equipment through the processes of radio resource control (radio resource control, RRC) connection establishment, RRC connection reestablishment, RRC connection recovery and the like; the inactive state is a state in which the terminal is disconnected from the access network device, but the access network device remains connected to the core network device, and the access network device saves the context of the terminal (for example, the identifier of the terminal); the idle state is a state in which the terminal disconnects from the access network device and the core network device, and the access network device releases the context of the terminal.

For a terminal in a connection state, the network device sends configuration information for the terminal in the connection state, so that the terminal configures according to the configuration information, and the terminal performs data transmission based on the configuration. And if the network equipment detects that the terminal has no data transmission for a long time, the network equipment sends an RRC connection release message to the terminal so as to indicate the terminal to enter an inactive state from a connected state through the RRC connection release message. After the terminal enters the inactive state, the configuration information received when the terminal is in the connected state is no longer suitable for the terminal which is currently in the inactive state.

Therefore, how to reasonably indicate configuration parameters for the terminal in the inactive state is a problem to be solved by those skilled in the art.

Disclosure of Invention

The embodiment of the application provides a configuration method and a configuration device, which realize that configuration parameters are reasonably indicated for a terminal in an inactive state after the terminal enters the inactive state from a connection state.

In a first aspect, an embodiment of the present application provides a configuration method, where the configuration method may include: receiving a Radio Resource Control (RRC) connection release message, wherein the RRC connection release message comprises first information, and the first information is used for indicating target configuration parameters; and entering a non-activated state according to the RRC connection release message, and determining a non-activated state context parameter according to the first information, wherein the non-activated state context parameter comprises a target configuration parameter, or the non-activated state context parameter comprises a parameter except the target configuration parameter in the terminal context parameter.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above first aspect.

Furthermore, a configuration device is provided comprising a processor and an interface circuit, the processor being arranged to communicate with other devices via the interface circuit and to perform the method provided in the first aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for being connected to a memory, for invoking a program stored in said memory for performing the method according to the first aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor for performing the method provided in the first aspect above and at least one memory.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above first aspect.

Furthermore, a computer readable storage medium storing a program is provided, which when called by a processor, performs the method of the above first aspect.

Furthermore, a program product, such as a computer-readable storage medium, is provided, including the above program.

It can be seen that, in the first aspect, while the network device indicates, through the RRC connection release message, that the terminal enters the inactive state from the connected state, the configuration parameter allocated to the terminal in the inactive state may be carried in the RRC connection release message, that is, the terminal receives a radio resource control RRC connection release message sent by the network device, where the RRC connection release message includes first information for indicating the target configuration parameter; therefore, the terminal can enter the inactive state according to the RRC connection release message, and the access layer context parameters of the inactive state are determined according to the first information, wherein the access layer context parameters of the inactive state comprise target configuration parameters, or the context parameters of the inactive state comprise parameters except the target configuration parameters in the context parameters of the terminal, so that the configuration parameters are reasonably indicated for the terminal in the inactive state.

It can be understood that in the embodiment of the present application, when the network device indicates the configuration parameters for the inactive terminal reasonably through the first information, the network device may be divided into two different scenarios. In one scenario, the network device may indicate, through the first information, configuration parameters configured for the terminal in the inactive state, so that the terminal retains the configuration parameters configured for it. In another scenario, the network device may indicate, through the first information, a configuration parameter that needs to be released by the terminal in the inactive state, so that the terminal in the inactive state releases the configuration parameter that needs to be released. In these two different scenarios, the target configuration parameters indicated by the first information are different.

In the first aspect, in a possible implementation manner, the target configuration parameters include: the network device performs curing treatment on the radio bearer configuration parameters of the plurality of terminals and/or the cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, when the plurality of terminals enter a non-activated state from a connected state, for the network device, only one set of configuration information is needed to be stored when the configuration information of the at least two terminals is stored, thereby reducing the storage cost of the network device.

In an implementation manner of the first aspect, the first information is an identifier corresponding to the target configuration parameter.

In an implementation manner of the first aspect, the terminal stores the identifier corresponding to the configuration parameter and the mapping relation of the configuration parameter, so that the terminal may determine, according to the identifier corresponding to the target configuration parameter and the mapping relation, that the inactive context parameter includes the identifier corresponding to the target configuration parameter, thereby retaining or releasing the target configuration parameter.

In the first aspect, in one possible implementation manner, the first information includes the target configuration parameter, and since the RRC connection release message directly carries the target configuration parameter, the terminal may directly determine the target configuration parameter, and retain or release the target configuration parameter directly carried in the RRC connection release message, although the configuration signaling overhead is greater when the target configuration parameter is carried in the RRC connection release message and sent to the terminal, it is not necessary for the terminal to define the context configuration information in the protocol in advance, thereby reducing the complexity of the protocol, and the terminal does not need to store the pre-configuration in advance, and reducing the configuration overhead of the storage overhead of the terminal.

In the first aspect, in one possible implementation manner, the configuration method further includes: and reporting the non-activated capacity information of the terminal so that the network equipment determines whether the terminal supports data transmission in the non-activated state according to the capacity information reported by the terminal.

For example, when the terminal reports its capability information, the terminal may report its capability information to the network device in at least four possible manners. Taking the example that the terminal supports data transmission in the inactive state, the four possible modes are respectively: the terminal can support data transmission in an inactive state, the terminal supports the configuration of the context parameters of the terminal through the pre-configuration identification, the terminal supports the common parameter configuration in the inactive state (in other words, the terminal supports the lightweight access layer configuration parameters), and the terminal supports the session of data transmission in a direct inactive state. Although the expression modes are different, the terminal can be indicated to support data transmission in the inactive state through the four different modes.

In an implementation manner of the first aspect, a first indication is received, where the first indication is used to instruct the terminal to monitor the physical downlink control channel when the terminal is in an inactive state.

In the foregoing first aspect, in one possible implementation manner, the first indication information is included in an RRC release message, and of course, the first indication information may also be carried in other messages, and may specifically be set according to actual needs.

In an implementation manner of the foregoing first aspect, the terminal may further receive a second indication, where the second indication is used to indicate that the terminal is allowed to perform uplink transmission when the terminal is in an inactive state.

In the first aspect, in a possible implementation manner, the terminal may send a random access request; and receiving a response message of the random access request, wherein the response message comprises an uplink grant and a second indication, and the second indication is used for indicating that uplink transmission is allowed on the uplink grant when the terminal is in a non-activated state, so that when the terminal needs to transmit data, the terminal can directly transmit the uplink on an uplink resource indicated by the uplink grant, the terminal can complete uplink transmission when the terminal is in the non-activated state, and the terminal can transmit the uplink without waiting until the RRC connection is restored, thereby preventing the terminal from entering a connection state to transmit data, not only improving the data transmission efficiency, but also reducing the cost required by RRC connection restoration.

In a second aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: determining a target configuration parameter; and transmitting a Radio Resource Control (RRC) connection release message, wherein the RRC connection release message comprises first information, the first information is used for indicating a target configuration parameter, the RRC connection release message is used for indicating the terminal to enter an inactive state according to the RRC connection release message, the first information is used for indicating the terminal to determine the context parameter of the inactive state, and the context parameter of the inactive state comprises the target configuration parameter, or the context parameter of the inactive state comprises parameters except the target configuration parameter in the context parameter of the terminal.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above second aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being arranged to communicate with other devices via the interface circuit and to perform the method provided in the second aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for interfacing with a memory, for invoking a program stored in said memory for performing the method according to the above second aspect. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor for performing the method provided in the second aspect above and at least one memory.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above second aspect.

Further, a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above second aspect is provided.

It can be seen that, in the second aspect, the network device may carry, while indicating, by the RRC connection release message, that the terminal enters the inactive state from the connected state, a configuration parameter allocated to the terminal in the inactive state, that is, the terminal receives a radio resource control RRC connection release message sent by the network device, where the RRC connection release message includes first information for indicating a target configuration parameter; therefore, the terminal can enter the inactive state according to the RRC connection release message, and the context parameters of the inactive state are determined according to the first information, wherein the context parameters of the inactive state comprise the target configuration parameters, or the context parameters of the inactive state comprise parameters except the target configuration parameters in the context parameters of the terminal, so that the configuration parameters are reasonably indicated for the terminal in the inactive state.

In the second aspect, in one possible implementation manner, the target configuration parameters include: the network device performs curing treatment on the radio bearer configuration parameters of the plurality of terminals and/or the cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, when the plurality of terminals enter a non-activated state from a connected state, for the network device, only one set of configuration information is needed to be stored when the configuration information of the at least two terminals is stored, thereby reducing the storage cost of the network device.

In the second aspect, in one possible implementation manner, the first information is an identifier corresponding to the target configuration parameter.

In the second aspect, in one possible implementation manner, the mapping relationship between the identifier corresponding to the configuration parameter and the configuration parameter is sent, so that the terminal may determine, according to the identifier corresponding to the target configuration parameter and the mapping relationship, that the context parameter in the inactive state includes the identifier corresponding to the target configuration parameter, thereby retaining or releasing the target configuration parameter.

In the second aspect, in one possible implementation manner, the first information includes the target configuration parameter, and since the RRC connection release message directly carries the target configuration parameter, the terminal may directly determine the target configuration parameter and reserve or release the target configuration parameter, while carrying the target configuration parameter in the RRC connection release message and sending the target configuration parameter to the terminal may cause the configuration signaling overhead to be large, it is not necessary for the terminal to define the context configuration information in the protocol in advance, thereby reducing the complexity of the protocol, and the terminal does not need to store the pre-configuration in advance, so as to reduce the configuration overhead of the storage overhead of the terminal.

In the second aspect, in one possible implementation manner, a session establishment request from a core network device is received, where the session establishment request includes a session type, and the session type is used to instruct the terminal to allow uplink transmission when the terminal is in an inactive state; and determining the target configuration parameters based on the session type, and sending the determined target configuration parameters to the terminal.

In the second aspect, in a possible implementation manner, the network device further sends a session establishment response to the core network device.

In the second aspect, in one possible implementation manner, a first indication is sent, where the first indication is used to instruct the terminal to monitor a physical downlink control channel when the terminal is in an inactive state.

In the second aspect, in one possible implementation manner, the first indication information is included in the RRC release message, and of course, the first indication information may also be carried in other messages, and may specifically be set according to actual needs.

In the second aspect, in one possible implementation manner, a second indication is sent, where the second indication is used to indicate that the terminal is allowed to perform uplink transmission when in an inactive state.

In the second aspect, in one possible implementation manner, the network device may receive a random access request; and sending a response message of the random access request, wherein the response message comprises an uplink grant and a second indication, and the second indication is used for indicating that uplink transmission is allowed on the uplink grant when the terminal is in a non-activated state, so that when the terminal needs to transmit data, the terminal can directly perform uplink transmission on uplink resources indicated by the uplink grant, the terminal can complete uplink transmission when the terminal is in the non-activated state, and the terminal can perform uplink transmission without waiting until the RRC connection is restored, so that the terminal is prevented from entering a connection state to transmit data, the data transmission efficiency is improved, and the cost required by RRC connection restoration is reduced.

In a third aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include:

Transmitting a first message to the network device, the first message including a random access request and/or physical uplink shared channel data, the physical uplink shared channel data including information for requesting recovery of the RRC connection; and receiving a response message of the first message from the network device, the response message including contention resolution information; receiving an uplink grant from a network device; and then carrying out uplink transmission on the uplink resources indicated by the uplink authorization.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above third aspect.

Furthermore, a configuration device is provided comprising a processor and an interface circuit, the processor being arranged to communicate with other devices via the interface circuit and to perform the method provided in the third aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for interfacing with a memory, for invoking a program stored in said memory for performing the method as described in the third aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor for performing the method provided in the third aspect above and at least one memory.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above third aspect.

Furthermore, a computer-readable storage medium storing a program which, when called by a processor, performs the method of the above third aspect is provided.

In the third aspect, after the terminal receives the contention resolution information, if the terminal has not received the RRC connection release message at this time, it indicates that there is data to be transmitted, the terminal receives an uplink grant from the network device, and performs uplink transmission on an uplink resource indicated by the uplink grant, without waiting until the RRC connection is restored, and without the terminal entering a connected state to transmit data, thereby not only improving data transmission efficiency, but also reducing overhead required for RRC connection restoration.

In the third aspect, in one possible implementation manner, the timer is started or restarted when the response message of the first message is received, so as to delay the duration of the terminal monitoring for authorization.

In the third aspect, in one possible implementation manner, during running of the timer, an uplink grant is received from the network device; and restarting the timer when the uplink grant is received, thereby delaying the duration of the terminal monitoring the uplink grant.

In the third aspect, in one possible implementation manner, during running of the timer, a downlink grant is received from the network device; and restarting the timer when the downlink grant is received, thereby delaying the duration of the terminal monitoring the downlink grant.

In the third aspect described above, in one possible implementation manner, the timer is not always in an operating state after being started or restarted, but is stopped under a condition that is satisfied, for example, in the scenario of stopping the timer described above. For example, when the terminal receives the RRC connection release message from the network device, the control timer stops running, i.e., the timer is stopped. It will be appreciated that the terminal may also stop the timer when it receives an RRC connection resume, connection setup message, etc. from the network device.

In a fourth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: receiving a first message from a terminal, wherein the first message comprises a random access request and/or physical uplink shared channel data, and the physical uplink shared channel data comprises information for requesting to recover the RRC connection; and sending a response message of the first message to the terminal, the response message including contention resolution information; sending an uplink authorization to the terminal; and carrying out data transmission on the uplink resources indicated by the uplink authorization.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above fourth aspect.

Furthermore, there is provided a configuration device comprising a processor and an interface circuit, the processor being arranged to communicate with other devices via the interface circuit and to perform the method provided in the fourth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for interfacing with a memory, for invoking a program stored in said memory for performing the method according to the fourth aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor for performing the method provided in the fourth aspect above and at least one memory.

Furthermore, a computer program is provided which, when being executed by a processor, is adapted to carry out the method of the fourth aspect above.

Further, a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above fourth aspect is provided.

In the fourth aspect, it can be seen that, after receiving the first message sent by the terminal, the network device sends a response message including contention resolution information to the terminal, and if no RRC connection release message is sent to the terminal at this time, which indicates that there is any data to be transmitted, then sends uplink grant to the terminal, so that the terminal performs uplink transmission on the uplink resource indicated by the uplink grant, without waiting until RRC connection is restored, and without the terminal entering a connection state to send data, thereby not only improving data sending efficiency, but also reducing the overhead required for RRC connection restoration.

In the fourth aspect, in one possible implementation manner, the network device further sends a radio resource control RRC connection release message to the terminal, so that when the terminal receives the radio resource control RRC connection release message from the network device, the control timer stops running, i.e. the timer stops. It will be appreciated that the terminal may also stop the timer when it receives a radio resource control RRC connection resume, connection setup message, etc. from the network device.

In a fifth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: transmitting a first message to the network device, the first message including a random access request and/or physical uplink shared channel data, the physical uplink shared channel data including information for requesting recovery of a Radio Resource Control (RRC) connection; receiving a response message of the first message from the network equipment, wherein the response message comprises uplink authorization and first indication information, and the first indication information is used for indicating whether uplink transmission is allowed on uplink resources indicated by the uplink authorization; and carrying out uplink transmission on the uplink resource according to the first indication information.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above fifth aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being for communicating with other devices via the interface circuit and performing the method provided in the fifth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for interfacing with a memory, for invoking a program stored in said memory for performing the method of the fifth aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor for performing the method provided in the fifth aspect above and at least one memory.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above fifth aspect.

Further, there is provided a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above fifth aspect.

In the fifth aspect, the terminal sends the RRC connection recovery request to the network device, so that the network device can allocate uplink authorization to the terminal when the terminal is in an inactive state, and indicate whether to allow uplink transmission on an uplink resource indicated by the uplink authorization through the indication information, so that the terminal completes uplink transmission in the inactive state, and can perform uplink transmission without waiting until RRC connection is recovered, and without the terminal entering a connection state to send data, thereby not only improving data sending efficiency, but also reducing overhead required by RRC connection recovery.

In a possible implementation manner of the fifth aspect, if the first indication information indicates that uplink transmission is allowed on the uplink resource, the second message including the uplink data is sent to the network device on the uplink resource, so that the terminal completes uplink transmission in the inactive state, and the terminal does not need to wait until the RRC connection is restored, and then can perform uplink transmission, and the terminal does not need to enter the connected state to send data, thereby not only improving the data sending efficiency, but also reducing the overhead required for RRC connection restoration.

In the fifth aspect, in one possible implementation manner, if the first indication information indicates that uplink transmission is not allowed on the uplink resource, a third message is sent to the network device on the uplink resource, where the third message is used to request to restore the RRC connection.

It should be noted that, when the first indication information indicates that the terminal does not allow uplink transmission on the uplink resource indicated by the uplink grant, the third message sent by the terminal on the uplink resource indicated by the uplink grant is only used to request to restore the RRC connection, and does not include uplink data. For example, the third message may be an RRC connection resume request.

In a possible implementation manner of the fifth aspect, the terminal starts or restarts the timer when receiving the response message of the first message, so as to delay the duration of the terminal listening for the authorization.

In a possible implementation manner of the fifth aspect, during running of the timer, the authorization is received from the network device; and restarting the timer when the authorization is received, thereby delaying the duration of the terminal monitoring the authorization.

In the fifth aspect described above, in one possible implementation manner, the timer is not always in an operating state after being started or restarted, but is stopped under a condition that is satisfied, for example, the scenario of stopping the timer described above. For example, when the terminal receives the RRC connection release message from the network device, the control timer stops running, i.e., the timer is stopped. It will be appreciated that the terminal may also stop the timer when it receives a radio resource control RRC connection resume, connection setup message, etc. from the network device.

In the fifth aspect described above, in one possible implementation manner, the response message includes contention resolution information. For example, the contention resolution information may be an identification of the terminal, or partial information of the second message, or partial information of the third message.

After receiving the contention resolution information, if the terminal does not receive the RRC connection release message at the moment, the terminal starts or restarts a timer, and receives authorization from the network device during the running of the timer; the grant may be an uplink grant or a downlink grant, and when the grant is received, the timer is restarted, thereby delaying the duration of the terminal listening for the grant. For example, if the uplink grant is received from the network device, the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink grant; if the downlink grant is received from the network device and the RRC connection release message is not received, which indicates that the data needs to be transmitted, the terminal starts or restarts the timer and waits for the time of the RRC connection release message, so that the terminal completes uplink transmission in an inactive state without waiting until the RRC connection is restored, and the terminal does not need to enter a connection state to transmit the data, thereby improving the data transmission efficiency and reducing the cost required by the RRC connection restoration.

In a possible implementation manner of the fifth aspect, the first message further includes second indication information, where the second indication information is used to indicate a comparison result of the data volume to be sent by the terminal and the data volume threshold.

In a sixth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: receiving a first message from a terminal, wherein the first message comprises a random access request and/or physical uplink shared channel data, and the physical uplink shared channel data comprises information for requesting to recover a Radio Resource Control (RRC) connection; and sending a response message of the first message to the terminal, wherein the response message comprises uplink authorization and first indication information, and the first indication information is used for indicating whether uplink transmission is allowed on uplink resources indicated by the uplink authorization; and carrying out uplink transmission on the uplink resource according to the first indication information.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above sixth aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being for communicating with other devices via the interface circuit and performing the method provided in the sixth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for being connected to a memory, for invoking a program stored in said memory for performing the method according to the sixth aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor and at least one memory, the at least one processor being adapted to perform the method provided in the sixth aspect above.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above sixth aspect.

Further, there is provided a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above sixth aspect.

In the sixth aspect, the network device allocates uplink grant to the terminal when the terminal is in the inactive state by receiving the RRC connection restoration request sent by the terminal, and indicates whether to allow uplink transmission on the uplink resource indicated by the uplink grant by the indication information, so that the terminal completes uplink transmission in the inactive state, and does not need to wait until RRC connection is restored, and does not need to enter a connection state to send data, thereby not only improving data sending efficiency, but also reducing overhead required by RRC connection restoration.

In the sixth aspect, in one possible implementation manner, if the first indication information indicates that uplink transmission is allowed on the uplink resource, the second message including the uplink data is received from the terminal on the uplink resource, so that the terminal completes uplink transmission in the inactive state, and does not need to wait until the RRC connection is restored, and does not need to enter the connected state to send data, thereby not only improving the sending efficiency of the data, but also reducing the overhead required for RRC connection restoration.

In the sixth aspect, in one possible implementation manner, if the first indication information indicates that uplink transmission is not allowed on the uplink resource, a third message is received from the terminal on the uplink resource, where the third message is used to request to restore the RRC connection.

It should be noted that, when the first indication information indicates that the terminal does not allow uplink transmission on the uplink resource indicated by the uplink grant, the third message received by the network device on the uplink resource indicated by the uplink grant is only used to request to restore the RRC connection, and does not include uplink data. For example, the third message may be an RRC connection resume request.

In a possible implementation manner of the sixth aspect described above, the radio resource control RRC connection release message is sent to the terminal, so that when the terminal receives the RRC connection release message from the network device, the control timer stops running, i.e. the timer is stopped. It will be appreciated that the terminal may also stop the timer when it receives a radio resource control RRC connection resume, connection setup message, etc. from the network device.

In the sixth aspect, in one possible implementation manner, the response message includes contention resolution information. For example, the contention resolution information may be an identification of the terminal, or partial information of the second message, or partial information of the third message.

In a possible implementation manner of the sixth aspect, the first message further includes second indication information, where the second indication information is used to indicate a comparison result of the data volume to be sent by the terminal and the data volume threshold.

In a seventh aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: receiving indication information, wherein the indication information is used for indicating a terminal to monitor a physical downlink control channel PDCCH scrambled by a cell radio network temporary identifier C-RNTI when the terminal is in a non-activated state; and monitoring the PDCCH scrambled by the C-RNTI according to the indication information.

Further, a configuration apparatus is provided, comprising means for performing the steps of the above seventh aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being for communicating with other devices via the interface circuit and performing the method provided in the seventh aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for being connected to a memory, for invoking a program stored in said memory for performing the method according to the seventh aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor and at least one memory, the at least one processor being adapted to perform the method provided in the seventh aspect above.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the seventh aspect above.

Further, a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above seventh aspect is provided.

It can be seen that, in the seventh aspect, the terminal receives the indication information sent by the network device, where the indication information indicates that the terminal monitors the PDCCH scrambled by the C-RNTI in the inactive state, and receives the downlink data in the process of monitoring the PDCCH scrambled by the C-RNTI, and the whole receiving process does not need to receive paging or initiate an RRC connection recovery request for the terminal, but directly receives the downlink data in the inactive state, which not only improves transmission efficiency, but also reduces overhead of the terminal.

In a possible implementation manner of the seventh aspect, the terminal may receive a radio resource control RRC connection release message, where the RRC connection release message includes indication information, so as to obtain the indication information. It will be appreciated that the indication information may also be carried in a broadcast message.

For example, the indication information may be implemented by a bit, for example, the bit has a value of 1, which indicates that a function of listening to a Physical Downlink Control Channel (PDCCH) scrambled by the C-RNTI is enabled in the inactive state, and the bit has a value of 0, which indicates that a function of listening to a Physical Downlink Control Channel (PDCCH) scrambled by the C-RNTI is not enabled in the inactive state. Alternatively, the indication information may be implemented by enumeration, for example: { TURE }, { downlink reception }. Since the PDCCH is scrambled by a cell radio network temporary identity (C-RNTI), in another implementation, the indication information may be a C-RNTI, for example, when the RRC connection release message carries the C-RNTI, the terminal is instructed to monitor the C-RNTI scrambled PDCCH in an inactive state; and when the RRC connection release message does not carry the C-RNTI, the terminal is indicated not to monitor the PDCCH in the inactive state.

In the seventh aspect, in a possible implementation manner, the terminal listens to the PDCCH scrambled by the C-RNTI may include: and determining paging occasion, and monitoring the PDCCH scrambled by the C-RNTI in a part of time slots or part of paging frames of the paging occasion, so that the terminal does not need to receive paging and initiate an RRC connection recovery request, and directly receives downlink data in an inactive state, thereby improving transmission efficiency and reducing the cost of the terminal.

In the seventh aspect, in a possible implementation manner, the terminal listens to the PDCCH scrambled by the C-RNTI may include: receiving the first parameter, and determining paging occasion according to the first parameter; and receiving the second parameter, and determining the opportunity to monitor the PDCCH scrambled by the C-RNTI according to the second parameter, wherein the paging opportunity is different from the opportunity to monitor the PDCCH scrambled by the C-RNTI, so that the terminal does not need to receive paging and initiate an RRC connection recovery request, but directly receives downlink data in an inactive state, thereby not only improving the transmission efficiency, but also reducing the cost of the terminal.

In the seventh aspect, in one possible implementation manner, when the terminal moves out of the valid area of the C-RNTI, monitoring of the PDCCH scrambled by the C-RNTI is stopped, thereby reducing power consumption of the terminal.

In an eighth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: determining a physical downlink control channel PDCCH scrambled by a cell radio network temporary identifier C-RNTI when a terminal can monitor in an inactive state; and sending indication information to the terminal, wherein the indication information is used for indicating the terminal to monitor a physical downlink control channel PDCCH scrambled by a cell radio network temporary identifier C-RNTI when the terminal is in an inactive state.

Further, a configuration device is provided, comprising means for performing the steps of the above eighth aspect.

Furthermore, there is provided a configuration device comprising a processor and an interface circuit, the processor being arranged to communicate with other devices via the interface circuit and to perform the method provided in the eighth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for connecting to a memory, for invoking a program stored in said memory for performing the method according to the above eighth aspect. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor and at least one memory, the at least one processor being adapted to perform the method provided in the eighth aspect above.

Furthermore, a computer program is provided which, when being executed by a processor, is adapted to carry out the method of the above eighth aspect.

Further, a computer-readable storage medium storing a program which, when called by a processor, performs the method of the above eighth aspect is provided.

In the embodiment of the application, the network equipment sends the indication information to the terminal to indicate the terminal to monitor the PDCCH scrambled by the C-RNTI when the terminal is in the inactive state, so that the terminal can receive downlink data in the process of monitoring the PDCCH scrambled by the C-RNTI.

In an eighth aspect of the foregoing disclosure, in one possible implementation manner, the network device may send a radio resource control RRC connection release message to the terminal, where the RRC connection release message includes indication information, so that the terminal obtains the indication information. It will be appreciated that the indication information may also be carried in a broadcast message.

In the eighth aspect, in one possible implementation manner, the network device may send a first parameter to the terminal, where the first parameter is used by the terminal to determine the paging occasion according to the first parameter; and sending a second parameter to the terminal, wherein the second parameter is used for determining the opportunity of monitoring the PDCCH scrambled by the C-RNTI according to the second parameter, and the paging opportunity is different from the opportunity of monitoring the PDCCH scrambled by the C-RNTI, so that the terminal does not need to receive paging, initiate RRC connection recovery request and directly receive downlink data in an inactive state, thereby improving the transmission efficiency and reducing the cost of the terminal.

In a ninth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: the terminal starts a first timer according to the requirement of Radio Resource Control (RRC) connection recovery, and sends an RRC connection recovery request message to the network equipment; the terminal restarts the first timer or starts the second timer during operation of the first timer according to downlink information received from the network device or according to data transmission with the network device.

Further, there is provided a configuration apparatus comprising means for performing the steps of the above ninth aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being for communicating with other devices via the interface circuit and performing the method provided in the ninth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for being connected to a memory, for invoking a program stored in said memory for performing the method according to the ninth aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor and at least one memory, the at least one processor being adapted to perform the method provided in the ninth aspect above.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the above ninth aspect.

Further, there is provided a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above ninth aspect.

It can be seen that in the ninth aspect, the terminal restarts the first timer or starts the second timer according to the downlink information received from the network device or performs data transmission with the terminal, so that the terminal can perform data transmission during the operation of the first timer or the second timer, and the time of the terminal waiting for the RRC response message of the RRC connection recovery request can be effectively prolonged, so that multiple data transmission is flexibly supported.

The configuration method provided by the embodiment of the application can comprise at least two possible scenes. In one possible scenario, when the terminal should meet the requirement of RRC connection recovery, it starts a first timer, and meets a restart condition during the operation of the first timer, and restarts the first timer to prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request. It can be seen that in this possible scenario, when the restart condition is met, the restarted timer is the same as the timer started when the need for RRC connection recovery is met, both are the first timers. In another possible scenario, the terminal starts a first timer when the need for RRC connection recovery is met, and starts a second timer when the start condition is met during operation of the first timer, so as to extend the time for the terminal to wait for an RRC response message of an RRC connection recovery request. It can be seen that in this possible scenario, when the restart condition is met, the restarted timer is not one timer, but a new timer is additionally set, as compared to when the need for RRC connection recovery is met. It will be appreciated that in this possible scenario, the first timer may also be stopped after the second timer is started; of course, the first timer may be stopped first, then the second timer may be started, or the first timer may be stopped while the second timer is started. Thus, the first timer is replaced with the second timer to extend the time for the terminal to wait for the RRC response message of the RRC connection resume request.

In the ninth aspect, in one possible implementation manner, the terminal sends uplink data to the network device, where the uplink data is sent together with the RRC connection restoration request message or sent independently, and the downlink information includes feedback information of the uplink data, where the feedback information of the uplink data is used to indicate whether the uplink data is successfully transmitted.

The co-transmission or independent transmission in the present application refers to whether the uplink data and the RRC connection recovery request message are transmitted through the same message, for example, a MAC PDU message, and if the uplink data and the RRC connection recovery request message are transmitted through the same message, it can be understood that the uplink data and the RRC connection recovery request message are transmitted together; in contrast, if the uplink data and the RRC connection recovery request message are not transmitted through the same message, it can be understood that the uplink data and the RRC connection recovery request message are transmitted independently. Further, if the uplink data is transmitted independently of the RRC connection restoration request message, the uplink data may be transmitted during the first timer operation period after the RRC connection restoration request message is transmitted.

In the ninth aspect, in one possible implementation manner, the downlink information includes contention resolution information, and if the contention resolution information is contention resolution success, it indicates that the RRC connection recovery request message is successfully sent, and the terminal may continue to send new uplink data on the pre-configured grant; in contrast, if the contention resolution information is a contention resolution failure, it indicates that the RRC connection recovery request message is failed to be sent, and the terminal may continue to retransmit the RRC connection recovery request message on the provisioned grant.

In the ninth aspect, in one possible implementation manner, the downlink information includes uplink grant information, and the uplink resource indicated by the uplink grant information may be used for retransmission of original uplink data, or may be used for initial transmission of new uplink data, so as to implement data transmission of multiple consecutive packets. In general, if there is an original uplink data to be retransmitted and there is a new uplink data to be retransmitted, the new uplink data may be initially transmitted through the uplink resource indicated by the uplink grant information, that is, the transmission priority of the data initial transmission is higher than the transmission priority of the data retransmission.

In the ninth aspect, in one possible implementation manner, the terminal sends uplink data using an uplink resource indicated by the uplink grant information.

In the ninth aspect, in one possible implementation manner, the downlink information includes downlink resource allocation information, where downlink resources indicated by the downlink resource allocation information may be used for retransmission of original downlink data, and may also be used for initial transmission of new downlink data, so as to implement early transmission of downlink data.

In the embodiment of the application, the uplink authorization information and the downlink resource allocation information can exist independently, that is, the downlink information received by the terminal can include the uplink authorization information or the downlink resource allocation information; the uplink grant information and the downlink resource allocation information may exist at the same time and are combined with each other, that is, the downlink information received by the terminal may include the uplink grant information and the downlink resource allocation information at the same time.

In the ninth aspect, in one possible implementation manner, the terminal receives downlink data on a downlink resource indicated by the downlink resource allocation information.

In a possible implementation manner of the ninth aspect, the downlink information includes indication information, where the indication information is used to instruct the terminal to restart the first timer, so that after receiving the information including the indication information, the terminal may restart the first timer, so that data transmission is performed during operation of the first timer, which can effectively prolong a time for the terminal to wait for an RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission.

In a possible implementation manner of the ninth aspect, the terminal receives a broadcast message or an RRC message from the network device, where the broadcast message or the RRC message includes information of a first timer, and the information of the first timer is used to indicate a duration of the first timer, so that the terminal may configure the duration of the first timer according to the information of the first timer.

In a possible implementation manner of the ninth aspect, the first timer is a T319 timer.

In the ninth aspect, in one possible implementation manner, the first timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the terminal restarts the first timer during operation of the first timer from downlink information received by the network device or data transmission between the network device and the network device; or alternatively

The first timer is a T319 timer and the second timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the terminal starts or restarts the second timer during operation of the first timer according to downlink information received from the network device or according to data transmission with the network device.

In a possible implementation manner of the ninth aspect, the terminal sends indication information to the network device, where the indication information is used to instruct the network device to start the first timer or the second timer, so as to synchronize information of the timer that has been started currently to the network device.

In the ninth aspect, in one possible implementation manner, when the terminal starts the second timer, the first timer is stopped, so that power consumption generated by the first timer in an operating state may be reduced.

In the ninth aspect, in one possible implementation manner, the first timer or the second timer is stopped when the terminal receives an RRC connection resume, an RRC connection setup, or an RRC connection release message from the network device.

In a tenth aspect, an embodiment of the present application further provides a configuration method, where the configuration method may include: receiving a Radio Resource Control (RRC) connection recovery request message from a terminal, wherein the RRC connection recovery request message is sent after the terminal starts a first timer according to the requirement of the Radio Resource Control (RRC) connection recovery; and during the operation of the first timer, sending downlink information to the terminal or carrying out data transmission with the terminal, and restarting the first timer or starting the second timer according to the downlink information received from the network equipment or according to the data transmission with the network equipment.

Further, there is provided a configuration apparatus comprising means for performing the steps of the above tenth aspect.

Further, there is provided a configuration device comprising a processor and an interface circuit, the processor being for communicating with other devices via the interface circuit and performing the method provided in the tenth aspect above. The processor includes one or more.

Furthermore, a configuration device is provided, comprising a processor, for being connected to a memory, for invoking a program stored in said memory for performing the method according to the tenth aspect above. The memory may be located within the device or may be located external to the device. And the processor includes one or more.

Furthermore, a configuration device is provided comprising at least one processor and at least one memory, the at least one processor being configured to perform the method provided in the tenth aspect above.

Furthermore, a computer program is provided, which, when being executed by a processor, is adapted to carry out the method of the tenth aspect above.

Further, there is provided a computer-readable storage medium storing a program that, when called by a processor, performs the method of the above tenth aspect.

It can be seen that, in the tenth aspect, the network device sends downlink information to the terminal or performs data transmission with the terminal, so that the terminal can restart the first timer or start the second timer according to the downlink information received from the network device or performs data transmission with the terminal, so that the terminal can perform data transmission during the operation of the first timer or the second timer, and the time of the terminal waiting for the RRC response message of the RRC connection recovery request can be effectively prolonged, thereby flexibly supporting multiple data transmission.

In the tenth aspect, in one possible implementation manner, uplink data is received from the terminal, and the uplink data is sent together with the RRC connection recovery request message or sent independently, where the downlink information includes feedback information of the uplink data, and the feedback information of the uplink data is used to indicate whether the uplink data is successfully transmitted.

In the tenth aspect, in one possible implementation manner, the downlink information includes contention resolution information, and if the contention resolution information is contention resolution success, it indicates that the RRC connection recovery request message is successfully sent, and the terminal may continue to send new uplink data on the pre-configured grant; in contrast, if the contention resolution information is a contention resolution failure, it indicates that the RRC connection recovery request message is failed to be sent, and the terminal may continue to retransmit the RRC connection recovery request message on the provisioned grant.

In the tenth aspect, in one possible implementation manner, the downlink information includes uplink grant information, and uplink resources indicated by the uplink grant information may be used for retransmission of original uplink data, and may also be used for initial transmission of new uplink data, so as to implement data transmission of continuous multiple packets. In general, if there is an original uplink data to be retransmitted and there is a new uplink data to be retransmitted, the new uplink data may be initially transmitted through the uplink resource indicated by the uplink grant information, that is, the transmission priority of the data initial transmission is higher than the transmission priority of the data retransmission.

In the tenth aspect, in one possible implementation manner, uplink data sent by using an uplink resource indicated by the uplink grant information is received from the terminal.

In the tenth aspect, in one possible implementation manner, the downlink information includes downlink resource allocation information, where downlink resources indicated by the downlink resource allocation information may be used for retransmission of original downlink data, and may also be used for initial transmission of new downlink data, so as to implement early transmission of downlink data.

In the tenth aspect, in one possible implementation manner, the downlink data is sent to the terminal on a downlink resource indicated by the downlink resource allocation information.

In the tenth aspect, in one possible implementation manner, the downlink information includes indication information, where the indication information is used to instruct the terminal to restart the first timer, so that after receiving the information including the indication information, the terminal may restart the first timer, so that data transmission is performed during operation of the first timer, which can effectively prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission.

In the tenth aspect, in one possible implementation manner, a broadcast message or an RRC message is sent to the terminal, where the broadcast message or the RRC message includes information of a first timer, and the information of the first timer is used to indicate a duration of the first timer, so that the terminal may configure the duration of the first timer according to the information of the first timer.

In the tenth aspect, in one possible implementation manner, the first timer is a T319 timer.

In the tenth aspect, in one possible implementation manner, the first timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the first timer is a period during which the terminal is running, downlink information that should be received from the network device or data transmission between the terminal and the network device should be restarted; or alternatively

The first timer is a T319 timer and the second timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the second timer is started or restarted by the terminal during operation of the first timer according to downlink information received from the network device or according to data transmission with the network device.

In the tenth aspect, in one possible implementation manner, the indication information is received from the terminal, where the indication information is used to instruct the first timer or the second timer that is started by the network device, so as to synchronize the information of the timer that has been started currently to the network device.

It will be appreciated that the apparatus shown in the above aspects may be a chip, and the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.

The number of the processors is one or more, and the number of the memories is one or more.

The memory may be integral to the processor or separate from the processor. In a specific implementation process, the memory and the processor may be integrated on the same chip, or may be respectively disposed on different chips.

The above information transmission or reception process may be, for example, a process of transmitting a random access request, a process of outputting a random access request from a processor, a process of receiving a response message of a random access request, and a process of receiving a response message of an input random access request from a processor. Specifically, the random access request output by the processor may be output to the transmitter, and the response message received by the processor to the input random access request may be from the receiver. Wherein the transmitter and receiver may be collectively referred to as a transceiver.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a network architecture according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another network architecture according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a configuration method according to an embodiment of the present application;

FIG. 5 is a flowchart illustrating another configuration method according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of negotiating and determining each configuration parameter set according to an embodiment of the present application;

Fig. 7 is a schematic flow chart of releasing parameters other than the target configuration parameter in the context parameters of the terminal according to the embodiment of the present application;

fig. 8 is a schematic flow chart of allocating a suitable configuration parameter set to a terminal according to an embodiment of the present application;

fig. 9 is a schematic flow chart of a configuration method according to an embodiment of the present application;

FIG. 10 is a flowchart of another configuration method according to an embodiment of the present application;

FIG. 11 is a flowchart illustrating another configuration method according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a MAC message according to an embodiment of the present application;

Fig. 13 is a schematic structural diagram of another MAC message according to an embodiment of the present application;

FIG. 14 is a flowchart of another configuration method according to an embodiment of the present application;

FIG. 15 is a schematic flow chart of a configuration method according to an embodiment of the present application;

fig. 16 is a schematic diagram of determining an opportunity to monitor a PDCCH scrambled by a C-RNTI according to an embodiment of the present application;

fig. 17 is a schematic diagram of another embodiment of determining an opportunity to monitor a PDCCH scrambled by a C-RNTI;

Fig. 18 is a schematic diagram of determining an opportunity to monitor a PDCCH scrambled by a C-RNTI according to an embodiment of the present application;

Fig. 19 is a schematic diagram of determining an opportunity to monitor a PDCCH scrambled by a C-RNTI according to an embodiment of the present application;

FIG. 20 is a flow chart of a configuration method according to an embodiment of the present application;

FIG. 21 is a flow chart of an alternative configuration method according to an embodiment of the present application;

FIG. 22 is a flowchart of another configuration method according to an embodiment of the present application;

FIG. 23 is a flowchart of another configuration method according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 25 is a schematic structural diagram of another network device according to an embodiment of the present application;

Fig. 26 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The embodiments of the present application are applied to communication systems, such as wideband code division multiple access systems (wideband code division multiple access, WCDMA), time division synchronous code division multiple access systems (TD-SCDMA), long term evolution systems (long term evolution, LTE), public land mobile network (public land mobile network, PLMN) systems, and even fifth generation (5th generation,5G) communication systems or other systems that may occur in the future, and some terms in the present application are explained below to facilitate understanding by those skilled in the art. It should be noted that, when the scheme of the embodiment of the present application is applied to a 5G system or other systems that may occur in the future, names of network devices and terminals may change, but this does not affect implementation of the scheme of the embodiment of the present application.

In order to reasonably allocate configuration parameters to a terminal in an inactive state, an embodiment of the present application provides a configuration method, for example, please refer to fig. 1, fig. 1 is a schematic diagram of an application scenario provided in the embodiment of the present application, where a communication system shown in the application scenario may include at least one terminal and network equipment, and of course, may also include core network equipment. The network device indicates the terminal to enter a non-activated state from a connected state through an RRC connection release message, and the RRC connection release message can carry configuration parameters distributed to the non-activated terminal, namely, the terminal receives a radio resource control RRC connection release message sent by the network device, wherein the RRC connection release message comprises first information for indicating target configuration parameters; in this way, the terminal can enter the inactive state according to the RRC connection release message, and determine the context parameter of the inactive state according to the first information, where the context parameter of the inactive state includes the target configuration parameter, or the context parameter of the inactive state includes a parameter other than the target configuration parameter in the context parameter of the terminal, so as to reasonably indicate the configuration parameter for the terminal in the inactive state.

For the terminal in the inactive state, since the network device needs to store the context information of each of the plurality of terminals in the inactive state, in order to reduce the storage overhead of the network device, a part of configuration parameters of the plurality of terminals may be subjected to the immobilization process. In general, the configuration parameters of the terminals can be divided into three types, wherein the three types of configuration parameters are respectively a security type configuration parameter, a radio bearer configuration parameter and a cell group configuration parameter, and since the security type configuration parameters of each terminal are different, the security type configuration parameters are not cured; but the radio bearer configuration parameters of the terminal and/or the cell group configuration parameters may be cured. And the radio bearer configuration parameters of the plurality of terminals and/or the cell group configuration parameters are cured, so that at least two terminals correspond to the same set of configuration parameters, and only one set of configuration information is needed to be stored when the configuration information of the at least two terminals is stored for the network equipment, thereby reducing the storage cost of the network equipment. Based on this, when the network device indicates the configuration parameter for the terminal in the inactive state through the first information, the target configuration parameter indicated by the first information may also include a radio bearer configuration parameter and/or a cell group configuration parameter; the security configuration parameters configured by the network device for the terminal can be sent to the terminal independently, and of course, the security configuration parameters can also be sent to the terminal together with the first information, and can be specifically set according to actual needs.

Since the security class configuration parameters are irrelevant to the implementation of the embodiment of the present application, the context parameters in the inactive state below the embodiment of the present application do not include the security class configuration parameters, which means radio bearer configuration parameters and cell group configuration parameters. By way of example, the radio bearer configuration parameters may include one or more of packet data convergence protocol (PACKET DATA convergence protocol, PDCP) layer parameters, service data adaptation protocol (SERVICE DATA adaptation protocol, SDAP) layer parameters, data bearer (data radio bearer, DRB) identity parameters, evolved PACKET SYSTEM (EPS) bearer identities, and the like. The Cell group configuration parameters may include one or more of a Cell group identity, a radio link control (radio link control, RLC) configuration parameter for a bearer, a Cell group configuration parameter for a medium access control (medium access control, MAC) layer, a physical Cell group configuration parameter, a configuration parameter for a dedicated Cell (pscell+pcell, spcell), and a configuration parameter for a Secondary Cell (Scell), etc. Illustratively, PDCP layer parameters may include a timeout timer (DISCARDTIMER), a PDCP SN size header compression configuration for uplink and downlink, a hold-on, PDCP status report needs for acknowledged mode (acknowledged mode, AM) bearer, out-of-order transmission, split (split) or repetition (duplication) configuration and reordering timers, etc. The SDAP layer parameters can include one or more of Session identification (Session ID), presence or absence of upstream/downstream SDAP header, default data bearer (data radio bearer, DRB), quality of service flow identifier (qoS flowidentifier, QFI), etc. The cell group identity may include an identity indicating a primary cell group or a secondary cell group; the RLC configuration parameters of the bearer may include three types of information, one type of information being identification type information, including Radio Bearer (RB) identification, logical Channel (LCH) identification; one type of information is configuration information of the RLC, including SN length of the RLC PDU, a segmentation reassembly timer, maximum retransmission times of acknowledged mode (Acknowledged Mode, AM) RLC, request parameters for controlling the RLC of the AM mode to send a status report to the receiving end, and a prohibit timer for sending the RLC status report of the AM RLC; one type of information is logical channel configuration information, which may include one or more of parameters used by the priority handling procedure (e.g., allowed subcarrier spacing, physical Uplink SHARED CHANNEL (PUSCH) Transport Block (TB) duration, transmission rate, logical channel priority, etc.), and LCH-corresponding scheduling request (scheduling request, SR) configuration. The cell group configuration parameters of the MAC layer may include discontinuous reception (Discontinuous Reception, DRX) configuration, SR, buffer status report (Buffer Status Report, BSR), configuration parameters of power headroom report (power headroom report, PHR), timer triggering release of RRC connection, timing adjustment group identity, and timing adjustment timer; the physical cell group configuration parameters may include one or more of an identity (x-RNTI) of a terminal for power control or scheduling resources, configuration information controlling downlink feedback, and maximum transmission power of the low frequency band FR 1. Spcell may include one or more of CellIndex, cell group identity, radio link failure detection configuration, radio link monitoring detection configuration, measurement configuration information, physical downlink control channel (physical downlink control channel, PDCCH), physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH), PUSCH configuration parameters, uplink (up link, UL) and downlink bandwidth portion (down link bandwidth part) DL BWP configuration, initial active BWP ID, and timer (timer) managing active BWP. For the configuration parameters of the Scell, only when carrier aggregation (carrier aggregation, CA) or dual chains (dual connectivity, DC) are configured is the configuration parameters of the Scell, and the configuration parameters of the Scell are a subset of Spcell configuration information.

Among them, 1) a terminal, also called User Equipment (UE), mobile Station (MS), mobile Terminal (MT), etc., is a device that provides voice/data connectivity to a user, for example, a handheld device with a wireless connection function, or an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone), a tablet, a notebook, a palm, a mobile internet device (mobile INTERNET DEVICE, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), or a wireless terminal in smart home (smart home), and the like.

2) A network device is a device in a wireless network, such as a radio access network (radio access network, RAN) node that accesses a terminal to the wireless network. Currently, some examples of RAN nodes are: a gNB, a transmission reception point (transmission reception point, TRP), an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), or a wireless fidelity (WIRELESS FIDELITY, wifi) Access Point (AP), etc. In one network architecture, the network devices may include a centralized unit (centralized unit, CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node.

3) In embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/" generally indicates that the front-rear associated object is an or relationship; furthermore, for elements (elements) that appear in the singular forms "a," "an," and "the," it does not mean "one or only one" unless the context clearly dictates otherwise. For example, "a device" means a device for one or more of such devices. Further, at least one (at least one of),. The term "means one or any combination of subsequent association objects, e.g." at least one of a, B and C "includes a, B, C, AB, AC, BC, or ABC. Determining Y from X does not mean determining Y from X alone, but may also determine Y from X and other information.

For example, please refer to fig. 2, fig. 2 is a schematic diagram of a network architecture according to an embodiment of the present application. As shown in fig. 2, the network architecture includes a CN device and a RAN device. The RAN device includes a baseband device and a radio frequency device, where the baseband device may be implemented by one node, or may be implemented by multiple nodes, and the radio frequency device may be implemented independently from the baseband device, or may be integrated into the baseband device, or a part of the radio frequency device may be integrated into the baseband device. For example, in a long term evolution (long term evolution, LTE) communication system, a RAN apparatus (eNB) includes a baseband device and a radio device, where the radio device may be remotely located relative to the baseband device, e.g., a remote radio unit (remote radio unit, RRU) is remotely located relative to the BBU.

The communication between the RAN device and the terminal follows a certain protocol layer structure. For example, the control plane protocol layer structure may include functions of protocol layers such as a radio resource control (radio resource control, RRC) layer, a packet data convergence layer protocol (PACKET DATA convergence protocol, PDCP) layer, a radio link control (radio link control, RLC) layer, a medium access control (MEDIA ACCESS control, MAC) layer, and a physical layer. The user plane protocol layer structure may include the functions of protocol layers such as PDCP layer, RLC layer, MAC layer, and physical layer; in one implementation, a service data adaptation protocol (SERVICE DATA adaptation protocol, SDAP) layer may also be included above the PDCP layer.

The functions of these protocol layers may be implemented by one node, or may be implemented by a plurality of nodes; for example, in one evolution architecture, a RAN device may include a centralized unit (centralized unit, CU) and a Distributed Unit (DU), and multiple DUs may be centrally controlled by one CU. As shown in fig. 2, a CU and a DU may be divided according to protocol layers of a wireless network, for example, functions of a PDCP layer and above are set at the CU, and functions of protocol layers below the PDCP layer, for example, functions of an RLC layer and a MAC layer, etc. are set at the DU.

The division of the protocol layer is merely an example, and other protocol layers may be divided, for example, division in the RLC layer, where functions of the RLC layer and above are set in the CU, and functions of the protocol layer below the RLC layer are set in the DU; or divided in a certain protocol layer, for example, a part of functions of the RLC layer and functions of protocol layers above the RLC layer are set at CU, and the remaining functions of the RLC layer and functions of protocol layers below the RLC layer are set at DU. In addition, the functions that require processing time to meet the latency requirement may be set in the DU and the functions that do not require processing time to meet the latency requirement may be set in the CU in other manners, such as time-lapse partitioning.

In addition, the rf device may be remote, not placed in the DU, or may be integrated in the DU, or a portion of the remote may be integrated in the DU, without any limitation.

With continued reference to fig. 3, fig. 3 is a schematic diagram of another network architecture provided in an embodiment of the present application, and, with respect to the architecture shown in fig. 2, the Control Plane (CP) and the User Plane (UP) of a CU may be implemented by separate entities, which are a control plane CU entity (CU-CP entity) and a user plane CU entity (CU-UP entity), respectively.

In the above network architecture, the signaling generated by the CU may be transmitted to the terminal through the DU, or the signaling generated by the terminal may be transmitted to the CU through the DU. The DU may be passed through to the terminal or CU directly through the protocol layer encapsulation without parsing the signaling. In the following embodiments, transmission or reception of signaling by a DU includes such a scenario if such signaling is involved in the transmission between the DU and the terminal. For example, the signaling of the RRC or PDCP layer is eventually processed as the signaling of the PHY layer to be transmitted to the terminal or converted from the received signaling of the PHY layer. Under this architecture, the signaling of the RRC or PDCP layer can be considered as being sent either by the DU or by the DU and radio frequency.

In the above embodiments, the CU is divided into network devices on the RAN side, and in addition, the CU may be divided into network devices on the CN side, which is not limited herein.

The apparatus in the following embodiments of the present application may be located in a terminal or a network device according to the functions implemented by the apparatus. When the above CU-DU structure is adopted, the network device may be a CU node, or a DU node, or a RAN device including the CU node and the DU node.

As can be seen from the above description, when the network device indicates that the terminal enters the inactive state from the connected state, and the configuration parameter is indicated by the terminal in the inactive state reasonably through the first information, the network device can be divided into two different scenarios. In one possible scenario, the network device may indicate, through the first information, a configuration parameter configured for the terminal in the inactive state, so that the terminal in the inactive state retains the configuration parameter configured for it. In another possible scenario, the network device may indicate, through the first information, a configuration parameter that needs to be released by the terminal in the inactive state, so that the terminal in the inactive state releases the configuration parameter that needs to be released. In these two different scenarios, the target configuration parameters indicated by the first information are different. The following describes in detail the technical solutions corresponding to these two different scenarios in combination with detailed embodiments.

In one possible scenario, when the network device indicates the configuration parameters configured for the terminal through the first information, so that the terminal retains the configuration parameters configured for the terminal, the configuration parameters that need to be retained may be indicated to the terminal in two different manners. In one mode, the network device may indicate the target configuration parameter to be reserved to the terminal in a direct indication mode, that is, the target configuration parameter indicated by the first information is the configuration parameter to be reserved by the terminal, so that the terminal determines the configuration parameter to be reserved directly according to the target configuration parameter indicated by the first information after receiving the first information, and reserves the target configuration parameter. In another mode, the network device may indicate to the terminal that the configuration parameter needs to be reserved through an indirect indication mode, that is, the target configuration parameter indicated by the first information is not the configuration parameter that the terminal needs to reserve, so that after the terminal receives the first information, the terminal determines parameters except for the target configuration parameter according to the target configuration parameter indicated by the first information, where the parameters except for the target parameter are the configuration parameters that the terminal needs to reserve. It can be seen that in the two different ways the definition of the target configuration parameters indicated by the first information is different. In a first mode, the target configuration parameter indicated by the first information is a configuration parameter that needs to be reserved by the terminal; in the second manner, the target configuration parameter indicated by the first information is not a configuration parameter that the terminal needs to reserve, and the parameters other than the target configuration parameter are configuration parameters that the terminal needs to reserve. Thus, in these two different ways, the target configuration parameters of the first indication information are different.

In this possible scenario, the first indication manner is mainly taken as an example for explanation, that is, the target configuration parameter indicated by the first information is the configuration parameter that needs to be reserved by the terminal. When the network device indicates, through the first information, that the terminal needs to reserve the target configuration parameters, the network device may indicate, through two possible ways, that the terminal needs to reserve the target configuration parameters. In a possible manner, the first information is an identifier of the target configuration parameter, that is, the network device indicates the identifier of the target configuration parameter to the terminal, so that the terminal determines the target configuration parameter to be reserved according to the identifier of the target configuration parameter; in another possible manner, the first information is the target configuration parameter itself, that is, the network device directly indicates the target configuration parameter to the terminal, so that the terminal can directly obtain the target configuration parameter to be reserved. Taking the first information as an example of the identification of the target configuration parameter, as shown in fig. 4, fig. 4 is a schematic flow chart of a configuration method according to an embodiment of the present application, where the configuration method may include:

S401, the network device sends a Radio Resource Control (RRC) connection release message to the terminal.

The RRC connection release message includes first information, and the first information is an identification of a target configuration parameter. The target configuration parameters may include radio bearer configuration parameters and/or cell group configuration parameters, for example.

Referring to the above description about configuration parameters, in order to reduce the storage overhead of the network device, the network device may perform curing processing on radio bearer configuration parameters of at least two terminals and/or cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, thereby reducing the storage overhead of the network device. After the curing process, a plurality of configuration parameter sets can be obtained, and then one or more appropriate configuration parameter sets are allocated to the terminal in the plurality of configuration parameter sets. The configuration parameters may be referred to as access layer configuration parameters, which may include radio bearer configuration parameters or, cell group configuration parameters, or both radio bearer configuration parameters and cell group configuration parameters. Taking an access stratum configuration parameter as an example, after curing, a plurality of predefined access stratum configuration parameter sets may be obtained, where the predefined access stratum configuration parameter sets are respectively: set 1, set 2, set 3, …, and set N. Optionally, when a suitable access layer configuration parameter set is allocated to the terminal, the corresponding access layer configuration parameter set may be allocated to the terminal according to a mode corresponding to the data radio bearer DRB of the terminal. When the mode corresponding to the DRB of the terminal is the acknowledged mode AM, the parameters in the set 1 may be indicated to the terminal as target configuration parameters, and one or more of the SDAP parameters, PDCP parameters, RLC parameters, and cell group configuration parameters of the MAC layer may be included in the set 1. The set 1 may also include DRB IDs. The SDAP parameters may include whether an uplink/downlink SDAP header exists or not, whether one or more of a default DRB and QFI exists, and optionally, the SDAP parameters may also be Session ID; the PDCP parameters may include one or more of DISCARDTIMER, uplink and downlink PDSP SN size, header compression configuration, full hold on, PDCP status reporting requirements for AM bearers, out-of-order transmission, and reordering timers. The RLC parameters may include one or more of RB identity, LCH identity, configuration information of RLC, SN length of RLC PDU, segmentation reassembly timer, maximum number of retransmissions of AM RLC, request parameters controlling AM mode to transmit poll to the receiving end, and prohibit timer of AM RLC to transmit RLC status report. The cell group of the MAC layer configures one or more of a subcarrier spacing allowed by one LCH ID, a TB duration of PUSCH, a transmission rate, and a logical channel priority, etc. If the Session ID is not included in the set 1, the network device may further indicate to the terminal which Session ID is associated with the parameters in the set 1. Similarly, if RB IDs are not included in set 1, the network device may further instruct the terminal which RB ID is associated with the parameters in set 1.

Conversely, when the mode corresponding to the DRB of the terminal is the unacknowledged mode UM, the parameter in the set 2 may be indicated to the terminal as the target configuration parameter, and one or more of the PDCP parameter and the RLC parameter may be included in the set 2. Of course, the set 2 may also include one or more of the SDAP parameters and the cell group configuration parameters of the MAC layer. The PDCP parameters may include DISCARDTIMER, uplink and downlink PDSP SN size, header compression configuration, finish hold on, out-of-order transmission, and one or more of reordering timers. The RLC parameters may include RB identity, LCH identity, configuration information for RLC: one or more of the SN length and segment reassembly timer of the RLC PDU. The SDAP parameters may include whether an uplink/downlink SDAP header exists or not, whether it is one or more of a default DRB and QFI, and optionally, the SDAP parameters may also be Session ID. The cell group of the MAC layer configures one or more of a subcarrier spacing allowed by one LCH ID, a TB duration of PUSCH, a transmission rate, and a logical channel priority, etc. If the Session ID is not included in the set 2, the network device may further instruct the terminal which Session ID is associated with the parameters in the set 2. Similarly, if the RB ID is not included in the set 2, the network device may further instruct the terminal which RB ID is associated with the parameters in the set 2.

In combination with the above description about the set 1 and the set 2, the set 3, the set 4, the set 5 and the set 6 may be further defined on the basis of the set 1 and the set 2. For example, set 3 may be defined as the set formed by the configuration parameters of sets 1 and Spcell; set 4 may be defined as the set of configuration parameters for sets 2 and Spcell; set 5 may be defined as the set formed by set 3 and the configuration parameters of Scell; set 6 may be defined as a set formed by set 4 and Scell configuration parameters, and of course, the embodiment of the present application is merely described by taking set 1, set 2, set 3, set 4, set 5 and set 6 as examples, but the embodiment of the present application is not limited thereto.

It may be understood that the above network device indicates, for a terminal, a configuration parameter set suitable for the terminal, and essentially indicates, to the terminal, the configuration parameters in the configuration parameter set, that is, the configuration parameters in the configuration parameter set are allocated to the terminal as target configuration parameters. When the network device indicates the target configuration parameter to the terminal, the network device may send the identifier of the target configuration parameter to the terminal as the first information carried in the RRC connection release message, so that the terminal performs the following S402 according to the RRC release message:

s402, the terminal enters a non-activated state according to the RRC connection release message, and determines that the context parameters of the non-activated state comprise the target configuration parameters corresponding to the identifiers according to the identifiers corresponding to the target configuration parameters and the mapping relation.

By way of example, the identification of the target configuration parameter may be a set identification of a set of configuration parameters, such as an identification of set 1, or an identification of set 2, etc.

And the terminal enters a non-activated state according to the RRC connection release message after receiving the RRC connection release message sent by the network equipment. In addition, because the mapping relation between the identifier corresponding to the configuration parameter and the configuration parameter is pre-stored in the terminal, after the terminal receives the identifier corresponding to the target configuration parameter, which is sent by the network device, the terminal can search the identifier corresponding to the target configuration parameter in the mapping relation according to the identifier corresponding to the target configuration parameter, and determine the configuration parameter corresponding to the identifier corresponding to the target configuration parameter as the target configuration parameter to be reserved, for example, the configuration parameter in the set 1 or the configuration parameter in the set 2, so as to obtain the target configuration parameter, thereby reserving the configuration parameter in the set 1 or the configuration parameter in the set 2, and performing configuration according to the target configuration parameter.

S403, the terminal reserves the target configuration parameters.

Furthermore, the network device performs curing treatment on radio bearer configuration parameters of a plurality of terminals and/or cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, when the plurality of terminals enter an inactive state from a connection state, for the network device, only one set of configuration information is needed to be stored when the configuration information of the at least two terminals is stored, thereby reducing the storage cost of the network device.

In addition, for the terminal, after entering the inactive state from the connected state according to the RRC connection release message, some or all of the MAC layer configuration information, RLC layer configuration information, PDCP layer configuration information, SDAP layer configuration information, physical cell group configuration information, spcell configuration, and Scell configuration information in the connected state may be released.

It should be noted that, before sending the RRC connection release message to the terminal, the network device may first obtain capability information reported by the terminal, and determine, according to the capability information reported by the terminal, whether the terminal supports data transmission in an inactive state. For example, when the terminal reports its capability information, the terminal may report its capability information to the network device in at least four possible manners. Taking the example that the terminal supports data transmission in the inactive state, the four possible modes are respectively: the terminal can support data transmission in an inactive state, the terminal supports the configuration of the context parameters of the terminal through the pre-configuration identification, the terminal supports the common parameter configuration in the inactive state (in other words, the terminal supports the lightweight access layer configuration parameters), and the terminal supports the session of data transmission in a direct inactive state. Although the expression modes are different, the terminal can be indicated to support data transmission in the inactive state through the four different modes.

It can be seen that the embodiment shown in fig. 4 described above describes in detail the technical solution of the target configuration parameter that the network device indicates, through the identification of the target configuration parameter, that the terminal needs to reserve in one possible scenario, when the first information is the identification of the target configuration parameter, and in another possible scenario, the network device indicates, through the target configuration parameter itself, that the terminal needs to reserve in another possible scenario. For example, referring to fig. 5, fig. 5 is a flowchart of another configuration method provided in an embodiment of the present application, where the configuration method may include:

S501, the network equipment sends a radio resource control RRC connection release message to the terminal.

The RRC connection release message includes first information, where the first information is a target configuration parameter. The target configuration parameters may include radio bearer configuration parameters and/or cell group configuration parameters, for example.

Referring to the above description about configuration parameters, in order to reduce the storage overhead of the network device, the network device may perform curing processing on radio bearer configuration parameters of at least two terminals and/or cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, thereby reducing the storage overhead of the network device. After the curing process, a plurality of configuration parameter sets can be obtained, and then one or more configuration parameter sets suitable for the terminal are allocated in the plurality of configuration parameter sets. It can be understood that, in this possible scenario, the method of obtaining multiple configuration parameter sets in advance by the network device and the method of indicating the appropriate one or more configuration parameter sets for the terminal are similar to the method of obtaining multiple configuration parameter sets in advance by the network device in S401 and the method of indicating the appropriate one or more configuration parameter sets for the terminal, respectively, and may be referred to the related description in S401, and the embodiments of the present application will not be repeated herein.

It can be seen that, in the embodiment shown in fig. 5, unlike the technical solution in the embodiment shown in fig. 4, when the network device indicates that the terminal needs to reserve the target configuration parameters, the network device directly uses the target configuration parameters in the configuration parameter set as the first information, and carries the first information in the RRC connection release message, so that the terminal performs the following S502 according to the RRC connection release message:

S502, entering a non-activated state according to the RRC connection release message, and determining a target configuration parameter according to the first information.

After receiving the RRC connection release message sent by the network device, the terminal is different from S403 above, in this possible implementation manner, the terminal does not need to store in advance a mapping relationship between the identifier corresponding to the configuration parameter and the configuration parameter, and further does not need to determine the target configuration parameter according to the identifier corresponding to the target configuration parameter and the mapping relationship, but directly enters the inactive state according to the RRC connection release message, and because the RRC connection release message directly carries the target configuration parameter, the terminal can directly acquire and retain the target configuration parameter. Although the configuration signaling overhead is larger when the target configuration parameters are carried in the RRC connection release message and sent to the terminal, the terminal does not need to store pre-configuration in advance, and the configuration overhead of the storage overhead of the terminal is reduced.

S503, the terminal reserves the target configuration parameters.

Further, in the embodiment of the present application, the network device performs the curing process on the radio bearer configuration parameters of the plurality of terminals and/or the cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, when the plurality of terminals enter the inactive state from the connection state, for the network device, only one set of configuration information needs to be stored when the configuration information of the at least two terminals is stored, thereby reducing the storage overhead of the network device.

Before sending the RRC connection release message to the terminal, the network device can firstly acquire the capability information reported by the terminal, and determine whether the terminal supports data transmission in an inactive state according to the capability information reported by the terminal. For example, when the terminal reports the capability information, the reporting manner is the same as that of the terminal in the embodiment shown in fig. 4, and specifically, reference may be made to the above description, and here, the embodiment of the present application will not be repeated.

In the embodiments shown in fig. 4 and fig. 5, when describing that the network device indicates, to the terminal, the configuration parameter that needs to be reserved through the first information, only the configuration parameter that needs to be reserved is described as an example, where the target configuration parameter indicated by the first information is the configuration parameter that needs to be reserved by the terminal. Of course, the target configuration parameter indicated by the first information may not be the configuration parameter that needs to be reserved by the terminal, and the terminal may determine, after receiving the first information, a parameter other than the target configuration parameter according to the target configuration parameter indicated by the first information, where the parameter other than the target parameter is the configuration parameter that needs to be reserved by the terminal, so as to reserve the parameter other than the target parameter. It is noted that in two different indication manners, the target configuration parameters indicated by the first information are different. Here, the embodiments of the present application are not described in detail.

The embodiments shown in fig. 4 and fig. 5 above describe in detail the technical solutions in which, in one possible scenario, the network device may indicate, through the first information, the configuration parameters configured for the terminal in the inactive state, so that the terminal in the inactive state remains as the configuration parameters configured for the terminal in the inactive state, and in another possible scenario, the technical solutions in which, in the network device may indicate, through the first information, the configuration parameters that need to be released by the terminal in the inactive state, so that the terminal in the inactive state releases the configuration parameters that need to be released will be described in detail below.

In another possible scenario, when the network device indicates, through the first information, the configuration parameters that need to be released by the terminal, so that the terminal releases the configuration parameters that need to be released, the configuration parameters that need to be released may also be indicated to the terminal in two different manners. In one mode, the network device may indicate the configuration parameter to be released to the terminal in a direct indication mode, that is, the target configuration parameter indicated by the first information is the configuration parameter to be released by the terminal, so that the terminal determines the configuration parameter to be released directly according to the target configuration parameter indicated by the first information after receiving the first information, and releases the target configuration parameter. In another mode, the network device may indicate to the terminal that the configuration parameter needs to be released by means of indirect indication, that is, the target configuration parameter indicated by the first information is not the configuration parameter that the terminal needs to release, so that after the terminal receives the first information, the terminal determines parameters except for the target configuration parameter according to the target configuration parameter indicated by the first information, where the parameters except for the target parameter are the configuration parameters that the terminal needs to release. It can also be seen that in the two different ways the definition of the target configuration parameters indicated by the first information is different. In a first mode, the target configuration parameter indicated by the first information is a configuration parameter that needs to be released by the terminal; in the second manner, the target configuration parameter indicated by the first information is not a configuration parameter that the terminal needs to release, and the parameters other than the target configuration parameter are configuration parameters that the terminal needs to release. Thus, in these two different ways, the target configuration parameters of the first indication information are different.

In this possible scenario, the first indication manner is mainly taken as an example for explanation, that is, the target configuration parameter indicated by the first information is the configuration parameter that needs to be released by the terminal. When the network device indicates, through the first information, that the terminal needs to release the target configuration parameter, the network device may indicate, through two possible ways, that the terminal needs to release the target configuration parameter. In a possible manner, the first information is an identifier of the target configuration parameter, that is, the network device indicates the identifier of the target configuration parameter to the terminal, so that the terminal determines the target configuration parameter to be released according to the identifier of the target configuration parameter; in another possible manner, the first information is the target configuration parameter itself, that is, the network device directly indicates the target configuration parameter to the terminal, so that the terminal can directly obtain the target configuration parameter to be released. Taking the first information as an example of the identification of the target configuration parameter, as shown in fig. 6, fig. 6 is a schematic flow chart for releasing parameters except the target configuration parameter in the context parameter of the terminal according to the embodiment of the present application, where the method may include:

s601, the network device sends a Radio Resource Control (RRC) connection release message to the terminal.

The RRC connection release message includes first information, and the first information is an identification of a target configuration parameter. For example, the target configuration parameters may include radio bearer configuration parameters, and/or cell group configuration parameters.

In this possible scenario, assuming that the network device has previously configured multiple sets of configuration parameters for the terminal, before the multiple sets of configuration parameters are pre-configured for the terminal, similarly, in order to reduce the storage overhead of the network device, the network device may perform curing processing on radio bearer configuration parameters of at least two terminals and/or cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters, thereby reducing the storage overhead of the network device. After the curing process, a plurality of configuration parameter sets can be obtained, and then the configuration parameters in the plurality of configuration parameter sets are configured to the terminal. It can be understood that in this possible scenario, the method of obtaining multiple configuration parameter sets in advance by the network device and the method of allocating multiple configuration parameter sets to the terminal are similar to the method of obtaining multiple configuration parameter sets in advance by the network device in S401 and the method of allocating multiple configuration parameter sets to the terminal, respectively, and may be referred to the related description in S401, and the embodiments of the present application will not be described herein again.

When the network device indicates, through the first information, that the terminal needs to release the target configuration parameter, the network device may send, as the first information, the identifier of the target configuration parameter to the terminal in the RRC connection release message, so that the terminal performs the following S602 according to the RRC release message:

s602, the terminal enters a non-activated state according to the RRC connection release message, and determines that the context parameters of the non-activated state comprise the target configuration parameters corresponding to the identifiers according to the identifiers corresponding to the target configuration parameters and the mapping relation.

And the terminal enters a non-activated state according to the RRC connection release message after receiving the RRC connection release message sent by the network equipment. In addition, because the mapping relationship between the identifier corresponding to the configuration parameter and the configuration parameter is pre-stored in the terminal, after the terminal receives the identifier corresponding to the target configuration parameter, which is sent by the network device, the terminal can search the identifier corresponding to the target configuration parameter in the mapping relationship according to the identifier corresponding to the target configuration parameter, and determine the configuration parameter corresponding to the identifier corresponding to the target configuration parameter as the target configuration parameter to be released, for example, the configuration parameter in the set 1 or the configuration parameter in the set 2 is determined as the target configuration parameter to be released, so as to obtain the target configuration parameter, thereby releasing the configuration parameter in the set 1 or the configuration parameter in the set 2.

S603, the terminal releases the target configuration parameters in the non-activated context parameters.

After receiving the RRC connection release message sent by the network device and determining the target configuration parameters to be released included in the context parameters of the terminal according to the first information carried by the RRC connection release message, the terminal can directly release the target configuration parameters, so that the network device can control which configuration parameters are used continuously and which configuration parameters are not used any more on the premise of reducing the storage overhead of the network device and the terminal.

In addition, for the terminal, after entering the inactive state from the connected state according to the RRC connection release message, other access layer parameters may be released, where the other access layer parameters include at least one of physical cell configuration information, spcell configuration information, and Scell configuration information. For example, when the terminal releases other access layer parameters, one way is: after receiving the RRC connection release message, the terminal defaults to release other access layer parameters, i.e., in this manner, the RRC message does not need to carry release indication information. In another manner, after receiving the RRC connection release message, the terminal may explicitly carry indication information for releasing other configurations in the RRC connection release message, so that the terminal releases other access layer parameters according to the indication information for releasing other configurations.

In a possible scenario, when the first information is the identifier of the target configuration parameter, the network device indicates, through the identifier of the target configuration parameter, the technical scheme of the target configuration parameter that the terminal needs to release, and of course, the first information may also be the target configuration parameter itself, that is, the network device may carry the target configuration parameter itself that needs to be released as the first information in the RRC connection release message, and send the first information to the terminal, so that the terminal may determine the target configuration parameter that needs to be released directly according to the first information, and compared with the identifier of the first information that is the target configuration parameter, the terminal does not need to store in advance the mapping relationship between the identifier corresponding to the configuration parameter and the configuration parameter, and does not need to determine the target configuration parameter according to the identifier corresponding to the target configuration parameter, but directly enters the inactive state according to the RRC connection release message, and because the target configuration parameter is directly carried in the RRC connection release message, the terminal may directly acquire and release the target configuration parameter. Although the configuration signaling overhead is larger when the target configuration parameters are carried in the RRC connection release message and sent to the terminal, the terminal does not need to store pre-configuration in advance, and the configuration overhead of the storage overhead of the terminal is reduced.

In the embodiment shown in fig. 7, when describing that the network device indicates, to the terminal, the configuration parameter that needs to be released through the first information, only the configuration parameter that needs to be released is described as an example of the target configuration parameter indicated by the first information. Of course, the target configuration parameter indicated by the first information may not be the configuration parameter that the terminal needs to release, and the corresponding terminal may determine, after receiving the first information, a parameter other than the target configuration parameter according to the target configuration parameter indicated by the first information, where the parameter other than the target parameter is the configuration parameter that the terminal needs to release, so as to release the parameter other than the target parameter. It is noted that in two different indication manners, the target configuration parameters indicated by the first information are different. Here, the embodiments of the present application are not described in detail.

Based on the embodiment shown in any one of fig. 4 to fig. 6, whether the network device indicates the configuration parameters that need to be reserved or the configuration parameters that need to be released by the terminal through the target configuration parameters indicated by the first information, the network device performs curing treatment on radio bearer configuration parameters of the plurality of terminals and/or cell group configuration parameters to obtain one or more configuration parameter sets before the network device indicates the configuration parameters through the first information; and then, indicating the configuration parameters in a certain configuration parameter set which needs to be reserved by the terminal or indicating the configuration parameters in a certain configuration parameter set which needs to be released by the terminal through the first information. In order to unify one or more configuration parameter sets configured by each network device for the terminal, the network device may negotiate with other network devices, e.g. the first network device, to determine each configuration parameter set before sending an RRC connection request message to the terminal indicating the target configuration parameter. For example, referring to fig. 7, fig. 7 is a schematic flow chart of negotiating and determining each set of configuration parameters according to an embodiment of the present application, and the method for determining each set of configuration parameters may include:

S701, the network device sends a first request message to the first network device.

The first request message is used for requesting the first network equipment to confirm the initial radio bearer configuration parameters and/or the initial cell group configuration parameters in the initial configuration parameter set.

For example, after the first network device receives the initial radio bearer configuration parameters and/or the initial cell group configuration parameters sent by the network device, one possible scenario is: if the first network equipment supports the initial radio bearer configuration parameter and/or the initial cell group configuration parameter, confirming and storing the initial radio bearer configuration parameter and/or the initial cell group configuration parameter, wherein the initial radio bearer configuration parameter and/or the initial cell group configuration parameter is/are included in a response message sent to the network equipment at the moment; another possible case is: if the first network device does not support the initial radio bearer configuration parameter and/or the initial cell group configuration parameter, the initial radio bearer configuration parameter and/or the initial cell group configuration parameter need to be modified, the initial radio bearer configuration parameter and/or the initial cell group configuration parameter are directly modified and the modified radio bearer configuration parameter and/or the modified cell group configuration parameter are stored, and at this time, the response message sent by the first network device to the network device includes the modified radio bearer configuration parameter and/or the modified cell group configuration parameter.

It should be noted that, when the network device negotiates with the first network device to determine each configuration parameter set, all configuration parameter sets may be sent to the first network device through the first request message; of course, the all configuration parameter sets may also be sent to the first network device through a plurality of first request messages, and may specifically be set according to actual needs, where the embodiment of the present application is not limited further.

S702, the first network device sends a first response message to the network device.

Wherein the first response message comprises the initial radio bearer configuration parameter and/or the initial cell group configuration parameter, or the modified radio bearer configuration parameter and the modified cell group configuration parameter of the first network device.

After receiving the first response message, the network device may determine a set of configuration parameters according to the first response message, i.e. perform the following S703:

S703, the network device determines a configuration parameter set according to the first response message.

If the initial radio bearer configuration parameter and/or the initial cell group configuration parameter are included in the first response message, it is indicated that the first network device supports the initial radio bearer configuration parameter and/or the initial cell group configuration parameter determined by the network device, and the initial radio bearer configuration parameter and/or the initial cell group configuration parameter are determined to be the configuration parameters which can be used subsequently, and the set including the configuration parameters is the configuration parameter set used subsequently. If the first response message includes the modified radio bearer configuration parameter and/or the modified cell group configuration parameter, it indicates that the first network device does not support the initial radio bearer configuration parameter and/or the initial cell group configuration parameter determined by the network device, then the modified radio bearer configuration parameter and/or the modified cell group configuration parameter are determined to be subsequent usable configuration parameters, a set including the configuration parameters is a subsequent usable configuration parameter set, and then the network device indicates, through the first information, the configuration parameters in a certain configuration parameter set that needs to be reserved by the terminal, or indicates the configuration parameters in a certain configuration parameter set that needs to be released by the terminal, and in an indication process, defects caused by non-uniform configuration parameters are avoided.

The embodiments shown in fig. 4 and fig. 5 above describe in detail the technical solution that, in order to reduce the storage overhead of the network device, the network device may perform curing processing on radio bearer configuration parameters of at least two terminals and/or cell group configuration parameters to obtain multiple configuration parameter sets, and then indicate, for the terminals, one or more appropriate configuration parameter sets in the multiple configuration parameter sets. For example, the network device may receive, before indicating the appropriate one or more configuration parameter sets for the terminal, indication information sent by the core network device, where the indication information is used to instruct the network device to indicate the appropriate one or more configuration parameter sets for the terminal. For example, referring to fig. 8, fig. 8 is a flowchart illustrating a process of allocating a suitable configuration parameter set to a terminal according to an embodiment of the present application, where the method may include:

S801, a terminal sends a registration request to core network equipment.

Wherein the registration request optionally includes capability information of the terminal. For example, the capability information of the terminal may support a Direct Data Transfer (DDT) session for the terminal, i.e., the terminal supports direct data transfer in an inactive state. It should be noted that, the terminal capability information is the same as the terminal capability information in the embodiment shown in fig. 4, and specifically, reference may be made to the related description in the embodiment shown in fig. 4, and here, the embodiment of the present application will not be repeated.

S802, the terminal sends a protocol data unit (protocol data unit, PDU) session establishment request to the core network equipment.

Optionally, the session type in the PDU session establishment request may indicate that the session type is a DDT session, i.e. the DDT session may be used for the terminal to directly perform data transmission in an inactive state. In this way, direct data transfer in the inactive state of session granularity can be achieved.

S803, the core network equipment optionally determines to establish the DDT session for the terminal according to the subscription data and/or the capability information of the terminal.

For example, when determining whether to establish a DDT session for a terminal, the core network device may search for subscription data of the terminal in a session management function (session management function, SMF) device, and determine whether to establish the DDT session for the terminal according to the subscription data of the terminal, e.g., when an operator signs a user of the terminal about to provide a DDT function for the terminal, determine to establish the DDT session for the terminal. Of course, it is also possible to determine whether to establish a DDT session for a terminal directly according to its own stored capability information of the terminal without searching for subscription data of the terminal through the SMF device.

After the judgment, if the core network device determines that the DDT session is established for the terminal, the following S804 is executed to the network device PDU session establishment request:

s804, the core network device sends PDU session establishment request to the network device.

The PDU session establishment request may include a session type, where the session type is used to indicate that the terminal is allowed to perform uplink transmission when in an inactive state. For example, the session type may be a boolean parameter, with a value of 1, indicating that data transmission may be performed in an inactive state; a value of 0 indicates that data transmission cannot be performed in an inactive state, and vice versa; or the session type is an enumeration type parameter, and the value is True, which indicates that the data transmission can be performed in an inactive state; a value of False indicates that data transmission cannot be performed in an inactive state; or the value is DDT session, which means that the data transmission can be carried out in the inactive state; the other value indicates that the data transmission can not be carried out in the inactive state. The session type may also be referred to as indication information.

It can be seen that the session type for indicating that the terminal is allowed to perform uplink transmission in the inactive state is carried in the PDU session establishment request and sent to the network device, and of course, the session type may be carried in the PDU session modification request and sent to the network device in addition to being carried in the PDU session establishment request and sent to the network device in the PDU session modification process. The embodiment of the present application is described herein only by taking the example of carrying the session type in the PDU session establishment request and sending it to the network device, but the embodiment of the present application is not limited thereto.

Further, the PDU session establishment request may further include a session identifier to identify the session; since a session may include multiple flows, the core network device indicates whether a session may allow uplink transmission in the inactive state, or may indicate in units of one flow, that is, indicates whether a flow identifier may allow uplink transmission in the inactive state. In this way, when the core network device sends a PDU session establishment request to the network device, the core network device only needs to add the flow identifier in the PDU session establishment request, so as to indicate whether uplink transmission can be allowed in the inactive state through the flow identifier. At this time, the above session type may also be referred to as a stream type, or collectively referred to as indication information.

S805, the network equipment distributes target configuration parameters for the terminal.

The method for allocating the target configuration parameters to the terminal by the network device may be referred to the related description in the embodiment shown in fig. 4, and the description of the embodiment of the present application is omitted here.

And S806, the network equipment sends the first information to the terminal.

Wherein the first information is used to indicate the target configuration parameter. For example, the first information may be an identifier corresponding to the target configuration parameter, or may be the target configuration parameter itself.

S807, the network device sends a PDU session establishment response to the core network device.

By means of the embodiment shown in fig. 8, the core network device may determine whether to establish a DDT session for a terminal according to subscription data and/or capability information of the terminal, and instruct, when determining to establish a DDT session for the terminal, the network device to establish a session or a certain flow in a session ID for the terminal through a session identifier or a flow identifier, where the instruction information (session type or flow type) is used to instruct the terminal to enable data transmission in an inactive state, and correspondingly, the network device may allocate a target configuration parameter for the terminal according to the instruction information, where the network device may also perform curing processing on radio bearer configuration parameters of a plurality of terminals and/or cell group configuration parameters when allocating the target configuration parameter for the terminal, so that at least two terminals correspond to the same set of configuration parameters, and thus, when the plurality of terminals enter the inactive state from the connected state, only one set of configuration information needs to be stored for the network device, thereby reducing storage overhead of the network device.

The embodiment shown in fig. 8 may be implemented in combination with the embodiment shown in fig. 4 or 5, and of course, the embodiment shown in fig. 8 may be implemented independently, i.e., the embodiment shown in fig. 8 is decoupled from the embodiment shown in fig. 4 or 5 and has no binding relationship.

Based on any of the above embodiments, after receiving the RRC connection release message sent by the network device, the terminal enters an inactive state according to the RRC connection release message. When the terminal is in the inactive state, if the terminal receives a first instruction sent by the network device and used for indicating the terminal to monitor the physical downlink control channel when in the inactive state, the terminal monitors the physical downlink control channel when in the inactive state. Optionally, the first indication may be included in an RRC release message, and of course, may also be carried in other messages, and specifically may be set according to actual needs.

In addition, when the terminal is in the inactive state, the terminal may also receive a second indication for indicating that the terminal is in the inactive state and that uplink transmission is allowed. In an example, the terminal may send a random access request to the network device and receive a response message of the random access request, where the response message includes an uplink grant and a second indication, so that when the terminal needs to perform DRB data transmission, DRB data uplink transmission may be performed on an uplink resource indicated by the uplink grant, which realizes that the terminal completes uplink DRB data transmission in an inactive state, and does not need to wait until RRC connection is restored, and does not need to enter a connection state to send data, thereby not only improving data sending efficiency, but also reducing overhead required for RRC connection restoration.

By any of the above embodiments, after receiving the RRC connection release message sent by the network device, the terminal may enter an inactive state according to the RRC connection release message. After entering the inactive state, if uplink transmission is to be performed, the terminal may send the preamble and the uplink data in the uplink resource indicated by the network device in the random access process, if the network device fails to analyze the uplink data, for the terminal, if the terminal needs to send the uplink data to the network device again, it is necessary to restore RRC connection first, and send the uplink data to the network device again when the network device is in the connected state, so that the network device may accurately receive the uplink data sent by the terminal, where the uplink data is PUSCH data. The uplink data includes RRC signaling and/or uplink DRB data. In order to implement uplink transmission of a terminal in an inactive state, for example, please refer to fig. 9, fig. 9 is a schematic flow chart of a configuration method provided in an embodiment of the present application, where the configuration method may include:

s901, the terminal acquires indication information and uplink resources sent by the network equipment.

The indication information is used for indicating the terminal to enable uplink transmission in the inactive state. Wherein the indication information is optional.

For example, when the terminal obtains the indication information, the indication information may be obtained through an RRC connection release message, or the indication information may be obtained through a broadcast message, and specifically may be set according to actual needs, where the manner of obtaining the indication information is not limited further.

For example, when the terminal acquires the uplink resource, the terminal may acquire the uplink resource in three possible manners. In a possible manner, the terminal may send a preamble to the network device and receive a random access response message sent by the network device, where the random access response may include the uplink resource, so as to obtain the uplink resource. In another possible manner, the terminal may use the uplink resource in the message a (MsgA) of the two-step random access channel (random ACCESS CHANNEL, RACH), and use the uplink resource as the uplink resource to be used, thereby obtaining the uplink resource. It can be appreciated that the uplink resources in the two-step RACH can be acquired through an RRC connection release message or a broadcast message. In another possible implementation manner, the terminal may directly use the uplink resource in the pre-configured PUSCH resource without sending the preamble, and take the uplink resource as the uplink resource to be used, so as to obtain the uplink resource. It can be appreciated that the pre-configured PUSCH resources may be obtained through RRC connection release messages or broadcast messages.

After the indication information and the uplink resource are respectively acquired, uplink transmission cannot be directly performed on the acquired uplink resource, but the uplink data amount to be transmitted is compared with the data amount threshold, and uplink transmission is performed according to the comparison result, that is, the following S902 is performed:

S902, when the terminal performs uplink transmission, a comparison result of the uplink data quantity to be transmitted and a data quantity threshold is obtained.

If the comparison result indicates that the uplink data amount to be transmitted is greater than the data amount threshold, the following steps S903-S904 are executed; if the comparison result indicates that the uplink data amount to be transmitted is smaller than the data amount threshold, the following S905 is executed; if the comparison result indicates that the amount of uplink data to be transmitted is equal to the data amount threshold, S903 to S904 described below, or S905 described below, are performed.

Wherein S902 is optional. The UE may optionally employ S903-S904 described below, or S905 described below.

S903, the terminal sends an RRC connection recovery request to the network device, and does not send uplink data.

And S904, the terminal transmits uplink data by using uplink resources in the contention resolution response when receiving the contention resolution response sent by the network equipment.

S905, the terminal sends the RRC connection recovery request to the network equipment and simultaneously sends uplink data to the network equipment through uplink resources.

For example, when the terminal sends an RRC connection recovery request to the network device, the RRC connection recovery request may carry an indication, where the indication is used to indicate a size relationship between an uplink data amount to be transmitted and a data amount threshold. For example, the indication may be represented by a boolean parameter (or boolean value), e.g. when the boolean value is 1, indicating that the amount of data to be transmitted is greater than the data amount threshold; when the boolean value is 0, it means that the data volume to be transmitted is smaller than the data volume threshold, or vice versa; for the case that the data volume to be transmitted is equal to the data volume threshold, the boolean value may be 0 or 1. Or the indication may be indicated by whether a field exists in the RRC connection resume request, and when the field exists in the RRC connection resume request, the indication indicates that the amount of data to be transmitted is less than the data amount threshold; when the field does not exist in the RRC connection recovery request, the data quantity to be transmitted is larger than a data quantity threshold, otherwise, the field can also be used; this field may or may not be present in the RRC connection resume request for the case where the amount of data to be sent is equal to the data amount threshold. Or the indication may be indicated by an enumerated field in the RRC connection recovery request, where when the field in the RRC connection recovery request is TRUE, it indicates that the amount of data to be sent is less than the data amount threshold; when the field in the RRC connection recovery request is FALSE, it indicates that the amount of data to be sent is greater than the data amount threshold, or vice versa; for the case where the amount of data to be sent is equal to the data amount threshold, the field in the RRC connection recovery request may be TRUE or FALSE. Taking the case that the value is TRUE, which indicates that the uplink data amount to be transmitted is greater than the data amount threshold, and the value is FALSE, which indicates that the uplink data amount to be transmitted is less than or equal to the data amount threshold, in S903, the indication carried in the RRC connection recovery request is TRUE; in S905, the indication carried in the RRC connection recovery request is FALSE. The embodiments of the present application are merely described by way of examples, and may be specifically set according to actual needs. The data volume threshold may be obtained from a broadcast message or a dedicated message sent by the network, or may be a preset value.

Correspondingly, the network device may further perform S906 to S907 described below after receiving the uplink data transmitted by the terminal through S904 or S905.

S906, the network device determines whether to allow uplink transmission on the uplink resource indicated by the uplink grant.

S907, the network device sends, to the terminal, indication information for indicating whether uplink transmission is allowed on an uplink resource indicated by the uplink grant.

If the indication information indicates that uplink transmission is allowed on the uplink resource indicated by the uplink grant, the terminal performs uplink transmission using the uplink resource when uplink transmission is required, and if the indication information indicates that uplink transmission is not allowed on the uplink resource indicated by the uplink grant, the terminal may perform the above-described steps S903 to S904 when uplink transmission is required.

It can be seen that, through the embodiment shown in fig. 9, the terminal sends the RRC connection recovery request to the network device, so that the network device can allocate uplink authorization to the terminal when the terminal is in an inactive state, and indicate whether to allow uplink transmission on the uplink resource indicated by the uplink authorization through the indication information, so that the terminal completes uplink transmission in the inactive state, and can perform uplink transmission without waiting until RRC connection is recovered, and without the terminal entering a connection state to send data, thereby not only improving data sending efficiency, but also reducing the overhead required by RRC connection recovery.

Based on the embodiment shown in fig. 9, taking two-step RACH transmission data as an example, before the terminal transmits uplink data to the network device, the terminal compares the uplink data amount to be transmitted with the data amount threshold, and determines whether to allow uplink transmission on the uplink resource indicated by the uplink grant according to the indication information transmitted by the network device. After the comparison, if the uplink data amount to be transmitted is less than or equal to the data amount threshold, and the terminal determines that uplink transmission can be performed on the uplink resource indicated by the uplink grant, recovering PDCP states of the DRB and the SRB, reconstructing PCDP entities, recovering states of the SRB and the DRB, and sending a first message to the network device, where the first message may include a preamble sent on the PRACH resource, and an RRC connection recovery request and uplink data sent on the PUSCH resource. Correspondingly, after receiving the preamble and PUSCH data sent by the terminal through the first message, the network device analyzes the received preamble and PUSCH data. When analyzing the preamble and the PUSCH data, the method can be divided into two different scenarios, wherein in one scenario, the network device successfully analyzes the preamble, but fails to analyze the PUSCH data; in another scenario, the network device successfully parses the preamble and successfully parses the PUSCH data. Hereinafter, these two different scenarios will be described in detail with reference to the detailed embodiments, respectively.

In a scenario, when the network device successfully parses the preamble but fails to parse the uplink data, as shown in fig. 10, fig. 10 is a schematic flow chart of another configuration method according to an embodiment of the present application, where the configuration method may include:

S1001, the terminal sends a first message to the network equipment.

Wherein the first message comprises a random access request and/or physical uplink shared channel data comprising information for requesting a recovery of a Radio Resource Control (RRC) connection, e.g. an RRC connection recovery request. For example, the random access request may be a preamble, and the physical uplink shared channel data may further include uplink data. Wherein the upstream data is optional.

After the terminal sends the first message to the network device, the network device may parse the preamble and the uplink data included in the first message, and when the network device succeeds in parsing the preamble, but fails in parsing the uplink data, the network device may send a response message of the first message to the terminal according to the parsing result, that is, execute the following S1002:

S1002, the network equipment sends a response message of the first message to the terminal.

The response message comprises uplink grant and first indication information, wherein the first indication information is used for indicating whether uplink transmission is allowed on uplink resources indicated by the uplink grant.

Optionally, the response message of the first message may further include a random access preamble identity (Random Access Preamble Identifier, rapid), a timing advance (TIME ADVANCE, TA) and a temporary cell radio network temporary identity (temporary cell radio network temporary identity, TC-RNTI). Wherein, the rapid is an identifier corresponding to the preamble in S1001, and if the rapid is the same as the identifier corresponding to the preamble sent by the terminal, the terminal confirms that the response message of the first message is the response message sent by the network device for the terminal. The TA indicates an advance of the uplink transmission timing, and is used for the terminal to adjust the uplink transmission timing. The TC-RNTI is an identifier allocated to the terminal by the network equipment, when the competition is solved, the TC-RNTI can be used as the C-RNTI, the network equipment indicates a PUSCH resource through a PDCCH scrambled by the C-RNTI, and the terminal uses the PUSCH resource to send uplink signaling or data. Optionally, the response message of the first message may further comprise an RRC dedicated signaling message, such as an RRC reconfiguration message.

For example, if the terminal determines that the timer is not started when uplink transmission can be performed on the uplink resource indicated by the uplink grant, the terminal starts the timer after receiving a response message of the first message sent by the network device; otherwise, if the terminal determines that the timer is started when uplink transmission can be performed on the uplink resource indicated by the uplink grant, the terminal restarts the timer after receiving the response message of the first message sent by the network device. The timer may be a T319 timer, for example, or may be another new timer.

The duration of the timer is used to define the longest waiting time or the maximum tolerant duration of the RRC connection recovery procedure. For example, when the timer may be a T319 timer, the terminal starts T319 when sending a connection recovery request, and stops T319 when receiving a connection recovery or connection establishment, connection release message sent by the network device; the terminal stops T319 when either it reselects the cell or it receives a higher layer indication from the terminal to exit the RRC connection setup. Otherwise, when T319 times out, the terminal releases the connection to enter an idle state by reason of failure in RRC connection recovery.

It can be seen that, unlike the prior art, in the embodiment of the present application, the response message of the first message sent by the network device to the terminal includes not only the uplink authorization information, but also the first indication information. The content indicated by the first indication information is different, and correspondingly, the uplink transmission modes of the terminal on the uplink resources indicated by the uplink authorization are also different. When the first indication information indicates that the terminal allows uplink transmission on the uplink resource indicated by the uplink grant, the following S1003 may be performed; in contrast, when the first indication information indicates that the terminal does not allow uplink transmission on the uplink resource indicated by the uplink grant, the following S1004 may be performed. The uplink transmission indicated by the first indication information refers to transmission of uplink DRB data.

The first indication information may be explicit indication information, for example, may be 1-bit indication information, and indicates that the terminal is allowed to perform uplink transmission on the uplink resource indicated by the uplink grant when the value of the first indication information is "1", and indicates that the terminal is not allowed to perform uplink transmission on the uplink resource indicated by the uplink grant when the value of the first indication information is "0". Of course, the meaning of the values may be reversed, and will not be further described herein.

Optionally, the response message may not carry the first indication information, that is, the terminal is indicated by an implicit indication manner, for example, when the uplink grant can accommodate all the data to be sent, the terminal performs uplink transmission of the DRB data on the uplink resource indicated by the uplink grant. Otherwise, the terminal does not carry out uplink transmission of the DRB data on the uplink resource indicated by the uplink authorization.

Optionally, the method may also include that the first indication information is carried in the response message when the terminal is allowed to perform uplink transmission on the uplink resource indicated by the uplink grant, and the method does not carry the first indication information in the response message when the terminal is not allowed to perform uplink transmission on the uplink resource indicated by the uplink grant, so as to indicate whether the terminal can use the uplink grant.

S1003, the terminal sends a second message to the network equipment on the uplink resource.

The second message includes uplink data and an RRC connection recovery request.

In S1003, when the first indication information indicates that the terminal allows uplink transmission on the uplink resource indicated by the uplink grant, the terminal may perform uplink transmission on the uplink resource indicated by the received uplink grant.

S1004, the terminal sends a third message to the network equipment on the uplink resource.

And when the first indication information indicates that the terminal does not allow uplink transmission on the uplink resource indicated by the uplink grant, the third message sent by the terminal on the uplink resource indicated by the uplink grant is only used for requesting to recover the RRC connection and does not include uplink DRB data. For example, the third message may be an RRC connection resume request.

In combination with the descriptions in S1003 and S1004, the network device, after receiving the second message or the third message sent by the terminal, sends contention resolution information to the terminal, that is, performs the following S1005:

S1005, the network device transmits contention resolution information to the terminal.

For example, the contention resolution information may be an identification of the terminal, or partial information of the second message, or partial information of the third message.

It will be appreciated that the timer is not always running after being started or restarted, but is stopped under certain conditions, such as the scenario of stopping the timer described above. For example, when the terminal receives a Radio Resource Control (RRC) connection release message from the network device, the control timer stops running, i.e., the timer is stopped. The terminal may also stop the timer when the terminal receives a Radio Resource Control (RRC) connection resume, a connection setup message, etc. from the network device.

It can be seen that, in the embodiment shown in fig. 10, the first message sent by the terminal to the network device includes a preamble, an RRC connection recovery request, and uplink data, and of course, the terminal may also not carry uplink data in the first message, but carry a second indication information, where the second indication information is used to indicate a comparison result between a data amount to be sent by the terminal and a data amount threshold, in this case, when the network device successfully parses the preamble, but fails to parse the uplink data, as shown in fig. 11, for example, fig. 11 is a flow chart of another configuration method provided in the embodiment of the present application, and the configuration method may include:

s1101, the terminal sends a first message to the network device.

Wherein the first message comprises a random access request and/or physical uplink shared channel data comprising information for requesting a recovery of a Radio Resource Control (RRC) connection, e.g. an RRC connection recovery request. For example, the random access request may be a preamble, and the physical uplink shared channel data may further include second indication information, where the second indication information is used to indicate a comparison result of the data amount to be sent by the terminal and the data amount threshold. Wherein the second indication information is optional.

It may be appreciated that when the terminal sends the first message including the second indication information to the network device, in one case, when the first message is an RRC connection resume request, the second indication information may be represented by a boolean value in the RRC connection resume request, for example, when the boolean value is 1, it indicates that the amount of data to be sent is greater than the data amount threshold; when the boolean value is 0, it indicates that the data volume to be transmitted is smaller than the data volume threshold, or vice versa; for the case where the amount of data to be transmitted is equal to the data amount threshold, the boolean value may be 0 or 1. Or the second indication information may indicate whether a field exists in the RRC connection recovery request, and when the field exists in the RRC connection recovery request, for example, TRUE, the second indication information indicates that the amount of data to be sent is less than the data amount threshold; when the field, for example NULL, does not exist in the RRC connection recovery request, it indicates that the amount of data to be sent is greater than the data amount threshold, and vice versa; this field may or may not be present in the RRC connection resume request for the case where the amount of data to be sent is equal to the data amount threshold. Or the second indication information can be represented by an enumeration field in the RRC connection recovery request, and when the field in the RRC connection recovery request is TRUE, the second indication information indicates that the amount of data to be sent is less than the data amount threshold; when the field in the RRC connection recovery request is FALSE, it indicates that the amount of data to be sent is greater than the data amount threshold, or vice versa; for the case where the amount of data to be sent is equal to the data amount threshold, the field in the RRC connection recovery request may be TRUE or FALSE.

In another case, when the first message is a MAC message, the MAC message is, for example, a MAC sub-PDU, which may include only a MAC header, or include an MAC header and an MAC CE, as an example, please refer to fig. 12, and fig. 12 is a schematic structural diagram of a MAC message provided in an embodiment of the present application. The MAC message only comprises an MAC header, the MAC header comprises a logic channel identification (LCH ID), and the LCH ID takes a preset value to indicate that the MAC header value carries second indication information. The second indication information may be implemented by an indication field in the MAC header, e.g. by means of a bit R reserved before. When the value of the R bit is 1, the data quantity to be transmitted is larger than a data quantity threshold; when the value of the R bit is 0, the data quantity to be sent is smaller than a data quantity threshold, otherwise, the R bit can be also used; when the data size to be transmitted is equal to the data size threshold, the value of the R bit may be 0 or 1.

For example, please refer to fig. 13, fig. 13 is a schematic diagram of another MAC message structure according to an embodiment of the present application. The MAC message includes a MAC header and a MAC CE, a field in the MAC CE carrying second indication information. The MAC header includes an LCH ID, which takes a preset value to indicate that the MAC CE carries the second indication information. Taking the example that a 1-bit field 1 in the MAC CE carries the second indication information, the value of the field 1 is 1, which indicates that the data volume to be sent is larger than a data volume threshold; the value of the field 1 is 0, which indicates that the data volume to be sent is smaller than the data volume threshold, otherwise, the data volume to be sent can also be the same; when the data volume to be transmitted is equal to the data volume threshold, the value of the field 1 may be 0 or 1.

It may be understood that, when the terminal sends the first message including the second indication information to the network device, the embodiment of the present application is only described by taking the first message as an example, where the first message may be an RRC connection restoration request message or an MAC message, and specifically may be set according to actual needs, and the embodiment of the present application is not limited further herein.

After the terminal sends the first message including the second indication information to the network device, the network device may parse the preamble and the physical uplink shared channel data included in the first message, and when the network device succeeds in parsing the preamble but fails in parsing the physical uplink shared channel data, the network device may send a response message of the first message to the terminal according to the parsing result, that is, execute the following S1102:

and S1102, the network equipment sends a response message of the first message to the terminal.

The response message comprises uplink grant and first indication information, wherein the first indication information is used for indicating whether uplink transmission is allowed on uplink resources indicated by the uplink grant. For example, the response message of the first message may be an RRC dedicated signaling message, such as an RRC connection release message or an RRC reconfiguration message.

The first indication information is the same as the above description and will not be repeated here.

It should be noted that, the method for the network device to send the response message of the first message to the terminal is similar to the method for the network device to send the response message of the first message to the terminal in S1002, which can be referred to the related description in S1002, and the embodiments of the present application will not be repeated here.

It can also be seen that, unlike the prior art, in the embodiment of the present application, the response message of the first message sent by the network device to the terminal includes not only the uplink grant information, but also the first indication information. The content indicated by the first indication information is different, and correspondingly, the uplink transmission modes of the terminal on the uplink resources indicated by the uplink authorization are also different. When the first indication information indicates that the terminal allows uplink transmission on the uplink resource indicated by the uplink grant, the following S1103 may be executed; in contrast, when the first indication information indicates that the terminal does not allow uplink DRB data transmission on the uplink resource indicated by the uplink grant, S1104 described below may be performed.

And S1103, the terminal sends a second message to the network equipment on the uplink resource.

The second message includes uplink data and an RRC connection recovery request.

In S1103, when the first indication information indicates that the terminal allows uplink transmission on the uplink resource indicated by the uplink grant, the terminal may perform uplink DRB data transmission on the received uplink resource indicated by the uplink grant.

And S1104, the terminal sends a third message to the network equipment on the uplink resource.

And when the first indication information indicates that the terminal does not allow uplink transmission on the uplink resource indicated by the uplink grant, the third message sent by the terminal on the uplink resource indicated by the uplink grant is only used for requesting to recover the RRC connection and does not include uplink data. For example, the third message may be an RRC connection resume request.

In combination with the descriptions in S1103 and S1104, the network device, after receiving the second message or the third message sent by the terminal, sends contention resolution information to the terminal, that is, performs the following S1105:

s1105, the network device transmits contention resolution information to the terminal.

It can be seen that the embodiments shown in fig. 10 and fig. 11 above describe in detail the technical solution in one scenario when the network device successfully parses the preamble, but fails to parse the uplink data; in the following, in another scenario, when the network device successfully parses the preamble and successfully parses the uplink data, as shown in fig. 14, for example, fig. 14 is a schematic flow chart of another configuration method provided in the embodiment of the present application, the configuration method may include:

S1401, the terminal sends a first message to the network device.

The first message includes a random access request and/or physical uplink shared channel data, and the physical uplink shared channel data includes information for requesting to recover the RRC connection.

It should be noted that, the method for the terminal to send the first message to the network device is similar to the method for the terminal to send the first message to the network device in S1001 or S1101, which can be referred to the related description in S1001 or S1101, and the embodiments of the present application will not be repeated here.

After the terminal sends the first message to the network device, the network device may parse the preamble and the physical uplink shared channel data included in the first message, and when the network device successfully parses the preamble and the physical uplink shared channel data, the network device may send a response message of the first message to the terminal according to the parsing result, that is, execute the following S1402:

s1402, the network device sends a response message of the first message to the terminal.

Wherein the response message includes contention resolution information. Optionally, the response message of the first message may further include RAPID, TA, and TC-RNTI.

In addition, the response message of the first message may not include the uplink resource and the first indication information; of course, the response message of the first message may also include the uplink resource and the first indication information.

When the response message is an RRC connection release message, the terminal resumes an initial state, e.g., an inactive state.

When the response message of the first message does not carry uplink resources and first indication information, the terminal determines that the contention resolution passes after receiving the response message, and starts or restarts a timer to convert the TC-RNTI into the C-RNTI. When the response message of the first message carries the uplink resource and the first indication information, and the first indication information is used for indicating that the uplink transmission is not allowed on the uplink resource indicated by the uplink authorization, the corresponding terminal determines that the contention resolution passes after receiving the response message, and starts or restarts the timer. At this time, the terminal may send an acknowledgement response of the response message to the network device on the uplink resource. When the response message of the first message carries the uplink resource and the first indication information, and the first indication is used for indicating that the uplink transmission is allowed on the uplink resource indicated by the uplink authorization, the corresponding terminal determines that the contention resolution passes after receiving the response message, and starts or restarts the timer. At this time, the terminal may send uplink data to the network device on the uplink resource.

It can be understood that after the terminal receives the response message of the contention resolution information from the network device, it indicates that the network device has successfully received the physical uplink shared channel data transmitted by the terminal. If the terminal has uplink data to be transmitted at this time, the terminal may further perform the following S1403-S1404:

S1403, an uplink grant is received from the network device.

S1404, uplink transmission is performed on the uplink resource indicated by the uplink grant.

After receiving the contention resolution information, if the terminal does not receive the RRC connection release message at the moment, the terminal starts or restarts a timer, and receives authorization from the network device during the running of the timer, wherein the authorization is used for uplink data transmission or downlink data reception; optionally, the grant is for a new transmission, not for a retransmission; the grant may be an uplink grant or a downlink grant, and when the grant is received, the timer is restarted, thereby delaying the duration of the terminal listening for the grant. For example, if the uplink grant is received from the network device, the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink grant; if the downlink grant is received from the network device and the RRC connection release message is not received, which indicates that the network device has data to transmit, the terminal starts or restarts the timer. The terminal prolongs the time waiting for the RRC connection release message in the above manner, realizes the data transmission of the terminal in the inactive state, and can perform uplink transmission without waiting until the RRC connection is restored, and does not need the terminal to enter the connection state to transmit data, thereby not only improving the data transmission efficiency, but also reducing the cost required by the RRC connection restoration.

It will be appreciated that in the embodiments shown in fig. 10, 11 and 14 described above, the timer is not always running after being started or restarted, but is stopped under certain conditions, such as the scenario described above for stopping the timer. For example, when the terminal receives a radio resource control RRC connection release message from the network device, the control timer stops running, i.e. the timer is stopped. The terminal may also stop the timer when the terminal receives a Radio Resource Control (RRC) connection resume, a connection setup message, etc. from the network device.

In the embodiments shown in fig. 10, 11 and 14, during the timer running, the terminal listens to the C-RNTI scrambled PDCCH, which indicates PUSCH resources for transmitting uplink data or BSR. Or during the running of the timer, the terminal monitors a PDCCH scrambled by the C-RNTI, wherein the PDCCH indicates PDSCH resources for receiving downlink data. Or during the running period of the timer, the terminal monitors the PDCCH scrambled by the C-RNTI and receives the downlink feedback of the uplink data.

And starting or restarting a timer when the terminal receives the uplink grant or the downlink grant of the C-RNTI scrambled PDCCH each time so as to keep monitoring the duration of the C-RNTI scrambled PDCCH, keeping synchronous with the transmission time of the C-RNTI scrambled PDCCH of the network equipment, and stopping monitoring the C-RNTI scrambled PDCCH when the timer is overtime.

In addition, in the prior art, when the network device has downlink data to be sent, the terminal will be paged first, and after receiving the paging, the terminal will initiate a random access procedure to the network device, and then, the terminal can receive the downlink data sent by the network device. For the terminal in the non-connection state, in the small and sparse data transmission scene, the terminal needs to execute the random access process to transmit small data, so that the overhead of the terminal is large, and the transmission delay is increased. In order to reduce the overhead of the terminal and reduce the transmission delay, the embodiment of the present application further provides a configuration method, for example, please refer to fig. 15, fig. 15 is a flow chart of a configuration method provided in the embodiment of the present application, and the configuration method may include:

S1501, the network device sends instruction information to the terminal.

The indication information is used for indicating the terminal to monitor a Physical Downlink Control Channel (PDCCH) when the terminal is in an inactive state.

Optionally, the network device may send an RRC connection release message to the terminal, where the RRC connection release message includes indication information, that is, the network device may send the indication information to the terminal with the RRC connection release message, and the terminal may obtain the indication information by receiving the RRC connection release message. It can be understood that after receiving the RRC connection release message, the terminal enters a non-active state from the connection state, and monitors the PDCCH in the non-active state according to the indication information, so that the terminal can be configured with the function of monitoring the PDCCH when the terminal is in the non-active state independently, and the function configuration is performed while the terminal is configured to enter the non-active state, without additional signaling to indicate separately, and signaling is saved. The network device may also send the indication information in other manners, for example, the indication information is carried in a broadcast message to be broadcast, and the corresponding terminal may obtain the indication information by receiving the broadcast message, so that it is not necessary to monitor the PDCCH when each terminal is in an inactive state separately. The embodiments of the present application are described herein by way of example only, and are not intended to be limiting.

For example, the indication information may be implemented by a bit, for example, the bit has a value of 1, which indicates that a function of listening to a Physical Downlink Control Channel (PDCCH) scrambled by the C-RNTI is enabled in the inactive state, and the bit has a value of 0, which indicates that a function of listening to the Physical Downlink Control Channel (PDCCH) is not enabled in the inactive state. Alternatively, the indication information may be implemented by enumeration, for example: { TURE }, { downlink reception }. Since the PDCCH is scrambled by a cell radio network temporary identity (C-RNTI), in another implementation, the indication information may be a C-RNTI, for example, when the RRC connection release message carries the C-RNTI, the terminal is instructed to monitor the C-RNTI scrambled PDCCH in an inactive state; and when the RRC connection release message does not carry the C-RNTI, the terminal is indicated not to monitor the PDCCH in the inactive state.

After receiving the indication information sent by the network equipment, the terminal can determine the C-RNTI of the scrambling PDCCH, and then monitor the C-RNTI scrambled PDCCH by using the C-RNTI.

In one implementation, the network device may send the C-RNTI to the terminal in an RRC connection release message, where the RRC connection release message may include the indication information and the C-RNTI, or include the C-RNTI, which is the indication information, as described above.

The C-RNTI is valid in an access network notification area (RAN notification area, RNA) or indicated cell or in a current access cell. For example, the network device may indicate the RNA to which the C-RNTI corresponds, where the C-RNTI corresponds to the RNA may be one or more, e.g., the network device indicates the RNA Identity (ID) or RNA ID list to which the C-RNTI corresponds, which RAN ID or RAN ID list may also be carried in the RRC connection release message, or in other messages. For another example, the network device may indicate a cell ID or a cell ID list corresponding to the C-RNTI, which may also be carried in the RRC connection release message or in another message. In this way, the terminal may monitor the PDCCH using the C-RNTI in the RAN area indicated by the RAN ID or the cell indicated by the cell ID. The C-RNTI may be considered valid within the current access cell, which is the cell sending the RRC connection release message, when the network device does not indicate an RNA or cell. In another implementation, the network device may not send the C-RNTI to the terminal, at which time the terminal may monitor the PDCCH scrambled by the C-RNTI by using the C-RNTI acquired during random access to the current access cell. The current access cell is a cell that transmits an RRC connection release message.

After receiving the indication information and determining the C-RNTI of the scrambled PDCCH, the terminal may monitor the C-RNTI scrambled PDCCH according to the indication information, i.e. execute the following S1502:

s1502, the terminal monitors the PDCCH scrambled by the C-RNTI according to the indication information.

The timing of the terminal listening to the PDCCH is described below. For example, in determining the opportunity to monitor the PDCCH, the opportunity to monitor the PDCCH may be determined from both the time domain and the frequency domain dimensions.

When determining the opportunity of monitoring the PDCCH in terms of time domain, the terminal can take the paging opportunity as the opportunity of monitoring the C-RNTI scrambled PDCCH. Specifically, the terminal receives the DRX configuration parameter, and determines paging time according to the discontinuous reception (discontinuous reception, DRX) configuration parameter, namely, monitors the time of the PDCCH scrambled by the paging radio network temporary identifier (paging radio network temporary identifier, P-RNTI); and takes the paging occasion as the occasion of monitoring the C-RNTI scrambled PDCCH. For example, referring to fig. 16, fig. 16 is a schematic diagram of determining an opportunity to monitor a PDCCH scrambled by a C-RNTI according to an embodiment of the present application. Optionally, part of the time in the paging occasion may be determined as the occasion of monitoring the PDCCH scrambled by the C-RNTI, and may specifically be set according to actual needs.

For example, when determining the paging occasion according to the DRX configuration parameter, a radio frame of the paging may be determined, i.e. a system frame number (SYSTEM FRAME number, SFN) is determined, where (sfn+pf_offset) mod t= (tdiv N) ×terminal_id mod N; and determining an i_s-th paging occasion in the radio frame, wherein i_s=floor (terminal_id/N) mod Ns. Where T denotes a DRX cycle of the terminal, N denotes a paging frame number in the DRX cycle, ns denotes a paging occasion number in the paging frame, pf_offset denotes an offset value for determining a paging radio frame, and terminal_id is a terminal identity, which is different in different communication systems, for example, in a 5G system, which is 5G-S-TMSI mod 1024. It will be appreciated that T, N, ns, PF _offset may be terminal-specific to the network device. For example, configured to the terminal through a broadcast message or configured to the terminal through an RRC dedicated message.

After determining the paging occasion of listening to P-RNTI PDCCH in the radio frame according to the DRX configuration parameters, the C-RNTI scrambled PDCCH may be listened to in all paging occasions or part of the time of the paging occasion. The C-RNTI scrambled PDCCH may be monitored at a partial duration of each paging occasion when the C-RNTI scrambled PDCCH is monitored at a partial time of the paging occasion, or the C-RNTI scrambled PDCCH may be monitored at a partial paging occasion.

The following describes, with reference to the accompanying drawings, monitoring the PDCCH scrambled by the C-RNTI for a part of the duration of each paging occasion, and for example, please refer to fig. 17, fig. 17 is a schematic diagram of another determination of the timing of monitoring the PDCCH scrambled by the C-RNTI according to an embodiment of the present application. As shown in connection with fig. 17, the hatched portion in fig. 17 is the opportunity to listen to the C-RNTI-scrambled PDCCH. The opportunity to monitor the C-RNTI scrambling PDCCH may be determined based on a parameter, which may be configured by the network device to the terminal or preset. For example, each paging occasion is N slots or symbols, which is used to indicate PDCCHs in which M slots or symbols are used to listen to C-RNTI scrambling. In one implementation, the parameter is used to indicate M, and the terminal defaults to the first M or last M slots or symbols for listening to the C-RNTI scrambled PDCCH. In another implementation, the parameter is used to indicate the S-th slot or symbol, and the terminal starts to monitor the C-RNTI-scrambled PDCCH from the S-th slot or symbol or starts to monitor the C-RNTI-scrambled PDCCH from the S-th slot or symbol. Wherein M, N, S are positive integers, and M and S are smaller than N.

When the PDCCH is monitored at a part of paging occasions, the occasions of monitoring the PDCCH scrambled by the C-RNTI can be determined in a similar manner to the above determination of paging occasions, for example, T in the above determination of SFN formula is modified to T1, wherein T1 is an integer multiple of T, i.e., (sfn+pf_offset) mod t= (T1 div N) (terminal_id mod N); the manner in which the paging occasions i_s in the radio frame are determined is unchanged.

Furthermore, the two modes above, i.e. listening to the C-RNTI scrambled PDCCH at part of the time of part of the paging occasion, can also be combined. For example, referring to fig. 18, fig. 18 is a schematic diagram of determining a timing of listening to a PDCCH scrambled by a C-RNTI according to an embodiment of the present application. As shown in connection with fig. 18, the hatched portion in fig. 18 is the opportunity to listen to the C-RNTI-scrambled PDCCH.

Alternatively, in another possible implementation, the determination of the timing to listen to the C-RNTI scrambled PDCCH and the determination of the paging timing are independent. For example, the timing of listening to the C-RNTI scrambled PDCCH may be determined in a similar manner as the paging occasion is determined, except that the parameters used are different, e.g., the PF_offset used is different. For example, when determining an opportunity to listen to the C-RNTI scrambled PDCCH according to the DRX configuration parameters, an SFN of the radio frame may be determined, where (sfn+pf_offset 1) mod t= (tdiv N) (terminal_id mod N); and determining the i_s-th listening occasion in the radio frame, and i_s=floor (terminal_id/N) mod Ns. Where T denotes a DRX cycle of the terminal, N denotes a paging frame number in the DRX cycle, ns denotes a paging occasion number in the paging frame, pf_offset1 denotes an offset value for determining a C-RNTI PDCCH radio frame, and terminal_id is a terminal identity, which is different in different communication systems, for example, in a 5G system, which is 5G-S-TMSI mod 1024. It will be appreciated that T, N, ns, PF _offset1 may be terminal-specific to the network device. For example, configured to the terminal through a broadcast message or configured to the terminal through an RRC dedicated message. Wherein pf_offset1 and an offset value pf_offset for determining a paging radio frame may be independently configured. So that the opportunity to listen to the C-RNTI scrambled PDCCH is independent of the paging opportunity to listen to the P-RNTI scrambled PDCCH. For example, referring to fig. 19, fig. 19 is a schematic diagram of determining a timing of listening to a PDCCH scrambled by a C-RNTI according to an embodiment of the present application.

In another possible implementation manner, the terminal may determine the SFN of the paging radio frame first, and then determine, according to the parameters, the radio frame of the PDCCH that listens to the C-RNTI scrambling, where the determination of the SFN of the paging radio frame is as described above, i.e., (sfn+pf_offset) mod t= (tdiv N) (terminal_id mod N); then, the terminal determines the SFN of the radio frame (also called C-RNTI PDCCH radio frame) of the PDCCH scrambled by the C-RNTI according to the offset value, where the offset value is the pf_offset2 identifier, and the C-RNTI PDCCH radio frame=paging radio frame+pf_offset2, where the pf_offset2 may be configured to the terminal by the network device, or may be a preset value. The terminal may then determine the occasion of listening to the C-RNTI-scrambled PDCCH within the C-RNTI PDCCH radio frame, i.e., the listening occasion, in the same manner as described above for the i_s-th paging occasion. For example, see fig. 19.

In addition, when the terminal moves out of the effective area of the C-RNTI, the monitoring of the PDCCH scrambled by the C-RNTI can be stopped.

Therefore, in the embodiment of the application, the network device sends the indication information to the terminal to indicate the terminal to monitor the PDCCH scrambled by the C-RNTI when the terminal is in the inactive state, so that the terminal can receive the downlink data in the process of monitoring the PDCCH scrambled by the C-RNTI.

In a wireless communication system, for example, a 5G communication system or an LTE communication system, after a terminal accesses a cell, a network device to which the cell belongs generates a context of the terminal, and the terminal also generates the context of the terminal according to a configuration message sent by the network device. After the RRC state of the terminal changes, the network device may process the terminal context. For example, the terminal transitions from an RRC connected state (abbreviated as connected state) to an RRC idle state (abbreviated as idle state), and the network device releases the context of the terminal. For another example, when the terminal transitions from the connected state to the inactive state, the terminal and the network device save a configuration of part of the access stratum (referred to as a context of the access stratum terminal) and a configuration of the non-access stratum (referred to as a context of the non-access stratum terminal). The terminal may periodically initiate an access network notification area update (RAN-based Notification Area Update, R-NAU) procedure to the network device informing the network device of the access network notification area (RAN-based Notification Area, RNA) in which the terminal is located. When the terminal in the inactive state reselects to a new cell, an R-NAU process is initiated to the network equipment to which the new cell belongs, and the RNA in which the terminal of the network equipment is located is informed.

And when the network equipment receives the downlink data of the terminal, paging the terminal in the cell of the RNA where the terminal is located. After receiving the paging, the terminal initiates a state transition process from an inactive state to a connection state, the network equipment informs the terminal to restore the stored configuration of the access layer, and after the terminal enters the connection state, the network equipment sends downlink data to the terminal. When the terminal has uplink data to be sent, the terminal initiates a state transition process from an inactive state to a connection state, the network equipment informs the terminal to restore the stored configuration of the access layer, and the terminal sends the uplink data after entering the connection state.

In the state transition process from the inactive state to the connected state, the terminal needs to send an RRC connection resume (resume) request message to the network device, in order to detect whether RRC connection resume is successful, a T319 timer is introduced, the terminal starts the T319 timer, sends the RRC connection resume request message to the network device, and stops the T319 timer when receiving an RRC response message such as an RRC connection resume, an RRC connection setup, or an RRC connection release message sent by the network device. When T319 expires, the terminal releases the connection into an idle state for the reason of failure in RRC connection recovery.

For a scenario that a terminal has a small amount of data transmission, uplink data transmission can be performed in an inactive state. For example, the terminal transmits uplink data to the network device while transmitting an RRC connection resume (resume) request message. In the above embodiment, after the terminal in the inactive state has been given to send the "RRC connection resume request" message, the terminal may continue to send data subsequently, and may not carry the RRC connection resume request message when sending data subsequently, so as to reduce signaling overhead. However, when the terminal transmits the subsequent data, if the T319 timer is overtime, the terminal will enter the RRC idle state, and cannot flexibly support multiple data transmission.

In the embodiments shown in fig. 10, 11 and 14, the terminal may restart the T319 timer under a certain condition, so that the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be prolonged, and multiple data transmission can be flexibly supported. Of course, a new timer may be started, for example, the new timer may be an RRC layer timer or a MAC layer timer other than the T319 timer, so that the terminal starts the new timer under a certain condition and performs data transmission during the operation of the new timer, which also can prolong the time of the terminal waiting for the RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission. For example, referring to the method provided by the embodiment of the present application, when the terminal shall meet the requirement of RRC connection recovery, the terminal starts a first timer and sends an RRC connection recovery request message to the network device; thus, during the operation of the first timer, the terminal can restart the first timer according to the downlink information received from the network device or according to the data transmission with the network device; or during operation of the first timer, the terminal may start the second timer based on downstream information received from the network device or based on data transmission with the network device. It can be seen that, in the embodiment of the present application, by restarting the first timer or starting the second timer, so that data transmission is performed during the operation of the first timer or the second timer, the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively prolonged, so that multiple data transmission is flexibly supported.

Based on the above description, it is apparent that the configuration method provided by the embodiment of the present application may include at least two possible scenarios. In one possible scenario, when the terminal should meet the requirement of RRC connection recovery, it starts a first timer, and meets a restart condition during the operation of the first timer, and restarts the first timer to prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request. It can be seen that in this possible scenario, when the restart condition is met, the restarted timer is the same as the timer started when the need for RRC connection recovery is met, both are the first timers. In another possible scenario, the terminal starts a first timer when the need for RRC connection recovery is met, and starts a second timer when the start condition is met during operation of the first timer, so as to extend the time for the terminal to wait for an RRC response message of an RRC connection recovery request. It can be seen that in this possible scenario, when the restart condition is met, the restarted timer is not one timer, but a new timer is additionally set, as compared to when the need for RRC connection recovery is met. It will be appreciated that in this possible scenario, the first timer may also be stopped after the second timer is started; of course, the first timer may be stopped first, then the second timer may be started, or the first timer may be stopped while the second timer is started. Thus, the first timer is replaced with the second timer to extend the time for the terminal to wait for the RRC response message of the RRC connection resume request.

It should be noted that the description of the two possible scenarios may be understood as a scheme when the first extension operation is performed by the first timer or the second timer. For the first timer in the first possible implementation manner, the terminal sends an RRC connection restoration request message to the network device, starts the first timer, and restarts the first timer to perform the first extension operation when the restart condition is met; the second extension operation, or the third extension operation, … … may be performed subsequently. In the following M (M is greater than or equal to 1) th extension operation, the terminal may directly transmit uplink data without transmitting an RRC connection resume request message to the network device, and restart the first timer when the restart condition is satisfied, so as to extend the time for the terminal to wait for the RRC response message of the RRC connection resume request. For the second timer in the second possible implementation manner, the terminal sends an RRC connection restoration request message to the network device, and starts the first timer; when the starting condition is met, starting the second timer to execute the first extension operation; and then a second extension operation, or a third extension operation … …, may be performed when the restart conditions are met. In the following M (M is greater than or equal to 1) th extension operation, the terminal may directly transmit uplink data without transmitting an RRC connection resume request message to the network device, and start or restart the second timer when a start or restart condition is satisfied, so as to extend the time for the terminal to wait for an RRC response message of the RRC connection resume request.

In order to facilitate understanding of the configuration method provided by the embodiment of the present application, the configuration method provided by the embodiment of the present application will be described in detail below with respect to the above two possible scenarios respectively.

First, for the first possible scenario described above, that is, when the terminal should meet the requirement of RRC connection recovery, the first timer is started, and the restart condition is met during the operation of the first timer, and the first timer is restarted, so as to prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request. For example, in such a possible scenario, at least three possible implementations may be included as follows when the time for the terminal to wait for the RRC response message of the RRC connection resume request is prolonged by restarting the first timer. In one possible implementation manner, the first timer may be a T319 timer configured by the current network, that is, when the terminal should meet the requirement of RRC connection recovery, the terminal starts the T319 timer first, and sends an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may restart the T319 timer according to downlink information received from the network device or according to data transmission with the network device. In another possible implementation manner, the first timer may be additionally set by the RRC layer, and a new timer T1 other than the T319 timer is set, that is, when the terminal needs to recover the RRC connection, the new timer T1 is started first, and an RRC connection recovery request message is sent to the network device; thus, during the operation of the new timer T1, the terminal may restart the new timer T1 based on the downlink information received from the network device or based on data transmission with the network device. In another possible implementation manner, the first timer may be a new timer T2 other than the T319 timer, unlike the timer T1 in the second possible implementation manner, the new timer T2 is a timer set in the MAC layer, that is, the terminal starts the new timer T2 first when the terminal should request for RRC connection recovery, and sends an RRC connection recovery request message to the network device; thus, during the operation of the new timer T2, the terminal may restart the new timer T2 based on the downlink information received from the network device or based on data transmission with the network device. In the following, how to flexibly support multiple data transmission by controlling the first timer to restart to extend the time for the terminal to wait for the RRC response message of the RRC connection resume request will be described in detail for the three possible implementations, respectively.

In a first possible implementation manner, the first timer may be a T319 timer configured by the current network, that is, when the terminal should meet the requirement of RRC connection recovery, the terminal starts the T319 timer first, and sends an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may restart the T319 timer according to downlink information received from the network device or according to data transmission with the network device. It should be noted that, in this possible implementation manner, it will be described by taking an example that, during operation of the T319 timer, the terminal may restart the T319 timer according to the downlink information received from the network device, and of course, during operation of the T319 timer, the T319 timer may also be restarted according to data transmission with the network device. For example, referring to fig. 20, fig. 20 is a flowchart of a configuration method according to an embodiment of the present application, where the configuration method may include:

s2001, when the terminal meets the RRC connection recovery requirement, it starts a T319 timer.

The terminal configures the duration of the T319 timer before starting the T319 timer, so that the T319 timer can be operated based on the configured duration. For example, when configuring the duration of the T319 timer, the terminal may receive a broadcast message or an RRC message from the network device, and configure the duration of the T319 timer according to information indicating the duration of the T319 timer included in the broadcast message or the RRC message. The duration of the T319 timer may be a first duration of the T319 timer of the current network configuration, for example, the first duration may be a value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms }, or may be greater than a second duration of the T319 timer of the current network configuration, which may be configured by a broadcast message or an RRC message, for example, the second duration may be a value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms,2500ms }, for example, the second duration may be 2500ms. Since the T319 timer is restarted when the restart condition is satisfied, the time for the terminal to wait for the RRC response message of the RRC connection resume request can be effectively prolonged for both of the two durations. It can be understood that when the configuration duration of the T319 timer becomes longer, the time for the terminal and the network device to perform data transmission becomes longer, so that the terminal network device can perform multiple data transmissions.

When the T319 timer is configured with the two different durations, it is determined which duration the T319 timer takes, i.e., the first duration or the second duration, before starting the timer. And determining which duration is adopted by the T319 timer, and determining that the duration of the T319 timer adopts a second duration if the terminal meets one of the following conditions. The method comprises the following steps that 1, a terminal expects continuous uplink data transmission in an inactive state; condition 2: the terminal can not send out uplink data at one time in a non-activated state; 3, the data quantity to be sent by the terminal is larger than a pre-configured threshold; the terminal supports the uplink data transmission in the inactive state; condition 5, the terminal is configured with a T319 timer of duration 2. In this case, after determining that the duration of the T319 timer adopts the second duration, the terminal may optionally further send an indication information to the network device, where the indication information is used to indicate to the network device that the duration of the T319 timer started by the terminal is the second duration, so as to synchronize the information that the T319 timer has been started to the network device. It will be appreciated that the operation of synchronizing the information that the terminal has started the T319 timer to the network device by the indication information may be performed only when the start operation is first performed, and in the subsequent restart operation, the terminal may not need to send the indication information to the network device any more.

S2002, the terminal sends RRC connection recovery request information to the network equipment.

For example, the RRC connection recovery request message may include at least one of an I-RNTI, authentication information of the terminal, and a cause value of the UE initiating the RRC connection recovery request. Wherein, I-RNTI is used to represent the unique identification of the terminal in an RNA range. The authentication information of the terminal is generated according to the C-RNTI and the RRC integrity key stored by the terminal.

When the terminal sends the RRC connection recovery request message to the network equipment, the terminal can send the RRC connection recovery request message to the network equipment through the uplink resource indicated by the configuration authorization information. For example, the configuration authorization information may be obtained from a broadcast message of the network device, or may be obtained from a dedicated message sent by the network device to the terminal. For example, the terminal may transmit at least one of uplink data, auxiliary information, and indication information that it is desired to keep transmitting data continuously in an inactive state to the network device, in addition to transmitting the RRC connection restoration request message to the network device. The auxiliary information is used for indicating the data quantity in the terminal cache so that the network equipment determines that the terminal enters a connection state or continues to be in an inactive state according to the data quantity in the terminal cache. When the terminal transmits uplink data to the network device, the uplink data is transmitted together with the RRC connection restoration request message or independently. The co-transmission or independent transmission in the present application refers to whether the uplink data and the RRC connection recovery request message are transmitted through the same message, for example, a MAC PDU message, and if the uplink data and the RRC connection recovery request message are transmitted through the same message, it can be understood that the uplink data and the RRC connection recovery request message are transmitted together; in contrast, if the uplink data and the RRC connection recovery request message are not transmitted through the same message, it can be understood that the uplink data and the RRC connection recovery request message are transmitted independently. Further, if the uplink data is transmitted independently of the RRC connection restoration request message, the uplink data may be transmitted during the first timer operation period after the RRC connection restoration request message is transmitted.

After the terminal sends the RRC connection restoration request message to the network device, the network device may correspondingly send corresponding downlink information to the terminal according to the RRC connection restoration request message, i.e. execute the following S2003:

And S2003, the network equipment sends downlink information to the terminal according to the RRC connection recovery request message.

If the terminal only sends the RRC connection recovery request message to the network device, the downlink information sent by the network device to the terminal includes feedback information of the RRC connection recovery request message. If the terminal sends the RRC connection recovery request message and the uplink data to the network device, the downlink information sent by the network device to the terminal comprises the RRC connection recovery request message and the feedback information of the uplink data.

For example, if the terminal only sends the RRC connection restoration request message to the network device, the downlink information may include at least one of the following: feedback information of the RRC connection recovery request message, a timing adjustment command, a power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of the newly added field. The indication information is used to instruct the terminal to restart the T319 timer, and of course, the downlink information may also include other information, where the embodiment of the present application is only described by taking at least one of feedback information, timing adjustment command, power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of a new field of the RRC connection recovery request message as an example, but the embodiment of the present application is not limited thereto. If the terminal sends the RRC connection recovery request message and the uplink data to the network device, the downlink information may include at least one of the following: feedback information of the RRC connection recovery request message, feedback information of uplink data, a timing adjustment command, a power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of a newly added field. Of course, the downlink information may also include other information, and the embodiment of the present application is described only by taking at least one of feedback information of the RRC connection recovery request message, feedback information of uplink data, a timing adjustment command, a power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of a new field as an example, but the embodiment of the present application is not limited thereto.

After receiving the RRC connection restoration request message sent by the terminal, or after receiving the RRC connection restoration request message and the uplink data sent by the terminal, the network device may generate corresponding downlink information based on the received RRC connection restoration request message, or the RRC connection restoration request message and the uplink data, and send the generated downlink information to the terminal. For example, when transmitting the generated information to the terminal, the network device may transmit the generated information to the terminal in downlink control information, a MAC message, or an RRC message of the PDCCH.

S2004, the terminal restarts the T319 timer according to the downlink information received from the network device during the operation of the T319 timer.

In connection with the above description in S2003, in the case where the terminal has only sent the RRC connection resume request message to the network device, the downlink information received by the terminal from the network device includes feedback information of the RRC connection resume request message, where the feedback information of the RRC connection resume request message indicates whether the RRC connection resume request message was successfully transmitted, and the feedback information is ACK or NACK. If the feedback information is ACK, the RRC connection recovery request message is successfully sent, and the terminal can continue to send new uplink data on the configuration authorization; if the feedback information is NACK, it indicates that the transmission of the RRC connection recovery request message fails, and the terminal can continue to retransmit the RRC connection recovery request message on the configuration authorization. In this case, the downlink information received by the terminal from the network device may further include contention resolution information, where the contention resolution information may be the contention resolution information in S1005 in the embodiment shown in fig. 10, or may be the contention resolution information in S1105 in the embodiment shown in fig. 11, and if the contention resolution information is contention resolution success, it indicates that the RRC connection recovery request message is successfully sent, and the terminal may continue to send new uplink data on the pre-allocation grant; if the contention resolution information is a contention resolution failure, it indicates that the RRC connection recovery request message is failed to be sent, and the terminal may continue to retransmit the RRC connection recovery request message on the preset grant.

If the downlink information received by the terminal from the network device includes the feedback information of the RRC connection recovery request message, the terminal restarts the T319 timer and performs data transmission during the operation period of the T319 timer, so that the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively prolonged, and multiple data transmission can be flexibly supported.

And when the terminal sends the RRC connection recovery request message and the uplink data to the network equipment, the downlink information received by the terminal from the network equipment comprises feedback information of the RRC connection recovery request message and the uplink data, wherein the feedback information of the RRC connection recovery request message and the uplink data indicates whether the RRC connection recovery request message and the uplink data are successfully transmitted or not, and the feedback information is ACK or NACK. If the feedback information is ACK, the RRC connection recovery request message and the uplink data are successfully sent, and the terminal can continue to send new uplink data on the configuration authorization; if the feedback information is NACK, it indicates that the RRC connection recovery request message and/or the uplink data transmission fails, and the terminal may continue to retransmit the RRC connection recovery request message on the configuration grant and/or retransmit some or all of the data in the original uplink data. Similarly, in this case, the downlink information received by the terminal from the network device may further include contention resolution information, where the contention resolution information may be the contention resolution information in S1005 in the embodiment shown in fig. 10, or may be the contention resolution information in S1105 in the embodiment shown in fig. 11, and if the contention resolution information is contention resolution success, it indicates that the RRC connection recovery request message and the uplink data are successfully transmitted, and the terminal may continue to transmit new uplink data on the pre-allocation grant; if the contention resolution information is a contention resolution failure, it indicates that the RRC connection recovery request message and/or the uplink data transmission fails, and the terminal may continue to retransmit the RRC connection recovery request message on the preset grant and/or retransmit some or all of the original uplink data.

If the downlink information received by the terminal from the network device includes the RRC connection recovery request message and feedback information of the uplink data, the terminal restarts the T319 timer and performs data transmission during the operation period of the T319 timer, so that the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively prolonged, and multiple data transmission can be flexibly supported.

For the above two cases, the downlink information received by the terminal may include, in addition to feedback information and/or contention resolution information, uplink grant information, where uplink resources indicated by the uplink grant information may be used for retransmission of original uplink data, or may be used for initial transmission of new uplink data, so as to realize continuous data transmission of multiple packets. In general, if there is an original uplink data to be retransmitted and there is a new uplink data to be retransmitted, the new uplink data may be initially transmitted through the uplink resource indicated by the uplink grant information, that is, the transmission priority of the data initial transmission is higher than the transmission priority of the data retransmission. The downlink information received by the terminal may also include downlink resource allocation information, where the downlink resource indicated by the downlink resource allocation information may be used for retransmission of original downlink data, or may be used for initial transmission of new downlink data, so as to implement early transmission of downlink data. It should be noted that, in the embodiment of the present application, the uplink grant information and the downlink resource allocation information may exist independently, that is, the downlink information received by the terminal may include the uplink grant information or the downlink resource allocation information; the uplink grant information and the downlink resource allocation information may exist at the same time, that is, the downlink information received by the terminal may include the uplink grant information and the downlink resource allocation information at the same time. If the downlink information received by the terminal from the network device includes the uplink authorization information and/or the downlink resource allocation information, the terminal restarts the T319 timer and performs data transmission during the operation period of the T319 timer, so that the time of the terminal waiting for the RRC response message of the RRC connection recovery request can be effectively prolonged, and multiple data transmission can be flexibly supported. Preferably, if the downlink information received by the terminal from the network device includes uplink authorization information for initial transmission and/or downlink resource allocation information for downlink initial transmission, the terminal restarts the T319 timer.

In addition, since the terminal restarts the T319 timer according to the downlink information received from the network device, the downlink information received by the terminal may include an indication information, which may be carried in a physical layer control signaling, a MAC layer message, or an RRC layer message, for instructing the terminal to restart the T319 timer; correspondingly, after receiving the information including the indication information, the terminal can restart the T319 timer, so that data transmission is performed during the running period of the T319 timer, the time of the terminal waiting for the RRC response message of the RRC connection recovery request can be effectively prolonged, and multiple data transmission can be flexibly supported.

In summary, when the terminal restarts the T319 timer according to the downlink information received from the network device during the operation of the T319 timer, if the downlink information received by the terminal includes any one or more of feedback information, uplink grant information, downlink resource allocation information, and indication information of a new field, the terminal restarts the T319 timer, so that data transmission is performed during the operation of the T319 timer, which can effectively prolong the time for the terminal to wait for the RRC response of the RRC connection recovery request message, and flexibly support multiple data transmission. The downlink information received by the terminal may also include a timing adjustment command and/or a power control command, for example. When the timing adjustment command is received, the timing adjustment command is applied to adjust the uplink transmission timing; when the power control command is received, the power control command is applied to perform power control.

After restarting the T319 timer according to the received downlink information, if the current T319 timer is started for the first time, the terminal may also send an indication information to the network device, where the indication information is used to indicate the T319 timer restarted by the network device, so as to synchronize the information that the T319 timer has been restarted to the network device. Also, for the T319 timer, the T319 timer is not always in an operation state after restarting, but is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

By executing the above S2001-S2004, i.e. when the terminal should request RRC connection recovery, starting a T319 timer and sending an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can restart the T319 timer according to the downlink information received from the network device, and perform data transmission during the operation of the T319 timer, so that the time for the terminal to wait for the RRC response of the RRC connection recovery request message can be effectively prolonged, and multiple data transmission can be flexibly supported. The above whole procedure may be understood as that the terminal performs the first extension operation, and after the first extension operation is performed, the T319 timer may be restarted and operated again according to the downlink information received from the network device, so as to extend the time for the terminal to wait for the RRC response of the RRC connection restoration request message again. It may be understood that, the method of performing the third extension operation by the terminal, or the following N (N is greater than 3) extension operation is similar to the method of performing the first extension operation by the terminal, where the embodiment of the present application is described by taking the example that after the first extension operation is performed, the T319 timer may be restarted and operated, and the restart of the T319 timer may be controlled again according to the downlink information received from the network device, where after the execution of the above S2004, the following S2005-S2007 may be further performed:

and S2005, the terminal transmits uplink data to the network equipment during the running period of the T319 timer.

When the terminal sends uplink data to the network equipment, the terminal can send the uplink data to the network equipment by configuring uplink resources indicated by the authorization information system. For example, the configuration authorization information may be obtained from a broadcast message of the network device, or may be obtained from a dedicated message (e.g., RRC message) sent by the network device to the terminal.

It can be seen that the terminal may not transmit the RRC connection restoration request message to the network device but directly transmit uplink data when performing the mth (M is greater than or equal to 1) extension operation, and restart the T319 timer when the restart condition is satisfied, to extend the time for the terminal to wait for the RRC response message of the RRC connection restoration request.

And S2006, the network equipment sends downlink information to the terminal according to the uplink data.

For example, the downlink information may include feedback information of uplink data, a timing adjustment command, a power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of a new field. Of course, the downlink information may also include other information, and the embodiment of the present application is described only by taking at least one of feedback information of uplink data, a timing adjustment command, a power control command, contention resolution information, uplink grant information, downlink resource allocation information, and indication information of a new field as an example, but the embodiment of the present application is not limited thereto.

After receiving the uplink data sent by the terminal, the network device may generate corresponding downlink information based on the received uplink data, and send the generated downlink information to the terminal. For example, when transmitting the generated information to the terminal, the network device may transmit the generated information to the terminal in downlink control information, a MAC message, or an RRC message of the PDCCH.

S2007, the terminal restarts the T319 timer again according to the downlink information received from the network device during the operation of the T319 timer.

When restarting the T319 timer for the second time according to the downlink information received from the network device, if the downlink information received by the terminal includes any one or more of feedback information, uplink grant information, downlink resource allocation information, and indication information of a newly added field, restarting the T319 timer, that is, performing a second extension operation, so that data transmission is performed during operation of the T319 timer, so that the time that the terminal waits for an RRC response of an RRC connection recovery request message can be effectively prolonged, and multiple data transmission can be flexibly supported. It will be appreciated that the T319 timer is also not always running after the second restart, but is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

In this possible implementation, when restarting the T319 timer, only the case that the terminal may restart the T319 timer according to the downlink information received from the network device during operation of the T319 timer is described, and of course, during operation of the T319 timer, the T319 timer may also be restarted according to data transmission with the network device, for example, during operation of the T319 timer, if the terminal sends uplink data, for example, data of a dedicated transmission channel (DEDICATED TRAFFIC CHANNEL, DTCH), the T319 timer is restarted; or if downlink data, for example, DTCH data, is received, the T319 timer is restarted.

In the embodiment shown in fig. 20, a first possible implementation manner is described in detail, when the first timer is a T319 timer configured by the current network, the terminal starts the T319 timer and sends an RRC connection restoration request message to the network device when the terminal meets the requirement of RRC connection restoration; during the operation of the T319 timer, the terminal may restart the technical scheme of the T319 timer according to the downlink information received from the network device. In the second possible implementation manner, when the first timer may be additionally set by the RRC layer and a new timer T1 other than the T319 timer is set, the terminal starts the new timer T1 and sends an RRC connection restoration request message to the network device when the terminal should meet the requirement of RRC connection restoration; during the operation of the new timer T1, the terminal may restart the technical scheme of the new timer T1 according to the downlink information received from the network device or according to the data transmission with the network device.

In this second possible implementation manner, unlike the embodiment shown in fig. 20 described above, the first timer in this possible implementation manner is not a T319 timer any more, but is a new timer T1 additionally set by the RRC layer, that is, the new timer T1 is started when the terminal should request for RRC connection recovery, and during the operation of the new timer T1, the new timer T1 is restarted according to downlink information received from the network device or according to data transmission with the network device, so as to extend the time for the terminal to wait for the RRC response message of the RRC connection recovery request, thereby flexibly supporting multiple data transmission. In this possible implementation, the T319 timer may not be started.

Before starting the new timer T1, the terminal configures the duration of the new timer T1, so that the new timer T1 may run based on the configured duration, and the configuration method of the duration of the new timer T1 is similar to the configuration method of the duration of the T319 timer in the embodiment shown in fig. 20, which is not described in detail herein. As for how to send the RRC connection resume request message to the network device after the start of the new timer T1 and how to restart the new timer T1 according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the new timer T1, the method of sending the RRC connection resume request message to the network device after the start of the T319 timer and how to restart the T319 timer according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the T319 timer is similar to the embodiment shown in fig. 20 described above, and the description of how to send the RRC connection resume request message to the network device after the start of the new timer T1 and how to restart the new timer T1 according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the new timer T1 will not be repeated.

In this possible implementation, unlike the embodiment shown in fig. 20 described above, the first timer in this possible implementation is not a T319 timer, but a new timer T1 other than the T319 timer is additionally set by the RRC layer, and in order to save power consumption of the terminal due to the operation of the T319 timer, in this possible implementation, the T319 timer may not be started. For the new timer T1, the new timer T1 is not always in an operating state after restarting, but the new timer T1 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

In the third possible implementation manner, when the first timer is a new timer T2 set by the MAC layer, the terminal starts the new timer T2 and sends an RRC connection recovery request message to the network device when the terminal meets the requirement of RRC connection recovery; during the operation of the new timer T2, the terminal may restart the technical scheme of the new timer T2 according to the downlink information received from the network device or according to the data transmission with the network device.

In this third possible implementation manner, unlike the embodiment shown in fig. 20 described above, the first timer in this possible implementation manner is not a T319 timer, but a new timer T2 set by the MAC layer, that is, the new timer T2 is started when the terminal should request for RRC connection recovery, and during the operation of the new timer T2, the new timer T2 is restarted according to downlink information received from the network device or according to data transmission with the network device, so as to extend the time for the terminal to wait for an RRC response message of an RRC connection recovery request, thereby flexibly supporting multiple data transmission. In this possible implementation, the T319 timer may not be started.

Before starting the new timer T2, the terminal configures the duration of the new timer T2, so that the new timer T2 may run based on the configured duration, and the configuration method of the duration of the new timer T2 is similar to the configuration method of the duration of the T319 timer in the embodiment shown in fig. 20, which is not described in detail herein. As for how to send the RRC connection resume request message to the network device after the start of the new timer T2 and how to restart the new timer T2 according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the new timer T2, the method of sending the RRC connection resume request message to the network device after the start of the T319 timer and how to restart the T319 timer according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the T319 timer is similar to the embodiment shown in fig. 20 described above, and the description of how to send the RRC connection resume request message to the network device after the start of the new timer T2 and how to restart the new timer T2 according to the downlink information received from the network device or according to the data transmission with the network device during the operation of the new timer T2 will not be repeated.

In this possible implementation, unlike the embodiment shown in fig. 20 described above, the first timer in this possible implementation is not a T319 timer, but a new timer T2 of the MAC layer, in order to save power consumption of the terminal due to the operation of the T319 timer, in this possible implementation, the T319 timer may not be started as well. For the new timer T2, the new timer T2 is not always in an operating state after restarting, but the new timer T2 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device. After restarting the new timer T2, if the timer T2 times out, the MAC layer of the terminal notifies the RRC layer that the timer T2 times out, and the MAC layer of the terminal enters an idle state according to the timer T2 time-out information terminal.

After describing the first possible scenario in detail, when the restart condition is met, the restarted timer and the timer started when the need of RRC connection recovery is met are the same timer, and are both the first timers, so as to prolong the time of the terminal waiting for the RRC response message of the RRC connection recovery request, thereby flexibly supporting the technical scheme of multiple data transmission. In another possible scenario, the technical scheme of the restarting timer and the timer started when the requirement of RRC connection recovery is met, rather than the same timer, is described in detail below, that is, the terminal starts the first timer when the requirement of RRC connection recovery is met, and starts the second timer when the starting condition is met during the operation of the first timer, so as to prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request. It will be appreciated that in this possible scenario, the first timer may also be stopped after the second timer is started; of course, the first timer may be stopped and the second timer may be started.

For example, in such a possible scenario, at least two possible implementations may be included as follows when the terminal waits for the RRC response message of the RRC connection resume request by starting the second timer. In one possible implementation manner, the first timer may be a T319 timer configured by the current network, the second timer may be a new timer additionally set by the RRC layer, and in order to distinguish the new timer T1 in the above embodiment, the new timer may be denoted as a new timer T3 in the present application, and the new timer T3 may be the new timer T1 in the above embodiment or the new timer additionally set. That is, when the terminal should meet the requirement of RRC connection recovery, firstly starting a T319 timer, and sending an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may start the new timer T3 based on downstream information received from the network device or based on data transmission with the network device. In one possible implementation manner, the first timer may be a T319 timer configured by the current network, the second timer may be a new timer additionally set by the MAC layer, and in order to distinguish the new timer T2 in the foregoing embodiment, the new timer may be denoted as a new timer T4 in the present application, and the new timer T4 may be the new timer T2 in the foregoing embodiment or the new timer additionally set. That is, when the terminal should meet the requirement of RRC connection recovery, firstly starting a T319 timer, and sending an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may start the new timer T4 based on downstream information received from the network device or based on data transmission with the network device. It will be appreciated that in this possible scenario, the first timer may also be stopped after the second timer is started. In the following, for two possible implementations, how to control the second timer to start so as to prolong the time of the terminal waiting for the RRC response message of the RRC connection resume request, so as to flexibly support multiple data transmission in this possible scenario will be described in detail.

In a first possible implementation manner, the first timer may be a T319 timer configured by the current network, and the second timer may be a new timer T3, which is additionally set by the RRC layer, except for the T319 timer. That is, when the terminal should meet the requirement of RRC connection recovery, firstly starting a T319 timer, and sending an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may start the new timer T3 based on downstream information received from the network device or based on data transmission with the network device. In this possible implementation, it will be described by way of example that the terminal may start or restart the new timer T3 according to the downlink information received from the network device during operation of the T319 timer, and of course, may start or restart the new timer T3 according to data transmission with the network device during operation of the T319 timer. For example, referring to fig. 21, fig. 21 is a flowchart of another configuration method provided in an embodiment of the present application, where the configuration method may include:

s2101, when the terminal meets the requirement of RRC connection recovery, starting a T319 timer.

The terminal configures the duration of the T319 timer before starting the T319 timer, so that the T319 timer can be operated based on the configured duration. In S2101, the configuration method of the duration of the T319 timer is similar to the configuration method of the duration of the T319 timer in S2001 in the above embodiment, and specifically, reference may be made to the related description of the duration of the configured T319 timer, and here, the embodiment of the present application will not be repeated.

After starting the T319 timer, an RRC connection resume request message may be sent to the network device, i.e. the following S2102 is performed:

S2102, the terminal sends RRC connection recovery request information to the network equipment.

In S2102, a method for sending an RRC connection restoration request message to a network device by a terminal is similar to the method for sending an RRC connection restoration request message to a network device by a terminal in S2002, and may be specifically described with reference to the related description of sending an RRC connection restoration request message to a network device by a terminal in S2002, where the method for sending an RRC connection restoration request message to a network device by a terminal is not described in detail.

In S2102, the terminal may send, in addition to the RRC connection restoration request message to the network device, at least one of uplink data, auxiliary information, and indication information of the data to be kept in the inactive state and continue to be sent to the network device, where the sending manner of these information is similar to the sending manner of at least one of the uplink data, auxiliary information, and indication information of the data to be kept in the inactive state and continue to be sent to the network device in S2002, which is described in S2002 above, and the description of at least one of the uplink data, auxiliary information, and indication information of the data to be kept in the inactive state and continue to be sent to the network device is omitted here. Unlike S2002 described above, in the embodiment of the present application, since there is a new timer T3 additionally set by the RRC layer in addition to the T319 timer, the terminal may further send a start indication information to the network device, where the start indication information is used to indicate that the new timer T3 is started when the start condition is met during the operation of the T319 timer, so as to achieve synchronization between the new timer T3 started by the terminal and the new timer T3 started by the network device.

After the terminal sends the RRC connection restoration request message to the network device, the corresponding network device may send corresponding downlink information to the terminal according to the RRC connection restoration request message, i.e. execute the following S2103:

And S2103, the network equipment sends downlink information to the terminal according to the RRC connection recovery request message.

In S2103, the method for the network device to send the downlink information to the terminal according to the RRC connection resume request message is similar to the method for the network device to send the downlink information to the terminal according to the RRC connection resume request message in the embodiment shown in fig. 20 described above, and reference may be made to the related description in S2003, and here, the embodiments of the present application will not be repeated.

S2104, the terminal starts a new timer T3 according to the downlink information received from the network device during the running of the timer T319.

Before starting the new timer T3, the terminal configures the duration of starting the new timer T3, so that the new timer T3 can be started based on the configured duration. For example, when configuring the duration of the new timer T3, the terminal may receive a broadcast message or an RRC message from the network device, and configure the duration of the new timer T3 according to information indicating the duration of the new timer T3 included in the broadcast message or the RRC message. For the method for acquiring the information indicating the duration of the new timer T3, the information indicating the duration of the new timer T3 and the information indicating the duration of the timer T319 may be acquired through the same broadcast message or RRC message, or may be acquired through different broadcast messages or RRC messages, and may specifically be set according to actual needs. For the time of acquiring the information indicating the duration of the new timer T3, the information indicating the duration of the new timer T3 may be acquired at the same time as the information indicating the duration of the timer T319, or may be acquired at a different time, for example, when determining to start the new timer T3, the information indicating the duration of the new timer T3 is acquired again, which may be specifically set according to actual needs.

The duration of the new timer T3 may be a first duration of the T319 timer of the current network configuration, for example, the first duration may be a certain value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms }, or may be greater than a second duration of the T319 timer of the current network configuration, which may be configured by a broadcast message or an RRC message, for example, the second duration may be a certain value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms,2500ms }, for example, the second duration may be 2500ms. Since the new timer T3 is started when the starting condition is satisfied, the time for the terminal to wait for the RRC response message of the RRC connection resume request can be effectively prolonged for both of the two different durations. It can be understood that when the configuration duration of the new timer T3 becomes longer, the time for the terminal and the network device to perform data transmission becomes longer, so that the terminal network device can perform multiple data transmissions.

After configuring the duration of the new timer T3, it is possible to perform S2104 that the terminal starts the new timer T3 according to the downlink information received from the network device during the running of the timer T319. The method for starting the new timer T3 according to the downlink information received from the network device during the operation of the T319 timer by the S2104 terminal is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer by the terminal in the S2004 described in the above S2004, and here, the method for how to start the new timer T3 according to the downlink information received from the network device during the operation of the T319 timer by the terminal will not be repeated in the embodiments of the present application.

In summary, when the terminal starts the new timer T3 according to the downlink information received from the network device during the operation of the timer T319, if the downlink information received by the terminal includes any one or more of feedback information of uplink data, uplink grant information, downlink resource allocation information, and indication information of a new field, the terminal starts the new timer T3, so that data transmission is performed during the operation of the new timer T3, which can effectively prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission. If the T319 timer is still running, the T319 timer may be stopped. For example, the new timer T3 is started first, and after the new timer T3 is started, the timer T319 is stopped; or the T319 timer may be stopped at the same time as the new timer T3 is started. The downlink information received by the terminal may also include a timing adjustment command and/or a power control command, for example. When the timing adjustment command is received, the timing adjustment command is applied to adjust the uplink transmission timing; when the power control command is received, the power control command is applied to perform power control.

After the terminal starts the new timer T3 according to the received downlink information, since the new timer T3 is started for the first time, the terminal may also synchronize the information that has started the new timer T3 to the network device by sending an indication information to the network device, where the indication information is used to indicate the new timer T3 started by the network device. Also, as for the new timer T3, the new timer T3 is not always in an operation state after being started, but the new timer T3 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

By executing the above S2101-S2104, i.e. when the terminal should meet the requirement of RRC connection recovery, starting a T319 timer and sending an RRC connection recovery request message to the network device; in this way, during the running period of the timer T319, the terminal can start the new timer T3 according to the downlink information received from the network device, and perform data transmission during the running period of the new timer T3, so that the time that the terminal waits for the RRC response of the RRC connection restoration request message can be effectively prolonged, and multiple data transmission can be flexibly supported. The above-mentioned whole procedure may be understood as that the terminal performs the first extension operation, and after the first extension operation is performed, the new timer T3 may be controlled again according to the downlink received from the network device to restart the new timer T3 during the start and operation of the new timer T3, so as to extend the time for the terminal to wait for the RRC response of the RRC connection resume request message again. It will be understood that, the method of performing the third extension operation by the terminal, or the N (N is greater than 3) th extension operation later, is similar to the method of performing the first extension operation by the terminal, where the embodiment of the present application is described by taking the example that, after the first extension operation is performed, the new timer T3 may be further started and operated, according to the downlink information received from the network device, and the following S2105-S2107 may be further performed after the new timer T3 is started according to the downlink information received from the network device by performing the above S2104:

And S2105, the terminal transmits uplink data to the network equipment during the operation of the new timer T3.

And S2106, the network equipment sends downlink information to the terminal according to the uplink data.

S2107, the terminal restarts the new timer T3 according to the downlink information received from the network device during the operation of the new timer T3.

In S2105-S2107, the terminal sends uplink data to the network device during the operation of the new timer T3, the network device sends downlink information to the terminal according to the uplink data, and the corresponding method for restarting the new timer T3 according to the downlink information received from the network device during the operation of the new timer T3 is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer, which is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer in the embodiment shown in fig. 20, and in S2005-S2007, the embodiment of the present application will not be repeated here.

Since the time for the terminal to wait for the RRC response of the RRC connection restoration request message is itself prolonged by restarting the T319 timer when the first prolonged operation is performed through the above-described S2001-S2004, the time for the terminal to wait for the RRC response of the RRC connection restoration request message is prolonged by restarting the T319 timer when the second prolonged operation is performed in the above-described S2007. In contrast to S2007, in the embodiment of the present application, since the time for the terminal to wait for the RRC response of the RRC connection resume request message is prolonged by starting the new timer T3 for the first time when the first time of the extending operation is performed in S2101 to S2104, the time for the terminal to wait for the RRC response of the RRC connection resume request message is started for the first time when the second time of the extending operation is performed in S2107.

When the terminal restarts the new timer T3 for the first time according to the downlink information received from the network device, if the downlink information received by the terminal includes any one or more of feedback information, uplink grant information, downlink resource allocation information, and indication information of a newly added field, the new timer T3 is restarted, that is, a second extension operation is performed, so that data transmission is performed during the operation of the new timer T3, so that the time for the terminal to wait for the RRC response of the RRC connection recovery request message can be effectively prolonged, and multiple data transmission can be flexibly supported. It will be appreciated that the new timer T3 is also not always running after the first restart, but the new timer T3 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

It will be appreciated that in this possible implementation, when starting the new timer T3, only the case where the terminal starts the new timer T3 according to the downlink information received from the network device during the operation of the timer T319 is described, and of course, during the operation of the timer T319, the new timer T3 may also be started according to the data transmission with the network device, for example, during the operation of the timer T319, if the terminal sends uplink data, the new timer T3 is started; or if downlink data is received, a new timer T3 is started.

In a second possible implementation manner, the first timer may be a T319 timer configured by the current network, and the second timer may be a new timer T4 set by the MAC layer. That is, when the terminal should meet the requirement of RRC connection recovery, firstly starting a T319 timer, and sending an RRC connection recovery request message to the network device; thus, during the operation of the T319 timer, the terminal may start the new timer T4 based on downstream information received from the network device or based on data transmission with the network device. It should be noted that, in this possible implementation manner, the new timer T4 may be started or restarted according to the data transmission with the network device by the terminal during the operation of the T319 timer, and of course, the new timer T4 may also be started or restarted according to the downlink information received from the network device during the operation of the T319 timer. For example, referring to fig. 22, fig. 22 is a flowchart of another configuration method provided in an embodiment of the present application, where the configuration method may include:

s2201, when the terminal meets the requirement of RRC connection recovery, starting a T319 timer.

The terminal configures the duration of the T319 timer before starting the T319 timer, so that the T319 timer can be operated based on the configured duration. In S2201, the configuration method of the duration of the T319 timer is similar to the configuration method of the duration of the T319 timer in S2001 in the above embodiment, and specifically, reference may be made to the description related to the duration of the configured T319 timer, and here, the embodiment of the present application will not be repeated.

After starting the T319 timer, an RRC connection resume request message may be sent to the network device, i.e. the following S2202 is performed:

S2202, the terminal sends an RRC connection recovery request message to the network device.

In S2202, the method for sending the RRC connection resume request message to the network device by the terminal is similar to the method for sending the RRC connection resume request message to the network device by the terminal in S2002, and may be specifically described with reference to the related description of sending the RRC connection resume request message to the network device by the terminal in S2002, where the method for sending the RRC connection resume request message to the network device by the terminal is not described in detail.

In this S2202, the terminal may send, in addition to the RRC connection restoration request message to the network device, at least one of the uplink data, the auxiliary information, and the indication information for which the data is expected to be kept in the inactive state and continue to be sent to the network device, which is similar to the above-described sending of at least one of the uplink data, the auxiliary information, and the indication information for which the data is expected to be kept in the inactive state and continue to be sent to the network device in S2002, which is described in the above-described S2002, and the description of at least one of the uplink data, the auxiliary information, and the indication information for which the data is expected to be kept in the inactive state and continue to be sent to the network device is omitted here. Unlike S2002 described above, in the embodiment of the present application, since there is a new timer T4 set by the MAC layer in addition to the T319 timer, the terminal may further send a start indication message to the network device, where the start indication message is used to indicate that the new timer T4 is started when the start condition is met during the operation of the T319 timer, so as to achieve synchronization between the new timer T4 started by the terminal and the new timer T3 started by the network device.

After the terminal sends the RRC connection restoration request message to the network device, the network device may correspondingly send, according to the RRC connection restoration request message, corresponding downlink information to the terminal, that is, perform the following S2203:

S2203, the network equipment sends downlink information to the terminal according to the RRC connection recovery request message.

In S2203, the method for the network device to send the downlink information to the terminal according to the RRC connection recovery request message is similar to the method for the network device to send the downlink information to the terminal according to the RRC connection recovery request message in S2103, which can be referred to the related description in S2103, and detailed description of the embodiment of the present application is omitted here. In addition, for the content included in the downlink information, reference may be made to the description related to S2104, and the description of the embodiment of the present application is not repeated here.

S2204, the terminal starts a new timer T4 according to the data transmission with the network device during the running of the timer T319.

Before starting the new timer T4, the terminal configures the duration of starting the new timer T4, so that the new timer T4 can be started based on the configured duration. For example, when configuring the duration of the new timer T4, the terminal may receive a broadcast message or an RRC message from the network device, and configure the duration of the new timer T4 according to information indicating the duration of the new timer T4 included in the broadcast message or the RRC message. It can be understood that, for the manner of acquiring the information indicating the duration of the new timer T4, the information indicating the duration of the new timer T4 may be acquired through the same broadcast message or RRC message with the information indicating the duration of the timer T319, or may be acquired through different broadcast messages or RRC messages, and may specifically be set according to actual needs. For the time of acquiring the information indicating the duration of the new timer T4, the information indicating the duration of the new timer T4 may be acquired at the same time as the information indicating the duration of the timer T319, or may be acquired at a different time, for example, when determining to start the new timer T4, the information indicating the duration of the new timer T4 is acquired again, which may be specifically set according to actual needs.

The duration of the new timer T4 may be a first duration of the T319 timer of the current network configuration, for example, the first duration may be a certain value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms }, or may be greater than a second duration of the T319 timer of the current network configuration, which may be configured by a broadcast message or an RRC message, for example, the second duration may be a certain value of {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms,2500ms }, for example, the second duration may be 2500ms. Since the new timer T4 is started when the starting condition is satisfied, the time for the terminal to wait for the RRC response message of the RRC connection resume request can be effectively prolonged for both of the two different durations. It can be understood that when the configuration duration of the new timer T4 becomes longer, the time for the terminal and the network device to perform data transmission becomes longer, so that the terminal network device can perform multiple data transmissions.

Unlike the first possible implementation manner described above, in the embodiment of the present application, during the operation of the T319 timer, since the new timer T4 is started according to the data transmission with the network device, even if any one or more of the feedback information, the uplink grant information, the downlink resource allocation information, and the indication information of the newly added field are included in the downlink information received by the terminal, the new timer T4 is not started, but the new timer T4 is started according to the data transmission with the network device, for example, during the operation of the T319 timer, if the terminal sends the uplink data, for example, the data of the DTCH, the new timer T4 is started; or if downlink data, for example, DTCH data, is received, the new timer T4 is started, so that data transmission is performed during the operation period of the new timer T4, the time of waiting for the RRC response message of the RRC connection recovery request by the terminal can be effectively prolonged, and multiple data transmission can be flexibly supported. After starting the timer T4, if the T319 timer is still running, the T319 timer may be stopped. After the terminal starts the new timer T4 according to the data transmission with the network device, since the new timer T4 is started for the first time, the terminal may also synchronize the information that the new timer T4 has been started to the network device by sending an indication information to the network device, where the indication information is used to indicate the new timer T4 started by the network device. Also, as for the new timer T4, the new timer T4 is not always in an operation state after being started, but the new timer T4 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device. After the new timer T4 is started, if the timer T4 times out, the MAC layer of the terminal notifies the RRC layer that the timer T4 times out, and the MAC layer of the terminal enters an idle state according to the timer T4 time-out information terminal.

Starting a T319 timer by executing the steps 2201-2204, namely, when the terminal meets the requirement of RRC connection recovery, and sending an RRC connection recovery request message to the network equipment; the terminal starts the new timer T4 according to the data transmission with the network device during the running period of the timer T319, and performs the data transmission during the running period of the new timer T4, so that the time for the terminal to wait for the RRC response of the RRC connection recovery request message can be effectively prolonged, and the transmission of multiple data can be flexibly supported. The above-mentioned whole procedure can be understood as that the terminal performs the first extension operation, and after the first extension operation is performed, the new timer T4 can be controlled to restart again according to the data transmission with the network device during the operation of the new timer T4, so as to extend the time for the terminal to wait for the RRC response of the RRC connection resume request message again. The method of the terminal performing the third extension operation, or the following nth extension operation (N is greater than 3) is similar to the method of the terminal performing the first extension operation, where the embodiment of the present application may further be described by taking the example that the new timer T4 is restarted according to the data transmission control with the network device during the start and operation of the new timer T4 after the first extension operation is performed, and after the execution of the above step S2104, the following steps S2205-S2207 may be further performed:

s2205, the terminal sends uplink data to the network equipment during the operation period of the new timer T4.

S2206, the network equipment sends downlink information to the terminal according to the uplink data.

In S2205-S2206, the method for transmitting uplink data to the network device by the terminal during the operation of the new timer T4 and the method for transmitting downlink information to the terminal by the network device according to the uplink data in the embodiment shown in fig. 20 described above are similar to the method for transmitting uplink data to the network device by the terminal during the operation of the timer T319 and transmitting downlink information to the terminal by the network device according to the uplink data in the embodiment shown in fig. 20 described above, and the description thereof will not be repeated here.

S2207, the terminal restarts the new timer T4 according to the data transmission with the network device during the operation of the new timer T4.

In S2207, the method for restarting the new timer T4 according to the data transmission with the network device during the operation of the new timer T4 by the terminal is similar to the method for restarting the new timer T4 according to the data transmission with the network device during the operation of the new timer T4 by the terminal in S2204, and the embodiments of the present application are not repeated here.

In the embodiment of the present application, since the time for the terminal to wait for the RRC response of the RRC connection resume request message is prolonged by starting the new timer T4 for the first time when the first time of the extending operation is performed in the above-described S2201-S2204, the time for the terminal to wait for the RRC response of the RRC connection resume request message is prolonged by restarting the new timer T4 for the first time when the second time of the extending operation is performed in the S2207. It will be appreciated that the new timer T4 is also not always running after the first restart, but the new timer T4 is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

In this possible implementation, when starting the new timer T4, the new timer T4 is started only according to the data transmission with the network device, for example, during the running of the timer T319, if the terminal sends uplink data, the new timer T4 is started; or if downlink data is received, the new timer T4 is started for illustration, and of course, during the running period of the timer T319, the terminal may also start the new timer T4 according to the downlink information received from the network device, specifically, refer to the description related to starting the new timer T3 according to the downlink information received from the network device in the first possible implementation manner, and here, the embodiment of the present application will not be repeated for how the terminal starts the new timer T4 according to the downlink information received from the network device.

In summary, it can be seen that when describing the technical solution provided in the embodiments of the present application through the two possible scenarios, in order to prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission, the terminal may start the first timer first according to the requirement of radio resource control RRC connection recovery, and both send the RRC connection recovery request message to the network device through the uplink resource indicated by the configuration grant information; and during the operation of the first timer, the terminal restarts the first timer or starts the second timer according to the downlink information received by the network equipment or according to the data transmission with the network equipment, so that the time of the terminal waiting for the RRC connection to recover is effectively prolonged, and the transmission of multiple times of data is flexibly supported. In the embodiment of the application, besides the RRC connection restoration request message can be sent to the network equipment through the uplink resource indicated by the configuration authorization information, the RRC connection restoration request message can also be sent to the network equipment through the uplink resource in the random access process. For example, the uplink resource may be a PUSCH resource preconfigured for the message a (MsgA) in the two-step RACH, or may be an uplink resource indicated in a random access response received by the terminal in the four-step RACH, which may be specifically set according to actual needs. It can be understood that when the RRC connection recovery request message is sent to the network device through the uplink resource in the random access procedure, and the restart condition is met during the operation of the first timer, the technical scheme of restarting the first timer can be equally applicable to the two possible scenarios, that is, in one possible scenario, when the restart condition is met, the restarted timer and the timer started when the requirement of RRC connection recovery is met are the same timer, both are the first timer. In another possible scenario, the terminal starts a first timer when the need for RRC connection recovery is met, and starts a second timer when the start condition is met during operation of the first timer, so as to extend the time for the terminal to wait for an RRC response message of an RRC connection recovery request. It will be appreciated that in this possible scenario, the first timer may also be stopped when the second timer is started.

In the following, a first possible implementation manner in the first scenario will mainly be described, where the first timer is a T319 timer configured by the current network, and the terminal sends an RRC connection recovery request to the network device through an uplink resource in a message a (MsgA) of the two-step RACH, and during operation of the T319 timer, the terminal may restart the T319 timer according to downlink information received from the network device or according to data transmission with the network device. In this possible implementation, it will be described by taking as an example that the terminal may restart the T319 timer according to the downlink information received from the network device during operation of the T319 timer, and of course, the T319 timer may also be restarted according to data transmission with the network device during operation of the T319 timer. For example, referring to fig. 23, fig. 23 is a flowchart of another configuration method according to an embodiment of the present application, where the configuration method may include:

S2301, when the terminal meets the requirement of RRC connection recovery, starting a T319 timer.

The terminal needs to configure the duration of the T319 timer before starting the T319 timer, so that the T319 timer can be operated based on the configured duration. In S2301, the configuration method of the T319 timer is similar to the configuration method of the T319 timer in S2001 in the above embodiment, and specific reference may be made to the description related to the duration of configuring the T319 timer, which is not repeated here in the embodiment of the present application.

S2302, the terminal sends the preamble to the network device.

For example, the terminal may transmit a preamble to the network device through message a (MsgA) of the two-step RACH, and the resource for transmitting the preamble may be PRACH resource preconfigured by the network device, which may be configured through a broadcast message or a dedicated message (e.g., RRC connection release message).

S2303, the terminal sends an RRC connection recovery request message to the network device.

When the terminal transmits the RRC connection restoration request message to the network device, unlike in S2002 described above, in the embodiment of the present application, the terminal may transmit the RRC connection restoration request message to the network device through message a (MsgA) of the two-step RACH, and the resource for transmitting the RRC connection restoration request message may be a PUSCH resource preconfigured by the network device, and the PUSCH resource may be configured through a broadcast message or a dedicated message (e.g., an RRC connection release message).

For example, the terminal may send, in addition to the RRC connection restoration request message to the network device, at least one of uplink data, auxiliary information, and indication information of desiring to keep sending data in an inactive state to the network device, where the sending manner of these information is similar to the sending manner of at least one of uplink data, auxiliary information, and indication information of desiring to keep sending data in an inactive state to the network device in S2002, and reference may be made to the description of at least one of uplink data, auxiliary information, and indication information of desiring to keep sending data in an inactive state to the network device in S2002. In the embodiment of the present application, taking the case that the terminal sends the RRC connection restoration request message to the network device, and also sends uplink data to the network device, the description of the technical solution provided in the embodiment of the present application is continued, and the corresponding network device executes the following S2304 after receiving the RRC connection restoration request message and the uplink data sent by the terminal:

S2304, the network device sends downlink information to the terminal according to the RRC connection recovery request message.

It should be noted that, in S2304, the method for the network device to send the downlink information to the terminal according to the RRC connection recovery request message is similar to the method for the network device to send the downlink information to the terminal according to the RRC connection recovery request message in the embodiment shown in fig. 20, and reference may be made to the related description in S2003, and here, the embodiments of the present application will not be repeated.

S2305, the terminal restarts the T319 timer according to the downlink information received from the network device during the operation of the T319 timer.

In S2305, the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer by the terminal is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer by the terminal in S2005 in the embodiment shown in fig. 20, and the description of the related step in S2005 is referred to herein, and for the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer by the terminal in S2305, the embodiment of the present application will not be repeated. In S2305, unlike in S2005 described above, feedback information is not included in the downlink information, but TC-RNTI may be included.

In summary, when restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer, if the downlink information received by the terminal includes any one or more of the uplink grant information, the downlink resource allocation information, and the indication information of the newly added field, the terminal restarts the T319 timer, so that data transmission is performed during the operation of the T319 timer, which can effectively prolong the time for the terminal to wait for the RRC response message of the RRC connection recovery request, and flexibly support multiple data transmission. The downlink information received by the terminal may also include a timing adjustment command and/or a power control command, for example.

By executing the above-mentioned S2301-S2305, that is, when the terminal should respond to the requirement of RRC connection restoration, starting a T319 timer and sending an RRC connection restoration request message to the network device; in this way, during the operation of the T319 timer, the terminal can restart the T319 timer according to the downlink information received from the network device, and perform data transmission during the operation of the T319 timer, so that the time for the terminal to wait for the RRC response of the RRC connection resume request message can be effectively prolonged, and multiple data transmission can be flexibly supported. The above whole procedure may be understood as that the terminal performs the first extension operation, and after the first extension operation is performed, the T319 timer may be restarted and operated again according to the downlink information received from the network device, so as to extend the time for the terminal to wait for the RRC response of the RRC connection restoration request message again. It may be understood that, the method of performing the third extension operation by the terminal, or the following nth extension operation (N is greater than 3) is similar to the method of performing the first extension operation by the terminal, where the embodiment of the present application is described by taking the example that after the first extension operation is performed, the T319 timer may be restarted and operated, and the following S2306-S2308 may be further performed after the T319 timer is restarted according to the downlink information received from the network device, where the T319 timer is controlled to be restarted according to the downlink information received from the network device, which is illustrated by the example:

S2306, the terminal sends uplink data to the network device during the running period of the T319 timer.

And S2307, the network equipment sends downlink information to the terminal according to the uplink data.

S2308, the terminal restarts the T319 timer according to the downlink information received from the network device during the operation of the T319 timer.

In S2306-S2308, the terminal sends uplink data to the network device during the operation of the new timer T319, the network device sends downlink information to the terminal according to the uplink data, and the corresponding method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer, which is similar to the method for restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer in the embodiment shown in fig. 20, and in S2005-S2007, the embodiment of the present application will not be repeated here.

In this possible implementation, when restarting the T319 timer, only the case is described in which the terminal may restart the T319 timer according to the downlink information received from the network device during operation of the T319 timer, and of course, during operation of the T319 timer, the T319 timer may also be restarted according to data transmission with the network device, for example, during operation of the T319 timer, if the terminal sends uplink data, for example, data of the DTCH, the T319 timer is restarted; or if downlink data, for example, DTCH data, is received, the T319 timer is restarted.

The embodiment shown in fig. 23 above describes in detail the technical solution that the terminal sends the RRC connection recovery request to the network device through message a (MsgA) of the two-step RACH, and during the operation of the T319 timer, the terminal may restart the T319 timer according to the downlink information received from the network device or according to the data transmission with the network device. Of course, the terminal may send an RRC connection recovery request to the network device through an uplink resource indicated in the random access response received through the four-step RACH, and during operation of the T319 timer, the terminal may restart the T319 timer according to downlink information received from the network device or according to data transmission with the network device.

In the technical solution that the RRC connection recovery request is sent to the network device by using the uplink resource indicated in the random access response received through the four-step RACH, and the T319 timer is restarted during the operation period of the T319 timer, unlike the technical solution that the RRC connection recovery request is sent to the network device by using the message a (MsgA) through the two-step RACH shown in fig. 23 and the T319 timer is restarted during the operation period of the T319 timer, the terminal receives the random access response sent by the network device before the terminal sends the RRC connection recovery request message to the network device in S2303, where the random access response may include the TC-RNTI, the uplink grant, and the timing advance command, so that the terminal may send the RRC connection recovery request message to the network device through the uplink grant in the random access response. For example, in addition to sending the RRC connection restoration request message to the network device, the terminal may send at least one of uplink data, auxiliary information, and indication information that it is desired to keep sending data in the inactive state to the network device, as described in the related description in S2303 above. Unlike in S2304 described above, the downlink information sent by the network device to the terminal according to the RRC connection recovery request message here is not at least one of the TC-RNTI, the timing adjustment command, the power control command, the contention resolution information, the uplink grant information, the downlink resource allocation information, and the indication information of the newly added field, but at least one of the feedback information, the timing adjustment command, the power control command, the contention resolution information, the uplink grant information, the downlink resource allocation information, and the indication information of the newly added field; in this way, when the terminal restarts the T319 timer according to the downlink information received from the network device during the operation of the T319 timer, if the downlink information received by the terminal includes any one or more of feedback information, uplink grant information, downlink resource allocation information, and indication information of a new field, the specific process may refer to the related descriptions in S2003 and S2004 in the embodiment shown in fig. 20, and the embodiments of the present application will not be described herein. After restarting the T319 timer, data transmission can be performed during the running period of the T319 timer, so that the time for the terminal to wait for the RRC connection to recover is effectively prolonged, and the transmission of multiple data is flexibly supported. For example, if the downlink information received by the terminal further includes a timing adjustment command and/or a power control command. When the timing adjustment command is received, the timing adjustment command is applied to adjust the uplink transmission timing; when the power control command is received, the power control command is applied to perform power control.

After restarting the T319 timer according to the received downlink information, the terminal may also synchronize the information that has restarted the T319 timer to the network device by sending an indication to the network device, where the indication is used to instruct the terminal to restart the T319 timer. Also, for the T319 timer, the T319 timer is not always in an operation state after restarting, but is stopped when the terminal receives an RRC connection resume message, an RRC connection setup message, or an RRC connection release message from the network device.

It will be appreciated that in this possible implementation manner, when restarting the T319 timer, only the T319 timer is described by way of example in that, during operation of the T319 timer, the terminal may restart the T319 timer according to any one or more of downlink information received from the network device, such as uplink grant information, downlink resource allocation information, and indication information of a newly added field, and of course, during operation of the T319 timer, the T319 timer may also be restarted according to data transmission with the network device, for example, during operation of the T319 timer, if the terminal transmits uplink data, such as DTCH data, then restarting the T319 timer; or if downlink data, for example, DTCH data, is received, the T319 timer is restarted.

It can be seen that the foregoing description is mainly directed to the first possible implementation manner in the first scenario, that is, when the first timer is the T319 timer configured by the current network, the RRC connection recovery request is sent to the network device through the message a (MsgA) of the two-step RACH, and during the operation of the T319 timer, the terminal may restart the T319 timer according to the downlink information received from the network device or according to data transmission with the network device; and sending an RRC connection recovery request to the network device through the uplink resource indicated in the random access response received by the four-step RACH, where during the running period of the T319 timer, the terminal may restart the technical solution of the T319 timer according to the downlink information received from the network device or according to data transmission with the network device, and of course, the first timer may also be a new timer additionally set by the RRC layer or a new timer of the MAC layer, and when the first timer may also be a new timer additionally set by the RRC layer or a new timer of the MAC layer, a specific implementation manner of controlling restarting of the first timer is similar to a specific implementation manner of controlling restarting of the first timer when the first timer is the T319 timer, which may be referred to the above description about controlling restarting of the first timer when the first timer is the T319 timer.

The embodiment of the application also provides a device for implementing any of the above methods, for example, an apparatus is provided that includes a unit (or means) configured to implement each step performed by the terminal in any of the above methods. As another example, another apparatus is provided that includes means for performing the steps performed by the network device in any of the methods above.

It should be understood that the division of the units in the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated when actually implemented. And the units in the device can be all realized in the form of software calls through the processing element; or can be realized in hardware; it is also possible that part of the units are implemented in the form of software, which is called by the processing element, and part of the units are implemented in the form of hardware. For example, each unit may be a processing element that is set up separately, may be implemented as integrated in a certain chip of the apparatus, or may be stored in a memory in the form of a program, and the functions of the unit may be called and executed by a certain processing element of the apparatus. Furthermore, all or part of these units may be integrated together or may be implemented independently. The processing element described herein may in turn be a processor, which may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in a processor element or in the form of software called by a processing element.

In one example, the unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, for example: one or more Application SPECIFIC INTEGRATED Circuits (ASIC), or one or more microprocessors (DIGITAL SINGNAL processor, DSP), or one or more field programmable gate arrays (Field Programmable GATE ARRAY, FPGA), or a combination of at least two of these integrated Circuit forms. For another example, when the units in the apparatus may be implemented in the form of a scheduler of processing elements, the processing elements may be general-purpose processors, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke a program. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above unit for receiving is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit of the chip for receiving signals from other chips or devices. The above unit for transmitting is an interface circuit of the apparatus for transmitting signals to other apparatuses. For example, when the device is implemented in the form of a chip, the transmitting unit is an interface circuit of the chip for transmitting signals to other chips or devices.

Fig. 24 is a schematic structural diagram of a network device according to an embodiment of the present application. Which may be the network device in the above embodiments, for implementing the operations of the network device in the above embodiments. As shown in fig. 24, the network device includes: an antenna 2401, a radio frequency device 2402, a baseband device 2403. The antenna 2401 is connected to a radio frequency device 2402. In the uplink direction, the radio frequency device 2402 receives information transmitted from a terminal through the antenna 2401, and transmits the information transmitted from the terminal to the baseband device 2403 for processing. In the downlink direction, the baseband device 2403 processes information of the terminal and transmits the processed information to the radio frequency device 2402, and the radio frequency device 2402 processes information of the terminal and transmits the processed information to the terminal through the antenna 2401.

The baseband apparatus 2403 may include one or more processing elements 24031, including, for example, a master CPU and other integrated circuits. In addition, the baseband apparatus 2403 may further include a storage element 24032 and an interface 24033, the storage element 24032 for storing programs and data; the interface 24033 is used to interact with the radio frequency device 2402, such as a common public radio interface (common public radio interface, CPRI). The above means for network device may be located on baseband means 2403, e.g., the above means for network device may be a chip on baseband means 2403 including at least one processing element for performing the steps of any of the methods performed by the above network device and interface circuitry for communicating with other means. In one implementation, the units of the network device implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for a network device includes a processing element and a storage element, where the processing element invokes the program stored in the storage element to perform the method performed by the network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing elements, i.e., on-chip memory elements, or may be memory elements on a different chip than the processing elements, i.e., off-chip memory elements.

In another implementation, the units of the network device implementing the steps of the above method may be configured as one or more processing elements, which are disposed on the baseband apparatus, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

The units of the network device implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC), e.g. the baseband device comprises the SOC chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the processing element invokes the stored program of the storage element to implement the method executed by the above network device; or at least one integrated circuit may be integrated within the chip for implementing the method performed by the above network device; or may be combined with the above implementation, the functions of part of the units are implemented in the form of processing element calling programs, and the functions of part of the units are implemented in the form of integrated circuits.

It will be seen that the above apparatus for a network device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is adapted to perform any of the methods performed by the network device provided by the above method embodiments. The processing element may be configured in a first manner: that is, a part or all of the steps executed by the network device are executed in a manner of calling the program stored in the storage element; the second way is also possible: i.e. by means of integrated logic circuitry of hardware in the processor element in combination with instructions to perform part or all of the steps performed by the network device; of course, some or all of the steps performed by the above network device may also be performed in combination with the first and second modes.

The processing element herein, as described above, may be a general purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessor DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.

The memory element may be one memory or may be a collective term for a plurality of memory elements.

Fig. 25 is a schematic structural diagram of another network device according to an embodiment of the present application. Which may be the network device in the above embodiments, for implementing the operations of the network device in the above embodiments. As shown in fig. 25, the network device includes: the processor 2501, the memory 2502, and the interface 2503 are in signal connection with the processor 2501, the memory 2502, and the interface 2503.

The above configuration means is located in the network device, and the functions of the respective units can be realized by the processor 2501 calling a program stored in the memory 2502. That is, the above configuration apparatus includes a memory for storing a program that is called by the processor to perform the method in the above method embodiment, and a processor. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. Or the functions of the various elements above may be implemented by one or more integrated circuits configured to implement the methods above. For example: one or more ASICs, or one or more microprocessor DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or may be combined with the above implementations.

Fig. 26 is a schematic structural diagram of a terminal according to an embodiment of the present application. Which may be the terminal in the above embodiment, for implementing the operation of the terminal in the above embodiment. As shown in fig. 26, the terminal includes: an antenna 2601, a radio frequency portion 2602, and a signal processing portion 2603. The antenna 2601 is connected to a radio frequency portion 2602. In the downlink direction, the radio frequency part 2602 receives information transmitted by the network device through the antenna 2601, and transmits the information transmitted by the network device to the signal processing part 2603 for processing. In the uplink direction, the signal processing portion 2603 processes information of the terminal and sends the processed information to the radio frequency portion 2602, and the radio frequency portion 2602 processes information of the terminal and sends the processed information to the network device through the antenna 2601.

The signal processing section 2603 may include a modem subsystem for implementing processing of the respective communication protocol layers of data; the system also comprises a central processing subsystem for realizing the processing of the terminal operating system and the application layer; in addition, other subsystems, such as a multimedia subsystem for enabling control of a terminal camera, screen display, etc., a peripheral subsystem for enabling connection with other devices, etc., may also be included. The modem subsystem may be a separately provided chip. Alternatively, the above means for the terminal may be located in the modem subsystem.

The modem subsystem may include one or more processing elements, including, for example, a master and other integrated circuits. The modulation and demodulation subsystem may further include a storage element and an interface circuit. The storage element is used for storing data and programs, but the program for executing the method executed by the terminal in the above method may not be stored in the storage element, but in a memory outside the modulation and demodulation subsystem, and the modulation and demodulation subsystem is loaded for use when in use. The interface circuit is used to communicate with other subsystems. The above means for a terminal may be located in a modem subsystem which may be implemented by a chip comprising at least one processing element for performing the steps of any of the methods performed by the above terminal and interface circuitry for communicating with other means. In one implementation, the unit of the terminal implementing each step in the above method may be implemented in the form of a processing element scheduler, for example, the apparatus for a terminal includes a processing element and a storage element, and the processing element invokes the program stored in the storage element to perform the method performed by the terminal in the above method embodiment. The memory element may be a memory element where the processing element is on the same chip, i.e. an on-chip memory element.

In another implementation, the program for executing the method executed by the terminal in the above method may be a storage element on a different chip than the processing element, i.e. an off-chip storage element. At this time, the processing element calls or loads a program from the off-chip storage element on the on-chip storage element to call and execute the method executed by the terminal in the above method embodiment.

In yet another implementation, the unit of the terminal implementing each step in the above method may be configured as one or more processing elements, which are disposed on the modem subsystem, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

The units of the terminal implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC) chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the processing element invokes the stored program of the storage element to implement the method executed by the terminal; or at least one integrated circuit may be integrated in the chip for implementing the method performed by the above terminal; or may be combined with the above implementation, the functions of part of the units are implemented in the form of processing element calling programs, and the functions of part of the units are implemented in the form of integrated circuits.

It will be seen that the above apparatus for a terminal may comprise at least one processing element and interface circuitry, wherein the at least one processing element is adapted to perform any of the methods performed by the terminal provided by the above method embodiments. The processing element may be configured in a first manner: that is, a part or all of the steps executed by the terminal are executed in a mode of calling the program stored in the storage element; the second way is also possible: i.e. by means of integrated logic circuitry of hardware in the processor element in combination with instructions to perform part or all of the steps performed by the terminal; of course, it is also possible to perform part or all of the steps performed by the terminal in combination with the first and second modes.

Claims

1. A method of configuration, comprising:

receiving a Radio Resource Control (RRC) connection release message, wherein the RRC connection release message comprises first information used for indicating target configuration parameters; the target configuration parameters include: radio bearer configuration parameters and cell group configuration parameters;

Entering a non-activated state according to the RRC connection release message, and determining a non-activated state context parameter according to the first information, wherein the non-activated state context parameter comprises the target configuration parameter, or the non-activated state context parameter comprises a parameter except the target configuration parameter in the terminal context parameter;

The first information is an identifier corresponding to the target configuration parameter; the terminal stores a mapping relation between an identifier corresponding to a configuration parameter and the configuration parameter, and the determining the context parameter of the inactive state according to the first information includes:

and determining that the non-activated context parameters comprise the target configuration parameters corresponding to the identifiers according to the identifiers corresponding to the target configuration parameters and the mapping relation.

2. The method according to claim 1, wherein the method further comprises:

And reporting the non-activated capacity information of the terminal.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and receiving a first instruction, wherein the first instruction is used for indicating the terminal to monitor a physical downlink control channel when the terminal is in an inactive state.

4. The method of claim 3, wherein the step of,

The first indication is included in the RRC connection release message.

5. The method according to any one of claims 1-2, 4, wherein the method further comprises:

and receiving a second instruction, wherein the second instruction is used for indicating that the terminal is allowed to perform uplink transmission when the terminal is in an inactive state.

6. The method of claim 5, wherein the receiving the second indication comprises:

sending a random access request;

and receiving a response message of the random access request, wherein the response message comprises an uplink grant and the second indication, and the second indication is used for indicating that uplink transmission is allowed on the uplink grant in a non-activated state.

7. A method of configuration, comprising:

Determining a target configuration parameter; the target configuration parameters include: radio bearer configuration parameters and cell group configuration parameters;

Transmitting a Radio Resource Control (RRC) connection release message, wherein the RRC connection release message comprises first information, and the first information is an identifier corresponding to the target configuration parameter; the first information is used for indicating the target configuration parameter, the RRC connection release message is used for indicating the terminal to enter a non-activated state according to the RRC connection release message, and the first information is used for indicating the terminal to determine a non-activated state context parameter, wherein the non-activated state context parameter comprises the target configuration parameter, or the non-activated state context parameter comprises a parameter except the target configuration parameter in the terminal context parameter;

The method further comprises the steps of:

and sending the mapping relation between the identifiers corresponding to the configuration parameters and the configuration parameters.

8. The method of claim 7, wherein the determining the target configuration parameter comprises:

Receiving a session establishment request from core network equipment, wherein the session establishment request comprises a session type, and the session type is used for indicating that a terminal is allowed to perform uplink transmission when the terminal is in an inactive state;

And determining the target configuration parameters based on the session type.

9. The method of claim 8, wherein the method further comprises:

And sending a session establishment response to the core network equipment.

10. The method according to any one of claims 7-9, further comprising:

And sending a first instruction, wherein the first instruction is used for indicating the terminal to monitor the physical downlink control channel when the terminal is in an inactive state.

11. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

The first indication information is included in the RRC connection release message.

12. The method according to any one of claims 7-9, 11, wherein the method further comprises:

and sending a second instruction, wherein the second instruction is used for indicating that the terminal is allowed to perform uplink transmission when the terminal is in an inactive state.

13. The method of claim 12, wherein the sending the second indication comprises:

Receiving a random access request;

And sending a response message of the random access request, wherein the response message comprises an uplink grant and the second indication, and the second indication is used for indicating that uplink transmission is allowed on the uplink grant in a non-activated state.

14. A configuration device, comprising: means for performing the steps of any of the preceding claims 1 to 6.

15. A configuration device, comprising: a processor for invoking a program in memory to perform the method of any of claims 1 to 6.

16. A configuration device, comprising: a processor for communicating with other devices and interface circuitry for performing the method of any of claims 1 to 6.

17. A configuration device, comprising: a unit for performing the steps of any of the preceding claims 7 to 13.

18. A configuration device, comprising: a processor for invoking a program in memory to perform the method of any of claims 7 to 13.

19. A configuration device, comprising: a processor for communicating with other devices and interface circuitry for performing the method of any of claims 7 to 13.

20. A computer readable storage medium storing a program which, when invoked by a processor, performs the method of any one of claims 1 to 13.

21. A computer program product comprising a program and when the program is called by a processor the method of any of claims 1 to 13 is performed.