WO2024026894A1 - 配置参数的方法、装置以及通信系统 - Google Patents

配置参数的方法、装置以及通信系统 Download PDF

Info

Publication number
WO2024026894A1
WO2024026894A1 PCT/CN2022/110714 CN2022110714W WO2024026894A1 WO 2024026894 A1 WO2024026894 A1 WO 2024026894A1 CN 2022110714 W CN2022110714 W CN 2022110714W WO 2024026894 A1 WO2024026894 A1 WO 2024026894A1
Authority
WO
WIPO (PCT)
Prior art keywords
link failure
terminal device
wireless link
configuration information
timer
Prior art date
Application number
PCT/CN2022/110714
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 PCT/CN2022/110714 priority Critical patent/WO2024026894A1/zh
Publication of WO2024026894A1 publication Critical patent/WO2024026894A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the embodiments of this application relate to the field of communication technology.
  • Dual Active Protocol Stack (DAPS) handover means that after the terminal device receives the radio resource control (RRC) message of the handover, it releases the source cell until it successfully randomly accesses the target network device (for example, the target gNB). A handover process in which the source network device (eg, source gNB) connection is maintained.
  • RRC radio resource control
  • the terminal equipment eg, UE
  • the terminal equipment continues to receive downlink user data from the source gNB until the source cell is released, and continues to transmit uplink user data to the source gNB until the random access procedure to the target gNB is successfully completed.
  • Figure 1 is a schematic diagram in a DAPS switching scenario.
  • the terminal device 101 switches from the source network device 102 to the target network device 103.
  • the source gNB releases Carrier Aggregation (CA), Dual Connectivity (DC), Supplementary Uplink (SUL), Multiple Transceiver Points (TRP), and Ethernet Ethernet Header Compression (EHC), Conditional Handover Opportunity (CHO), Uplink Data Compression (UDC), New Radio Sidelink (NR sidelink) configuration and vehicle-to-everything side link (V2X sidelink) configuration, and the target gNB will not perform the above configuration until the DAPS handover is completed (e.g., at least in the same message releasing the source PCell).
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • SUL Supplementary Uplink
  • TRP Multiple Transceiver Points
  • EHC Ethernet Ethernet Header Compression
  • CHO Conditional Handover Opportunity
  • UDC Uplink Data Compression
  • NR sidelink New Radio Sidelink
  • V2X sidelink vehicle-to-everything side link
  • the terminal For RRC-triggered DAPS switching, once the switching command is received, the terminal creates a media access control (MAC) entity for the target network device; establishes the target wireless link for each Data Radio Bearer (DRB) configured with DAPS Route Control (RLC) entity and an associated Dedicated Transmission Channel (DTCH) logical channel; for each DRB configured with DAPS, reconfigure the Packet Data Convergence Protocol (PDCP) entity, where the The PDCP entities have separate secure and reliable header compression (ROCH) for the source and destination and associate them with the source and destination configured RLC entities respectively.
  • DRB Data Radio Bearer
  • RLC DAPS Route Control
  • DTCH Dedicated Transmission Channel
  • DAPS handover fails, if the source link has not been released, the UE falls back to the source cell configuration, restores the connection with the source cell, reports the DAPS handover failure through the source, and does not trigger RRC connection reestablishment.
  • the terminal equipment e.g., UE
  • SRBs signaling radio bearers
  • the UE releases the source cell SRBs configuration.
  • DAPS handover to the target cell fails, and if the source cell link is available, the UE falls back to the source cell configuration and resumes the source cell SRBs for control plane signaling transmission.
  • the terminal device if the terminal device is configured with a DAPS bearer, when the first configuration information (rlf-TimersAndConstants) of a cell group is not configured, or the received first configuration information is set to release (release), the terminal device Use the values of timers T301, T310, T311 and constants N310, N311 included in the ue-TimersAndConstants received in System Information Block (SIB) 1 for the target cell group to perform processing related to wireless link failure.
  • SIB System Information Block
  • the inventor of this application found that if the terminal equipment is configured with a DAPS bearer, then the terminal equipment is likely to be in DAPS handover, that is, the terminal equipment has the system information block (SIB) 1 of the source cell and the SIB1 of the target cell. Under the mechanism, there is no consistent understanding of the source of SIB1 between different terminal equipment or terminal equipment and network equipment. For example: (1) Based on implementation, some terminal equipment uses the parameters/constants in the source cell SIB1, and some terminals use the target cell SIB1. Parameters/constants; (2) Terminal equipment and network equipment have inconsistent understandings of the source of SIB1. These two possibilities will cause some terminal equipment to be insufficiently sensitive or too sensitive to trigger wireless link failure, that is, triggering wireless links unnecessarily. The link failure process or the wireless link failure process is triggered too late, resulting in longer service interruption.
  • SIB system information block
  • Embodiments of the present application provide a method, device and communication system for configuring parameters, enabling different terminal devices and network devices to have a consistent understanding of the values of timers and constants for wireless link failure, thereby avoiding unnecessary triggering of wireless links.
  • the wireless link failure process or the wireless link failure process is triggered too late, resulting in longer service interruption.
  • a device for configuring parameters is provided, which is applied to a terminal device, and the device includes a first application unit:
  • DAPS dual activation protocol stack
  • the terminal device When the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to the radio link failure of the cell group or the received first configuration information (rlf-TimersAndConstants) is set to the first state (release )hour,
  • the first application unit uses the information related to the radio link failure in the system information block (SIB) 1 of the source cell or the target cell for the target cell group for synchronization reconfiguration.
  • SIB system information block
  • an apparatus for configuring parameters which is applied to network equipment, and the apparatus includes a first configuration unit:
  • the first configuration unit sends a radio resource control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information to the terminal device,
  • RRC radio resource control
  • the dual activation protocol stack (DAPS) bearer is configured for the terminal device, when the first configuration information (rlf-TimersAndConstants) of the cell group related to the radio link failure is not configured for the terminal device or is sent to When the first configuration information (rlf-TimersAndConstants) of the terminal device is set to the first state (release),
  • the radio resource control reconfiguration message includes dedicated system information block 1 delivery information (dedicatedSIB1-Delivery).
  • the dedicated system information block 1 delivery information has information related to radio link failure in the system information block (SIB) 1 of the target cell. Information.
  • an apparatus for configuring parameters which is applied to network equipment, and the apparatus includes a second configuration unit:
  • the second configuration unit sends a Radio Resource Control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information to the terminal device,
  • RRC Radio Resource Control
  • the second configuration unit configures the first configuration information (rlf-TimersAndConstants) related to wireless link failure for the terminal device, and
  • the first configuration information (rlf-TimersAndConstants) is set to a second state (setup).
  • a device for configuring parameters is provided, which is applied to a terminal device, and the device includes a second application unit:
  • the second application unit receives a Radio Resource Control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information from the network device,
  • RRC Radio Resource Control
  • the second application unit receives first configuration information (rlf-TimersAndConstants) related to wireless link failure from the network device, wherein , the first configuration information (rlf-TimersAndConstants) is set to the second state (setup).
  • first configuration information rlf-TimersAndConstants
  • an apparatus for configuring parameters is provided, which is applied to a terminal device, and the apparatus includes a third application unit:
  • DAPS dual activation protocol stack
  • the terminal device When the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to wireless link failure or the received first configuration information (rlf-TimersAndConstants) is set to the first state (release),
  • the third application unit uses the same information related to radio link failure as the source cell group for the target cell group.
  • the beneficial effect of the embodiments of the present application is to enable different terminal devices and network devices to have a consistent understanding of the values of timers and constants for wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link too late.
  • the road failure process and the resulting business interruption are to enable different terminal devices and network devices to have a consistent understanding of the values of timers and constants for wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link too late.
  • Figure 1 is a schematic diagram in the DAPS switching scenario
  • Figure 2 is a schematic diagram of a method for configuring parameters according to the embodiment of the first aspect
  • Figure 3 is a schematic diagram of a method for configuring parameters according to the embodiment of the second aspect
  • Figure 4 is a schematic diagram of a method for configuring parameters according to the embodiment of the third aspect
  • Figure 5 is a schematic diagram of a method for configuring parameters according to the embodiment of the fourth aspect
  • Figure 6 is a schematic diagram of a method for configuring parameters according to the embodiment of the fifth aspect
  • Figure 7 is a schematic diagram of a device for configuring parameters according to the embodiment of the sixth aspect.
  • Figure 8 is a schematic diagram of a device for configuring parameters in the embodiment of the seventh aspect
  • Figure 9 is a schematic diagram of a device for configuring parameters in the embodiment of the eighth aspect.
  • Figure 10 is a schematic diagram of a device for configuring parameters in the embodiment of the ninth aspect
  • Figure 11 is a schematic diagram of a device for configuring parameters in the embodiment of the tenth aspect
  • Figure 12 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be used by these terms. restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprises,” “includes,” “having” and the like refer to the presence of stated features, elements, elements or components but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system can be carried out according to any stage of communication protocols, which may include but are not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G. , New Wireless (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device.
  • Network equipment may include but is not limited to the following equipment: integrated access and backhaul node (IAB-node), relay (relay), base station (BS, Base Station), access point (AP, Access Point), sending and receiving Point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, wireless network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) etc.
  • IAB-node integrated access and backhaul node
  • relay relay
  • base station BS, Base Station
  • AP Access Point
  • TRP Transmission Reception Point
  • broadcast transmitter mobile management entity
  • MME Mobile Management Entity
  • gateway server
  • wireless network controller RNC, Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc.
  • it may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay or low-power node (such as femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femeto, pico, etc.
  • base station may include some or all of their functions, each of which may provide communications coverage to a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device) refers to a device that accesses a communication network through a network device and receives network services.
  • Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), mobile terminal (MT, mobile termination), stations, etc.
  • the terminal equipment may include but is not limited to the following equipment: cellular phone (Cellular Phone), personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld device, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld device machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measuring.
  • the terminal device can include but is not limited to: Machine Type Communication (MTC) terminals, Vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to the side of the user or terminal, which may be a certain UE or may include one or more terminal devices as above.
  • the high-level signaling may be, for example, radio resource control (RRC) signaling; for example, it is called an RRC message (RRC message), and includes, for example, a master information block (MIB), system information (system information), Dedicated RRC message; also known as RRC IE (RRC information element).
  • RRC radio resource control
  • the high-level signaling may also be F1-C signaling, or F1AP protocol, for example.
  • this application is not limited to this.
  • RLF Radio Link Failure
  • the terminal device In the Radio Resource Control Connection (RRC_CONNECTED) state, based on the reference signal and the reference signal threshold configured by the network, the terminal device performs Radio Link Monitoring (RLM) in the activated bandwidth part (BWP).
  • RLM Radio Link Monitoring
  • the reference signal is, for example, synchronization signal block/channel state information reference signal (SSB/CSI-RS)
  • Wireless link monitoring is applicable to SA NR (Standalone New Radio), NR-DC (New Radio - New Radio Dual Connectivity) and NE-DC (New Radio - Evolved Universal Terrestrial Radio Access Dual Connectivity) operating modes PCell (primary cell) and PSCell (primary and secondary cell) in NR-DC and EN-DC (Evolved Universal Terrestrial Radio Access - New Wireless Dual Connectivity) operating modes.
  • SA NR Standalone New Radio
  • NR-DC New Radio - New Radio Dual Connectivity
  • NE-DC New Radio - Evolved Universal Terrestrial Radio Access Dual Connectivity
  • PCell primary cell
  • PSCell primary and secondary cell
  • EN-DC Evolved Universal Terrestrial Radio Access - New Wireless Dual Connectivity
  • SSB-based RLM is based on the SSB associated with the initial downlink bandwidth part (DL BWP) and can only be configured for the initial DL BWP and DL BWPs that include the SSB associated with the initial DL BWP.
  • DL BWP downlink bandwidth part
  • RLM is only performed based on CSI-RS. End devices are not required to perform RLM outside of activating DL BWP.
  • the terminal device continues the detection of radio link failure on the source cell until the random access procedure to the target cell is successfully completed. After announcing the RLF, the terminal device remains in RRC_CONNECTED. For the RLF in the source cell, it stops sending or receiving any data through the source link and releases the source link, but maintains the source RRC configuration. If the handover failure is subsequently announced in the target cell, the terminal The device selects a suitable cell and initiates RRC reestablishment.
  • the terminal device If a suitable cell is not found within a period of time after the handover is announced, the terminal device enters the radio resource control idle (RRC_IDLE) state; otherwise, in the case of DAPS handover, the target before releasing the source cell For RLF in the cell, the terminal device selects a suitable cell and initiates RRC reestablishment. If a suitable cell is not found within a period of time after the handover is announced, the terminal device enters RRC_IDLE.
  • RRC_IDLE radio resource control idle
  • the source primary cell group (MCG) MAC indicates a random access problem
  • the source MCG detects a wireless link failure, that is, the source RLF;
  • allowedServingCells only includes secondary cells:
  • MCG detects wireless link failure, that is, MCG RLF
  • the detection of wireless link failure also includes that the terminal will:
  • allowedServingCells only includes secondary cells:
  • SCG detects wireless link failure, that is, SCG RLF
  • the terminal device When the terminal device receives the Radio Resource Control Reconfiguration (RRCReconfiguration) information, the terminal device behaves as follows:
  • RRCReconfiguration includes masterCellGroup or secondaryCellGroup
  • the terminal device will perform MCG/SCG cell group configuration according to 5.3.5.5.
  • CellGroupConfig includes spCellConfig
  • the terminal will configure the secondary primary cell (SpCell) according to 5.3.5.5.7.
  • the terminal configures the RLF timers and constants of this cell group as defined in 5.3.5.5.6. Otherwise, if rlf-TimersAndConstants of this cell group is not configured, if a DAPS bearer is configured, the terminal is the target cell.
  • the group uses the values of timers T301, T310, T311 and constants N310, N311, as included in the ue-TimersAndConstants received in SIB1.
  • the terminal uses the values of timers T301, T310, T311 and constants N310, N311 for the target cell group, just as the ue- received in SIB1 TimersAndConstants includes (value).
  • the terminal equipment performs handover, which means that the terminal equipment performs synchronous reconfiguration of the primary cell;
  • the terminal equipment performs DAPS handover means that when the terminal equipment is configured with a DAPS bearer, the terminal equipment performs Synchronous reconfiguration of the primary cell; during the DAPS handover process of the terminal device, the cell group where the source cell is located can be the source cell group, and the cell group where the target cell is located can be the target cell group.
  • An embodiment of the first aspect provides a method for configuring parameters, which method is applied to a terminal device.
  • Figure 2 is a schematic diagram of a method for configuring parameters according to the embodiment of the first aspect. As shown in Figure 2, the method of configuring parameters includes:
  • Operation 201 In the case where the terminal device is configured with a dual activation protocol stack (DAPS) bearer, when the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to the wireless link failure of the cell group or the received When the first configuration information (rlf-TimersAndConstants) is set to the first state, the terminal device uses the wireless link in the system information block (SIB) 1 of the source cell or the target cell for the synchronously reconfigured target cell group. Information about the failure.
  • SIB system information block
  • performing synchronous reconfiguration of the primary cell means that the terminal equipment performs DAPS switching.
  • DAPS dual activation protocol stack
  • the first configuration information is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constant; the first state is, for example, release.
  • the parameter rlf-TimersAndConstants and release please refer to related technologies.
  • the information related to the wireless link failure in the system information block (SIB) 1 includes: the values of timer T301, timer T310, timer T311, constant N310 and constant N311 included in the system information block (SIB) 1.
  • the terminal device uses the timer T301, timer T310, timer T311, and constant N310 included in the second configuration information received in the system information block (SIB) 1 of the source cell or the target cell for the synchronously reconfigured target cell group. and the value of constant N311.
  • the second configuration information is, for example, the parameter ue-TimersAndConstants, that is, the terminal device timers and constants.
  • the terminal device and the network device have a consistent understanding of the timer and constant values of the wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link failure process too late, and the resulting business interruption.
  • the terminal device may use information related to the radio link failure in the system information block (SIB) 1 of the source cell for the target cell group for synchronization reconfiguration.
  • SIB system information block
  • the standard may be modified based on the following Table 1.
  • the standard when the first configuration information received by the terminal device is set to the first value (for example, release), the standard may be modified based on the following Table 2.
  • the terminal device may obtain the system information block (SIB) 1 of the source cell through a system information block (SIB) 1 acquisition process.
  • the SIB1 acquisition process includes: applying BCCH configuration to obtain MIB; obtaining SIB1 according to the SIB1 information included in the MIB.
  • the terminal device may receive a radio resource control (RRC) reconfiguration message having the system information block (SIB) 1 of the source cell, for example, the parameter dedicatedSIB1- in the RRC reconfiguration message.
  • RRC radio resource control
  • SIB system information block
  • Delivery contains the SIB1 of the active cell.
  • the RRC reconfiguration message is not configured with a DAPS bearer (ie, DAPS bearer).
  • the terminal device may use information related to the radio link failure in the system information block (SIB) 1 of the target cell for the synchronously reconfigured target cell group.
  • SIB system information block
  • the standard may be modified based on the following Table 1.
  • the standard when the first configuration information received by the terminal device is set to the first value (for example, release), the standard may be modified based on the following Table 4.
  • the terminal device may obtain the system information block (SIB) 1 of the target cell through a system information block (SIB) 1 acquisition process.
  • SIB system information block
  • the terminal device may receive a radio resource control (RRC) reconfiguration message having the system information block (SIB) 1 of the target cell, for example, the parameter dedicatedSIB1- in the RRC reconfiguration message.
  • RRC radio resource control
  • SIB system information block
  • Delivery contains the SIB1 of the target cell.
  • any DAPS bearer ie, any DAPS bearer
  • the terminal device when the terminal device is configured with a DAPS bearer, it receives a radio resource control (RRC) reconfiguration carrying synchronization reconfiguration information (the synchronization reconfiguration information is, for example, parameter reconfiguration with sync). message, the terminal device can obtain the system information block (SIB) 1 of the target cell through the system information (System Information, SI) acquisition process.
  • RRC radio resource control
  • the terminal device when the terminal device is configured with a DAPS bearer, when the rlf-TimersAndConstants of a cell group is not configured, or the received rlf-TimersAndConstants is set to release, the terminal device receives the message sent by the network device.
  • the dedicated system information block 1 transmits (dedicatedSIB1-Delivery) information, and the dedicated system information block 1 transmits information having information related to radio link failure in the system information block (SIB) 1 of the target cell.
  • the network device may forcefully send dedicated SIB1-Delivery information having system information block (SIB)1 of the target cell to the terminal device.
  • the standard can be modified based on the following Table 5.
  • Table 5 the modification involves ASN.1.
  • the standard can be modified based on the following Table 6.
  • Table 6 the modification does not involve ASN.1.
  • An embodiment of the second aspect of the present application provides a method for configuring parameters, which method is applied to a network device, and which corresponds to the embodiment of the first aspect.
  • Figure 3 is a schematic diagram of a method for configuring parameters according to the embodiment of the second aspect. As shown in Figure 3, the method includes:
  • Operation 301 The network device sends a radio resource control (RRC) reconfiguration message carrying synchronized reconfiguration information to the terminal device.
  • RRC radio resource control
  • DAPS dual activation protocol stack
  • the terminal device when the terminal device is not When the first configuration information (rlf-TimersAndConstants) related to wireless link failure of the configured cell group or the first configuration information (rlf-TimersAndConstants) sent to the terminal device is set to the first state (release), the wireless resource
  • the control reconfiguration message includes dedicated system information block 1 delivery information (dedicatedSIB1-Delivery), which has information related to radio link failure in the system information block (SIB) 1 of the target cell.
  • the synchronization reconfiguration information is, for example, parameter reconfiguration with sync.
  • the first configuration information is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constant; the first state is, for example, release.
  • the parameter rlf-TimersAndConstants and release please refer to related technologies.
  • the information related to the radio link failure in the system information block (SIB) 1 of the target cell includes: timer T301, timer T310, timer T311, constant N310 and constant N311 included in the system information block (SIB) 1. value.
  • the terminal device uses the timer T301, timer T310, timer T311, constant N310 and constant included in the second configuration information received in the system information block (SIB) 1 of the target cell for the target cell group for synchronous reconfiguration.
  • the second configuration information is, for example, the parameter ue-TimersAndConstants, that is, the terminal device timers and constants.
  • the terminal device and the network device have a consistent understanding of the timer and constant values of the wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link failure process too late, and the resulting business interruption.
  • An embodiment of the third aspect provides a method for configuring parameters, which method is applied to a network device.
  • Figure 4 is a schematic diagram of a method for configuring parameters according to the embodiment of the third aspect. As shown in Figure 4, the method of configuring parameters includes:
  • Operation 401 The network device sends a Radio Resource Control (RRC) reconfiguration message carrying synchronized reconfiguration information to the terminal device.
  • RRC Radio Resource Control
  • DAPS dual activation protocol stack
  • the synchronization reconfiguration information is, for example, parameter reconfiguration with sync.
  • the first configuration information is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constant;
  • the second state is, for example, setup.
  • the parameter rlf-TimersAndConstants and setup please refer to related technologies.
  • the network device in the case where a dual activation protocol stack (DAPS) bearer is configured for the terminal device, the network device always configures first configuration information (for example, rlf-TimersAndConstants) for the terminal device, and , the first configuration information (for example, rlf-TimersAndConstants) is always set to the second state (for example, setup).
  • first configuration information for example, rlf-TimersAndConstants
  • the first configuration information (eg, rlf-TimersAndConstants) that is set to the second state (eg, setup) includes the target cell group used by the terminal device in the synchronization reconfiguration process of the main cell.
  • Information related to wireless link failure includes: timer T301, timer T310, timer T311, constant N310 and the value of constant N311.
  • operation 401 may be implemented by modifying Abstract Syntax Notation dotone (ASN.1).
  • ASN.1 Abstract Syntax Notation dotone
  • the standard can be modified according to Table 7 below.
  • operation 401 may be implemented without modifying ASN.1, but by describing it in the domain description.
  • the standard can be modified according to Table 8 below.
  • the terminal device and the network device have a consistent understanding of the timer and constant values of the wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link failure process too late, and resulting business disruption.
  • An embodiment of the fourth aspect provides a method for configuring parameters, which method is applied to a terminal device.
  • Figure 5 is a schematic diagram of a method for configuring parameters according to the embodiment of the fourth aspect. As shown in Figure 5, the method of configuring parameters includes:
  • Operation 501 The terminal device receives a radio resource control reconfiguration message carrying synchronized reconfiguration information from the network device, where, in the case where the terminal device is configured with a dual activation protocol stack (DAPS) bearer, the terminal device receives the radio resource control reconfiguration message from the network device.
  • DAPS dual activation protocol stack
  • the synchronization reconfiguration information is, for example, parameter reconfiguration with sync.
  • the first configuration information is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constant;
  • the second state is, for example, setup.
  • the parameter rlf-TimersAndConstants and setup please refer to related technologies.
  • the wireless resource carrying synchronous reconfiguration information (for example, the synchronous reconfiguration information is reconfiguration with sync)
  • the control (RRC) reconfiguration message always includes the first configuration information (eg, rlf-TimersAndConstants), and the first configuration information (eg, rlf-TimersAndConstants) is always set to the second state (eg, setup) .
  • the first configuration information (eg, rlf-TimersAndConstants) that is set to the second state (eg, setup) includes the target cell group used by the terminal device in the synchronization reconfiguration process of the main cell.
  • Information related to wireless link failure includes: the value of timer T301, timer T310, timer T311, constant N310 and constant N311.
  • the terminal device and the network device have a consistent understanding of the value of the timer and constant of the wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link failure process too late, and resulting business disruption.
  • An embodiment of the fifth aspect provides a method for configuring parameters, which method is applied to a terminal device.
  • Figure 6 is a schematic diagram of a method for configuring parameters according to the embodiment of the fifth aspect. As shown in Figure 6, the method of configuring parameters includes:
  • Operation 601 In the case where the terminal device is configured with a dual activation protocol stack (DAPS) bearer, when the terminal device does not receive the first configuration information related to the wireless link failure or the received first configuration information is set to the first In a state, the terminal device uses the same information related to radio link failure as the source cell group for the target cell group.
  • DAPS dual activation protocol stack
  • the target cell group is a target cell group for synchronous reconfiguration, that is, a target cell group for DAPS handover.
  • the first configuration information related to the radio link failure corresponds to the target cell group associated with the synchronized reconfiguration.
  • the information related to the wireless link failure includes: timer T301, timer T310, timer T311, constant N310 and values of constant N311.
  • the first configuration information is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constant; the first state is, for example, release.
  • the parameter rlf-TimersAndConstants and release please refer to related technologies.
  • using the same information related to the radio link failure as the source cell group may refer to: using the information related to the radio link failure in the system information block (SIB) 1 of the source cell. .
  • SIB system information block
  • the SIB1 of the source cell is used.
  • Information about link failure is, for example, the parameter rlf-TimersAndConstants, that is, the wireless link failure timer and constants; the third state is, for example, release.
  • parameters rlf-TimersAndConstants and release please refer to related technologies.
  • the information related to the radio link failure in the system information block (SIB) 1 of the source cell includes: timer T301, timer T310, timer T311, and constants included in the system information block (SIB) 1 of the source cell. N310 and the value of constant N311.
  • using the same information related to the radio link failure as the source cell group may also refer to: using the third configuration information related to the radio link failure of the source cell group (for example, rlf-TimersAndConstants).
  • the terminal device when the terminal device is configured with the third configuration information (for example, rlf-TimersAndConstants) related to the radio link failure of the source cell group and the received third configuration information (for example, rlf-TimersAndConstants) is set to the fourth state (for example, setup), use the third configuration information (for example, rlf-TimersAndConstants) of the source cell group related to the radio link failure.
  • the fourth state is, for example, setup.
  • the third configuration information (eg, rlf-TimersAndConstants) set to the fourth state (eg, setup) has information related to the radio link failure of the source cell group.
  • the information related to the radio link failure of the source cell group includes: the values of timer T301, timer T310, timer T311, constant N310 and constant N311 of the source cell group.
  • the standard may be modified according to Table 9 below to implement operation 601.
  • the terminal device and the network device have a consistent understanding of the value of the timer and constant of the wireless link failure, thereby avoiding unnecessary triggering of the wireless link failure process or triggering the wireless link failure process too late, and resulting business disruption.
  • An embodiment of the sixth aspect provides an apparatus for configuring parameters, which is applied to a terminal device and corresponds to the method of configuring parameters of the embodiment of the first aspect.
  • FIG. 7 is a schematic diagram of a device for configuring parameters according to the embodiment of the sixth aspect.
  • the device 700 for configuring parameters includes a first application unit 701 .
  • the terminal device is configured with a dual activation protocol stack (DAPS) bearer
  • DAPS dual activation protocol stack
  • the terminal device when the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to the radio link failure of the cell group or the received first configuration information
  • the first application unit 701 uses the system information block (SIB) 1 of the source cell or the target cell and the wireless Information about link failure.
  • SIB system information block
  • the information related to the wireless link failure in the system information block (SIB) 1 includes: timer T301, timer T310, timer T311, and constant N310 included in the system information block (SIB) 1 and the value of constant N311.
  • the second configuration information (ue-TimersAndConstants) received in system information block (SIB) 1 includes values of timer T301, timer T310, timer T311, constant N310 and constant N311.
  • the device 700 for configuring parameters further includes a first acquisition unit 702 .
  • the first obtaining unit 702 obtains the system information block (SIB) 1 through the system information block (SIB) 1 obtaining process; or, the first obtaining unit 702 receives a radio resource control (RRC) reconfiguration message, and the radio resource control reconfiguration message has the system information block (SIB) 1. Information Block (SIB)1.
  • the device 700 for configuring parameters further includes a second acquisition unit 703 .
  • the second acquisition unit 703 obtains the system information block (SIB) 1 of the target cell through the system information (SI) acquisition process. .
  • the device 700 for configuring parameters further includes a third acquisition unit 704 .
  • the third acquisition unit 704 receives the dedicated system information block 1 delivery information (dedicatedSIB1-Delivery) sent by the network device.
  • the dedicated system information block 1 delivery information has information related to wireless link failure in the system information block (SIB) 1 of the target cell. Information.
  • An embodiment of the seventh aspect provides an apparatus for configuring parameters, which is applied to a network device and corresponds to the method of configuring parameters of the embodiment of the second aspect.
  • FIG. 8 is a schematic diagram of a device for configuring parameters in the embodiment of the seventh aspect.
  • the device 800 for configuring parameters includes a first configuration unit 801 .
  • the first configuration unit 801 sends a radio resource control (RRC) reconfiguration message to the terminal device.
  • RRC radio resource control
  • the radio resource control reconfiguration message includes dedicated system information block 1 delivery information (dedicatedSIB1-Delivery), and the dedicated system information
  • the block 1 transmission information has the information related to the radio link failure in the system information block (SIB) 1 of the target cell.
  • the information related to the wireless link failure in the system information block (SIB) 1 includes: timer T301, timer T310, timer T311, and constant N310 included in the system information block (SIB) 1 and the value of constant N311.
  • the information related to wireless link failure in the system information block (SIB) 1 includes: the timer T301 included in the second configuration information (ue-TimersAndConstants) received in the system information block (SIB) 1. T310, timer T311, constant N310 and the value of constant N311.
  • An embodiment of the eighth aspect provides an apparatus for configuring parameters, which is applied to a network device and corresponds to the method of configuring parameters of the embodiment of the third aspect.
  • Figure 9 is a schematic diagram of a device for configuring parameters in the embodiment of the eighth aspect. As shown in Figure 9, the device 900 for configuring parameters includes a second configuration unit 901.
  • the second configuration unit 901 sends a radio resource control (RRC) reconfiguration message carrying synchronization reconfiguration (reconfiguration with sync) information to the terminal device.
  • RRC radio resource control
  • the second configuration unit 901 configures the first configuration information (rlf-TimersAndConstants) related to the wireless link failure for the terminal device, and the third A configuration information (rlf-TimersAndConstants) is set to the second state (setup).
  • the second configuration unit 901 when the dual activation protocol stack (DAPS) bearer is configured for the terminal device, the second configuration unit 901 always configures the first configuration information (rlf-TimersAndConstants) for the terminal device, And the first configuration information (rlf-TimersAndConstants) is always set to the second state (setup).
  • the first configuration information (rlf-TimersAndConstants) includes information related to wireless link failure used by the terminal device for the target cell group.
  • information related to wireless link failure includes:
  • timer T301 timer T301, timer T310, timer T311, constant N310 and constant N311.
  • An embodiment of the ninth aspect provides an apparatus for configuring parameters, which is applied to a terminal device and corresponds to the method of configuring parameters of the embodiment of the fourth aspect.
  • Figure 10 is a schematic diagram of a device for configuring parameters in the embodiment of the ninth aspect. As shown in Figure 10, the device 1000 for configuring parameters includes a second application unit 1001.
  • the second application unit 1001 receives a radio resource control (RRC) reconfiguration message carrying synchronization reconfiguration (reconfiguration with sync) information from a network device.
  • RRC radio resource control
  • the second application unit 1001 receives the first configuration information (rlf-TimersAndConstants) related to the wireless link failure from the network device, wherein, the The first configuration information (rlf-TimersAndConstants) is set to the second state (setup).
  • DAPS dual activation protocol stack
  • the first configuration information (rlf-TimersAndConstants) set to the second state (setup) includes information related to wireless link failure used by the terminal device for the target cell group.
  • the radio resource control (RRC) reconfiguration message carrying synchronization reconfiguration (reconfiguration with sync) information always includes a first Configuration information (rlf-TimersAndConstants), and the first configuration information (rlf-TimersAndConstants) is always set to the second state (setup).
  • DAPS dual activation protocol stack
  • information related to wireless link failure includes:
  • An embodiment of the tenth aspect provides an apparatus for configuring parameters, which is applied to a terminal device and corresponds to the method of configuring parameters of the embodiment of the fifth aspect.
  • Figure 11 is a schematic diagram of a device for configuring parameters in the embodiment of the tenth aspect. As shown in Figure 11, the device 1100 for configuring parameters includes a third application unit 1101.
  • the third application unit 1101 uses the same information related to wireless link failure as the source cell group for the target cell group.
  • the first configuration information (rlf-TimersAndConstants) related to wireless link failure corresponds to the target cell group of synchronous reconfiguration (reconfiguration with sync).
  • information related to wireless link failure includes:
  • timer T301 timer T301, timer T310, timer T311, constant N310 and constant N311.
  • using the same information related to the radio link failure as the source cell group includes: using the information related to the radio link failure in the system information block (SIB) 1 of the source cell.
  • SIB system information block
  • the terminal device is not configured with the third configuration information (rlf-TimersAndConstants) related to wireless link failure of the source cell group or the received third configuration information (rlf-TimersAndConstants) is set to the third In the release state, the information related to the radio link failure in the system information block (SIB) 1 of the source cell is used.
  • using the same information related to radio link failure as the source cell group includes: using third configuration information (rlf-TimersAndConstants) of the source cell group related to radio link failure.
  • third configuration information rlf-TimersAndConstants
  • the terminal device is configured with the third configuration information (rlf-TimersAndConstants) related to the radio link failure of the source cell group and the received third configuration information (rlf-TimersAndConstants) is set to the fourth state ( setup)
  • use the third configuration information (rlf-TimersAndConstants) of the source cell group related to radio link failure use the third configuration information (rlf-TimersAndConstants) of the source cell group related to radio link failure.
  • An embodiment of the present application also provides a communication system, which may include a terminal device and a network device. At least one of the terminal device and the network device may have the composition of the electronic device shown in FIG. 12 .
  • FIG. 12 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • electronic device 1200 may include a processor 1210 (eg, a central processing unit CPU) and a memory 1212; the memory 1212 is coupled to the processor 1210.
  • the memory 1212 can store various data; in addition, it also stores an information processing program 1230, and the program 1230 is executed under the control of the processor 1210.
  • the processor 1210 may be configured to execute a program to implement the methods in the embodiments of the first to fourth aspects.
  • the electronic device 1200 may also include: a transceiver 1240 and an antenna 1250 , etc.; the functions of the above components are similar to those in the prior art and will not be described again here. It is worth noting that the electronic device 1200 does not necessarily include all components shown in FIG. 12 ; in addition, the electronic device 1200 may also include components not shown in FIG. 12 , and reference may be made to the prior art.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect, the fourth aspect or the fifth aspect. .
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect or the third aspect.
  • Embodiments of the present application also provide a storage medium storing a computer program, wherein the computer program causes an electronic device to perform the method described in at least one of the embodiments of the first to fifth aspects.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or component described above, or enables the logic component to implement the various methods described above or steps.
  • This application also involves storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, etc.
  • the methods/devices described in connection with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules using a Field Programmable Gate Array (FPGA), for example.
  • FPGA Field Programmable Gate Array
  • the software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and storage media may be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings may be implemented as a general-purpose processor or a digital signal processor (DSP) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microprocessors. processor, one or more microprocessors combined with DSP communications, or any other such configuration.
  • a method of configuring parameters, applied to terminal equipment includes:
  • DAPS dual activation protocol stack
  • the terminal device When the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to the radio link failure of the cell group or the received first configuration information (rlf-TimersAndConstants) is set to the first state (release )hour,
  • the terminal device uses the information related to the radio link failure in the system information block (SIB) 1 of the source cell or the target cell for the target cell group for synchronous reconfiguration.
  • SIB system information block
  • the information related to wireless link failure in the system information block (SIB) 1 includes:
  • timer T301 timer T301, timer T310, timer T311, constant N310 and constant N311 included in system information block (SIB) 1.
  • the information related to wireless link failure in the system information block (SIB) 1 includes:
  • the second configuration information (ue-TimersAndConstants) received in system information block (SIB) 1 includes the values of timer T301, timer T310, timer T311, constant N310 and constant N311.
  • the terminal device obtains the system information block (SIB) 1 through a system information block (SIB) 1 acquisition process; or
  • the terminal device receives a radio resource control (RRC) reconfiguration message, the radio resource control reconfiguration message having the system information block (SIB) 1.
  • RRC radio resource control
  • SIB system information block
  • the terminal device When the terminal device receives a radio resource control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information, the terminal device obtains the system information block (SI) of the target cell through a system information (SI) acquisition process. SIB)1.
  • RRC radio resource control
  • SIB system information block
  • the terminal device receives the dedicated system information block 1 delivery information (dedicatedSIB1-Delivery) sent by the network device.
  • the dedicated system information block 1 delivery information has the information in the system information block (SIB) 1 of the target cell and the wireless link. Information about the failure.
  • a method of configuring parameters, applied to network equipment includes:
  • the network device sends a radio resource control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information to the terminal device,
  • RRC radio resource control
  • DAPS dual activation protocol stack
  • the radio resource control reconfiguration message includes dedicated system information block 1 delivery information (dedicatedSIB1-Delivery).
  • the dedicated system information block 1 delivery information has information related to radio link failure in the system information block (SIB) 1 of the target cell. Information.
  • the information related to wireless link failure in the system information block (SIB) 1 includes:
  • the system information block (SIB) 1 includes timer T301, timer T310, timer T311, the value of constant N310 and the value of constant N311.
  • the information related to wireless link failure in the system information block (SIB) 1 includes:
  • the second configuration information (ue-TimersAndConstants) received in system information block (SIB) 1 includes the values of timer T301, timer T310, timer T311, constant N310 and constant N311.
  • a method of configuring parameters, applied to network equipment includes:
  • the network device sends a radio resource control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information to the terminal device,
  • RRC radio resource control
  • the network device configures first configuration information (rlf-TimersAndConstants) related to wireless link failure for the terminal device, and the The first configuration information (rlf-TimersAndConstants) is set to the second state (setup).
  • first configuration information rlf-TimersAndConstants
  • DAPS dual activation protocol stack
  • the network device always configures the first configuration information (rlf-TimersAndConstants) for the terminal device, and the first configuration information (rlf-TimersAndConstants) is always set to the second state (setup).
  • the first configuration information includes information related to wireless link failure used by the terminal device for the target cell group.
  • the information related to wireless link failure includes:
  • timer T301 timer T301, timer T310, timer T311, constant N310 and constant N311.
  • a method of configuring parameters, applied to terminal equipment includes:
  • the terminal device receives a radio resource control (RRC) reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) information from the network device,
  • RRC radio resource control
  • the terminal device receives first configuration information (rlf-TimersAndConstants) related to wireless link failure from the network device, wherein: The first configuration information (rlf-TimersAndConstants) is set to the second state (setup).
  • DAPS dual activation protocol stack
  • the first configuration information (rlf-TimersAndConstants) set to the second state (setup) includes information related to wireless link failure used by the terminal device for the target cell group.
  • the information related to wireless link failure includes:
  • DAPS dual activation protocol stack
  • the radio resource control (RRC) reconfiguration message carrying synchronization reconfiguration (reconfiguration with sync) information always includes the first configuration information (rlf-TimersAndConstants), and the first configuration information (rlf-TimersAndConstants) always is set to the second state (setup).
  • a method of configuring parameters, applied to terminal equipment includes:
  • DAPS dual activation protocol stack
  • the terminal device When the terminal device is not configured with the first configuration information (rlf-TimersAndConstants) related to wireless link failure or the received first configuration information (rlf-TimersAndConstants) is set to the first state (release),
  • the terminal device uses the same information about radio link failure for the target cell group as the source cell group.
  • the first configuration information (rlf-TimersAndConstants) related to wireless link failure corresponds to the target cell group of synchronous reconfiguration (reconfiguration with sync).
  • the method for configuring parameters as described in appendix 18, wherein the use of the same information related to wireless link failure as the source cell group includes:
  • SIB System Information Block
  • the terminal device When the terminal device is not configured with the third configuration information (rlf-TimersAndConstants) related to wireless link failure of the source cell group or the received third configuration information (rlf-TimersAndConstants) is set to the third state ( release), use the information related to the radio link failure in the system information block (SIB) 1 of the source cell; or
  • the terminal device When the terminal device is configured with the third configuration information (rlf-TimersAndConstants) related to radio link failure of the source cell group and the received third configuration information (rlf-TimersAndConstants) is set to the fourth state ( setup), use the third configuration information (rlf-TimersAndConstants) of the source cell group related to radio link failure.
  • the third configuration information rlf-TimersAndConstants
  • Information related to wireless link failure includes:
  • timer T301 timer T301, timer T310, timer T311, constant N310 and constant N311.

