WO2021062974A1 - 配置方法和装置 - Google Patents

配置方法和装置 Download PDF

Info

Publication number
WO2021062974A1
WO2021062974A1 PCT/CN2020/075402 CN2020075402W WO2021062974A1 WO 2021062974 A1 WO2021062974 A1 WO 2021062974A1 CN 2020075402 W CN2020075402 W CN 2020075402W WO 2021062974 A1 WO2021062974 A1 WO 2021062974A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
timer
information
network device
uplink
Prior art date
Application number
PCT/CN2020/075402
Other languages
English (en)
French (fr)
Inventor
徐小英
曾清海
戴明增
黄曲芳
娄崇
陈雁
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080062554.8A priority Critical patent/CN114679919B/zh
Priority to EP20871813.0A priority patent/EP4030809A4/en
Publication of WO2021062974A1 publication Critical patent/WO2021062974A1/zh
Priority to US17/707,614 priority patent/US20220225465A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • This application relates to the field of communication technology, and in particular to a configuration method and device.
  • the state of the terminal can be divided into three types, which are connected state, inactive state (also called deactivated state) and idle state. )state.
  • the connection state is the state in which the terminal establishes a connection through radio resource control (RRC) connection, RRC connection re-establishment, and RRC connection recovery has completed connection establishment with the access network equipment and core network equipment; inactive
  • RRC radio resource control
  • the state is that 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 terminal's context (such as the terminal's identity);
  • the idle state is the terminal disconnected state.
  • the connection with the access network device and the core network device is opened, and the access network device releases the state of the context of the terminal.
  • the network device For a terminal in the connected state, the network device will send configuration information for the terminal in the connected state, so that the terminal is configured according to the configuration information, and then the terminal performs data transmission based on the configuration. If the network device detects that the terminal has no data transmission for a long time, it will send an RRC connection release message to the terminal to instruct the terminal to enter the inactive state from the connected state through the RRC connection release message. After the terminal enters the inactive state, the configuration information received when it is in the connected state will no longer be adapted to the terminal that is currently in the inactive state.
  • the embodiments of the present application provide a configuration method and device, after the terminal enters the inactive state from the connected state, it is possible to reasonably indicate the configuration parameters for the terminal in the inactive state.
  • an embodiment of the present application provides a configuration method.
  • the configuration method may include: receiving a radio resource control RRC connection release message, where the RRC connection release message includes first information, and the first information is used to indicate target configuration parameters; and The RRC connection release message enters the inactive state, and the inactive state context parameters are determined according to the first information, wherein the inactive state context parameters include target configuration parameters, or the inactive state context parameters include terminal context parameters except for Parameters other than target configuration parameters.
  • a configuration device which includes units or means for executing each step of the first aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the above first aspect.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the first aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above first aspect.
  • a computer program is provided, which is used to execute the method of the above first aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above first aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the RRC connection release message can carry the configuration parameters allocated to the inactive terminal in the RRC connection release message, namely The terminal receives the radio resource control RRC connection release message sent by the network device.
  • the RRC connection release message includes the first information used to indicate the target configuration parameter; in this way, the terminal can enter the inactive state according to the RRC connection release message, and according to the first information Determine the access layer context parameters in the inactive state, where the access layer context parameters in the inactive state include target configuration parameters, or the inactive context parameters include parameters other than the target configuration parameters in the context parameters of the terminal, Therefore, it is possible to reasonably indicate configuration parameters for the terminal in the inactive state.
  • the network device when the network device reasonably indicates the configuration parameters for the inactive terminal through the first information, it can be divided into two different scenarios.
  • the network device may indicate the configuration parameters configured for the terminal in the inactive state through the first information, so that the terminal retains the configuration parameters configured for the terminal.
  • the network device may indicate the configuration parameters that need to be released by the terminal in the inactive state through the first information, so that the terminal in the inactive state releases the configuration parameters that need to be released.
  • the target configuration parameters indicated by the first information are different.
  • the target configuration parameters include: radio bearer configuration parameters, and/or cell group configuration parameters
  • the network device configures the parameters of the radio bearers for multiple terminals
  • the configuration parameters of the cell group are solidified so that at least two terminals correspond to the same set of configuration parameters, so that when multiple terminals enter the inactive state from the connected state, for the network device, the configuration of the at least two terminals is stored
  • the configuration parameters of the at least two terminals is stored
  • only one set of configuration information needs to be stored, thereby reducing the storage overhead of network equipment.
  • the first information is an identifier corresponding to the target configuration parameter.
  • the terminal stores the identification corresponding to the configuration parameter and the mapping relationship between the configuration parameter, so that the terminal can determine the inactive state according to the identification corresponding to the target configuration parameter and the mapping relationship.
  • the context parameter includes identifying the corresponding target configuration parameter, so that the target configuration parameter is retained or released.
  • the first information includes target configuration parameters. Since the RRC connection release message directly carries target configuration parameters, the terminal can directly determine the target configuration parameters and retain or Release the target configuration parameters directly carried in the RRC connection release message. Although the target configuration parameters are carried in the RRC connection release message and sent to the terminal, the configuration signaling overhead will be large, but for the terminal, there is no need to predefine it in the protocol.
  • the information of the context configuration reduces the complexity of the protocol, and the terminal does not need to store the pre-configuration in advance, which reduces the storage overhead and configuration overhead of the terminal.
  • the foregoing configuration method further includes: reporting the inactive state capability information of the terminal, so that the network device can determine whether the terminal supports the inactive state according to the capability information reported by the terminal. Data transmission is carried out in the state.
  • the terminal when the terminal reports its capability information, it can report its capability information to the network device in at least four possible ways.
  • the four possible methods are: the terminal can support data transmission in the inactive state, the terminal supports configuring the context parameters of the terminal through a pre-configured identifier, and the terminal supports inactive Common parameter configuration in the state (in other words, the terminal supports lightweight access layer configuration parameters), and the terminal supports the data transmission session in the direct inactive state.
  • the expression modes are different, the four different modes can all indicate that the terminal supports data transmission in the inactive state.
  • a first indication is received, where the first indication is used to instruct the terminal to monitor the physical downlink control channel when in an inactive state.
  • the first indication information is included in the RRC release message.
  • it can also be carried in other messages, which can be specifically set according to actual needs.
  • the terminal may also 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.
  • the terminal may send a random access request; and receive a response message of the random access request.
  • the response message includes an uplink authorization and a second indication, and the second indication is used to indicate
  • the uplink transmission on the uplink authorization is allowed, so that when the terminal needs to transmit data, it can directly perform the uplink transmission on the uplink resources indicated by the uplink authorization, so that the terminal can complete the uplink transmission in the inactive state.
  • inventions of the present application also provide a configuration method.
  • the configuration method may include: determining target configuration parameters; and sending a radio resource control RRC connection release message.
  • the RRC connection release message includes first information, and the first information is used for Indicate target configuration parameters, the RRC connection release message is used to instruct the terminal to enter the inactive state according to the RRC connection release message, and the first information is used to instruct the terminal to determine the inactive state context parameters, where the inactive state context parameters include target configuration parameters , Or, the context parameters in the inactive state include parameters other than the target configuration parameters in the context parameters of the terminal.
  • a configuration device which includes units or means for performing each step of the second aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the second aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the second aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above second aspect.
  • a computer program is provided, which is used to execute the method of the above second aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above second aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the RRC connection release message can carry the configuration parameters allocated to the inactive terminal in the RRC connection release message, namely The terminal receives the radio resource control RRC connection release message sent by the network device.
  • the RRC connection release message includes the first information used to indicate the target configuration parameter; in this way, the terminal can enter the inactive state according to the RRC connection release message, and according to the first information Determine the context parameters of the inactive state, where the context parameters of the inactive state include target configuration parameters, or, the context parameters of the inactive state include parameters other than the target configuration parameters in the context parameters of the terminal, thereby achieving a reasonable
  • the terminal in the inactive state indicates the configuration parameters.
  • the target configuration parameters include: radio bearer configuration parameters, and/or cell group configuration parameters
  • the network device configures the parameters of the radio bearers for multiple terminals
  • the configuration parameters of the cell group are solidified so that at least two terminals correspond to the same set of configuration parameters, so that when multiple terminals enter the inactive state from the connected state, for the network device, the configuration of the at least two terminals is stored
  • the configuration parameters of the at least two terminals is stored
  • only one set of configuration information needs to be stored, thereby reducing the storage overhead of network equipment.
  • the first information is an identifier corresponding to the target configuration parameter.
  • the mapping relationship between the identifier corresponding to the configuration parameter and the configuration parameter is sent, so that the terminal can determine the inactive context parameter according to the identifier corresponding to the target configuration parameter and the mapping relationship Including the identification of the corresponding target configuration parameter, so as to retain or release the target configuration parameter.
  • the first information includes target configuration parameters. Since the RRC connection release message directly carries the target configuration parameters, the terminal can directly determine the target configuration parameters and retain or To release the target configuration parameter, although the target configuration parameter is carried in the RRC connection release message and sent to the terminal, the configuration signaling overhead will be higher, but for the terminal, there is no need to predefine the context configuration information in the protocol, thereby reducing The protocol is complicated, and the terminal does not need to store pre-configuration in advance, which reduces the configuration overhead of the storage overhead of the terminal.
  • a session establishment request from a core network device is received, the session establishment request includes a session type, and the session type is used to indicate that the terminal is allowed to perform uplink transmission when the terminal is in an inactive state; Based on the session type, the target configuration parameters are determined, so that the determined target configuration parameters are sent to the terminal.
  • the network device also sends a session establishment response to the core network device.
  • a first indication is sent, and the first indication is used to instruct the terminal to monitor the physical downlink control channel when in the inactive state.
  • the first indication information is included in the RRC release message.
  • it can also be carried in other messages, which can be specifically set according to actual needs.
  • a second indication is sent, and the second indication is used to indicate that the terminal is allowed to perform uplink transmission when the terminal is in an inactive state.
  • the network device may receive a random access request; and send a response message to the random access request.
  • the response message includes the uplink authorization and the second instruction, and the second instruction is used for Indicate that the uplink transmission on the uplink authorization is allowed when in the inactive state, so that when the terminal needs to perform data transmission, it can directly perform the uplink transmission on the uplink resources indicated by the uplink authorization, so that the terminal can complete the uplink transmission when in the inactive state.
  • an embodiment of the present application also provides a configuration method, and the configuration method may include:
  • the response message includes contention resolution information; the uplink authorization is received from the network device; and the uplink transmission is performed on the uplink resources indicated by the uplink authorization.
  • a configuration device which includes units or means for performing the steps of the third aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the third aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the third aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above third aspect.
  • a computer program is provided, which is used to execute the method of the third aspect above when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above third aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the terminal after receiving the contention resolution information, if the terminal has not received the RRC connection release message at this time, indicating that there is still data to be transmitted, it will receive the uplink authorization from the network device and authorize the uplink. Uplink transmission is performed on the indicated uplink resources without waiting until the RRC connection is restored, and the terminal does not need to enter the connected state to send data, which not only improves the efficiency of data transmission, but also reduces the overhead required for RRC connection restoration.
  • the timer is started or restarted, thereby delaying the duration of the terminal listening to the authorization.
  • the uplink authorization is received from the network device; and when the uplink authorization is received, the timer is restarted, thereby delaying the duration of the terminal monitoring the uplink authorization.
  • the downlink authorization is received from the network device; when the downlink authorization is received, the timer is restarted, thereby delaying the duration of the terminal monitoring the downlink authorization.
  • the timer is not always in the running state, but the timer is stopped when certain conditions are met, for example, the scenario of stopping the timer described above .
  • the control timer stops running, that is, the timer is stopped. It can be understood that when the terminal receives the RRC connection recovery, connection establishment message, etc. from the network device, the terminal can also stop the timer.
  • an embodiment of the present application also provides a configuration method.
  • the configuration method may include: receiving a first message from a terminal, the first message including a random access request and/or physical uplink shared channel data, and physical uplink shared channel data. It includes information for requesting to restore the RRC connection; and sends a response message of the first message to the terminal, the response message includes contention resolution information; sends an uplink grant to the terminal; and performs data transmission on the uplink resource indicated by the uplink grant.
  • a configuration device which includes units or means for performing the steps of the fourth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the fourth aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the fourth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above fourth aspect.
  • a computer program is provided, which is used to execute the method of the above fourth aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above fourth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the network device after receiving the first message sent by the terminal, the network device sends a response message including contention resolution information to the terminal. If the RRC connection release message has not been sent to the terminal at this time, it indicates that there is still data. If transmission is needed, the uplink authorization is sent to the terminal, so that the terminal can perform uplink transmission on the uplink resources indicated by the uplink authorization, without having to wait until the RRC connection is restored before performing the uplink transmission. There is no need for the terminal to enter the connected state to send data, which not only improves data transmission It is efficient and reduces the overhead required for RRC connection recovery.
  • the network device also 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 Run, that is, stop the timer. It can be understood that when the terminal receives a radio resource control RRC connection recovery, connection establishment message, etc. from the network device, the terminal can also stop the timer.
  • the embodiments of the present application also provide a configuration method.
  • the configuration method may include: sending a first message to a network device, where the first message includes a random access request and/or physical uplink shared channel data.
  • the data includes information used to request the restoration of the radio resource control RRC connection; and a response message of the first message is received from the network device, the response message includes uplink authorization and first indication information, the first indication information is used to indicate whether to allow the uplink authorization indication Uplink transmission is performed on the uplink resource; and uplink transmission is performed on the uplink resource according to the first indication information.
  • a configuration device which includes units or means for performing the steps of the fifth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the fifth aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, configured to be connected to a memory, and used to call a program stored in the memory to execute the method described in the fifth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above fifth aspect.
  • a computer program is provided, which is used to execute the method of the above fifth aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above fifth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the terminal sends an RRC connection recovery request to the network device, so that the network device can allocate the uplink authorization to the terminal when the terminal is in the inactive state, and indicate whether to allow the uplink authorization indication through the indication information
  • the uplink transmission is performed on the uplink resources of the terminal, which realizes that the terminal completes the uplink transmission in the inactive state, and does not need to wait until the RRC connection is restored to perform the uplink transmission.
  • the second message including the uplink data is sent to the network device on the uplink resource to achieve
  • the terminal completes the uplink transmission in the inactive state, and does not need to wait until the RRC connection is restored to perform the uplink transmission.
  • the terminal does not need to enter the connected state to send data, which not only improves the data transmission efficiency, but also reduces the overhead required for the RRC connection recovery.
  • a third message is sent to the network device on the uplink resource, where the third message Used to request the restoration of the RRC connection.
  • the third message sent by the terminal on the uplink resources indicated by the uplink authorization is only used to request the restoration of the RRC connection, and Does not include upstream data.
  • the third message may be an RRC connection recovery request.
  • the terminal starts or restarts the timer when receiving the response message of the first message, thereby delaying the duration of the terminal listening to the authorization.
  • the authorization is received from the network device; and when the authorization is received, the timer is restarted, thereby delaying the duration of the terminal listening to the authorization.
  • the timer after the timer is started or restarted, it is not always in a running state, but stops the timer when certain conditions are met, such as the scenario of stopping the timer described above .
  • the control timer stops running, that is, the timer is stopped. It can be understood that when the terminal receives a radio resource control RRC connection recovery, connection establishment message, etc. from the network device, the terminal can also stop the timer.
  • the response message includes contention resolution information.
  • the contention resolution information may be the identification of the terminal, or partial information of the second message, or partial information of the third message.
  • the terminal After the terminal receives the contention resolution information, if it has not received the RRC connection release message at this time, the terminal starts or restarts the timer, and receives authorization from the network device during the timer operation; the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink authorization; if the downlink authorization is received from the network device, and it has not been received
  • the terminal starts or restarts the timer, and waits for the time for the RRC connection release message, so that the terminal can complete the uplink transmission when the RRC connection is inactive, without having to wait until the RRC connection is restored
  • Uplink transmission does not require the terminal to enter the connected state to send data, which not only improves the efficiency of data transmission, but also reduces the overhead required for RRC connection recovery.
  • the first message further includes second indication information, and the second indication information is used to indicate a comparison result between the amount of data to be sent by the terminal and the data amount threshold.
  • inventions of the present application also provide a configuration method.
  • the configuration method may include: receiving a first message from a terminal, where the first message includes a random access request and/or physical uplink shared channel data, and physical uplink shared channel data. It includes information for requesting the restoration of the radio resource control RRC connection; and sends a response message of the first message to the terminal.
  • the response message includes uplink authorization and first indication information.
  • the first indication information is used to indicate whether to allow the uplink authorization indication in the uplink. Perform uplink transmission on the resource; perform uplink transmission on the uplink resource according to the first indication information.
  • a configuration device which includes units or means for executing each step of the sixth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the sixth aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, configured to be connected to a memory, and used to call a program stored in the memory to execute the method described in the sixth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above sixth aspect.
  • a computer program is provided, which is used to execute the method of the above sixth aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above sixth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the network device receives the RRC connection recovery request sent by the terminal, allocates an uplink grant to the terminal when the terminal is in an inactive state, and indicates whether to allow the uplink resource indicated by the uplink grant through the indication information It realizes that the terminal completes the uplink transmission when in the inactive state, and does not need to wait until the RRC connection is restored to perform the uplink transmission. There is no need for the terminal to enter the connected state to send data, which not only improves the efficiency of data transmission, but also reduces the recovery of the RRC connection. The required overhead.
  • the second message including the uplink data is received from the terminal on the uplink resource, thereby realizing the terminal
  • the uplink transmission is completed in the inactive state, and the uplink transmission does not need to wait until the RRC connection is restored, and the terminal does not need to enter the connected state to send data, which not only improves the data transmission efficiency, but also reduces the overhead required for the RRC connection recovery.
  • a third message is received from the terminal on the uplink resource, where the third message is To request to restore the RRC connection.
  • the third message received by the network device on the uplink resource indicated by the uplink authorization is only used to request the restoration of the RRC connection. Does not include upstream data.
  • the third message may be an RRC connection recovery request.
  • a 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, that is, it stops. Timer. It can be understood that when the terminal receives a radio resource control RRC connection recovery, connection establishment message, etc. from the network device, the terminal can also stop the timer.
  • the response message includes contention resolution information.
  • the contention resolution information may be the identification of the terminal, or partial information of the second message, or partial information of the third message.
  • the first message further includes second indication information, and the second indication information is used to indicate a comparison result between the amount of data to be sent by the terminal and the data amount threshold.
  • the embodiments of the present application also provide a configuration method.
  • the configuration method may include: receiving indication information, where the indication information is used to instruct the terminal to monitor the physical downlink scrambled by the cell radio network temporary identification C-RNTI when in an inactive state Control the channel PDCCH; and monitor the PDCCH scrambled by the C-RNTI according to the indication information.
  • a configuration device which includes units or means for performing the steps of the seventh aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the seventh aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, configured to be connected to a memory and used to call a program stored in the memory to execute the method described in the seventh aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the seventh aspect above.
  • a computer program is provided, which is used to execute the method of the seventh aspect above when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the seventh aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the terminal receives the indication information sent by the network device, the indication information instructs the terminal to monitor the C-RNTI scrambled PDCCH when in the inactive state, and is in the process of monitoring the C-RNTI scrambled PDCCH
  • the whole receiving process does not need to receive paging or initiate an RRC connection recovery request, but directly receives the downlink data in the inactive state, which not only improves the transmission efficiency, but also reduces the terminal's overhead .
  • the terminal may receive a radio resource control RRC connection release message, and the RRC connection release message includes indication information, thereby obtaining the indication information. It is understandable that the instruction information can also be carried in the broadcast message.
  • the indication information can be realized by one bit.
  • the value of this bit is 1, which means that the function of monitoring the physical downlink control channel (PDCCH) scrambled by C-RNTI when in the inactive state is enabled, and the value of this bit is 0 means that the function of monitoring the physical downlink control channel (PDCCH) scrambled by the C-RNTI in the inactive state is not enabled.
  • the indication information can also be implemented through enumeration type, for example: ⁇ TURE ⁇ , ⁇ downlink reception ⁇ . Since the PDCCH is scrambled by the cell radio network temporary identity (C-RNTI), in another implementation, the indication information may be C-RNTI.
  • the terminal when the C-RNTI is carried in the RRC connection release message, the terminal is indicated Monitor the PDCCH scrambled by the C-RNTI in the inactive state; when the RRC connection release message does not carry the C-RNTI, the terminal is instructed not to monitor the PDCCH in the inactive state.
  • the terminal monitoring the PDCCH scrambled by the C-RNTI may include: determining the paging occasion, and monitoring the C- in part of the time slot or part of the paging frame of the paging occasion.
  • RNTI scrambled PDCCH so that for the terminal, there is no need to receive paging or initiate an RRC connection recovery request, but to directly receive downlink data in the inactive state, which not only improves the transmission efficiency, but also reduces the terminal's overhead.
  • the terminal monitoring the PDCCH scrambled by the C-RNTI may include: receiving a first parameter, and determining a paging occasion according to the first parameter; and receiving a second parameter, according to The second parameter determines the timing of monitoring the C-RNTI scrambled PDCCH, where the paging timing is different from the timing of monitoring the C-RNTI scrambled PDCCH, so that for the terminal, there is no need to receive paging or initiate an RRC connection recovery request.
  • the terminal when the terminal moves out of the effective area of the C-RNTI, it stops monitoring the PDCCH scrambled by the C-RNTI, thereby reducing the power consumption of the terminal.
  • the embodiments of the present application also provide a configuration method, which may include: determining that the terminal can monitor the physical downlink control channel PDCCH scrambled by the cell radio network temporary identifier C-RNTI when in an inactive state; and reporting to the terminal Send indication information, which is used to instruct the terminal to monitor the physical downlink control channel PDCCH scrambled by the cell radio network temporary identifier C-RNTI when the terminal is in the inactive state.
  • a configuration device which includes units or means for performing the steps of the eighth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the eighth aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the eighth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above eighth aspect.
  • a computer program is provided, which is used to execute the method of the above eighth aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above eighth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the network device sends indication information to the terminal to instruct the terminal to monitor the C-RNTI scrambled PDCCH when in the inactive state, so that the terminal can monitor the C-RNTI scrambled PDCCH.
  • the downlink data is received in the process.
  • the entire receiving process does not need to receive paging or initiate an RRC connection recovery request. Instead, the downlink data is directly received in the inactive state, which not only improves the transmission efficiency, but also reduces the terminal’s performance. Overhead.
  • the network device may send a radio resource control RRC connection release message to the terminal, and the RRC connection release message includes indication information, so that the terminal can obtain the indication information. It is understandable that the instruction information can also be carried in the broadcast message.
  • 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 sends the second parameter to the terminal.
  • the second parameter is used for the terminal to determine the timing of monitoring the C-RNTI scrambled PDCCH according to the second parameter.
  • the paging timing is different from the timing of monitoring the C-RNTI scrambled PDCCH.
  • the embodiments of the present application also provide a configuration method, which may include: in response to a radio resource control RRC connection recovery requirement, the terminal starts a first timer, and sends an RRC connection recovery request message to the network device; the terminal; During the running of the first timer, according to the downlink information received from the network device or according to the data transmission with the network device, restart the first timer or start the second timer.
  • a configuration device which includes units or means for performing the steps of the ninth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the above ninth aspect.
  • the processor includes one or more.
  • a configuration device including a processor, configured to be connected to a memory and used to call a program stored in the memory to execute the method described in the ninth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the above ninth aspect.
  • a computer program is provided, which is used to execute the method of the above ninth aspect when being executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above ninth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • the terminal restarts the first timer or starts the second timer according to the downlink information received from the network device or the data transmission with the terminal, so that the terminal can start the first timer or the second timer.
  • Data transmission during operation can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, thereby flexibly supporting multiple data transmissions.
  • the configuration method provided in the embodiment of the present application may include at least two possible scenarios.
  • a possible scenario when the terminal responds to the RRC connection recovery demand, it starts the first timer, and meets the restart condition during the running of the first timer, restarts the first timer to extend the terminal waiting for RRC The time of the RRC response message for the connection recovery request.
  • the restarted timer when the restart condition is met, the restarted timer is the same timer as the restarted timer when the RRC connection is restored, and both are the first timers.
  • the terminal when the terminal responds to the RRC connection recovery demand, it starts the first timer, and when the start condition is met during the running of the first timer, the second timer is started to extend the waiting time of the terminal.
  • the time of the RRC response message of the RRC connection recovery request when the restart condition is met, the restarted timer is not a timer, but a new timer that is additionally set when the restarted timer is required for the recovery of the RRC connection. Device.
  • the first timer after starting the second timer, the first timer can also be stopped; of course, the first timer can also be stopped first, and then the second timer can be started, or after starting the second timer. At the same time as the second timer, stop the first timer. In this way, the second timer is used to take over the work of the first timer to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the terminal sends uplink data to the network device, and the uplink data is sent together with the RRC connection recovery request message or independently, wherein the downlink information includes the feedback information of the uplink data, and the uplink data and the RRC connection recovery request message are sent independently.
  • the data feedback information is used to indicate whether the uplink data is successfully transmitted.
  • the common transmission or independent transmission in this application refers to whether the uplink data and the RRC connection recovery request message are sent through the same message, such as a MAC PDU message. If the uplink data and the RRC connection recovery request message are sent through the same message, it can be understood as The uplink data and the RRC connection recovery request message are sent together; on the contrary, if the uplink data and the RRC connection recovery request message are not sent in the same message, it can be understood that the uplink data and the RRC connection recovery request message are sent independently. In addition, if the uplink data and the RRC connection recovery request message are sent independently, the uplink data may be sent during the running period of the first timer after the RRC connection recovery request message is sent.
  • the downlink information includes contention resolution information. If the contention resolution information is successful contention resolution, it means that the RRC connection recovery request message is sent successfully, and the terminal can continue to pre-configure the authorization. Send new uplink data; on the contrary, if the contention resolution information is that the contention resolution failed, it means that the RRC connection recovery request message has failed to be sent, and the terminal can continue to retransmit the RRC connection recovery request message on the pre-allocation authorization.
  • the downlink information includes uplink grant information
  • the uplink resources indicated by the uplink grant information can be used for retransmission of the original uplink data, and can also be used for the initial transmission of new uplink data. Transmission, to realize the data transmission of multiple consecutive packets. Under normal circumstances, if there is original uplink data that needs to be retransmitted, and new uplink data needs to be transmitted initially, the new uplink data can be first transmitted through the uplink resources indicated by the uplink authorization information, that is, the transmission priority of the initial data transmission. Higher than the transmission priority of data retransmission.
  • the terminal transmits uplink data by using the uplink resource indicated by the uplink grant information.
  • the downlink information includes downlink resource allocation information, and the downlink resource indicated by the downlink resource allocation information can be used for retransmission of original downlink data or for new downlink data.
  • uplink authorization information and downlink resource allocation information can exist independently, that is, the downlink information received by the terminal can include uplink authorization information or downlink resource allocation information; uplink authorization information and downlink resource allocation information can exist at the same time , Combined with each other, that is, the downlink information received by the terminal can include both uplink grant information and downlink resource allocation information.
  • the terminal receives downlink data on the downlink resource indicated by the downlink resource allocation information.
  • the downlink information includes indication information
  • the indication information is used to instruct the terminal to restart the first timer, so that the terminal can restart the first timer after receiving the information including the indication information.
  • the first timer enables data transmission during the operation of the first timer, which can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly supports multiple data transmissions.
  • the terminal receives the broadcast message or the RRC message from the network device, the broadcast message or the RRC message includes the information of the first timer, and the information of the first timer is used to indicate the first timer.
  • the duration of a timer so that the terminal can configure the duration of the first timer according to the information of the first timer.
  • the first timer is a T319 timer.
  • the first timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the terminal should access the network from the network while the first timer is running. For the downlink information received by the device or the data transmission between the device and the network device, restart the first timer; or,
  • the first timer is a T319 timer
  • the second timer is an RRC layer timer or a MAC layer timer other than the T319 timer.
  • the terminal is based on the downlink received from the network device. According to information or data transmission with the network device, the second timer is started or restarted.
  • the terminal sends instruction information to the network device, and the instruction information is used to indicate the first timer or the second timer started by the network device, so as to change the currently started timing
  • the information of the device is synchronized to the network device.
  • the first timer is stopped, which can reduce the power consumption caused by the running state of the first timer.
  • the terminal stops the first timer or the second timer when receiving the RRC connection recovery, RRC connection establishment, or RRC connection release message from the network device.
  • the embodiments of the present application also provide a configuration method.
  • the configuration method may include: receiving a radio resource control RRC connection recovery request message from the terminal, where the RRC connection recovery request message is a requirement of the terminal to recover the radio resource control RRC connection. It is sent after the first timer is started; during the operation of the first timer, it sends downlink information to the terminal or performs data transmission with the terminal, and is used to indicate that it is based on the downlink information received from the network device or based on the data between the network device and the network device. To transmit, restart the first timer or start the second timer.
  • a configuration device which includes units or means for performing the steps of the tenth aspect above.
  • a configuration device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the tenth aspect above.
  • the processor includes one or more.
  • a configuration device including a processor, which is connected to a memory and used to call a program stored in the memory to execute the method described in the tenth aspect above.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a configuration device which includes at least one processor and at least one memory, and the at least one processor is configured to execute the method provided in the tenth aspect above.
  • a computer program is provided, which is used to perform the method of the tenth aspect above when the computer program is executed by a processor.
  • a computer-readable storage medium stores a program, and when the program is called by a processor, the method of the above tenth aspect is executed.
  • a program product such as a computer-readable storage medium, including the above program.
  • 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 first timer according to the downlink information received from the network device or data transmission with the terminal.
  • Two timers so that the terminal can transmit data during the operation of the first timer or the second timer, which can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, thereby flexibly supporting multiple data transmissions .
  • the uplink data is received from the terminal, and the uplink data is sent together or independently with the RRC connection recovery request message, where the downlink information includes the feedback information of the uplink data, and the information of the uplink data The feedback information is used to indicate whether the uplink data is successfully transmitted.
  • the common transmission or independent transmission in this application refers to whether the uplink data and the RRC connection recovery request message are sent through the same message, such as a MAC PDU message. If the uplink data and the RRC connection recovery request message are sent through the same message, it can be understood as The uplink data and the RRC connection recovery request message are sent together; on the contrary, if the uplink data and the RRC connection recovery request message are not sent in the same message, it can be understood that the uplink data and the RRC connection recovery request message are sent independently. In addition, if the uplink data and the RRC connection recovery request message are sent independently, the uplink data may be sent during the running period of the first timer after the RRC connection recovery request message is sent.
  • the downlink information includes contention resolution information. If the contention resolution information is that the contention resolution is successful, it means that the RRC connection recovery request message is sent successfully, and the terminal can continue to pre-configure the authorization. Send new uplink data; on the contrary, if the contention resolution information is that the contention resolution failed, it means that the RRC connection recovery request message has failed to be sent, and the terminal can continue to retransmit the RRC connection recovery request message on the pre-allocation authorization.
  • the downlink information includes uplink grant information
  • the uplink resources indicated by the uplink grant information can be used for retransmission of the original uplink data, and can also be used for the initial transmission of new uplink data. Transmission, to realize the data transmission of multiple consecutive packets. Under normal circumstances, if there is original uplink data that needs to be retransmitted, and new uplink data needs to be transmitted initially, the new uplink data can be first transmitted through the uplink resources indicated by the uplink authorization information, that is, the transmission priority of the initial data transmission. Higher than the transmission priority of data retransmission.
  • the uplink data sent by the uplink resource indicated by the uplink grant information is received from the terminal.
  • the downlink information includes downlink resource allocation information, and the downlink resources indicated by the downlink resource allocation information can be used for retransmission of the original downlink data or for new downlink data.
  • uplink authorization information and downlink resource allocation information can exist independently, that is, the downlink information received by the terminal can include uplink authorization information or downlink resource allocation information; uplink authorization information and downlink resource allocation information can exist at the same time , Combined with each other, that is, the downlink information received by the terminal can include both uplink grant information and downlink resource allocation information.
  • the downlink data is sent to the terminal on the downlink resource indicated by the downlink resource allocation information.
  • the downlink information includes indication information
  • the indication information is used to instruct the terminal to restart the first timer, so that the terminal can restart the first timer after receiving the information including the indication information.
  • the first timer enables data transmission during the operation of the first timer, which can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly supports multiple data transmissions.
  • a broadcast message or an RRC message is sent to the terminal.
  • the broadcast message or the RRC message includes the information of the first timer, and the information of the first timer is used to indicate the first timing.
  • the duration of the first timer so that the terminal can configure the duration of the first timer according to the information of the first timer.
  • the first timer is a T319 timer.
  • the first timer is an RRC layer timer or a MAC layer timer other than the T319 timer, and the first timer is the first timer of the terminal.
  • the downlink information that should be received from the network device or the data transmission with the network device should be restarted; or,
  • the first timer is a T319 timer
  • the second timer is an RRC layer timer or a MAC layer timer other than the T319 timer
  • the second timer is the terminal during the operation of the first timer, according to the slave network
  • the downlink information received by the device is started or restarted based on the data transmission with the network device.
  • the indication information is received from the terminal, and the indication information is used to indicate the first timer or the second timer started by the network device, so as to change the value of the currently started timer Information is synchronized to network equipment.
  • the devices shown in the above aspects can be a chip, and the processor can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.;
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • processors There are one or more processors and one or more memories.
  • the memory can be integrated with the processor, or the memory and the processor can be provided separately.
  • the memory and the processor may be integrated on the same chip, or may be separately arranged on different chips.
  • the embodiment of the present application does not limit the type of the memory and the way of setting the memory and the processor.
  • the above information transmission or receiving process can be a process of outputting a random access request from the processor, receiving a response message of a random access request, or receiving a response message of an input random access request from the processor. process.
  • the random access request output by the processor may be output to the transmitter, and the response message of the input random access request received by the processor may come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of a network architecture provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of another network architecture provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a configuration method provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of another configuration method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a process of negotiating and determining various configuration parameter sets according to an embodiment of the application
  • FIG. 7 is a schematic flowchart of releasing parameters other than the target configuration parameter in the context parameters of the terminal according to an embodiment of the application;
  • FIG. 8 is a schematic diagram of a process for allocating a suitable configuration parameter set to a terminal according to an embodiment of the application
  • FIG. 9 is a schematic flowchart of a configuration method provided by an embodiment of the application.
  • FIG. 10 is a schematic flowchart of another configuration method provided by an embodiment of the application.
  • FIG. 11 is a schematic flowchart of yet another configuration method provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a MAC message provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of another MAC message provided by an embodiment of this application.
  • FIG. 14 is a schematic flowchart of yet another configuration method provided by an embodiment of this application.
  • FIG. 15 is a schematic flowchart of a configuration method provided by an embodiment of this application.
  • FIG. 16 is a schematic diagram of determining a timing to monitor a PDCCH scrambled by C-RNTI according to an embodiment of the application;
  • FIG. 17 is another schematic diagram of determining the timing of monitoring the PDCCH scrambled by C-RNTI according to an embodiment of the application.
  • FIG. 18 is another schematic diagram of determining a timing to monitor a PDCCH scrambled by C-RNTI according to an embodiment of the application;
  • FIG. 19 is another schematic diagram of determining a timing to monitor a PDCCH scrambled by C-RNTI according to an embodiment of the application.
  • FIG. 20 is a schematic flowchart of a configuration method provided by an embodiment of this application.
  • FIG. 21 is a schematic flowchart of another configuration method provided by an embodiment of this application.
  • FIG. 22 is a schematic flowchart of yet another configuration method provided by an embodiment of this application.
  • FIG. 23 is a schematic flowchart of yet another configuration method provided by an embodiment of this application.
  • FIG. 24 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • FIG. 25 is a schematic structural diagram of another network device provided by an embodiment of this application.
  • FIG. 26 is a schematic structural diagram of a terminal provided by an embodiment of this application.
  • the embodiments of this application are applied to communication systems, such as wideband code division multiple access (WCDMA), time division-synchronization code division multiple access (TD-SCDMA), long-term evolution System (long term evolution, LTE), public land mobile network (public land mobile network, PLMN) system, even fifth generation (5th generation, 5G) communication system or other systems that may appear in the future, the following are some of the terms in this application The explanation is provided to facilitate the understanding of those skilled in the art. It should be noted that when the solution of the embodiment of this application is applied to a 5G system or other systems that may appear in the future, the names of network devices and terminals may change, but this does not affect the implementation of the solution of the embodiment of this application.
  • WCDMA wideband code division multiple access
  • TD-SCDMA time division-synchronization code division multiple access
  • LTE long-term evolution System
  • PLMN public land mobile network
  • 5G fifth generation
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • the communication system shown in this application scenario may include at least one terminal and network equipment, and of course, may also include core network equipment.
  • the RRC connection release message can carry the configuration parameters allocated to the inactive terminal in the RRC connection release message, that is, the terminal receives the radio resource control sent by the network device.
  • the RRC connection release message includes 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 parameters of the inactive state according to the first information, where ,
  • the context parameters in the inactive state include target configuration parameters, or the context parameters in the inactive state include parameters other than the target configuration parameters in the context parameters of the terminal, so as to reasonably indicate the configuration parameters for the terminal in the inactive state.
  • the network device when the network device reasonably indicates the configuration parameters for the inactive terminal through the first information, it can be divided into two different scenarios.
  • the network device may indicate the configuration parameters configured for the terminal in the inactive state through the first information, so that the terminal retains the configuration parameters configured for the terminal.
  • the network device may indicate the configuration parameters that need to be released by the terminal in the inactive state through the first information, so that the terminal in the inactive state releases the configuration parameters that need to be released.
  • the target configuration parameters indicated by the first information are different.
  • terminal configuration parameters can be divided into three types.
  • the three types of configuration parameters are security configuration parameters, radio bearer configuration parameters, and cell group configuration parameters. Since the security configuration parameters of each terminal are different, Therefore, the security configuration parameters are not solidified; however, the radio bearer configuration parameters of the terminal and/or the cell group configuration parameters can be solidified.
  • the configuration of the at least two terminals is stored For information, only one set of configuration information needs to be stored, thereby reducing the storage overhead of network equipment.
  • the target configuration parameters indicated by the first information may also include radio bearer configuration parameters, and/or cell group configuration parameters; as for the network device
  • the security configuration parameters configured for the terminal can be sent to the terminal separately, of course, can also be sent to the terminal together with the first information, and can be specifically set according to actual needs.
  • the inactive context parameters in the following embodiments of the present application do not include security configuration parameters, and refer to radio bearer configuration parameters and cell group configuration parameters.
  • the radio bearer configuration parameters may include packet data convergence protocol (PDCP) layer parameters, service data adaptation protocol (service data adaptation protocol, SDAP) layer parameters, and data bearer (data radio bearer, DRB) identification
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • DRB data bearer
  • EPS evolved packet system
  • Cell group configuration parameters can include cell group identification, bearer radio link control (RLC) configuration parameters, medium access control (MAC) layer cell group configuration parameters, physical cell group configuration parameters, One or more of the configuration parameters of the dedicated cell (PSCell+PCell, Spcell) and the configuration parameters of the secondary cell (Secondary Cell, Scell).
  • the PDCP layer parameters may include a timeout timer (discardTimer), uplink and downlink PDCP SN size header compression configuration, full protection open, acknowledged mode (acknowledged mode, AM) carried PDCP status report needs, out of order sending, offloading ( split) or duplication (duplication) configuration and reordering timer, etc.
  • SDAP layer parameters can include one of the session identifier (Session ID), the presence or absence of the uplink/downlink SDAP header, whether it is the default data bearer (data radio bearer, DRB), and the quality of service flow identifier (qoS flow identifier, QFI), etc. Or more.
  • Session ID session identifier
  • DRB data radio bearer
  • QFI quality of service flow identifier
  • the cell group identifier may include an identifier indicating the primary cell group or the secondary cell group;
  • the bearer RLC configuration parameters may include three types of information, one type of information is identification information, including radio bearer (RB) identifiers, Logical channel (logical channel, LCH) identification; one type of information is RLC configuration information, including RLC PDU SN length, segment reassembly timer, Acknowledged Mode (Acknowledged Mode, AM) RLC maximum retransmission times, control
  • the AM mode RLC sends the status report request parameters to the receiving end and the AM RLC sends the RLC status report prohibit timer;
  • one type of information is the logical channel configuration information, which can include the parameters used in the priority processing process (for example, allow The sub-carrier spacing of the physical uplink shared channel (physical uplink shared channel, PUSCH) transport block (transport block, TB) duration, transmission rate, logical channel priority, etc.) and the scheduling request corresponding to the LCH (scheduling request,
  • the cell group configuration parameters of the MAC layer can include discontinuous reception (DRX) configuration, SR, Buffer Status Report (BSR), power headroom report (PHR) configuration parameters, and trigger release RRC connection timer, timing adjustment group identification and timing adjustment timer; physical cell group configuration parameters may include the identification of the terminal used for power control or scheduling resources (x-RNTI), configuration information for controlling downlink feedback, and low frequency band FR1 One or more of the maximum transmit power.
  • DRX discontinuous reception
  • BSR Buffer Status Report
  • PHR power headroom report
  • RRC connection timer timing adjustment group identification and timing adjustment timer
  • physical cell group configuration parameters may include the identification of the terminal used for power control or scheduling resources (x-RNTI), configuration information for controlling downlink feedback, and low frequency band FR1 One or more of the maximum transmit power.
  • Spcell configuration parameters can include CellIndex, cell group identification, radio link failure detection configuration, radio link monitoring detection configuration, measurement configuration information, physical downlink control channel (PDCCH), physical downlink shared channel (physical downlink control channel, PDCCH) downlink shared channel, PDSCH), PUSCH configuration parameters, uplink (UL) and downlink bandwidth part (downlink bandwidth part) DL BWP configuration, initial DL BWP configuration, initial activation BWP ID and management activation BWP One or more of the timers.
  • the configuration parameters of the Scell are only available when carrier aggregation (CA) or dual connectivity (DC) is configured, and the configuration parameters of the Scell are a subset of the Spcell configuration information.
  • CA carrier aggregation
  • DC dual connectivity
  • terminal also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • UE user equipment
  • UE mobile station
  • MT mobile terminal
  • UE user equipment
  • MID mobile internet devices
  • VR virtual reality
  • augmented reality, AR wireless terminals in industrial control
  • wireless terminals in self-driving wireless terminals in remote medical surgery
  • smart grids The wireless terminal in the transportation safety (transportation safety), the wireless terminal in the smart city (smart city), or the wireless terminal in the smart home (smart home), etc.
  • a network device is a device in a wireless network, such as a radio access network (RAN) node that connects a terminal to the wireless network.
  • RAN nodes are: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B) B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit) , BBU), or wireless fidelity (Wifi) access point (AP), etc.
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • a device means to one or more such devices.
  • at least one (at least one of)" means one or any combination of subsequent associated objects, for example, "at least one of A, B and C” includes A, B, C, AB, AC, BC, or ABC. Determining Y based on X does not mean that Y is determined only based on X, but Y can also be determined based on X and other information.
  • the network architecture includes CN equipment and RAN equipment.
  • the RAN equipment includes a baseband device and a radio frequency device.
  • the baseband device can be implemented by one node or by multiple nodes.
  • the radio frequency device can be implemented remotely from the baseband device, or integrated into the baseband device, or partly remotely.
  • the RAN equipment eNB
  • the RAN equipment includes a baseband device and a radio frequency device.
  • the radio frequency device can be arranged remotely relative to the baseband device, such as a remote radio unit (radio unit).
  • RRU is arranged remotely relative to the BBU.
  • the control plane protocol layer structure can include the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media interface. Access control (media access control, MAC) layer and physical layer and other protocol layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • the user plane protocol layer structure can include the functions of the PDCP layer, the RLC layer, the MAC layer, and the physical layer; in one implementation, the PDCP layer can also include the service data adaptation protocol (SDAP) Floor.
  • SDAP service data adaptation protocol
  • the RAN device can include a centralized unit (CU) and a distributed unit (DU), Multiple DUs can be centrally controlled by one CU.
  • CU and DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and the above protocol layers are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and MAC layer, are set in the DU.
  • This type of protocol layer division is just an example, it can also be divided in other protocol layers, for example, in the RLC layer, the functions of the RLC layer and above protocol layers are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, in a certain protocol layer, for example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. In addition, it can also be divided in other ways, for example, by time delay. The functions that need to meet the delay requirement for processing time are set in the DU, and the functions that do not need to meet the delay requirement are set in the CU.
  • the radio frequency device can be remote, not placed in the DU, can also be integrated in the DU, or part of the remote part is integrated in the DU, and there is no restriction here.
  • FIG. 3 is a schematic diagram of another network architecture provided by an embodiment of the application.
  • the control plane (CP) and the user plane (UP) of the CU can also be separated. It is implemented by dividing it into different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity).
  • the signaling generated by the CU can be sent to the terminal through the DU, or the signaling generated by the terminal can be sent to the CU through the DU.
  • the DU may directly pass the protocol layer encapsulation and transparently transmit to the terminal or CU without analyzing the signaling. If the following embodiments involve the transmission of such signaling between the DU and the terminal, at this time, the sending or receiving of the signaling by the DU includes this scenario.
  • RRC or PDCP layer signaling will eventually be processed as PHY layer signaling and sent to the terminal, or converted from received PHY layer signaling. Under this architecture, the RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and radio frequency.
  • the CU is divided into network equipment on the RAN side.
  • the CU can also be divided into network equipment on the CN side, which is not limited here.
  • the devices in the following embodiments of the present application may be located in a terminal or a network device according to their realized functions.
  • the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.
  • the network device when the network device instructs the terminal to enter the inactive state from the connected state, and the inactive terminal is reasonably instructed to configure parameters through the first information, it can be divided into two different scenarios.
  • the network device may indicate the configuration parameters configured for the terminal in the inactive state through the first information, so that the terminal in the inactive state retains the configuration parameters configured for it.
  • the network device may indicate the configuration parameters that need to be released by the terminal in the inactive state through the first information, so that the terminal in the inactive state releases the configuration parameters that need to be released.
  • the target configuration parameters indicated by the first information are different. In the following, the technical solutions corresponding to these two different scenarios will be described in detail in conjunction with detailed embodiments.
  • the network device 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, it can indicate the configuration parameters that need to be retained to the terminal in two different ways .
  • the network device can indicate the target configuration parameters that need to be retained to the terminal by means of direct instructions, that is, the target configuration parameters indicated by the first information are the configuration parameters that need to be retained by the terminal, so that the terminal receives the first After the information is provided, the configuration parameters that need to be retained are determined directly according to the target configuration parameters indicated by the first information, and the target configuration parameters are retained.
  • the network device may indicate the configuration parameters that need to be retained to the terminal through an indirect indication, that is, the target configuration parameter indicated by the first information is not a configuration parameter that the terminal needs to retain, so that the terminal will receive the first information , Determine parameters other than the target configuration parameter according to the target configuration parameter indicated by the first information, and the parameter other than the target parameter is the configuration parameter that the terminal needs to retain.
  • the definitions of the target configuration parameters indicated by the first information are different.
  • the target configuration parameter indicated by the first information is a configuration parameter that needs to be reserved by the terminal; in the second way, the target configuration parameter indicated by the first information is not a configuration parameter that needs to be reserved by the terminal, except for the target configuration parameter.
  • the parameters other than the configuration parameters are the configuration parameters that the terminal needs to retain. Therefore, in these two different ways, the target configuration parameters of the first indication information are different.
  • the first indication mode is mainly used as an example for description, that is, the target configuration parameter indicated by the first information is the configuration parameter that the terminal needs to retain.
  • the network device indicates the target configuration parameter that the terminal needs to retain through the first information, it can indicate the target configuration parameter that the terminal needs to retain in two possible ways.
  • the first information is the identification of the target configuration parameter, that is, the network device indicates the identification of the target configuration parameter to the terminal, so that the terminal can determine the target configuration parameter that needs to be retained according to the identification of the target configuration parameter;
  • 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 that needs to be retained.
  • the first information is the target configuration parameter identification as an example.
  • FIG. 4 is a schematic flowchart of a configuration method provided by an embodiment of the application.
  • the configuration method may include:
  • the network device sends a radio resource control (RRC) connection release message to the terminal.
  • RRC radio resource control
  • the RRC connection release message includes the first information, and the first information is the identifier of the target configuration parameter.
  • the target configuration parameters may include radio bearer configuration parameters, and/or cell group configuration parameters.
  • the network device may solidify the radio bearer configuration parameters of at least two terminals, and/or the cell group configuration parameters, so that at least two terminals correspond to the same Set configuration parameters, thereby reducing the storage overhead of network equipment.
  • multiple configuration parameter sets can be obtained, and then one or more suitable configuration parameter sets are allocated to the terminal among the multiple configuration parameter sets.
  • the configuration parameters may be referred to as access stratum configuration parameters, and the access stratum configuration parameters may include radio bearer configuration parameters or cell group configuration parameters, or include both radio bearer configuration parameters and cell group configuration parameters.
  • the access layer configuration parameters can be obtained, namely: set 1, set 2, set 3, ..., and set N.
  • the corresponding access stratum configuration parameter set can be assigned to the terminal according to the mode corresponding to the DRB of the data radio bearer of the terminal.
  • the parameters in set 1 can be indicated to the terminal as the target configuration parameters.
  • the set 1 can include SDAP parameters, PDCP parameters, RLC parameters, and MAC layer cell group configuration parameters One or more of.
  • the set 1 may also include DRB ID.
  • the SDAP parameters can include the presence or absence of the uplink/downlink SDAP header, whether it is one or more of the default DRB and QFI.
  • the SDAP parameters can also be Session ID;
  • PDCP parameters can include discardTimer, uplink and downlink PDSP SN One or more of size, header compression configuration, full protection enabled, PDCP status report carried by AM, out-of-sequence sending, and reordering timer.
  • RLC parameters can include RB identification, LCH identification, RLC configuration information, RLC PDU SN length, segment reassembly timer, AM RLC maximum retransmission times, control AM mode to send poll request parameters to the receiving end, and AM RLC One or more of the prohibition timers for sending the RLC status report.
  • the cell group configuration parameters of the MAC layer include one or more of the allowable sub-carrier spacing of one LCH ID, PUSCH TB duration, transmission rate, and logical channel priority. If the session ID is not included in the set 1, the network device may further indicate which session ID of the terminal is associated with the parameters in the set 1. Similarly, if the RB ID is not included in the set 1, the network device may further indicate which RB ID of the terminal is associated with the parameter in the set 1.
  • the parameters in set 2 may be indicated to the terminal as target configuration parameters, and the set 2 may include one or more of PDCP parameters and RLC parameters .
  • 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 one or more of discardTimer, uplink and downlink PDSP SN size, header compression configuration, complete protection on, out-of-order sending, and reordering timers.
  • RLC parameters may include RB identification, LCH identification, RLC configuration information: one or more of the SN length of the RLC PDU and the segment reassembly timer.
  • the SDAP parameters can include the presence or absence of the uplink/downlink SDAP header, and whether it is one or more of the default DRB and QFI.
  • the SDAP parameters can also be Session ID.
  • the cell group configuration parameters of the MAC layer include one or more of the allowable sub-carrier spacing of one LCH ID, PUSCH TB duration, transmission rate, and logical channel priority. If the session ID is not included in the set 2, the network device may further indicate which session ID of the terminal is associated with the parameter in the set 2. Similarly, if the RB ID is not included in the set 2, the network device may further indicate which RB ID of the terminal is associated with the parameter in the set 2.
  • set 3 can be defined as a set formed by set 1 and the configuration parameters of Spcell
  • set 4 can be defined as a set formed by configuration parameters of set 2 and Spcell
  • set 5 can be defined as a set formed by configuration parameters of set 3
  • Set 6 can be defined as a set formed by the configuration parameters of set 4 and Scell.
  • the embodiment of this application only uses set 1, set 2, set 3, set 4, set 5, and set 6 as examples for illustration , But it does not mean that the embodiments of the present application are limited to this.
  • the above-mentioned network device indicates to the terminal a configuration parameter set suitable for the terminal, essentially indicating the configuration parameter in the configuration parameter set to the terminal, that is, assigning the configuration parameter in the configuration parameter set to the terminal as the target configuration parameter.
  • the target configuration parameter identifier may be carried as the first information in the RRC connection release message and sent to the terminal, so that the terminal performs the following S402 according to the RRC release message:
  • S402 The terminal enters the inactive state according to the RRC connection release message, and determines, according to the identifier corresponding to the target configuration parameter, and the mapping relationship, that the context parameter of the inactive state includes the target configuration parameter corresponding to the identifier.
  • the identification of the target configuration parameter may be a set identification of a configuration parameter set, such as the identification of set 1, or the identification of set 2, and so on.
  • the terminal After receiving the RRC connection release message sent by the network device, the terminal enters the inactive state according to the RRC connection release message.
  • the terminal since the terminal pre-stores the identifier corresponding to the configuration parameter and the mapping relationship between the configuration parameters, after receiving the first information sent by the network device as the identifier corresponding to the target configuration parameter, the terminal can use the identifier corresponding to the target configuration parameter in the mapping relationship Find the identifier corresponding to the target configuration parameter in the target configuration parameter, and determine the configuration parameter corresponding to the identifier corresponding to the target configuration parameter as the target configuration parameter that needs to be retained, such as the configuration parameter in set 1 or the configuration parameter in set 2, to obtain the target configuration Parameters, so as to retain the configuration parameters in the set 1 or the configuration parameters in the set 2, and configure according to the target configuration parameters.
  • the terminal retains target configuration parameters.
  • the network device performs curing processing on the radio bearer configuration parameters of multiple terminals and/or the cell group configuration parameters so that at least two terminals correspond to the same set of configuration parameters, so that when multiple terminals enter the inactive state from the connected state
  • the network device performs curing processing on the radio bearer configuration parameters of multiple terminals and/or the cell group configuration parameters so that at least two terminals correspond to the same set of configuration parameters, so that when multiple 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 the storage overhead of the network device.
  • the terminal after entering the inactive state from the connected state according to the RRC connection release message, it can also release the MAC layer configuration information, RLC layer configuration information, PDCP layer configuration information, SDAP layer configuration information, and Part or all of physical cell group configuration information, Spcell configuration, and Scell configuration information.
  • the network device may first obtain the capability information reported by the terminal, and determine whether the terminal supports data transmission in the inactive state according to the capability information reported by the terminal. For example, when the terminal reports its capability information, it can report its capability information to the network device in at least four possible ways.
  • the terminal supporting data transmission in the inactive state the four possible methods are: the terminal can support data transmission in the inactive state, the terminal supports configuring the context parameters of the terminal through a pre-configured identifier, and the terminal supports inactive Common parameter configuration in the state (in other words, the terminal supports lightweight access layer configuration parameters), and the terminal supports the data transmission session in the direct inactive state.
  • the expression modes are different, the four different modes can all indicate that the terminal supports data transmission in the inactive state.
  • FIG. 4 is described in detail in a possible scenario.
  • the network device indicates the target configuration parameter that the terminal needs to retain through the identifier of the target configuration parameter.
  • the technical solution will be described in detail.
  • the network device uses the target configuration parameter itself to indicate the technical solution of the target configuration parameter that the terminal needs to retain.
  • FIG. 5 is a schematic flowchart of another configuration method provided by an embodiment of the application.
  • the configuration method may include:
  • the network device sends a radio resource control RRC connection release message to the terminal.
  • the RRC connection release message includes the first information, and the first information is the target configuration parameter.
  • the target configuration parameters may include radio bearer configuration parameters, and/or cell group configuration parameters.
  • the network device may solidify the radio bearer configuration parameters of at least two terminals, and/or the cell group configuration parameters, so that at least two terminals correspond to the same Set configuration parameters, thereby reducing the storage overhead of network equipment.
  • multiple configuration parameter sets can be obtained, and then one or more suitable configuration parameter sets are allocated to the terminal in the multiple configuration parameter sets.
  • the method for the network device to obtain multiple configuration parameter sets in advance, and the method for indicating the appropriate one or more configuration parameter sets for the terminal are respectively the same as the method for the network device to obtain in advance in S401.
  • the method for multiple configuration parameter sets is similar to the method for indicating one or more suitable configuration parameter sets for the terminal.
  • S401 the related description of this embodiment of the present application will not be repeated.
  • the difference from the technical solution in the embodiment shown in FIG. 4 is that when the network device indicates the target configuration parameter that the terminal needs to retain, it directly sets the configuration parameter
  • the target configuration parameter in the set itself is used as the first information, which is carried in the RRC connection release message and sent to the terminal, so that the terminal performs the following S502 according to the RRC release message:
  • S502 Enter the inactive state according to the RRC connection release message, and determine the target configuration parameter according to the first information.
  • the terminal After the terminal receives the RRC connection release message sent by the network device, the difference from S403 above is that in this possible implementation, the terminal does not need to pre-store the identifier corresponding to the configuration parameter and the mapping relationship between the configuration parameter, and it does not need to be based on The identification and mapping relationship corresponding to the target configuration parameter determines the target configuration parameter, but directly enters the inactive state according to the RRC connection release message, and since the RRC connection release message directly carries the target configuration parameter, the terminal can directly acquire and retain it The target configuration parameter.
  • the target configuration parameter is carried in the RRC connection release message and sent to the terminal, the configuration signaling overhead is relatively large, but for the terminal, the terminal does not need to pre-store the pre-configuration, which reduces the storage overhead configuration overhead of the terminal.
  • the terminal retains target configuration parameters.
  • the network device performs curing processing on the radio bearer configuration parameters of multiple terminals, and/or the cell group configuration parameters, so that at least two terminals correspond to the same set of configuration parameters.
  • the terminal enters the inactive state from the connected state, for the network device, when storing the configuration information of the at least two terminals, only one set of configuration information needs to be stored, thereby reducing the storage overhead of the network device.
  • the terminal after entering the inactive state from the connected state according to the RRC connection release message, it can also release the MAC layer configuration information, RLC layer configuration information, PDCP layer configuration information, SDAP layer configuration information, and Part or all of physical cell group configuration information, Spcell configuration, and Scell configuration information.
  • the network device Before sending the RRC connection release message to the terminal, the network device may first obtain the capability information reported by the terminal, and determine whether the terminal supports data transmission in the inactive state according to the capability information reported by the terminal. For example, when the terminal reports its capability information, the reporting manner is the same as that of the terminal reporting in the embodiment shown in FIG.
  • the network device when describing that the network device indicates the configuration parameters that need to be retained to the terminal through the first information, only the target configuration parameter indicated by the first information is the terminal
  • the configuration parameters that need to be retained are described as an example.
  • the target configuration parameter indicated by the first information may not be a configuration parameter that needs to be retained by the terminal.
  • the terminal may determine the target configuration parameter in addition to the target configuration parameter according to the target configuration parameter indicated by the first information.
  • the parameters other than the target parameter are the configuration parameters that the terminal needs to retain, so that the parameters other than the target parameter are retained. It is worth noting that in the two different indication modes, the target configuration parameters indicated by the first information are different.
  • the embodiments of the present application will not be repeated.
  • the network device can indicate the configuration parameters configured for the terminal in the inactive state through the first information, so that the terminal in the inactive state remains as The technical solution for configuring configuration parameters will be described in detail below.
  • the network device can indicate the configuration parameters that the inactive terminal needs to release through the first information, so that the inactive terminal The technical solution for releasing the configuration parameters that need to be released.
  • the network device when the network device indicates the configuration parameter that needs to be released by the terminal through the first information, so that the terminal releases the configuration parameter that needs to be released, it can also indicate to the terminal that the configuration parameter needs to be released in two different ways.
  • Configuration parameters In one manner, the network device may indicate the configuration parameters that need to be released to the terminal by means of direct instructions, that is, the target configuration parameter indicated by the first information is the configuration parameter that needs to be released by the terminal, so that the terminal receives the first information Then, directly determine the configuration parameter that needs to be released according to the target configuration parameter indicated by the first information, and release the target configuration parameter.
  • the network device may indicate the configuration parameters that need to be released to the terminal through an indirect indication, that is, the target configuration parameter indicated by the first information is not the configuration parameter that needs to be released by the terminal, so that the terminal after receiving the first information , Determine parameters other than the target configuration parameter according to the target configuration parameter indicated by the first information, and the parameter other than the target parameter is the configuration parameter that needs to be released by the terminal. It can also be seen that in the two different ways, the definitions of the target configuration parameters indicated by the first information are different.
  • the target configuration parameter indicated by the first information is the configuration parameter that needs to be released by the terminal; in the second method, the target configuration parameter indicated by the first information is not the configuration parameter that needs to be released by the terminal, except for the target configuration parameter.
  • the parameters other than the configuration parameters are the configuration parameters that the terminal needs to release. Therefore, in these two different ways, the target configuration parameters of the first indication information are different.
  • the first indication mode is mainly used as an example for description, that is, the target configuration parameter indicated by the first information is the configuration parameter that the terminal needs to release.
  • the network device indicates the target configuration parameter that needs to be released by the terminal through the first information, it can indicate the target configuration parameter that needs to be released by the terminal in two possible ways.
  • the first information is the identification of the target configuration parameter, that is, the network device indicates the identification of the target configuration parameter to the terminal, so that the terminal can determine the target configuration parameter that needs to be released according to the identification of the target configuration parameter;
  • 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 that needs to be released.
  • FIG. 6 is a context parameter for releasing the terminal provided by an embodiment of this application, except for the target configuration parameter. Schematic diagram of the flow of the parameters, the method may include:
  • the network device sends a radio resource control (RRC) connection release message to the terminal.
  • RRC radio resource control
  • the RRC connection release message includes the first information, and the first information is the identifier of the target configuration parameter.
  • the target configuration parameters may include radio bearer configuration parameters, and/or cell group configuration parameters.
  • the network device has pre-configured multiple sets of configuration parameters for the terminal.
  • the network device Before configuring multiple sets of configuration parameters for the terminal in advance, similarly, in order to reduce the storage overhead of the network device, the network device can configure at least two sets of configuration parameters.
  • the radio bearer configuration parameters of each terminal and/or the cell group configuration parameters are solidified, so that at least two terminals correspond to the same set of configuration parameters, thereby reducing the storage overhead of the network device.
  • multiple configuration parameter sets can be obtained, and then the configuration parameters in the multiple configuration parameter sets are configured to the terminal.
  • the method for the network device to obtain multiple configuration parameter sets in advance, and the method for allocating multiple configuration parameter sets to the terminal are respectively the same as the network device in the above S401 to obtain multiple configuration parameters in advance.
  • the method of aggregation is similar to the method of allocating multiple sets of configuration parameters to the terminal, and reference may be made to the relevant description in S401 above.
  • the description of the embodiment of the present application will not be repeated.
  • the target configuration parameter identifier can be carried as the first information in the RRC connection release message and sent to the terminal, so that the terminal executes the download according to the RRC release message.
  • S602 The terminal enters the inactive state according to the RRC connection release message, and determines, according to the identifier corresponding to the target configuration parameter, and the mapping relationship, that the context parameter of the inactive state includes the target configuration parameter corresponding to the identifier.
  • the identification of the target configuration parameter may be a set identification of a configuration parameter set, such as the identification of set 1, or the identification of set 2, and so on.
  • the terminal After receiving the RRC connection release message sent by the network device, the terminal enters the inactive state according to the RRC connection release message.
  • the terminal since the terminal pre-stores the identifier corresponding to the configuration parameter and the mapping relationship between the configuration parameters, after receiving the first information sent by the network device as the identifier corresponding to the target configuration parameter, the terminal can use the identifier corresponding to the target configuration parameter in the mapping relationship Find the identifier corresponding to the target configuration parameter in the file, and determine the configuration parameter corresponding to the identifier corresponding to the target configuration parameter as the target configuration parameter that needs to be released. For example, the configuration parameter in set 1 or the configuration parameter in set 2 is determined to be released. The target configuration parameter is used to obtain the target configuration parameter, so as to release the configuration parameter in the set 1 or the configuration parameter in the set 2.
  • S603 The terminal releases the target configuration parameter in the context parameters in the inactive state.
  • the terminal After the terminal receives the RRC connection release message sent by the network device, and determines the target configuration parameter that needs to be released included in the context parameter of the terminal according to the first information it carries, it can directly release the target configuration parameter, thereby realizing the reduction Under the premise of the storage overhead of the network equipment and the terminal, the network equipment can control which configuration parameters continue to be used and which configuration parameters are no longer used.
  • the terminal after entering the inactive state from the connected state according to the RRC connection release message, other access layer parameters can be released.
  • the other access layer parameters include physical cell configuration information, Spcell configuration information, and Scell At least one of configuration information.
  • the terminal releases other access layer parameters one way is: after receiving the RRC connection release message, the terminal releases other access layer parameters by default, that is, in this way, the RRC message does not need to carry the release Instructions.
  • the RRC connection release message may explicitly carry indication information for releasing other configurations, so that the terminal releases other access layer parameters according to the indication information for releasing other configurations.
  • the network device when the first information is the identification of the target configuration parameter, the network device indicates the target configuration parameter that needs to be released by the terminal through the identification of the target configuration parameter
  • the first information can also be the target configuration parameter itself, that is, the network device can take the target configuration parameter itself that needs to be released as the first information, carry it in the RRC connection release message and send it to the terminal, so that the terminal can directly follow the first
  • the information can determine the target configuration parameter that needs to be released.
  • the terminal does not need to pre-store the identification corresponding to the configuration parameter and the mapping relationship between the configuration parameter, and there is no need for the identification corresponding to the target configuration parameter.
  • mapping relationship determines the target configuration parameter, but directly enters the inactive state according to the RRC connection release message, and since the RRC connection release message directly carries the target configuration parameter, the terminal can directly acquire and release the target configuration parameter.
  • the target configuration parameter is carried in the RRC connection release message and sent to the terminal, the configuration signaling overhead is relatively large, but for the terminal, the terminal does not need to pre-store the pre-configuration, which reduces the storage overhead configuration overhead of the terminal.
  • the network device when describing that the network device indicates the configuration parameters that need to be released to the terminal through the first information, only the target configuration parameters indicated by the first information are those that the terminal needs to release.
  • the configuration parameters are described as an example.
  • the target configuration parameter indicated by the first information may not be a configuration parameter that the terminal needs to release.
  • the terminal may determine which target configuration parameter is excluded from the target configuration parameter according to the target configuration parameter indicated by the first information.
  • the parameters other than the target parameter are the configuration parameters that the terminal needs to release, so that the parameters other than the target parameter are released. It is worth noting that in the two different indication modes, the target configuration parameters indicated by the first information are different.
  • the embodiments of the present application will not be repeated.
  • the network device uses the target configuration parameter indicated by the first information to indicate the configuration parameter that the terminal needs to retain or the configuration parameter that the terminal needs to release, it will pass the first Before an information indicates, the radio bearer configuration parameters of multiple terminals and/or the cell group configuration parameters will be solidified to obtain one or more configuration parameter sets; only then can the first information be used to instruct the terminal to retain A configuration parameter in a certain configuration parameter set, or a configuration parameter in a certain configuration parameter set that instructs the terminal to release.
  • the network device may first negotiate with other network devices, such as the first network device, before sending the RRC connection request message indicating the target configuration parameter to the terminal.
  • the set of configuration parameters For an example, please refer to FIG. 7.
  • FIG. 7 is a schematic diagram of a process for negotiating and determining each configuration parameter set according to an embodiment of the application.
  • the method for determining each configuration parameter set may include:
  • the network device sends a first request message to the first network device.
  • the first request message includes an initial configuration parameter set
  • the initial configuration parameter set includes initial radio bearer configuration parameters and/or initial cell group configuration parameters determined by the network device
  • the first request message is used to request the first network device to confirm The initial radio bearer configuration parameter and/or the initial cell group configuration parameter in the initial configuration parameter set.
  • a possible situation is: if the first network device supports the initial radio bearer configuration parameters and/or Or initial cell group configuration parameters, then confirm and store the initial radio bearer configuration parameters and/or initial cell group configuration parameters.
  • the response message sent to the network device still includes the initial radio bearer configuration parameters and/or initial cell Group configuration parameters; another possible situation is: if the first network device does not support the initial radio bearer configuration parameters and/or the initial cell group configuration parameters, the initial radio bearer configuration parameters and/or the initial cell group configuration parameters need to be modified , The initial radio bearer configuration parameters and/or the initial cell group configuration parameters are directly modified and the modified radio bearer configuration parameters and/or the modified cell group configuration parameters are stored. At this time, the first network device sends the network device The sent response message includes the modified radio bearer configuration parameters and/or the modified cell group configuration parameters.
  • the network device when the network device negotiates with the first network device to determine each configuration parameter set, it can send all the configuration parameter sets to the first network device through the first request message; of course, it can also pass the all configuration parameter sets through The multiple first request messages are sent to the first network device, which can be specifically set according to actual needs.
  • the embodiment of the present application does not make further restrictions.
  • the first network device sends a first response message to the network device.
  • the first response message includes initial radio bearer configuration parameters and/or initial cell group configuration parameters, or modified radio bearer configuration parameters and modified cell group configuration parameters by the first network device.
  • the network device may determine the configuration parameter set according to the first response message, that is, perform the following S703:
  • the network device determines a configuration parameter set according to the first response message.
  • the first response message includes the initial radio bearer configuration parameters and/or the initial cell group configuration parameters, it means that the first network device supports the initial radio bearer configuration parameters and/or the initial cell group configuration parameters determined by the network device.
  • the initial radio bearer configuration parameter and/or the initial cell group configuration parameter is determined to be the configuration parameter that can be used subsequently, and the set including the configuration parameter is the configuration parameter set for subsequent use.
  • the first response message includes the modified radio bearer configuration parameters and/or the modified cell group configuration parameters, it means that the first network device does not support the initial radio bearer configuration parameters and/or the initial cell group determined by the network device Configuration parameters, the modified radio bearer configuration parameters and/or the modified cell group configuration parameters are determined as configuration parameters that can be used subsequently, and the set including the configuration parameters is the configuration parameter set for subsequent use.
  • the network The device can then indicate the configuration parameters in a certain configuration parameter set that the terminal needs to retain through the first information, or instruct the configuration parameters in a certain configuration parameter set that the terminal needs to release, and in the instruction process, avoiding the inconsistency of various configuration parameters The defects brought by.
  • the network device can perform solidification processing on the radio bearer configuration parameters of at least two terminals, and/or the cell group configuration parameters.
  • a plurality of configuration parameter sets are obtained, and then, a technical solution of one or more suitable configuration parameter sets is indicated for the terminal in the plurality of configuration parameter sets.
  • the network device may first receive the 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 parameters for the terminal. set.
  • FIG. 8 is a schematic diagram of a process for allocating a suitable configuration parameter set to a terminal according to an embodiment of the application. The method may include:
  • S801 The terminal sends a registration request to the core network device.
  • the registration request may optionally include the capability information of the terminal.
  • the capability information of the terminal may be that the terminal supports a direct data transmission (DDT) session, that is, the terminal supports direct data transmission in an inactive state.
  • DDT direct data transmission
  • the terminal capability information is the same as the terminal capability information in the embodiment shown in FIG. 4.
  • the terminal capability information is the same as the terminal capability information in the embodiment shown in FIG. 4.
  • the terminal sends a protocol data unit (protocol data unit, PDU) session establishment request to the core network device.
  • PDU protocol data unit
  • the PDU session establishment request may optionally indicate that the session type is a DDT session, that is, the DDT session can be used for the terminal to directly perform data transmission in an inactive state. In this way, direct data transmission in the inactive state of the session granularity can be realized.
  • the core network device may optionally determine to establish a DDT session for the terminal according to the subscription data and/or capability information of the terminal.
  • the core network device can search for the terminal's subscription data through the session management function (SMF) device, and determine whether to establish a DDT for the terminal according to the terminal's subscription data
  • SMF session management function
  • For a session for example, when an operator signs a contract with a user of a terminal to provide the DDT function for him, it is determined to establish a DDT session for the terminal.
  • SMF session management function
  • the core network device determines to establish a DDT session for the terminal, it sends a PDU session establishment request to the network device, that is, executes the following S804:
  • the core network device sends a PDU session establishment request to the network device.
  • the PDU session establishment request may include a session type, and the session type is used to instruct the terminal to allow uplink transmission when it is in an inactive state.
  • the session type can be a boolean parameter, with a value of 1, which means that data transmission can be performed in the inactive state; a value of 0, which means that data transmission cannot be performed in the inactive state, or vice versa; or,
  • the session type is an enumerated parameter.
  • the value is True, which means that data can be transmitted in the inactive state; the value is False, which means that data cannot be transmitted in the inactive state; or, the value is a DDT session, which means that data can be transmitted in the inactive state.
  • Data transmission is performed in the inactive state; the value is other, which means that data transmission cannot be performed in the inactive state.
  • This session type can also be called indication information.
  • the session type used to indicate that the terminal is allowed to perform uplink transmission when in the inactive state is carried in the PDU session establishment request and sent to the network device, of course, in addition to being carried in the PDU session establishment request and sent to the network device
  • the session type can also be carried in the PDU session modification request and sent to the network device.
  • the embodiment of the present application only takes the session type carried in the PDU session establishment request and sent to the network device as an example for description, but it does not mean that the embodiment of the present application is limited to this.
  • the above PDU session establishment request may also include a session identifier to identify the session; since a session may include multiple streams, the core network device indicates whether a session can allow uplink transmission in the inactive state, or The indication is performed in a flow unit, that is, whether a flow identifier can be allowed to perform uplink transmission in the inactive state.
  • the core network device sends a PDU session establishment request to the network device, it only needs to add the flow identifier in the session to the PDU session establishment request, so that the flow identifier can indicate whether the uplink can be allowed in the inactive state. transmission.
  • the above session types can also be referred to as stream types, or collectively referred to as indication information.
  • the network device allocates target configuration parameters to the terminal.
  • S806 The network device sends the first information to the terminal.
  • the first information is used to indicate the target configuration parameter.
  • 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.
  • the core network device can determine whether to establish a DDT session for the terminal according to the subscription data and/or capability information of the terminal, and when it is determined to establish the DDT session for the terminal, instruct the network device through the session identifier or the flow identifier Establish a certain session or a certain flow in the session ID for the terminal.
  • the indication information (session type or flow type) is used to indicate that the terminal can perform data transmission in the inactive state.
  • the network device can act as the terminal according to the indication information. Assign target configuration parameters.
  • the network device can also solidify the radio bearer configuration parameters of multiple terminals, and/or the cell group configuration parameters, so that at least two terminals correspond to the same set of configurations In this way, when multiple terminals enter the inactive state from the connected state, for the network device, when storing the configuration information of the at least two terminals, only one set of configuration information needs to be stored, thereby reducing the network device’s Storage overhead.
  • the embodiment shown in Figure 8 can be implemented in combination with the embodiment shown in Figure 4 or Figure 5.
  • the embodiment shown in Figure 8 can also be implemented independently, that is, the embodiment shown in Figure 8 and the embodiment shown in Figure 4 Or the embodiment shown in FIG. 5 is decoupled and does not have a binding relationship.
  • the terminal after receiving the RRC connection release message sent by the network device, the terminal enters the inactive state according to the RRC connection release message.
  • the terminal When the terminal is in the inactive state, if the terminal receives the first instruction sent by the network device to instruct the terminal to monitor the physical downlink control channel in the inactive state, the terminal monitors the physical downlink control channel in the inactive state.
  • the first indication may be included in the RRC release message, of course, it may also be carried in other messages, which can be specifically set according to actual needs.
  • the terminal may also receive a second indication for indicating that the terminal is allowed to perform uplink transmission when in the inactive state.
  • the terminal may send a random access request to the network device and receive a response message for the random access request.
  • the response message includes an uplink authorization and a second indication.
  • the uplink authorization indication can be Uplink DRB data transmission is performed on the uplink resources, which realizes that the terminal completes the uplink DRB data transmission when the terminal is in the inactive state, and does not need to wait until the RRC connection is restored to perform the uplink transmission. There is no need for the terminal to enter the connected state to send data, which not only improves the efficiency of data transmission , And reduces the overhead required for RRC connection recovery.
  • the terminal after receiving the RRC connection release message sent by the network device, the terminal can enter the inactive state according to the RRC connection release message. After entering the inactive state, if uplink transmission is to be performed, the terminal can send the preamble and uplink data in the uplink resource indicated by the network device during the random access process. If the network device fails to parse the uplink data, the terminal will be In other words, if you want to send uplink data to the network device again, you need to restore the RRC connection first, and re-send the uplink data to the network device when it is in the connected state, so that the network device can accurately receive the uplink data sent by the terminal.
  • the uplink data is PUSCH data.
  • the uplink data includes RRC signaling and/or uplink DRB data.
  • RRC signaling and/or uplink DRB data.
  • FIG. 9 is a schematic flowchart of a configuration method provided by an embodiment of the application, and the configuration method may include:
  • S901 The terminal obtains the instruction information and the uplink resource sent by the network device.
  • the indication information is used to instruct the terminal to enable uplink transmission in the inactive state. Wherein, the indication information is optional.
  • the terminal when the terminal obtains the indication information, it can obtain the indication information through the RRC connection release message, or it can obtain the indication information through the broadcast message, which can be set according to actual needs.
  • the terminal when the terminal obtains the indication information, it can obtain the indication information through the RRC connection release message, or it can obtain the indication information through the broadcast message, which can be set according to actual needs.
  • the application examples do not make further restrictions.
  • the terminal when it obtains the uplink resource, it can obtain the uplink resource in three possible ways.
  • the terminal may send a preamble to the network device, and receive a random access response message sent by the network device, and the random access response may include the uplink resource, so as to obtain the uplink resource.
  • the terminal can 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 to obtain To the uplink resource.
  • MsgA message A
  • RACH random access channel
  • the uplink resources in the two-step RACH can be obtained through an RRC connection release message or a broadcast message.
  • the terminal may directly use the uplink resource in the pre-configured PUSCH resource without sending the preamble, and use the uplink resource as the uplink resource to be used, so as to obtain the uplink resource.
  • the pre-configured PUSCH resource can be obtained through an RRC connection release message or a broadcast message.
  • the terminal When performing uplink transmission, the terminal obtains a comparison result between the amount of uplink data to be transmitted and the data amount threshold.
  • the comparison result indicates that the amount of uplink data to be transmitted is greater than the data amount threshold, the following S903-S904 are executed; if the comparison result indicates that the amount of uplink data to be transmitted is less than the data amount threshold, the following S905 is executed; if the comparison result indicates that the amount of data is to be transmitted If the amount of upstream data is equal to the data amount threshold, the following S903-S904 or the following S905 are executed.
  • S902 is optional.
  • the UE can arbitrarily choose to use the following S903-S904 or the following S905.
  • the terminal sends an RRC connection recovery request to the network device without sending uplink data.
  • the terminal uses the uplink resource in the contention resolution response to transmit uplink data.
  • the RRC connection recovery request may carry an indication, which is used to indicate the magnitude relationship between the amount of uplink data to be transmitted and the data amount threshold.
  • the indication can be represented by a boolean parameter (or boolean value).
  • boolean value when the boolean value is 1, it means 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 to be transmitted is The amount is less than the data amount threshold, and vice versa; when the amount of data to be transmitted is equal to the data amount threshold, the Boolean value can be 0 or 1.
  • the indication can be indicated by whether a field in the RRC connection recovery request exists or not.
  • the field exists in the RRC connection recovery request, it means that the amount of data to be transmitted is less than the data volume threshold; when the RRC connection recovery request does not include the The field indicates that the amount of data to be transmitted is greater than the data amount threshold, and vice versa; when the amount of data to be sent is equal to the data amount threshold, this field may or may not exist in the RRC connection recovery request.
  • the indication may be indicated by an enumerated field in the RRC connection recovery request.
  • the field in the RRC connection recovery request When the field in the RRC connection recovery request is TRUE, it means that the amount of data to be sent is less than the data volume threshold; when the RRC connection recovery request is in When the field is FALSE, it means that the amount of data to be sent is greater than the data amount threshold, and vice versa; when the amount of data to be sent is equal to the data amount threshold, the field in the RRC connection recovery request can be TRUE or FALSE.
  • 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 only take these several methods as examples for description, which can 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.
  • the network device may further execute the following S906-S907.
  • S906 The network device determines whether to allow uplink transmission on the uplink resource indicated by the uplink authorization.
  • S907 The network device sends to the terminal indication information used to indicate whether to allow uplink transmission on the uplink resource indicated by the uplink authorization.
  • the uplink resource is used for uplink transmission; if the indication information indicates that uplink transmission is not allowed on the uplink resource indicated by the uplink authorization , When the terminal needs to perform uplink transmission, the terminal can perform the above S903-S904.
  • the terminal sends an RRC connection recovery request to the network device, so that the network device can allocate the uplink authorization to the terminal when the terminal is in the inactive state, and indicate whether to allow the terminal through the indication information.
  • Uplink transmission is performed on the uplink resources indicated by the uplink authorization, which realizes that the terminal completes the uplink transmission in the inactive state, and does not need to wait until the RRC connection is restored to perform the uplink transmission.
  • the terminal does not need to enter the connected state to send data, which not only improves the efficiency of data transmission , And reduces the overhead required for RRC connection recovery.
  • the terminal compares the amount of uplink data to be transmitted with the data amount threshold before sending uplink data to the network device, and according to the instructions sent by the network device The information determines whether to allow uplink transmission on the uplink resource indicated by the uplink grant. After comparison, if the amount of uplink data to be transmitted is less than or equal to the data amount threshold, and the terminal determines that the uplink transmission can be performed on the uplink resources indicated by the uplink authorization, the PDCP state of the DRB and SRB is restored, and the PCDP entity is rebuilt, and the SRB is restored And the status of the DRB, and send a first message to the network device.
  • the first message may include the preamble sent on the PRACH resource, and the RRC connection recovery request and uplink data sent on the PUSCH resource.
  • the network device will analyze the received preamble and PUSCH data.
  • the network device successfully parses the preamble but fails to parse the PUSCH data; in another scenario, the network device successfully parses the preamble. , And successfully parse the PUSCH data. In the following, detailed embodiments will be used to describe these two different scenarios in detail.
  • Configuration methods can include:
  • the terminal sends a first message to a network device.
  • the first message includes a random access request and/or physical uplink shared channel data
  • the physical uplink shared channel data includes information for requesting the restoration of a radio resource control (RRC) connection, such as an RRC connection restoration request.
  • RRC radio resource control
  • the random access request may be a preamble
  • the physical uplink shared channel data may also include uplink data.
  • the uplink data is optional.
  • the network device can parse the preamble and uplink data included in the first message.
  • the network device When the network device successfully parses the preamble but fails to parse the uplink data, the network device will send a message according to the analysis result.
  • the terminal sends the response message of the first message, that is, executes the following S1002:
  • the network device sends a response message of the first message to the terminal.
  • the response message includes uplink authorization and first indication information, and the first indication information is used to indicate whether to allow uplink transmission on the uplink resources indicated by the uplink authorization.
  • the response message of the first message may also include a random access preamble identifier (Random Access Preamble Identifier, RAP ID), a timing advance (time advance, TA), and a temporary cell radio network temporary identifier (temporary cell radio network temporary). identity, TC-RNTI).
  • RAP ID is the identifier corresponding to the preamble in S1001. If the RAP ID and the identifier corresponding to the preamble sent by the terminal are the same, the terminal confirms that the response message of the first message is the response message sent by the network device for it.
  • TA represents the advance of the uplink transmission timing, and is used for the terminal to adjust the uplink transmission timing.
  • the TC-RNTI is the identifier assigned by the network equipment to the terminal. When the contention is resolved, the TC-RNTI can be used as a C-RNTI.
  • the network equipment indicates the PUSCH resource through the PDCCH scrambled by the C-RNTI, and the terminal uses the PUSCH resource to send uplink signals. Order or data.
  • the response message of the first message may also include an RRC dedicated signaling message, such as an RRC reconfiguration message.
  • the terminal does not start the timer when it determines that it can perform uplink transmission on the uplink resource indicated by the uplink authorization, the terminal starts the timer after receiving the response message of the first message sent by the network device; otherwise, if the terminal determines The timer may be started when uplink transmission is performed on the uplink resource indicated by the uplink authorization, and the terminal restarts the timer after receiving the response message of the first message sent by the network device.
  • the timer can be a T319 timer or other new timers.
  • the duration of the timer is used to limit the maximum waiting time or the maximum tolerable duration of the RRC connection recovery process.
  • the timer can be the T319 timer
  • the terminal starts T319 when sending a connection recovery request, and stops T319 when it receives a connection recovery or connection establishment or connection release message sent by the network device; or, the terminal reselects the cell or receives
  • the terminal stops T319. Otherwise, when T319 times out, the terminal will release the connection and enter the idle state due to the failure of the RRC connection recovery.
  • the response message of the first message sent by the network device to the terminal not only includes the uplink authorization information, but also further includes the first indication information.
  • the content indicated by the first indication information is different, and correspondingly, the manner in which the terminal performs uplink transmission on the uplink resource indicated by the uplink authorization is also different.
  • the first indication information indicates that the terminal is allowed to perform uplink transmission on the uplink resources indicated by the uplink authorization
  • the following S1003 may be performed; on the contrary, when the first indication information indicates that the terminal is not allowed to perform uplink transmission on the uplink resources indicated by the uplink authorization At this time, the following S1004 can be executed.
  • the uplink transmission indicated by the first indication information refers to the transmission of uplink DRB data.
  • the above first indication information may be explicit indication information, for example, it may be 1-bit indication information.
  • the value is "1"
  • it indicates that the terminal is allowed to perform uplink transmission on the uplink resources indicated by the uplink authorization.
  • the value is "0"
  • it indicates that the terminal is not allowed to perform uplink transmission on the uplink resource indicated by the uplink authorization.
  • the meaning of the value can also be reversed, so I won't repeat it here.
  • the response message may not carry the first indication information, that is, the terminal is instructed by implicit indication.
  • the terminal performs on the uplink resources indicated by the uplink authorization. Uplink transmission of DRB data. Otherwise, the terminal does not perform uplink transmission of DRB data on the uplink resource indicated by the uplink grant.
  • the first indication information may be carried in the response message when the terminal is allowed to perform uplink transmission on the uplink resource indicated by the uplink authorization, and the first indication information may be included in the response message when the terminal is not allowed to perform uplink transmission on the uplink resource indicated by the uplink authorization.
  • the manner of not carrying the first indication information indicates whether the terminal can use the uplink authorization.
  • the terminal sends a second message to the network device on the uplink resource.
  • the second message includes uplink data and RRC connection recovery request.
  • the terminal when the first indication information indicates that the terminal is allowed to perform uplink transmission on the uplink resource indicated by the uplink authorization, the terminal may perform uplink transmission on the uplink resource indicated by the received uplink authorization.
  • the terminal sends a third message to the network device on the uplink resource.
  • the third message is used to request the restoration of the RRC connection.
  • the third message sent by the terminal on the uplink resources indicated by the uplink authorization only uses The request to restore the RRC connection does not include the uplink DRB data.
  • the third message may be an RRC connection recovery request.
  • the network device After receiving the second message or the third message sent by the terminal, the network device will send contention resolution information to the terminal, that is, perform the following S1005:
  • the network device sends contention resolution information to the terminal.
  • the contention resolution information may be the identification of the terminal, or partial information of the second message, or partial information of the third message.
  • the terminal After the terminal receives the contention resolution information, if it has not received the RRC connection release message at this time, the terminal starts or restarts the timer, and receives authorization from the network device during the timer operation; the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink authorization; if the downlink authorization is received from the network device, and it has not been received
  • the terminal starts or restarts the timer and waits for the time of the RRC connection release message, which realizes that the terminal completes uplink transmission when the RRC connection is inactive, and does not need to wait until the RRC connection is restored.
  • Uplink transmission does not require the terminal to enter the connected state to send data, which not only improves the efficiency of data transmission, but also reduces the overhead required for RRC connection recovery.
  • the timer is stopped when certain conditions are met, for example, the scenario of stopping the timer described above.
  • the control timer stops running, that is, the timer is stopped.
  • RRC radio resource control
  • the first message sent by the terminal to the network device includes the preamble, the RRC connection recovery request, and the uplink data.
  • the terminal may also not include the preamble in the first message.
  • Carrying uplink data, but carrying a second indication information the second indication information is used to indicate the comparison result of the terminal's to-be-sent data volume and the data volume threshold.
  • the network device parses the preamble successfully, but When parsing uplink data fails, as an example, please refer to FIG. 11.
  • FIG. 11 is a schematic flowchart of another configuration method provided by an embodiment of the application, and the configuration method may include:
  • 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
  • the physical uplink shared channel data includes information used to request the restoration of a radio resource control (RRC) connection, such as an RRC connection restoration request.
  • RRC radio resource control
  • the random access request may be a preamble
  • the physical uplink shared channel data may further include second indication information, which is used to indicate the comparison result between the amount of data to be sent by the terminal and the data amount threshold.
  • the second indication information is optional.
  • the second indication information can be used through the RRC connection recovery request
  • a Boolean value in indicates that, for example, when the Boolean value is 1, it means that the amount of data to be sent is greater than the data amount threshold; when the Boolean value is 0, it means that the amount of data to be sent is less than the data amount threshold, and vice versa; When the amount of data to be sent is equal to the data amount threshold, the Boolean value can be either 0 or 1.
  • the second indication information may indicate whether a field in the RRC connection recovery request exists or not.
  • the field When the field exists in the RRC connection recovery request, for example, TRUE, it indicates that the amount of data to be sent is less than the data amount threshold; This field does not exist in the connection recovery request. For example, when it is NULL, it means that the amount of data to be sent is greater than the data volume threshold, and vice versa; when the amount of data to be sent is equal to the data volume threshold, this field can be present in the RRC connection recovery request , Or the field does not exist.
  • the second indication information may be indicated by an enumerated field in the RRC connection recovery request.
  • the field in the RRC connection recovery request 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 volume threshold; when the RRC connection is restored When the field in the request is FALSE, it means that the amount of data to be sent is greater than the data amount threshold, and vice versa; when the amount of data to be sent is equal to the data amount threshold, the field in the RRC connection recovery request can be TRUE or FALSE.
  • the MAC message when the first message is a MAC message, the MAC message is, for example, a MAC sub-PDU.
  • the MAC sub-PDU may include only the MAC header, or include the MAC header and MAC CE.
  • FIG. 12 is a schematic diagram of the structure of a MAC message provided by an embodiment of the application.
  • the MAC message only includes a MAC header, and the MAC header includes a logical channel identifier (LCH ID), and the LCH ID takes a preset value, indicating that the MAC header value carries the second indication information.
  • the second indication information can be realized by the indication field in the MAC header, for example, by using the previously reserved bit R.
  • the value of the R bit When the value of the R bit is 1, it means that the amount of data to be sent is greater than the data amount threshold; when the value of the R bit is 0, it means that the amount of data to be sent is less than the data amount threshold, and vice versa; when the amount of data to be sent is equal to When the data volume threshold is used, the value of the R bit can be 0 or 1.
  • FIG. 13 is a schematic structural diagram of another MAC message provided by an embodiment of the application.
  • the MAC message includes a MAC header and a MAC CE, and the field in the MAC CE carries the second indication information.
  • the MAC header includes the LCH ID, and the LCH ID takes a preset value, indicating that the MAC CE carries the second indication information. Take the 1-bit field 1 in the MAC CE that carries the second indication information as an example.
  • this field 1 is 1, indicating that the amount of data to be sent is greater than the data amount threshold; the value of field 1 is 0, indicating that the data is to be sent The amount is less than the data amount threshold, and vice versa; when the amount of data to be sent is equal to the data amount threshold, the value of this field 1 can be 0 or 1.
  • the embodiment of this application only uses the example that the first message can be an RRC connection recovery request message or a MAC message. Actual settings need to be performed, and the embodiments of the present application do not make further restrictions here.
  • the network device can parse the preamble and the physical uplink shared channel data included in the first message.
  • the network device successfully parses the preamble, but parses the physical uplink
  • the network device will send a response message of the first message to the terminal according to the analysis result, that is, perform the following S1102:
  • the network device sends a response message of the first message to the terminal.
  • the response message includes uplink authorization and first indication information, and the first indication information is used to indicate whether to allow uplink transmission on the uplink resources indicated by the uplink authorization.
  • 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.
  • 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.
  • the relevant description in S1002. The application embodiment will not be repeated.
  • the response message of the first message sent by the network device to the terminal not only includes the uplink authorization information, but also further includes the first indication information.
  • the content indicated by the first indication information is different, and correspondingly, the manner in which the terminal performs uplink transmission on the uplink resource indicated by the uplink authorization is also different.
  • the terminal sends a second message to the network device on the uplink resource.
  • the second message includes uplink data and RRC connection recovery request.
  • the terminal when the first indication information indicates that the terminal is allowed to perform uplink transmission on the uplink resource indicated by the uplink authorization, the terminal may perform uplink DRB data transmission on the uplink resource indicated by the received uplink authorization.
  • the terminal sends a third message to the network device on the uplink resource.
  • the third message is used to request the restoration of the RRC connection.
  • the third message sent by the terminal on the uplink resources indicated by the uplink authorization only uses The request to restore the RRC connection does not include uplink data.
  • the third message may be an RRC connection recovery request.
  • the network device After receiving the second message or the third message sent by the terminal, the network device will send contention resolution information to the terminal, that is, perform the following S1105:
  • the network device sends contention resolution information to the terminal.
  • the contention resolution information may be the identification of the terminal, or partial information of the second message, or partial information of the third message.
  • the terminal After the terminal receives the contention resolution information, if it has not received the RRC connection release message at this time, the terminal starts or restarts the timer, and receives authorization from the network device during the timer operation; the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the authorization can be an uplink authorization or a downlink authorization Authorize, and restart the timer when the authorization is received, so as to delay the time the terminal monitors the authorization.
  • the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink authorization; if the downlink authorization is received from the network device, and it has not been received
  • the terminal starts or restarts the timer and waits for the time of the RRC connection release message, which realizes that the terminal completes uplink transmission when the RRC connection is inactive, without having to wait until the RRC connection is restored.
  • Uplink transmission does not require the terminal to enter the connected state to send data, which not only improves the efficiency of data transmission, but also reduces the overhead required for RRC connection recovery.
  • FIG. 14 is a schematic flowchart of another configuration method provided by an embodiment of the application. Methods can include:
  • the terminal sends a first message to a network device.
  • the first message includes a random access request and/or physical uplink shared channel data
  • the physical uplink shared channel data includes information for requesting restoration of the RRC connection.
  • 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.
  • this application implements The examples will not be repeated.
  • the network device can parse the preamble and the physical uplink shared channel data included in the first message.
  • the network device successfully parses the preamble and parses the physical uplink shared channel data successfully , The network device will send the response message of the first message to the terminal according to the analysis result, that is, perform the following S1402:
  • the network device sends a response message of the first message to the terminal.
  • the response message includes contention resolution information.
  • the response message of the first message may also include RAPID, TA, and TC-RNTI.
  • 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.
  • the terminal When the response message is an RRC connection release message, the terminal returns to the initial state, for example, the inactive state.
  • the terminal determines that the contention resolution is passed, starts or restarts the timer, and converts the TC-RNTI to the C-RNTI.
  • the response message of the first message carries the uplink resources and the first indication information, and the first indication information is used to indicate "uplink transmission on the uplink resources indicated by the uplink authorization is not allowed"
  • the terminal receives the After responding to the message, it is determined that the contention resolution is passed, and the timer is started or restarted. At this time, the terminal may send a confirmation response of the response message to the network device on the uplink resource.
  • the terminal When the response message of the first message carries the uplink resource and the first indication information, and the first indication is used to indicate "allow uplink transmission on the uplink resource indicated by the uplink authorization", correspondingly, the terminal receives the response message After that, it is determined that the contention resolution is passed, and the timer is started or restarted. At this time, the terminal can send uplink data to the network device on the uplink resource.
  • the terminal receives the contention resolution information response message from the network device, it indicates that the network device has successfully received the physical uplink shared channel data sent by the terminal. If the terminal still has uplink data to be transmitted at this time, the terminal can also continue to perform the following S1403-S1404:
  • S1404 Perform uplink transmission on the uplink resource indicated by the uplink authorization.
  • the terminal After receiving the contention resolution information, if the terminal has not received the RRC connection release message at this time, the terminal starts or restarts the timer, and during the running of the timer, receives the authorization from the network device, and the authorization is used for uplink data transmission or Downlink data reception; optionally, the authorization is used for new transmissions, not for retransmissions; the authorization can be an uplink authorization or a downlink authorization, and when the authorization is received, the timer is restarted, thereby delaying the terminal's monitoring of the authorization.
  • the terminal starts or restarts the timer, and performs uplink transmission on the uplink resource indicated by the uplink authorization; if the downlink authorization is received from the network device, and it has not been received When the RRC connection release message indicates that the network device still has data to be transmitted, the terminal starts or restarts the timer.
  • the terminal extends the time to wait for the RRC connection release message, and realizes the data transmission when the terminal is in the inactive state. It does not need to wait until the RRC connection is restored to perform the uplink transmission. There is no need for the terminal to enter the connected state to send data, which not only improves the data transmission It is efficient and reduces the overhead required for RRC connection recovery.
  • the timer is not always in the running state after being started or restarted, but the timer is stopped when certain conditions are met, for example, as described above The scene of stopping the timer.
  • the control timer stops running, that is, the timer is stopped.
  • the terminal receives a radio resource control (RRC) connection recovery, connection establishment message, etc. from the network device, the terminal can also stop the timer.
  • RRC radio resource control
  • the terminal monitors the PDCCH scrambled by the C-RNTI.
  • the PDCCH indicates the PUSCH resource and is used to send uplink data or BSR.
  • the terminal monitors the PDCCH scrambled by the C-RNTI, and the PDCCH indicates PDSCH resources for receiving downlink data.
  • the terminal monitors the PDCCH scrambled by the C-RNTI, and receives downlink feedback of uplink data.
  • the terminal Each time the terminal receives the uplink grant or downlink grant of the C-RNTI scrambled PDCCH, it starts or restarts the timer to keep monitoring the PDCCH scrambled by the C-RNTI for the duration of the PDCCH scrambled by the network equipment.
  • the PDCCH transmission time is kept synchronized, and when the timer expires, the terminal stops monitoring the PDCCH scrambled by the C-RNTI.
  • FIG. 15 is a schematic flowchart of a configuration method provided by an embodiment of the present application.
  • Configuration methods can include:
  • the network device sends instruction information to the terminal.
  • the indication information is used to instruct the terminal to monitor the physical downlink control channel (PDCCH) when in the inactive state.
  • PDCCH physical downlink control channel
  • the network device may send an RRC connection release message to the terminal.
  • the RRC connection release message includes indication information. That is, the network device may carry the indication information in the RRC connection release message and send it to the terminal.
  • the terminal may receive The RRC connection release message obtains the indication information. It is understandable that after receiving the RRC connection release message, the terminal will enter the inactive state from the connected state, and then monitor the PDCCH in the inactive state according to the indication information, so that the terminal can be independently configured to monitor the PDCCH in the inactive state. This function is configured when it is configured to enter the inactive state, and no additional signaling is required to indicate separately, saving signaling.
  • the network device can also send the instruction information in other ways, for example, carry the instruction information in a broadcast message and broadcast it.
  • the terminal can obtain the instruction information by receiving the broadcast message. In this way, there is no need to separate the instruction information for each terminal. Monitor the PDCCH configuration when in the inactive state.
  • the embodiments of the present application only take these two methods as examples for description, but it does not mean that the embodiments of the present application are limited to these.
  • the indication information can be realized by one bit.
  • the value of this bit is 1, which means that the function of monitoring the physical downlink control channel (PDCCH) scrambled by C-RNTI when in the inactive state is enabled, and the value of this bit is 0 means that the function of monitoring the physical downlink control channel (PDCCH) in the inactive state is not enabled.
  • the indication information can also be implemented through enumeration type, for example: ⁇ TURE ⁇ , ⁇ downlink reception ⁇ . Since the PDCCH is scrambled by the cell radio network temporary identity (C-RNTI), in another implementation, the indication information may be C-RNTI.
  • the terminal when the C-RNTI is carried in the RRC connection release message, the terminal is indicated Monitor the PDCCH scrambled by the C-RNTI in the inactive state; when the RRC connection release message does not carry the C-RNTI, the terminal is instructed not to monitor the PDCCH in the inactive state.
  • the terminal After receiving the instruction information sent by the network device, the terminal can determine the C-RNTI that scrambles the PDCCH, and then use the C-RNTI to monitor the PDCCH scrambled by the C-RNTI.
  • the network device may send the C-RNTI to the terminal in the RRC connection release message.
  • the RRC connection release message may include the indication information and the C-RNTI, or include the C-RNTI, as described above, the C-RNTI -RNTI is the indication information.
  • the C-RNTI is valid in an access network notification area (RAN notification area, RNA) or indicated cell, or in the current access cell.
  • the network device may indicate the RNA corresponding to the C-RNTI, where there may be one or more RNAs corresponding to the C-RNTI.
  • the network device may indicate the RNA ID or RNA ID list corresponding to the C-RNTI, the RAN ID Or the RAN ID list can also be carried in the RRC connection release message, or carried in other messages.
  • the network device may indicate the cell ID or cell ID list corresponding to the C-RNTI, and the cell ID or cell ID list may also be carried in the RRC connection release message, or carried in other messages.
  • the terminal can use the C-RNTI to monitor the PDCCH in the RAN area indicated by the RAN ID or the cell indicated by the cell ID.
  • the network device does not indicate the RNA or the cell, it can be considered that the C-RNTI is valid in the current access cell, where the current access cell is the cell that sends the RRC connection release message.
  • the network device may not send the C-RNTI to the terminal.
  • the terminal may monitor the C-RNTI by using the C-RNTI acquired during the random access process of accessing the current cell. Scrambled PDCCH.
  • the current access cell is the cell that sends the RRC connection release message.
  • the terminal After receiving the indication information and determining the C-RNTI to scramble the PDCCH, the terminal can monitor the PDCCH scrambled by the C-RNTI according to the indication information, that is, perform the following S1502:
  • the terminal monitors the PDCCH scrambled by the C-RNTI according to the indication information.
  • the time to monitor the PDCCH can be determined from the two dimensions of the time domain and the frequency domain.
  • the terminal can use the paging occasion as the time to monitor the C-RNTI scrambled PDCCH. Specifically, the terminal receives the DRX configuration parameters, and determines the paging occasion according to the discontinuous reception (discontinuous reception, DRX) configuration parameters, that is, monitors the PDCCH scrambled by the paging radio network temporary identifier (P-RNTI) Time; and use the paging occasion as an occasion to monitor the PDCCH scrambled by the C-RNTI.
  • DRX discontinuous reception
  • P-RNTI radio network temporary identifier
  • FIG. 16 is a schematic diagram of determining a timing for monitoring a PDCCH scrambled by C-RNTI according to an embodiment of the application.
  • part of the time in the paging occasion can be determined as the time to monitor the PDCCH scrambled by the C-RNTI, which can be specifically set according to actual needs.
  • T represents the DRX cycle of the terminal
  • N represents the number of paging frames in the DRX cycle
  • Ns represents the number of paging occasions in the paging frame
  • PF_offset represents the offset value used to determine the paging radio frame
  • the terminal_ID is The terminal identifier is different in different communication systems.
  • T, N, Ns, and PF_offset may be configured by the network device to the terminal.
  • it is configured to the terminal through a broadcast message or configured to the terminal through an RRC dedicated message.
  • the PDCCH scrambled by the C-RNTI can be monitored at all paging occasions or part of the paging occasion.
  • the C-RNTI scrambled PDCCH can be monitored during a part of the paging occasion.
  • FIG. 17 is another method of determining monitoring C-RNTI scrambling provided by an embodiment of the application. Schematic diagram of the timing of the PDCCH. As shown in FIG. 17, the shaded part in FIG. 17 is the time to monitor the PDCCH scrambled by the C-RNTI.
  • the timing for monitoring the C-RNTI to scramble the PDCCH may be determined according to a parameter, and the parameter may be configured by the network device to the terminal, or preset.
  • each paging occasion is N time slots or symbols
  • this parameter is used to indicate that the M time slots or symbols are used to monitor the C-RNTI scrambled PDCCH.
  • this parameter is used to indicate M, and the terminal defaults that the first M or the last M time slots or symbols are used to monitor the PDCCH scrambled by the C-RNTI.
  • this parameter is used to indicate the S-th time slot or symbol, and the terminal starts to monitor the C-RNTI scrambled PDCCH from the S-th time slot or symbol or starts to monitor after the S-th time slot or symbol PDCCH scrambled by C-RNTI.
  • M, N, S are positive integers, and M and S are less than N.
  • a similar method to the above determination of the paging occasion can be used to determine the time to monitor the C-RNTI scrambled PDCCH.
  • FIG. 18 is another schematic diagram of determining the timing of monitoring the PDCCH scrambled by the C-RNTI according to an embodiment of the application. As shown in FIG. 18, the shaded part in FIG. 18 is the time to monitor the PDCCH scrambled by the C-RNTI.
  • determining the timing of monitoring the PDCCH scrambled by the C-RNTI and determining the paging timing are independent.
  • a manner similar to determining the paging occasion may be used to determine the timing of monitoring the PDCCH scrambled by the C-RNTI.
  • the difference is that the parameters used are different, for example, the PF_offset used is different.
  • T represents the DRX cycle of the terminal
  • N represents the number of paging frames in the DRX cycle
  • Ns represents the number of paging occasions in the paging frame
  • PF_offset1 represents the offset value used to determine the C-RNTI PDCCH radio frame
  • the terminal_ ID is a terminal identifier, which is different in different communication systems.
  • T, N, Ns, and PF_offset1 may be configured by the network device to the terminal.
  • it is configured to the terminal through a broadcast message or configured to the terminal through an RRC dedicated message.
  • PF_offset1 and the offset value PF_offset used to determine the paging radio frame can be configured independently. This makes the timing of monitoring the PDCCH scrambled by the C-RNTI and the paging timing of the PDCCH scrambled by the P-RNTI independent.
  • FIG. 19 is another schematic diagram of determining the timing of monitoring the PDCCH scrambled by the C-RNTI according to an embodiment of the application.
  • the radio frame also known as C-RNTI scrambled PDCCH
  • the offset value is PF_offset2 identification
  • C-RNTI PDCCH radio frame paging radio frame + PF_offset2, where PF_offset2 can be configured by the network device to the terminal, or it can be a preset value.
  • the terminal can use the same manner as the above to determine the i_sth paging occasion to determine the timing of monitoring the PDCCH scrambled by the C-RNTI in the C-RNTI PDCCH radio frame, that is, the monitoring timing.
  • the i_sth paging occasion can be configured by the network device to the terminal, or it can be a preset value.
  • the terminal when the terminal moves out of the effective area of the C-RNTI, it can stop monitoring the PDCCH scrambled by the C-RNTI.
  • the network device sends indication information to the terminal to instruct the terminal to monitor the C-RNTI scrambled PDCCH when the terminal is in the inactive state, so that the terminal can monitor the C-RNTI scrambled
  • the downlink data is received during the PDCCH process.
  • the entire receiving process does not need to receive paging or initiate an RRC connection recovery request. Instead, the downlink data is directly received in the inactive state, which not only improves transmission efficiency, but also reduces Terminal overhead.
  • the network device to which the cell belongs will generate the context of the terminal, and the terminal will also generate the context of the terminal according to the configuration message sent by the network device.
  • the network device After the RRC state of the terminal changes, the network device will process the terminal context. For example, when the terminal transitions from the RRC connected state (referred to as the connected state) to the RRC idle state (referred to as the idle state), the network device will release the context of the terminal.
  • the terminal and network equipment save part of the access layer configuration (called the context of the access layer terminal) and the non-access layer configuration (called the non-access layer terminal's context). Context).
  • the terminal may periodically initiate an access network notification area update (RAN-based Notification Area Update, R-NAU) process to the network equipment to inform the network equipment terminal of the access network notification area (RAN-based Notification Area, RNA).
  • R-NAU access network notification Area Update
  • RNA RAN-based Notification Area
  • the terminal in the inactive state reselects to a new cell, it initiates an R-NAU process to the network device to which the new cell belongs, and informs the network device of the RNA where the terminal is located.
  • the network device When the network device receives the downlink data of the terminal, it pages the terminal in the RNA cell where the terminal is located. After the terminal receives the page, it initiates a state transition process from the inactive state to the connected state. The network device notifies the terminal to restore the saved access layer configuration. After the terminal enters the connected state, the network device sends downlink data to the terminal. When the terminal has uplink data to be sent, the terminal initiates a state transition process from the inactive state to the connected state, the network device notifies the terminal to restore the saved access layer configuration, and the terminal sends the uplink data after entering the connected state.
  • the terminal needs to send an RRC connection resume (resume) request message to the network device.
  • RRC connection resume resume (resume) request message
  • the T319 timer is introduced.
  • the terminal starts the T319 timer and sends it to the network device.
  • the network device sends an RRC connection recovery request message, and stops the T319 timer when receiving an RRC response message such as an RRC connection recovery, an RRC connection establishment, or an RRC connection release message sent by the network device.
  • T319 expires, the terminal releases the connection and enters the idle state due to the failure of the RRC connection recovery.
  • uplink data transmission can be performed in the inactive state.
  • the terminal sends uplink data to the network device while sending the RRC connection resume (resume) request message.
  • the terminal in the inactive state may continue to send data after sending the "RRC connection recovery request" message, and the RRC connection recovery request message may not be carried when the subsequent data is sent, so as to reduce the signaling overhead.
  • the terminal sends subsequent data if the T319 timer expires, the terminal will enter the RRC idle state and cannot flexibly support multiple data transmissions.
  • the terminal can restart the T319 timer when certain conditions are met. This can extend the time the terminal waits for the RRC response message of the RRC connection recovery request and flexibly support multiple Data transmission.
  • a new timer can also be started.
  • the new timer can be an RRC layer timer or a MAC layer timer other than the T319 timer, so that the terminal can start the new timer when certain conditions are met.
  • And perform data transmission during the operation of the new timer which can also extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly supports multiple data transmissions.
  • the terminal When the terminal responds to the requirement of RRC connection recovery, it starts the first timer and sends the RRC connection recovery request message to the network device; in this way, during the running of the first timer, the terminal The first timer can be restarted according to the downlink information received from the network device or according to the data transmission with the network device; or, during the operation of the first timer, the terminal can be based on the downlink information received from the network device or according to the For data transmission with the network device, the second timer is started. It can be seen that in the embodiment of the present application, by restarting the first timer or starting the second timer, data transmission is performed during the running period of the first timer or the second timer, which can effectively extend the terminal waiting for the RRC connection. Recovery of the requested RRC response message time, thereby flexibly supporting multiple data transmissions.
  • the configuration method provided by the embodiment of the present application may include at least two possible scenarios.
  • a possible scenario when the terminal responds to the RRC connection recovery demand, it starts the first timer, and meets the restart condition during the running of the first timer, restarts the first timer to extend the terminal waiting for RRC The time of the RRC response message for the connection recovery request.
  • the restarted timer when the restart condition is met, the restarted timer is the same timer as the restarted timer when the RRC connection is restored, and both are the first timers.
  • the terminal when the terminal responds to the RRC connection recovery demand, it starts the first timer, and when the start condition is met during the running of the first timer, the second timer is started to extend the waiting time of the terminal.
  • the time of the RRC response message of the RRC connection recovery request when the restart condition is met, the restarted timer is not a timer, but a new timer that is additionally set when the restarted timer is required for the recovery of the RRC connection. Device.
  • the first timer after starting the second timer, the first timer can also be stopped; of course, the first timer can also be stopped first, and then the second timer can be started, or after starting the second timer. At the same time as the second timer, stop the first timer. In this way, the second timer is used to take over the work of the first timer, so as to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the terminal sends an RRC connection recovery request message to the network device, starts the first timer, and restarts the first timer when the restart condition is met, In order to perform the first extension operation; the second extension operation or the third extension operation can be performed subsequently,....
  • M is greater than or equal to 1
  • the terminal may directly send uplink data without sending an RRC connection recovery request message to the network device, and restart the first timer when the restart condition is met. , In order to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the terminal sends an RRC connection recovery request message to the network device and starts the first timer; and when the start condition is met, the second timer is started, To perform the first extension operation; and then when the restart conditions can be met, perform the second extension operation, or the third extension operation;
  • M is greater than or equal to 1
  • the terminal may directly send uplink data without sending an RRC connection recovery request message to the network device, and when the start or restart conditions are met, start or restart the The second timer is to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the terminal responds to the RRC connection recovery demand, it starts the first timer, and meets the restart condition during the running of the first timer, restarts the first timer to Extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the following at least three possible implementation manners may be included.
  • the first timer may be the T319 timer configured by the current network, that is, when the terminal responds to the RRC connection recovery request, it first starts the T319 timer and sends the RRC connection recovery request to the network device. Message; 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 or according to the data transmission with the network device.
  • the first timer may be a new timer T1 that is additionally set by the RRC layer, in addition to the T319 timer, that is, the terminal starts the new timer first when the RRC connection is restored.
  • the terminal can restart the new timing according to the downlink information received from the network device or according to the data transmission with the network device ⁇ T1.
  • the first timer may be an additional setting, a new timer T2 in addition to the T319 timer, which is different from the timer T1 in the second possible implementation manner described above.
  • the new timer T2 is a timer set in the MAC layer, that is, when the terminal responds to the RRC connection recovery demand, it first starts the new timer T2, and sends the RRC connection recovery request message to the network device; in this way, the new timer During the operation of T2, the terminal can 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.
  • the following describes in detail how to control the restart of the first timer to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request for the above three possible implementation manners, so as to flexibly support multiple data transmissions.
  • the first timer may be the T319 timer configured by the current network, that is, when the terminal responds to the requirement of RRC connection recovery, it first starts the T319 timer and sends the RRC connection to the network device. Resume request message; 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 or according to the data transmission with the network device. It should be noted that in this possible implementation manner, during the running of the T319 timer, the terminal can restart the T319 timer according to the downlink information received from the network device as an example for description.
  • FIG. 20 is a schematic flowchart of a configuration method provided by an embodiment of the application.
  • the configuration method may include:
  • S2001 The terminal starts the T319 timer when responding to the requirement of RRC connection recovery.
  • the terminal Before starting the T319 timer, the terminal first configures the duration of the T319 timer, so that the T319 timer can run 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 the information indicating the duration of the T319 timer included in the broadcast message or the RRC message duration. Among them, the duration of the T319 timer can be the first duration of the T319 timer configured in the current network.
  • the first duration can be ⁇ 100ms, 200ms, 300ms, 400ms, 600ms, 1000ms, 1500ms, 2000ms ⁇
  • a certain value can also be greater than a second duration of the T319 timer configured in the current network.
  • the second duration can be configured through broadcast messages or RRC messages.
  • the second duration is ⁇ 100ms, 200ms, 300ms, 400ms, 600ms ,1000ms,1500ms,2000ms,2500ms ⁇ , for example, the second duration can be 2500ms.
  • the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively extended. 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, which is convenient for the terminal network device to perform multiple data transmissions.
  • the T319 timer is configured with the above two different durations, before starting the timer, first determine which duration the T319 timer uses, that is, the first duration or the second duration. When determining which time duration the T319 timer uses, if the terminal meets one of the following conditions, it is determined that the duration of the T319 timer uses the second duration.
  • Condition 1 the terminal expects continuous uplink data transmission in the inactive state; condition 2: the terminal cannot send uplink data in the inactive state at one time; condition 3, the amount of data to be sent by the terminal is greater than the pre-configured threshold; condition 4, the terminal supports inactive State uplink data transmission; Condition 5, the terminal is configured with a T319 timer of duration 2.
  • the terminal may also send an indication message to the network device.
  • the indication information is used to indicate to the network device, the terminal starts the T319 timing
  • the duration of the device is the second duration, so that the information that the T319 timer has been started is synchronized to the network device. It is understandable that the operation of synchronizing the information that the terminal has started the T319 timer to the network device through the indication information can be performed only when the start operation is performed for the first time, and in the subsequent restart operation, the terminal does not need to send the information to the network device. Send the instructions.
  • S2002 The terminal sends an RRC connection recovery request message to the network device.
  • the RRC connection recovery request message may include at least one of the I-RNTI, the identity verification information of the terminal, and the reason value for the UE to initiate the RRC connection recovery request.
  • I-RNTI is used to represent the unique identification of the terminal in the range of an RNA.
  • the identity verification information of the terminal is the identity verification information generated according to the C-RNTI and the RRC integrity key stored by the terminal.
  • the terminal may send the RRC connection recovery request message to the network device by configuring the uplink resource indicated by the authorization information.
  • the configuration authorization information can be obtained from a broadcast message of the network device, or can be obtained from a dedicated message sent by the network device to the terminal.
  • the terminal may also send to the network device at least one of uplink data, auxiliary information, and indication information that it is expected to remain in an inactive state and continue to send data.
  • the auxiliary information is used to indicate the amount of data in the terminal buffer, so that the network device determines that the terminal enters the connected state or continues to be in the inactive state according to the amount of data in the terminal buffer.
  • the uplink data and the RRC connection recovery request message are sent together or independently.
  • the common transmission or independent transmission in this application refers to whether the uplink data and the RRC connection recovery request message are sent through the same message, such as a MAC PDU message.
  • the uplink data and the RRC connection recovery request message are sent through the same message, it can be understood as The uplink data and the RRC connection recovery request message are sent together; on the contrary, if the uplink data and the RRC connection recovery request message are not sent in the same message, it can be understood that the uplink data and the RRC connection recovery request message are sent independently. In addition, if the uplink data and the RRC connection recovery request message are sent independently, the uplink data may be sent during the running period of the first timer after the RRC connection recovery request message is sent.
  • the network device can send corresponding downlink information to the terminal according to the RRC connection recovery request message, that is, perform the following S2003:
  • the network device sends downlink information to the terminal according to the RRC connection recovery request message.
  • the downlink information sent by the network device to the terminal includes the feedback information of the RRC connection recovery request message. If the terminal sends an RRC connection recovery request message and uplink data to the network device, the downlink information sent by the network device to the terminal includes the RRC connection recovery request message and feedback information of the uplink data.
  • the downlink information may include at least one of the following: feedback information of the RRC connection recovery request message, timing adjustment commands, power control commands, contention resolution information, Uplink authorization information, downlink resource allocation information, and indication information of newly added fields.
  • the indication information is used to instruct the terminal to restart the T319 timer.
  • the downlink information may also include other information.
  • the embodiment of the present application only uses the downlink information to include the feedback information and timing adjustment of the RRC connection recovery request message.
  • 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, timing adjustment command, power control command , Contention resolution information, uplink authorization information, downlink resource allocation information, and indication information for newly added fields.
  • the downlink information may also include other information.
  • the embodiment of the application only uses the downlink information to include the feedback information of the RRC connection recovery request message, the feedback information of the uplink data, the timing adjustment command, the power control command, and the contention resolution information.
  • At least one of the uplink authorization information, the downlink resource allocation information, and the indication information of the newly added field is described as an example, but it does not mean that the embodiment of the present application is limited to this.
  • the network device After the network device receives the RRC connection recovery request message sent by the terminal, or the RRC connection recovery request message and uplink data sent by the terminal, it can be based on the received RRC connection recovery request message, or the RRC connection recovery request message and uplink data. Generate corresponding downlink information, and send the generated downlink information to the terminal. For example, when the network device sends the generated information to the terminal, the generated information may be carried in the PDCCH downlink control information, MAC message, or RRC message and sent to the terminal.
  • the downlink information received by the terminal from the network device includes the feedback information of the RRC connection recovery request message, and the RRC connection is recovered
  • the feedback information of the request message indicates whether the RRC connection recovery request message is successfully transmitted, and the feedback information is ACK or NACK. If the feedback information is ACK, it means that the RRC connection recovery request message is sent successfully and the terminal can continue to send new uplink data on the configuration authorization; if the feedback information is NACK, it means that the RRC connection recovery request message has failed to be sent and the terminal can continue Retransmit the RRC connection recovery request message on the configuration authorization.
  • the downlink information received by the terminal from the network device may also include contention resolution information.
  • the contention resolution information may be the contention resolution information in S1005 in the embodiment shown in FIG. 10, or may be the content resolution information in S1005 in the embodiment shown in FIG.
  • the contention resolution information in S1105 in the embodiment shown in 11 if the contention resolution information is that the contention resolution is successful, it means that the RRC connection recovery request message is sent successfully, and the terminal can continue to send new uplink data on the pre-allocation authorization; if The contention resolution information is that the contention resolution failed, which means that the RRC connection recovery request message has failed to be sent, and the terminal can continue to retransmit the RRC connection recovery request message on the pre-configuration authorization.
  • the terminal restarts the T319 timer and performs data transmission during the T319 timer operation, which can effectively extend the terminal waiting for the RRC connection recovery request
  • the time of the RRC response message can flexibly support multiple data transmissions.
  • the downlink information received by the terminal from the network device includes the RRC connection recovery request message and the feedback information of the uplink data.
  • the RRC connection recovery request message and The feedback information of the uplink data indicates whether the RRC connection recovery request message and the uplink data are successfully transmitted, and the feedback information is ACK or NACK.
  • the feedback information is ACK, it means that the RRC connection recovery request message and 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 means that the RRC connection recovery request message and/or If the uplink data transmission fails, the terminal can continue to retransmit the RRC connection recovery request message on the configuration grant, and/or retransmit part or all of the original uplink data.
  • the downlink information received by the terminal from the network device may also include contention resolution information.
  • the contention resolution information may also be the contention resolution information in S1005 in the embodiment shown in FIG. It can be the contention resolution information in S1105 in the embodiment shown in Figure 11 above.
  • the contention resolution information is that the contention resolution is successful, it means that the RRC connection recovery request message and uplink data are successfully sent, and the terminal can continue to perform new pre-allocation authorization. If the contention resolution information is that the contention resolution failed, it means that the RRC connection recovery request message and/or the uplink data transmission failed, and the terminal can continue to retransmit the RRC connection recovery request message on the pre-configuration authorization, and/ Or, retransmission of part or all of the original uplink data.
  • the terminal restarts the T319 timer and performs data transmission during the T319 timer operation, which can effectively extend the terminal's waiting for RRC
  • the time of the RRC response message of the connection recovery request can flexibly support multiple data transmissions.
  • the downlink information received by the terminal may also include uplink authorization information, and the uplink resources indicated by the uplink authorization information may be used for The retransmission of the original uplink data can also be used for the initial transmission of new uplink data to achieve data transmission of multiple consecutive packets.
  • the new uplink data can be first transmitted through the uplink resources indicated by the uplink authorization information, that is, the transmission priority of the initial data transmission. Higher than the transmission priority of data retransmission.
  • the downlink information received by the terminal may also include downlink resource allocation information.
  • 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 to realize downlink data. Early pass. It should be noted that in this embodiment of the application, uplink authorization information and downlink resource allocation information may exist independently, that is, the downlink information received by the terminal may include uplink authorization information or downlink resource allocation information; uplink authorization information and downlink resources The allocation information can exist at the same time, that is, the downlink information received by the terminal can include both uplink grant information and downlink resource allocation information.
  • the terminal restarts the T319 timer and performs data transmission during the T319 timer operation, which can effectively extend the terminal waiting for the RRC connection
  • the time for the RRC response message of the recovery request can flexibly support multiple data transmissions.
  • the terminal restarts the T319 timer 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 initial downlink transmission.
  • the terminal restarts the T319 timer according to the downlink information received from the network device, for example, the downlink information received by the terminal may include an indication information, which may be carried in the physical layer control signaling, MAC layer message Or in the RRC layer message, the indication information is used to instruct the terminal to restart the T319 timer; correspondingly, the terminal can restart the T319 timer after receiving the information including the indication information, so that data can be performed during the running of the T319 timer. Transmission can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly supports multiple data transmissions.
  • the terminal when the terminal is running the T319 timer, when the terminal restarts the T319 timer according to the downlink information received from the network device, if the downlink information received by the terminal includes feedback information, uplink authorization information, and downlink resource allocation When any one or more of the information and the indication information of the newly added field are selected, the T319 timer is restarted, so that data transmission is performed during the running of the T319 timer, which can effectively prolong the terminal waiting for the RRC response of the RRC connection recovery request message. Time, flexibly supports multiple data transmissions.
  • the downlink information received by the terminal further includes a timing adjustment command and/or a power control command. Wherein, when the timing adjustment command is received, the timing adjustment command is applied to perform uplink transmission timing adjustment; when the power control command is received, the power control command is applied to perform power control.
  • the terminal After the terminal restarts the T319 timer according to the received downlink information, if the current T319 timer is started for the first time, the terminal can also send an instruction message to the network device, which is used to instruct the network device to restart the T319 timer , So as to synchronize the information that the T319 timer has been restarted to the network device. Moreover, for the T319 timer, after restarting, the T319 timer is not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the T319 timer.
  • the terminal By executing the above S2001-S2004, when the terminal responds to the RRC connection recovery demand, it starts the T319 timer and sends the RRC connection recovery request message to the network device; in this way, the terminal can receive the request from the network device during the operation of the T319 timer. Restart the T319 timer for the downlink information and perform data transmission during the operation of the T319 timer, which can effectively extend the time that the terminal waits for the RRC response of the RRC connection recovery request message, and flexibly supports multiple data transmissions.
  • the above whole process can be understood as the terminal performing the first extension operation.
  • the T319 timer can also be restarted according to the downlink information received from the network device while the T319 timer is restarted and running.
  • the timer is used to extend the time for the terminal to wait for the RRC response of the RRC connection recovery request message again.
  • This process can be understood as the terminal performing the second extension operation.
  • the method for the terminal to perform the third extension operation, or the Nth (N greater than 3) extension operation thereafter is similar to the method for the terminal to perform the first extension operation.
  • the device receives the downlink information and restarts the T319 timer, it can further execute the following S2005-S2007:
  • S2005 The terminal sends uplink data to the network device during the operation of the T319 timer.
  • the terminal can send the uplink data to the network device by configuring the uplink resource indicated by the authorization information system.
  • the configuration authorization information can be obtained from a broadcast message of the network device, or can be obtained from a dedicated message (such as an RRC message) sent by the network device to the terminal.
  • the terminal may not send the RRC connection recovery request message to the network device, but directly send the uplink data, and restart the T319 when the restart condition is met. Timer to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request.
  • the network device sends downlink information to the terminal according to the uplink data.
  • the downlink information may include uplink data feedback information, timing adjustment commands, power control commands, contention resolution information, uplink authorization information, downlink resource allocation information, and indication information of newly added fields.
  • the downlink information may also include other information.
  • the embodiment of the application only uses the downlink information to include uplink data feedback information, timing adjustment commands, power control commands, contention resolution information, uplink authorization information, and downlink resource allocation information.
  • at least one of the indication information of the newly added field are described as an example, but it does not mean that the embodiment of the present application is limited to this.
  • 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 the network device sends the generated information to the terminal, the generated information may be carried in the PDCCH downlink control information, MAC message, or RRC message and sent to the terminal.
  • the terminal restarts 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 feedback information, uplink authorization information, downlink resource allocation information, and the indication information of the newly added field.
  • the T319 timer is restarted, that is, the second extension operation is performed, so that data transmission is performed during the running of the T319 timer, which can effectively extend the time the terminal waits for the RRC response of the RRC connection recovery request message. It flexibly supports multiple data transmissions. For details, please refer to the relevant description in the above S2004. Here, the details are not described in the embodiment of the present application.
  • the terminal when restarting the T319 timer, it is just taken as an example that the terminal can restart the T319 timer according to the downlink information received from the network device during the running period of the T319 timer.
  • the T319 timer can also be restarted according to the data transmission with the network device. For example, during the operation of the T319 timer, if the terminal sends uplink data, for example, dedicated traffic channel (DTCH) ) Data, restart the T319 timer; or, if downlink data, such as DTCH data, is received, restart the T319 timer.
  • uplink data for example, dedicated traffic channel (DTCH)
  • DTCH dedicated traffic channel
  • the terminal When the first timer is the T319 timer configured by the current network, the terminal first starts the T319 timer when the RRC connection is restored. And send an RRC connection recovery request message to the network device; during the running of the T319 timer, the terminal can restart the technical solution of the T319 timer according to the downlink information received from the network device.
  • the first timer can be an additional timer T1 set by the RRC layer, in addition to the T319 timer, the terminal responds to the requirement of RRC connection recovery.
  • the RRC connection recovery request message is sent to the network device; during the operation of the new timer T1, the terminal can according to the downlink information received from the network device or according to the data transmission with the network device, The technical solution for restarting the new timer T1.
  • the difference from the embodiment shown in FIG. 20 is that the first timer in this possible implementation is no longer the T319 timer, but is additionally set by the RRC layer.
  • a new timer T1 in addition to the T319 timer that is, when the terminal responds to the RRC connection recovery demand, the new timer T1 is started, and during the operation of the new timer T1, according to the received from the network device Downlink information or restart the new timer T1 according to the data transmission with the network device, so as to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, thereby flexibly supporting multiple data transmissions.
  • the T319 timer may not be started.
  • the terminal Before starting the new timer T1, the terminal first configures the duration of the new timer T1 so that the new timer T1 can run based on the configured duration.
  • the method for configuring the duration of the new timer T1 is the same as that shown in FIG. 20.
  • the method for configuring the duration of the T319 timer in the embodiment is similar, and details are not described herein again in the embodiment of the present application.
  • the method of the new timer T1 is the same as in the embodiment shown in FIG. 20.
  • the RRC connection recovery request message is sent to the network device, and during the running of the T319 timer, according to the received from the network device
  • the downlink information or the method of restarting the T319 timer according to data transmission with the network device is similar.
  • the new timer T1 after the new timer T1 is started, how to send the RRC connection recovery request message to the network device , 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 embodiment of this application will not repeat the description.
  • the first timer in this possible implementation manner is not the T319 timer, but is additionally set by the RRC layer, except for the T319 timing A new timer T1 outside the device, in order to save the power consumption of the terminal due to the operation of the T319 timer, in this possible implementation manner, the T319 timer may not be started.
  • the new timer T1 after restarting, the new timer T1 is not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the new timer T1.
  • the terminal when the first timer is a new timer T2 set by the MAC layer, the terminal first starts the new timer T2 when the RRC connection is restored and sends it to the network device.
  • RRC connection recovery request message during the operation of the new timer T2, the terminal can restart the technical solution 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.
  • the first timer in this possible implementation manner is not the T319 timer, but a new timing set by the MAC layer.
  • T2 that is, when the terminal responds to the RRC connection recovery demand, it starts the new timer T2, and during the operation of the new timer T2, according to the downlink information received from the network equipment or according to the data between the network equipment
  • the transmission restarts the new timer T2 to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, thereby flexibly supporting multiple data transmissions.
  • the T319 timer may not be started.
  • the terminal Before starting the new timer T2, the terminal first configures the duration of the new timer T2 so that the new timer T2 can run based on the configured duration.
  • the method for configuring the duration of the new timer T2 is the same as that shown in FIG. 20.
  • the method for configuring the duration of the T319 timer in the embodiment is similar, and details are not described herein again in the embodiment of the present application.
  • the method of the new timer T2 is the same as in the embodiment shown in FIG. 20.
  • an RRC connection recovery request message is sent to the network device, and during the running period of the T319 timer, according to the received from the network device
  • the downlink information or the method of restarting the T319 timer according to data transmission with the network device is similar.
  • the new timer T2 how to send the RRC connection recovery request message to the network device
  • the embodiment of this application will not repeat the description.
  • the first timer in this possible implementation manner is not the T319 timer, but a new timer T2 of the MAC layer.
  • the T319 timer may also not be started.
  • the new timer T2 after restarting, the new timer T2 is not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the new timer T2.
  • the MAC layer of the terminal After restarting the new timer T2, if the timer T2 expires, the MAC layer of the terminal will notify the RRC layer that the timer T2 expires, and the MAC layer of the terminal enters the idle state according to the timer T2 timeout information.
  • the restart timer is the same as the timer started when the RRC connection is restored, and both are the first timer to extend The time for the terminal to wait for the RRC response message of the RRC connection recovery request, thereby flexibly supporting the technical solution of multiple data transmissions.
  • the restarted timer is not the same as the restarted timer when the RRC connection is restored, but an extra set.
  • the new timer technical solution that is, when the terminal responds to the RRC connection recovery demand, it starts the first timer, and when the start condition is met during the running of the first timer, starts the second timer to extend the terminal waiting The time of the RRC response message of the RRC connection recovery request. It is understandable that in this possible scenario, after starting the second timer, the first timer can also be stopped; of course, the first timer can also be stopped first, and then the second timer can be started.
  • the first timer may be the T319 timer configured by the current network
  • the second timer may be a new timer other than the T319 timer that is additionally set by the RRC layer.
  • the new timer in this application can be recorded as the new timer T3.
  • the new timer T3 can be the new timer T1 in the above embodiment, or it can be a new timer that is additionally set. Timer.
  • the terminal when the terminal responds to the requirement of RRC connection recovery, it first starts the T319 timer and sends an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can be based on the downlink information received from the network device or according to the For data transmission with the network device, the new timer T3 is started.
  • 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, in order to distinguish the new timer in the foregoing embodiment T2
  • the new timer in this application may be recorded as a new timer T4
  • the new timer T4 may be the new timer T2 in the foregoing embodiment, or may be a new timer additionally set.
  • the terminal when the terminal responds to the requirement of RRC connection recovery, it first starts the T319 timer and sends an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can be based on the downlink information received from the network device or according to the For data transmission with the network device, the new timer T4 is started. It is understandable that in this possible scenario, after starting the second timer, the first timer can also be stopped. In the following, two possible implementations will be described in detail in this possible scenario, how to control the start of the second timer to prolong the time that the terminal waits for the RRC response message of the RRC connection recovery request, so as to flexibly support Multiple data transmissions.
  • the first timer may be the T319 timer configured by the current network
  • the second timer may be a new timer T3 that is additionally set by the RRC layer, in addition to the T319 timer. . That is, when the terminal responds to the requirement of RRC connection recovery, it first starts the T319 timer and sends an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can be based on the downlink information received from the network device or according to the For data transmission with the network device, the new timer T3 is started.
  • the terminal can start or restart the new timer T3 according to the downlink information received from the network device as an example for description.
  • the new timer T3 can also be started or restarted according to data transmission with the network device.
  • FIG. 21 is a schematic flowchart of another configuration method provided by an embodiment of the application.
  • the configuration method may include:
  • the terminal starts the T319 timer when responding to the requirement of RRC connection recovery.
  • the terminal Before starting the T319 timer, the terminal first configures the duration of the T319 timer, so that the T319 timer can run based on the configured duration.
  • the method for configuring the duration of the T319 timer is similar to the method for configuring the duration of the T319 timer in S2001 in the foregoing embodiment. For details, please refer to the relevant description of configuring the duration of the T319 timer. Let me repeat it again.
  • the RRC connection recovery request message can be sent to the network device, that is, the following S2102 is performed:
  • the terminal sends an RRC connection recovery request message to the network device.
  • the RRC connection recovery request message may include at least one of the I-RNTI, the identity verification information of the terminal, and the reason value for the UE to initiate the RRC connection recovery request.
  • I-RNTI is used to represent the unique identification of the terminal in the range of an RNA.
  • the identity verification information of the terminal is the identity verification information generated according to the C-RNTI and the RRC integrity key stored by the terminal.
  • the method for the terminal to send the RRC connection recovery request message to the network device is similar to the method for the terminal to send the RRC connection recovery request message to the network device in S2002.
  • the method for the terminal to send the RRC connection recovery request message to the network device will not be repeated in this embodiment of the application.
  • the terminal in addition to sending the RRC connection recovery request message to the network device, can also send to the network device at least one of uplink data, auxiliary information, and indication information that it is expected to remain in the inactive state and continue to send data.
  • the information sending method is similar to the sending method of at least one of the uplink data, auxiliary information, and the indication information that it is expected to remain in the inactive state to continue sending data to the network device in the above S2002.
  • the relevant description of at least one of the data, the auxiliary information, and the instruction information that is expected to remain in the inactive state to continue sending the data is not repeated here in the embodiment of the present application.
  • the difference from S2002 above is that in the embodiment of this application, in addition to the T319 timer, there is a new timer T3 additionally set by the RRC layer, so the terminal can also send a start instruction message to the network device.
  • the start indication information is used to indicate that during the subsequent operation of the T319 timer, if the start condition is met, the new timer T3 is started, thereby realizing synchronization between the new timer T3 started by the terminal and the new timer T3 started by the network device.
  • the network device can send corresponding downlink information to the terminal according to the RRC connection recovery request message, that is, perform the following S2103:
  • S2103 The network device sends downlink information to the terminal according to the RRC connection recovery request message.
  • the method for the network device to send downlink information to the terminal according to the RRC connection recovery request message is similar to the method for the S2003 network device to send downlink information to the terminal according to the RRC connection recovery request message. Refer to the related description in the above S2003, here, the description of the embodiment of the present application will not be repeated.
  • S2104 During the operation of the T319 timer, the terminal starts a new timer T3 according to the downlink information received from the network device.
  • the terminal Before starting the new timer T3, the terminal first configures the duration of starting the new timer T3, so that the starting new timer T3 can run 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 new timer according to the information indicating the duration of the new timer T3 included in the broadcast message or the RRC message The duration of T3. Regarding the method of obtaining 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 T319 timer can be acquired through the same broadcast message or RRC message, or through different broadcast messages or RRC message acquisition can be set according to actual needs.
  • the information indicating the duration of the new timer T3 can be acquired at the same time as the information indicating the duration of the T319 timer, or can be acquired at a different time.
  • the information indicating the duration of the new timer T3 is acquired, which can be specifically set according to actual needs.
  • the duration of the new timer T3 can be the first duration of the T319 timer configured in the current network.
  • the first duration can be ⁇ 100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms ⁇
  • a certain value of can also be greater than a second duration of the T319 timer configured in the current network.
  • the second duration can be configured through a broadcast message or an RRC message.
  • the second duration is ⁇ 100ms, 200ms, 300ms, 400ms, A value in 600ms, 1000ms, 1500ms, 2000ms, 2500ms ⁇ , for example, the second duration can be 2500ms.
  • the new timer T3 Since the new timer T3 is started when the start condition is met, for these two different durations, the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively extended. 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, which is convenient for the terminal network device to perform multiple data transmissions.
  • the terminal After the duration of the new timer T3 is configured, it can be executed S2104 that the terminal starts the new timer T3 according to the downlink information received from the network device during the operation of the T319 timer.
  • the method of starting a new timer T3 according to the downlink information received from the network device is the same as the method of the terminal in the above S2004 during the operation of the T319 timer, restarting the T319 timer according to the downlink information received from the network device
  • the method of the device is similar, please refer to the relevant description in the above S2004.
  • the method of how the terminal starts the new timer T3 according to the downlink information received from the network device during the operation of the T319 timer is not in the embodiment of this application. Go ahead and repeat.
  • the new timer T3 is started, so that data transmission is performed during the operation of the new timer T3, which can effectively extend the terminal waiting for the RRC connection recovery request
  • the time of the RRC response message can flexibly support multiple data transmissions. If the T319 timer is still running, you can stop the T319 timer.
  • the new timer T3 is started first, and after the new timer T3 is started, the T319 timer is stopped; or the T319 timer can be stopped at the same time as the new timer T3 is started.
  • the downlink information received by the terminal further includes a timing adjustment command and/or a power control command.
  • the timing adjustment command is received, the timing adjustment command is applied to perform uplink transmission timing adjustment; when the power control command is received, the power control command is applied to perform power control.
  • the terminal 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 can also send an indication message to the network device, and the indication information is used to indicate the new timer T3 started by the network device.
  • the timer T3 is used to synchronize the information that the new timer T3 has been started to the network device.
  • the new timer T3 after it is started, the new timer T3 is not always in the running state, but the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device. When, stop the new timer T3.
  • the terminal By executing the above S2101-S2104, that is, when the terminal responds to the requirement of RRC connection recovery, it starts the T319 timer and sends an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can respond to the data received from the network device.
  • the new timer T3 is started with the downlink information and data transmission is performed during the operation of the new timer T3, which can effectively extend the time that the terminal waits for the RRC response of the RRC connection recovery request message, and flexibly supports multiple data transmissions.
  • the above whole process can be understood as the terminal performing the first extension operation.
  • the device T3 After performing the first extension operation, it can also control and restart the new timer again according to the downlink received from the network device during the start and operation of the new timer T3.
  • the device T3 is used to extend the time for the terminal to wait for the RRC response of the RRC connection recovery request message again.
  • This process can be understood as the terminal performing the second extension operation.
  • the method for the terminal to perform the third extension operation, or the Nth (N greater than 3) extension operation thereafter is similar to the method for the terminal to perform the first extension operation.
  • the new timer T3 can also be restarted according to the downlink information received from the network device during the start and operation of the new timer T3 as an example. For example, after the execution of the above S2104 is based on the slave After the downlink information received by the network device starts the new timer T3, the following S2105-S2107 may be further executed:
  • the terminal sends uplink data to the network device.
  • S2106 The network device sends downlink information to the terminal according to the uplink data.
  • the terminal sends uplink data to the network device during the operation of the new timer T3, and the network device sends downlink information to the terminal according to the uplink data.
  • the terminal sends the downlink information to the terminal during the operation of the new timer T3.
  • the method of restarting the new timer T3 with the received downlink information is the same as in the embodiment shown in FIG. 20, in S2005-S2007, the terminal sends uplink data to the network device during the operation of the T319 timer, and the network device sends the uplink data to the network device according to the uplink data.
  • the terminal sends downlink information.
  • the method for the terminal to restart the T319 timer according to the downlink information received from the network device during the operation of the T319 timer is similar.
  • this application The embodiment will not be repeated.
  • the first extension operation performed through the above S2001-S2004 is itself by restarting the T319 timer to extend the time the terminal waits for the RRC response of the RRC connection recovery request message, therefore, when the second extension operation is performed in the above S2007, it is The T319 timer is restarted for the second time to extend the time that the terminal waits for the RRC response of the RRC connection recovery request message.
  • the difference from the above S2007 is that when the first extension operation is performed through the above S2101-S2104, the new timer T3 is started for the first time to extend the time that the terminal waits for the RRC response of the RRC connection recovery request message. Therefore, when the second extension operation is performed in this S2107, the new timer T3 is restarted for the first time to extend the time that the terminal waits for the RRC response of the RRC connection recovery request message.
  • the new timer T3 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 feedback information, uplink authorization information, downlink resource allocation information, and indication information of newly added fields When any one or more of them, the new timer T3 is restarted, that is, the second extension operation is performed, so that data transmission is performed during the operation of the new timer T3, which can effectively extend the terminal waiting for the RRC response of the RRC connection recovery request message It can flexibly support multiple data transmissions. For details, please refer to the relevant description in the above S2004. Here, the embodiments of the present application will not be repeated here.
  • the new timer T3 is restarted for the first time, it is also not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the new timer T3.
  • the terminal when starting the new timer T3, it is just taken as an example that the terminal can start the new timer T3 according to the downlink information received from the network device while the T319 timer is running.
  • a new timer T3 can also be started according to the data transmission with the network device. For example, during the operation of the T319 timer, if the terminal sends uplink data, the new timer T3 is started. ; Or, if downlink data is received, a new timer T3 is started.
  • the first timer may be a T319 timer configured by the current network
  • the second timer may be a new timer T4 set by the MAC layer. That is, when the terminal responds to the requirement of RRC connection recovery, it first starts the T319 timer and sends an RRC connection recovery request message to the network device; in this way, during the operation of the T319 timer, the terminal can be based on the downlink information received from the network device or according to the For data transmission with the network device, the new timer T4 is started. It should be noted that in this possible implementation manner, during the T319 timer running period, the terminal can start or restart the new timer T4 according to the data transmission with the network device as an example for description.
  • FIG. 22 is a schematic flowchart of still another configuration method provided by an embodiment of the application.
  • the configuration method may include:
  • the terminal starts the T319 timer when responding to the requirement of RRC connection recovery.
  • the terminal Before starting the T319 timer, the terminal first configures the duration of the T319 timer, so that the T319 timer can run based on the configured duration.
  • the method for configuring the duration of the T319 timer is similar to the method for configuring the duration of the T319 timer in S2001 in the foregoing embodiment. For details, please refer to the relevant description of configuring the duration of the T319 timer. Let me repeat it again.
  • an RRC connection recovery request message can be sent to the network device, that is, the following S2202 is performed:
  • the terminal sends an RRC connection recovery request message to the network device.
  • the RRC connection recovery request message may include at least one of the I-RNTI, the identity verification information of the terminal, and the reason value for the UE to initiate the RRC connection recovery request.
  • I-RNTI is used to represent the unique identification of the terminal in the range of an RNA.
  • the identity verification information of the terminal is the identity verification information generated according to the C-RNTI and the RRC integrity key stored by the terminal.
  • the method for the terminal to send the RRC connection recovery request message to the network device is similar to the method for the terminal to send the RRC connection recovery request message to the network device in S2002.
  • the terminal to send an RRC connection recovery request to the network device please refer to the above S2002 for the terminal to send an RRC connection recovery request to the network device.
  • the method for the terminal to send the RRC connection recovery request message to the network device will not be repeated in this embodiment of the application.
  • the terminal may also send to the network device at least one of uplink data, auxiliary information, and indication information that it is expected to remain in the inactive state and continue to send data.
  • the information sending method is similar to the sending method of at least one of the uplink data, auxiliary information, and the indication information that it is expected to remain in the inactive state to continue sending data to the network device in the above S2002.
  • the relevant description of at least one of the data, the auxiliary information, and the instruction information that is expected to remain in the inactive state to continue sending the data, is not repeated here in the embodiment of the present application.
  • the terminal in addition to the T319 timer, there is a new timer T4 set by the MAC layer. Therefore, the terminal can also send a start instruction message to the network device.
  • the start indication information is used to indicate that during the subsequent operation of the T319 timer, if the start condition is met, the new timer T4 is started, thereby realizing synchronization between the new timer T4 started by the terminal and the new timer T3 started by the network device.
  • the network device can send corresponding downlink information to the terminal according to the RRC connection recovery request message, that is, perform the following S2203:
  • S2203 The network device sends downlink information to the terminal according to the RRC connection recovery request message.
  • the method for the network device to send downlink information to the terminal according to the RRC connection recovery request message is similar to the method for the network device to send downlink information to the terminal according to the RRC connection recovery request message in S2103.
  • the terminal starts a new timer T4 according to the data transmission with the network device.
  • the terminal Before starting the new timer T4, the terminal first configures the duration of starting the new timer T4, so that the starting new timer T4 can run 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 new timer according to the information indicating the duration of the new timer T4 included in the broadcast message or the RRC message The duration of T4.
  • the information indicating the duration of the new timer T4 can be obtained through the same broadcast message or RRC message as the information indicating the duration of the T319 timer, or through The acquisition of different broadcast messages or RRC messages can be specifically set according to actual needs.
  • the information indicating the duration of the new timer T4 can be acquired at the same time as the information indicating the duration of the T319 timer, or can be acquired at a different time.
  • the information indicating the duration of the new timer T4 is acquired, which can be specifically set according to actual needs.
  • the duration of the new timer T4 can be the first duration of the T319 timer configured in the current network.
  • the first duration can be ⁇ 100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms ⁇
  • a certain value of can also be greater than a second duration of the T319 timer configured in the current network.
  • the second duration can be configured through a broadcast message or an RRC message.
  • the second duration is ⁇ 100ms, 200ms, 300ms, 400ms, A value in 600ms, 1000ms, 1500ms, 2000ms, 2500ms ⁇ , for example, the second duration can be 2500ms.
  • the new timer T4 Since the new timer T4 is started when the start condition is met, for these two different durations, the time for the terminal to wait for the RRC response message of the RRC connection recovery request can be effectively extended. 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, which is convenient for the terminal network device to perform multiple data transmissions.
  • the new timer T4 since the new timer T4 is started according to the data transmission with the network device, even if the terminal receives
  • the downlink information includes any one or more of feedback information, uplink authorization information, downlink resource allocation information, and newly added field indication information
  • the new timer T4 will not be started, but based on the relationship between the network device and the network device. Data transmission starts a new timer T4.
  • a new timer T4 is started; or, if downlink data is received, such as DTCH
  • the new timer T4 is started to enable data transmission during the operation of the new timer T4, which can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly supports multiple data transmissions.
  • the T319 timer can be stopped.
  • the terminal 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 can also send an instruction message to the network device, and the instruction information is used to instruct the network device The new timer T4 is started, thereby synchronizing the information that the new timer T4 has been started to the network device. Moreover, for the new timer T4, after it is started, the new timer T4 is not always in the running state, but the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device. When, stop the new timer T4.
  • the MAC layer of the terminal After starting the new timer T4, if the timer T4 expires, the MAC layer of the terminal will notify the RRC layer that the timer T4 has expired, and the MAC layer of the terminal will enter the idle state according to the information that the timer T4 has expired.
  • the terminal By executing the above S2201-S2204, when the terminal responds to the RRC connection recovery demand, it starts the T319 timer and sends an RRC connection recovery request message to the network device; during the T319 timer is running, the terminal is based on the data between the network device and the network device.
  • the transmission starts the new timer T4 and performs data transmission during the operation of the new timer T4, which can effectively extend the time that the terminal waits for the RRC response of the RRC connection recovery request message, and flexibly supports multiple data transmissions.
  • the above whole process can be understood as the terminal performing the first extension operation. After performing the first extension operation, it can also control and restart the new timer again according to the data transmission with the network device during the running period of the new timer T4.
  • T4 is to extend the time for the terminal to wait for the RRC response of the RRC connection recovery request message again.
  • This process can be understood as the terminal performing the second extension operation.
  • the method for the terminal to perform the third extension operation or the subsequent Nth (N greater than 3) extension operation is similar to the method for the terminal to perform the first extension operation.
  • the terminal sends uplink data to the network device during the running of the new timer T4.
  • S2206 The network device sends downlink information to the terminal according to the uplink data.
  • the terminal sends uplink data to the network device during the operation of the new timer T4, and the network device sends downlink information to the terminal according to the uplink data, which is the same as in the embodiment shown in FIG. 20, in S2005-S2006 During the operation of the T319 timer, the terminal sends uplink data to the network device.
  • the method for the network device to send downlink information to the terminal according to the uplink data is similar. Refer to the relevant description in the above S2005-S2006. Go ahead and repeat.
  • the terminal restarts the new timer T4 according to the data transmission with the network device.
  • 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, which is the same as that in S2204 during the operation of the new timer T4.
  • the method of starting the new timer T4 for data transmission is similar, and the details are not described in the embodiment of the present application here.
  • the time for the terminal to wait for the RRC response of the RRC connection recovery request message is extended by starting the new timer T4 for the first time, therefore, it is performed in S2207 In the second extension operation, it is the first time to restart the new timer T4 to extend the time that the terminal waits for the RRC response of the RRC connection recovery request message. It is understandable that after the new timer T4 is restarted for the first time, it is also not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the new timer T4.
  • the new timer T4 when the new timer T4 is started, the new timer T4 is only started according to the data transmission with the network device. For example, during the operation of the T319 timer, if the terminal sends uplink data, Then start a new timer T4; or, if downlink data is received, start a new timer T4 as an example for description.
  • the terminal can also start a new timer according to the downlink information received from the network device.
  • the terminal can also start a new timer according to the downlink information received from the network device for details, please refer to the related description of starting a new timer T3 according to the downlink information received from the network device in the first possible implementation manner.
  • the terminal starts the new timer T3 according to the downlink information received from the network device The timer T4 is not described in detail in the embodiment of the present application.
  • the terminal in order to extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, the terminal flexibly supports multiple data transmissions.
  • the first timer can be started first, and the RRC connection recovery request message is sent to the network device through the uplink resource indicated by the configuration authorization information; and during the running of the first timer, the terminal is based on Restarting the first timer or starting the second timer according to the downlink information received by the network device or the data transmission with the network device effectively prolongs the time for the terminal to wait for the RRC connection to resume, thereby flexibly supporting multiple times Sending of data.
  • the RRC connection recovery request message in addition to sending the RRC connection recovery request message to the network device through the uplink resource indicated by the configuration authorization information, the RRC connection recovery request message can also be sent to the network device through the uplink resource in the random access process.
  • the uplink resource can be the PUSCH resource pre-configured for message A (MsgA) in the two-step RACH, or the uplink resource indicated in the random access response received by the terminal in the four-step RACH, which can be specifically based on actual needs. Make settings.
  • the technical solution of restarting the first timer is also applicable
  • the restarted timer is the same timer as the restarted timer when the RRC connection is restored.
  • the terminal responds to the RRC connection recovery demand, it starts the first timer, and when the start condition is met during the running of the first timer, the second timer is started to extend the waiting time of the terminal. The time of the RRC response message of the RRC connection recovery request. It is understandable that in this possible scenario, when the second timer is started, the first timer can also be stopped.
  • the first timer is the T319 timer configured by the current network
  • the terminal transmits the uplink resource in the two-step RACH message A (MsgA) to the network device Send an RRC connection recovery request.
  • MsgA two-step RACH message A
  • the terminal can restart the T319 timer according to the downlink information received from the network device or according to the data transmission with the network device.
  • the terminal can restart the T319 timer according to the downlink information received from the network device as an example for description.
  • FIG. 23 is a schematic flowchart of another configuration method provided by an embodiment of this application.
  • the configuration method may include:
  • the terminal starts the T319 timer when responding to the requirement of RRC connection recovery.
  • the terminal Before starting the T319 timer, the terminal needs to configure the duration of the T319 timer, so that the T319 timer can run based on the configured duration.
  • the configuration method of the T319 timer is similar to the configuration method of the T319 timer in S2001 in the foregoing embodiment. For details, please refer to the relevant description of configuring the duration of the T319 timer. Go into details.
  • the terminal sends a preamble to the network device.
  • the terminal may send a preamble to the network device through a two-step RACH message A (MsgA), and the resource for sending the preamble may be a PRACH resource pre-configured by the network device, and the PRACH resource may be through a broadcast message or a dedicated message (For example, RRC connection release message) configuration.
  • MsgA two-step RACH message A
  • the resource for sending the preamble may be a PRACH resource pre-configured by the network device, and the PRACH resource may be through a broadcast message or a dedicated message (For example, RRC connection release message) configuration.
  • the terminal sends an RRC connection recovery request message to the network device.
  • the RRC connection recovery request message may include at least one of the I-RNTI, the identity verification information of the terminal, and the reason value for the UE to initiate the RRC connection recovery request.
  • I-RNTI is used to indicate the unique identification of the terminal in the range of an RNA.
  • the identity verification information of the terminal is the identity verification information generated according to the C-RNTI and the RRC integrity key stored by the terminal.
  • the terminal When the terminal sends the RRC connection recovery request message to the network device, the difference from the above S2002 is that in this embodiment of the application, the terminal can send the RRC connection recovery request message to the network device through a two-step RACH message A (MsgA).
  • the resource for sending the RRC connection recovery request message may be a PUSCH resource pre-configured by the network device, and the PUSCH resource may be configured through a broadcast message or a dedicated message (for example, an RRC connection release message).
  • the terminal may also send to the network device at least one of uplink data, auxiliary information, and indication information that it is expected to remain in the inactive state and continue to send data.
  • the sending method is similar to the sending method of at least one of the uplink data, auxiliary information, and the indication information that it is expected to remain in the inactive state to continue sending data to the network device in S2002.
  • the sending of uplink data to the network device in S2002 refer to the sending of uplink data to the network device in S2002, The description of at least one information in the auxiliary information and the instruction information that is expected to be kept in the inactive state to continue sending data is not repeated here in the embodiment of the present application.
  • the terminal in addition to sending the RRC connection recovery request message to the network device, the terminal will also send uplink data to the network device as an example to continue to explain the technical solution provided by the embodiment of this application.
  • the network device After receiving the RRC connection recovery request message and uplink data sent by the terminal, the following S2304 is performed:
  • S2304 The network device sends downlink information to the terminal according to the RRC connection recovery request message.
  • the method for the network device to send downlink information to the terminal according to the RRC connection recovery request message is the same as in the embodiment shown in FIG. 20, the S2003 network device sends the downlink information to the terminal according to the RRC connection recovery request message.
  • the method is similar, please refer to the related description in the above S2003, here, the embodiment of the present application will not repeat the description.
  • the method of restarting the T319 timer according to the downlink information received from the network device during the operation of the T319 timer in S2305 is the same as in the embodiment shown in FIG.
  • the method for restarting the T319 timer from the downlink information received by the network device is similar.
  • the S2305 terminal restart the T319 timer according to the downlink information received from the network device during the operation of the T319 timer ? The method of the T319 timer will not be repeated in this embodiment of the application.
  • the difference from S2005 above is that the downlink information does not include feedback information, but may include TC-RNTI.
  • the terminal when the terminal is 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 uplink authorization information, downlink resource allocation information, and newly added information
  • the T319 timer is restarted, so that data transmission is performed during the running of the T319 timer, which can effectively extend the time that the terminal waits for the RRC response message of the RRC connection recovery request, and flexibly Support multiple data sending.
  • the downlink information received by the terminal further includes a timing adjustment command and/or a power control command.
  • the terminal By executing the above S2301-S2305, when the terminal responds to the RRC connection recovery demand, it starts the T319 timer and sends the RRC connection recovery request message to the network device; in this way, during the T319 timer operation period, the terminal can receive according to the request from the network device Restart the T319 timer and perform data transmission during the operation of the T319 timer, which can effectively extend the time for the terminal to wait for the RRC response of the RRC connection recovery request message, and flexibly support multiple data transmissions.
  • the above whole process can be understood as the terminal performing the first extension operation.
  • the T319 timer can also be restarted according to the downlink information received from the network device while the T319 timer is restarted and running.
  • the timer is used to extend the time for the terminal to wait for the RRC response of the RRC connection recovery request message again.
  • This process can be understood as the terminal performing the second extension operation.
  • the method for the terminal to perform the third extension operation or the Nth (N greater than 3) extension operation thereafter is similar to the method for the terminal to perform the first extension operation.
  • the slave network controls the restart of the T319 timer again according to the downlink information received by the device as an example for description. For example, after executing the above S2305 according to the slave After the downlink information received by the network device restarts the T319 timer, the following S2306-S2308 can be further executed:
  • S2306 The terminal sends uplink data to the network device during the operation of the T319 timer.
  • S2307 The network device sends downlink information to the terminal according to the uplink data.
  • the terminal sends uplink data to the network device during the operation of the new timer T319, and the network device sends downlink information to the terminal according to the uplink data.
  • the terminal sends the downlink information to the terminal during the operation of the T319 timer.
  • the method of restarting the T319 timer based on the downlink information is the same as in the embodiment shown in FIG. 20.
  • the terminal sends uplink data to the network device during the operation of the T319 timer, and the network device sends the uplink data to the terminal according to the uplink data.
  • the method for the terminal to restart the T319 timer according to the downlink information received from the network device during the operation of the T319 timer is similar.
  • the embodiment of the present application Do not repeat it here.
  • the terminal when restarting the T319 timer, it is just taken as an example that the terminal can restart the T319 timer according to the downlink information received from the network device during the T319 timer running period.
  • the T319 timer can also be restarted according to data transmission with the network device. For example, during the operation of the T319 timer, if the terminal sends uplink data, for example, DTCH data, the T319 timer is restarted; Or, if downlink data is received, for example, DTCH data, the T319 timer is restarted.
  • the terminal sends an RRC connection recovery request to the network device through a two-step RACH message A (MsgA), and during the operation of the T319 timer, the terminal can be based on the downlink information received from the network device Or according to the data transmission with the network device, restart the technical solution of the T319 timer.
  • the terminal can send 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, and during the operation of the T319 timer, the terminal can according to the downlink information received from the network device or according to the For data transmission with network equipment, restart the T319 timer.
  • the two-step RACH message A sends an RRC connection recovery request to the network device, and the technical solution of restarting the T319 timer during the T319 timer is running.
  • the difference is that the S2303 terminal sends the RRC Before the connection recovery request message, the terminal first receives the random access response sent by the network device.
  • the random access response may include TC-RNTI, uplink authorization, and timing advance commands, so that the terminal can pass the uplink authorization in the random access response.
  • the terminal can also send uplink data and auxiliary information to the network device, as well as to keep in the inactive state to continue.
  • uplink data and auxiliary information For at least one piece of information in the instruction information for sending data, refer to the relevant description in S2303 above.
  • the downlink information sent by the network device to the terminal according to the RRC connection recovery request message no longer includes TC-RNTI, timing adjustment commands, power control commands, contention resolution information, uplink authorization information, and downlink information.
  • At least one of resource allocation information and indication information of newly added fields includes feedback information, timing adjustment commands, power control commands, contention resolution information, uplink authorization information, downlink resource allocation information, and indications of newly added fields At least one of the information; 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 feedback information, uplink authorization information, and downlink When any one or more of the resource allocation information and the indication information of the newly added field are selected, the T319 timer is restarted.
  • the relevant descriptions in S2003 and S2004 in the embodiment shown in FIG. 20.
  • the embodiments of this application will not be repeated.
  • the downlink information received by the terminal further includes a timing adjustment command and/or a power control command.
  • the timing adjustment command is applied to perform uplink transmission timing adjustment
  • the power control command is applied to perform power control.
  • the terminal can also send an indication message to the network device, which is used to instruct the terminal to restart the T319 timer, thereby synchronizing the information that the T319 timer has been restarted To network equipment.
  • the T319 timer after restarting, the T319 timer is not always in the running state, but when the terminal receives the RRC connection recovery message, the RRC connection establishment message, or the RRC connection release message from the network device, Stop the T319 timer.
  • the terminal when the T319 timer is restarted, it is only during the T319 timer running period, the terminal can be based on the downlink information received from the network device, such as uplink authorization information, downlink resource allocation For any one or more of the information and the instruction information of the newly added field, restart the T319 timer as an example for description.
  • the T319 can also be restarted according to the data transmission with the network device.
  • Timer for example, during the operation of the T319 timer, if the terminal sends uplink data, such as DTCH data, restart the T319 timer; or if it receives downlink data, such as DTCH data, restart the T319 timer .
  • uplink data such as DTCH data
  • downlink data such as DTCH data
  • the first timer when the first timer is the T319 timer configured by the current network, the two-step RACH message A (MsgA) is sent to the network.
  • the device sends an RRC connection recovery request, and while the T319 timer is running, the terminal can restart the T319 timer according to the downlink information received from the network device or according to the data transmission with the network device; and the four-step RACH receives
  • the uplink resource indicated in the random access response to the network device sends an RRC connection recovery request to the network device, and during the operation of the T319 timer, the terminal can restart according to the downlink information received from the network device or according to the data transmission with the network device
  • the first timer may also be a new timer additionally set by the RRC layer or a new timer at the MAC layer.
  • the specific implementation manner of controlling the restart of the first timer is similar to the specific implementation manner of controlling the restart of the first timer when the first timer is the T319 timer. Refer to the above-mentioned related description of controlling the restart of the first timer when the first timer is the T319 timer, and details are not described herein again in the embodiment of the present application.
  • a device for implementing any of the above methods.
  • a device is provided that includes a unit (or means) for implementing each step performed by the terminal in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step executed by the network device in any of the above methods.
  • each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • FIG. 24 is a schematic structural diagram of a network device provided by an embodiment of this application. It may be the network device in the above embodiment, and is used to implement the operation of the network device in the above embodiment.
  • the network equipment includes: an antenna 2401, a radio frequency device 2402, and a baseband device 2403.
  • the antenna 2401 is connected to the radio frequency device 2402.
  • the radio frequency device 2402 receives the information sent by the terminal through the antenna 2401, and sends the information sent by the terminal to the baseband device 2403 for processing.
  • the baseband device 2403 processes the terminal information and sends it to the radio frequency device 2402
  • the radio frequency device 2402 processes the terminal information and sends it to the terminal via the antenna 2401.
  • the baseband device 2403 may include one or more processing elements 24031, for example, including a main control CPU and other integrated circuits.
  • the baseband device 2403 may also include a storage element 24032 and an interface 24033.
  • the storage element 24032 is used to store programs and data; the interface 24033 is used to exchange information with the radio frequency device 2402.
  • the interface is, for example, a common public radio interface. , CPRI).
  • the above apparatus for network equipment may be located in the baseband device 2403.
  • the above apparatus for network equipment may be a chip on the baseband device 2403.
  • the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute the above network.
  • the interface circuit is used to communicate with other devices.
  • the unit for the network device to implement each step in the above method can be implemented in the form of a processing element scheduler.
  • the device for the network device includes a processing element and a storage element, and the processing element calls the program stored by the storage element to Perform the method performed by the network device in the above method embodiment.
  • the storage element may be a storage element with the processing element on the same chip, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • the unit of the network device that implements each step in the above method may be configured as one or more processing elements, and these processing elements are arranged on the baseband device.
  • the processing elements here may be integrated circuits, such as one Or multiple ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the units for the network equipment to implement each step in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the baseband device includes the SOC chip for implementing the above method.
  • At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above network device; or, at least one integrated circuit can be integrated in the chip to implement the above network The method executed by the device; or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above apparatus for a network device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any method performed by the network device provided in the above method embodiments.
  • the processing element can execute part or all of the steps executed by the network device in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps performed by the network device are executed in the method; of course, part or all of the steps executed by the network device above can also be executed in combination with the first method and the second method.
  • the processing element here is the same as the above description, and it may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • a general-purpose processor such as a CPU
  • integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element can be a memory or a collective term for multiple storage elements.
  • FIG. 25 is a schematic structural diagram of another network device provided by an embodiment of this application. It may be the network device in the above embodiment, and is used to implement the operation of the network device in the above embodiment. As shown in FIG. 25, the network device includes: a processor 2501, a memory 2502, and an interface 2503, and the processor 2501, a memory 2502, and the interface 2503 are connected in signal.
  • the above configuration device is located in the network device, and the functions of each unit can be implemented by the processor 2501 calling a program stored in the memory 2502. That is, the above configuration device includes a memory and a processor, and the memory is used to store a program, and the program is called by the processor to execute the method in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU. Or the functions of the above units may be realized by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • FIG. 26 is a schematic structural diagram of a terminal provided by an embodiment of this application. It may be the terminal in the above embodiment, and is used to implement the operation of the terminal in the above embodiment.
  • the terminal includes an antenna 2601, a radio frequency part 2602, and a signal processing part 2603.
  • the antenna 2601 is connected to the radio frequency part 2602.
  • the radio frequency part 2602 receives the information sent by the network device through the antenna 2601, and sends the information sent by the network device to the signal processing part 2603 for processing.
  • the signal processing part 2603 processes the terminal information and sends it to the radio frequency part 2602.
  • the radio frequency part 2602 processes the terminal information and sends it to the network device via the antenna 2601.
  • the signal processing part 2603 may include a modem subsystem, which is used to process the various communication protocol layers of the data; it may also include a central processing subsystem, which is used to process the terminal operating system and the application layer; in addition, it may also include Other subsystems, such as multimedia subsystems, peripheral subsystems, etc., where the multimedia subsystem is used to control the terminal camera, screen display, etc., and the peripheral subsystem is used to realize the connection with other devices.
  • the modem subsystem can be a separate chip.
  • the above apparatus for the terminal may be located in the modem subsystem.
  • the modem subsystem may include one or more processing elements, for example, a master control and other integrated circuits.
  • the modem subsystem may also include storage elements and interface circuits.
  • the storage element is used to store data and programs, but the program used to execute the method executed by the terminal in the above method may not be stored in the storage element, but stored in a memory outside the modem subsystem.
  • the demodulation subsystem is loaded and used.
  • the interface circuit is used to communicate with other subsystems.
  • the above device for the terminal may be located in the modem subsystem, which may be implemented by a chip, the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute any of the methods performed by the above terminal In each step, the interface circuit is used to communicate with other devices.
  • the unit for the terminal to implement each step in the above method can be implemented in the form of a processing element scheduler.
  • the device for the terminal includes a processing element and a storage element, and the processing element calls the program stored by the storage element to execute the above The method executed by the terminal in the method embodiment.
  • the storage element may be a storage element whose processing element is on the same chip, that is, an on-chip storage element.
  • the program used to execute the method executed by the terminal in the above method may be a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • 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.
  • the terminal that implements each step in the above method may be configured as one or more processing elements, and these processing elements are arranged on the modem subsystem, where the processing elements may be integrated circuits, such as : 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 can be integrated together to form a chip.
  • the units for the terminal to implement each step in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC), and the SOC chip is used to implement the above method.
  • SOC system-on-a-chip
  • At least one processing element and storage element can be integrated in the chip, and the above terminal execution method can be implemented by the processing element calling the stored program of the storage element; or, at least one integrated circuit can be integrated in the chip for realizing the above terminal execution Or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above apparatus for a terminal may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any of the methods performed by the terminal provided in the above method embodiments.
  • the processing element can execute part or all of the steps executed by the terminal in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps executed by the terminal are executed in a manner; of course, part or all of the steps executed by the terminal may be executed by combining the first manner and the second manner.
  • the processing element here is the same as the above description, and it may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • a general-purpose processor such as a CPU
  • integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element can be a memory or a collective term for multiple storage elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种配置方法和装置，网络设备在通过RRC连接释放消息指示终端由连接态进入非激活态的同时，可以在该RRC连接释放消息中携带为非激活态的终端分配的配置参数，即终端接收网络设备发送的无线资源控制RRC连接释放消息，该RRC连接释放消息包括用于指示目标配置参数的第一信息；这样终端就可以根据RRC连接释放消息进入非激活态，且根据第一信息确定非激活态的上下文参数，其中，非激活态的上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数，该目标配置参数为适合非激活态的终端的配置参数，从而实现了合理地为处于非激活态的终端分配配置参数。

Description

配置方法和装置
本申请要求于2019年09月30日提交中国专利局、申请号为PCT/CN2019/109722、申请名称为“配置方法和装置”的国际专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种配置方法和装置。
背景技术
在LTE网络中，从接入网的角度看，终端的状态可以分为三种，这种状态分别为连接(connected)态、非激活(inactive)态(又称去激活态)和空闲(idle)态。其中，连接态为终端通过无线资源控制(radio resource control，RRC)连接建立，RRC连接重建立，RRC连接恢复等过程与接入网设备以及核心网设备之间完成了连接建立的状态；非激活态为终端与接入网设备断开了连接，但接入网设备保持与核心网设备的连接，且接入网设备保存了终端的上下文(例如终端的标识)的状态；空闲态为终端断开了与接入网设备和核心网设备的连接，且接入网设备释放了终端的上下文的状态。
对于处于连接态的终端，网络设备会为该处于连接态的终端发送配置信息，以使终端根据该配置信息进行配置，进而终端基于配置进行数据传输。网络设备若检测到该终端长时间没有数据传输后，会向该终端发送RRC连接释放消息，以通过该RRC连接释放消息指示该终端由连接态进入非激活态。终端进入非激活态之后，其处于连接态时接收到的配置信息将不再适应于当前处于非激活态的终端。
因此，如何合理地为处于非激活态的终端指示配置参数，是本领域技术人员亟待解决的问题。
发明内容
本申请实施例提供一种配置方法和装置，在终端由连接态进入至非激活态后，实现了合理地为处于非激活态的终端指示配置参数。
第一方面，本申请实施例提供一种配置方法，该配置方法可以包括：接收无线资源控制RRC连接释放消息，RRC连接释放消息包括第一信息，第一信息用于指示目标配置参数；并根据RRC连接释放消息进入非激活态，且根据第一信息确定非激活态的上下文参数，其中，非激活态的上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数。
此外，还提供一种配置装置，包括用于执行以上第一方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第一方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第一方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第一方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第一方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第一方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第一方面中，网络设备在通过RRC连接释放消息指示终端由连接态进入非激活态的同时，可以在该RRC连接释放消息中携带为非激活态的终端分配的配置参数，即终端接收网络设备发送的无线资源控制RRC连接释放消息，该RRC连接释放消息包括用于指示目标配置参数的第一信息；这样终端就可以根据RRC连接释放消息进入非激活态，且根据第一信息确定非激活态的接入层上下文参数，其中，非激活态的接入层上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数，从而实现了合理地为处于非激活态的终端指示配置参数。
可以理解的是，在本申请实施例中，网络设备在通过第一信息合理地为非激活态的终端指示配置参数时，可以分为两种不同的场景。在一种场景中，网络设备可以通过第一信息指示为非激活态的终端配置的配置参数，以使终端保留为其配置的配置参数。在另一种场景中，网络设备可以通过第一信息指示非激活态的终端需要释放的配置参数，以使非激活态的终端释放掉需要释放的配置参数。在这两种不同的场景中，第一信息指示的目标配置参数是不同的。
在上述第一方面中，在一种可能的实现方式中，目标配置参数包括：无线承载配置参数，和/或，小区组配置参数，网络设备通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样当多个终端由连接态进入非激活态时，对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。
在上述第一方面中，在一种可能的实现方式中，第一信息为目标配置参数对应的标识。
在上述第一方面中，在一种可能的实现方式中，终端存储有配置参数对应的标识和配置参数的映射关系，使得终端可以根据目标配置参数对应的标识，及映射关系确定非激活态的上下文参数包括标识对应的目标配置参数，从而保留或者释放该目标配置参数。
在上述第一方面中，在一种可能的实现方式中，第一信息包括目标配置参数，由于RRC连接释放消息中直接携带的是目标配置参数，使得终端可以直接确定目标配置参数，并保留或者释放RRC释放连接消息中直接携带的目标配置参数，虽然将目标配置参数携带在RRC连接释放消息中发送给终端，会使得配置信令开销较大，但对于终端而言，无需在协议中预先定义上下文配置的信息，从而减少协议的复杂，终端不必预先存储预配置，降低 了终端的存储开销的配置开销。
在上述第一方面中，在一种可能的实现方式中，上述配置方法还包括：上报终端的非激活态的能力信息，以使网络设备根据终端上报的能力信息确定该终端是否支持在非激活态下进行数据传输。
示例的，终端在上报其能力信息时，可以通过至少四种可能的方式向网络设备上报其能力信息。以终端支持在非激活态下进行数据传输为例，该四种可能的方式分别为：终端能支持非激活态下的数据传输、终端支持通过预配置标识配置终端的上下文参数、终端支持非激活态下的公共的参数配置(换言之，终端支持轻量级的接入层配置参数)、终端支持直接非激活态下的数据传输的会话。虽然表达方式不同，但是通过该四种不同的方式均可以指示终端支持非激活态下的数据传输。
在上述第一方面中，在一种可能的实现方式中，接收第一指示，第一指示用于指示终端在非激活态时监听物理下行控制信道。
在上述第一方面中，在一种可能的实现方式中，第一指示信息包括在RRC释放消息中，当然，也可以携带在其它消息中，具体可以根据实际需要进行设置。
在上述第一方面中，在一种可能的实现方式中，终端还可以接收第二指示，第二指示用于指示终端在非激活态时允许进行上行传输。
在上述第一方面中，在一种可能的实现方式中，终端可以发送随机接入请求；并接收随机接入请求的响应消息，响应消息包括上行授权和第二指示，第二指示用于指示在非激活态时允许在上行授权上进行上行传输，这样当终端需要进行数据传输时，可以直接在上行授权指示的上行资源上进行上行传输，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，避免终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
第二方面，本申请实施例还提供一种配置方法，该配置方法可以包括：确定目标配置参数；并发送无线资源控制RRC连接释放消息，RRC连接释放消息包括第一信息，第一信息用于指示目标配置参数，RRC连接释放消息用于指示终端根据RRC连接释放消息进入非激活态，第一信息用于指示终端确定非激活态的上下文参数，其中，非激活态的上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数。
此外，还提供一种配置装置，包括用于执行以上第二方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第二方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第二方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第二方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第二方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第二方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第二方面中，网络设备在通过RRC连接释放消息指示终端由连接态进入非激活态的同时，可以在该RRC连接释放消息中携带为非激活态的终端分配的配置参数，即终端接收网络设备发送的无线资源控制RRC连接释放消息，该RRC连接释放消息包括用于指示目标配置参数的第一信息；这样终端就可以根据RRC连接释放消息进入非激活态，且根据第一信息确定非激活态的上下文参数，其中，非激活态的上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数，从而实现了合理地为处于非激活态的终端指示配置参数。
在上述第二方面中，在一种可能的实现方式中，目标配置参数包括：无线承载配置参数，和/或，小区组配置参数，网络设备通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样当多个终端由连接态进入非激活态时，对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。
在上述第二方面中，在一种可能的实现方式中，第一信息为目标配置参数对应的标识。
在上述第二方面中，在一种可能的实现方式中，发送配置参数对应的标识和配置参数的映射关系，使得终端可以根据目标配置参数对应的标识，及映射关系确定非激活态的上下文参数包括标识对应的目标配置参数，从而保留或者释放该目标配置参数。
在上述第二方面中，在一种可能的实现方式中，第一信息包括目标配置参数，由于RRC连接释放消息中直接携带的是目标配置参数，使得终端可以直接确定目标配置参数，并保留或者释放该目标配置参数，虽然将目标配置参数携带在RRC连接释放消息中发送给终端，会使得配置信令开销较大，但对于终端而言，无需在协议中预先定义上下文配置的信息，从而减少协议的复杂，终端不必预先存储预配置，降低了终端的存储开销的配置开销。
在上述第二方面中，在一种可能的实现方式中，接收来自核心网设备的会话建立请求，会话建立请求中包括会话类型，会话类型用于指示终端在非激活态时允许进行上行传输；基于会话类型，确定目标配置参数，从而将确定好的目标配置参数发送给终端。
在上述第二方面中，在一种可能的实现方式中，网络设备还向核心网设备发送会话建立响应。
在上述第二方面中，在一种可能的实现方式中，发送第一指示，第一指示用于指示终端在非激活态时监听物理下行控制信道。
在上述第二方面中，在一种可能的实现方式中，第一指示信息包括在RRC释放消息中，当然，也可以携带在其它消息中，具体可以根据实际需要进行设置。
在上述第二方面中，在一种可能的实现方式中，发送第二指示，第二指示用于指示终端在非激活态时允许进行上行传输。
在上述第二方面中，在一种可能的实现方式中，网络设备可以接收随机接入请求；并发送随机接入请求的响应消息，响应消息包括上行授权和第二指示，第二指示用于指示在非激活态时允许在上行授权上进行上行传输，这样当终端需要进行数据传输时，可以直接在上行授权指示的上行资源上进行上行传输，实现了终端在非激活态时完成上行传输，而 无需等到恢复RRC连接之后才能进行上行传输，避免终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
第三方面，本申请实施例还提供一种配置方法，该配置方法可以包括：
向网络设备发送第一消息，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据包括用于请求恢复RRC连接的信息；并从网络设备接收第一消息的响应消息，响应消息包括竞争解决信息；从网络设备接收上行授权；再在上行授权指示的上行资源上进行上行传输。
此外，还提供一种配置装置，包括用于执行以上第三方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第三方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第三方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第三方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第三方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第三方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第三方面中，终端在接收到竞争解决信息后，若此时还未接收到RRC连接释放消息，说明还有数据需要传输，则从网络设备接收上行授权，并在该上行授权指示的上行资源上进行上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第三方面中，在一种可能的实现方式中，在接收到第一消息的响应消息时，启动或重启定时器，从而延迟终端监听授权的时长。
在上述第三方面中，在一种可能的实现方式中，在定时器运行期间，从网络设备接收上行授权；并在接收到上行授权时，重启定时器，从而延迟终端监听上行授权的时长。
在上述第三方面中，在一种可能的实现方式中，在定时器运行期间，从网络设备接收下行授权；在接收到下行授权时，重启定时器，从而延迟终端监听下行授权的时长。
在上述第三方面中，在一种可能的实现方式中，定时器在启动或者重启之后，不是一直处于运行状态，而是在满足一定条件下停止定时器，例如以上描述的停止定时器的场景。例如，当终端从网络设备接收RRC连接释放消息时，控制定时器停止运行，即停止定时器。可以理解，当终端从网络设备接收RRC连接恢复、连接建立消息等，终端也可以停止定时器。
第四方面，本申请实施例还提供一种配置方法，该配置方法可以包括：从终端接收第一消息，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据 包括用于请求恢复RRC连接的信息；并向终端发送第一消息的响应消息，响应消息包括竞争解决信息；向终端发送上行授权；在上行授权指示的上行资源上进行数据传输。
此外，还提供一种配置装置，包括用于执行以上第四方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第四方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第四方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第四方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第四方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第四方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第四方面中，网络设备在接收到终端发送的第一消息后，向终端发送包括竞争解决信息的响应消息，若此时还未向终端发送RRC连接释放消息，说明还有数据需要传输，则向终端发送上行授权，使得终端在该上行授权指示的上行资源上进行上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第四方面中，在一种可能的实现方式中，网络设备还向终端发送无线资源控制RRC连接释放消息，以使终端从网络设备接收无线资源控制RRC连接释放消息时，控制定时器停止运行，即停止定时器。可以理解，当终端从网络设备接收无线资源控制RRC连接恢复、连接建立消息等，终端也可以停止定时器。
第五方面，本申请实施例还提供一种配置方法，该配置方法可以包括：向网络设备发送第一消息，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据包括用于请求恢复无线资源控制RRC连接的信息；并从网络设备接收第一消息的响应消息，响应消息包括上行授权和第一指示信息，第一指示信息用于指示是否允许在上行授权指示的上行资源上进行上行传输；根据第一指示信息在上行资源上进行上行传输。
此外，还提供一种配置装置，包括用于执行以上第五方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第五方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第五方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第五方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第五方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第五方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第五方面中，终端通过向网络设备发送RRC连接恢复请求，使得网络设备可以在终端处于非激活态时，为该终端分配上行授权，并通过指示信息指示是否允许在上行授权指示的上行资源上进行上行传输，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第五方面中，在一种可能的实现方式中，若第一指示信息指示允许在上行资源上进行上行传输，则在上行资源上向网络设备发送包括上行数据的第二消息，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第五方面中，在一种可能的实现方式中，若第一指示信息指示不允许在上行资源上进行上行传输，则在上行资源上向网络设备发送第三消息，其中，第三消息用于请求恢复RRC连接。
需要注意的是，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行传输时，终端在上行授权指示的上行资源上发送的第三消息只用于请求恢复RRC连接，并不包括上行数据。示例的，该第三消息可以为RRC连接恢复请求。
在上述第五方面中，在一种可能的实现方式中，终端在接收到第一消息的响应消息时，启动或重启定时器，从而延迟终端监听授权的时长。
在上述第五方面中，在一种可能的实现方式中，在定时器运行期间，从网络设备接收授权；并在接收到授权时，重启定时器，从而延迟终端监听授权的时长。
在上述第五方面中，在一种可能的实现方式中，定时器在启动或者重启之后，不是一直处于运行状态，而是在满足一定条件下停止定时器，例如以上描述的停止定时器的场景。例如，当终端从网络设备接收到该RRC连接释放消息时，控制定时器停止运行，即停止定时器。可以理解，当终端从网络设备接收无线资源控制RRC连接恢复、连接建立消息等，终端也可以停止定时器。
在上述第五方面中，在一种可能的实现方式中，响应消息包括竞争解决信息。示例的，竞争解决信息可以为终端的标识，或者第二消息的部分信息、或者第三消息的部分信息。
终端在接收到竞争解决信息后，若此时还未接收到RRC连接释放消息，则终端启动或重启定时器，并在定时器运行期间，从网络设备接收授权；该授权可以为上行授权或者下行授权，并在接收到该授权时，重启定时器，从而延迟终端监听授权的时长。示例的，若从网络设备接收到的是上行授权，则终端启动或者重启定时器，并在该上行授权指示的上行资源上进行上行传输；若从网络设备接收到的是下行授权，且未接收到RRC连接释放消息，说明还有数据需要传输，则终端启动或重启定时器，等待RRC连接释放消息的时间，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行 上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第五方面中，在一种可能的实现方式中，第一消息还包括第二指示信息，第二指示信息用于指示终端的待发送数据量与数据量门限的比较结果。
第六方面，本申请实施例还提供一种配置方法，该配置方法可以包括：从终端接收第一消息，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据包括用于请求恢复无线资源控制RRC连接的信息；并向终端发送第一消息的响应消息，响应消息包括上行授权和第一指示信息，第一指示信息用于指示是否允许在上行授权指示的上行资源上进行上行传输；根据第一指示信息在上行资源上进行上行传输。
此外，还提供一种配置装置，包括用于执行以上第六方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第六方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第六方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第六方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第六方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第六方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第六方面中，网络设备通过接收终端发送的RRC连接恢复请求，在终端处于非激活态时，为该终端分配上行授权，并通过指示信息指示是否允许在上行授权指示的上行资源上进行上行传输，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第六方面中，在一种可能的实现方式中，若第一指示信息指示允许在上行资源上进行上行传输，则在上行资源上从终端接收包括上行数据的第二消息，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
在上述第六方面中，在一种可能的实现方式中，若第一指示信息指示不允许在上行资源上进行上行传输，则在上行资源上从终端接收第三消息，其中，第三消息用于请求恢复RRC连接。
需要注意的是，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行传输时，网络设备在上行授权指示的上行资源上接收的第三消息只用于请求恢复RRC连接，并不包括上行数据。示例的，该第三消息可以为RRC连接恢复请求。
在上述第六方面中，在一种可能的实现方式中，向终端发送无线资源控制RRC连接 释放消息，这样当终端从网络设备接收到该RRC连接释放消息时，控制定时器停止运行，即停止定时器。可以理解，当终端从网络设备接收无线资源控制RRC连接恢复、连接建立消息等，终端也可以停止定时器。
在上述第六方面中，在一种可能的实现方式中，响应消息包括竞争解决信息。示例的，竞争解决信息可以为终端的标识，或者第二消息的部分信息、或者第三消息的部分信息。
在上述第六方面中，在一种可能的实现方式中，第一消息还包括第二指示信息，第二指示信息用于指示终端的待发送数据量与数据量门限的比较结果。
第七方面，本申请实施例还提供一种配置方法，该配置方法可以包括：接收指示信息，指示信息用于指示终端在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；并根据指示信息监听C-RNTI加扰的PDCCH。
此外，还提供一种配置装置，包括用于执行以上第七方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第七方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第七方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第七方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第七方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第七方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第七方面中，终端通过接收网络设备发送的指示信息，该指示信息指示终端在非激活态时监听C-RNTI加扰的PDCCH，并在监听C-RNTI加扰的PDCCH的过程中接收下行数据，该整个接收过程对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
在上述第七方面中，在一种可能的实现方式中，终端可以接收无线资源控制RRC连接释放消息，RRC连接释放消息包括指示信息，从而获取到该指示信息。可以理解的是，该指示信息也可以携带在广播消息中。
示例的，该指示信息可以通过一个比特实现，例如，该比特取值为1，表示启用在非激活态时监听C-RNTI加扰的物理下行控制信道(PDCCH)的功能，该比特取值为0，表示不启用在非激活态时监听C-RNTI加扰的物理下行控制信道(PDCCH)的功能。或者，该指示信息也可以通过枚举型实现，例如：{TURE}，{downlink reception}。由于PDCCH通过小区无线网络临时标识(C-RNTI)加扰，故在另一种实现中，该指示信息可以为C-RNTI，例如，当RRC连接释放消息中携带C-RNTI时，则指示终端在非激活态监听该C-RNTI加扰的PDCCH；当RRC连接释放消息中未携带C-RNTI时，则指示终端在非激 活态不监听PDCCH。
在上述第七方面中，在一种可能的实现方式中，终端监听C-RNTI加扰的PDCCH，可以包括：确定寻呼时机，在寻呼时机的部分时隙或部分寻呼帧监听C-RNTI加扰的PDCCH，这样对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
在上述第七方面中，在一种可能的实现方式中，终端监听C-RNTI加扰的PDCCH，可以包括：接收第一参数，根据第一参数确定寻呼时机；并接收第二参数，根据第二参数确定监听C-RNTI加扰的PDCCH的时机，其中寻呼时机和监听C-RNTI加扰的PDCCH的时机不同，这样对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
在上述第七方面中，在一种可能的实现方式中，在终端移出C-RNTI的有效区域时，停止监听C-RNTI加扰的PDCCH，从而降低了终端的电量消耗。
第八方面，本申请实施例还提供一种配置方法，该配置方法可以包括：确定终端可在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；并向终端发送指示信息，指示信息用于指示终端在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH。
此外，还提供一种配置装置，包括用于执行以上第八方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第八方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第八方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第八方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第八方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第八方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，本申请实施例中，网络设备通过向终端发送指示信息，以通过指示信息指示终端在非激活态时监听C-RNTI加扰的PDCCH，这样终端可以在监听C-RNTI加扰的PDCCH的过程中接收下行数据，该整个接收过程对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
在上述第八方面中，在一种可能的实现方式中，网络设备可以向终端发送无线资源控制RRC连接释放消息，RRC连接释放消息包括指示信息，以使终端获取到该指示信息。可以理解的是，该指示信息也可以携带在广播消息中。
在上述第八方面中，在一种可能的实现方式中，网络设备可以向终端发送第一参数， 第一参数用于终端根据第一参数确定寻呼时机；并向终端发送第二参数，第二参数用于终端根据第二参数确定监听C-RNTI加扰的PDCCH的时机，其中寻呼时机和监听C-RNTI加扰的PDCCH的时机不同，这样对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
第九方面，本申请实施例还提供一种配置方法，该配置方法可以包括：终端应无线资源控制RRC连接恢复的需求，启动第一定时器，且向网络设备发送RRC连接恢复请求消息；终端在第一定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启第一定时器或启动第二定时器。
此外，还提供一种配置装置，包括用于执行以上第九方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第九方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第九方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第九方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第九方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第九方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第九方面中，终端根据从网络设备接收到的下行信息或与终端进行数据传输重启第一定时器或者启动第二定时器，这样终端可以在第一定时器或者第二定时器运行期间进行数据传输，可以有效地延长了终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。
本申请实施例提供的配置方法可以包括至少两种可能的场景。在一种可能的场景中，终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足重启条件，重启该第一定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以看出，在该种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器为同一个定时器，均为第一定时器。在另一种可能的场景中，终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足启动条件时，启动第二定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以看出，在该种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器不是一个定时器，而是额外设置的一个新的定时器。可以理解的是，在该种可能的场景中，在启动第二定时器之后，还可以停止第一定时器；当然，也可以先停止第一定时器，接着启动第二定时器，或者在启动第二定时器的同时，停止第一定时器。如此，用第二定时器接替第一定时器工作，以延长终端等待RRC连接恢 复请求的RRC响应消息的时间。
在上述第九方面中，在一种可能的实现方式中，终端向网络设备发送上行数据，上行数据与RRC连接恢复请求消息共同发送或独立发送，其中，下行信息包括上行数据的反馈信息，上行数据的反馈信息用于指示上行数据是否成功传输。
本申请中的共同发送或者独立发送是指上行数据与RRC连接恢复请求消息是否通过同一个消息，例如MAC PDU消息发送，若上行数据与RRC连接恢复请求消息通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息共同发送；相反的，上行数据与RRC连接恢复请求消息不是通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息独立发送。此外，若上行数据与RRC连接恢复请求消息独立发送，则可以在在RRC连接恢复请求消息发送之后，在第一定时器运行期间内发送该上行数据。
在上述第九方面中，在一种可能的实现方式中，下行信息包括竞争解决信息，若竞争解决信息为竞争解决成功，则说明RRC连接恢复请求消息发送成功，终端可以继续在预配授权上进行新的上行数据的发送；相反的，若竞争解决信息为竞争解决失败，则说明RRC连接恢复请求消息发送失败，终端可以继续在预配授权上进行RRC连接恢复请求消息的重传。
在上述第九方面中，在一种可能的实现方式中，下行信息包括上行授权信息，该上行授权信息指示的上行资源可以用于原上行数据的重传，也可以用于新上行数据的初传，实现连续多次包的数据传输。通常情况下，若有原上行数据需要重传，且有新上行数据需要初传，则可以先通过该上行授权信息指示的上行资源进行新上行数据的初传，即数据初传的传输优先级高于数据重传的传输优先级。
在上述第九方面中，在一种可能的实现方式中，终端利用上行授权信息指示的上行资源发送上行数据。
在上述第九方面中，在一种可能的实现方式中，下行信息包括下行资源分配信息，该下行资源分配信息指示的下行资源可以用于原下行数据的重传，也可以用于新下行数据的初传，实现下行数据早传。
在本申请实施例中，上行授权信息和下行资源分配信息可以独立存在，即终端接收到的下行信息中可以包括上行授权信息，或者下行资源分配信息；上行授权信息和下行资源分配信息可以同时存在，互相结合，即终端接收到的下行信息中可以同时包括上行授权信息和下行资源分配信息。
在上述第九方面中，在一种可能的实现方式中，终端在下行资源分配信息所指示的下行资源上接收下行数据。
在上述第九方面中，在一种可能的实现方式中，下行信息包括指示信息，指示信息用于指示终端重启第一定时器，这样终端在接收到包括该指示信息的信息后，可以重启该第一定时器，使得在第一定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。
在上述第九方面中，在一种可能的实现方式中，终端从网络设备接收广播消息或RRC消息，广播消息或RRC消息包括第一定时器的信息，第一定时器的信息用于指示第一定时器的时长，这样终端可以根据该第一定时器的信息，对第一定时器的时长进行配置。
在上述第九方面中，在一种可能的实现方式中，第一定时器为T319定时器。
在上述第九方面中，在一种可能的实现方式中，第一定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且终端在第一定时器运行期间，应从网络设备接收到的下行信息或应与网络设备之间的数据传输，重启第一定时器；或者，
第一定时器为T319定时器，且第二定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且终端在第一定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动或重启第二定时器。
在上述第九方面中，在一种可能的实现方式中，终端向网络设备发送指示信息，指示信息用于指示网络设备启动的第一定时器或第二定时器，从而将已经当前启动的定时器的信息同步给网络设备。
在上述第九方面中，在一种可能的实现方式中，当终端启动第二定时器时，停止第一定时器，这样可以减少因第一定时器处于运行状态产生的功耗。
在上述第九方面中，在一种可能的实现方式中，终端从网络设备接收RRC连接恢复、RRC连接建立、或RRC连接释放消息时，停止第一定时器或第二定时器。
第十方面，本申请实施例还提供一种配置方法，该配置方法可以包括：从终端接收无线资源控制RRC连接恢复请求消息，RRC连接恢复请求消息是终端应无线资源控制RRC连接恢复的需求，启动第一定时器后发送的；在第一定时器运行期间，向终端发送下行信息或与终端进行数据传输，用于指示根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启第一定时器或启动第二定时器。
此外，还提供一种配置装置，包括用于执行以上第十方面各个步骤的单元或手段(means)。
此外，提供一种配置装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上第十方面提供的方法。该处理器包括一个或多个。
此外，提供一种配置装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行以上第十方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种配置装置，包括至少一个处理器和至少一个存储器，至少一个处理器用于执行以上第十方面提供的方法。
此外，提供一种计算机程序，该计算机程序程序在被处理器执行时用于执行以上第十方面的方法。
此外，提供一种计算机可读存储介质，所述计算机可读存储介质存储程序，所述程序被处理器调用时，执行以上第十方面的方法。
此外，提供一种程序产品，例如计算机可读存储介质，包括以上程序。
可见，在上述第十方面中，网络设备通过向终端发送下行信息或与终端进行数据传输，使得终端可以根据从网络设备接收到的下行信息或与终端进行数据传输重启第一定时器或者启动第二定时器，这样终端可以在第一定时器或者第二定时器运行期间进行数据传输，可以有效地延长了终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。
在上述第十方面中，在一种可能的实现方式中，从终端接收上行数据，上行数据与RRC连接恢复请求消息共同发送或独立发送，其中，下行信息包括上行数据的反馈信息，上行 数据的反馈信息用于指示上行数据是否成功传输。
本申请中的共同发送或者独立发送是指上行数据与RRC连接恢复请求消息是否通过同一个消息，例如MAC PDU消息发送，若上行数据与RRC连接恢复请求消息通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息共同发送；相反的，上行数据与RRC连接恢复请求消息不是通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息独立发送。此外，若上行数据与RRC连接恢复请求消息独立发送，则可以在在RRC连接恢复请求消息发送之后，在第一定时器运行期间内发送该上行数据。
在上述第十方面中，在一种可能的实现方式中，下行信息包括竞争解决信息，若竞争解决信息为竞争解决成功，则说明RRC连接恢复请求消息发送成功，终端可以继续在预配授权上进行新的上行数据的发送；相反的，若竞争解决信息为竞争解决失败，则说明RRC连接恢复请求消息发送失败，终端可以继续在预配授权上进行RRC连接恢复请求消息的重传。
在上述第十方面中，在一种可能的实现方式中，下行信息包括上行授权信息，该上行授权信息指示的上行资源可以用于原上行数据的重传，也可以用于新上行数据的初传，实现连续多次包的数据传输。通常情况下，若有原上行数据需要重传，且有新上行数据需要初传，则可以先通过该上行授权信息指示的上行资源进行新上行数据的初传，即数据初传的传输优先级高于数据重传的传输优先级。
在上述第十方面中，在一种可能的实现方式中，从终端接收利用上行授权信息指示的上行资源发送的上行数据。
在上述第十方面中，在一种可能的实现方式中，下行信息包括下行资源分配信息，该下行资源分配信息指示的下行资源可以用于原下行数据的重传，也可以用于新下行数据的初传，实现下行数据早传。
在本申请实施例中，上行授权信息和下行资源分配信息可以独立存在，即终端接收到的下行信息中可以包括上行授权信息，或者下行资源分配信息；上行授权信息和下行资源分配信息可以同时存在，互相结合，即终端接收到的下行信息中可以同时包括上行授权信息和下行资源分配信息。
在上述第十方面中，在一种可能的实现方式中，在下行资源分配信息所指示的下行资源上向终端发送下行数据。
在上述第十方面中，在一种可能的实现方式中，下行信息包括指示信息，指示信息用于指示终端重启第一定时器，这样终端在接收到包括该指示信息的信息后，可以重启该第一定时器，使得在第一定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。
在上述第十方面中，在一种可能的实现方式中，向终端发送广播消息或RRC消息，广播消息或RRC消息包括第一定时器的信息，第一定时器的信息用于指示第一定时器的时长，这样终端可以根据该第一定时器的信息，对第一定时器的时长进行配置。
在上述第十方面中，在一种可能的实现方式中，第一定时器为T319定时器。
在上述第十方面中，在一种可能的实现方式中，第一定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且第一定时器是终端在第一定时器运行期间，应从网络设备接收到的下行信息或应与网络设备之间的数据传输重启的；或者，
第一定时器为T319定时器，且第二定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且第二定时器是终端在第一定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动或重启的。
在上述第十方面中，在一种可能的实现方式中，从终端接收指示信息，指示信息用于指示网络设备启动的第一定时器或第二定时器，从而将已经当前启动的定时器的信息同步给网络设备。
可以理解的是，以上各方面所示的装置可以是一个芯片，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
以上处理器为一个或多个，存储器为一个或多个。
存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
以上信息传输或接收过程例如发送随机接入请求，可以为从处理器输出随机接入请求的过程，接收随机接入请求的响应消息，可以为从处理器接收输入随机接入请求的响应消息的过程。具体地，处理器输出的随机接入请求可以输出给发射器，处理器接收的输入随机接入请求的响应消息可以来自接收器。其中，发射器和接收器可以统称为收发器。
附图说明
图1为本申请实施例提供的一种应用场景示意图；
图2为本申请实施例提供的一种网络架构的示意图；
图3为本申请实施例提供的另一种网络架构的示意图；
图4为本申请实施例提供的一种配置方法的流程示意图；
图5为本申请实施例提供的另一种配置方法的流程示意图；
图6为本申请实施例提供的一种协商确定各配置参数集合的流程示意图；
图7为本申请实施例提供的一种释放该终端的上下文参数中除所述目标配置参数之外的参数的流程示意图；
图8为本申请实施例提供的一种为终端分配合适配置参数集合的流程示意图；
图9为本申请实施例提供的一种配置方法的流程示意图；
图10为本申请实施例提供的另一种配置方法的流程示意图；
图11为本申请实施例提供的再一种配置方法的流程示意图；
图12为本申请实施例提供的一种MAC消息的结构示意图；
图13为本申请实施例提供的另一种MAC消息的结构示意图；
图14为本申请实施例提供的又一种配置方法的流程示意图；
图15为本申请实施例提供的一种配置方法的流程示意图；
图16为本申请实施例提供的一种确定监听C-RNTI加扰的PDCCH的时机的示意图；
图17为本申请实施例提供的另一种确定监听C-RNTI加扰的PDCCH的时机的示意图；
图18为本申请实施例提供的再一种确定监听C-RNTI加扰的PDCCH的时机的示意图；
图19为本申请实施例提供的又一种确定监听C-RNTI加扰的PDCCH的时机的示意图；
图20为本申请实施例提供的一种配置方法的流程示意图；
图21为本申请实施例提供的一种另配置方法的流程示意图；
图22为本申请实施例提供的再一种配置方法的流程示意图；
图23为本申请实施例提供的又一种配置方法的流程示意图；
图24为本申请实施例提供的一种网络设备的结构示意图；
图25为本申请实施例提供的另一种网络设备的结构示意图；
图26为本申请实施例提供的一种终端的结构示意图。
具体实施方式
本申请实施例应用于通信系统，例如宽带码分多址系统(wideband code division multiple access，WCDMA)、时分同步码分多址系统(time division-synchronization code division multiple access，TD-SCDMA)，长期演进系统(long term evolution，LTE)、公共陆地移动网络(public land mobile network，PLMN)系统，甚至第五代(5th generation，5G)通信系统或未来可能出现的其他系统，以下对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。需要说明的是，当本申请实施例的方案应用于5G系统或未来可能出现的其他系统时，网络设备和终端的名称可能发生变化，但这并不影响本申请实施例方案的实施。
为了合理地为处于非激活态的终端分配配置参数，本申请实施例提供了一种配置方法，示例的，请参见图1所示，图1为本申请实施例提供的一种应用场景示意图，在该应用场景所示的通信系统中可以包括至少一个终端和网络设备，当然，也可以包括核心网设备。网络设备在通过RRC连接释放消息指示终端由连接态进入非激活态的同时，可以在该RRC连接释放消息中携带为非激活态的终端分配的配置参数，即终端接收网络设备发送的无线资源控制RRC连接释放消息，该RRC连接释放消息包括用于指示目标配置参数的第一信息；这样终端就可以根据RRC连接释放消息进入非激活态，且根据第一信息确定非激活态的上下文参数，其中，非激活态的上下文参数包括目标配置参数，或，非激活态的上下文参数包括终端的上下文参数中除目标配置参数之外的参数，从而合理地为处于非激活态的终端指示配置参数。
可以理解的是，在本申请实施例中，网络设备在通过第一信息合理地为非激活态的终端指示配置参数时，可以分为两种不同的场景。在一种场景中，网络设备可以通过第一信息指示为非激活态的终端配置的配置参数，以使终端保留为其配置的配置参数。在另一种场景中，网络设备可以通过第一信息指示非激活态的终端需要释放的配置参数，以使非激活态的终端释放掉需要释放的配置参数。在这两种不同的场景中，第一信息指示的目标配置参数是不同的。
对于非激活状态的终端，由于网络设备需要存储多个处于非激活态的终端中每一个终端的上下文信息，为了减少网络设备的存储开销，可以对多个终端的一部分配置参数进行固定化处理。通常情况下，终端的配置参数可以分为三类，该三种类配置参数分别为安全 类配置参数、无线承载配置参数，和，小区组配置参数，由于每个终端的安全类配置参数均不同，所以不对该安全类配置参数进行固化处理；但可以对终端的无线承载配置参数，和/或，小区组配置参数进行固化处理。通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。基于此，网络设备在通过第一信息为非激活态的终端指示配置参数时，该第一信息指示的目标配置参数同样可以包括无线承载配置参数，和/或，小区组配置参数；至于网络设备为终端配置的安全类配置参数，可以单独发送给终端，当然，也可以与该第一信息一起发送给终端，具体可以根据实际需要进行设置。
由于安全类配置参数跟本申请实施例的实现无关，因此本申请实施例以下的非激活态的上下文参数不包括安全类配置参数，是指无线承载配置参数和小区组配置参数。示例的，无线承载配置参数可以包括分组数据汇聚协议(packet data convergence protocol，PDCP)层参数、业务数据适配协议(service data adaptation protocol，SDAP)层参数、数据承载(data radio bearer，DRB)标识参数及演进分组系统(evolved packet system，EPS)承载标识等参数中的一个或多个。小区组配置参数可以包括小区组标识、承载的无线链路控制(radio link control，RLC)配置参数、媒体接入控制(medium access control，MAC)层的小区组配置参数、物理小区组配置参数、专用小区(PSCell+PCell，Spcell)的配置参数及辅小区(Secondary Cell，Scell)的配置参数等参数中的一个或多个。示例的，PDCP层参数可以包括超时定时器(discardTimer)、上下行的PDCP SN大小头压缩配置、完保开启、确认模式(acknowledged mode，AM)承载的PDCP状态报告需要、乱序发送、分流(split)或重复(duplication)的配置及重排序定时器等。SDAP层参数可以包括会话标识(Session ID)、上行/下行SDAP头存在与否、是否为默认数据承载(data radio bearer，DRB)及服务质量流标识符(qoS flow identifier，QFI)等中的一个或多个。小区组标识可以包括指示主小区组或者辅小区组的标识；承载的RLC配置参数可以包括三种类型的信息，一种类型的信息为标识类信息，包括无线承载(radio bearer，RB)标识、逻辑信道(logical channel，LCH)标识；一种类型的信息为RLC的配置信息，包括RLC PDU的SN长度、分段重组定时器、确认模式(Acknowledged Mode，AM)RLC的最大重传次数、控制AM模式的RLC向接收端发状态报告的请求参数及AM RLC的发送RLC状态报告的禁止定时器；一种类型的信息为逻辑信道配置信息，可以包括优先级处理过程使用的参数(例如，允许的子载波间隔、物理上行链路共享通道(physical uplink shared channel，PUSCH)的传输块(transport block，TB)持续时长、发送速率、逻辑信道优先级等)及LCH对应的调度请求(scheduling request，SR)配置中的一个或多个。MAC层的小区组配置参数可以包括不连续接收(Discontinuous Reception，DRX)配置、SR、缓存状态报告(Buffer Status Report，BSR)、功率余量报告(power headroom report，PHR)的配置参数、触发释放RRC连接的定时器、定时调整组标识及定时调整定时器；物理小区组配置参数可以包括用于功率控制或调度资源的终端的标识(x-RNTI)、控制下行反馈的配置信息及低频段FR1的最大发送功率中的一个或多个。Spcell的配置参数可以包括CellIndex、小区组标识、无线链路失败检测配置、无线链路监测的检测配置、测量配置信息、物理下行控制信道(physical downlink control channel，PDCCH)、物理下行共享信道(physical downlink shared channel， PDSCH)、PUSCH的配置参数、上行链路(up link，UL)和下行链路带宽部分(down link bandwidth part)DL BWP配置、初始DL BWP配置、初始激活BWP ID及管理激活BWP的定时器(timer)中的一个或多个。对于Scell的配置参数，只有在配置了载波聚合(carrier aggregation，CA)或双链接(dual connectivity，DC)时才有该Scell的配置参数，且该Scell的配置参数为Spcell配置信息的子集。
其中，1)终端，又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、或车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端等。
2)网络设备，是无线网络中的设备，例如将终端接入到无线网络的无线接入网(radio access network，RAN)节点。目前，一些RAN节点的举例为：gNB、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。
3)在本申请的实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”一般表示前后关联对象是一种“或”的关系；此外，对于单数形式“a”，“an”和“the”出现的元素(element)，除非上下文另有明确规定，否则其不意味着“一个或仅一个”，而是意味着“一个或多于一个”。例如，“a device”意味着对一个或多个这样的device。再者，至少一个(at least one of).......”意味着后续关联对象中的一个或任意组合，例如“A,B和C中的至少一个”包括A，B，C，AB，AC，BC，或ABC。根据X确定Y并不意味着仅仅根据X确定Y，还可以根据X和其它信息确定Y。
示例的，请参考图2，图2为本申请实施例提供的一种网络架构的示意图。如图2所示，该网络架构包括CN设备和RAN设备。其中RAN设备包括基带装置和射频装置，其中基带装置可以由一个节点实现，也可以由多个节点实现，射频装置可以从基带装置拉远独立实现，也可以集成基带装置中，或者部分拉远部分集成在基带装置中。例如，在长期演进(long term evolution，LTE)通信系统中，RAN设备(eNB)包括基带装置和射频装置，其中射频装置可以相对于基带装置拉远布置，例如射频拉远单元(remote radio unit， RRU)相对于BBU拉远布置。
RAN设备和终端之间的通信遵循一定的协议层结构。例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层等协议层的功能。用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能；在一种实现中，PDCP层之上还可以包括业务数据适配协议(service data adaptation protocol,SDAP)层。
这些协议层的功能可以由一个节点实现，或者可以由多个节点实现；例如，在一种演进结构中，RAN设备可以包括集中单元(centralized unit，CU)和分布单元(distributed unit，DU)，多个DU可以由一个CU集中控制。如图2所示，CU和DU可以根据无线网络的协议层划分，例如PDCP层及以上协议层的功能设置在CU，PDCP以下的协议层，例如RLC层和MAC层等的功能设置在DU。
这种协议层的划分仅仅是一种举例，还可以在其它协议层划分，例如在RLC层划分，将RLC层及以上协议层的功能设置在CU，RLC层以下协议层的功能设置在DU；或者，在某个协议层中划分，例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外，也可以按其它方式划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
此外，射频装置可以拉远，不放在DU中，也可以集成在DU中，或者部分拉远部分集成在DU中，在此不作任何限制。
请继续参考图3，图3为本申请实施例提供的另一种网络架构的示意图，相对于图2所示的架构，还可以将CU的控制面(CP)和用户面(UP)分离，分成不同实体来实现，分别为控制面CU实体(CU-CP实体)和用户面CU实体(CU-UP实体)。
在以上网络架构中，CU产生的信令可以通过DU发送给终端，或者终端产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装而透传给终端或CU。以下实施例中如果涉及这种信令在DU和终端之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为PHY层的信令发送给终端，或者，由接收到的PHY层的信令转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频发送的。
在以上实施例中CU划分为RAN侧的网络设备，此外，也可以将CU划分为CN侧的网络设备，在此不做限制。
本申请以下实施例中的装置，根据其实现的功能，可以位于终端或网络设备。当采用以上CU-DU的结构时，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的RAN设备。
通过上述描述可知，网络设备在指示终端由连接态进入非激活态，且通过第一信息合理地为非激活态的终端指示配置参数时，可以分为两种不同的场景。在一种可能的场景中，网络设备可以通过第一信息指示为非激活态的终端配置的配置参数，以使非激活态的终端保留为其配置的配置参数。在另一种可能的场景中，网络设备可以通过第一信息指示非激活态的终端需要释放的配置参数，以使非激活态的终端释放掉需要释放的配置参数。在这 两种不同的场景中，第一信息指示的目标配置参数是不同的。下面，将结合详细地实施例，针对这两种不同的场景对应的技术方案进行详细地说明。
在一种可能的场景中，网络设备在通过第一信息指示为终端配置的配置参数，以使终端保留为其配置的配置参数时，可以通过两种不同的方式向终端指示需要保留的配置参数。在一种方式中，网络设备可以通过直接指示的方式将需要保留的目标配置参数指示给终端，即第一信息指示的目标配置参数即为终端需要保留的配置参数，使得终端在接收到第一信息后，直接根据该第一信息指示的目标配置参数确定需要保留的配置参数，并保留该目标配置参数。在另一种方式中，网络设备可以通过间接指示的方式向终端指示需要保留的配置参数，即第一信息指示的目标配置参数不是终端需要保留的配置参数，使得终端在接收到第一信息后，根据第一信息指示的目标配置参数确定除该目标配置参数之外的参数，该除目标参数之外的参数即为终端需要保留的配置参数。可以看出，在该两种不同的方式中，第一信息指示的目标配置参数的定义是不同的。在第一种方式中，第一信息指示的目标配置参数为终端需要保留的配置参数；在第二种方式中，第一信息指示的目标配置参数不是终端需要保留的配置参数，而除该目标配置参数之外的参数才是终端需要保留的配置参数。因此，这两种不同的方式中，第一指示信息的目标配置参数是不同的。
在该种可能的场景中，主要以第一种指示方式为例进行说明，即第一信息指示的目标配置参数即为终端需要保留的配置参数。网络设备在通过第一信息指示终端需要保留的目标配置参数时，可以通过两种可能的方式指示终端需要保留的目标配置参数。在一种可能的方式中，第一信息为目标配置参数的标识，即网络设备将目标配置参数的标识指示给终端，以使终端根据目标配置参数的标识确定需要保留的目标配置参数；在另一可能的方式中，第一信息为目标配置参数本身，即网络设备直接将目标配置参数指示给终端，这样终端就可以直接获取到需要保留的目标配置参数。先以第一信息为目标配置参数的标识为例，示例的，请参见图4所示，图4为本申请实施例提供的一种配置方法的流程示意图，该配置方法可以包括：
S401、网络设备向终端发送无线资源控制(RRC)连接释放消息。
其中，RRC连接释放消息包括第一信息，第一信息为目标配置参数的标识。示例的，该目标配置参数可以包括无线承载配置参数，和/或，小区组配置参数。
参见上述关于配置参数的相关描述，为了降低网络设备的存储开销，网络设备可以对至少两个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，从而降低网络设备的存储开销。经过固化处理之后，可以得到多个配置参数集合，之后，再在多个配置参数集合中为终端分配合适的一个或多个配置参数集合。配置参数可以称为接入层配置参数，接入层配置参数可以包括无线承载配置参数或，小区组配置参数，或者既包括无线承载配置参数又包括小区组配置参数。示例的，以接入层配置参数为例，经过固化之后，可以得到多个预定义的接入层配置参数集合，分别为：集合1、集合2、集合3，…，及集合N。可选的，在为终端分配合适的接入层配置参数集合时，可以根据终端的数据无线承载DRB对应的模式为终端分配其对应的接入层配置参数集合。当终端的DRB对应的模式为确认模式AM时，可以将集合1中的参数作为目标配置参数指示给终端，该集合1中可以包括SDAP参数、PDCP参数、RLC参数及MAC层的小区组配置参数中的一个或多个。该集合1也可以包括DRB ID。其中，SDAP 参数可以包括上行/下行SDAP头存在与否，是否为默认DRB及QFI中的一个或多个，可选的，SDAP参数也可以Session ID；PDCP参数可以包括discardTimer，上下行的PDSP SN大小，头压缩配置，完保开启、AM承载的PDCP状态报告需要，乱序发送及重排序定时器中的一个或多个。RLC参数可以包括RB标识、LCH标识、RLC的配置信息、RLC PDU的SN长度、分段重组定时器、AM RLC的最大重传次数、控制AM模式向接收端发poll的请求参数及AM RLC的发送RLC状态报告的禁止定时器中的一个或多个。MAC层的小区组配置参数一个LCH ID所允许的子载波间隔、PUSCH的TB持续时长、发送速率及逻辑信道优先级等中的一个或多个。若该集合1中不包括Session ID，则网络设备可以进一步指示终端哪个session ID和该集合1中的参数关联。类似的，若该集合1中不包括RB ID，则网络设备可以进一步指示终端哪个RB ID和该集合1中的参数关联。
相反的，当终端的DRB对应的模式为非确认模式UM时，可以为将集合2中的参数作为目标配置参数指示给终端，该集合2中可以包括PDCP参数和RLC参数中的一个或多个。当然，该集合2也可以包括SDAP参数和MAC层的小区组配置参中的一个或多个数。其中，PDCP参数可以包括discardTimer，上下行的PDSP SN大小，头压缩配置，完保开启、乱序发送及重排序定时器中的一个或多个。RLC参数可以包括RB标识、LCH标识、RLC的配置信息：RLC PDU的SN长度及分段重组定时器中的一个或多个。SDAP参数可以包括上行/下行SDAP头存在与否，是否为默认DRB及QFI中的一个或多个，可选的，SDAP参数也可以Session ID。MAC层的小区组配置参数一个LCH ID所允许的子载波间隔、PUSCH的TB持续时长、发送速率及逻辑信道优先级等中的一个或多个。若该集合2中不包括Session ID，则网络设备可以进一步指示终端哪个session ID和该集合2中的参数关联。类似的，若该集合2中不包括RB ID，则网络设备可以进一步指示终端哪个RB ID和该集合2中的参数关联。
结合上述关于集合1和集合2的描述，还可以在集合1和集合2的基础上，进一步定义集合3、集合4、集合5及集合6。例如，可以将集合3定义为集合1和Spcell的配置参数形成的集合；可以将集合4定义为集合2和Spcell的配置参数形成的集合；可以将集合5定义为集合3和Scell的配置参数形成的集合；可以将集合6定义为集合4和Scell的配置参数形成的集合，当然，本申请实施例只是以该集合1、集合2、集合3、集合4、集合5及集合6为例进行说明，但并不代表本申请实施例仅局限于此。
可以理解的是，上述网络设备为终端指示适合该终端的配置参数集合，实质上是将配置参数集合中的配置参数指示给终端，即将该配置参数集合中的配置参数作为目标配置参数分配给终端。网络设备在将目标配置参数指示给终端时，可以将该目标配置参数的标识作为第一信息携带在RRC连接释放消息中发送给终端，以使终端根据该RRC释放消息执行下述S402：
S402、终端根据RRC连接释放消息进入非激活态，且根据目标配置参数对应的标识，及映射关系确定非激活态的上下文参数包括标识对应的目标配置参数。
示例的，该目标配置参数的标识可以为配置参数集合的集合标识，例如集合1的标识、或者集合2的标识等。
终端在接收到网络设备发送的RRC连接释放消息之后，根据该RRC连接释放消息进入非激活态。此外，由于终端预先存储有配置参数对应的标识和配置参数的映射关系，这 样终端在接收到网络设备发送第一信息为目标配置参数对应的标识之后，可以根据目标配置参数对应的标识在映射关系中查找该目标配置参数对应的标识，并将目标配置参数对应的标识对应的配置参数确定为需要保留的目标配置参数，例如集合1中的配置参数或者集合2中的配置参数，以得到目标配置参数，从而保留该集合1中的配置参数或者集合2中的配置参数，并根据该目标配置参数进行配置。
S403、终端保留目标配置参数。
进一步的，网络设备通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样当多个终端由连接态进入非激活态时，对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。
此外，对于终端而言，在根据RRC连接释放消息由连接态进入至非激活态之后，还可以释放连接态下的MAC层配置信息、RLC层配置信息、PDCP层配置信息、SDAP层配置信息、物理小区组配置信息、Spcell的配置、Scell的配置信息中的部分或全部。
需要说明的是，网络设备在向终端发送RRC连接释放消息之前，可以先获取终端上报的能力信息，并根据终端上报的能力信息确定该终端是否支持在非激活态下进行数据传输。示例的，终端在上报其能力信息时，可以通过至少四种可能的方式向网络设备上报其能力信息。以终端支持在非激活态下进行数据传输为例，该四种可能的方式分别为：终端能支持非激活态下的数据传输、终端支持通过预配置标识配置终端的上下文参数、终端支持非激活态下的公共的参数配置(换言之，终端支持轻量级的接入层配置参数)、终端支持直接非激活态下的数据传输的会话。虽然表达方式不同，但是通过该四种不同的方式均可以指示终端支持非激活态下的数据传输。
可以看出，上述图4所示的实施例详细描述在一种可能的场景中，当第一信息为目标配置参数的标识时，网络设备通过目标配置参数的标识指示终端需要保留的目标配置参数的技术方案，下面，将详细描述在另一种可能的场景中，当第一信息为目标配置参数本身时，网络设备通过目标配置参数本身指示终端需要保留的目标配置参数的技术方案。示例的，请参见图5所示，图5为本申请实施例提供的另一种配置方法的流程示意图，该配置方法可以包括：
S501、网络设备向终端发送无线资源控制RRC连接释放消息。
其中，RRC连接释放消息包括第一信息，第一信息为目标配置参数。示例的，该目标配置参数可以包括无线承载配置参数，和/或，小区组配置参数。
参见上述关于配置参数的相关描述，为了降低网络设备的存储开销，网络设备可以对至少两个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，从而降低网络设备的存储开销。经过固化处理之后，可以得到多个配置参数集合，之后，再在该多个配置参数集合中为终端分配合适的一个或多个配置参数集合。可以理解的是，在该种可能的场景中，网络设备预先得到多个配置参数集合的方法，及为终端指示合适的一个或多个配置参数集合的方法分别与上述S401中的网络设备预先得到多个配置参数集合的方法，及为终端指示合适的一个或多个配置参数集合的方法类似，可参见上述S401中的相关描述，在此，本申请实施例不再进行赘述。
可以看出，在该图5所示的实施例中，与上述图4所示的实施例中的技术方案不同的 是，网络设备在指示终端需要保留的目标配置参数时，是直接将配置参数集合中的目标配置参数本身作为第一信息，携带在RRC连接释放消息中发送给终端，以使终端根据该RRC释放消息执行下述S502：
S502、根据RRC连接释放消息进入非激活态，且根据第一信息确定目标配置参数。
终端在接收到网络设备发送的RRC连接释放消息之后，与上述S403不同的是，在该种可能的实现方式中，终端无需预先存储有配置参数对应的标识和配置参数的映射关系，更无需根据目标配置参数对应的标识及映射关系确定目标配置参数，而是直接根据该RRC连接释放消息进入非激活态，且由于RRC连接释放消息中直接携带的是目标配置参数，使得终端可以直接获取并保留该目标配置参数。虽然将目标配置参数携带在RRC连接释放消息中发送给终端，会使得配置信令开销较大，但对于终端而言，终端不必预先存储预配置，降低了终端的存储开销的配置开销。
S503、终端保留目标配置参数。
进一步的，在本申请实施例中，网络设备通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样当多个终端由连接态进入非激活态时，对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。
此外，对于终端而言，在根据RRC连接释放消息由连接态进入至非激活态之后，还可以释放连接态下的MAC层配置信息、RLC层配置信息、PDCP层配置信息、SDAP层配置信息、物理小区组配置信息、Spcell的配置、Scell的配置信息中的部分或全部。
网络设备在向终端发送RRC连接释放消息之前，可以先获取终端上报的能力信息，并根据终端上报的能力信息确定该终端是否支持在非激活态下进行数据传输。示例的，终端在上报其能力信息时，其上报方式与上述图4所示的实施例中终端上报方式相同，具体可参见上述相关描述，在此，本申请实施例不再进行赘述。
需要说明的是，在上述图4和图5所示的实施例中，在描述网络设备通过第一信息向终端指示需要保留的配置参数时，只是以第一信息指示的目标配置参数即为终端需要保留的配置参数为例进行说明。当然，第一信息指示的目标配置参数也可以不是终端需要保留的配置参数，对应的，终端在接收到该第一信息后，可以根据第一信息指示的目标配置参数确定除该目标配置参数之外的参数，该除目标参数之外的参数即为终端需要保留的配置参数，从而保留该除目标参数之外的参数。值得注意的是，在两种不同的指示方式中，第一信息指示的目标配置参数是不同的。在此，本申请实施例不再进行赘述。
上述图4和图5所示的实施例详细描述了在一种可能的场景中，网络设备可以通过第一信息指示为非激活态的终端配置的配置参数，以使非激活态的终端保留为其配置的配置参数的技术方案，下面，将详细描述了在另一种可能的场景中，网络设备可以通过第一信息指示非激活态的终端需要释放的配置参数，以使非激活态的终端释放掉需要释放的配置参数的技术方案。
在另一种可能的场景中，网络设备在通过第一信息指示终端需要释放的配置参数，以使终端释放掉需要释放的配置参数时，同样可以通过两种不同的方式向终端指示需要释放的配置参数。在一种方式中，网络设备可以通过直接指示的方式将需要释放的配置参数指示给终端，即第一信息指示的目标配置参数即为终端需要释放的配置参数，使得终端在接 收到第一信息后，直接根据该第一信息指示的目标配置参数确定需要释放的配置参数，并释放该目标配置参数。在另一种方式中，网络设备可以通过间接指示的方式向终端指示需要释放的配置参数，即第一信息指示的目标配置参数不是终端需要释放的配置参数，使得终端在接收到第一信息后，根据第一信息指示的目标配置参数确定除该目标配置参数之外的参数，该除目标参数之外的参数即为终端需要释放的配置参数。同样可以看出，在该两种不同的方式中，第一信息指示的目标配置参数的定义是不同的。在第一种方式中，第一信息指示的目标配置参数为终端需要释放的配置参数；在第二种方式中，第一信息指示的目标配置参数不是终端需要释放的配置参数，而除该目标配置参数之外的参数才是终端需要释放的配置参数。因此，这两种不同的方式中，第一指示信息的目标配置参数是不同的。
在该种可能的场景中，主要以第一种指示方式为例进行说明，即第一信息指示的目标配置参数即为终端需要释放的配置参数。网络设备在通过第一信息指示终端需要释放的目标配置参数时，可以通过两种可能的方式指示终端需要释放的目标配置参数。在一种可能的方式中，第一信息为目标配置参数的标识，即网络设备将目标配置参数的标识指示给终端，以使终端根据目标配置参数的标识确定需要释放的目标配置参数；在另一可能的方式中，第一信息为目标配置参数本身，即网络设备直接将目标配置参数指示给终端，这样终端就可以直接获取到需要释放的目标配置参数。先以第一信息为目标配置参数的标识为例，示例的，请参见图6所示，图6为本申请实施例提供的一种释放该终端的上下文参数中除所述目标配置参数之外的参数的流程示意图，该方法可以包括：
S601、网络设备向终端发送无线资源控制(RRC)连接释放消息。
其中，RRC连接释放消息包括第一信息，第一信息为目标配置参数的标识。示例的，目标配置参数可以包括无线承载配置参数，和/或，小区组配置参数。
在该种可能的场景中，假设网络设备已经预先为终端配置了多套配置参数，在为终端预先配置多套配置参数之前，同样的，为了降低网络设备的存储开销，网络设备可以对至少两个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，从而降低网络设备的存储开销。经过固化处理之后，可以得到多个配置参数集合，之后，再在该多个配置参数集合中的配置参数配置给终端。可以理解的是，在该种可能的场景中，网络设备预先得到多个配置参数集合的方法，及为终端分配多套配置参数集合的方法分别与上述S401中的网络设备预先得到多个配置参数集合的方法，及为终端分配多套配置参数集合的方法类似，可参见上述S401中的相关描述，在此，本申请实施例不再进行赘述。
网络设备在通过第一信息指示终端需要释放的目标配置参数时，可以将该目标配置参数的标识作为第一信息携带在RRC连接释放消息中发送给终端，以使终端根据该RRC释放消息执行下述S602：
S602、终端根据RRC连接释放消息进入非激活态，且根据目标配置参数对应的标识，及映射关系确定非激活态的上下文参数包括标识对应的目标配置参数。
示例的，该目标配置参数的标识可以为配置参数集合的集合标识，例如集合1的标识、或者集合2的标识等。
终端在接收到网络设备发送的RRC连接释放消息之后，根据该RRC连接释放消息进入非激活态。此外，由于终端预先存储有配置参数对应的标识和配置参数的映射关系，这 样终端在接收到网络设备发送第一信息为目标配置参数对应的标识之后，可以根据目标配置参数对应的标识在映射关系中查找该目标配置参数对应的标识，并将目标配置参数对应的标识对应的配置参数确定为需要释放的目标配置参数，例如集合1中的配置参数或者集合2中的配置参数确定为需要释放的目标配置参数，以得到目标配置参数，从而释放该集合1中的配置参数或者集合2中的配置参数。
S603、终端释放该非激活态的上下文参数中的目标配置参数。
终端在接收到网络设备发送的RRC连接释放消息，并根据其携带的第一信息确定终端的上下文参数中包括的需要释放的目标配置参数后，就可以直接释放该目标配置参数，从而实现在降低网络设备和终端的存储开销的前提下，使得网络设备可以控制哪些配置参数继续使用，哪些配置参数不再使用。
此外，对于终端而言，在根据RRC连接释放消息由连接态进入至非激活态之后，还可以释放其他接入层参数，该其它接入层参数包括物理小区配置信息、Spcell的配置信息及Scell配置信息中的至少一种。示例的，终端在释放其他接入层参数时，一种方式为：终端在接收到该RRC连接释放消息后，默认释放其他接入层参数，即在该种方式中，RRC消息中无需携带释放指示信息。在另一种方式中，终端接收RRC连接释放消息后，该RRC连接释放消息中可以显式携带释放其他配置的指示信息，使得终端根据该释放其他配置的指示信息释放其他接入层参数。
上述图6所示的实施例详细描述了在一种可能的场景中，当第一信息为目标配置参数的标识时，网络设备通过目标配置参数的标识指示终端需要释放的目标配置参数的技术方案，当然，第一信息也可以为目标配置参数本身，即网络设备可以将需要释放的目标配置参数本身作为第一信息，携带在RRC连接释放消息中发送给终端，以使终端直接根据该第一信息就可以确定需要释放的目标配置参数，与第一信息为目标配置参数的标识相比，终端无需预先存储有配置参数对应的标识和配置参数的映射关系，更无需根据目标配置参数对应的标识及映射关系确定目标配置参数，而是直接根据该RRC连接释放消息进入非激活态，且由于RRC连接释放消息中直接携带的是目标配置参数，使得终端可以直接获取并释放该目标配置参数。虽然将目标配置参数携带在RRC连接释放消息中发送给终端，会使得配置信令开销较大，但对于终端而言，终端不必预先存储预配置，降低了终端的存储开销的配置开销。
需要说明的是，在上述图7所示的实施例中，在描述网络设备通过第一信息向终端指示需要释放的配置参数时，只是以第一信息指示的目标配置参数即为终端需要释放的配置参数为例进行说明。当然，第一信息指示的目标配置参数也可以不是终端需要释放的配置参数，对应的，终端在接收到该第一信息后，可以根据第一信息指示的目标配置参数确定除该目标配置参数之外的参数，该除目标参数之外的参数即为终端需要释放的配置参数，从而释放该除目标参数之外的参数。值得注意的是，在两种不同的指示方式中，第一信息指示的目标配置参数是不同的。在此，本申请实施例不再进行赘述。
基于上述图4-图6任一附图所示的实施例，网络设备无论是通过第一信息指示的目标配置参数指示终端需要保留的配置参数，还是指示终端需要释放的配置参数，在通过第一信息指示之前，都会先对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，以得到一个或多个配置参数集合；之后才能通过第一信息指示终端需要保留的某个 配置参数集合中配置参数，或者，指示终端需要释放的某个配置参数集合中配置参数。为了统一各网络设备为终端配置的一个或多个配置参数集合，网络设备在向终端发送用于指示目标配置参数的RRC连接请求消息之前，可以先与其它网络设备，例如第一网络设备共同协商以确定各配置参数集合。示例的，请参见图7所示，图7为本申请实施例提供的一种协商确定各配置参数集合的流程示意图，该确定各配置参数集合的方法可以包括：
S701、网络设备向第一网络设备发送给第一请求消息。
其中，第一请求消息中包括初始配置参数集合，该初始配置参数集合中包括网络设备确定的初始无线承载配置参数和/或初始小区组配置参数，第一请求消息用于请求第一网络设备确认该初始配置参数集合中的初始无线承载配置参数和/或初始小区组配置参数。
示例的，第一网络设备接收到网络设备发送的包括初始无线承载配置参数和/或初始小区组配置参数之后，一种可能的情况是：若第一网络设备支持该初始无线承载配置参数和/或初始小区组配置参数，则确认并存储该初始无线承载配置参数和/或初始小区组配置参数，此时向网络设备发送的响应消息中包括的还是该初始无线承载配置参数和/或初始小区组配置参数；另一种可能的情况是：若第一网络设备不支持该初始无线承载配置参数和/或初始小区组配置参数，需要修改该初始无线承载配置参数和/或初始小区组配置参数，则直接对该初始无线承载配置参数和/或初始小区组配置参数进行修改并存储修改后的无线承载配置参数和/或修改后的小区组配置参数，此时，第一网络设备向网络设备发送的响应消息中包括的是修改后的无线承载配置参数和/或修改后的小区组配置参数。
需要说明的是，网络设备在与第一网络设备协商确定各配置参数集合时，可以将全部配置参数集合通过第一请求消息发送给第一网络设备；当然，也可以将该全部配置参数集合通过多个第一请求消息发送给第一网络设备，具体可以根据实际需要进行设置，在此，本申请实施例不做进一步地限制。
S702、第一网络设备向网络设备发送第一响应消息。
其中，第一响应消息包括初始无线承载配置参数和/或初始小区组配置参数，或者，第一网络设备修改后的无线承载配置参数和修改后的小区组配置参数。
网络设备在接收到第一响应消息之后，可以根据该第一响应消息确定配置参数集合，即执行下述S703：
S703、网络设备根据第一响应消息确定配置参数集合。
若第一响应消息中包括的是初始无线承载配置参数和/或初始小区组配置参数，则说明第一网络设备支持网络设备确定的初始无线承载配置参数和/或初始小区组配置参数，则将包括该初始无线承载配置参数和/或初始小区组配置参数确定为后续可使用的配置参数，包括该配置参数的集合即为后续使用的配置参数集合。若第一响应消息中包括的是修改后的无线承载配置参数和/或修改后的小区组配置参数，则说明第一网络设备不支持网络设备确定的初始无线承载配置参数和/或初始小区组配置参数，则将包括修改后的无线承载配置参数和/或修改后的小区组配置参数确定为后续可使用的配置参数，包括该配置参数的集合即为后续使用的配置参数集合，之后，网络设备就可以通过第一信息指示终端需要保留的某个配置参数集合中配置参数，或者，指示终端需要释放的某个配置参数集合中配置参数，且在指示过程中，避免了各配置参数不统一带来的缺陷。
上述图4和图5所示的实施例，详细描述了为了降低网络设备的存储开销，网络设备 可以对至少两个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，以得到多个配置参数集合，之后，再在该多个配置参数集合中为终端指示合适的一个或多个配置参数集合的技术方案。示例的，网络设备在为终端指示合适的一个或者多个配置参数集合之前，可以先接收核心网设备发送的指示信息，该指示信息用于指示网络设备为终端指示合适的一个或者多个配置参数集合。示例的，请参见图8所示，图8为本申请实施例提供的一种为终端分配合适配置参数集合的流程示意图，该方法可以包括：
S801、终端向核心网设备发送注册请求。
其中，注册请求中可选包括该终端的能力信息。示例的，该终端的能力信息可以为终端支持直接数据传输(direct data transmission，DDT)会话，即终端支持在非激活态下直接进行数据传输。需要说明的是，终端能力信息与上述图4所示的实施例中终端能力信息相同，具体可参见图4所示的实施例中的相关描述，在此，本申请实施例不再进行赘述。
S802、终端向核心网设备发送协议数据单元(protocol data unit，PDU)会话建立请求。
可选的，该PDU会话建立请求中可选指示会话类型为DDT会话，即该DDT会话可以用于终端在非激活态下直接进行数据传输。如此可以实现会话粒度的非激活态下直接的数据传输。
S803、核心网设备可选根据终端的签约数据和/或能力信息确定为终端建立DDT会话。
示例的，核心网设备在确定是否为终端建立DDT会话时，可以通过会话管理功能(session management function，SMF)设备中查找该终端的签约数据，并根据该终端的签约数据确定是否为终端建立DDT会话，例如运营商与终端的用户签约为其提供DDT功能时，确定为终端建立DDT会话。当然，也可以无需通过SMF设备查找该终端的签约数据，而是直接根据其自身存储的终端的能力信息确定是否为终端建立DDT会话。
经过判断之后，若核心网设备确定为终端建立DDT会话，则向网络设备PDU会话建立请求，即执行下述S804：
S804、核心网设备向网络设备发送PDU会话建立请求。
其中，该PDU会话建立请求中可以包括会话类型，该会话类型用于指示终端在非激活态时允许进行上行传输。示例的，该会话类型可以是一个布尔型参数，取值为1，表示可以在非激活态进行数据传输；取值为0，表示不能在非激活态进行数据传输，反过来也可以；或者，该会话类型为枚举型参数，取值为True，表示可以在非激活态进行数据传输；取值为False，表示不能在非激活态进行数据传输；或者，取值为DDT会话，表示可以在非激活态进行数据传输；取值为其它，表示不能在非激活态进行数据传输。该会话类型又可以称为指示信息。
可以看出，用于指示终端在非激活态时允许进行上行传输的会话类型是携带在PDU会话建立请求中发送给网络设备的，当然，除了携带在PDU会话建立请求中发送给网络设备之外，还可以在PDU会话修改过程中，将会话类型携带在PDU会话修改请求中发送给网络设备。在此，本申请实施例只是以将会话类型携带在PDU会话建立请求中发送给网络设备为例进行说明，但并不代表本申请实施例仅局限于此。
进一步地，以上PDU会话建立请求中还可以包括会话标识，以标识该会话；由于一个会话中可以包括多个流，核心网设备指示一个会话是否可在非激活态时允许进行上行传输，也可以以一个流为单位进行指示，即指示一个流标识是否可在非激活态时允许进行上 行传输。这样，核心网设备在向网络设备发送PDU会话建立请求时，只需要将该PDU会话建立请求中增加该会话中的流标识即可，以通过流标识指示是否可在非激活态时允许进行上行传输。此时，以上会话类型又可以称为流类型，或者统称为指示信息。
S805、网络设备为终端分配目标配置参数。
网络设备为终端分配目标配置参数的方法可参见上述图4所示的实施例中的相关描述，在此，本申请实施例不再进行赘述。
S806、网络设备向终端发送第一信息。
其中，第一信息用于指示该目标配置参数。示例的，第一信息可以为目标配置参数对应的标识，也可以为目标配置参数本身。
S807、网络设备向核心网设备发送PDU会话建立响应。
通过图8所示的实施例，核心网设备可以根据终端的签约数据和/或能力信息确定是否为终端建立DDT会话，并在确定为终端建立DDT会话时，通过会话标识或流标识指示网络设备为该终端建立某个会话或会话ID中的某个流，指示信息(会话类型或流类型)用于指示终端在非激活态可以进行数据传输，对应的，网络设备可以根据该指示信息为终端分配目标配置参数，在为终端分配目标配置参数时，网络设备同样可以通过对多个终端的无线承载配置参数，和/或，小区组配置参数进行固化处理，使得至少两个终端对应同一套配置参数，这样当多个终端由连接态进入非激活态时，对于网络设备而言，在存储该至少两个终端的配置信息时，只需要存储一套配置信息即可，从而降低了网络设备的存储开销。
该图8所示的实施例可以与图4或者图5所示的实施例结合实现，当然，该图8所示的实施例也可以独立实现，即该图8所示的实施例与图4或图5所示的实施例是解耦合的，不具有绑定关系。
基于上述任一实施例，终端接收到网络设备发送的RRC连接释放消息之后，会根据该RRC连接释放消息进入非激活态。当终端处于非激活态时，若终端接收到网络设备发送的用于指示终端在非激活态时监听物理下行控制信道的第一指示，则终端在非激活态时监听物理下行控制信道。可选的，第一指示可以包括在RRC释放消息中，当然，也可以携带在其它消息中，具体可以根据实际需要进行设置。
此外，当终端处于非激活态时，终端还可以接收用于指示终端在非激活态时允许进行上行传输的第二指示。示例的，终端可以向网络设备发送随机接入请求，并接收随机接入请求的响应消息，该响应消息包括上行授权和第二指示，这样当终端需要进行DRB数据传输时，可以在上行授权指示的上行资源上进行DRB数据上行传输，实现了终端在非激活态时完成上行DRB数据传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
通过上述任一实施例，终端在接收到网络设备发送的RRC连接释放消息之后，可以根据该RRC连接释放消息进入非激活态。在进入非激活态之后，若要进行上行传输，则终端可以在随机接入过程中，在网络设备指示的上行资源中发送前导码和上行数据，若网络设备解析上行数据失败，则对于终端而言，若要再次向网络设备发送上行数据，则需要先恢复RRC连接，并在其处于连接态时重新向网络设备发送上行数据，以使网络设备可以准确地接收到终端发送的上行数据，该上行数据为PUSCH数据。该上行数据包括RRC 信令和/或上行DRB数据。为了实现终端在非激活态进行上行传输，示例的，请参见图9所示，图9为本申请实施例提供的一种配置方法的流程示意图，该配置方法可以包括：
S901、终端获取网络设备发送的指示信息和上行资源。
其中，指示信息用于指示终端使能在非激活态时进行上行传输。其中，所述指示信息是可选的。
示例的，终端在获取指示信息时，可以通过RRC连接释放消息获取该指示信息，也可以通过广播消息获取该指示信息，具体可以根据实际需要进行设置，在此，对于指示信息的获取方式，本申请实施例不做进一步地限制。
示例的，终端在获取上行资源时，可以通过三种可能的方式获取该上行资源。在一种可能的方式中，终端可以向网络设备发送前导码，并接收网络设备发送的随机接入响应消息，该随机接入响应中可以包括该上行资源，从而获取到该上行资源。在另一种可能的方式中，终端可以利用两步随机接入信道(random access channel，RACH)的消息A(MsgA)中的上行资源，并将该上行资源作为待使用的上行资源，从而获取到该上行资源。可以理解的是，该两步RACH中的上行资源可以通过RRC连接释放消息或者广播消息获取。在又一种可能的实现方式中，终端可以无需发送前导码，而是直接使用预配置的PUSCH资源中的上行资源，并将该上行资源作为待使用的上行资源，从而获取到该上行资源。可以理解的是，预配置的PUSCH资源可以通过RRC连接释放消息或者广播消息获取。
在分别获取到指示信息和上行资源之后，还不能直接在获取到的上行资源上进行上行传输，而是需要先将待传输的上行数据量与数据量门限进行比较，并根据比较结果进行上行传输，即执行下述S902：
S902、终端在进行上行传输时，获取待传输的上行数据量与数据量门限的比较结果。
若比较结果指示待传输的上行数据量大于数据量门限，则执行下述S903-S904；若比较结果指示待传输的上行数据量小于数据量门限，则执行下述S905；若比较结果指示待传输的上行数据量等于数据量门限，则执行下述S903-S904，或下述S905。
其中，S902是可选的。UE可以任意选择采用下述S903-S904，或下述S905。
S903、终端向网络设备发送RRC连接恢复请求，不发送上行数据。
S904、终端在接收到网络设备发送的竞争解决响应时，使用竞争解决响应中的上行资源传输上行数据。
S905、终端向网络设备发送RRC连接恢复请求的同时，通过上行资源向网络设备发送上行数据。
示例的，终端在向网络设备发送RRC连接恢复请求时，该RRC连接恢复请求中可以携带一个指示，该指示用于指示待传输的上行数据量与数据量门限之间的大小关系。示例的，该指示可以用一个布尔型参数(或布尔值)表示，例如，当该布尔值为1时，表示待传输数据量大于数据量门限；当该布尔值为0时，表示待传输数据量小于数据量门限，反之也可以；对于待传输数据量等于数据量门限的情况下，布尔值可以为0，也可以为1。或者，该指示可以通过该RRC连接恢复请求中的一个字段是否存在表示，当该RRC连接恢复请求中存在该字段，表示待传输数据量小于数据量门限；当该RRC连接恢复请求中不存在该字段，表示待传输数据量大于数据量门限，反之也可以；对于待发送数据量等于数据量门限的情况下，RRC连接恢复请求中可以存在该字段，也可以不存在该字段。或者， 该指示可以通过该RRC连接恢复请求中的一个枚举型字段表示，当该RRC连接恢复请求中的字段为TRUE时，表示待发送数据量小于数据量门限；当该RRC连接恢复请求中的该字段为FALSE时，表示待发送数据量大于数据量门限，反之也可以；对于待发送数据量等于数据量门限的情况下，RRC连接恢复请求中该字段可以为TRUE，也可以为FALSE。以取值为TRUE表示待传输的上行数据量大于数据量门限，取值为FALSE表示待传输的上行数据量小于或等于数据量门限为例，则在S903中，RRC连接恢复请求中携带的指示为TRUE；在S905中，RRC连接恢复请求中携带的指示为FALSE。在此，本申请实施例只是以这几种方式为例进行说明，具体可以根据实际需要进行设置。其中，数据量门限可以从网络发送的广播消息或专用消息中获得，也可以为预设值。
对应的，网络设备在接收到终端通过S904或者S905发送的上行数据之后，可以进一步执行下述S906-S907。
S906、网络设备确定是否允许在上行授权指示的上行资源上进行上行传输。
S907、网络设备向终端发送用于指示是否允许在上行授权指示的上行资源上进行上行传输的指示信息。
若指示信息指示允许在上行授权指示的上行资源上进行上行传输，则终端需要进行上行传输时，利用该上行资源进行上行传输，若指示信息指示不允许在上行授权指示的上行资源上进行上行传输，则终端需要进行上行传输时，则终端可以执行上述S903-S904。
由此可见，通过图9所示的实施例，终端通过向网络设备发送RRC连接恢复请求，使得网络设备可以在终端处于非激活态时，为该终端分配上行授权，并通过指示信息指示是否允许在上行授权指示的上行资源上进行上行传输，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
基于上述图9所示的实施例，以两步RACH发送数据为例，终端在向网络设备发送上行数据之前，将待传输的上行数据量与数据量门限进行比较，且根据网络设备发送的指示信息确定是否允许在上行授权指示的上行资源上进行上行传输。经过比较之后，若待传输的上行数据量小于或者等于数据量门限，且终端确定可以在上行授权指示的上行资源上进行上行传输，则恢复DRB和SRB的PDCP状态，并重建PCDP实体，恢复SRB和DRB的状态，并向网络设备发送第一消息，该第一消息可以包括在PRACH资源上发送的preamble，以及在PUSCH资源上发送的RRC连接恢复请求和上行数据。对应的，网络设备在接收到终端通过第一消息发送的前导码和PUSCH数据之后，会对接收到的前导码和PUSCH数据进行解析。在解析前导码和PUSCH数据时，可以分为两种不同的场景，在一种场景中，网络设备解析前导码成功，但解析PUSCH数据失败；在另一种场景中，网络设备解析前导码成功，且解析PUSCH数据成功。下面，将通过详细的实施例，分别针对这两种不同的场景进行详细地说明。
在一种场景中，当网络设备解析前导码成功，但解析上行数据失败时，示例的，请参见图10所示，图10为本申请实施例提供的另一种配置方法的流程示意图，该配置方法可以包括：
S1001、终端向网络设备发送第一消息。
其中，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数 据包括用于请求恢复无线资源控制(RRC)连接的信息，例如RRC连接恢复请求。示例的，随机接入请求可以为前导码，物理上行共享信道数据还可以包括上行数据。其中，上行数据是可选的。
终端向网络设备发送第一消息之后，网络设备可以对第一消息中包括的前导码和上行数据进行解析，当网络设备解析前导码成功，但解析上行数据失败时，网络设备会根据解析结果向终端发送第一消息的响应消息，即执行下述S1002：
S1002、网络设备向终端发送第一消息的响应消息。
其中，响应消息包括上行授权和第一指示信息，第一指示信息用于指示是否允许在上行授权指示的上行资源上进行上行传输。
可选的，第一消息的响应消息还可以包括随机接入前导标识(Random Access Preamble Identifier，RAP ID)、定时提前量(time advance，TA)及临时小区无线网络临时标识(temporary cell radio network temporary identity，TC-RNTI)。其中，RAP ID为S1001中的前导码对应的标识，若RAP ID和终端发送的前导码对应的标识相同，终端则确认该第一消息的响应消息为网络设备为其发送的响应消息。TA表示上行发送定时的提前量，用于终端调整上行发送定时。TC-RNTI为网络设备为终端分配的标识，当竞争解决时，该TC-RNTI可以作为C-RNTI使用，网络设备通过C-RNTI加扰的PDCCH指示PUSCH资源，终端使用该PUSCH资源发送上行信令或数据。可选的，第一消息的响应消息还可以包括RRC专用信令消息，例如RRC重配置消息。
示例的，若终端确定可以在上行授权指示的上行资源上进行上行传输时未启动定时器，则终端在接收到网络设备发送的第一消息的响应消息之后，启动定时器；反之，若终端确定可以在上行授权指示的上行资源上进行上行传输时已经启动定时器，则终端在接收到网络设备发送的第一消息的响应消息之后，重启定时器。示例的，该定时器可以为T319定时器，也可以为其它新的定时器。
其中，定时器的时长用于限定为RRC连接恢复过程的最长等待时间或最大容忍时长。例如，当定时器可以为T319定时器时，终端发送连接恢复请求时启动T319，当收到网络设备发送的连接恢复或连接建立、连接释放消息，则停止T319；或者，终端重选小区或者收到终端的高层指示退出RRC连接建立时，终端停止T319。否则，当T319超时，终端以RRC连接恢复失败的原因释放连接进入空闲态。
可以看出，与现有技术中不同的是，在本申请实施例中，网络设备向终端发送的第一消息的响应消息中不仅包括上行授权信息，还进一步包括了第一指示信息。该第一指示信息指示的内容不同，对应的，终端在上行授权指示的上行资源上进行上行传输的方式也不同。当第一指示信息指示终端允许在上行授权指示的上行资源上进行上行传输时，可以执行下述S1003；相反的，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行传输时，可以执行下述S1004。第一指示信息所指示的上行传输是指上行DRB数据的传输。
以上第一指示信息可以为显性的指示信息，例如，可以为1比特指示信息，当其取值为“1”时，指示允许终端在上行授权指示的上行资源上进行上行传输，当其取值为“0”时，指示不允许终端在上行授权指示的上行资源上进行上行传输。当然，取值的含义也可以反过来，在此不再赘述。
可选的，响应消息中也可以不携带第一指示信息，即通过隐式指示的方式指示终端，例如，当上行授权能容纳所有的待发送数据时，终端在上行授权指示的上行资源上进行DRB数据的上行传输。否则，终端不在上行授权指示的上行资源上进行DRB数据的上行传输。
可选的，也可以在允许终端在上行授权指示的上行资源上进行上行传输时在响应消息中携带第一指示信息，不允许终端在上行授权指示的上行资源上进行上行传输时在响应消息中不携带第一指示信息的方式来指示终端是否可以使用该上行授权。
S1003、终端在上行资源上向网络设备发送第二消息。
其中，第二消息中包括上行数据和RRC连接恢复请求。
在该S1003中，当第一指示信息指示终端允许在上行授权指示的上行资源上进行上行传输时，终端就可以在接收到的上行授权指示的上行资源上进行上行传输。
S1004、终端在上行资源上向网络设备发送第三消息。
其中，第三消息用于请求恢复RRC连接，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行传输时，终端在上行授权指示的上行资源上发送的第三消息只用于请求恢复RRC连接，并不包括上行DRB数据。示例的，该第三消息可以为RRC连接恢复请求。
结合上述S1003和上述S1004中的描述，对应的，网络设备在接收到终端发送的第二消息或者第三消息之后，会向终端发送竞争解决信息，即执行下述S1005：
S1005、网络设备向终端发送竞争解决信息。
示例的，竞争解决信息可以为终端的标识，或者第二消息的部分信息、或者第三消息的部分信息。
终端在接收到竞争解决信息后，若此时还未接收到RRC连接释放消息，则终端启动或重启定时器，并在定时器运行期间，从网络设备接收授权；该授权可以为上行授权或者下行授权，并在接收到该授权时，重启定时器，从而延迟终端监听授权的时长。示例的，若从网络设备接收到的是上行授权，则终端启动或者重启定时器，并在该上行授权指示的上行资源上进行上行传输；若从网络设备接收到的是下行授权，且未接收到RRC连接释放消息，说明还有数据需要传输，则终端启动或重启定时器，等待RRC连接释放消息的时间，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
可以理解的是，定时器在启动或者重启之后，不是一直处于运行状态，而是在满足一定条件下停止定时器，例如以上描述的停止定时器的场景。例如，当终端从网络设备接收无线资源控制(RRC)连接释放消息时，控制定时器停止运行，即停止定时器。当终端从网络设备接收无线资源控制(RRC)连接恢复、连接建立消息等，终端也可以停止定时器。
可以看出，在上述图10所示的实施例中，终端向网络设备发送的第一消息中包括有前导码、RRC连接恢复请求和上行数据，当然，终端也可以在在第一消息中不携带上行数据，而是携带一个第二指示信息，该第二指示信息用于指示终端的待发送数据量与数据量门限的比较结果，在该种情况下，当网络设备解析前导码成功，但解析上行数据失败时，示例的，请参见图11所示，图11为本申请实施例提供的再一种配置方法的流程示意图， 该配置方法可以包括：
S1101、终端向网络设备发送第一消息。
其中，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据包括用于请求恢复无线资源控制(RRC)连接的信息，例如RRC连接恢复请求。示例的，随机接入请求可以为前导码，物理上行共享信道数据还可以包括第二指示信息，该第二指示信息用于指示终端的待发送数据量与数据量门限的比较结果。其中，第二指示信息是可选的。
可以理解的是，终端在向网络设备发送包括第二指示信息的第一消息时，在一种情况下，当第一消息为RRC连接恢复请求时，第二指示信息可以通过该RRC连接恢复请求中的一个布尔值表示，例如，当该布尔值为1时，表示待发送数据量大于数据量门限；当该布尔值为0时，表示待发送数据量小于数据量门限，反之也可以；对于待发送数据量等于数据量门限的情况下，布尔值可以为0，也可以为1。或者，第二指示信息可以通过该RRC连接恢复请求中的一个字段是否存在表示，当该RRC连接恢复请求中存在该字段，例如为TRUE时，表示待发送数据量小于数据量门限；当该RRC连接恢复请求中不存在该字段，例如为NULL时，表示待发送数据量大于数据量门限，反之也可以；对于待发送数据量等于数据量门限的情况下，RRC连接恢复请求中可以存在该字段，也可以不存在该字段。或者，第二指示信息可以通过该RRC连接恢复请求中的一个枚举型字段表示，当该RRC连接恢复请求中的字段为TRUE时，表示待发送数据量小于数据量门限；当该RRC连接恢复请求中的该字段为FALSE时，表示待发送数据量大于数据量门限，反之也可以；对于待发送数据量等于数据量门限的情况下，RRC连接恢复请求中该字段可以为TRUE，也可以为FALSE。
在另一种情况下，当第一消息为MAC消息时，该MAC消息例如为MAC子PDU，该MAC子PDU可以只包括MAC头，或者包括MAC头和MAC CE示例的，请参见图12，图12为本申请实施例提供的一种MAC消息的结构示意图。该MAC消息只包括MAC头，MAC头包括逻辑信道标识(LCH ID)，该LCH ID取预设值，表示MAC头值携带第二指示信息。第二指示信息可以通过该MAC头中的指示域实现，例如利用之前预留的比特位R来实现。该R比特的取值为1时，表示待发送数据量大于数据量门限；该R比特的取值为0时，表示待发送数据量小于数据量门限，反之也可以；当待发送数据量等于数据量门限时，该R比特的取值可以为0，也可以为1。
示例的，请参见图13，图13为本申请实施例提供的另一种MAC消息的结构示意图。该MAC消息包括MAC头和MAC CE，MAC CE中的字段携带第二指示信息。MAC头包括LCH ID，该LCH ID取预设值，表示MAC CE携带第二指示信息。以MAC CE中的1比特字段1携带该第二指示信息为例，该字段1的取值为1，表示待发送数据量大于数据量门限；该字段1的取值为0，表示待发送数据量小于数据量门限，反之也可以；当待发送数据量等于数据量门限时，该字段1的取值可以为0，也可以为1。
可以理解的是，终端在向网络设备发送包括第二指示信息的第一消息时，本申请实施例只是以该第一消息可以为RRC连接恢复请求消息或MAC消息为例进行说明，具体可以根据实际需要进行设置，在此，本申请实施例不做进一步地限制。
终端在向网络设备发送包括第二指示信息的第一消息之后，网络设备可以对第一消息 中包括的前导码和物理上行共享信道数据进行解析，当网络设备解析前导码成功，但解析物理上行共享信道数据失败时，网络设备会根据解析结果向终端发送第一消息的响应消息，即执行下述S1102：
S1102、网络设备向终端发送第一消息的响应消息。
其中，响应消息包括上行授权和第一指示信息，第一指示信息用于指示是否允许在上行授权指示的上行资源上进行上行传输。示例的，该第一消息的响应消息可以为RRC专用信令消息，例如RRC连接释放消息或者RRC重配置消息。
第一指示信息同以上描述，在此不再赘述。
需要说明的是，网络设备向终端发送第一消息的响应消息的方法与上述S1002中网络设备向终端发送第一消息的响应消息的方法类似，可参见上述S1002中的相关描述，在此，本申请实施例不再进行赘述。
同样可以看出，与现有技术中不同的是，在本申请实施例中，网络设备向终端发送的第一消息的响应消息中不仅包括上行授权信息，还进一步包括了第一指示信息。该第一指示信息指示的内容不同，对应的，终端在上行授权指示的上行资源上进行上行传输的方式也不同。当第一指示信息指示终端允许在上行授权指示的上行资源上进行上行传输时，可以执行下述S1103；相反的，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行DRB数据传输时，可以执行下述S1104。
S1103、终端在上行资源上向网络设备发送第二消息。
其中，第二消息中包括上行数据和RRC连接恢复请求。
在该S1103中，当第一指示信息指示终端允许在上行授权指示的上行资源上进行上行传输时，终端就可以在接收到的上行授权指示的上行资源上进行上行DRB数据传输。
S1104、终端在上行资源上向网络设备发送第三消息。
其中，第三消息用于请求恢复RRC连接，当第一指示信息指示终端不允许在上行授权指示的上行资源上进行上行传输时，终端在上行授权指示的上行资源上发送的第三消息只用于请求恢复RRC连接，并不包括上行数据。示例的，该第三消息可以为RRC连接恢复请求。
结合上述S1103和上述S1104中的描述，对应的，网络设备在接收到终端发送的第二消息或者第三消息之后，会向终端发送竞争解决信息，即执行下述S1105：
S1105、网络设备向终端发送竞争解决信息。
示例的，竞争解决信息可以为终端的标识，或者第二消息的部分信息、或者第三消息的部分信息。
终端在接收到竞争解决信息后，若此时还未接收到RRC连接释放消息，则终端启动或重启定时器，并在定时器运行期间，从网络设备接收授权；该授权可以为上行授权或者下行授权，并在接收到该授权时，重启定时器，从而延迟终端监听授权的时长。示例的，若从网络设备接收到的是上行授权，则终端启动或者重启定时器，并在该上行授权指示的上行资源上进行上行传输；若从网络设备接收到的是下行授权，且未接收到RRC连接释放消息，说明还有数据需要传输，则终端启动或重启定时器，等待RRC连接释放消息的时间，实现了终端在非激活态时完成上行传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC 连接恢复所需的开销。
可以看出，上述图10和图11所示的实施例详细描述了在一种场景中，当网络设备解析前导码成功，但解析上行数据失败的技术方案；下面，将详细描述在另一种场景中，当网络设备解析前导码成功，且解析上行数据成功的技术方案，示例的，请参见图14所示，图14为本申请实施例提供的又一种配置方法的流程示意图，该配置方法可以包括：
S1401、终端向网络设备发送第一消息。
其中，第一消息包括随机接入请求和/或物理上行共享信道数据，物理上行共享信道数据包括用于请求恢复RRC连接的信息。
需要说明的是，终端向网络设备发送第一消息的方法与上述S1001或S1101中终端向网络设备发送第一消息的方法类似，可参见上述S1001或S1101中的相关描述，在此，本申请实施例不再进行赘述。
当终端在向网络设备发送第一消息之后，网络设备可以对第一消息中包括的前导码和物理上行共享信道数据进行解析，当网络设备解析前导码成功，且解析物理上行共享信道数据成功时，网络设备会根据解析结果向终端发送第一消息的响应消息，即执行下述S1402：
S1402、网络设备向终端发送第一消息的响应消息。
其中，响应消息包括竞争解决信息。可选的，第一消息的响应消息还可以包括RAPID、TA及TC-RNTI。
此外，第一消息的响应消息中可以不包括上行资源和第一指示信息；当然，第一消息的响应消息中也可以包括上行资源和第一指示信息。
在响应消息为RRC连接释放消息时，终端恢复到起始状态，例如非激活态。
当第一消息的响应消息中不携带上行资源和第一指示信息时，终端在接收到该响应消息后，确定竞争解决通过，并启动或者重启定时器，将TC-RNTI转为C-RNTI。当第一消息的响应消息中携带上行资源和第一指示信息，且该第一指示信息用于指示“不允许在上行授权指示的上行资源上进行上行传输”，对应的，终端在接收到该响应消息后，确定竞争解决通过，并启动或者重启定时器。此时，终端可以在该上行资源上向网络设备发送响应消息的确认响应。当第一消息的响应消息中携带上行资源和第一指示信息，且该第一指示用于指示“允许在上行授权指示的上行资源上进行上行传输”，对应的，终端在接收到该响应消息后，确定竞争解决通过，并启动或者重启定时器。此时，终端可以在该上行资源上向网络设备发送上行数据。
可以理解的是，终端从网络设备接收到竞争解决信息的响应消息之后，说明网络设备已经成功接收到终端发送的物理上行共享信道数据。若此时终端还有待传输的上行数据，则终端还可以继续执行下述S1403-S1404：
S1403、从网络设备接收上行授权。
S1404、在上行授权指示的上行资源上进行上行传输。
终端在接收到竞争解决信息后，若此时还未接收到RRC连接释放消息，则终端启动或重启定时器，并在定时器运行期间，从网络设备接收授权，该授权用于上行数据发送或下行数据接收；可选的，该授权用于新传，不用于重传；该授权可以为上行授权或者下行授权，并在接收到该授权时，重启定时器，从而延迟终端监听授权的时长。示例的，若从 网络设备接收到的是上行授权，则终端启动或者重启定时器，并在该上行授权指示的上行资源上进行上行传输；若从网络设备接收到的是下行授权，且未接收到RRC连接释放消息，说明网络设备还有数据需要传输，则终端启动或重启定时器。终端通过以上方式延长等待RRC连接释放消息的时间，实现了终端在非激活态时的数据传输，而无需等到恢复RRC连接之后才能进行上行传输，无需终端进入连接态发送数据，不仅提高数据的发送效率，而且降低了RRC连接恢复所需的开销。
可以理解的是，在上述图10、图11及图14所示的实施例中，定时器在启动或者重启之后，不是一直处于运行状态，而是在满足一定条件下停止定时器，例如以上描述的停止定时器的场景。例如，当终端从网络设备接收无线资源控制RRC连接释放消息时，控制定时器停止运行，即停止定时器。当终端从网络设备接收无线资源控制(RRC)连接恢复、连接建立消息等，终端也可以停止定时器。
在上述图10、图11及图14所示的实施例中，在定时器运行期间，终端监听C-RNTI加扰的PDCCH，该PDCCH指示PUSCH资源，用于发送上行数据或BSR。或者，在定时器运行期间，终端监听C-RNTI加扰的PDCCH，该PDCCH指示PDSCH资源，用于接收下行数据。或者，在定时器运行期间，终端监听C-RNTI加扰的PDCCH，接收上行数据的下行反馈。
终端在每一次接收到C-RNTI加扰的PDCCH的上行授权或下行授权时，启动或重启定时器，以保持监听C-RNTI加扰的PDCCH的时长，与网络设备的C-RNTI加扰的PDCCH发送时间保持同步，并当定时器超时，终端停止监听C-RNTI加扰的PDCCH。
此外，现有技术中，当网络设备有下行数据需要发送时会先寻呼终端，对应的，终端在接收到该寻呼后，会向网络设备发起随机接入过程，之后，才能接收网络设备发送的下行数据。对于处于非连接态的终端，在小且稀疏数据发送场景下，由于终端需要先执行随机接入过程才能发送一个小数据，导致终端的开销大，而且也增加了传输时延。为了减低终端的开销，且降低传输时延，本申请实施例还提供了一种配置方法，示例的，请参见图15，图15为本申请实施例提供的一种配置方法的流程示意图，该配置方法可以包括：
S1501、网络设备向终端发送指示信息。
其中，指示信息用于指示终端在非激活态时监听物理下行控制信道(PDCCH)。
可选的，网络设备可以向终端发送RRC连接释放消息，该RRC连接释放消息包括指示信息，即网络设备可以将该指示信息携带在RRC连接释放消息中发送给终端，对应的，终端可以通过接收RRC连接释放消息获得该指示信息。可以理解的是，终端在接收到RRC连接释放消息后，会由连接态进入非激活态，进而根据该指示信息在非激活态监听PDCCH，如此可以针对终端独立配置其进行非激活态时监听PDCCH的功能，且在配置其进入非激活态的同时进行该功能配置，无需另外的信令单独指示，节约信令。网络设备也可以通过其它方式发送该指示信息，例如将该指示信息携带在广播消息中进行广播，对应的，终端可以通过接收该广播消息获取该指示信息，如此，不需要针对每个终端都单独进行非激活态时监听PDCCH的配置。在此，本申请实施例只是以这两种方式为例进行说明，但并不代表本申请实施例仅局限于此。
示例的，该指示信息可以通过一个比特实现，例如，该比特取值为1，表示启用在非激活态时监听C-RNTI加扰的物理下行控制信道(PDCCH)的功能，该比特取值为0，表 示不启用在非激活态时监听物理下行控制信道(PDCCH)的功能。或者，该指示信息也可以通过枚举型实现，例如：{TURE}，{downlink reception}。由于PDCCH通过小区无线网络临时标识(C-RNTI)加扰，故在另一种实现中，该指示信息可以为C-RNTI，例如，当RRC连接释放消息中携带C-RNTI时，则指示终端在非激活态监听该C-RNTI加扰的PDCCH；当RRC连接释放消息中未携带C-RNTI时，则指示终端在非激活态不监听PDCCH。
终端接收到网络设备发送的指示信息后，可以确定加扰PDCCH的C-RNTI，进而利用该C-RNTI监听该C-RNTI加扰的PDCCH。
在一种实现方式中，网络设备可以在RRC连接释放消息中向终端发送C-RNTI，此时RRC连接释放消息可以包括指示信息和C-RNTI，或者包括C-RNTI，同以上描述，该C-RNTI即为指示信息。
该C-RNTI在接入网通知区域(RAN notification area，RNA)或指示的小区或在当前接入小区内是有效的。例如，网络设备可以指示C-RNTI对应的RNA，其中C-RNTI对应到RNA可以为一个或多个，例如，网络设备指示C-RNTI对应的RNA标识(ID)或RNA ID列表，该RAN ID或RAN ID列表也可以携带在RRC连接释放消息中，或者携带在其它消息中。再如，网络设备可以指示C-RNTI对应的小区ID或小区ID列表，该小区ID或小区ID列表也可以携带在RRC连接释放消息中，或者携带在其它消息中。如此，终端可以在该RAN ID指示的RAN区域或小区ID指示的小区内使用C-RNTI监听PDCCH。当网络设备不指示RNA或小区的时候，可以认为C-RNTI在当前接入小区内是有效的，其中，当前接入小区是发送RRC连接释放消息的小区。在另一种实现方式中，网络设备可以不向终端发送C-RNTI，此时，终端可以通过使用在接入当前接入小区的随机接入过程中获取的C-RNTI，监听该C-RNTI加扰的PDCCH。其中，当前接入小区是发送RRC连接释放消息的小区。
终端在接收到该指示信息，并确定加扰PDCCH的C-RNTI之后，就可以根据该指示信息监听C-RNTI加扰的PDCCH，即执行下述S1502：
S1502、终端根据指示信息监听C-RNTI加扰的PDCCH。
下面描述，终端监听PDCCH的时机。示例的，在确定监听PDCCH的时机时，可以从时域和频域两个维度确定监听PDCCH的时机。
在时域方面确定监听PDCCH的时机时，终端可以将寻呼时机作为监听C-RNTI加扰的PDCCH的时机。具体，终端接收DRX配置参数，并根据非连续接收(discontinuous reception，DRX)配置参数确定寻呼时机，即监听寻呼无线网络临时标识(paging radio network temporary identifier，P-RNTI)加扰的PDCCH的时机；并且将该寻呼时机作为监听C-RNTI加扰的PDCCH的时机。示例的，请参见图16，图16为本申请实施例提供的一种确定监听C-RNTI加扰的PDCCH的时机的示意图。可选的，可以将该寻呼时机中的部分时间确定为监听C-RNTI加扰的PDCCH的时机，具体可以根据实际需要进行设置。
示例的，在根据DRX配置参数确定寻呼时机时，可以确定寻呼的无线帧，即确定系统帧号(system frame number，SFN)，其中，(SFN+PF_offset)mod T＝(T div N)*(终端_ID mod N)；及确定无线帧中的第i_s个寻呼时机，其中，i_s＝floor(终端_ID/N)mod Ns。其中，T表示终端的DRX周期，N表示DRX周期内的寻呼帧数，Ns表示寻呼帧内的寻 呼时机数，PF_offset表示用于确定寻呼无线帧的偏移值，终端_ID为终端标识，在不同通信系统中不同，例如，在5G系统中，其为5G-S-TMSI mod 1024。可以理解的是，T、N、Ns、PF_offset可以是网络设备配置给终端的。例如，通过广播消息配置给终端或者通过RRC专用消息配置给终端。
在根据DRX配置参数确定无线帧中监听P-RNTI PDCCH的寻呼时机后，可以在全部寻呼时机或寻呼时机的部分时间中监听C-RNTI加扰的PDCCH。在寻呼时机的部分时间监听C-RNTI加扰的PDCCH时，可以在每个寻呼时机的部分时长监听C-RNTI加扰的PDCCH，或者可以在部分寻呼时机监听C-RNTI加扰的PDCCH。
下面结合附图描述在每个寻呼时机的部分时长监听C-RNTI加扰的PDCCH，示例的，请参见图17，图17为本申请实施例提供的另一种确定监听C-RNTI加扰的PDCCH的时机的示意图。结合图17所示，图17中的阴影部分为监听C-RNTI加扰的PDCCH的时机。该监听C-RNTI加扰PDCCH的时机可以根据参数来确定，该参数可以是网络设备配置给终端的，或者预设的。例如，每个寻呼时机为N个时隙或者符号，该参数用于指示其中M个时隙或符号用于监听C-RNTI加扰的PDCCH。一种实现中，该参数用于指示M，终端默认前M或后M个时隙或符号用于监听C-RNTI加扰的PDCCH。另一种实现中，该参数用于指示第S个时隙或符号，则终端从第S个时隙或符号开始监听C-RNTI加扰的PDCCH或从第S个时隙或符号之后开始监听C-RNTI加扰的PDCCH。其中，M，N，S为正整数，且M和S小于N。
在部分寻呼时机监听PDCCH时，可以采用以上确定寻呼时机类似的方式，确定监听C-RNTI加扰的PDCCH的时机，例如，将以上确定SFN公式中的T修改为T1，其中，T1是T的整数倍，即(SFN+PF_offset)mod T＝(T1div N)*(终端_ID mod N)；确定确定无线帧中的寻呼时机i_s的方式不变。
此外，也可以结合以上两种方式，即在部分寻呼时机的部分时间监听C-RNTI加扰的PDCCH。示例的，请参见图18，图18为本申请实施例提供的再一种确定监听C-RNTI加扰的PDCCH的时机的示意图。结合图18所示，图18中的阴影部分为监听C-RNTI加扰的PDCCH的时机。
可选的，在另一种可能的实现方式中，确定监听C-RNTI加扰的PDCCH的时机和确定寻呼时机是独立的。示例的，可以采用类似确定寻呼时机的方式确定监听C-RNTI加扰的PDCCH的时机，区别在于采用的参数有所区别，例如采用的PF_offset不同。例如，在根据DRX配置参数确定监听C-RNTI加扰的PDCCH的时机时，可以确定无线帧的SFN，其中，(SFN+PF_offset1)mod T＝(T div N)*(终端_ID mod N)；及确定无线帧中的第i_s个监听时机，且i_s＝floor(终端_ID/N)mod Ns。其中，T表示终端的DRX周期，N表示DRX周期内的寻呼帧数，Ns表示寻呼帧内的寻呼时机数，PF_offset1表示用于确定C-RNTI PDCCH无线帧的偏移值，终端_ID为终端标识，在不同通信系统中不同，例如，在5G系统中，其为5G-S-TMSI mod 1024。可以理解的是，T、N、Ns、PF_offset1可以是网络设备配置给终端的。例如，通过广播消息配置给终端或者通过RRC专用消息配置给终端。其中PF_offset1和用于确定寻呼无线帧的偏移值PF_offset可以独立配置。使得监听C-RNTI加扰的PDCCH的时机与监听P-RNTI加扰的PDCCH的寻呼时机是独立的。示例的，请参见图19，图19为本申请实施例提供的又一种确定监听C-RNTI加扰的PDCCH的时机的 示意图。
在另一种可能的实现方式中，终端可以先确定寻呼无线帧的SFN，而后根据参数，确定监听C-RNTI加扰的PDCCH的无线帧，其中寻呼无线帧的SFN的确定方式同以上描述，即，(SFN+PF_offset)mod T＝(T div N)*(终端_ID mod N)；而后，终端根据偏移值确定监听C-RNTI加扰的PDCCH的无线帧(又称为C-RNTI PDCCH无线帧)的SFN，偏移值为PF_offset2标识，则C-RNTI PDCCH无线帧＝寻呼无线帧+PF_offset2，其中PF_offset2可以由网络设备配置给终端，也可以为预设值。而后，终端可以采用以上确定第i_s个寻呼时机相同的方式确定C-RNTI PDCCH无线帧内的监听C-RNTI加扰的PDCCH的时机，即监听时机。示例的，可参见图19。
此外，在终端移出C-RNTI的有效区域时，可以停止监听C-RNTI加扰的PDCCH。
由此可见，本申请实施例中，网络设备通过向终端发送指示信息，以通过指示信息指示终端在非激活态时监听C-RNTI加扰的PDCCH，这样终端可以在监听C-RNTI加扰的PDCCH的过程中接收下行数据，该整个接收过程对于终端而言，无需接收寻呼，也无需发起RRC连接恢复请求，而是直接在非激活态接收下行数据，不仅提高了传输效率，而且降低了终端的开销。
在无线通信系统，例如5G通信系统、或LTE通信系统中，终端接入小区后，小区所属的网络设备会生成该终端的上下文，终端也会根据网络设备发送的配置消息生成该终端的上下文。终端的RRC状态改变后，网络设备会对终端上下文进行处理。例如终端从RRC连接态(简称为连接态)转换到RRC空闲态(简称为空闲态)，网络设备会释放终端的上下文。再如，当终端从连接态转换为inactive态时，终端和网络设备保存部分接入层的配置(称为接入层终端的上下文)和非接入层配置(称为非接入层终端的上下文)。终端可周期性地向网络设备发起接入网通知区域更新(RAN-based Notification Area Update，R-NAU)过程，告知网络设备终端所在的接入网通知区域(RAN-based Notification Area，RNA)。当inactive态的终端重选到新的小区，向新的小区所属的网络设备发起R-NAU过程，告知网络设备终端所在的RNA。
当网络设备收到终端的下行数据时，在终端所在的RNA的小区里寻呼终端。终端收到寻呼后，发起从inactive态到连接态的状态转换过程，网络设备通知终端恢复保存的接入层的配置，待终端进入连接态后网络设备向终端发送下行数据。当终端有上行数据待发送时，终端发起从inactive态到连接态的状态转换过程，网络设备通知终端恢复保存的接入层的配置，终端进入连接态后发送上行数据。
终端从inactive态到连接态的状态转换过程中，终端需要向网络设备发送RRC连接恢复(resume)请求消息，为了检测RRC连接恢复是否成功，引入了T319定时器，终端启动该T319定时器，向网络设备发送RRC连接恢复请求消息，且在收到网络设备发送的RRC连接恢复、RRC连接建立、或RRC连接释放消息等RRC响应消息时，停止该T319定时器。当T319到期时，终端以RRC连接恢复失败的原因释放连接进入空闲态。
对于终端有少量数据传输的场景，可以在inactive态进行上行数据传输。例如在终端在发送RRC连接恢复(resume)请求消息的同时向网络设备发送上行数据。在以上实施例中，已经给出inactive态的终端在发送“RRC连接恢复请求”消息后，后续可以继续发送数据，且后续发送数据时可以不携带RRC连接恢复请求消息，以降低信令开销。可是， 终端发送后续数据时，如果T319定时器超时，终端将进入RRC空闲态，无法灵活支持多次数据的发送。
在以上图10、图11及图14所示的实施例中，终端在满足一定条件下，可以重启T319定时器，如此可以延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。当然，也可以启动新的定时器，示例的，该新的定时器可以为除T319定时器之外的RRC层定时器或MAC层定时器，使得终端在满足一定条件下启动该新的定时器，并在该新的定时器运行期间进行数据传输，同样可以延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。示例的，可参见本申请实施例提供的方法，终端在应RRC连接恢复的需求时，启动第一定时器，并向网络设备发送RRC连接恢复请求消息；这样在第一定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启第一定时器；或者，在第一定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动第二定时器。可以看出，在本申请实施例中，通过重启第一定时器或者启动第二定时器，使得在第一定时器或者第二定时器运行期间进行数据传输，可以有效地延长了终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。
基于上述描述不难看出，本申请实施例提供的配置方法可以包括至少两种可能的场景。在一种可能的场景中，终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足重启条件，重启该第一定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以看出，在该种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器为同一个定时器，均为第一定时器。在另一种可能的场景中，终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足启动条件时，启动第二定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以看出，在该种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器不是一个定时器，而是额外设置的一个新的定时器。可以理解的是，在该种可能的场景中，在启动第二定时器之后，还可以停止第一定时器；当然，也可以先停止第一定时器，接着启动第二定时器，或者在启动第二定时器的同时，停止第一定时器。如此，用第二定时器接替第一定时器工作，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。
需要说明的是，上述两种可能的场景中的相关描述，可以理解为通过第一定时器或者第二定时器执行第一次延长操作时的方案。对于上述第一种可能的实现方式中的第一定时器而言，终端向网络设备发送RRC连接恢复请求消息，且启动第一定时器，并在满足重启条件时，重启该第一定时器，以执行第一次延长操作；后续可以执行第二次延长操作，或者第三次延长操作，……。在之后的第M(M大于或等于1)次延长操作时，终端可以无需向网络设备发送RRC连接恢复请求消息，而是直接发送上行数据，并在满足重启条件时，重启该第一定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。对于上述第二种可能的实现方式中的第二定时器而言，终端向网络设备发送RRC连接恢复请求消息，且启动第一定时器；并在满足启动条件时，启动该第二定时器，以执行第一次延长操作；而后在可以在满足重启条件时，执行第二次延长操作，或者第三次延长操作……。在之后的第M(M大于或等于1)次延长操作时，终端可以无需向网络设备发送 RRC连接恢复请求消息，而是直接发送上行数据，并在满足启动或重启条件时，启动或重启该第二定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。
为了便于理解本申请实施例提供的配置方法，下面，将分别针对上述两种可能的场景，对本申请实施例提供的配置方法进行详细地说明。
首先，对于上述第一种可能的场景，即终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足重启条件，重启该第一定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。示例的，在该种可能的场景中，在通过重启第一定时器延长终端等待RRC连接恢复请求的RRC响应消息的时间时，可以包括下述至少三种可能的实现方式。在一种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，即终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器。在另一种可能的实现方式中，该第一定时器可以为RRC层额外设置的，除T319定时器之外的一个新定时器T1，即终端在应RRC连接恢复的需求时，先启动新定时器T1，并向网络设备发送RRC连接恢复请求消息；这样在新定时器T1运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该新定时器T1。在又一种可能的实现方式中，该第一定时器可以为额外设置的，除T319定时器之外的一个新定时器T2，与上述第二种可能的实现方式中定时器T1不同的是，该新定时器T2是设置在MAC层中的定时器，即终端在应RRC连接恢复的需求时，先启动新定时器T2，并向网络设备发送RRC连接恢复请求消息；这样在新定时器T2运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该新定时器T2。下面，将分别针对上述三种可能的实现方式，详细描述如何通过控制第一定时器重启，以延长终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。
在上述第一种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，即终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器。需要说明的是，在该种可能的实现方式中，将以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启该T319定时器为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输重启该T319定时器。示例的，请参见图20所示，图20为本申请实施例提供的一种配置方法的流程示意图，该配置方法可以包括：
S2001、终端在应RRC连接恢复的需求时，启动T319定时器。
终端在启动T319定时器之前，先配置该T319定时器的时长，使得该T319定时器可以基于配置的时长进行运行。示例的，在配置该T319定时器的时长时，终端可以从网络设备接收广播消息或RRC消息，并根据该广播消息或RRC消息中包括的指示T319定时器时长的信息，配置该T319定时器的时长。其中，该T319定时器的时长可以为目前网络配置的T319定时器的第一时长，示例的，该第一时长可以为{100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms}中的某一值，也可以大于目前网络配置的T319定时器的一个第二时长，该第二时长可以通过广播消息或RRC消息进行配置，例如，第二时长为 {100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms，2500ms}中的某一值，示例的，第二时长可以为2500ms。由于在满足重启条件时，均会重启该T319定时器，因此，对于这两种不同的时长，均可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以理解的是，在T319定时器的配置时长变长时，终端和网络设备进行数据传输的时间变长，便于终端网络设备进行多次数据传输。
当T319定时器被配置了上述两种不同的时长时，在启动定时器之前，先确定该T319定时器采用哪一种时长，即第一时长或者第二时长。在确定该T319定时器采用哪一种时长，若终端满足下述条件之一，则确定该T319定时器的时长采用第二时长。条件1，终端期望非激活态的连续上行数据传输；条件2：终端不能在非激活态一次性发完上行数据；条件3，终端待发送数据量大于预配置门限；条件4，终端支持非激活态的上行数据传输；条件5，终端被配置了时长2的T319定时器。在该种情况下，终端在确定该T319定时器的时长采用第二时长之后，可选的，终端还可以向网络设备发送一个指示信息，该指示信息用于指示网络设备，终端启动的T319定时器的时长为第二时长，从而将已经启动该T319定时器的信息同步给网络设备。可以理解的是，通过指示信息将终端已经启动该T319定时器的信息同步给网络设备的操作可以仅在第一次执行启动操作时执行，在后续重启的操作中，终端可以无需再向网络设备发送该指示信息。
S2002、终端向网络设备发送RRC连接恢复请求消息。
示例的，RRC连接恢复请求消息可以包括I-RNTI、终端的身份验证信息，以及UE发起RRC连接恢复请求的原因值中的至少一种。其中，I-RNTI用于表示终端在一个RNA范围的唯一标识。终端的身份验证信息是根据终端存储的C-RNTI和RRC完整性密钥生成的身份验证信息。
终端在向网络设备发送RRC连接恢复请求消息时，可以通过配置授权信息指示的上行资源向网络设备发送RRC连接恢复请求消息。示例得，该配置授权信息可以从网络设备的广播消息中获取，也可以从网络设备向终端发送的专用消息中获取。示例的，终端除了向网络设备发送RRC连接恢复请求消息之外，还可以向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息。其中，辅助信息用于指示终端缓存中的数据量，以使网络设备根据终端缓存中的数据量确定终端进入连接态或者继续处于非激活态。当终端向网络设备发送上行数据时，该上行数据与RRC连接恢复请求消息共同发送或独立发送。本申请中的共同发送或者独立发送是指上行数据与RRC连接恢复请求消息是否通过同一个消息，例如MAC PDU消息发送，若上行数据与RRC连接恢复请求消息通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息共同发送；相反的，上行数据与RRC连接恢复请求消息不是通过同一个消息发送，则可以理解为上行数据与RRC连接恢复请求消息独立发送。此外，若上行数据与RRC连接恢复请求消息独立发送，则可以在在RRC连接恢复请求消息发送之后，在第一定时器运行期间内发送该上行数据。
终端在向网络设备发送RRC连接恢复请求消息之后，对应的，网络设备可以根据该RRC连接恢复请求消息向终端发送相应的下行信息，即执行下述S2003：
S2003、网络设备根据RRC连接恢复请求消息向终端发送下行信息。
若终端仅向网络设备发送了RRC连接恢复请求消息，则网络设备向终端发送的下行 信息中包括该RRC连接恢复请求消息的反馈信息。若终端向网络设备发送了RRC连接恢复请求消息和上行数据，则网络设备向终端发送的下行信息中包括RRC连接恢复请求消息和上行数据的反馈信息。
示例的，若终端仅向网络设备发送了RRC连接恢复请求消息，则下行信息中可以包括下述至少一种：RRC连接恢复请求消息的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息。其中，该指示信息用于指示终端重启该T319定时器，当然，该下行信息也可以包括其它信息，在此，本申请实施例只是以该下行信息包括RRC连接恢复请求消息的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息中的至少一种为例进行说明，但并不代表本申请实施例仅局限于此。若终端向网络设备发送了RRC连接恢复请求消息和上行数据，则下行信息中可以包括下述至少一种：RRC连接恢复请求消息的反馈信息、上行数据的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息。当然，该下行信息也可以包括其它信息，在此，本申请实施例只是以该下行信息包括RRC连接恢复请求消息的反馈信息、上行数据的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息中的至少一种为例进行说明，但并不代表本申请实施例仅局限于此。
网络设备在接收到终端发送的RRC连接恢复请求消息，或者，终端发送的RRC连接恢复请求消息和上行数据之后，可以基于接收到的RRC连接恢复请求消息，或者，RRC连接恢复请求消息和上行数据生成的相应的下行信息，并将生成的下行信息发送给终端。示例的，网络设备在将生成的信息发送给终端时，可以将该生成的信息携带在PDCCH的下行控制信息、MAC消息、或者RRC消息中发送给终端。
S2004、终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器。
结合上述S2003中的相关描述，在终端仅向网络设备发送了RRC连接恢复请求消息的情况下，终端从网络设备接收到的下行信息中包括该RRC连接恢复请求消息的反馈信息，该RRC连接恢复请求消息的反馈信息指示RRC连接恢复请求消息是否成功传输，该反馈信息为ACK或者NACK。若反馈信息为ACK，则说明RRC连接恢复请求消息发送成功，终端可以继续在配置授权上进行新的上行数据的发送；若反馈信息为NACK，则说明RRC连接恢复请求消息发送失败，终端可以继续在配置授权上进行RRC连接恢复请求消息的重传。在该种情况下，终端从网络设备接收到的下行信息中还可以包括竞争解决信息，该竞争解决信息可以为上述图10所示的实施例中S1005中的竞争解决信息，也可以为上述图11所示的实施例中S1105中的竞争解决信息，若竞争解决信息为竞争解决成功，则说明RRC连接恢复请求消息发送成功，终端可以继续在预配授权上进行新的上行数据的发送；若竞争解决信息为竞争解决失败，则说明RRC连接恢复请求消息发送失败，终端可以继续在预配授权上进行RRC连接恢复请求消息的重传。
若终端从网络设备接收到的下行信息中包括该RRC连接恢复请求消息的反馈信息，则终端重启T319定时器，并在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。
在终端向网络设备发送了RRC连接恢复请求消息和上行数据的情况下，终端从网络设备接收到的下行信息中包括该RRC连接恢复请求消息和上行数据的反馈信息，该RRC连接恢复请求消息和上行数据的反馈信息指示RRC连接恢复请求消息和上行数据是否成功传输，该反馈信息为ACK或者NACK。若反馈信息为ACK，则说明RRC连接恢复请求消息和上行数据发送成功，终端可以继续在配置授权上进行新的上行数据的发送；若反馈信息为NACK，则说明RRC连接恢复请求消息和/或上行数据发送失败，终端可以继续在配置授权上进行RRC连接恢复请求消息的重传，和/或，原上行数据中的部分数据或全部数据的重传。同样的，在该种情况下，终端从网络设备接收到的下行信息中还可以包括竞争解决信息，该竞争解决信息也可以为上述图10所示的实施例中S1005中的竞争解决信息，也可以为上述图11所示的实施例中S1105中的竞争解决信息，若竞争解决信息为竞争解决成功，则说明RRC连接恢复请求消息和上行数据发送成功，终端可以继续在预配授权上进行新的上行数据的发送；若竞争解决信息为竞争解决失败，则说明RRC连接恢复请求消息和/或上行数据发送失败，终端可以继续在预配授权上进行RRC连接恢复请求消息的重传，和/或，原上行数据中的部分数据或全部数据的重传。
若终端从网络设备接收到的下行信息中包括该RRC连接恢复请求消息和上行数据的反馈信息，则终端重启T319定时器，并在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。
针对上述两种情况，终端接收到的下行信息除了可能包括反馈信息和/或竞争解决信息之外，终端接收到的下行信息还可以包括上行授权信息，该上行授权信息指示的上行资源可以用于原上行数据的重传，也可以用于新上行数据的初传，实现连续多次包的数据传输。通常情况下，若有原上行数据需要重传，且有新上行数据需要初传，则可以先通过该上行授权信息指示的上行资源进行新上行数据的初传，即数据初传的传输优先级高于数据重传的传输优先级。示例的，终端接收到的下行信息还可以包括下行资源分配信息，该下行资源分配信息指示的下行资源可以用于原下行数据的重传，也可以用于新下行数据的初传，实现下行数据早传。需要说明的是，在本申请实施例中，上行授权信息和下行资源分配信息可以独立存在，即终端接收到的下行信息中可以包括上行授权信息，或者下行资源分配信息；上行授权信息和下行资源分配信息可以同时存在，即终端接收到的下行信息中可以同时包括上行授权信息和下行资源分配信息。若终端从网络设备接收到的下行信息中包括该上行授权信息和/或下行资源分配信息，则终端重启T319定时器，并在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。优选地，若终端从网络设备接收到的下行信息中包括用于初传的上行授权信息和/或用于下行初传的下行资源分配信息，则终端重启T319定时器。
此外，由于终端是根据从网络设备接收到的下行信息重启该T319定时器，示例的，终端接收到的下行信息可以包括一个指示信息，该指示信息可以携带在物理层控制信令、MAC层消息或者RRC层消息中，该指示信息用于指示终端重启该T319定时器；对应的，终端在接收到包括该指示信息的信息后，可以重启该T319定时器，使得在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。
综上所述，终端在T319定时器运行期间，终端在根据从网络设备接收到的下行信息 重启该T319定时器时，若终端接收到的下行信息中包括反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则重启T319定时器，使得在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送。示例的，终端接收到的下行信息还包括定时调整命令和/或功率控制命令。其中，在接收到该定时调整命令时，应用该定时调整命令进行上行传输定时调整；在接收到该功率控制命令时，应用该功率控制命令进行功率控制。
终端在根据接收到的下行信息重启该T319定时器之后，若当前T319定时器为初次启动，则终端还可以通过向网络设备发送一个指示信息，该指示信息用于指示网络设备重启的T319定时器，从而将已经重启该T319定时器的信息同步给网络设备。并且，对于该T319定时器而言，在重启之后，该T319定时器不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该T319定时器。
通过执行上述S2001-S2004，即终端在应RRC连接恢复的需求时，启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启T319定时器，并在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送。上述整个过程，可以理解为终端执行第一次延长操作，在执行完第一次延长操作后，还可以在T319定时器重启并运行期间，根据从网络设备接收到的下行信息再次控制重启该T319定时器，以再次延长终端等待RRC连接恢复请求消息的RRC响应的时间，该过程可以理解为终端执行第二次延长操作。可以理解的是，终端执行第三次延长操作、或者之后的第N(N大于3)次延长操作的方法与终端执行第一次延长操作的方法类似，在此，本申请实施例以在执行完第一次延长操作后，还可以在T319定时器重启并运行期间，根据从网络设备接收到的下行信息再次控制重启T319定时器为例进行说明，示例的，在执行完上述S2004根据从网络设备接收到的下行信息重启该T319定时器之后，还可以进一步执行下述S2005-S2007：
S2005、终端在T319定时器运行期间，向网络设备发送上行数据。
终端在向网络设备发送上行数据时，可以通过配置授权信息系指示的上行资源向网络设备发送上行数据。示例得，该配置授权信息可以从网络设备的广播消息中获取，也可以从网络设备向终端发送的专用消息(例如RRC消息)中获取。
可以看出，在执行第M次(M大于或等于1)延长操作时，终端可以不向网络设备发送RRC连接恢复请求消息，而是直接发送上行数据，并在满足重启条件时，重启该T319定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。
S2006、网络设备根据上行数据向终端发送下行信息。
示例的，该下行信息中可以包括上行数据的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息。当然，该下行信息也可以包括其它信息，在此，本申请实施例只是以该下行信息包括上行数据的反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息中的至少一种为例进行说明，但并不代表本申请实施例仅局 限于此。
网络设备在接收到终端发送的上行数据之后，可以基于接收到的上行数据生成的相应的下行信息，并将生成的下行信息发送给终端。示例的，网络设备在将生成的信息发送给终端时，可以将该生成的信息携带在PDCCH的下行控制信息、MAC消息、或者RRC消息中发送给终端。
S2007、终端在T319定时器运行期间，根据从网络设备接收到的下行信息再次重启该T319定时器。
终端在根据从网络设备接收到的下行信息第二次重启该T319定时器时，若终端接收到的下行信息中包括反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则重启T319定时器，即执行第二次延长操作，使得在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送，具体可以参见上述S2004中的相关描述，在此，本申请实施例不再进行赘述。可以理解的是，该T319定时器在第二次重启之后，同样不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该T319定时器。
在该种可能的实现方式中，在重启T319定时器时，只是以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息，重启该T319定时器为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输重启该T319定时器，例如，在T319定时器运行期间，若终端发送了上行数据，例如，专用传输信道(dedicated traffic channel，DTCH)的数据，则重启T319定时器；或者，若接收到下行数据，例如，DTCH的数据，则重启T319定时器。
上述图20所示的实施例，详细描述了第一种可能的实现方式中，当第一定时器为目前网络配置的T319定时器，终端在应RRC连接恢复的需求时，先启动该T319定时器，并向网络设备发送RRC连接恢复请求消息；在该T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启该T319定时器的技术方案。下面，将描述在上述第二种可能的实现方式中，当第一定时器可以为RRC层额外设置的，除T319定时器之外的一个新定时器T1时，终端在应RRC连接恢复的需求时，先启动新定时器T1，并向网络设备发送RRC连接恢复请求消息；在新定时器T1运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该新定时器T1的技术方案。
在该第二种可能的实现方式中，与上述图20所示的实施例不同的是，该种可能的实现方式中的第一定时器不再是T319定时器，而是RRC层额外设置的，除T319定时器之外的一个新定时器T1，即终端在应RRC连接恢复的需求时，启动的是该新定时器T1，并在新定时器T1运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T1，以延长终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。在该种可能的实现方式中，可不启动T319定时器。
终端在启动新定时器T1之前，先配置该新定时器T1的时长，使得该新定时器T1可以基于配置的时长进行运行，该新定时器T1的时长的配置方法与上述图20所示的实施例中T319定时器的时长的配置方法类似，在此，本申请实施例不再进行赘述。至于在新定时器T1启动之后，如何向网络设备发送RRC连接恢复请求消息，并在新定时器T1运行 期间，如何根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T1的方法与上述图20所示的实施例中，在T319定时器启动之后，向网络设备发送RRC连接恢复请求消息，并在T319定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该T319定时器的方法类似，具体可参见上述相关描述，在此，对于在新定时器T1启动之后，如何向网络设备发送RRC连接恢复请求消息，以及在新定时器T1运行期间，如何根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T1，本申请实施例不再进行赘述。
在该种可能的实现方式中，与上述图20所示的实施例不同的是，该种可能的实现方式中的第一定时器不是T319定时器，而是RRC层额外设置的，除T319定时器之外的一个新定时器T1，为了节省终端因T319定时器运行产生的功耗，在该种可能的实现方式中，可不启动T319定时器。对于该新定时器T1而言，在重启之后，该新定时器T1不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该新定时器T1。
在上述第三种可能的实现方式中，当第一定时器为MAC层设置的一个新定时器T2时，终端在应RRC连接恢复的需求时，先启动新定时器T2，并向网络设备发送RRC连接恢复请求消息；在新定时器T2运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该新定时器T2的技术方案。
在该第三种可能的实现方式中，与上述图20所示的实施例不同的是，该种可能的实现方式中的第一定时器不是T319定时器，而是MAC层设置的一个新定时器T2，即终端在应RRC连接恢复的需求时，启动的是该新定时器T2，并在新定时器T2运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T2，以延长终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。在该种可能的实现方式中，可不启动T319定时器。
终端在启动新定时器T2之前，先配置该新定时器T2的时长，使得该新定时器T2可以基于配置的时长进行运行，该新定时器T2的时长的配置方法与上述图20所示的实施例中T319定时器的时长的配置方法类似，在此，本申请实施例不再进行赘述。至于在新定时器T2启动之后，如何向网络设备发送RRC连接恢复请求消息，并在新定时器T2运行期间，如何根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T2的方法与上述图20所示的实施例中，在T319定时器启动之后，向网络设备发送RRC连接恢复请求消息，并在T319定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该T319定时器的方法类似，具体可参见上述相关描述，在此，对于在新定时器T2启动之后，如何向网络设备发送RRC连接恢复请求消息，以及在新定时器T2运行期间，如何根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输重启该新定时器T2，本申请实施例不再进行赘述。
在该种可能的实现方式中，与上述图20所示的实施例不同的是，该种可能的实现方式中的第一定时器不是T319定时器，而是MAC层的一个新定时器T2，为了节省终端因T319定时器运行产生的功耗，在该种可能的实现方式中，同样可不启动T319定时器。对于该新定时器T2而言，在重启之后，该新定时器T2不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时， 停止该新定时器T2。在重启该新定时器T2之后，若该定时器T2超时，则终端的MAC层会通知RRC层该定时器T2超时，终端的MAC层根据该定时器T2超时信息终端终端进入空闲态。
在详细描述完第一种可能的场景，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器为同一个定时器，均为第一定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送的技术方案。下面，将详细描述在另一种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器不是同一个定时器，而是额外设置的一个新的定时器的技术方案，即终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足启动条件时，启动第二定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以理解的是，在该种可能的场景中，在启动第二定时器之后，还可以停止第一定时器；当然，也可以先停止第一定时器，接着启动第二定时器。
示例的，在该种可能的场景中，在通过启动第二定时器延长终端等待RRC连接恢复请求的RRC响应消息的时间时，可以包括下述至少两种可能的实现方式。在一种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，第二定时器可以为RRC层额外设置的，除T319定时器之外的一个新定时器，为了区分上述实施例中的新定时器T1，本申请中该新定时器可以记为新定时器T3，该新定时器T3可以为上述实施例中的新定时器T1，也可以为额外设置的新的定时器。即，终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动该新定时器T3。在一种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，第二定时器可以为MAC层额外设置的一个新定时器，为了区分上述实施例中的新定时器T2，本申请中该新定时器可以记为新定时器T4，该新定时T4可以为上述实施例中的新定时器T2，也可以为额外设置的新的定时器。即，终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动该新定时器T4。可以理解的是，在该种可能的场景中，在启动第二定时器之后，还可以停止第一定时器。下面，将分别针对两种可能的实现方式，详细描述在该种可能的场景中，如何通过控制第二定时器启动，以延长终端等待RRC连接恢复请求的RRC响应消息的时间，从而灵活地支持多次数据的发送。
在上述第一种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，第二定时器可以为RRC层额外设置的，除T319定时器之外的一个新定时器T3。即，终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动该新定时器T3。在该种可能的实现方式中，将以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息启动或重启该新定时器T3为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输启动或重启该新定时器T3。示例的，请参见图21所示，图21为本申请实施例提供的一种另配置方法的流程示意图，该配置方法可以包括：
S2101、终端在应RRC连接恢复的需求时，启动T319定时器。
终端在启动T319定时器之前，先配置该T319定时器的时长，使得该T319定时器可以基于配置的时长进行运行。在该S2101中，T319定时器时长的配置方法与上述实施例中S2001中T319定时器时长的配置方法类似，具体可参见上述配置T319定时器的时长的相关描述，在此，本申请实施例不再进行赘述。
在启动T319定时器之后，就可以向网络设备发送RRC连接恢复请求消息，即执行下述S2102：
S2102、终端向网络设备发送RRC连接恢复请求消息。
示例的，RRC连接恢复请求消息可以包括I-RNTI、终端的身份验证信息，以及UE发起RRC连接恢复请求的原因值中的至少一种。其中，I-RNTI用于表示终端在一个RNA范围的唯一标识。终端的身份验证信息是根据终端存储的C-RNTI和RRC完整性密钥生成的身份验证信息。
在该S2102中，终端向网络设备发送RRC连接恢复请求消息的方法与上述S2002中终端向网络设备发送RRC连接恢复请求消息的方法类似，具体可以参见上述S2002中终端向网络设备发送RRC连接恢复请求消息的相关描述，在此，对于终端向网络设备发送RRC连接恢复请求消息的方法，本申请实施例不再进行赘述。
在该S2102中，终端除了向网络设备发送RRC连接恢复请求消息之外，也可以向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息，这些信息的发送方式与上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的发送方式类似，可参见上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的相关描述，在此，本申请实施例不再进行赘述。与上述S2002不同的是，在本申请实施例中，由于除了T319定时器之外，还有RRC层额外设置的一个新定时器T3，因此，终端还可以再向网络设备发送一个启动指示信息，该启动指示信息用于指示后续在T319定时器运行期间，若满足启动条件，则启动该新定时器T3，从而实现终端启动的新定时器T3和网络设备启动的新定时器T3的同步。
终端在向网络设备发送RRC连接恢复请求消息之后，对应的，网络设备可以根据该RRC连接恢复请求消息向终端发送相应的下行信息，即执行下述S2103：
S2103、网络设备根据RRC连接恢复请求消息向终端发送下行信息。
在S2103中，网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法与上述上述图20所示的实施例中，S2003网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法类似，可参见上述S2003中的相关描述，在此，本申请实施例不再进行赘述。
S2104、终端在T319定时器运行期间，根据从网络设备接收到的下行信息启动新定时器T3。
终端在启动新定时器T3之前，先配置该启动新定时器T3的时长，使得该启动新定时器T3可以基于配置的时长进行运行。示例的，在配置该新定时器T3的时长时，终端可以从网络设备接收广播消息或RRC消息，并根据该广播消息或RRC消息中包括的指示新定时器T3时长的信息，配置该新定时器T3的时长。对于该指示新定时器T3时长的信息的获取方式，该指示新定时器T3时长的信息可以与指示T319定时器时长的信息通过同一个 广播消息或RRC消息获取，也可以通过不同的广播消息或RRC消息获取，具体可以根据实际需要进行设置。对于该指示新定时器T3时长的信息的获取时间，该指示新定时器T3时长的信息可以与指示T319定时器时长的信息在同一时间获取，也可以在不同的时间获取，例如，在确定启动该新定时器T3时，再获取该指示新定时器T3时长的信息，具体可以根据实际需要进行设置。
其中，该新定时器T3的时长可以为目前网络配置的T319定时器的第一时长，示例的，该第一时长可以为{100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms}中的某一值，也可以大于目前网络配置的T319定时器的一个第二时长，该第二时长可以通过广播消息或RRC消息进行配置，例如，第二时长为{100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms，2500ms}中的某一值，示例的，第二时长可以为2500ms。由于在满足启动条件时，均会启动该新定时器T3，因此，对于这两种不同的时长，均可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以理解的是，在新定时器T3的配置时长变长时，终端和网络设备进行数据传输的时间变长，便于终端网络设备进行多次数据传输。
在配置了新定时器T3的时长之后，就可以执行S2104终端在T319定时器运行期间，根据从网络设备接收到的下行信息启动新定时器T3。S2104终端在T319定时器运行期间，根据从网络设备接收到的下行信息启动新定时器T3的方法与上述S2004中终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法类似，可参见上述S2004中的相关描述，在此，对于终端在T319定时器运行期间，如何根据从网络设备接收到的下行信息启动新定时器T3的方法，本申请实施例不再进行赘述。
综上所述，终端在T319定时器运行期间，终端在根据从网络设备接收到的下行信息启动新定时器T3时，若终端接收到的下行信息中包括上行数据的反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则启动新定时器T3，使得在新定时器T3运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。若T319定时器还在运行状态，则可以停止T319定时器。例如，先启动新定时器T3，并在新定时器T3启动后，停止T319定时器；或者可以在启动新定时器T3的同时停止T319定时器。示例的，终端接收到的下行信息还包括定时调整命令和/或功率控制命令。在接收到该定时调整命令时，应用该定时调整命令进行上行传输定时调整；在接收到该功率控制命令时，应用该功率控制命令进行功率控制。
终端在根据接收到的下行信息启动该新定时器T3之后，由于该新定时器T3为初次启动，则终端还可以通过向网络设备发送一个指示信息，该指示信息用于指示网络设备启动的新定时器T3，从而将已经启动新定时器T3的信息同步给网络设备。并且，对于该新定时器T3而言，在启动之后，该新定时器T3不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该新定时器T3。
通过执行上述S2101-S2104，即终端在应RRC连接恢复的需求时，启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息启动新定时器T3，并在新定时器T3运行期间进行数据传输， 可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送。上述整个过程，可以理解为终端执行第一次延长操作，在执行完第一次延长操作后，还可以在新定时器T3启动并运行期间，根据从网络设备接收到的下行再次控制重启新定时器T3，以再次延长终端等待RRC连接恢复请求消息的RRC响应的时间，该过程可以理解为终端执行第二次延长操作。可以理解的是，终端执行第三次延长操作、或者之后的第N(N大于3)次延长操作的方法与终端执行第一次延长操作的方法类似，在此，本申请实施例以在执行完第一次延长操作后，还可以在新定时器T3启动并运行期间，根据从网络设备接收到的下行信息控制重启新定时器T3为例进行说明，示例的，在执行完上述S2104根据从网络设备接收到的下行信息启动该新定时器T3之后，还可以进一步执行下述S2105-S2107：
S2105、终端在新定时器T3运行期间，向网络设备发送上行数据。
S2106、网络设备根据上行数据向终端发送下行信息。
S2107、终端在新定时器T3运行期间，根据从网络设备接收到的下行信息重启该新定时器T3。
在S2105-S2107中，终端在新定时器T3运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息，对应的，终端在新定时器T3运行期间，根据从网络设备接收到的下行信息重启该新定时器T3的方法，与上述图20所示的实施例中，S2005-S2007中，终端在T319定时器运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息，对应的，终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法类似，可参见上述S2005-S2007中的相关描述，在此，本申请实施例不再进行赘述。
由于通过上述S2001-S2004执行第一次延长操作时，本身就是通过重启T319定时器延长终端等待RRC连接恢复请求消息的RRC响应的时间，因此，在上述S2007中执行第二次延长操作时，是第二次重启T319定时器以延长终端等待RRC连接恢复请求消息的RRC响应的时间。而在本申请实施例中，与上述S2007不同的是，由于通过上述S2101-S2104执行第一次延长操作时，是通过首次启动新定时器T3延长终端等待RRC连接恢复请求消息的RRC响应的时间，因此，在该S2107中执行第二次延长操作时，是第一次重启新定时器T3以延长终端等待RRC连接恢复请求消息的RRC响应的时间。
终端在根据从网络设备接收到的下行信息第一次重启该新定时器T3时，若终端接收到的下行信息中包括反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则重启新定时器T3，即执行第二次延长操作，使得在新定时器T3运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送，具体可以参见上述S2004中的相关描述，在此，本申请实施例不再进行赘述。可以理解的是，该新定时器T3在第一次重启之后，同样不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该新定时器T3。
可以理解的是，在该种可能的实现方式中，在启动新定时器T3时，只是以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息启动新定时器T3为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输启动新定时 器T3，例如，在T319定时器运行期间，若终端发送了上行数据，则启动新定时器T3；或者，若接收到下行数据，则启动新定时器T3。
在上述第二种可能的实现方式中，该第一定时器可以为目前网络配置的T319定时器，第二定时器可以为MAC层设置的一个新定时器T4。即，终端在应RRC连接恢复的需求时，先启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动该新定时器T4。需要说明的是，在该种可能的实现方式中，将以在T319定时器运行期间，终端可以根据与网络设备之间的数据传输启动或重启该新定时器T4为例进行说明，当然，在T319定时器运行期间，也可以根据从网络设备接收到的下行信息启动或重启该新定时器T4。示例的，请参见图22所示，图22为本申请实施例提供的再一种配置方法的流程示意图，该配置方法可以包括：
S2201、终端在应RRC连接恢复的需求时，启动T319定时器。
终端在启动T319定时器之前，先配置该T319定时器的时长，使得该T319定时器可以基于配置的时长进行运行。在该S2201中，T319定时器时长的配置方法与上述实施例中S2001中T319定时器时长的配置方法类似，具体可参见上述配置T319定时器的时长的相关描述，在此，本申请实施例不再进行赘述。
在启动T319定时器之后，就可以向网络设备发送RRC连接恢复请求消息，即执行下述S2202：
S2202、终端向网络设备发送RRC连接恢复请求消息。
示例的，RRC连接恢复请求消息可以包括I-RNTI、终端的身份验证信息，以及UE发起RRC连接恢复请求的原因值中的至少一种。其中，I-RNTI用于表示终端在一个RNA范围的唯一标识。终端的身份验证信息是根据终端存储的C-RNTI和RRC完整性密钥生成的身份验证信息。
在该S2202中，终端向网络设备发送RRC连接恢复请求消息的方法与上述S2002中终端向网络设备发送RRC连接恢复请求消息的方法类似，具体可以参见上述S2002中终端向网络设备发送RRC连接恢复请求消息的相关描述，在此，对于终端向网络设备发送RRC连接恢复请求消息的方法，本申请实施例不再进行赘述。
在该S2202中，终端除了向网络设备发送RRC连接恢复请求消息之外，也可以向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息，这些信息的发送方式与上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的发送方式类似，可参见上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的相关描述，在此，本申请实施例不再进行赘述。与上述S2002不同的是，在本申请实施例中，由于除了T319定时器之外，还有MAC层设置的一个新定时器T4，因此，终端还可以再向网络设备发送一个启动指示信息，该启动指示信息用于指示后续在T319定时器运行期间，若满足启动条件，则启动该新定时器T4，从而实现终端启动的新定时器T4和网络设备启动的新定时器T3的同步。
终端在向网络设备发送RRC连接恢复请求消息之后，对应的，网络设备可以根据该RRC连接恢复请求消息向终端发送相应的下行信息，即执行下述S2203：
S2203、网络设备根据RRC连接恢复请求消息向终端发送下行信息。
在S2203中，网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法与上述S2103中网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法类似，可参见上述S2103中的相关描述，在此，本申请实施例不再进行赘述。此外，对于下行信息包括的内容，可参见上述上述S2104中的相关描述，在此，本申请实施例不再进行赘述。
S2204、终端在T319定时器运行期间，根据与网络设备之间的数据传输启动新定时器T4。
终端在启动新定时器T4之前，先配置该启动新定时器T4的时长，使得该启动新定时器T4可以基于配置的时长进行运行。示例的，在配置该新定时器T4的时长时，终端可以从网络设备接收广播消息或RRC消息，并根据该广播消息或RRC消息中包括的指示新定时器T4时长的信息，配置该新定时器T4的时长。可以理解的是，对于该指示新定时器T4时长的信息的获取方式，该指示新定时器T4时长的信息可以与指示T319定时器时长的信息通过同一个广播消息或RRC消息获取，也可以通过不同的广播消息或RRC消息获取，具体可以根据实际需要进行设置。对于该指示新定时器T4时长的信息的获取时间，该指示新定时器T4时长的信息可以与指示T319定时器时长的信息在同一时间获取，也可以在不同的时间获取，例如，在确定启动该新定时器T4时，再获取该指示新定时器T4时长的信息，具体可以根据实际需要进行设置。
其中，该新定时器T4的时长可以为目前网络配置的T319定时器的第一时长，示例的，该第一时长可以为{100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms}中的某一值，也可以大于目前网络配置的T319定时器的一个第二时长，该第二时长可以通过广播消息或RRC消息进行配置，例如，第二时长为{100ms,200ms,300ms,400ms,600ms,1000ms,1500ms,2000ms，2500ms}中的某一值，示例的，第二时长可以为2500ms。由于在满足启动条件时，均会启动该新定时器T4，因此，对于这两种不同的时长，均可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以理解的是，在新定时器T4的配置时长变长时，终端和网络设备进行数据传输的时间变长，便于终端网络设备进行多次数据传输。
与上述第一种可能的实现方式不同的是，在本申请实施例中，在T319定时器运行期间，由于是根据与网络设备之间的数据传输启动新定时器T4，因此，即使终端接收到的下行信息中包括反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，也不会启动该新定时器T4，而是根据与网络设备之间的数据传输启动新定时器T4，例如，在T319定时器运行期间，若终端发送了上行数据，例如，DTCH的数据，则启动新定时器T4；或者，若接收到下行数据，例如，DTCH的数据，则启动新定时器T4，使得在新定时器T4运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。在启动该定时器T4之后，若T319定时器还在运行状态，则可以停止T319定时器。终端在根据与网络设备之间的数据传输启动该新定时器T4之后，由于该新定时器T4为初次启动，则终端还可以通过向网络设备发送一个指示信息，该指示信息用于指示网络设备启动的新定时器T4，从而将已经启动新定时器T4的信息同步给网络设备。并且，对于该新定时器T4而言，在启动之后，该新定时器T4不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、 RRC连接建立消息、或RRC连接释放消息消息时，停止该新定时器T4。在启动该新定时器T4之后，若该定时器T4超时，则终端的MAC层会通知RRC层该定时器T4超时，终端的MAC层根据该定时器T4超时信息终端终端进入空闲态。
通过执行上述S2201-S2204，即终端在应RRC连接恢复的需求时，启动T319定时器，并向网络设备发送RRC连接恢复请求消息；终端在T319定时器运行期间，根据与网络设备之间的数据传输启动新定时器T4，并在新定时器T4运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多次数据的发送。上述整个过程，可以理解为终端执行第一次延长操作，在执行完第一次延长操作后，还可以在新定时器T4运行期间，根据与网络设备之间的数据传输再次控制重启新定时器T4，以再次延长终端等待RRC连接恢复请求消息的RRC响应的时间，该过程可以理解为终端执行第二次延长操作。终端执行第三次延长操作、或者之后的第N(N大于3)次延长操作的方法与终端执行第一次延长操作的方法类似，在此，本申请实施例以在执行完第一次延长操作后，还可以在新定时器T4启动并运行期间，根据与网络设备之间的数据传输控制重启新定时器T4为例进行说明，示例的，在执行完上述S2104根据与网络设备之间的数据传输启动该新定时器T4之后，还可以进一步执行下述S2205-S2207：
S2205、终端在新定时器T4运行期间，向网络设备发送上行数据。
S2206、网络设备根据上行数据向终端发送下行信息。
在S2205-S2206中，终端在新定时器T4运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息的方法，与上述图20所示的实施例中，S2005-S2006中，终端在T319定时器运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息的方法类似，可参见上述S2005-S2006中的相关描述，在此，本申请实施例不再进行赘述。
S2207、终端在新定时器T4运行期间，根据与网络设备之间的数据传输重启该新定时器T4。
在S2207中终端在新定时器T4运行期间，根据与网络设备之间的数据传输重启该新定时器T4的方法，与上述S2204中终端在新定时器T4运行期间，根据与网络设备之间的数据传输启动该新定时器T4的方法类似，在此，本申请实施例不再进行赘述。
在本申请实施例中，由于通过上述S2201-S2204执行第一次延长操作时，是通过首次启动新定时器T4延长终端等待RRC连接恢复请求消息的RRC响应的时间，因此，在该S2207中执行第二次延长操作时，是第一次重启新定时器T4以延长终端等待RRC连接恢复请求消息的RRC响应的时间。可以理解的是，该新定时器T4在第一次重启之后，同样不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该新定时器T4。
在该种可能的实现方式中，在启动新定时器T4时，只是以根据与网络设备之间的数据传输启动新定时器T4，例如，在T319定时器运行期间，若终端发送了上行数据，则启动新定时器T4；或者，若接收到下行数据，则启动新定时器T4为例进行说明，当然，在T319定时器运行期间，终端也可以根据从网络设备接收到的下行信息启动新定时器T4，具体可参见上述第一种可能的实现方式中根据从网络设备接收到的下行信息启动新定时器T3的相关描述，在此，对于终端如何根据从网络设备接收到的下行信息启动新定时器 T4，本申请实施例不再进行赘述。
综上可以看出，在通过上述两种可能的场景描述本申请实施例提供的技术方案时，为了延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送，终端应无线资源控制RRC连接恢复的需求，可以先启动第一定时器，且都是通过配置授权信息指示的上行资源向网络设备发送RRC连接恢复请求消息；并在第一定时器运行期间，终端根据网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启所述第一定时器或启动第二定时器，有效地延长了终端等待RRC连接恢复的时间，从而灵活地支持多次数据的发送。在本申请实施例中，除了可以通过配置授权信息指示的上行资源向网络设备发送RRC连接恢复请求消息之外，还可以通过随机接入过程中的上行资源向网络设备发送RRC连接恢复请求消息。示例的，该上行资源可以为两步RACH中为消息A(MsgA)预先配置的PUSCH资源，也可以为四步RACH中终端接收到的随机接入响应中指示的上行资源，具体可以根据实际需要进行设置。可以理解的是，当通过随机接入过程中的上行资源向网络设备发送RRC连接恢复请求消息时，并在第一定时器运行期间满足重启条件，重启该第一定时器的技术方案同样可以适用于上述两种可能的场景，即在一种可能的场景中，在满足重启条件时，重启的定时器与在应RRC连接恢复的需求时，启动的定时器为同一个定时器，均为第一定时器。在另一种可能的场景中，终端在应RRC连接恢复的需求时，启动的是第一定时器，并在第一定时器运行期间满足启动条件时，启动第二定时器，以延长终端等待RRC连接恢复请求的RRC响应消息的时间。可以理解的是，在该种可能的场景中，在启动第二定时器时，还可以停止第一定时器。
下面，将主要针对第一种场景中第一种可能的实现方式，即第一定时器为目前网络配置的T319定时器，终端通过两步RACH的消息A(MsgA)中的上行资源向网络设备发送RRC连接恢复请求，在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器。在该种可能的实现方式中，将以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启该T319定时器为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输重启该T319定时器。示例的，请参见图23所示，图23为本申请实施例提供的又一种配置方法的流程示意图，该配置方法可以包括：
S2301、终端在应RRC连接恢复的需求时，启动T319定时器。
终端在启动T319定时器之前，需要先配置该T319定时器的时长，使得该T319定时器可以基于配置的时长进行运行。在该S2301中，T319定时器的配置方法与上述实施例中S2001中T319定时器的配置方法类似，具体可参见上述配置T319定时器的时长的相关描述，在此，本申请实施例不再进行赘述。
S2302、终端向网络设备发送前导码。
示例的，终端可以通过两步RACH的消息A(MsgA)向网络设备发送前导码，且该发送该前导码的资源可以为网络设备预先配置的PRACH资源，该PRACH资源可以通过广播消息或专用消息(比如，RRC连接释放消息)配置。
S2303、终端向网络设备发送RRC连接恢复请求消息。
示例的，RRC连接恢复请求消息可以包括I-RNTI、终端的身份验证信息，以及UE发起RRC连接恢复请求的原因值中的至少一种。其中，I-RNTI用于表示终端在一个RNA范 围的唯一标识。终端的身份验证信息是根据终端存储的C-RNTI和RRC完整性密钥生成的身份验证信息。
终端在向网络设备发送RRC连接恢复请求消息时，与上述S2002中不同的是，在本申请实施例中，终端可以通过两步RACH的消息A(MsgA)向网络设备发送RRC连接恢复请求消息，且发送该RRC连接恢复请求消息的资源可以为网络设备预先配置的PUSCH资源，该PUSCH资源可以通过可以通过广播消息或专用消息(比如，RRC连接释放消息)配置。
示例的，终端除了向网络设备发送RRC连接恢复请求消息之外，也可以向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息，这些信息的发送方式与上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的发送方式类似，可参见上述S2002中向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息的相关描述，在此，本申请实施例不再进行赘述。在本申请实施例中，将以终端除了向网络设备发送RRC连接恢复请求消息之外，还向网络设备发送上行数据为例，继续对本申请实施例提供的技术方案进行说明，对应的，网络设备在接收到终端发送的RRC连接恢复请求消息和上行数据之后，执行下述S2304：
S2304、网络设备根据RRC连接恢复请求消息向终端发送下行信息。
需要说明的是，在S2304中，网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法与上述图20所示的实施例中，S2003网络设备根据RRC连接恢复请求消息向终端发送下行信息的方法类似，可参见上述S2003中的相关描述，在此，本申请实施例不再进行赘述。
S2305、终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器。
在S2305中，终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法与上述图20所示的实施例中，S2005终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法类似，可参见上述S2005中的相关描述，在此，对于S2305终端在T319定时器运行期间，如何根据从网络设备接收到的下行信息重启该T319定时器的方法，本申请实施例不再进行赘述。在S2305中，与上述S2005中不同的是，该下行信息中不包括反馈信息，而是可能包括TC-RNTI。
综上所述，终端在T319定时器运行期间，在根据从网络设备接收到的下行信息重启该T319定时器时，若终端接收到的下行信息中包括上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则重启T319定时器，使得在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求的RRC响应消息的时间，灵活地支持多次数据的发送。示例的，终端接收到的下行信息还包括定时调整命令和/或功率控制命令。
通过执行上述S2301-S2305，即终端在应RRC连接恢复的需求时，启动T319定时器，并向网络设备发送RRC连接恢复请求消息；这样在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启该T319定时器，并在T319定时器运行期间进行数据传输，可以有效地延长终端等待RRC连接恢复请求消息的RRC响应的时间，灵活地支持多 次数据的发送。上述整个过程，可以理解为终端执行第一次延长操作，在执行完第一次延长操作后，还可以在T319定时器重启并运行期间，根据从网络设备接收到的下行信息再次控制重启该T319定时器，以再次延长终端等待RRC连接恢复请求消息的RRC响应的时间，该过程可以理解为终端执行第二次延长操作。可以理解的是，终端执行第三次延长操作、或者之后的第N次(N大于3)延长操作的方法与终端执行第一次延长操作的方法类似，在此，本申请实施例以在执行完第一次延长操作后，还可以在T319定时器重启并运行期间，根从网络据设备接收到的下行信息再次控制重启T319定时器为例进行说明，示例的，在执行完上述S2305根据从网络设备接收到的下行信息重启该T319定时器之后，还可以进一步执行下述S2306-S2308：
S2306、终端在T319定时器运行期间，向网络设备发送上行数据。
S2307、网络设备根据上行数据向终端发送下行信息。
S2308、终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器。
在S2306-S2308中，终端在新定时器T319运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息，对应的，终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法，与上述图20所示的实施例中，S2005-S2007中，终端在T319定时器运行期间，向网络设备发送上行数据，网络设备根据上行数据向终端发送下行信息，对应的，终端在T319定时器运行期间，根据从网络设备接收到的下行信息重启该T319定时器的方法类似，可参见上述S2005-S2007中的相关描述，在此，本申请实施例不再进行赘述。
在该种可能的实现方式中，在重启T319定时器时，只是以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息重启该T319定时器为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输重启该T319定时器，例如，在T319定时器运行期间，若终端发送了上行数据，例如，DTCH的数据，则重启T319定时器；或者，若接收到下行数据，例如，DTCH的数据，则重启T319定时器。
上述图23所示的实施例详细描述了终端通过两步RACH的消息A(MsgA)向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器的技术方案。当然，终端可以通过四步RACH接收到的随机接入响应中指示的上行资源向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器。
在通过四步RACH接收到的随机接入响应中指示的上行资源向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，重启该T319定时器的技术方案中，与上述图23所示的通过两步RACH的消息A(MsgA)向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，重启该T319定时器的技术方案中不同的是，在上述S2303终端向网络设备发送RRC连接恢复请求消息之前，终端先接收网络设备发送的随机接入响应，该随机接入响应中可以包括TC-RNTI、上行授权以及定时提前命令，使得终端可以通过该随机接入响应中的上行授权向网络设备发送RRC连接恢复请求消息。示例的，终端除了向网络设备发送RRC连接恢复请求消息之外，终端除了向网络设备发送RRC连接恢复请求消 息之外，也可以向网络设备发送上行数据、辅助信息及期望保持在非激活态继续发送数据的指示信息中的至少一个信息，可参见上述S2303中的相关描述。与上述S2304中不同的是，此处网络设备根据RRC连接恢复请求消息向终端发送的下行信息中不再是包括TC-RNTI、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息中的至少一种，而是包括反馈信息、定时调整命令、功率控制命令、竞争解决信息、上行授权信息、下行资源分配信息、以及新增字段的指示信息中的至少一种；这样终端在T319定时器运行期间，在根据从网络设备接收到的下行信息重启该T319定时器时，若终端接收到的下行信息中包括反馈信息、上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种时，则重启T319定时器，具体过程可以参见上述图20所示的实施例中S2003以及S2004中的相关描述，在此，本申请实施例不再进行赘述。这样重启T319定时器之后，可以在T319定时器运行期间进行数据传输，有效地延长了终端等待RRC连接恢复的时间，从而灵活地支持多次数据的发送。示例的，若终端接收到的下行信息还包括定时调整命令和/或功率控制命令。其中，在接收到该定时调整命令时，应用该定时调整命令进行上行传输定时调整；在接收到该功率控制命令时，应用该功率控制命令进行功率控制。
终端在根据接收到的下行信息重启该T319定时器之后，还可以通过向网络设备发送一个指示信息，该指示信息用于指示终端重启的T319定时器，从而将已经重启该T319定时器的信息同步给网络设备。并且，对于该T319定时器而言，在重启之后，该T319定时器不是一直处于运行状态，而是在终端从网络设备接收RRC连接恢复消息、RRC连接建立消息、或RRC连接释放消息消息时，停止该T319定时器。
可以理解的是，在该种可能的实现方式中，在重启T319定时器时，只是以在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息，例如上行授权信息、下行资源分配信息以及新增字段的指示信息中的任一种或者多种，重启该T319定时器为例进行说明，当然，在T319定时器运行期间，也可以根据与网络设备之间的数据传输重启该T319定时器，例如，在T319定时器运行期间，若终端发送了上行数据，例如，DTCH的数据，则重启T319定时器；或者，若接收到下行数据，例如，DTCH的数据，则重启T319定时器。
可以看出，上述描述主要是针对第一种场景中第一种可能的实现方式，即第一定时器为目前网络配置的T319定时器时，分别通过两步RACH的消息A(MsgA)向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器；以及通过四步RACH接收到的随机接入响应中指示的上行资源向网络设备发送RRC连接恢复请求，并在T319定时器运行期间，终端可以根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，重启该T319定时器的技术方案，当然，该第一定时器也可以为RRC层额外设置的一个新的定时器或者MAC层的一个新定时器，当第一定时器也可以为RRC层额外设置的一个新的定时器或者MAC层的一个新定时器时，控制该第一定时器重启的具体实现方式与当第一定时器为T319定时器时控制该第一定时器重启的具体实现方式类似，可参见上述当第一定时器为T319定时器时控制该第一定时器重启的相关描述，在此，本申请实施例不再进行赘述。
本申请实施例还提供用于实现以上任一种方法的装置，例如，提供一种装置包括用以实现以上任一种方法中终端所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中网络设备所执行的各个步骤的单元(或手段)。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
图24为本申请实施例提供的一种网络设备的结构示意图。其可以为以上实施例中的网络设备，用于实现以上实施例中网络设备的操作。如图24所示，该网络设备包括：天线2401、射频装置2402、基带装置2403。天线2401与射频装置2402连接。在上行方向上，射频装置2402通过天线2401接收终端发送的信息，将终端发送的信息发送给基带装置2403进行处理。在下行方向上，基带装置2403对终端的信息进行处理，并发送给射频装置2402，射频装置2402对终端的信息进行处理后经过天线2401发送给终端。
基带装置2403可以包括一个或多个处理元件24031，例如，包括一个主控CPU和其它集成电路。此外，该基带装置2403还可以包括存储元件24032和接口24033，存储元件24032用于存储程序和数据；接口24033用于与射频装置2402交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。以上用于网络设备的装置可以位于基带装置2403，例如，以上用于网络设备的装置可以为基带装置2403上的芯片，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上网络设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，网络设备实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如用于网络设备的装置包 括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中网络设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件，也可以为与处理元件处于不同芯片上的存储元件，即片外存储元件。
在另一种实现中，网络设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于基带装置上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
网络设备实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，例如，基带装置包括该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上网络设备执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上网络设备执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上用于网络设备的装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种网络设备执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行网络设备执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行网络设备执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行以上网络设备执行的部分或全部步骤。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。
存储元件可以是一个存储器，也可以是多个存储元件的统称。
图25为本申请实施例提供的另一种网络设备的结构示意图。其可以为以上实施例中的网络设备，用于实现以上实施例中网络设备的操作。如图25所示，该网络设备包括：处理器2501，存储器2502，和接口2503，处理器2501、存储器2502和接口2503信号连接。
以上配置装置位于该网络设备中，且各个单元的功能可以通过处理器2501调用存储器2502中存储的程序来实现。即，以上配置装置包括存储器和处理器，存储器用于存储程序，该程序被处理器调用，以执行以上方法实施例中的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。或者以上各个单元的功能可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
图26为本申请实施例提供的一种终端的结构示意图。其可以为以上实施例中的终端，用于实现以上实施例中终端的操作。如图26所示，该终端包括：天线2601、射频部分2602、信号处理部分2603。天线2601与射频部分2602连接。在下行方向上，射频部分2602通过天线2601接收网络设备发送的信息，将网络设备发送的信息发送给信号处理部分2603进行处理。在上行方向上，信号处理部分2603对终端的信息进行处理，并发 送给射频部分2602，射频部分2602对终端的信息进行处理后经过天线2601发送给网络设备。
信号处理部分2603可以包括调制解调子系统，用于实现对数据各通信协议层的处理；还可以包括中央处理子系统，用于实现对终端操作系统以及应用层的处理；此外，还可以包括其它子系统，例如多媒体子系统，周边子系统等，其中多媒体子系统用于实现对终端相机，屏幕显示等的控制，周边子系统用于实现与其它设备的连接。调制解调子系统可以为单独设置的芯片。可选的，以上用于终端的装置可以位于该调制解调子系统。
调制解调子系统可以包括一个或多个处理元件，例如，包括一个主控和其它集成电路。此外，该调制解调子系统还可以包括存储元件和接口电路。存储元件用于存储数据和程序，但用于执行以上方法中终端所执行的方法的程序可能不存储于该存储元件中，而是存储于调制解调子系统之外的存储器中，使用时调制解调子系统加载使用。接口电路用于与其它子系统通信。以上用于终端的装置可以位于调制解调子系统，该调制解调子系统可以通过芯片实现，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上终端执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，终端实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如用于终端的装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中终端执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件。
在另一种实现中，用于执行以上方法中终端所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件，即片外存储元件。此时，处理元件从片外存储元件调用或加载程序于片内存储元件上，以调用并执行以上方法实施例中终端执行的方法。
在又一种实现中，终端实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于调制解调子系统上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
终端实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上终端执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上终端执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上用于终端的装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种终端执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行终端执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行终端执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行终端执行的部分或全部步骤。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。
存储元件可以是一个存储器，也可以是多个存储元件的统称。

Claims (84)

  1. 一种配置方法，其特征在于，包括：
    接收无线资源控制RRC连接释放消息，所述RRC连接释放消息包括第一信息，所述第一信息用于指示目标配置参数；
    根据所述RRC连接释放消息进入非激活态，且根据所述第一信息确定非激活态的上下文参数，其中，所述非激活态的上下文参数包括所述目标配置参数，或，所述非激活态的上下文参数包括终端的上下文参数中除所述目标配置参数之外的参数。
  2. 根据权利要求1所述的方法，其特征在于，
    所述目标配置参数包括：无线承载配置参数，和/或，小区组配置参数。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述第一信息为所述目标配置参数对应的标识。
  4. 根据权利要求3所述的方法，其特征在于，所述终端存储有配置参数对应的标识和配置参数的映射关系，所述根据所述第一信息确定非激活态的上下文参数，包括：
    根据所述目标配置参数对应的标识，及所述映射关系确定所述非激活态的上下文参数包括所述标识对应的目标配置参数。
  5. 根据权利要求1或2所述的方法，其特征在于，
    所述第一信息包括所述目标配置参数。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    上报所述终端的非激活态的能力信息。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    接收第一指示，所述第一指示用于指示所述终端在非激活态时监听物理下行控制信道。
  8. 根据权利要求7所述的方法，其特征在于，
    所述第一指示包括在所述RRC释放消息中。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    接收第二指示，所述第二指示用于指示所述终端在非激活态时允许进行上行传输。
  10. 根据权利要求9所述的方法，其特征在于，所述接收第二指示，包括：
    发送随机接入请求；
    接收所述随机接入请求的响应消息，所述响应消息包括上行授权和所述第二指示，所述第二指示用于指示在非激活态时允许在所述上行授权上进行上行传输。
  11. 一种配置方法，其特征在于，包括：
    确定目标配置参数；
    发送无线资源控制RRC连接释放消息，所述RRC连接释放消息包括第一信息，所述第一信息用于指示所述目标配置参数，所述RRC连接释放消息用于指示终端根据所述RRC连接释放消息进入非激活态，所述第一信息用于指示终端确定非激活态的上下文参数，其中，所述非激活态的上下文参数包括所述目标配置参数，或，所述非激活态的上下文参数包括终端的上下文参数中除所述目标配置参数之外的参数。
  12. 根据权利要求11所述的方法，其特征在于，
    所述目标配置参数包括：无线承载配置参数，和/或，小区组配置参数。
  13. 根据权利要求11或12所述的方法，其特征在于，
    所述第一信息为所述目标配置参数对应的标识。
  14. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    发送所述配置参数对应的标识和配置参数的映射关系。
  15. 根据权利要求11或12所述的方法，其特征在于，
    所述第一信息包括所述目标配置参数。
  16. 根据权利要求11-15任一项所述的方法，其特征在于，所述确定目标配置参数，包括：
    接收来自核心网设备的会话建立请求，所述会话建立请求中包括会话类型，所述会话类型用于指示终端在非激活态时允许进行上行传输；
    基于所述会话类型，确定所述目标配置参数。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送会话建立响应。
  18. 根据权利要求11-17任一项所述的方法，其特征在于，所述方法还包括：
    发送第一指示，所述第一指示用于指示终端在非激活态时监听物理下行控制信道。
  19. 根据权利要求18所述的方法，其特征在于，
    所述第一指示信息包括在所述RRC释放消息中。
  20. 根据权利要求11-19任一项所述的方法，其特征在于，所述方法还包括：
    发送第二指示，所述第二指示用于指示终端在非激活态时允许进行上行传输。
  21. 根据权利要求20所述的方法，其特征在于，所述发送第二指示，包括：
    接收随机接入请求；
    发送所述随机接入请求的响应消息，所述响应消息包括上行授权和所述第二指示，所述第二指示用于指示在非激活态时允许在所述上行授权上进行上行传输。
  22. 一种配置方法，其特征在于，包括：
    向网络设备发送第一消息，所述第一消息包括随机接入请求和/或物理上行共享信道数据，所述物理上行共享信道数据包括用于请求恢复RRC连接的信息；
    从所述网络设备接收第一消息的响应消息，所述响应消息包括竞争解决信息；
    从所述网络设备接收上行授权；
    在所述上行授权指示的上行资源上进行上行传输。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    在接收到所述第一消息的响应消息时，启动或重启定时器。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    在定时器运行期间，从所述网络设备接收上行授权；
    在接收到所述上行授权时，重启定时器。
  25. 根据权利要求23或24所述的方法，其特征在于，所述方法还包括：
    在定时器运行期间，从网络设备接收下行授权；
    在接收到所述下行授权时，重启定时器。
  26. 根据权利要求23-25任一项所述的方法，其特征在于，所述方法还包括：
    从所述网络设备接收无线资源控制RRC连接释放消息；
    在接收到所述RRC连接释放消息时，停止定时器。
  27. 一种配置方法，其特征在于，包括：
    从终端接收第一消息，所述第一消息包括随机接入请求和/或物理上行共享信道数据，所述物理上行共享信道数据包括用于请求恢复RRC连接的信息；
    向所述终端发送第一消息的响应消息，所述响应消息包括竞争解决信息；
    向所述终端发送上行授权；在所述上行授权指示的上行资源上进行数据传输。
  28. 根据权利要求27所述的方法，其特征在于，所述方法还包括：
    向所述终端发送无线资源控制RRC连接释放消息。
  29. 一种配置方法，其特征在于，包括：
    向网络设备发送第一消息，所述第一消息包括随机接入请求和/或物理上行共享信道数据，所述物理上行共享信道数据包括用于请求恢复无线资源控制RRC连接的信息；
    从所述网络设备接收第一消息的响应消息，所述响应消息包括上行授权和第一指示信息，所述第一指示信息用于指示是否允许在所述上行授权指示的上行资源上进行上行传输；
    根据所述第一指示信息在所述上行资源上进行上行传输。
  30. 根据权利要求29所述的方法，其特征在于，
    若所述第一指示信息指示允许在所述上行资源上进行上行传输，则在所述上行资源上向所述网络设备发送第二消息，其中，所述第二消息中包括上行数据。
  31. 根据权利要求29所述的方法，其特征在于，
    若所述第一指示信息指示不允许在所述上行资源上进行上行传输，则在所述上行资源上向所述网络设备发送第三消息，其中，所述第三消息用于请求恢复RRC连接。
  32. 根据权利要求29-31任一项所述的方法，其特征在于，所述方法还包括：
    在接收到所述第一消息的响应消息时，启动或重启定时器。
  33. 根据权利要求32所述的方法，其特征在于，所述方法还包括：
    在定时器运行期间，从网络设备接收授权；
    在接收到所述授权时，重启定时器。
  34. 根据权利要求31或32所述的方法，其特征在于，所述方法还包括：
    从所述网络设备接收无线资源控制RRC连接释放消息；
    在接收到所述RRC连接释放消息时，停止定时器。
  35. 根据权利要求29-34任一项所述的方法，其特征在于，
    所述响应消息包括竞争解决信息。
  36. 根据权利要求29-35任一项所述的方法，其特征在于，
    第一消息还包括第二指示信息，所述第二指示信息用于指示所述终端的待发送数据量与数据量门限的比较结果。
  37. 一种配置方法，其特征在于，包括：
    从终端接收第一消息，所述第一消息包括随机接入请求和/或物理上行共享信道数据，所述物理上行共享信道数据包括用于请求恢复无线资源控制RRC连接的信息；
    向所述终端发送第一消息的响应消息，所述响应消息包括上行授权和第一指示信息， 所述第一指示信息用于指示是否允许在所述上行授权指示的上行资源上进行上行传输；
    根据所述第一指示信息在所述上行资源上进行上行传输。
  38. 根据权利要求37所述的方法，其特征在于，
    若所述第一指示信息指示允许在所述上行资源上进行上行传输，则在所述上行资源上从终端接收第二消息，其中，所述第二消息中包括上行数据。
  39. 根据权利要求37所述的方法，其特征在于，
    若所述第一指示信息指示不允许在所述上行资源上进行上行传输，则在所述上行资源上从终端接收第三消息，其中，所述第三消息用于请求恢复RRC连接。
  40. 根据权利要求37或39所述的方法，其特征在于，所述方法还包括：
    向所述终端发送无线资源控制RRC连接释放消息。
  41. 根据权利要求37-40任一项所述的方法，其特征在于，
    所述响应消息包括竞争解决信息。
  42. 根据权利要求37-41任一项所述的方法，其特征在于，
    第一消息还包括第二指示信息，所述第二指示信息用于指示所述终端的待发送数据量与数据量门限的比较结果。
  43. 一种配置方法，其特征在于，包括：
    接收指示信息，所述指示信息用于指示终端在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
    根据所述指示信息监听C-RNTI加扰的PDCCH。
  44. 根据权利要求43所述的方法，其特征在于，所述接收指示信息，包括：
    接收无线资源控制RRC连接释放消息，所述RRC连接释放消息包括所述指示信息。
  45. 根据权利要求43或44所述的方法，其特征在于，所述监听C-RNTI加扰的PDCCH，包括：
    确定寻呼时机，在所述寻呼时机的部分时隙或部分寻呼帧监听所述C-RNTI加扰的PDCCH。
  46. 根据权利要求43或44所述的方法，其特征在于，所述监听C-RNTI加扰的PDCCH，包括：
    接收第一参数，根据所述第一参数确定寻呼时机；
    接收第二参数，根据所述第二参数确定监听所述C-RNTI加扰的PDCCH的时机，其中所述寻呼时机和监听所述C-RNTI加扰的PDCCH的时机不同。
  47. 根据权利要求43-46任一项所述的方法，其特征在于，
    在所述终端移出所述C-RNTI的有效区域时，停止监听所述C-RNTI加扰的PDCCH。
  48. 一种配置方法，其特征在于，包括：
    确定终端可在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH；
    向所述终端发送指示信息，所述指示信息用于指示终端在非激活态时监听小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH。
  49. 根据权利要求48所述的方法，其特征在于，所述向所述终端发送指示信息，包括：
    向所述终端发送无线资源控制RRC连接释放消息，所述RRC连接释放消息包括所述指示信息。
  50. 根据权利要求48或49所述的方法，其特征在于，所述方法还包括：
    向所述终端发送第一参数，所述第一参数用于所述终端根据所述第一参数确定寻呼时机；
    向终端发送第二参数，所述第二参数用于所述终端根据所述第二参数确定监听所述C-RNTI加扰的PDCCH的时机，其中所述寻呼时机和监听所述C-RNTI加扰的PDCCH的时机不同。
  51. 一种配置方法，其特征在于，包括：
    终端应无线资源控制RRC连接恢复的需求，启动第一定时器，且向网络设备发送RRC连接恢复请求消息；
    所述终端在所述第一定时器运行期间，根据从所述网络设备接收到的下行信息或根据与所述网络设备之间的数据传输，重启所述第一定时器或启动第二定时器。
  52. 根据权利要求51所述的方法，其特征在于，所述方法还包括：
    所述终端向所述网络设备发送上行数据，所述上行数据与所述RRC连接恢复请求消息共同发送或独立发送，其中，所述下行信息包括所述上行数据的反馈信息，所述上行数据的反馈信息用于指示所述上行数据是否成功传输。
  53. 根据权利要求51或52所述的方法，其特征在于，所述下行信息包括竞争解决信息。
  54. 根据权利要求51-53任一项所述的方法，其特征在于，所述下行信息包括上行授权信息。
  55. 根据权利要求54所述的方法，其特征在于，所述方法还包括：
    所述终端利用所述上行授权信息指示的上行资源发送上行数据。
  56. 根据权利要求51-55任一项所述的方法，其特征在于，所述下行信息包括下行资源分配信息。
  57. 根据权利要求56所述的方法，其特征在于，所述方法还包括：
    所述终端在所述下行资源分配信息所指示的下行资源上接收下行数据。
  58. 根据权利要求51-57任一项所述的方法，其特征在于，所述下行信息包括指示信息，所述指示信息用于指示所述终端重启所述第一定时器。
  59. 根据权利要求51-58任一项所述的方法，其特征在于，所述方法还包括：
    所述终端从网络设备接收广播消息或RRC消息，所述广播消息或RRC消息包括所述第一定时器的信息，所述第一定时器的信息用于指示所述第一定时器的时长。
  60. 根据权利要求51-59任一项所述的方法，其特征在于，所述第一定时器为T319定时器。
  61. 根据权利要求51至59任一项所述的方法，其特征在于，所述第一定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且所述终端在所述第一定时器运行期间，应从网络设备接收到的下行信息或应与网络设备之间的数据传输，重启所述第一定时器；或者，
    所述第一定时器为T319定时器，且所述第二定时器为除T319定时器之外的RRC层 定时器或MAC层定时器，且所述终端在所述第一定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动或重启所述第二定时器。
  62. 根据权利要求51-61任一项所述的方法，其特征在于，所述方法还包括：
    所述终端向网络设备发送指示信息，所述指示信息用于指示所述网络设备启动的所述第一定时器或第二定时器。
  63. 根据权利要求51-62任一项所述的方法，其特征在于，所述方法还包括：
    当所述终端启动第二定时器时，停止所述第一定时器。
  64. 根据权利要求51-63任一项所述的方法，其特征在于，所述方法还包括：
    所述终端从网络设备接收RRC连接恢复、RRC连接建立、或RRC连接释放消息时，停止所述第一定时器或所述第二定时器。
  65. 一种配置方法，其特征在于，包括：
    从终端接收无线资源控制RRC连接恢复请求消息，所述RRC连接恢复请求消息是所述终端应无线资源控制RRC连接恢复的需求，启动第一定时器后发送的；
    在所述第一定时器运行期间，向所述终端发送下行信息或与所述终端进行数据传输，用于指示所述根据从所述网络设备接收到的下行信息或根据与所述网络设备之间的数据传输，重启所述第一定时器或启动第二定时器。
  66. 根据权利要求65所述的方法，其特征在于，所述方法还包括：
    从所述终端接收上行数据，所述上行数据与所述RRC连接恢复请求消息共同发送或独立发送，其中，所述下行信息包括所述上行数据的反馈信息，所述上行数据的反馈信息用于指示所述上行数据是否成功传输。
  67. 根据权利要求65或66所述的方法，其特征在于，所述下行信息包括竞争解决信息。
  68. 根据权利要求65-67任一项所述的方法，其特征在于，所述下行信息包括上行授权信息。
  69. 根据权利要求68所述的方法，其特征在于，所述方法还包括：
    从所述终端接收利用所述上行授权信息指示的上行资源发送的上行数据。
  70. 根据权利要求65-69任一项所述的方法，其特征在于，所述下行信息包括下行资源分配信息。
  71. 根据权利要求70所述的方法，其特征在于，所述方法还包括：
    在所述下行资源分配信息所指示的下行资源上向所述终端发送下行数据。
  72. 根据权利要求65-71任一项所述的方法，其特征在于，所述下行信息包括指示信息，所述指示信息用于指示所述终端重启所述第一定时器。
  73. 根据权利要求65-72任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端发送广播消息或RRC消息，所述广播消息或RRC消息包括所述第一定时器的信息，所述第一定时器的信息用于指示所述第一定时器的时长。
  74. 根据权利要求65-73任一项所述的方法，其特征在于，所述第一定时器为T319定时器。
  75. 根据权利要求65至73任一项所述的方法，其特征在于，所述第一定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且所述第一定时器是所述终端在所述第一 定时器运行期间，应从网络设备接收到的下行信息或应与网络设备之间的数据传输重启的；或者，
    所述第一定时器为T319定时器，且所述第二定时器为除T319定时器之外的RRC层定时器或MAC层定时器，且所述第二定时器是所述终端在所述第一定时器运行期间，根据从网络设备接收到的下行信息或根据与网络设备之间的数据传输，启动或重启的。
  76. 根据权利要求65-75任一项所述的方法，其特征在于，所述方法还包括：
    从所述终端接收指示信息，所述指示信息用于指示所述网络设备启动的所述第一定时器或第二定时器。
  77. 一种配置装置，其特征在于，包括：用于执行上述权利要求1至10任一项所述的各个步骤的单元；或者，用于执行上述权利要求22至26任一项所述的各个步骤的单元；或者，用于执行上述权利要求29至36任一项所述的各个步骤的单元；或者，用于执行上述权利要求43至47任一项所述的各个步骤的单元；或者，用于执行上述权利要求51至64任一项所述的各个步骤的单元。
  78. 一种配置装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求1至10任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求22至26任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求29至36任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求43至47任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求51至64任一项所述的方法。
  79. 一种配置装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求1至10任一项所述的方法；或者，所述处理器用于执行权利要求22至26任一项所述的方法；或者，所述处理器用于执行权利要求29至36任一项所述的方法；或者，所述处理器用于执行权利要求43至47任一项所述的方法；或者，所述处理器用于执行权利要求51至64任一项所述的方法。
  80. 一种配置装置，其特征在于，包括：用于执行上述权利要求11至21任一项所述的各个步骤的单元；或者，用于执行上述权利要求27至28任一项所述的各个步骤的单元；或者，用于执行上述权利要求37至42任一项所述的各个步骤的单元；或者，用于执行上述权利要求48至50任一项所述的各个步骤的单元；或者，用于执行上述权利要求65至76任一项所述的各个步骤的单元。
  81. 一种配置装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求11至21任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求27至28任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求37至42任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求48至50任一项所述的方法；或者，用于调用存储器中的程序，以执行权利要求65至76任一项所述的方法。
  82. 一种配置装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求11至21任一项所述的方法；或者，所述处理器用于执行权利要求27至28任一项所述的方法；或者，所述处理器用于执行权利要求37至42任一项所述的方法；或者，所述处理器用于执行权利要求48至50任一项所述的方法；或者，所述处理器用于执行权利要求65至76任一项所述的方法。
  83. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所 述程序被处理器调用时，权利要求1至76任一项所述的方法被执行。
  84. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求1至76任一项所述的方法被执行。
PCT/CN2020/075402 2019-09-30 2020-02-14 配置方法和装置 WO2021062974A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202080062554.8A CN114679919B (zh) 2019-09-30 2020-02-14 配置方法和装置
EP20871813.0A EP4030809A4 (en) 2019-09-30 2020-02-14 CONFIGURATION METHOD AND DEVICE
US17/707,614 US20220225465A1 (en) 2019-09-30 2022-03-29 Configuration Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/109722 WO2021062797A1 (zh) 2019-09-30 2019-09-30 配置方法和装置
CNPCT/CN2019/109722 2019-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/707,614 Continuation US20220225465A1 (en) 2019-09-30 2022-03-29 Configuration Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2021062974A1 true WO2021062974A1 (zh) 2021-04-08

Family

ID=75336364

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2019/109722 WO2021062797A1 (zh) 2019-09-30 2019-09-30 配置方法和装置
PCT/CN2020/075402 WO2021062974A1 (zh) 2019-09-30 2020-02-14 配置方法和装置

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/109722 WO2021062797A1 (zh) 2019-09-30 2019-09-30 配置方法和装置

Country Status (4)

Country Link
US (1) US20220225465A1 (zh)
EP (1) EP4030809A4 (zh)
CN (1) CN114679919B (zh)
WO (2) WO2021062797A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11622388B2 (en) * 2021-03-08 2023-04-04 Nokia Technologies Oy Energy efficient, RRC state aware uplink radio resource allocation
US11683851B2 (en) * 2021-03-15 2023-06-20 Qualcomm Incorporated Multi-USIM suspension and optimized resumption
US20230016194A1 (en) * 2021-07-15 2023-01-19 Qualcomm Incorporated Modifying a configuration of a radio bearer based on a request for quality of service (qos) for a communication flow

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018145585A1 (en) * 2017-02-13 2018-08-16 Huawei Technologies Co., Ltd. System and method for user equipment identification and communications
CN108616943A (zh) * 2017-01-26 2018-10-02 华为技术有限公司 信息传输方法、基站以及用户设备
US20180324869A1 (en) * 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink early data transmission
CN109391963A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 一种传输方法和网络设备
CN109923915A (zh) * 2016-11-13 2019-06-21 Lg电子株式会社 用于接收下行链路信号的方法和用户设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247553B (zh) * 2013-03-22 2019-07-26 华为技术有限公司 建立连接的方法及设备
CN104105214B (zh) * 2013-04-01 2017-08-18 电信科学技术研究院 一种数据传输方法及装置
US10728927B2 (en) * 2016-11-11 2020-07-28 FG Innovation Company Limited Data packet delivery in RRC inactive state
KR20190125499A (ko) * 2017-03-22 2019-11-06 엘지전자 주식회사 랜덤 접속 과정을 수행하는 방법 및 이를 위한 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109923915A (zh) * 2016-11-13 2019-06-21 Lg电子株式会社 用于接收下行链路信号的方法和用户设备
CN108616943A (zh) * 2017-01-26 2018-10-02 华为技术有限公司 信息传输方法、基站以及用户设备
WO2018145585A1 (en) * 2017-02-13 2018-08-16 Huawei Technologies Co., Ltd. System and method for user equipment identification and communications
US20180324869A1 (en) * 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink early data transmission
CN109391963A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 一种传输方法和网络设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Introduction of SA", 3GPP TSG-WG2 MEETING #102 R2-1809239; SECTION 4.2.1, 25 May 2018 (2018-05-25), XP051520562 *
OPPO: "2-steps RACH procedure for NR-U", 3GPP DRAFT; R2-1816263 - 2-STEPS RACH PROCEDURE FOR NR-U, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, 12 November 2018 (2018-11-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051555863 *
OPPO: "MsgB contents and formats in 2-step RACH", 3GPP DRAFT; R2-1905600 - MSGB CONTENTS AND FORMATS IN 2-STEP RACH, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051729103 *
See also references of EP4030809A4

Also Published As

Publication number Publication date
EP4030809A4 (en) 2023-03-01
CN114679919A (zh) 2022-06-28
WO2021062797A1 (zh) 2021-04-08
CN114679919B (zh) 2024-05-03
EP4030809A1 (en) 2022-07-20
US20220225465A1 (en) 2022-07-14

Similar Documents

Publication Publication Date Title
WO2021077434A1 (zh) 一种通信方法及装置
CN110140409B (zh) 通信装置、基础设施设备和方法
EP4236570A2 (en) Light connection method and apparatus for use in wireless communication system
RU2768363C2 (ru) Способ передачи данных и устройство
KR102200982B1 (ko) Ue의 상태 전환 방법 및 장치
WO2015169148A1 (zh) D2d资源的配置、分配方法及装置
WO2019232732A1 (zh) 一种寻呼消息传输方法和相关设备
JP2018019403A (ja) 無線通信システムにおけるランダムアクセス手順のｍｓｇ３送信を改善するための方法及び装置
EP3440889B1 (en) Light connection method and apparatus for use in wireless communication system
US7917137B2 (en) Optimization of uplink resource grant procedure and apparatus
WO2021062974A1 (zh) 配置方法和装置
CN108886748B (zh) 用于减少信令开销和减少终端电池的方法和设备
WO2012028076A1 (zh) 一种机器类通信设备的数据传输处理方法及设备
WO2022152003A1 (zh) 非激活态下数据传输方法及装置
WO2016019739A1 (zh) 用户状态的处理方法及装置
WO2023030088A1 (zh) 旁链路通信方法及设备
WO2021213014A1 (zh) 一种通信方法及装置
WO2022000509A1 (zh) 无线通信方法、终端设备和网络设备
CN115529662A (zh) 一种通信方法及装置
WO2023051366A1 (zh) 一种控制传输的方法及相关装置
WO2022267883A1 (zh) 一种通信方法及装置
WO2023010257A1 (zh) 侧行通信方法、装置、设备及存储介质
WO2022237614A1 (zh) 由用户设备执行的方法以及用户设备
WO2024065137A1 (zh) 配置信息获取方法, 配置信息转发方法以及终端设备
WO2023134410A1 (zh) 通信方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20871813

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020871813

Country of ref document: EP

Effective date: 20220413