WO2024031272A1 - Procédés, appareils, dispositif de signalement et support de stockage - Google Patents

Procédés, appareils, dispositif de signalement et support de stockage Download PDF

Info

Publication number
WO2024031272A1
WO2024031272A1 PCT/CN2022/110948 CN2022110948W WO2024031272A1 WO 2024031272 A1 WO2024031272 A1 WO 2024031272A1 CN 2022110948 W CN2022110948 W CN 2022110948W WO 2024031272 A1 WO2024031272 A1 WO 2024031272A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal device
mcg
mcg link
connection reestablishment
Prior art date
Application number
PCT/CN2022/110948
Other languages
English (en)
Chinese (zh)
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 CN202280002779.3A priority Critical patent/CN115516916A/zh
Priority to PCT/CN2022/110948 priority patent/WO2024031272A1/fr
Publication of WO2024031272A1 publication Critical patent/WO2024031272A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to reporting methods, devices, equipment and storage media.
  • the Multi-Radio Dual Connectivity (MR-DC) technology is introduced to allow terminal equipment to access two cell groups at the same time (that is, access the Master Cell Group (Master Cell Group) through the main base station). , MCG), access the secondary cell group (Secondary Cell Group, SCG)) through the secondary base station to improve the data throughput rate and the mobility performance of the UE.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • MCG wireless link failure Radio Link Failure, RLF
  • RLF Radio Link Failure
  • MCG RLF Radio Link Failure
  • the fast MCG link recovery mechanism is: sending MCGFailureInformation (MCG failure information) message to the main base station through SCG, so that the terminal device can be quickly switched to a new primary cell (Primary Cell, PCell) to restore the MCG link.
  • MCG failure information MCG failure information
  • PCell Primary Cell
  • the terminal device needs to trigger the connection reestablishment process to restore the MCG link every time an MCG RLF occurs, which results in a long time and low efficiency.
  • the reporting method, device, equipment and storage medium proposed in this disclosure are to solve the technical problems in the related art that the MCG link recovery method is time-consuming and low in efficiency.
  • embodiments of the present disclosure provide a reporting method, which is executed by a terminal device and includes:
  • a reporting method In response to an MCG RLF occurring in a terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • embodiments of the present disclosure provide a reporting method, which is executed by a network device and includes:
  • Receive information reported by the terminal device which is information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • an embodiment of the present disclosure provides a communication device, which is configured in a terminal device and includes:
  • a processing module configured to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure MCG RLF;
  • the transceiver module is configured to report the recorded information to the network device.
  • an embodiment of the present disclosure provides a communication device, which is configured in a network device and includes:
  • the transceiver module is configured to receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication system, which includes the communication device described in the third aspect to the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect to The communication device according to the sixth aspect, or the system includes the communication device according to the seventh aspect to the communication device according to the eighth aspect, or the system includes the communication device according to the ninth aspect to the tenth aspect. the above-mentioned communication device.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned network device and/or the above-mentioned terminal device.
  • the network device is caused to execute the above-mentioned The method described in the first aspect, and/or causing the terminal device to perform the method described in the second aspect.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in any one of the above first to second aspects.
  • the present disclosure provides a chip system.
  • the chip system includes at least one processor and an interface, and is used to support a network device to implement the functions involved in the method described in the first aspect, and/or to support a terminal device.
  • Implement the functions involved in the method described in the second aspect for example, determine or process at least one of the data and information involved in the above method.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data of the source secondary node.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in any one of the above first to second aspects.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flowchart of a reporting method provided by another embodiment of the present disclosure.
  • Figure 3 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 4 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 5 is a schematic flowchart of a reporting method provided by another embodiment of the present disclosure.
  • Figure 6 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 7 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 8 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 9 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 10 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 11 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 12 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 13 is a schematic flow chart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 14 is a schematic flowchart of a reporting method provided by yet another embodiment of the present disclosure.
  • Figure 15 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 16 is a schematic structural diagram of a communication device provided by another embodiment of the present disclosure.
  • Figure 17 is a block diagram of a communication device provided by an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • the words "if” and “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • the terminal equipment establishes "Dual Connectivity" with the master base station (Master Node, MN) and the secondary base station (Secondary Node, SN), and uses the master cell group (Master Cell Group, MCG) and the secondary cell group (Secondary Cell Group) at the same time , SCG) resources. Among them, there is a control connection between the main base station and the core network.
  • the mobile station either initiates call reestablishment or forcibly disconnects the link. Since forcibly disconnecting the link actually introduces a call drop process, it must be ensured that the mobile station considers the wireless link failure only when the communication quality is truly unacceptable.
  • PCell Primary Cell
  • PCell The cell used to initiate initial access under MCG.
  • PSCell Primary Secondary Cell
  • FIG. 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to one network device and one terminal device.
  • the number and form of devices shown in Figure 1 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included. Network equipment, two or more terminal devices.
  • the communication system shown in Figure 1 includes a network device 11 and a terminal device 12 as an example.
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the network device 11 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the network device 11 may be an evolved base station (evolved NodeB, eNB), a transmission reception point (TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other base stations in future mobile communication systems. Base stations or access nodes in wireless fidelity (WiFi) systems, etc.
  • the embodiments of the present disclosure do not limit the specific technologies and specific equipment forms used by network equipment.
  • the network equipment provided by the embodiments of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU).
  • the CU may also be called a control unit (control unit).
  • CU-DU is used.
  • the structure can separate the protocol layers of network equipment, such as base stations, and place some protocol layer functions under centralized control on the CU. The remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the
  • the terminal device 12 in the embodiment of the present disclosure may be an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • FIG. 2 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 2a, the reporting method may include the following steps:
  • Step 201 In response to the occurrence of MCG RLF, record information related to the MCG link failure.
  • recording information related to MCG link failure may specifically include: recording first information, and the first information may include at least one of the following:
  • Step 202 Report the recorded information to the network device.
  • the terminal device reports its recorded information (ie, the above-mentioned first information) to the network device based on the request of the network device.
  • the "information related to MCG link failure" in the above step 201 can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reconstruction process needs to be triggered to restore the MCG link.
  • the T316 timer when the T316 timer is not configured, the T316 timer times out, SCG transmission is suspended, SCG is in an inactive state, PSCell addition is currently in progress, or PSCell change is currently in progress, it means that the fast MCG link cannot be restored at present. mechanism to quickly restore the MCG link, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the above-mentioned "triggering the connection reestablishment process” generally takes a long time, which will lead to low recovery efficiency of the MCG link.
  • the terminal device will record the information related to the MCG link failure and report it to the network device, so that when the terminal device currently occurs
  • the network device side can determine based on the information related to the MCG link failure reported by the terminal.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 3 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 3, the reporting method may include the following steps:
  • Step 301 In response to the occurrence of MCG RLF, trigger the connection reestablishment process and record information related to MCG link failure.
  • the difference between the embodiment corresponding to Figure 3 and the embodiment corresponding to Figure 2 is that in Figure 2, after MCG RLF occurs in the terminal device, information related to MCG link failure is recorded.
  • the embodiment of Figure 3 is: when an MCG RLF occurs on the terminal device and it is determined to trigger the connection reestablishment process, the terminal device only records information related to the MCG link failure.
  • Step 302 Report the recorded information to the network device.
  • the terminal device reports the recorded information related to the MCG link failure to the network device, and the network device can infer based on the content of the information related to the MCG link failure.
  • the reason why the terminal device needs to restore the MCG link by triggering the connection reestablishment process after MCG RLF occurs that is, the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after MCG RLF occurs), so that the subsequent MCG link can be restored based on this reason
  • the information related to MCG link failure reported by the terminal device to the network device is:
  • T316 timer is not configured
  • the network device can infer that the reason why the terminal device needs to trigger the connection reestablishment process to restore the MCG link after MCG RLF occurs is that the T316 timer is not configured and the SCG is currently in an inactive state.
  • the network device can make corresponding optimization adjustments to the terminal device.
  • the optimization adjustments can include, for example, configuring the T316 timer to the terminal device, and/or controlling the SCG to be in an active state.
  • the fast MCG link recovery mechanism can be directly used to restore the MCG link, which is shorter in time and more efficient.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 4 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 4, the reporting method may include the following steps:
  • Step 401 Record second information, which is the actual triggering reason of the current connection reestablishment process.
  • the second information essentially represents: the actual reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link.
  • the second information may include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the terminal device may record all the actual triggering reasons as the second information.
  • the terminal device may select reasons less than or equal to N from the actual triggering reasons to record as the second information, where N is a positive integer.
  • N may be agreed by the terminal device based on the protocol, and/or may also be determined by the terminal device based on instructions from the network device, and the number of actual triggering reasons specifically selected by the terminal device should be less than or equal to the current connection. The total number of actual triggering reasons for the reconstruction process.
  • the above-mentioned terminal device selects less than or equal to N reasons to record as the second information. Specifically, it can be understood as: when the total number of actual triggering reasons of the current connection reestablishment process When the number is less than N, then less than N reasons can be selected from the actual triggering reasons of the current connection reestablishment process and recorded as the second information.
  • the terminal device cannot select 4 reasons as the second information from the actual triggering reasons of the current connection reestablishment process.
  • the terminal device can select less than 4 reasons as the second information.
  • Second information for example, the terminal device can choose to use "T316 timer not configured” among the actual triggering reasons of the current connection reestablishment process as the second information, or the terminal device can choose to use the actual triggering reason of the current connection reestablishment process as the second information.
  • the two reasons "T316 timer is not configured and SCG is in an inactive state" are used as the second information.
  • the terminal device when the terminal device selects less than or equal to N reasons from the actual triggering reasons, the terminal device may arbitrarily select less than or equal to N reasons based on independent selection, and/or , or it may be that the terminal device preferentially selects reasons less than or equal to N with higher priority based on priority. Different reasons correspond to different priorities. The correspondence between the reasons and the priorities may be agreed upon by the protocol or indicated by the network device. For example, the priority order between various reasons can be: T316 timer timeout > SCG suspends transmission > PSCell is being added or changed > SCG is in an inactive state.
  • the terminal device when the actual triggering cause of the current connection reestablishment process includes the timeout of the T316 timer, the terminal device should also record the timing duration of the T316 timer as the second information.
  • Step 402 Report the second information to the network device.
  • the terminal device reports the second information to the network device, and the network device can determine based on the content of the second information that the terminal device needs to trigger the connection after MCG RLF occurs.
  • the reason for rebuilding the process to restore the MCG link that is, the reason why the fast MCG link recovery mechanism cannot be used to restore the MCG link after MCG RLF occurs), so that the terminal equipment can be optimized and adjusted accordingly based on this reason to prevent subsequent "due to The same reason leads to the situation where the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link.
  • the second information reported by the terminal device to the network device is:
  • the T316 timer times out, and the duration of the T316 timer is 40 milliseconds (ms).
  • the network device can infer based on the second information reported by the terminal device that the reason why the terminal device needs to trigger the connection reestablishment process to restore the MCG link after the MCG RLF occurs is: the T316 timer expires due to the short timing length. The server times out. At this time, the network device can make corresponding optimization adjustments to the terminal device.
  • the optimization adjustment can be as follows: configuring a new timing duration for the T316 timer. The new timing duration is greater than the original timing duration of the T316 timer, and the new timing duration is longer than the original timing duration of the T316 timer.
  • the timing length should be able to support the completion of the fast MCG link recovery mechanism to ensure that after subsequent MCG RLF occurs on the terminal device, the MCG link can be successfully restored based on the fast MCG link recovery mechanism.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG. 5 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 5, the reporting method may include the following steps:
  • Step 501 In response to the occurrence of MCG RLF, the connection reestablishment process is triggered, and the actual triggering reason of the current connection reestablishment process includes a specific reason, and third information is recorded.
  • the third information includes the specific reason corresponding to the current connection reestablishment process.
  • the specific reason may be determined by the terminal device based on the protocol agreement, and/or it may also be determined by the terminal device based on instructions from the network device.
  • the specific reason may specifically be any one or more of all possible reasons that cause the MCG link to be restored by triggering the connection reestablishment process after the MCG RLF occurs.
  • the specific reason may include at least one of: T316 timer timeout, SCG transmission pause, PSCell addition in progress, and PSCell change in progress.
  • the specific reasons include T316 timer timeout, SCG transmission pause, PSCell addition in progress, PSCell change in progress; and, the actual triggering reasons of the current connection reestablishment process are: T316 timer not configured, SCG transmission pause. At this time, only "SCG transmission pause" is recorded as the third information.
  • the terminal device may use all the specific reasons corresponding to the current connection reestablishment process as third information. In another embodiment of the present disclosure, the terminal device may select less than or equal to N reasons from the specific reasons corresponding to the current connection reestablishment process to record as the third information, where N is a positive integer.
  • the above-mentioned N may be agreed upon by the terminal device based on the protocol, and/or may also be determined by the terminal device based on instructions from the network device. For specific details related to this part of the content, please refer to the above embodiment description.
  • the terminal device when the specific reason corresponding to the current connection reestablishment process includes the T316 timer timeout, the terminal device should also record the timing length of the T316 timer as the third information.
  • Step 502 Report the third information to the network device.
  • step 502 please refer to the description of the above embodiment.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 6 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 6, the reporting method may include the following steps:
  • Step 601 In response to the occurrence of MCG RLF, the connection reestablishment process is triggered, and the actual triggering reason of the current connection reestablishment process does not include a specific reason, and no information is recorded.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 7 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 7, the reporting method may include the following steps:
  • Step 701 In response to the occurrence of MCG RLF, record information related to the MCG link failure.
  • Step 702 Record the information related to the MCG link failure into an RLF report (Report) (such as VarRLF-Report).
  • RLF report Report
  • Step 703 Report the RLF Report to the network device.
  • the terminal device restores the MCG link based on the connection reestablishment process, it will report the RLF Report to the network device based on the request of the network device.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 8 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 8, the reporting method may include the following steps:
  • Step 801 Send capability information to the network device, where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 9 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 9, the reporting method may include the following steps:
  • Step 901 Receive information reported by the terminal device.
  • the information is information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 10 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 10, the reporting method may include the following steps:
  • Step 1001 Receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded when the terminal device determines to trigger the connection reestablishment process to restore the MCG link after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • FIG 11 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 11, the reporting method may include the following steps:
  • Step 1101 Receive second information reported by the terminal device, where the second information is the actual triggering reason for the current connection reestablishment process.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 12 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 12, the reporting method may include the following steps:
  • Step 1201 Receive third information reported by the terminal device, where the third information includes a specific reason included in the actual triggering reason of the current connection reestablishment process.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 13 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 13, the reporting method may include the following steps:
  • Step 1301 Send a request message to the terminal device, where the request message is used to request the terminal device to report the information.
  • Step 1302 Receive the information reported by the terminal device through RLF Report.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 14 is a schematic flowchart of a reporting method provided by an embodiment of the present disclosure. The method is executed by a network device. As shown in Figure 14, the reporting method may include the following steps:
  • Step 1401 Receive capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • Figure 15 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in Figure 14, the device may include:
  • a processing module configured to record information related to the MCG link failure in response to the occurrence of a primary cell group radio link failure MCG RLF;
  • the transceiver module is configured to report the recorded information to the network device.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and will report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reestablishment process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • the processing module is also used to:
  • connection reestablishment process In response to determining that the connection reestablishment process is to be triggered to restore the MCG link, information related to the MCG link failure is recorded.
  • the processing module is also used to:
  • first information where the first information includes at least one of the following:
  • the processing module is also used to:
  • the actual triggering reasons include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the processing module is also used to:
  • the specific cause is at least partially the same as the actual triggering cause.
  • the device is also used for:
  • the device is also used for at least one of the following:
  • the specific cause is determined based on indications from the network device.
  • the processing module is also used to:
  • N is a positive integer, and the selected actual triggering The number of reasons is less than or equal to the total number of actual triggering reasons for the current connection reestablishment process;
  • the third information recorded includes:
  • the processing module is also used to:
  • the terminal device independently selects less than or equal to N reasons; and/or
  • the device is also used for:
  • the N is determined based on instructions from the network device.
  • the processing module is also used to:
  • the processing module is also used to:
  • the timing duration of the T316 timer is recorded as the third information.
  • the processing module is also used to:
  • the transceiver module is also used to:
  • the device is also used for:
  • Figure 16 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in Figure 16, the device may include:
  • the transceiver module is configured to receive information reported by the terminal device.
  • the information is the information related to the MCG link failure recorded by the terminal device after the MCG RLF occurs.
  • the terminal device in response to an MCG RLF occurring on the terminal device, the terminal device will record information related to the MCG link failure; and will report the recorded information to the network device.
  • the "information related to MCG link failure" can reflect whether the MCG link cannot be quickly restored based on the fast MCG link recovery mechanism, but the connection reconstruction process needs to be triggered to restore the MCG link.
  • the network The device side can determine "the reason why the fast MCG link recovery mechanism cannot be used to quickly restore the MCG link" based on the information related to MCG link failure reported by the terminal, and then make corresponding optimization adjustments to the terminal device to prevent subsequent If the situation "Due to the same reason, the terminal device cannot use the fast MCG link recovery mechanism to quickly restore the MCG link" occurs again; then when the terminal device encounters MCG RLF next time, there is no need to trigger the connection reestablishment process to restore the MCG. Instead, you can directly use the fast MCG link recovery mechanism to quickly restore the MCG link, so that the MCG link recovery takes less time and is more efficient.
  • the information is information related to MCG link failure recorded by the terminal device after MCG RLF occurs and when it is determined to trigger the connection reestablishment process to restore the MCG link. .
  • the transceiver module is also used to:
  • the transceiver module is also used to:
  • the actual triggering reasons include at least one of the following:
  • T316 timer is not configured
  • SCG is in an inactive state
  • the transceiver module is also used to:
  • the specific cause is at least partially the same as the actual triggering cause.
  • the device is also used for:
  • the device is also used for:
  • N is a positive integer
  • N is the maximum number of reasons that can be included in the second information or the third information.
  • the second information in response to the actual triggering reason of the current connection reestablishment process including T316 timer timeout, the second information also includes the timing duration of the T316 timer;
  • the third information In response to the specific reason corresponding to the current connection reestablishment process including T316 timer timeout, the third information also includes the timing duration of the T316 timer.
  • the transceiver module is also used to:
  • the device is also used for:
  • the device is also used for:
  • Receive capability information sent by the terminal device where the capability information is used to indicate whether the terminal device supports recording and reporting the information related to MCG link failure.
  • FIG 17 is a schematic structural diagram of a communication device 1700 provided by an embodiment of the present application.
  • the communication device 1700 may be a network device, a terminal device, a chip, a chip system, or a processor that supports a network device to implement the above method, or a chip, a chip system, or a processor that supports a terminal device to implement the above method. Processor etc.
  • the device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1700 may include one or more processors 1701.
  • the processor 1701 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device 1700 may also include one or more memories 1702, on which a computer program 1704 may be stored.
  • the processor 1701 executes the computer program 1704, so that the communication device 1700 performs the steps described in the above method embodiments. method.
  • the memory 1702 may also store data.
  • the communication device 1700 and the memory 1702 can be provided separately or integrated together.
  • the communication device 1700 may also include a transceiver 1705 and an antenna 1706.
  • the transceiver 1705 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1705 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1700 may also include one or more interface circuits 1707.
  • the interface circuit 1707 is used to receive code instructions and transmit them to the processor 1701 .
  • the processor 1701 executes the code instructions to cause the communication device 1700 to perform the method described in the above method embodiment.
  • the processor 1701 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1701 may store a computer program 1703, and the computer program 1703 runs on the processor 1701, causing the communication device 1700 to perform the method described in the above method embodiment.
  • the computer program 1703 may be solidified in the processor 1701, in which case the processor 1701 may be implemented by hardware.
  • the communication device 1700 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processor and transceiver described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited by FIG. 17 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • the communication device may be a chip or a chip system
  • the schematic structural diagram of the chip shown in FIG. 18 refer to the schematic structural diagram of the chip shown in FIG. 18 .
  • the chip shown in Figure 18 includes a processor 1801 and an interface 1802.
  • the number of processors 1801 may be one or more, and the number of interfaces 1802 may be multiple.
  • the chip also includes a memory 1803, which is used to store necessary computer programs and data.
  • This application also provides a readable storage medium on which instructions are stored. When the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • This application also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in this application can also be described as one or more, and the plurality can be two, three, four or more, which is not limited by this application.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • the corresponding relationships shown in each table in this application can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which are not limited by this application.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

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