Landscapes

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

Abstract

本申请实施例提供一种配置参数的方法、装置以及通信系统，该配置参数的装置，应用于终端设备，所述装置包括第一应用单元：在所述终端设备被配置了双激活协议栈承载的情况下，当所述终端设备未被配置小区组的与无线链路失败有关的第一配置信息或者收到的所述第一配置信息被设置为第一状态时，所述第一应用单元为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。

Description

配置参数的方法、装置以及通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
双激活协议栈(DAPS，Dual Active Protocol Stack)切换是指终端设备收到切换的无线资源控制(RRC)消息后、直到成功随机接入到目标网络设备(例如，目标gNB)后释放源小区，都维持源网络设备(例如，源gNB)连接的一种切换过程。
DAPS切换期间，终端设备(例如，UE)继续从源gNB接收下行用户数据直到释放源小区，并继续向源gNB传输上行用户数据直到向目标gNB的随机接入过程成功完成。
图1是DAPS切换场景下的一个示意图，终端设备101从源网络设备102切换到目标网络设备103。
DAPS切换期间，仅使用源PCell(主小区)和目标PCell。向UE发送切换命令前，源gNB释放载波聚合(Carrier Aggregation，CA)，双链接(Dual Connectivity，DC)，补充的上行链路(Supplementary Uplink，SUL)，多发送接收点(TRP)，以太网头部压缩(Ethernet Header Compression，EHC)，条件切换机会(Conditional Handover Opportunity，CHO)，上行数据压缩(Uplink Data Compression，UDC)，新无线边链路(NR sidelink)配置和车辆对万物边链路(V2X sidelink)配置，并且在DAPS切换完成前(例如，至少在释放源PCell的同一条消息中)目标gNB不会进行以上配置。
对于RRC触发的DAPS切换，一旦收到切换命令，终端为目标网络设备创建一个媒体访问控制(MAC)实体；为每个配置了DAPS的数据无线承载(Data Radio Bearer，DRB)建立目标的无线链路控制(RLC)实体和一个关联的专用传输通道(Dedicated Transmission Channel，DTCH)逻辑信道；对每个配置了DAPS的DRB，重配分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)实体，其中该PDCP实体有单独的源和目标的安全和可靠头压缩(ROCH)，并将他们与源和目标配置的RLC实体分别关联。
当DAPS切换失败时，如果源链路尚未被释放，UE回退到源小区配置，恢复与 源小区的连接，通过源上报DAPS切换失败，不触发RRC连接重建。
当收到请求DAPS切换的切换命令时，终端设备(例如，UE)挂起源小区信令无线承载(SRBs)，停止发送和接收到源小区的任何RRC控制面信令，并建议与目标小区的SRBs。成功执行DAPS切换后，收到来自目标小区的源小区释放指示时，UE释放源小区SRBs配置。当DAPS切换到目标小区失败时，且如果源小区链路可用，那么UE回退到源小区配置并恢复控制面信令传输的源小区SRBs。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
根据当前机制，如果终端设备被配置了DAPS承载，当未配置一个小区组的第一配置信息(rlf-TimersAndConstants)，或者收到的该第一配置信息被设置为释放(release)时，终端设备为目标小区组使用系统信息块(SIB)1里收到的ue-TimersAndConstants包括的定时器T301，T310，T311和常量N310，N311的值，从而进行与无线链路失败相关的处理。
本申请的发明人发现，如果终端设备被配置了DAPS承载，那么该终端设备很可能处于DAPS切换，也就是该终端设备具有源小区的系统信息块(SIB)1以及目标小区的SIB1，在当前机制下，不同终端设备或终端设备与网络设备之间对于SIB1的来源没有一致理解，例如：(1)基于实现，有些终端设备使用源小区SIB1里的参数/常量，有些终端使用目标小区SIB1里的参数/常量；(2)终端设备和网络设备对于SIB1的来源有不一致的理解，这两种可能将会造成一些终端设备对触发无线链路失败不够灵敏或过于灵敏，即不必要地触发无线链路失败过程或过晚触发无线链路失败过程，从而导致更长的业务中断。
本申请的实施例提供一种配置参数的方法、装置以及通信系统，能够使不同终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的更长时间的业务中断。
根据本申请实施例的一个方面，提供一种配置参数的装置，应用于终端设备，所 述装置包括第一应用单元：
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，
当所述终端设备未被配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述第一应用单元为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
根据本申请实施例的另一个方面，提供一种配置参数的装置，应用于网络设备，所述装置包括第一配置单元：
所述第一配置单元向终端设备发送携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息，
在为所述终端设备配置了双激活协议栈(DAPS)承载的情况下，当没有为所述终端设备配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者发送给所述终端设备的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述无线资源控制重配消息包括专用系统信息块1传送信息(dedicatedSIB1-Delivery)，所述专用系统信息块1传送信息具有目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
根据本申请实施例的另一个方面，提供一种配置参数的装置，应用于网络设备，所述装置包括第二配置单元：
所述第二配置单元向终端设备发送携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息，
在为所述终端设备配置了双激活协议栈(DAPS)承载的情况下，所述第二配置单元为所述终端设备配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，且所述第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
根据本申请实施例的另一个方面，提供一种配置参数的装置，应用于终端设备，所述装置包括第二应用单元：
所述第二应用单元从网络设备接收携带同步重配置(reconfiguration with sync) 信息的无线资源控制(RRC)重配消息，
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，所述第二应用单元从所述网络设备接收与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，其中，所述第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
根据本申请实施例的另一个方面，提供一种配置参数的装置，应用于终端设备，所述装置包括第三应用单元：
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，
当所述终端设备未被配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述第三应用单元为目标小区组使用与源小区组相同的与无线链路失败有关的信息。
本申请实施例的有益效果在于：能够使不同终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是DAPS切换场景下的一个示意图；
图2是第一方面的实施例的配置参数的方法的一个示意图；
图3是第二方面的实施例的配置参数的方法的一个示意图；
图4是第三方面的实施例的配置参数的方法的一个示意图；
图5是第四方面的实施例的配置参数的方法的一个示意图；
图6是第五方面的实施例的配置参数的方法的一个示意图；
图7是第六方面的实施例的配置参数的装置的一个示意图；
图8是第七方面的实施例中配置参数的装置的一个示意图；
图9是第八方面的实施例中配置参数的装置的一个示意图；
图10是第九方面的实施例中配置参数的装置的一个示意图；
图11是第十方面的实施例中配置参数的装置的一个示意图；
图12是本申请实施例的电子设备的组成的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、 增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、中继(relay)、基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、移动终端(MT，mobile termination)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行 监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在本申请的各实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括主信息块(MIB)、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是F1-C信令，或者叫F1AP协议。但本申请不限于此。
关于无线链路失败(RLF)的说明如下。
在无线资源控制连接(RRC_CONNECTED)状态下，基于参考信号和网络配置的参考信号阈值，终端设备在激活的带宽部分(BWP)里执行无线链路监听(Radio Link Monitoring，RLM)。其中，参考信号例如是同步信号块/信道状态信息参考信号(SSB/CSI-RS)
无线链路监听适用于SA NR(独立组网新无线)、NR-DC(新无线-新无线双连接)和NE-DC(新无线-演进的通用地面无线电接入双连接)操作模式下的PCell(主小区)和NR-DC和EN-DC(演进的通用地面无线电接入-新无线双连接)操作模式下的PSCell(主辅小区)。
基于SSB的RLM基于初始下行链路带宽部分(DL BWP)关联的SSB，且仅能为初始DL BWP和包括初始DL BWP关联的SSB的DL BWPs配置。对于其他DL BWPs，RLM仅基于CSI-RS执行。不要求终端设备在激活DL BWP之外执行RLM。
在DAPS切换的情况下，终端设备继续源小区上无线链路失败的检测，直到向目标小区的随机接入过程成功完成。宣布RLF之后，终端设备保持在RRC_CONNECTED，对于源小区里的RLF，停止通过源链路的任何数据发送或接收并释放源链路，但维持源RRC配置，如果之后目标小区里宣布切换失败，终端设备选择一个合适的小区并发起RRC重建，如果在切换宣布后一段时间内未找到一个合适的小区，终端设备进入无线资源控制空闲(RRC_IDLE)状态；否则在DAPS切换情况下对于释放源小区前目标小区里的RLF，终端设备选择一个合适的小区并发起 RRC重建，如果在切换宣布后一段时间内未找到一个合适的小区，终端设备进入RRC_IDLE。
RRC_CONNECTED下的物理层问题的检测，即，终端设备将会：
1>如果配置了任何DAPS承载，当从低层收到源特殊小区的连续N310个“out-of-sync”指示且T304正在运行时：
2>启动源特殊小区的定时器T310。
1>当从低层收到特殊小区的连续N310个“out-of-sync”指示同时T300、T301、T304、T311、T316和T319都未运行：
2>启动相应特殊小区的定时器T310。
物理层问题的恢复，即，当从低层收到特殊小区的连续N311个“in-sync”(同步)指示，同时T310正在运行，终端设备将会：
1>停止相应特殊小区的定时器T310.
1>停止相应特殊小区的定时器T312.
无线链路失败的检测，包括终端将会：
1>如果配置了任何DAPS承载且T304正在运行：
2>一旦源特殊小区里T310超时；或
2>一旦源主小区组(MCG)MAC指示随机接入问题；或
2>一旦源MCG RLC指示已经达到最大重传次数；或
2>一旦源MCG MAC指示持续上行通话前监听(LBT)失败：
3>认为源MCG检测到无线链路失败，即源RLF；
3>挂起源MCG里所有DRBs的发送和接收；
3>重置源MCG MAC；
3>释放源连接
1>否则：
2>DAPS切换期间：以下仅适用于目标PCell
2>一旦PCell里T310超时；或
2>一旦PCell里T312超时；或
2>一旦MCG MAC指示随机接入问题同时T300、T301、T304、T311和T319都未运行；或
2>一旦MCG RLC指示已经达到最大重传次数；或
2>如果作为IAB节点连接，一旦从MCG收到BAP实体的BH RLF指示；或
2>一旦MCG MAC指示持续上行LBT失败同时T304未运行：
3>如果这个指示来自MCG RLC且配置了CA duplication且对MCG激活，且对于相应的逻辑信道，allowedServingCells仅包括辅小区：
4>发起失败信息过程以上报RLC失败
3>否则：
4>认为MCG检测到无线链路失败，即MCG RLF；
4>丢弃存储的分段RRC消息的所有分段；
4>如果AS安全尚未被激活：
5>执行进入RRC_IDLE时的行为，释放原因是“other”；
4>否则，如果AS安全已经被激活但尚未建立SRB2且至少一个DRB，或对于IAB尚未建立SRB2：
5>存储无线链路失败信息；
5>执行进入RRC_IDLE时的行为，释放原因是“RRC连接失败”；
4>否则：
5>存储无线链路失败信息；
5>如果配置了T316；且
5>如果辅小区组(SCG)传输未被挂起；且
5>如果未进行PSCell改变或PSCell增加(即NR-DC情况下NR PSCell的定时器T304未运行或NE-DC情况下E-UTRA PSCell的定时器T307未运行)：
6>发起MCG失败信息过程以上报MCG无线链路失败
5>否则：
6>发起连接重建过程
无线链路失败的检测，还包括终端将会：
1>一旦PSCell里T310超时；或
1>一旦PSCell里T312超时；或
1>一旦SCG MAC指示随机接入问题；或
1>一旦SCG RLC指示已经达到最大重传次数；或
1>如果作为IAB节点连接，一旦从SCG收到BAP实体的BH RLF指示；或
1>一旦SCG MAC指示持续上行LBT失败：
2>如果这个指示来自SCG RLC且配置了CA duplication且对SCG激活，且对于相应的逻辑信道，allowedServingCells仅包括辅小区：
3>发起失败信息过程以上报RLC失败
2>否则：
3>认为SCG检测到无线链路失败，即SCG RLF；
3>如果MCG未挂起：
4>发起SCG失败信息过程以上报SCG无线链路失败。
3>否则：
4>发起连接重建过程。
当终端设备收到无线资源控制重配置(RRCReconfiguration)信息时，终端设备的行为如下：
Figure PCTCN2022110714-appb-000001
Figure PCTCN2022110714-appb-000002
如上所示，如果RRCReconfiguration包括masterCellGroup或secondaryCellGroup，终端设备将会根据5.3.5.5执行MCG/SCG的小区组配置。
Figure PCTCN2022110714-appb-000003
Figure PCTCN2022110714-appb-000004
如果CellGroupConfig包括spCellConfig，终端将会根据5.3.5.5.7配置辅主小区(SpCell)。
Figure PCTCN2022110714-appb-000005
Figure PCTCN2022110714-appb-000006
如果SpCellConfig包括rlf-TimersAndConstants，终端如5.3.5.5.6里定义的配置这个小区组的RLF定时器和常量，否则如果未配置这个小区组的rlf-TimersAndConstants，如果配置了DAPS承载，终端为目标小区组使用定时器T301,T310,T311和常量N310,N311的值，正如SIB1里收到的ue-TimersAndConstants包括的(值)。
5.3.5.5.6里定义的行为如下：
Figure PCTCN2022110714-appb-000007
如上所示，如果收到的rlf-TimersAndConstants设置为release，如果配置了DAPS承载，终端为目标小区组使用定时器T301,T310,T311和常量N310,N311的值，正如SIB1里收到的ue-TimersAndConstants包括的(值)。
在本申请的说明中：终端设备进行切换，是指，终端设备进行主小区的同步重配置；终端设备进行DAPS切换，是指，在终端设备被配置了DAPS承载的情况下，该终端设备进行主小区的同步重配置；在终端设备进行DAPS切换的过程中，源小区所在的小区组可以是源小区组，目标小区所在的小区组可以是目标小区组。
第一方面的实施例
第一方面的实施例提供一种配置参数的方法，该方法应用于终端设备。
图2是第一方面的实施例的配置参数的方法的一个示意图。如图2所示，该配置参数的方法包括：
操作201、在终端设备被配置了双激活协议栈(DAPS)承载的情况下，当终端设备未被配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态时，该终端设备为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
在本申请中，终端设备被配置了双激活协议栈(DAPS)承载的情况下，进行主小区的同步重配置，意味着该终端设备进行DAPS切换。
在操作201中，第一配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第一状态例如是release。关于参数rlf-TimersAndConstants，以及release的说明，可以参考相关技术。
系统信息块(SIB)1里的与无线链路失败有关的信息包括：系统信息块(SIB)1中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。例如，终端设备为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1中收到的第二配置信息包括的定时器T301,定时器T310，定时器T311，常量N310以及常量N311的值。其中，第二配置信息例如是参数ue-TimersAndConstants，即，终端设备定时器和常量，关于参数ue-TimersAndConstants，定时器T301，定时器T310，定时器T311，常量N310以及常量N311的说明，可以参考相关技术。
通过操作201，终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
在操作201的至少一个实施例中，该终端设备可以为同步重配置的目标小区组使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
例如，在终端设备没有被配置第一配置信息的情况下，可以基于如下的表1对标准进行修改。
表1
Figure PCTCN2022110714-appb-000008
Figure PCTCN2022110714-appb-000009
又例如，在终端设备收到的第一配置信息被设置为第一值(例如，release)时，可以基于如下的表2对标准进行修改。
表2
Figure PCTCN2022110714-appb-000010
在一个具体实施方式中，终端设备可以通过系统信息块(SIB)1获取过程获得源小区的该系统信息块(SIB)1。SIB1获取过程包括：应用BCCH配置，获取MIB；根据MIB包括的SIB1的信息，获取SIB1。
在另一个具体实施方式中，终端设备可以接收无线资源控制(RRC)重配消息，RRC重配消息具有源小区的该系统信息块(SIB)1，例如，RRC重配消息中的参数dedicatedSIB1-Delivery(专用SIB1传送)中包含有源小区的SIB1，此外，该RRC重配消息里没有配置DAPS承载(即，DAPS bearer)。
在操作201的至少另一个实施例中，该终端设备可以为同步重配置的目标小区组 使用目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
例如，在终端设备没有被配置第一配置信息的情况下，可以基于如下的表1对标准进行修改。
表3
Figure PCTCN2022110714-appb-000011
Figure PCTCN2022110714-appb-000012
又例如，在终端设备收到的第一配置信息被设置为第一值(例如，release)时，可以基于如下的表4对标准进行修改。
表4
Figure PCTCN2022110714-appb-000013
在一个具体实施方式中，终端设备可以通过系统信息块(SIB)1获取过程获得目标小区的该系统信息块(SIB)1。
在另一个具体实施方式中，终端设备可以接收无线资源控制(RRC)重配消息，RRC重配消息具有目标小区的该系统信息块(SIB)1，例如，RRC重配消息中的参数dedicatedSIB1-Delivery(专用SIB1传送)中包含有目标小区的SIB1，此外，该RRC重配消息里可以被配置任何DAPS承载(即，any DAPS bearer)。
在又一个具体实施方式中，终端设备在被配置了DAPS承载的情况下，在收到携带同步重配置信息(该同步重配置信息例如是参数reconfiguration with sync)的无线 资源控制(RRC)重配消息时，该终端设备可以通过系统信息(System Information，SI)获取过程获得该目标小区的系统信息块(SIB)1。
在再一个具体实施方式中，终端设备在被配置了DAPS承载的情况下，当未配置一个小区组的rlf-TimersAndConstants，或者收到的rlf-TimersAndConstants设置为release时，该终端设备接收网络设备发送的专用系统信息块1传送(dedicatedSIB1-Delivery)信息，该专用系统信息块1传送信息具有该目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。例如，网络设备可以强制向该终端设备发送具有目标小区的系统信息块(SIB)1的专用系统信息块1传送(dedicatedSIB1-Delivery)信息。
例如，可以基于如下的表5对标准进行修改，在表5中，修改涉及到ASN.1。
表5
Figure PCTCN2022110714-appb-000014
Figure PCTCN2022110714-appb-000015
Figure PCTCN2022110714-appb-000016
Figure PCTCN2022110714-appb-000017
Figure PCTCN2022110714-appb-000018
又例如，可以基于如下的表6对标准进行修改，在表6中，修改不涉及到ASN.1。
表6
Figure PCTCN2022110714-appb-000019
Figure PCTCN2022110714-appb-000020
Figure PCTCN2022110714-appb-000021
Figure PCTCN2022110714-appb-000022
Figure PCTCN2022110714-appb-000023
第二方面的实施例
本申请第二方面的实施例提供一种配置参数的方法，该方法应用于网络设备，该方法与第一方面的实施例对应。
图3是第二方面的实施例的配置参数的方法的一个示意图，如图3所示，该方法包括：
操作301、网络设备向终端设备发送携带同步重配置信息的无线资源控制(RRC)重配消息，在为该终端设备配置了双激活协议栈(DAPS)承载的情况下，当没有为该终端设备配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者发送给该终端设备的第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，该无线资源控制重配消息包括专用系统信息块1传送信息(dedicatedSIB1-Delivery)，该专用系统信息块1传送信息具有目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
在操作301中，同步重配置信息例如是参数reconfiguration with sync。
在操作301中，第一配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第一状态例如是release。关于参数rlf-TimersAndConstants，以及release的说明，可以参考相关技术。
目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息包括：系统信息块(SIB)1中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。例如，终端设备为同步重配置的目标小区组使用目标小区的系统信息块(SIB)1中收到的第二配置信息中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。其中，第二配置信息例如是参数ue-TimersAndConstants，即，终端设备定时器和常量，关于参数ue-TimersAndConstants，定时器T301，定时器T310，定时器T311，常量N310以及常量N311的说明，可以参考相关技术。
通过操作301，终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
第三方面的实施例
第三方面的实施例提供一种配置参数的方法，该方法应用于网络设备。
图4是第三方面的实施例的配置参数的方法的一个示意图。如图4所示，该配置参数的方法包括：
操作401、网络设备向终端设备发送携带同步重配置信息的无线资源控制(RRC)重配消息，其中，在为该终端设备配置了双激活协议栈(DAPS)承载的情况下，该网络设备为该终端设备配置与无线链路失败有关的第一配置信息，且该第一配置信息被设置为第二状态。
在操作401中，同步重配置信息例如是参数reconfiguration with sync。
在操作401中，第一配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第二状态例如是setup(设置)。关于参数rlf-TimersAndConstants，以及setup的说明，可以参考相关技术。
在操作401的至少一个实施例中，在为终端设备配置了双激活协议栈(DAPS)承载的情况下，网络设备总是为该终端设备配置第一配置信息(例如，rlf-TimersAndConstants)，并且，该第一配置信息(例如，rlf-TimersAndConstants)总是被设置为第二状态(例如，setup)。
在操作401中，被设置为第二状态(例如，setup)的该第一配置信息(例如，rlf-TimersAndConstants)中包含有该终端设备为主小区的同步重配置过程中的目标小区组使用的与无线链路失败有关的信息。其中，与无线链路失败有关的信息包括：定时器T301,定时器T310,定时器T311，常量N310以及常量N311的值。
在至少一个实施例中，可以通过修改抽象语法标记1(Abstract Syntax Notation dotone，ASN.1)来实现操作401。
例如，可以根据下面的表7，对标准进行修改。
表7
Figure PCTCN2022110714-appb-000024
Figure PCTCN2022110714-appb-000025
Figure PCTCN2022110714-appb-000026
Figure PCTCN2022110714-appb-000027
Figure PCTCN2022110714-appb-000028
Figure PCTCN2022110714-appb-000029
在至少另一个实施例中，可以不修改ASN.1，而是通过在域描述里进行说明，从而实现操作401。
例如，可以根据下面的表8，对标准进行修改。
表8
Figure PCTCN2022110714-appb-000030
Figure PCTCN2022110714-appb-000031
Figure PCTCN2022110714-appb-000032
Figure PCTCN2022110714-appb-000033
Figure PCTCN2022110714-appb-000034
Figure PCTCN2022110714-appb-000035
通过第三方面的实施例，终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
第四方面的实施例
第四方面的实施例提供一种配置参数的方法，该方法应用于终端设备。
图5是第四方面的实施例的配置参数的方法的一个示意图。如图5所示，该配置参数的方法包括：
操作501、终端设备从网络设备接收携带同步重配置信息的无线资源控制重配消息，其中，在该终端设备被配置了双激活协议栈(DAPS)承载的情况下，该终端设备从该网络设备接收与无线链路失败有关的第一配置信息，该第一配置信息被设置为第二状态。
在操作501中，同步重配置信息例如是参数reconfiguration with sync。
在操作501中，第一配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第二状态例如是setup(设置)。关于参数rlf-TimersAndConstants，以及setup的说明，可以参考相关技术。
在操作501的至少一个实施例中，在该终端设备被配置了双激活协议栈(DAPS)承载的情况下，携带同步重配置信息(例如，同步重配置信息是reconfiguration with sync)的该无线资源控制(RRC)重配消息总是包括该第一配置信息(例如， rlf-TimersAndConstants)，并且，该第一配置信息(例如，rlf-TimersAndConstants)总是被设置为第二状态(例如，setup)。
在操作501中，被设置为第二状态(例如，setup)的该第一配置信息(例如，rlf-TimersAndConstants)中包含有该终端设备为主小区的同步重配置过程中的目标小区组使用的与无线链路失败有关的信息。其中，与无线链路失败有关的信息包括：定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
通过第四方面的实施例，终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
第五方面的实施例
第五方面的实施例提供一种配置参数的方法，该方法应用于终端设备。
图6是第五方面的实施例的配置参数的方法的一个示意图。如图6所示，该配置参数的方法包括：
操作601、在终端设备被配置了双激活协议栈(DAPS)承载的情况下，当终端设备未被与无线链路失败有关的第一配置信息或者收到的该第一配置信息被设置为第一状态时，该终端设备为目标小区组使用与源小区组相同的与无线链路失败有关的信息。
在操作601中，目标小区组是同步重配置的目标小区组，即，DAPS切换的目标小区组。与无线链路失败有关的第一配置信息对应与该同步重配置的该目标小区组。
在操作601中，与无线链路失败有关的信息包括：定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
在操作601中，第一配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第一状态例如是release。关于参数rlf-TimersAndConstants，以及release的说明，可以参考相关技术。
在操作601的至少一个实施例中，使用与源小区组相同的与无线链路失败有关的信息，可以指：使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
例如，当该终端设备未被配置源小区组的与无线链路失败有关的第三配置信息或者收到的该第三配置信息被设置为第三状态时，使用源小区的SIB1里的与无线链路 失败有关的信息。其中，第三配置信息例如是参数rlf-TimersAndConstants，即，无线链路失败计时器和常量；第三状态例如是release。关于参数rlf-TimersAndConstants，以及release的说明，可以参考相关技术。
其中，源小区的系统信息块(SIB)1里的与无线链路失败有关的信息包括：源小区的系统信息块(SIB)1中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
在操作601的至少另一个实施例中，使用与源小区组相同的与无线链路失败有关的信息，也可以指：使用源小区组的与无线链路失败有关的第三配置信息(例如，rlf-TimersAndConstants)。
例如，当终端设备被配置了源小区组的与无线链路失败有关的第三配置信息(例如，rlf-TimersAndConstants)且收到的第三配置信息(例如，rlf-TimersAndConstants)被设置为第四状态(例如，setup)时，使用源小区组的与无线链路失败有关的第三配置信息(例如，rlf-TimersAndConstants)。其中，第四状态例如是setup。被设置为第四状态(例如，setup)的第三配置信息(例如，rlf-TimersAndConstants)具有该源小区组的与无线链路失败有关的信息。其中，该源小区组的与无线链路失败有关的信息包括：该源小区组的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
在一个具体实施例中，可以根据下面的表9，对标准进行修改，从而实施操作601。
表9
Figure PCTCN2022110714-appb-000036
Figure PCTCN2022110714-appb-000037
Figure PCTCN2022110714-appb-000038
通过第五方面的实施例，终端设备以及网络设备对无线链路失败的定时器和常量的值有一致理解，从而避免不必要地触发无线链路失败过程或过晚触发无线链路失败过程，以及由此造成的业务中断。
第六方面的实施例
第六方面的实施例提供一种配置参数的装置，应用于终端设备，与第一方面的实施例的配置参数的方法对应。
图7是第六方面的实施例的配置参数的装置的一个示意图，如图7所示，配置参数的装置700包括第一应用单元701。
在终端设备被配置了双激活协议栈(DAPS)承载的情况下，当终端设备未被配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，第一应用单元701为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
在至少一个实施例中，系统信息块(SIB)1里的与无线链路失败有关的信息包括：系统信息块(SIB)1中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。例如，系统信息块(SIB)1中收到的第二配置信息(ue-TimersAndConstants)包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
如图7所示，配置参数的装置700还包括第一获取单元702。第一获取单元702通过系统信息块(SIB)1获取过程获得系统信息块(SIB)1；或者，第一获取单元702接收无线资源控制(RRC)重配消息，无线资源控制重配消息具有系统信息块(SIB)1。
如图7所示，配置参数的装置700还包括第二获取单元703。终端设备收到携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息时，第二获取单元703通过系统信息(SI)获取过程获得目标小区的系统信息块(SIB)1。
如图7所示，配置参数的装置700还包括第三获取单元704。第三获取单元704接收网络设备发送的专用系统信息块1传送信息(dedicatedSIB1-Delivery)，该专用系统信息块1传送信息具有目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
第七方面的实施例
第七方面的实施例提供一种配置参数的装置，应用于网络设备，与第二方面的实施例的配置参数的方法对应。
图8是第七方面的实施例中配置参数的装置的一个示意图，如图8所示，配置参数的装置800包括第一配置单元801。
第一配置单元801向终端设备发送无线资源控制(RRC)重配消息。
其中，在为该终端设备配置了双激活协议栈(DAPS)承载的情况下，当没有为终端设备配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者发送给终端设备的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，该无线资源控制重配消息包括专用系统信息块1传送信息(dedicatedSIB1-Delivery)，所述专用系统信息块1传送信息具有目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
在至少一个实施例中，系统信息块(SIB)1里的与无线链路失败有关的信息包括：系统信息块(SIB)1中包括的定时器T301，定时器T310，定时器T311，常量N310的值以及常量N311的值。例如，其中，系统信息块(SIB)1里的与无线链路失败有关的信息包括：系统信息块(SIB)1中收到的第二配置信息(ue-TimersAndConstants)包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
第八方面的实施例
第八方面的实施例提供一种配置参数的装置，应用于网络设备，与第三方面的实施例的配置参数的方法对应。
图9是第八方面的实施例中配置参数的装置的一个示意图，如图9所示，配置参数的装置900包括第二配置单元901。
第二配置单元901向终端设备发送携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息。
其中，在为终端设备配置了双激活协议栈(DAPS)承载的情况下，第二配置单元901为该终端设备配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，且该第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
在至少一个实施例中，在为该终端设备配置了双激活协议栈(DAPS)承载的情况下，第二配置单元901总是为该终端设备配置所述第一配置信息(rlf-TimersAndConstants)，且该第一配置信息(rlf-TimersAndConstants)总是被设置为第二状态(setup)。其中，该第一配置信息(rlf-TimersAndConstants)中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
在至少一个实施例中，与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
第九方面的实施例
第九方面的实施例提供一种配置参数的装置，应用于终端设备，与第四方面的实施例的配置参数的方法对应。
图10是第九方面的实施例中配置参数的装置的一个示意图，如图10所示，配置参数的装置1000包括第二应用单元1001。
第二应用单元1001从网络设备接收携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息。
其中，在终端设备被配置了双激活协议栈(DAPS)承载的情况下，第二应用单元1001从网络设备接收与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，其中，所述第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
其中，被设置为第二状态(setup)的所述第一配置信息(rlf-TimersAndConstants)中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
在至少一个实施例中，在终端设备被配置了双激活协议栈(DAPS)承载的情况下，携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配 消息总是包括第一配置信息(rlf-TimersAndConstants)，且所述第一配置信息(rlf-TimersAndConstants)总是被设置为第二状态(setup)。
在至少一个实施例中，与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310的值以及常量N311的值。
第十方面的实施例
第十方面的实施例提供一种配置参数的装置，应用于终端设备，与第五方面的实施例的配置参数的方法对应。
图11是第十方面的实施例中配置参数的装置的一个示意图，如图11所示，配置参数的装置1100包括第三应用单元1101。
在终端设备被配置了双激活协议栈(DAPS)承载的情况下，当终端设备未被配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，第三应用单元1101为目标小区组使用与源小区组相同的与无线链路失败有关的信息。
其中，与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)对应同步重配置(reconfiguration with sync)的目标小区组。
在至少一个实施例中，与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
在至少一个具体实施方式中，使用与源小区组相同的与无线链路失败有关的信息，包括：使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息。例如，当所述终端设备未被配置源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)或者收到的所述第三配置信息(rlf-TimersAndConstants)被设置为第三状态(release)时，使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
在至少另一个具体实施方式中，使用与源小区组相同的与无线链路失败有关的信息，包括：使用源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)。例如，当终端设备被配置了源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)且收到的所述第三配置信息(rlf-TimersAndConstants)被设置为第四状态(setup)时，使用源小区组的与无线链 路失败有关的第三配置信息(rlf-TimersAndConstants)。
第十二方面的实施例
本申请实施例还提供一种通信系统，该通信系统可以包括终端设备和网络设备。该终端设备和网络设备中的至少一者可以具有图12所示的电子设备的组成。
图12是本申请实施例的电子设备的组成的一个示意图。如图12所示，电子设备1200可以包括：处理器1210(例如中央处理器CPU)和存储器1212；存储器1212耦合到处理器1210。其中该存储器1212可存储各种数据；此外还存储信息处理的程序1230，并且在处理器1210的控制下执行该程序1230。
例如，处理器1210可以被配置为执行程序而实现如第一方面的实施例至第四方面的实施例中的方法。
此外，如图12所示，电子设备1200还可以包括：收发机1240和天线1250等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，电子设备1200也并不是必须要包括图12中所示的所有部件；此外，电子设备1200还可以包括图12中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一方面、第四方面或第五方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第二方面或第三方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得电子设备执行第一方面至第五方面的实施例中至少一者所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用 现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
1.一种配置参数的方法，应用于终端设备，所述方法包括：
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，
当所述终端设备未被配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述终端设备为同步重配置的目标小区组使用源小区或者目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
2.如附记1所述的配置参数的方法，其中，
所述系统信息块(SIB)1里的与无线链路失败有关的信息包括：
系统信息块(SIB)1中包括的定时器T301,定时器T310,定时器T311，常量N310以及常量N311的值。
3.如附记1或2所述的配置参数的方法，其中，
所述系统信息块(SIB)1里的与无线链路失败有关的信息，包括：
系统信息块(SIB)1中收到的第二配置信息(ue-TimersAndConstants)包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
4.如附记1所述的配置参数的方法，其中，所述方法还包括：
所述终端设备通过系统信息块(SIB)1获取过程获得所述系统信息块(SIB)1；或者
所述终端设备接收无线资源控制(RRC)重配消息，所述无线资源控制重配消息具有所述系统信息块(SIB)1。
5.如附记1所述的配置参数的方法，其中，所述方法还包括：
所述终端设备收到携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息时，所述终端设备通过系统信息(SI)获取过程获得所述目标小区的系统信息块(SIB)1。
6.如附记1所述的配置参数的方法，其中，所述方法还包括：
所述终端设备接收网络设备发送的专用系统信息块1传送信息(dedicatedSIB1-Delivery)，所述专用系统信息块1传送信息具有所述目标小区的系统信息块(SIB)1里的与无线链路失败有关的信息。
7.一种配置参数的方法，应用于网络设备，所述方法包括：
所述网络设备向终端设备发送携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息，
在为所述终端设备配置了双激活协议栈(DAPS)承载的情况下，
当没有为所述终端设备配置小区组的与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者发送给所述终端设备的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述无线资源控制重配消息包括专用系统信息块1传送信息(dedicatedSIB1-Delivery)，所述专用系统信息块1传送信息具有目标小区的系统信 息块(SIB)1里的与无线链路失败有关的信息。
8.如附记7所述的配置参数的方法，其中，
所述系统信息块(SIB)1里的与无线链路失败有关的信息包括：
所述系统信息块(SIB)1中包括的定时器T301,定时器T310,定时器T311，常量N310的值以及常量N311的值。
9.如附记7或8所述的配置参数的方法，其中，
其中，所述系统信息块(SIB)1里的与无线链路失败有关的信息，包括：
系统信息块(SIB)1中收到的第二配置信息(ue-TimersAndConstants)包括的定时器T301,定时器T310,定时器T311，常量N310以及常量N311的值。
10.一种配置参数的方法，应用于网络设备，所述方法包括：
所述网络设备向终端设备发送携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息，
在为所述终端设备配置了双激活协议栈(DAPS)承载的情况下，所述网络设备为所述终端设备配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，且所述第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
11.如附记10所述的配置参数的方法，其中，
在为所述终端设备配置了双激活协议栈(DAPS)承载的情况下，
所述网络设备总是为所述终端设备配置所述第一配置信息(rlf-TimersAndConstants)，且所述第一配置信息(rlf-TimersAndConstants)总是被设置为第二状态(setup)。
12.如附记10所述的配置参数的方法，其中，
所述第一配置信息(rlf-TimersAndConstants)中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
13.如附记12所述的配置参数的方法，其中，
所述与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
14.一种配置参数的方法，应用于终端设备，所述方法包括：
所述终端设备从网络设备接收携带同步重配置(reconfiguration with sync)信息的无线资源控制(RRC)重配消息，
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，所述终端设备从所述网络设备接收与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)，其中，所述第一配置信息(rlf-TimersAndConstants)被设置为第二状态(setup)。
15.如附记14所述的配置参数的方法，其中，
被设置为第二状态(setup)的所述第一配置信息(rlf-TimersAndConstants)中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
16.如附记15所述的配置参数的方法，其中，
所述与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310的值以及常量N311的值。
17.如附记14所述的配置参数的方法，其中，
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，
携带同步重配置(reconfiguration with sync)信息的所述无线资源控制(RRC)重配消息总是包括所述第一配置信息(rlf-TimersAndConstants)，且所述第一配置信息(rlf-TimersAndConstants)总是被设置为第二状态(setup)。
18.一种配置参数的方法，应用于终端设备，所述方法包括：
在所述终端设备被配置了双激活协议栈(DAPS)承载的情况下，
当所述终端设备未被配置与无线链路失败有关的第一配置信息(rlf-TimersAndConstants)或者收到的所述第一配置信息(rlf-TimersAndConstants)被设置为第一状态(release)时，
所述终端设备为目标小区组使用与源小区组相同的与无线链路失败有关的信息。
19.如附记18所述的配置参数的方法，其中，
与无线链路失败有关的所述第一配置信息(rlf-TimersAndConstants)对应同步重配置(reconfiguration with sync)的目标小区组。
20.如附记18所述的配置参数的方法，其中，所述使用与源小区组相同的与无线链路失败有关的信息，包括：
使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息；或者
使用源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)。
21.如附记18所述的配置参数的方法，其中，
使用与源小区组相同的与无线链路失败有关的信息，包括：
当所述终端设备未被配置源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)或者收到的所述第三配置信息(rlf-TimersAndConstants)被设置为第三状态(release)时，使用源小区的系统信息块(SIB)1里的与无线链路失败有关的信息；或者
当所述终端设备被配置了源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)且收到的所述第三配置信息(rlf-TimersAndConstants)被设置为第四状态(setup)时，使用源小区组的与无线链路失败有关的第三配置信息(rlf-TimersAndConstants)。
22.如附记18、19、20或21所述的配置参数的方法，其中，
与无线链路失败有关的信息包括：
定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。

Claims (19)

  1. 一种配置参数的装置，应用于终端设备，所述装置包括第一应用单元：
    在所述终端设备被配置了双激活协议栈承载的情况下，
    当所述终端设备未被配置小区组的与无线链路失败有关的第一配置信息或者收到的所述第一配置信息被设置为第一状态时，
    所述第一应用单元为同步重配置的目标小区组使用源小区或者目标小区的系统信息块1里的与无线链路失败有关的信息。
  2. 如权利要求1所述的配置参数的装置，其中，
    所述系统信息块1里的与无线链路失败有关的信息包括：
    系统信息块1中包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
  3. 如权利要求1或2所述的配置参数的装置，其中，
    所述系统信息块1里的与无线链路失败有关的信息，包括：
    系统信息块1中收到的第二配置信息包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
  4. 如权利要求1所述的配置参数的装置，其中，所述装置还包括第一获取单元：
    所述第一获取单元通过系统信息块1获取过程获得所述系统信息块1；或者
    所述第一获取单元接收无线资源控制重配消息，所述无线资源控制重配消息具有所述系统信息块1。
  5. 如权利要求1所述的配置参数的装置，其中，所述装置还包括第二获取单元：
    所述终端设备收到携带同步重配置信息的无线资源控制重配消息时，所述第二获取单元通过系统信息获取过程获得所述目标小区的系统信息块1。
  6. 如权利要求1所述的配置参数的装置，其中，所述装置还包括第三获取单元：
    所述第三获取单元接收网络设备发送的专用系统信息块1传送信息，所述专用系统信息块1传送信息具有所述目标小区的系统信息块1里的与无线链路失败有关的信息。
  7. 一种配置参数的装置，应用于网络设备，所述装置包括第一配置单元或第二配置单元：
    所述第一配置单元向终端设备发送携带同步重配置信息的无线资源控制重配消 息，
    在为所述终端设备配置了双激活协议栈承载的情况下，当没有为所述终端设备配置小区组的与无线链路失败有关的第一配置信息或者发送给所述终端设备的所述第一配置信息被设置为第一状态时，所述无线资源控制重配消息包括专用系统信息块1传送信息，所述专用系统信息块1传送信息具有目标小区的系统信息块1里的与无线链路失败有关的信息；
    所述第二配置单元向终端设备发送携带同步重配置信息的无线资源控制重配消息，其中，在为所述终端设备配置了双激活协议栈承载的情况下，所述第二配置单元为所述终端设备配置与无线链路失败有关的第一配置信息，且所述第一配置信息被设置为第二状态。
  8. 如权利要求7所述的配置参数的装置，其中，
    所述系统信息块1里的与无线链路失败有关的信息包括：
    所述系统信息块1中包括的定时器T301，定时器T310，定时器T311，常量N310的值以及常量N311的值。
  9. 如权利要求7所述的配置参数的装置，其中，
    其中，所述系统信息块1里的与无线链路失败有关的信息，包括：
    系统信息块1中收到的第二配置信息包括的定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
  10. 如权利要求7所述的配置参数的装置，其中，
    在为所述终端设备配置了双激活协议栈承载的情况下，
    所述第二配置单元总是为所述终端设备配置所述第一配置信息，且所述第一配置信息总是被设置为第二状态。
  11. 如权利要求7所述的配置参数的装置，其中，
    在所述第二配置单元为所述终端设备配置的所述第一配置信息中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
  12. 如权利要求11所述的配置参数的装置，其中，
    所述与无线链路失败有关的信息包括：
    定时器T301，定时器T310，定时器T311，常量N310以及常量N311的值。
  13. 一种配置参数的装置，应用于终端设备，所述装置包括第二应用单元或第三 应用单元：
    所述第二应用单元从网络设备接收携带同步重配置信息的无线资源控制重配消息，其中，在所述终端设备被配置了双激活协议栈承载的情况下，所述第二应用单元从所述网络设备接收与无线链路失败有关的第一配置信息，其中，所述第一配置信息被设置为第二状态；
    在所述终端设备被配置了双激活协议栈承载的情况下，当所述终端设备未被配置与无线链路失败有关的第一配置信息或者收到的所述第一配置信息被设置为第一状态时，所述第三应用单元为目标小区组使用与源小区组相同的与无线链路失败有关的信息。
  14. 如权利要求13所述的配置参数的装置，其中，
    被设置为第二状态的所述第一配置信息中包含有所述终端设备为目标小区组使用的与无线链路失败有关的信息。
  15. 如权利要求14所述的配置参数的装置，其中，
    所述与无线链路失败有关的信息包括：
    定时器T301，定时器T310，定时器T311，常量N310的值以及常量N311的值。
  16. 如权利要求13所述的配置参数的装置，其中，
    在所述终端设备被配置了双激活协议栈承载的情况下，
    携带同步重配置信息的所述无线资源控制重配消息总是包括所述第一配置信息，且所述第一配置信息总是被设置为第二状态。
  17. 如权利要求13所述的配置参数的装置，其中，
    在所述终端设备未被配置与无线链路失败有关的第一配置信息或者收到的所述第一配置信息被设置为第一状态的情况下，所述与无线链路失败有关的所述第一配置信息对应同步重配置的目标小区组。
  18. 如权利要求13所述的配置参数的装置，其中，所述使用与源小区组相同的与无线链路失败有关的信息，包括：
    使用源小区的系统信息块1里的与无线链路失败有关的信息；或者
    使用源小区组的与无线链路失败有关的第三配置信息。
  19. 如权利要求13所述的配置参数的装置，其中，
    使用与源小区组相同的与无线链路失败有关的信息，包括：
    当所述终端设备未被配置源小区组的与无线链路失败有关的第三配置信息或者收到的所述第三配置信息被设置为第三状态时，使用源小区的系统信息块1里的与无线链路失败有关的信息；或者
    当所述终端设备被配置了源小区组的与无线链路失败有关的第三配置信息且收到的所述第三配置信息被设置为第四状态时，使用源小区组的与无线链路失败有关的第三配置信息。