Abstract

La présente divulgation concerne des procédés, des appareils, un dispositif de signalement et un support de stockage. Un procédé comprend : en réponse à l'apparition d'un défaut de liaison radio de groupe de cellules maîtresses (MCG RLF), l'enregistrement d'informations relatives au défaut de liaison MCG ; et le signalement, à un dispositif de réseau, des informations enregistrées. Dans le procédé divulgué dans la présente divulgation, la récupération de liaison MCG nécessite relativement peu de temps et présente une grande efficacité.
PCT/CN2022/110948 2022-08-08 2022-08-08 Procédés, appareils, dispositif de signalement et support de stockage WO2024031272A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002779.3A CN115516916A (zh) 2022-08-08 2022-08-08 一种上报方法、装置、设备及存储介质
PCT/CN2022/110948 WO2024031272A1 (fr) 2022-08-08 2022-08-08 Procédés, appareils, dispositif de signalement et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110948 WO2024031272A1 (fr) 2022-08-08 2022-08-08 Procédés, appareils, dispositif de signalement et support de stockage

Publications (1)

Publication Number Publication Date
WO2024031272A1 true WO2024031272A1 (fr) 2024-02-15

Family

ID=84513839

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110948 WO2024031272A1 (fr) 2022-08-08 2022-08-08 Procédés, appareils, dispositif de signalement et support de stockage