PCT/CN2022/110714 2022-08-05 2022-08-05 配置参数的方法、装置以及通信系统 WO2024026894A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110714 WO2024026894A1 (zh) 2022-08-05 2022-08-05 配置参数的方法、装置以及通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110714 WO2024026894A1 (zh) 2022-08-05 2022-08-05 配置参数的方法、装置以及通信系统

Publications (1)

Publication Number Publication Date
WO2024026894A1 true WO2024026894A1 (zh) 2024-02-08

Family

ID=89848428

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110714 WO2024026894A1 (zh) 2022-08-05 2022-08-05 配置参数的方法、装置以及通信系统

Country Status (1)

Country Link
WO (1) WO2024026894A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113677040A (zh) * 2020-05-13 2021-11-19 夏普株式会社 无线链路失败恢复方法及对应的用户设备
CN114557114A (zh) * 2019-11-13 2022-05-27 夏普株式会社 终端装置、基站装置以及方法
WO2022149898A1 (ko) * 2021-01-08 2022-07-14 삼성전자 주식회사 차세대 이동 통신 시스템에서 daps 핸드오버를 수행할 때 발생할 수 있는 오류를 방지하는 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114557114A (zh) * 2019-11-13 2022-05-27 夏普株式会社 终端装置、基站装置以及方法
CN113677040A (zh) * 2020-05-13 2021-11-19 夏普株式会社 无线链路失败恢复方法及对应的用户设备
WO2022149898A1 (ko) * 2021-01-08 2022-07-14 삼성전자 주식회사 차세대 이동 통신 시스템에서 daps 핸드오버를 수행할 때 발생할 수 있는 오류를 방지하는 방법 및 장치

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Correction to the configuration of rlf-TimersAndConstants [H372]", 3GPP DRAFT; R2-1812336, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Gothenburg, Sweden; 20180820 - 20180824, 10 August 2018 (2018-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051521943 *
INTEL CORPORATION: "RRC running CR for NR mobility on DAPS HO ( [107bis#54])", 3GPP DRAFT; R2-1914833, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051816777 *

Similar Documents

Publication Publication Date Title
JP7433488B2 (ja) 無線アクセスネットワーク通知エリア（ｒｎａ）更新の拒否時の構成を処理するための方法および装置
JP6587001B2 (ja) 無線端末及びその方法
KR102094893B1 (ko) 데이터 수신 방법 및 사용자기기와, 데이터 전송 방법 및 기지국
CN108476535B (zh) 无线终端、无线站、方法及其介质
US10986576B2 (en) Method and apparatus for transmitting and receiving data in wireless communication system
WO2020167205A1 (en) Early measurement reporting with rrc resume request message and indication of request for early measurements in association with paging
WO2013091161A1 (en) A method and apparatus for mobility robustness optimization
US20220279617A1 (en) Sidelink rlf handling
WO2020118519A1 (zh) 无线通信方法、终端设备和网络设备
EP4018714A1 (en) Recovery over sidelink
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2022082518A1 (zh) 信号的接收和发送方法、装置和通信系统
JP2024113129A (ja) 端末装置、通信のための方法、基地局及び基地局の方法
JP2021510950A (ja) 媒体アクセス制御層の制御要素の確認方法、装置及び通信システム
WO2024026894A1 (zh) 配置参数的方法、装置以及通信系统
WO2017166291A1 (zh) 一种通信方法、终端、基站和移动性管理设备
CN116347651A (zh) 无线通信方法、终端设备和网络设备
WO2024031402A1 (zh) 测量放松的方法、装置以及通信系统
US20240259907A1 (en) Method and apparatus for triggering generation of backhaul radio link failure notification
WO2023130348A1 (zh) 中继选择或重选方法、装置和系统
WO2023122889A1 (zh) 一种通信处理方法及装置、终端设备、接入网设备
WO2023130362A1 (zh) 收发信息的方法、装置和通信系统
WO2024031404A1 (zh) 测量放松的方法、装置以及通信系统
WO2024207195A1 (zh) 多路径的通信方法以及装置
WO2024207234A1 (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: 22953694

Country of ref document: EP

Kind code of ref document: A1