Country Status (2)

Country Link
CN (1) CN115516916A (fr)
WO (1) WO2024031272A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071597A (zh) * 2020-07-31 2022-02-18 大唐移动通信设备有限公司 一种信息处理方法、装置、设备及可读存储介质
WO2022075626A1 (fr) * 2020-10-08 2022-04-14 삼성전자 주식회사 Procédé et appareil de gestion de liaison dans une communication sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071597A (zh) * 2020-07-31 2022-02-18 大唐移动通信设备有限公司 一种信息处理方法、装置、设备及可读存储介质
WO2022075626A1 (fr) * 2020-10-08 2022-04-14 삼성전자 주식회사 Procédé et appareil de gestion de liaison dans une communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 36.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V16.6.0, 29 September 2021 (2021-09-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 1091, XP052056891 *

Also Published As

Publication number Publication date
CN115516916A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
WO2024065842A1 (fr) Procédé et appareil d'ajout de chemin
WO2023201756A1 (fr) Procédé et appareil de traitement d'informations pour mobilité conditionnelle
WO2024065127A1 (fr) Procédé de commande de transmission d'informations de dispositif relais et appareil associé
WO2023206034A1 (fr) Procédé de traitement pour rétroaction de demande de répétition automatique hybride (harq), et appareil associé
WO2023225830A1 (fr) Procédé et appareil de connexion de relais
WO2024031272A1 (fr) Procédés, appareils, dispositif de signalement et support de stockage
KR20240001256A (ko) 단말 활성화 상태 결정 방법 및 장치(method and apparatus for determining activation state of terminal)
WO2024060234A1 (fr) Procédé de rapport d'informations et appareil
WO2024060143A1 (fr) Procédé/appareil/dispositif de rapport et support de stockage
WO2024031274A1 (fr) Procédé et appareil d'enregistrement et de rapport pour rapport de transfert intercellulaire réussi (shr)
WO2024000207A1 (fr) Procédé et appareil de déclenchement de rapport d'avance temporelle (tar), dispositif et support de stockage
WO2023240419A1 (fr) Procédé et appareil de commande d'accès
WO2023201755A1 (fr) Procédé de configuration pour gestion de mobilité, et appareil
WO2024031275A1 (fr) Procédé et appareil d'enregistrement et de rapport pour rapport de transfert réussi (shr) dans une technologie d'accès radio (rat)
WO2024060154A1 (fr) Procédé, appareil et dispositif de rapport, et support de stockage
WO2024000208A1 (fr) Procédé de déclenchement de rapport d'avance temporelle (tar), appareil, dispositif, et support de stockage
WO2024031373A1 (fr) Procédé et appareil de détermination selon laquelle des défaillances de procédure lbt continues sont déclenchées
WO2024092661A1 (fr) Procédé et dispositif d'identification de modèle
WO2023193271A1 (fr) Procédé et appareil de mise à jour pour groupes de cellules d'un dispositif terminal en double connectivité
WO2024031721A1 (fr) Procédé de détection de signalisation de planification, et appareil
WO2024026800A1 (fr) Procédé/appareil/dispositif de récupération après défaillance de faisceau de liaison latérale sl, et support de stockage
WO2024026886A1 (fr) Procédé de rapport d'informations et appareil
WO2024045042A1 (fr) Procédé, appareil et dispositif de déclenchement d'interaction de capacité et support de stockage
US20240114483A1 (en) Paging processing method, communication apparatus, and storage medium
WO2024060233A1 (fr) Procédé de rapport d'informations et appareil

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: 22954252

Country of ref document: EP

Kind code of ref document: A1