Communication method, apparatus and system

Abstract

Provided in the present application are a communication method, apparatus and system. The method comprises: executing a first service by means of a first resource, wherein the first resource is a resource of a first cell, a first communication apparatus is under the coverage of the first cell, and the first communication apparatus establishes a radio resource control (RRC) connection with a first network device by means of the first cell; during the execution of the first service, determining that a failure occurs, wherein the failure comprises at least one of the following: a radio link failure (RLF), an RRC connection reconfiguration failure, an integrity check failure, or an RRC connection reestablishment failure; and initiating an RRC connection reestablishment process, and using the first resource to execute the first service. A first communication apparatus can still use a first resource after a failure occurs, and thus can execute a first service, thereby ensuring the transmission of the first service to a certain extent, and reducing the impact of the failure on the first service.

Description

A communication method, apparatus and system

[0001] This application claims priority to Chinese Patent Application No. 202510125003.6, filed on January 24, 2025, entitled "A Communication Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a communication method, apparatus, and system. Background Technology

[0003] With the development of communication technology, the 3rd generation partnership project (3GPP) defined the ambient internet of things (A-IoT or AIoT) technology.

[0004] AIoT devices can perform services with corresponding devices, which can be called readers. For example, network devices or terminals can act as readers. When a terminal acts as a reader, if the connection between the terminal and the network device is unstable, it will affect the transmission of AIoT services.

[0005] Therefore, ensuring the transmission of AIoT services is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method, apparatus, and system that can guarantee the transmission of AIoT services even when the connection is unstable.

[0007] Firstly, a communication method is provided, which can be executed by a first communication device. Unless otherwise specified, the "first communication device" in this application can refer to a first communication device (e.g., a terminal device), a component of the first communication device, or a logic module or software that can implement all or part of the functions of the first communication device. For ease of description, the following description uses the execution by the first communication device as an example.

[0008] The method includes: executing a first service through a first resource, wherein the first resource is a resource of a first cell, the first communication device is under the coverage of the first cell, and the first communication device establishes a radio resource control (RRC) connection with a first network device through the first cell; during the execution of the first service, a failure occurs, the failure including at least one of the following: radio link failure (RLF), RRC connection reconfiguration failure, integrity verification failure, or RRC connection reconstruction; initiating an RRC connection reconstruction process, and using the first resource to execute the first service.

[0009] Based on the above scheme, the first communication device can still use the first resource after a failure, thereby enabling it to execute the first service, which to a certain extent guarantees the transmission of the first service and reduces the impact of the failure on the first service.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the initiation of the RRC connection reconstruction process and the use of the first resource to execute the first service includes: when initiating the RRC connection reconstruction process, using the first resource to execute the first service; selecting a cell; if the selected cell is the first cell, continuing to use the first resource to execute the first service; if the selected cell is the second cell, releasing the first resource, wherein the second cell is different from the first cell.

[0011] Based on the above scheme, the first resource can be used when initiating the RRC connection reconstruction process. That is, if the first communication device experiences a link failure (i.e., a failure occurs) in the first cell, but then re-establishes a connection with the first network device in the first cell (meaning the first communication device's execution of the first service will not be affected by the failure), this continues until the first network device issues a new command, or until the first communication device fails to reconstruct, or until the first communication device selects another cell. If the first communication device does not select the first cell, the first resource can be used before selecting a cell. This avoids the inability to execute the first service after a failure, improving resource utilization flexibility while ensuring service transmission.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the initiation of the RRC connection reconstruction process and the execution of the first service using the first resource includes: selecting a cell; if the selected cell is the first cell, executing the first service using the first resource; if the selected cell is the second cell, releasing the first resource, wherein the second cell is different from the first cell.

[0013] Based on the above scheme, the first resource can be used when reselecting the first cell, so that the first communication device can execute the first service before re-establishing the connection through the first cell, reducing the impact of failure on the first service and improving the flexibility of resource use while ensuring service transmission.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the initiation of the RRC connection reconstruction process and the execution of the first service using the first resource includes: selecting a cell; if the selected cell is the first cell and the RRC connection reconstruction is completed through the first cell, executing the first service using the first resource; if the selected cell is the second cell, releasing the first resource, wherein the second cell is different from the first cell.

[0015] Based on the above scheme, the first resource can be used when re-establishing the connection through the first cell, avoiding the need for the first communication device to wait for the RRC reconfiguration instruction before configuring the corresponding resources to execute the first service after re-establishing the connection. This reduces the impact of failure on the first service and improves the flexibility of resource usage while ensuring service transmission.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving first information, the first information being used to instruct the first communication device to use the first resources to perform the first service when initiating the RRC connection reconstruction process; or, the first information being used to instruct the first communication device to use the first resources to perform the first service if the selected cell is the first cell during the RRC connection reconstruction process; or, the first information being used to instruct the first communication device to use the first resources to perform the first service if the selected cell is the first cell during the RRC connection reconstruction process and the RRC connection reconstruction is completed through the first cell.

[0017] Based on the above scheme, the first information can indicate different times for the use of the first resource, increasing the flexibility of resource allocation and indication. Alternatively, network devices can flexibly control the use of the first resource by the first communication device through the first information, improving the flexibility of resource use while ensuring the transmission of the first service.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first information is contained in a first message, wherein the first message is system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0019] Based on the above scheme, the first information can be included in multiple messages, improving the flexibility of indication. Furthermore, if the first information is included in a system message, the first network device can send the first information to all (or some) communication devices (including the first communication device) under its coverage; or, it can send the first information to all (or some) communication devices that have established a connection with it; or, it can send the first information to all (or some) UEs under the coverage of cell #1; or, it can send the first information to all (or some) communication devices that have established a connection with the first network device through the first cell. In this case, the first information is at the cell level, thus saving signaling overhead. If the first message is included in an RRC reconfiguration message, that is, the first network device can send information indicating its own resource configuration to each communication device (including the first communication device), then the first information is at the communication device level, thus carrying more information when sending the first information, increasing the flexibility of resource configuration.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the initiation of RRC connection reconstruction further includes: starting a first timer and performing cell selection during the operation of the first timer; the cell selection further includes: if a cell is selected, starting a second timer and sending an RRC request message through the selected cell during the operation of the second timer.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the execution of the first service through the first resource further includes: receiving third information, the third information indicating the first resource and a third timer, and executing the first service through the first resource during the operation of the third timer; the release of the first resource further includes: the third timer timing out or stopping the third timer.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the first business is an environmental Internet of Things (AIoT) business.

[0023] Secondly, a communication method is provided, which can be executed by a first communication device. Unless otherwise specified, the "first communication device" in this application can refer to a first communication device (e.g., a terminal device), a component of the first communication device, or a logic module or software that can implement all or part of the functions of the first communication device. For ease of description, the following description uses the execution by the first communication device as an example.

[0024] The method includes: performing a first service through a first resource, wherein the first resource is a resource of a first cell, the first communication device is under the coverage of the first cell, and the first communication device establishes a Radio Resource Control (RRC) connection with a first network device through the first cell; receiving a second message, wherein the second message is used to instruct the first communication device to switch from the first cell to a third cell; initiating an RRC connection reconstruction process, and performing the first service using a second resource, wherein the second resource is a resource of the third cell.

[0025] Based on the above scheme, the first communication device can still use the second resource after receiving the handover instruction, thereby enabling it to execute the first service. This ensures the transmission of the first service to a certain extent and reduces the impact of cell handover on the first service.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the initiation of the RRC connection reconstruction process and the use of the second resource to execute the first service includes: when initiating the RRC connection reconstruction process, using the second resource to execute the first service; selecting a cell; if the selected cell is the third cell, continuing to use the second resource to execute the first service; if the selected cell is the second cell, releasing the second resource, wherein the second cell is different from the third cell.

[0027] Based on the above scheme, the second resource can be used when initiating the RRC connection reconstruction process. That is, if the first communication device eventually establishes a connection through the target cell during cell handover or after a handover failure, the first communication device can use the second resource after initiating the RRC connection reconstruction until the network device issues a new command, or until the reconstruction fails. If the first communication device does not select a target cell, the second resource can also be used between initiating the connection reconstruction and selecting a cell. This avoids the inability to execute the first service during handover or RRC reconstruction, improving resource utilization flexibility while ensuring service transmission.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, the initiation of the RRC connection reconstruction process and the use of the second resource to execute the first service includes: selecting a cell; if the selected cell is the third cell, using the second resource to execute the first service; if the selected cell is the second cell, releasing the second resource, wherein the second cell is different from the third cell.

[0029] Based on the above scheme, the second resource can be used when selecting the target cell, so that the first communication device can execute the first service before establishing a connection through the target cell, reducing the impact of cell handover or RRC reconstruction on the first service, and improving the flexibility of resource use while ensuring service transmission.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the initiation of the RRC connection reconstruction process and the use of the second resource to execute the first service includes: selecting a cell; if the selected cell is the third cell and the RRC connection reconstruction is completed through the third cell, the second resource is used to execute the first service; if the selected cell is the second cell, the second resource is released, wherein the second cell is different from the third cell.

[0031] Based on the above scheme, the second resource can be used when establishing a connection through the target cell, avoiding the need for the first communication device to wait for the RRC reconfiguration instruction before configuring the corresponding resources to execute the first service after re-establishing the connection. This reduces the impact of cell handover or RRC reconstruction on the first service, and improves the flexibility of resource use while ensuring service transmission.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: upon receiving the second message, using the second resource to perform the first service.

[0033] Based on the above scheme, the second resource can be used upon receiving the handover information. That is, during cell handover, the first communication device can use the second resource after receiving the handover information until the network device issues a new command, until reconstruction fails, or until another cell is selected. If the first communication device has not selected a target cell, it can also use the second resource from the moment it receives the second message. This avoids the inability to execute the first service during handover, improving resource utilization flexibility while ensuring service transmission.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: receiving second information, the second information being used to instruct the first communication device to use the second resources to perform the first service when initiating the RRC connection reconstruction process; or, the second information being used to instruct the first communication device to use the second resources to perform the first service if the selected cell is the third cell during the RRC connection reconstruction process; or, the second information being used to instruct the first communication device to use the second resources to perform the first service if the selected cell is the third cell during the RRC connection reconstruction process and the RRC connection reconstruction is completed through the third cell; or, the second information being used to instruct the first communication device to use the second resources to perform the first service when receiving the second message.

[0035] Based on the above scheme, the second information can indicate different times for the use of the second resource, increasing the flexibility of resource allocation and indication. Alternatively, network devices can flexibly control the use of the second resource by the first communication device through the second information, improving the flexibility of resource use while ensuring the transmission of the first service.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the second information is contained in a third message, wherein the third message is system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0037] Based on the above scheme, the second information can be included in multiple messages, improving the flexibility of indication. Furthermore, if the second information is included in a system message, it is at the cell level, saving signaling overhead. If the second information is included in an RRC reconfiguration message, it is at the communication device level, allowing more information to be carried when sending the second information, increasing the flexibility of resource allocation.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, the initiation of RRC connection reconstruction further includes: starting a first timer and performing cell selection during the operation of the first timer; the cell selection further includes: if a cell is selected, starting a second timer and sending an RRC request message through the selected cell during the operation of the second timer.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the execution of the first service through the first resource further includes: receiving third information, the third information indicating the first resource and a third timer, and executing the first service through the second resource during the operation of the third timer; the release of the second resource further includes: the third timer timing out or stopping the third timer.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, the first business is an environmental Internet of Things (AIoT) business.

[0041] Thirdly, a communication method is provided, which can be executed by a first network device. Unless otherwise specified, the "first network device" in this application can refer to a first network device (e.g., a base station), a component within the first network device, or a logic module or software capable of implementing all or part of the functions of the first network device. For ease of description, the following description uses execution by a first network device as an example.

[0042] The method includes: sending first information, the first information indicating at least one of the following: when a first communication device initiates a Radio Resource Control (RRC) connection re-establishment process, it uses a first resource to perform a first service; or, during the RRC connection re-establishment process, if the selected cell is a first cell, the first communication device uses the first resource to perform the first service; or, during the RRC connection re-establishment process, if the selected cell is the first cell and the RRC connection re-establishment is completed through the first cell, the first communication device uses the first resource to perform the first service; wherein, the first resource is the resource of the first cell, and under the coverage of the first cell, the first communication device establishes an RRC connection with the first network device through the first cell.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the first information is contained in the first message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0044] It should be noted that the beneficial effects of the third aspect and its corresponding implementation can be referred to the relevant descriptions of the first aspect and its corresponding implementation, which will not be repeated here.

[0045] Fourthly, a communication method is provided, which can be executed by a first network device. Unless otherwise specified, the "first network device" in this application can refer to a first network device (e.g., a base station), a component within the first network device, or a logic module or software capable of implementing all or part of the functions of the first network device. For ease of description, the following description uses execution by a first network device as an example.

[0046] The method includes: sending a second message, the second message indicating at least one of the following: when a first communication device initiates an RRC connection re-establishment process, it uses a second resource to perform a first service; or, during the RRC connection re-establishment process, if the selected cell is a third cell, the first communication device uses the second resource to perform the first service; or, during the RRC connection re-establishment process, if the selected cell is the third cell and the RRC connection re-establishment is completed through the third cell, the first communication device uses the second resource to perform the first service; or, upon receiving a second message, the first communication device uses the second resource to perform the first service; wherein the first communication device establishes a Radio Resource Control (RRC) connection with the first network device.

[0047] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second information is contained in the third message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0048] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: sending the second message, the second message being used to instruct the first communication device to switch to the third cell.

[0049] It should be noted that the beneficial effects of the fourth aspect and its corresponding implementation can be referred to the relevant descriptions of the second aspect and its corresponding implementation, which will not be repeated here.

[0050] Fifthly, a communication apparatus is provided for performing the method provided in any one of the first to fourth aspects. Specifically, the communication apparatus may include units and / or modules for performing the method provided in any implementation of any one of the first to fourth aspects, such as a processing unit and a transceiver unit.

[0051] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0052] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0053] For example, if the communication device is the first communication device described above or a component of the first communication device (e.g., a chip or circuit), then the communication device includes:

[0054] The processing unit is configured to execute a first service using a first resource, wherein the first resource is a resource of a first cell, the first communication device is under the coverage of the first cell, and the first communication device establishes a radio resource control (RRC) connection with a first network device through the first cell; during the execution of the first service, if a failure occurs, the failure includes at least one of the following: radio link failure (RLF), RRC connection reconfiguration failure, integrity verification failure, or RRC connection reconstruction; initiate an RRC connection reconstruction process and use the first resource to execute the first service.

[0055] For example, if the communication device is the first communication device described above or a component of the first communication device (e.g., a chip or circuit), then the communication device includes:

[0056] The processing unit is configured to execute a first service using a first resource, wherein the first resource is a resource of a first cell, and the first communication device is under the coverage of the first cell, wherein the first communication device establishes a Radio Resource Control (RRC) connection with a first network device through the first cell; initiate an RRC connection reconstruction process; and execute the first service using a second resource, wherein the second resource is a resource of the third cell.

[0057] The transceiver unit is used to receive a second message, which instructs the first communication device to switch from the first cell to the third cell.

[0058] For example, if the communication device is the first network device or a component of the first network device (e.g., a chip or circuit), then the communication device includes:

[0059] A transceiver unit is configured to transmit first information, the first information indicating at least one of the following: when a first communication device initiates a Radio Resource Control (RRC) connection re-establishment process, it uses the first resource to perform a first service; or, during the RRC connection re-establishment process, if the selected cell is the first cell, the first communication device uses the first resource to perform the first service; or, during the RRC connection re-establishment process, if the selected cell is the first cell and the RRC connection re-establishment is completed through the first cell, the first communication device uses the first resource to perform the first service; wherein, the first resource is the resource of the first cell, and under the coverage of the first cell, the first communication device establishes an RRC connection with the first network device through the first cell.

[0060] For example, if the communication device is the aforementioned second network device or a component of the second network device (e.g., a chip or circuit), then the communication device includes:

[0061] A transceiver unit is configured to transmit second information, the second information indicating at least one of the following: the first communication device, during the initiation of an RRC connection reconstruction process, uses the second resource to perform a first service; or, during the initiation of an RRC connection reconstruction process, if the selected cell is a third cell, the first communication device uses the second resource to perform the first service; or, during the initiation of an RRC connection reconstruction process, if the selected cell is the third cell and the RRC connection reconstruction is completed through the third cell, the first communication device uses the second resource to perform the first service; or, upon receiving a second message, the first communication device uses the second resource to perform the first service; wherein the first communication device establishes a Radio Resource Control (RRC) connection with the first network device.

[0062] Sixthly, a processor is provided for executing the methods provided in the above aspects.

[0063] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0064] In a seventh aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including a method for performing any of the implementations of the first to fourth aspects described above.

[0065] Eighthly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing the method provided by any of the implementations of the first to fourth aspects.

[0066] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the implementations of the first to fourth aspects described above.

[0067] A ninth aspect provides a communication system comprising a first communication device for performing the method provided in the first aspect and a first network device for performing the method provided in the third aspect; or, comprising a first communication device for performing the method provided in the second aspect and a second network device for performing the method provided in the fourth aspect.

[0068] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any one of the implementations of the first to fourth aspects described above. Attached Figure Description

[0069] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0070] Figure 2 is a schematic diagram of an RLF process applicable to an embodiment of this application.

[0071] Figure 3 is a schematic diagram of a HO process applicable to an embodiment of this application.

[0072] Figure 4 is a schematic diagram of a communication method 400 applicable to an embodiment of this application.

[0073] Figure 5 is a schematic diagram of a communication method 500 applicable to an embodiment of this application.

[0074] Figure 6 is a schematic diagram of a communication method 600 applicable to an embodiment of this application.

[0075] Figure 7 is a schematic diagram of a communication method 700 applicable to an embodiment of this application.

[0076] Figure 8 is a schematic diagram of a communication method 800 applicable to an embodiment of this application.

[0077] Figure 9 is a schematic diagram of a communication method 900 applicable to an embodiment of this application.

[0078] Figure 10 is a schematic diagram of a communication method 1000 applicable to an embodiment of this application.

[0079] Figure 11 is a schematic diagram of a communication method 1100 applicable to an embodiment of this application.

[0080] Figure 12 is a schematic diagram of a communication method 1200 applicable to an embodiment of this application.

[0081] Figure 13 is a schematic diagram of the structure of a communication device 1300 provided in an embodiment of this application.

[0082] Figure 14 is a schematic diagram of the structure of a communication device 1400 provided in an embodiment of this application.

[0083] Figure 15 is a schematic diagram of the structure of a chip system 1500 provided in an embodiment of this application. Detailed Implementation

[0084] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0085] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) systems (or new radio (NR)), beyond 5G (B5G) mobile communication systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication networks. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, sidelink (SL) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0086] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses "device" as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the term "terminal device / network device" in this application can be replaced by a terminal device that performs the corresponding communication method described in this application with the network device.

[0087] The terminal devices in this application include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. These terminal devices can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, IoT terminal, AIoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initialization protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multi-helicopter, quad-helicopter, or airplane), boat, remote control device, smart home device, industrial equipment, or devices built into the above devices (e.g., communication modules, modems, or chips in the above devices), or other processing devices connected to a wireless modem. For ease of description, the terminal equipment will be described below using UE as an example.

[0088] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0089] The network device in this application embodiment can be a device for communicating with a terminal device. This network device may include an access network device or a radio access network device, such as a base station (BS). In this application embodiment, the access network device may refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), mobile switching center, next-generation NodeB (gNB), next-generation base station in future communication systems, access node in a WiFi system, relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, building base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0090] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0091] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, central unit-control planes (CU-CP), central unit-user planes (CU-UP), or RUs, etc. CUs and DUs can be configured separately or included in the same network element, such as a BBU. Radio units (RUs) can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0092] RAN nodes can support one or more types of fronthaul interfaces, each corresponding to a DU and RU with different functions. If the fronthaul interface between the DU and RU is a common public radio interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, some downlink and / or uplink baseband functions, such as, for downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix addition (CP), are moved from the DU to the RU; and for uplink, digital beamforming (BF), or one or more of fast Fourier transform (FFT) / cyclic prefix removal (CP), are moved from the DU to the RU.

[0093] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0094] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN / ORAN) architecture. In an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0095] In this embodiment, the device for implementing the function of the terminal device / network device can be the terminal device / network device itself, or it can be a device capable of supporting the terminal device / network device in implementing that function, such as a chip system or a chip. This device can be installed in the terminal device / network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete components.

[0096] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0097] Network equipment may also include core network equipment, such as access and mobility management function (AMF), or operations, administration and maintenance (OAM) equipment, or third-party equipment, such as over-the-top (OTT) equipment or cloud servers, or equipment equipped with AI modules, such as RAN intelligent controller (RIC).

[0098] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0099] As shown in Figure 1, the network architecture includes a wireless access network 100. The wireless access network 100 can be a future wireless access network or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 120) can be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) within the wireless access network 100. Figure 1 is only a schematic diagram; this wireless communication system may also include other devices, such as core network equipment, wireless relay equipment, and / or wireless backhaul equipment, which are not shown in Figure 1.

[0100] In practical applications, this wireless communication system can include multiple network devices and multiple terminal devices simultaneously, without limitation. A network device can serve one or more terminal devices simultaneously. A terminal device can also access one or more network devices simultaneously. The embodiments of this application do not limit the number of terminal devices and network devices included in the wireless communication system.

[0101] It should be noted that the terminal device shown in Figure 1 can act as a reader, working in conjunction with AIoT devices (as devices) to jointly execute AIoT services. Specific details about readers and devices will be explained below and will not be repeated here.

[0102] It should be understood that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0103] To facilitate understanding of the embodiments of this application, the terms involved in this application will be briefly explained first.

[0104] It should be understood that the basic concepts introduced below are illustrated using the basic concepts specified in the NR protocol as examples, but do not limit the embodiments of this application to be applied only to NR systems. Therefore, the standard names that appear when describing NR systems are functional descriptions, and the specific names are not limited, but only indicate the functions of the device, and can be extended to other future systems accordingly.

[0105] 1. Ambient IoT (A-IoT or AIoT)

[0106] In IoT scenarios, the number of devices that can be accommodated can be increased by reducing device size and complexity. IoT includes AIoT, which can be applied to various scenarios. For example, in logistics and warehousing, AIoT devices can be used for inventory and tracking of goods, as well as monitoring the status of goods during transportation. In industrial manufacturing, tags can be used to monitor the environment and equipment status. Furthermore, AIoT can be considered for other consumer-facing businesses, such as managing user assets. By locating tags through inventory processes or similar procedures, users can determine whether their items are lost and in what area, thus enabling AIoT-based item retrieval.

[0107] 2. Device and reader

[0108] For IoT scenarios, reducing device size and complexity can potentially increase the number of devices that can be accommodated in an IoT environment. These IoT devices can include AIoT devices. For example, the peak power consumption of AIoT devices ranges from 1μW to several hundred μW. Uplink transmission in AIoT devices can be generated internally, or the device can perform backscattering based on an externally provided carrier wave. In some implementations, an AIoT device with a peak power consumption of approximately 1μW (e.g., device1) lacks uplink or downlink amplification capabilities; an AIoT device with a peak power consumption of several hundred μW (e.g., device2) possesses both uplink and / or downlink amplification capabilities.

[0109] AIoT devices can perform services with corresponding devices. In this case, the AIoT device can be called a device, and the corresponding device can be called a reader. It should be noted that the device can also include user equipment (UE), tags, or AIoT tags, or other IoT devices, or it can be a unit among the above devices that can perform the corresponding functions; the reader can include network devices (e.g., base stations or interrogators) or UE, or it can be a unit among the above devices that can perform the corresponding functions. This application embodiment does not limit the devices that can be used as devices and readers. The UE that acts as a reader can be called an AIoT-enabled UE, a UE reader, an IoT-enabled UE, an intermediate node, an intermediate UE, etc., and is referred to as UE in this application embodiment.

[0110] In an AIoT scenario, the device and reader can perform at least one of the following operations: inventory operation, read operation, write operation, disable operation, kill or disable operation, or lock operation. In other words, the device and reader can perform at least one of the above AIoT services. For details regarding the specific content of AIoT services, please refer to relevant descriptions in the current technology; these will not be elaborated upon in this application. In addition, other operations can be performed between the tag and the reader, which will not be listed here.

[0111] It should be noted that in the embodiments of this application, "execute AIoT services" can also be understood as "execute AIoT services using air interface resources (such as AIoT air interface resources)," which will not be elaborated further below.

[0112] Furthermore, the names "device" and "reader" are not limited in this application embodiment. For example, "device" can also be called a tag or AIoT tag, etc. A tag can also be called an electronic tag or tag device, etc. For example, a tag implemented through an AIoT device can also be called an AIoT tag. In this application embodiment, the tag can function as a UE to communicate with network devices. Currently, tags are typically classified in the following two ways:

[0113] (1) Classification method 1: Tags can be divided into passive tags, semi-passive tags, and active tags. Passive tags and semi-passive tags can use reflection-based communication methods, while active tags use active carrier generation communication methods.

[0114] (2) Classification Method 2: The labels can be divided into device A, device B, and device C. Among them, device A has no energy storage and cannot generate signals independently, but uses backscatter to transmit signals; device B has energy storage but cannot generate signals independently, and uses backscatter to transmit signals, wherein the energy stored in device B can amplify the reflected signal; device C has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0115] It should be understood that the tags in the embodiments of this application can be classified according to classification method 1 or classification method 2, and the embodiments of this application are applicable to tags of any category under classification method 1 or classification method 2. Alternatively, the tags in the embodiments of this application may not be classified according to the above two classification methods, but rather according to the classification method for AIoT devices shown above, and the embodiments of this application are applicable to tags of any category under that classification method. Alternatively, the tags in the embodiments of this application may have other classification methods, or may not be classified at all. The embodiments of this application do not impose any limitations on these aspects.

[0116] In one possible implementation, the tag uses a low-precision, low-power mid-to-low frequency ring oscillator or a completely oscillator-less method to receive downlink signals. In this case, when the tag is operating, the energy and / or carrier for communication can be supplied by the reader or other devices, and communication is based on the reflected carrier. For example, the reader can send a carrier signal to the tag, the tag receives the carrier signal through an antenna, and the tag can adjust the information to be transmitted in the reflected signal. In this way, the power consumption of the tag's downlink reception can be further reduced. Optionally, the carrier can also be understood as an excitation signal, which can be sent by a device other than the reader. Thus, the reader can be replaced by other devices that can serve as an excitation source, such as a carrier wave node.

[0117] In one possible implementation, the tag is a miniature wireless transceiver device, mainly comprising a built-in tag antenna, coupling element, and chip. The tag's chip contains storage space capable of supporting the reader reading or writing tag data. After the tag receives the radio frequency signal transmitted by the reader through its antenna, it can couple the radio frequency signal through the coupling element. This coupler channel can then provide power to the tag's chip and transmit the data stored in the chip back to the reader via the antenna. For example, a cellular network-based infrastructure, including a communication network between the reader and the tag, can be referred to as a passive IoT network, or AIoT.

[0118] 3. Radio Link Failure (RLF)

[0119] RLF refers to the interruption of the connection between the UE and the network device due to various reasons during wireless communication.

[0120] For example, a UE may declare an RLF (or, in other words, the UE may cause an RLF, declare an RLF, or detect an RLF) when any of the following conditions are met:

[0121] (1) Timer started after physical layer reports wireless problem expires: If the physical layer detects a wireless problem and starts a timer (such as T310), and the physical layer problem is not resolved before the timer expires.

[0122] (2) Timer started when a measurement report is triggered expires: If a timer started when a measurement report is triggered expires, and another wireless problem timer is running at the same time.

[0123] (3) Random access procedure failure: The UE encounters a problem during the random access process (such as beam failure or recovery failure).

[0124] (4) RLC layer failure: The number of retransmissions in the RLC layer has reached the limit.

[0125] (5) Uplink Listen-Before-Talk (LBT) failure: For example, the uplink LBT continues to fail.

[0126] (6) Received a backhaul radio link failure (BH RLF) indication from the Integrated Access and Backhaul Mobile Terminal (IAB-MT).

[0127] Figure 2 illustrates the RLF process using the "Physical Layer Report Wireless Problems" declaration as an example.

[0128] Figure 2 is a schematic diagram of an RLF process applicable to an embodiment of this application.

[0129] Specifically, a UE in Radio Resource Control (RRC) connected state will perform Radio Link Monitoring (RLM) to monitor the downlink radio link quality. Being in RRC connected state can be understood as the UE establishing an RRC connection with a network device (e.g., a base station). Alternatively, it can be understood as the UE establishing an RRC connection with the network device through cell #1, where cell #1 covers the UE and is the network device's cell.

[0130] When a physical layer problem is detected, such as a physical layer problem in the primary cell, or when the RRC layer receives multiple (e.g., N310) consecutive out-of-synchronization indications from the physical layer (e.g., at time T0#1 in Figure 2), the UE can start Timer A (Timer A can be T310) and restore the radio link during the operation of Timer A.

[0131] If the physical layer problem is resolved during the execution of timer A, the UE can continue to remain in the RRC connected state;

[0132] If the physical layer problem is not resolved during the execution of Timer A, the UE can initiate a connection re-establishment process when Timer A times out (e.g., at time T1#1 in Figure 2). For example, the UE can declare an RLF when Timer A times out, and the UE can also initiate a connection re-establishment process, such as the UE starting Timer B (Timer B can be T311) at time T1#1, and performing cell selection or cell reselection during the execution of Timer B.

[0133] If the UE fails to select a suitable cell during the operation of timer B, the UE can enter the RRC idle state when timer B times out.

[0134] If the UE selects a suitable cell during the operation of Timer B (e.g., time T2#1 in Figure 2), the UE can also stop Timer B, start Timer C (Timer C can be T301), and send an RRC message (e.g., an RRC Re-establishment Request message). Furthermore, during the operation of Timer C, the UE can wait to receive the corresponding RRC response message (e.g., an RRC Re-establishment message or an RRC Setup message).

[0135] If the UE does not receive the corresponding RRC response message during the operation of timer C, the UE can enter the RRC idle state when timer C times out.

[0136] If the UE receives the corresponding RRC response message during the operation of timer C (for example, at time T3#1 in Figure 2), the UE can also stop timer C and remain in the RRC connected state.

[0137] 4. Toggle (handover, HO)

[0138] Mobility management of a UE in RRC connected state can be controlled by a network device (e.g., a network device that has established an RRC connection with the UE). For example, the source base station instructs the UE to hand over to a target cell and how to perform the handover by sending an RRC reconfiguration message containing a handover command. Specifically, upon receiving the RRC reconfiguration message containing the handover command, the UE can immediately release the source cell (or the original cell) and stop uplink / downlink data transmission with the source cell. Alternatively, the UE can access the target cell based on the content of the handover command. It should be noted that in various embodiments of this application, the original cell and the source cell can be substituted for each other.

[0139] Figure 3 is a schematic diagram of a HO process applicable to an embodiment of this application.

[0140] Specifically, when a UE in RRC connected state receives a handover command (e.g., an RRC reconfiguration message carrying reconfigurationWithSync (RRCReconfiguration message)) (e.g., at time T0#2 in Figure 3), the UE can perform a handover. For example, the UE can start timer D (timer D can be T304) at time T0#2 and perform a handover during the execution of timer D (e.g., handover to the target cell, or initiating random access in the target cell, etc.).

[0141] If the handover is successful (i.e., successful access to the target cell) during the operation of timer D, the UE can continue to remain in the RRC connected state;

[0142] If the handover is not successful during the operation of timer D, the UE can initiate a connection reconstruction process when timer D times out (for example, at time T1#2 in Figure 3). For example, the UE can start timer B (timer B can be T311) at time T1#2 and perform cell selection or cell reselection during the operation of timer B.

[0143] If the UE fails to select a suitable cell during the operation of timer B, the UE can enter the RRC idle state when timer B times out.

[0144] If the UE selects a suitable cell during the execution of Timer B (e.g., time T2#2 in Figure 3), the UE can also stop Timer B, start Timer C (Timer C can be T301), and send an RRC message (e.g., an RRC Re-establishment Request message). Furthermore, during the execution of Timer C, the UE can wait to receive the RRC response message corresponding to the RRC message (e.g., an RRC Re-establishment message or an RRC Setup message).

[0145] If the UE does not receive the corresponding RRC response message during the operation of timer C, the UE can enter the RRC idle state when timer C times out.

[0146] If the UE receives the corresponding RRC response message during the operation of timer C (for example, at time T3#2 in Figure 3), the UE can also stop timer C and remain in the RRC connected state.

[0147] Based on the above, when the UE is in RRC connected state, there may be situations where the RRC connection between the UE and the network device is unstable. This can be understood as the RRC connection established by the UE with the network device through cell #1 being unstable. Situations where the RRC connection is unstable may include at least one of the following: the UE detects an RLF (Redirect Line Request), the UE receives a handover command, the UE needs to perform a handover, RRC connection reconfiguration fails, integrity verification fails, or the RRC connection is rebuilt. It should be understood that other situations may occur between the UE and the network device that lead to RRC connection instability, which are not limited here. Therefore, in the case of an unstable RRC connection, the UE can still perform cell selection and establish a connection with the network device through the newly selected cell, thus not affecting normal communication.

[0148] In an AIoT scenario, taking the UE as a reader as an example, before the aforementioned RRC connection instability occurs, the UE can execute AIoT services while in an RRC connected state. For example, the UE establishes an RRC connection with network device #1 and executes AIoT services under the control of network device #1. It should be noted that the UE executing AIoT services under the control of network device #1 can be understood as follows: during the UE's execution of AIoT services, the AIoT air interface resources used are configured by network device #1 (for example, network device #1 configures resource #1 for the UE; resource #1 is a resource of cell #1, and resource #1 is an AIoT air interface resource, thus the UE can use resource #1 to execute AIoT services).

[0149] Optionally, resource #1 can be a resource configured by network device #1 for the UE to use when the UE is in RRC connected state.

[0150] It should be noted that when the terminal acts as a reader, unstable connections between the terminal and network devices can affect the transmission of AIoT services. For example, during the aforementioned RLF (Recurrent Link Failure) process, if the UE experiences an RLF, it needs to initiate an RRC (Recurrent Connection Re-establishment) process and select a suitable cell. If the UE was using resource #1 of cell #1 to perform AIoT services before the RLF occurred, the RLF will result in the UE having no usable AIoT resources (e.g., resource #1 of cell #1 may be invalid when the UE performs cell selection or cell reselection), thus affecting the AIoT services currently being performed by the UE.

[0151] For example, during the handover process described above, if the UE handover fails, the UE needs to initiate an RRC connection reconstruction process and select a suitable cell. If the UE was using resource #1 of cell #1 to perform AIoT services before the handover, the handover will result in the UE not having any usable AIoT resources (for example, resource #1 of cell #1 may be invalid when the UE performs cell selection or cell reselection), thus affecting the AIoT services currently being performed by the UE.

[0152] In view of this, embodiments of this application propose a communication method that can guarantee the transmission of AIoT services even when the connection is unstable.

[0153] Figure 4 is a schematic diagram of a communication method 400 applicable to an embodiment of this application.

[0154] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application may be a first communication device (e.g., a UE) and a first network device; or, it may be a functional module in the first communication device and the first network device that can call and execute a program.

[0155] The following, without loss of generality, details the communication method provided in the embodiments of this application using the interaction between a first communication device and a first network device as an example. It should be understood that FIG4 illustrates the steps or operations of the communication method, but these steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations of the various operations in FIG4.

[0156] Method 400 may include the following steps:

[0157] S401: The first communication device performs the first service through the first resource.

[0158] Wherein, the first resource is the resource of the first cell, and the first communication device is under the coverage of the first cell, and the first communication device establishes a Radio Resource Control (RRC) connection with the first network device through the first cell.

[0159] Optionally, the first resource is configured by the first network device for the first communication device. For details on the specific method by which the first network device configures the first resource, please refer to the relevant description in step S601 of method 600 below (e.g., configuration based on implementation 1 or implementation 2; or configuration based on other methods), which will not be elaborated upon here.

[0160] For example, when the first network device configures the first resource based on implementation method 1, the execution of the first service through the first resource further includes: receiving third information, wherein the third information indicates the first resource.

[0161] For example, when the first network device configures the first resource based on implementation method 2, the execution of the first service through the first resource further includes: receiving third information, the third information indicating the first resource and a third timer, and executing the first service through the first resource during the operation of the third timer.

[0162] Regarding the content of the third information, please refer to the relevant description of message #1 in methods 600-800 below. Regarding the content of the third timer, please refer to the relevant description of timer #2 in methods 600-800 below. The embodiments of this application will not be described in detail here.

[0163] Optionally, the first service is an environmental Internet of Things (AIoT) service.

[0164] Optionally, the first resource can be an air interface resource. In this embodiment of the application, "performing the first service through the first resource" can also be understood as "performing the first service using AIoT air interface resources".

[0165] S402: A failure condition occurs during the execution of the first service by the first communication device.

[0166] The failure scenarios include at least one of the following: wireless link failure (RLF), RRC connection reconfiguration failure, integrity verification failure, or RRC connection reconstruction. The first communication device performs the first service through the first resource.

[0167] It should be understood that for details regarding the failure scenarios, please refer to the relevant descriptions in the current technology, which will not be repeated here.

[0168] S403: The first communication device initiates an RRC connection reconstruction process and uses the first resource to execute the first service.

[0169] Optionally, initiating RRC connection reconstruction further includes: starting a first timer, and performing cell selection or cell reselection during the operation of the first timer. For example, the first timer is T311 in the current technology.

[0170] For example, if the execution timing of step S403 corresponds to the first moment, the first communication device can also start the first timer at the first moment, thereby initiating a connection reconstruction process during the operation of the first timer, such as performing cell selection or cell reselection. In other words, the moment of initiating the RRC reconstruction process can also be understood as the moment of starting the first timer, so "the first communication device initiates the RRC connection reconstruction process and uses the first resource to execute the first service" can also be understood as: the first communication device starts the first timer and uses the first resource to execute the first service during the operation of the first timer.

[0171] For example, if the execution timing of step S403 corresponds to the first moment, the first communication device can also start the first timer after the first moment. In other words, "the first communication device initiates the RRC connection reconstruction process and uses the first resource to execute the first service" can also include: the first communication device starts the first timer and uses the first resource to execute the first service during the operation of the first timer.

[0172] For details regarding the first timer, please refer to the description of timer #3 in methods 600-800 below, which will not be repeated here.

[0173] In one possible implementation (method A), step S403 is implemented based on steps S403a-S403b:

[0174] S403a: When initiating the RRC connection reconstruction process, the first communication device uses the first resource to execute the first service.

[0175] S403b: The first communication device selects a cell. If the selected cell is the first cell, the first communication device continues to use the first resource to perform the first service; if the selected cell is the second cell, the first communication device releases the first resource.

[0176] The second cell is different from the first cell. In this case, the first resource can be used when initiating the RRC connection reconstruction process. That is, if the link corresponding to the first cell fails (i.e., a failure occurs), and the first communication device re-establishes its connection with the first network device in the first cell (i.e., the first communication device's execution of the first service will not be affected by the failure), it can continue until the first network device issues a new command, or until the first communication device fails to reconstruct, or until the first communication device selects another cell. If the first communication device does not select the first cell, the first resource can also be used before selecting a cell. This avoids the inability to execute the first service after a failure, improving the flexibility of resource usage while ensuring service transmission.

[0177] It should be noted that for further details regarding steps S403a-S403b, please refer to the description of method 800 below (e.g., S802-S804), which will not be repeated here in the embodiments of this application.

[0178] In one possible implementation (method B), step S403 is implemented based on step S403c:

[0179] S403c: The first communication device selects a cell. If the selected cell is the first cell, the first resource is used to execute the first service; if the selected cell is the second cell, the first resource is released.

[0180] The second cell is different from the first cell.

[0181] It should be noted that from the initiation of RRC connection reconstruction to the selection of the first cell, the first resource is invalid. Invalid first resource can be understood as: the first communication device suspends the use of the first resource, but does not release it.

[0182] In this scenario, the first resource can be used when reselecting the first cell, allowing the first communication device to execute the first service before re-establishing the connection through the first cell. This reduces the impact of failures on the first service and improves the flexibility of resource utilization while ensuring service transmission.

[0183] It should be noted that for further details regarding step S403c, please refer to the description of method 700 below (e.g., S703-S704), which will not be repeated here in the embodiments of this application.

[0184] In one possible implementation (method C), step S403 is implemented based on step S403d:

[0185] S403d: The first communication device selects a cell. If the selected cell is the first cell and the RRC connection is re-established through the first cell, the first resource is used to execute the first service. If the selected cell is the second cell, the first resource is released.

[0186] The second cell is different from the first cell.

[0187] It should be noted that from the initiation of RRC connection reconstruction to the completion of RRC connection reconstruction through the first cell, the first resource is invalid.

[0188] In this scenario, the first resource can be used when re-establishing the connection through the first cell, avoiding the need for the first communication device to wait for an RRC reconfiguration instruction before configuring the corresponding resources to execute the first service after re-establishing the connection. This reduces the impact of failures on the first service and improves the flexibility of resource usage while ensuring service transmission.

[0189] It should be noted that for further details regarding step S403d, please refer to the description of method 600 below (e.g., S604), which will not be repeated here in the embodiments of this application.

[0190] For example, when the first network device configures the first resource based on implementation 2, the release of the first resource further includes: the third timer timeout or stopping the third timer.

[0191] Optionally, method 400 further includes step S404: the first network device sends first information to the first communication device; correspondingly, the first communication device receives the first information from the first network device.

[0192] In one possible implementation, the first information can be used by the network device to enable or control whether "the first communication device can use AIoT resources, for example, whether it can use the first resource." In other words, the first information can be understood as a switch for the network device to "use the first resource." Here, "whether the first communication device can use the first resource" can be understood as whether the first communication device can use the first resource when the connection is unstable; "whether it can use the first resource" can also be understood as whether it can use the first resource to perform the first service.

[0193] Optionally, if the first communication device receives the first information, it may use the first resource according to the instruction of the first information. The first information may indicate one or more of the following: the first communication device uses the first resource corresponding to the first cell (original cell); or, the first communication device successfully rebuilds in the original cell and uses the first resource corresponding to the original cell; or, the first communication device selects to rebuild in the original cell and uses the first resource corresponding to the original cell; or, the first communication device initiates RRC connection rebuilding and uses the first resource corresponding to the original cell.

[0194] Optionally, the above-mentioned use of the first resource can also be replaced by restoration of use of the first resource. That is, the first information may also indicate one or more of the following: the first communication device restores the use of the first resource corresponding to the first cell (original cell); or, the first communication device restores the use of the first resource corresponding to the original cell after successful reconstruction of the original cell; or, the first communication device selects to rebuild the original cell and restores the use of the first resource corresponding to the original cell; or, the first communication device initiates RRC connection reconstruction and restores the use of the first resource corresponding to the original cell. It is understood that in the various embodiments of this application, the use of the first resource and the restoration of use of the first resource can be substituted for each other.

[0195] Optionally, the network device may indicate the first information in one or more of the following ways: For example, if the network device configures or sends the first information, the first communication device can use the first resource; if the network device does not configure or send the first information, the first communication device cannot use the first resource. Another example: the first information occupies 1 bit; if the bit corresponding to the first information exists, the first communication device can use the first resource; if the bit corresponding to the first information does not exist, the first communication device cannot use the first resource. Yet another example: the first information occupies 1 bit; if the bit corresponding to the first information is 1 or 0, the first communication device can use the first resource; if the bit corresponding to the first information is 0 or 1, the first communication device cannot use the first resource.

[0196] It should be understood that the embodiments of this application do not limit the timing of the execution of "using the first resource according to the instruction of the first information".

[0197] For example, the first communication device may use the first resource after receiving the first information.

[0198] For example, depending on the different implementations of step S403, the first communication device may further determine whether to use the first resource based on the content of the first information. For instance, the first information may indicate the situation in which the first communication device can use the first resource (for example, the first communication device may first receive the first information, and then determine whether to use the first resource based on the content indicated by the first information and the actual situation). For example, it may indicate one or more of the following situations.

[0199] For example, corresponding to S403a-S403b, the first information is used to instruct the first communication device to use the first resource to perform the first service when initiating the RRC connection reconstruction process.

[0200] For example, corresponding to S403c, the first information is used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the first cell, to use the first resource to perform the first service.

[0201] For example, corresponding to S403d, the first information is used to instruct the first communication device, during the process of initiating RRC connection reconstruction, if the selected cell is the first cell and the RRC connection reconstruction is completed through the first cell, to use the first resources to execute the first service.

[0202] In this scenario, the first information can indicate the timing of different uses of the first resource, increasing the flexibility of resource allocation and indication. Alternatively, network devices can use the first information to flexibly control the use of the first resource by the first communication device, improving resource utilization flexibility while ensuring the transmission of the first service.

[0203] It should be noted that the present application embodiment does not limit the timing of the execution of step S404.

[0204] Optionally, the first information is included in the first message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0205] It should be noted that the method of carrying the first information can be referred to in the relevant description of information #1 in methods 600-800 below, and will not be repeated here.

[0206] Optionally, the cell selection process further includes: if a suitable cell is selected, starting a second timer, and sending an RRC request message through the selected cell during the operation of the second timer.

[0207] For example, if "cell selection" corresponds to the second time, the first communication device can also send a request message (e.g., an RRC reconstruction request) through the selected cell at the second time; and / or, the first communication device can also start a second timer at the second time, thereby waiting to receive a response message (a response message corresponding to the request message) sent by the network device during the operation of the second timer. In other words, the time of cell selection can also be understood as the time of starting the second timer.

[0208] For example, if "selecting a cell" corresponds to the second time, then the first communication device can also send a request message (e.g., an RRC reconstruction request) through the selected cell after the second time. In other words, the time of selecting a cell can also be understood as the time before the second timer is started.

[0209] It should be noted that the details of the second timer can be found in the description of timer #4 in methods 600-800 below, and will not be repeated here in the embodiments of this application.

[0210] Figure 5 is a schematic diagram of a communication method 500 applicable to an embodiment of this application.

[0211] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application may be a first communication device (e.g., a UE) and a first network device; or, it may be a functional module in the first communication device and the first network device that can call and execute a program.

[0212] Without loss of generality, the communication method provided in this application embodiment will be described in detail below using the interaction between a first communication device and a first network device as an example. It should be understood that FIG5 illustrates the steps or operations of the communication method, but these steps or operations are merely examples, and other operations or variations of the various operations in FIG5 can also be performed in the embodiments of this application.

[0213] Method 500 may include the following steps:

[0214] S501: The first communication device performs the first service through the first resource.

[0215] Wherein, the first resource is the resource of the first cell, and the first communication device, under the coverage of the first cell, establishes a Radio Resource Control (RRC) connection with the first network device through the first cell.

[0216] Optionally, the first resource is configured by the first network device for the first communication device. For details on the specific method by which the first network device configures the first resource, please refer to the relevant description in step S601 of method 600 below (e.g., configuration based on implementation 1 or implementation 2; or configuration based on other methods), which will not be elaborated upon here.

[0217] For example, when the first network device configures the first resource based on implementation method 1, the execution of the first service through the first resource further includes: receiving third information, wherein the third information indicates the first resource.

[0218] For example, when the first network device configures the first resource based on implementation method 2, the execution of the first service through the first resource further includes: receiving third information, the third information indicating the first resource and a third timer, and executing the first service through the first resource during the operation of the third timer.

[0219] Regarding the content of the third information, please refer to the relevant description of message #1 in methods 600-800 below. Regarding the content of the third timer, please refer to the relevant description of timer #2 in methods 600-800 below. The embodiments of this application will not be described in detail here.

[0220] Optionally, the first service is an AIoT service.

[0221] Optionally, the first resource can be an air interface resource. In this embodiment of the application, "performing the first service through the first resource" can also be understood as "performing the first service using AIoT air interface resources".

[0222] S502: The first network device sends a second message to the first communication device; correspondingly, the first communication device receives the second message from the first network device.

[0223] The second message is used to instruct the first communication device to switch from the first cell to the third cell. The third cell can also be called the target cell, and the third cell is the cell of the second network device.

[0224] Optionally, the second network device may be the same as or different from the first network device, without limitation.

[0225] Optionally, the second message includes a second resource, which is a resource of the third cell.

[0226] Optionally, the second resource is a resource used to perform the first business.

[0227] Optionally, the second resource is sent from the first network device to the first communication device. For example, the second resource can be determined or configured by the second network device. Regarding the specific method by which the second network device determines or configures the second resource, please refer to the relevant description in step S901 of method 900 below (e.g., configuration based on implementation 1 or implementation 2; or configuration based on other methods), which will not be elaborated upon here. The second network device can send the second resource to the first network device through the Xn port (the interface between the first network device and the second network device), and then the first network device will send the second resource to the first communication device.

[0228] Optionally, step S502 further includes: releasing the first resource.

[0229] For example, when the first network device configures the first resource based on implementation 2, releasing the first resource further includes: the first communication device considering that the third timer has timed out or stopping the third timer, the third timer corresponding to the first resource. It is understood that, since the first communication device receives the second message (for example, if the second message is an RRCReconfiguration message carrying reconfigurationWithSync), the first communication device can overwrite stored information based on the second message, such as overwriting the information configured in the previously received RRCReconfiguration message. That is, the configuration of the first resource is overwritten, or in other words, the first communication device releases the first resource. Furthermore, if the configuration of the first resource is overwritten, or the first resource is released, the first communication device considers that the third timer has timed out or stops the third timer.

[0230] Optionally, before step S502, method 500 may further include: the second network device sending the second message to the first network device.

[0231] S503: The first communication device initiates an RRC connection reconstruction process and uses the second resource to execute the first service.

[0232] Optionally, the second resource can be an air interface resource. In this embodiment, "performing the first service through the second resource" can also be understood as "performing the first service using AIoT air interface resources".

[0233] For example, when the second resource is configured based on implementation method 1, the execution of the first service through the second resource further includes: receiving third information, the third information indicating the second resource.

[0234] For example, when the second resource is configured based on implementation method 2, the execution of the first service through the second resource further includes: receiving third information, the third information indicating the second resource and a third timer, and executing the first service through the second resource during the operation of the third timer.

[0235] Optionally, the third information may be included in the second message, or in the switching command.

[0236] Regarding the content of the third information, please refer to the relevant description of message #1 in methods 900-1200 below. Regarding the content of the third timer, please refer to the relevant description of timer #2.1 in methods 900-1200 below. The embodiments of this application will not be repeated here.

[0237] Optionally, initiating RRC connection reconstruction further includes: starting a first timer, and performing cell selection or cell reselection during the operation of the first timer. For example, the first timer is T311 in the current technology.

[0238] For example, if the execution timing of step S503 corresponds to the first moment, the first communication device can also start the first timer at the first moment, thereby initiating a connection reconstruction process during the operation of the first timer, such as performing cell selection or cell reselection. In other words, the moment of initiating the RRC reconstruction process can also be understood as the moment of starting the first timer, so "the first communication device initiates the RRC connection reconstruction process and uses the second resource to execute the first service" can also be understood as: the first communication device starts the first timer and uses the second resource to execute the first service during the operation of the first timer.

[0239] For example, if the execution timing of step S503 corresponds to the first moment, the first communication device can also start the first timer after the first moment. In other words, "the first communication device initiates the RRC connection reconstruction process and uses the second resource to execute the first service" can also include: the first communication device starts the first timer and uses the second resource to execute the first service during the operation of the first timer.

[0240] For details regarding the first timer, please refer to the description of timer #3 in methods 900-1200 below, which will not be repeated here.

[0241] In one possible implementation (method D), step S503 is implemented based on steps S503a-S503b:

[0242] S503a: When initiating the RRC connection reconstruction process, the first communication device uses the second resource to execute the first service.

[0243] S503b: The first communication device selects a cell. If the selected cell is the third cell, the first communication device continues to use the second resource to perform the first service; if the selected cell is the second cell, the first communication device releases the second resource.

[0244] The second cell is different from the third cell.

[0245] It should be noted that the second resource is invalid before initiating the RRC connection re-establishment. The invalidation of the second resource can be understood as the first communication device suspending its use of the second resource, but not releasing it.

[0246] In this scenario, the second resource can be used when initiating the RRC connection re-establishment process. That is, if the first communication device eventually establishes a connection through the target cell during or after a cell handover, it can use the second resource after initiating the RRC connection re-establishment until a new command is issued by the network device, or until the re-establishment fails. If the first communication device does not select a target cell, the second resource can also be used between initiating the connection re-establishment and selecting a cell. This avoids the inability to execute the first service during the handover or RRC re-establishment process, improving resource utilization flexibility while ensuring service transmission.

[0247] It should be noted that for further details regarding steps S503a-S503b, please refer to the description of method 1100 below (e.g., S1102-S1104), which will not be repeated here in the embodiments of this application.

[0248] In one possible implementation (method E), step S503 is implemented based on step S503c:

[0249] S503c: The first communication device selects a cell. If the selected cell is the third cell, the second resource is used to execute the first service; if the selected cell is the second cell, the second resource is released.

[0250] The second cell is different from the third cell.

[0251] It should be noted that the second resource is invalid before the third cell is selected. The invalidation of the second resource can be understood as: the first communication device suspends the use of the second resource, but does not release it.

[0252] In this scenario, a second resource can be used when selecting a target cell, allowing the first communication device to execute the first service before establishing a connection through the target cell. This reduces the impact of cell handover or RRC reconstruction on the first service, improving resource utilization flexibility while ensuring service transmission.

[0253] It should be noted that for further details regarding step S503c, please refer to the description of method 1000 below (e.g., S1003-S1004), which will not be repeated here in the embodiments of this application.

[0254] In one possible implementation (method F), step S503 is implemented based on step S503d:

[0255] S503d: The first communication device selects a cell. If the selected cell is the third cell and the RRC connection is re-established through the third cell, the second resource is used to execute the first service. If the selected cell is the second cell, the second resource is released.

[0256] The second cell is different from the third cell.

[0257] It should be noted that the second resource is invalid until the RRC connection is re-established via the third cell. The invalidation of the second resource can be understood as the first communication device suspending its use of the second resource but not releasing it.

[0258] In this scenario, the second resource can be used when establishing a connection through the target cell, avoiding the need for the first communication device to wait for an RRC reconfiguration instruction before configuring the corresponding resources to execute the first service after re-establishing the connection. This reduces the impact of cell handover or RRC reconstruction on the first service, improving the flexibility of resource usage while ensuring service transmission.

[0259] It should be noted that for further details regarding step S503d, please refer to the description of method 900 below (e.g., S904), which will not be repeated here in the embodiments of this application.

[0260] In one possible implementation (method G), the above implementation DF also includes:

[0261] S503e: When the first communication device receives the second message, it uses the second resource to execute the first service.

[0262] In this scenario, the second resource can be used upon receiving the handover information. That is, during cell handover, the first communication device can use the second resource after receiving the handover information until the network device issues a new command, until reconstruction fails, or until another cell is selected. If the first communication device has not selected a target cell, it can also use the second resource from the moment it receives the second message. This avoids the inability to execute the first service during handover, improving resource utilization flexibility while ensuring service transmission.

[0263] It should be noted that for further details regarding step S503e, please refer to the description of method 1200 below. This application embodiment will not be repeated here.

[0264] Optionally, method 500 further includes step S504: the first network device sends second information to the first communication device; correspondingly, the first communication device receives the second information from the first network device.

[0265] In one possible implementation, the second information can be used by the network device to enable or control whether the first communication device can use AIoT resources, for example, whether it can use the second resource. In other words, the second information can be understood as a switch for the network device to enable or disable the first communication device's use of the second resource. Specifically, "whether the first communication device can use the second resource" can be understood as whether the first communication device can use the second resource during cell handover; "whether it can use the second resource" can also be understood as whether it can use the second resource to perform the first service.

[0266] Optionally, if the first communication device receives the second information, it may use the second resource according to the instructions of the second information. The second information may indicate one or more of the following: the first communication device uses the second resource corresponding to the second cell (target cell); or, the first communication device successfully rebuilds in the target cell and uses the second resource corresponding to the target cell; or, the first communication device selects the target cell for rebuilding and uses the second resource corresponding to the target cell; or, the first communication device initiates RRC connection rebuilding and uses the second resource corresponding to the target cell.

[0267] Optionally, the above-described use of the second resource can be replaced by restoring the use of the second resource. In various embodiments of this application, using the second resource and restoring the use of the second resource can be substituted for each other. Regarding the description of the second information, please refer to the relevant description of the first information in method 400 above, which will not be repeated here.

[0268] Optionally, the network device may indicate the second information in one or more of the following ways: For example, if the network device configures or sends the second information, the first communication device can use the second resource; if the network device does not configure or send the second information, the first communication device cannot use the second resource. Another example: the second information occupies 1 bit; if the bit corresponding to the second information exists, the first communication device can use the second resource; if the bit corresponding to the second information does not exist, the first communication device cannot use the second resource. Yet another example: the second information occupies 1 bit; if the bit corresponding to the second information is 1 or 0, the first communication device can use the second resource; if the bit corresponding to the second information is 0 or 1, the first communication device cannot use the second resource.

[0269] It should be understood that the embodiments of this application do not limit the timing of the execution of "using the second resource according to the instruction of the second information".

[0270] For example, the first communication device may use the second resource after receiving the second information.

[0271] For example, depending on the different implementations of step S503, the first communication device may further determine whether to use the second resource based on the content of the second information. For instance, the second information may indicate the situation in which the first communication device can use the second resource (for example, the first communication device may first receive the second information, and then determine whether to use the second resource based on the content indicated by the second information and the actual situation). For example, it may indicate one or more of the following situations.

[0272] For example, corresponding to S503a-S503b, the second information is used to instruct the first communication device to use the second resource to perform the first service when initiating the RRC connection reconstruction process.

[0273] For example, corresponding to S503c, the second information is used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the third cell, to use the second resource to perform the first service.

[0274] For example, corresponding to S503d, the second information is used to instruct the first communication device, during the process of initiating RRC connection reconstruction, if the selected cell is the third cell and the RRC connection reconstruction is completed through the third cell, to use the second resource to execute the first service.

[0275] For example, corresponding to S503e, the second information is used to instruct the first communication device to use the second resource to perform the first service when it receives the second message.

[0276] In this scenario, the second information can indicate different times for the use of the second resource, increasing the flexibility of resource allocation and indication. Alternatively, network devices can use the second information to flexibly control the use of the second resource by the first communication device, improving resource utilization flexibility while ensuring the transmission of the first service.

[0277] It should be noted that the embodiments of this application do not impose any restrictions on the timing of the execution of step S504.

[0278] Optionally, the second information is included in a third message, which may be the second message, system information, an RRC reconfiguration message, or an RRC connection reconstruction message.

[0279] It should be noted that the method of carrying the second information can be referred to in the relevant description of information #1 in methods 900-1200 below, and will not be repeated here.

[0280] Optionally, the cell selection process further includes: if a suitable NR cell is selected, starting a second timer, and sending an RRC request message through the selected cell during the operation of the second timer.

[0281] For example, if "cell selection" corresponds to the second time, the first communication device can also send a request message (e.g., an RRC reconstruction request) through the selected cell at the second time; and / or, the first communication device can also start a second timer at the second time, thereby waiting to receive a response message (a response message corresponding to the request message) sent by the network device during the operation of the second timer. In other words, the time of cell selection can also be understood as the time of starting the second timer.

[0282] For example, if "selecting a cell" corresponds to the second time, then the first communication device can also send a request message (e.g., an RRC reconstruction request) through the selected cell after the second time. In other words, the time of selecting a cell can also be understood as the time before the second timer is started.

[0283] It should be noted that the details of the second timer can be found in the description of timer #4 in methods 900-1200 below, and will not be repeated here in the embodiments of this application.

[0284] Figure 6 is a schematic diagram of a communication method 600 applicable to an embodiment of this application.

[0285] It should be understood that method 600 can be applied to the UE (or, or a unit (e.g., a chip) in the UE) and network device #1 (or, or a unit (e.g., a chip) in network device #1).

[0286] It should be noted that method 600 can be regarded as a specific implementation of method C in method 400.

[0287] Optionally, message #1 can be used as an example of the third message in method 400 above.

[0288] Optionally, resource #1 can be used as an example of the first resource in method 400 above.

[0289] Optionally, cell #1 can be used as an example of the first cell in method 400 above.

[0290] Alternatively, timer #3 can be used as an example of the first timer in method 400 above.

[0291] Optionally, information #1 can be used as an example of the first information in method 400 above.

[0292] Alternatively, timer #4 can be used as an example of the second timer in method 400 above.

[0293] Alternatively, timer #2 can be used as an example of the third timer in method 400 above.

[0294] It should also be noted that the above optional content also applies to methods 700-800, which will not be repeated below.

[0295] S601: The UE detected a physical layer problem.

[0296] Optionally, before step S601, the UE is in RRC connection state (i.e., the UE establishes an RRC connection with network device #1). The UE in RRC connection state will perform RLM to monitor the downlink radio link quality.

[0297] Specifically, the UE detects a physical layer problem at time T0#3 and restores the radio link.

[0298] For example, the UE detects a physical layer problem in the primary cell. Another example is that the UE's RRC layer receives a number #1 (e.g., N310) consecutive out-of-synchronization indications from the physical layer. The number #1 can be configured by network device #1, determined by the UE itself, or predefined by the protocol. This application embodiment does not limit the value or determination method of the number #1.

[0299] Optionally, the UE can start timer #1 at time T0#3 (for example, timer #1 can be T310 in the current technology, which will not be described in detail). For example, the UE can start timer #1 when a physical layer problem is detected. As another example, the UE's RRC layer can start timer #1 when it receives #1 consecutive out-of-synchronization indications from the physical layer.

[0300] Optionally, before step S601, the UE in the RRC connection state can execute service #1. Specifically, the UE can use resource #1 to execute service #1, wherein resource #1 can be configured by network device #1, resource #1 can be a resource of cell #1 (for example, it can be a resource dedicated to executing service #1, or it can be a resource that can be used to execute multiple services (including service #1)), cell #1 belongs to network device #1, and under the coverage of cell #1, the UE can establish an RRC connection with network device #1 through cell #1.

[0301] Optionally, the resources involved in the embodiments of this application can be understood as time-domain, frequency-domain, and / or spatial-domain resources, without limitation.

[0302] Optionally, if service #1 is an AIoT service, the UE can act as a reader to perform the AIoT service.

[0303] For example, the UE can execute AIoT services after receiving an AIoT service request from a network device (such as a core network device or network device #1). For instance, the UE can execute AIoT services when it has established an RRC connection with network device #1 (in RRC connected state). Network device #1 can also send message #1 to the UE, which configures resource #1, so that the UE can use resource #1 to execute AIoT services after receiving message #1.

[0304] Optionally, network device #1 can configure resource #1 for the UE in the following two ways:

[0305] Implementation method 1: The use and release of resource #1 are indicated by network device #1 through different information.

[0306] For example, network device #1 sends message #1.1 to configure resource #1 for the UE, or it can be understood as network device #1 sending message #1.1 to instruct the UE to use resource #1. Upon receiving message #1.1, the UE can use resource #1 to perform service #1. Network device #1 then sends message #1.2 to release resource #1 for the UE. Upon receiving message #1.2, the UE can release resource #1.

[0307] In other words, resource #1 is valid after the UE receives message #1.1 (i.e., the UE can use resource #1 (e.g., use resource #1 to perform service #1)) until the UE receives message #1.2.

[0308] Implementation Method 2: The use and release of resource #1 are indicated by the same information by network device #1. In other words, the use of resource #1 is indicated by network device #1 through information, and the release of resource #1 is controlled by time period.

[0309] For example, network device #1 sends message #1 to configure resource #1 for the UE, and simultaneously indicates the validity period (Duration1) of resource #1 to the UE. Here, Duration1 represents the effective scope of resource #1. For instance, when the UE receives message #1, resource #1 is valid and remains valid for Duration1 until Duration1 ends.

[0310] Optionally, Duration1 can be maintained using timer #2. For example, the UE can start timer #2 when it receives message #1, and the maximum duration of timer #2 is Duration1. Thus, while timer #2 is running, resource #1 is valid (for example, the UE can use resource #1 to perform service #1); if timer #2 times out, resource #1 becomes invalid (for example, the UE can release resource #1).

[0311] It should be noted that message #1 can directly configure resource #1 for the UE (for example, message #1 includes the specific range of time-domain, frequency-domain, and / or spatial-domain resources corresponding to resource #1); or, message #1 can indirectly configure resource #1 for the UE (for example, message #1 includes identifier #1 (identifier #1 is used to uniquely indicate resource #1); or, message #1 includes index #1 (for example, the UE and network device #1 can jointly maintain list #1, list #1 includes multiple resources and an index corresponding to each resource, index #1 is used to indicate resource #1)). This application embodiment does not limit the content of message #1.

[0312] Optionally, resource #1 can also be configured in other ways. For example, if the UE has previously established an RRC connection with network device #1 and previously used resource #1 to perform service #1, and if the UE re-establishes an RRC connection with network device #1 and performs service #1, the UE can determine to reuse resource #1 based on historical information. This application embodiment does not limit the configuration method of resource #1.

[0313] Optionally, the UE can also restore the radio link during the operation of timer #1.

[0314] For example, while timer #1 is running, resource #1 is valid, and the UE can continue to use resource #1 to perform service #1.

[0315] In one possible implementation, if the physical layer problem is resolved during the operation of timer #1, the UE can remain in the RRC connected state, and thus the UE can continue to use resource #1 to perform service #1.

[0316] In another possible implementation, if the physical layer problem is not resolved during the operation of timer #1, method 600 may optionally include step S602: the UE initiates a connection reconstruction process.

[0317] Specifically, the UE initiates a connection re-establishment process at time T1#3. During this process, the UE can perform cell selection or cell reselection. Resource #1 is invalid during the connection re-establishment process.

[0318] Optionally, time T1#3 can be the time when timer #1 times out.

[0319] Optionally, the UE may declare an RLF at time T1#3.

[0320] Optionally, the UE can start timer #3 at time T1#3 (for example, timer #3 can be T311 in the current technology, which will not be described in detail). Thus, the UE can perform cell selection or cell reselection during the operation of timer #3.

[0321] It should be noted that invalidating resource #1 can be understood as the UE suspending the use of resource #1, but not releasing resource #1. In other words, during the connection reconstruction process, the UE can retain the configuration information related to resource #1, but will no longer use resource #1 to perform service #1.

[0322] Optionally, S602 can also be understood as: the UE initiates a connection reconstruction process and considers resource #1 invalid; and / or, the UE starts timer #3 and considers resource #1 invalid during the execution of timer #3; and / or, the UE performs cell selection or cell reselection and considers resource #1 invalid.

[0323] It should be noted that the resource #1 corresponding to "resource #1 is invalid" can be configured through the two implementation methods in step S601, or it can be configured through other methods. This application embodiment does not limit it.

[0324] For example, when resource #1 is configured using implementation method 2 (the duration of resource #1's validity is maintained by timer #2), the "resource #1 invalid" can include the following two implementation methods:

[0325] (1) Sub-implementation method #1: Timer #2 times out or stops when the UE initiates the connection reconstruction process.

[0326] For example, the UE initiates a connection reconstruction process, deeming timer #2 to have timed out or stopped, or stops timer #2 and deems resource #1 invalid.

[0327] For example, the UE starts timer #3, considers timer #2 to have timed out or stopped, or stops timer #2 and considers resource #1 invalid.

[0328] For example, when the UE performs cell selection or cell reselection, it considers timer #2 to have timed out or stopped, or stops timer #2 and considers resource #1 to be invalid.

[0329] (2) Sub-implementation method #2: Timer #2 continues to run during the connection reconstruction process initiated by the UE.

[0330] For example, when the UE initiates a connection reconstruction process, timer #2 continues to run and considers resource #1 invalid.

[0331] For example, the UE starts timer #3, timer #2 continues to run, and considers resource #1 invalid.

[0332] For example, when the UE performs cell selection or cell reselection, timer #2 continues to run and resource #1 is considered invalid.

[0333] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0334] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#3 in Figure 6), then optionally, method 600 further includes step S603: the UE sends request message #1.

[0335] Specifically, at time T2#3, the UE sends request message #1 through the selected cell (appropriate cell) and waits to receive response message #1 from the network device. During this process, resource #1 remains invalid.

[0336] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0337] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0338] Optionally, the UE may send a request message #1 to network device #2. Network device #2 may be the same as network device #1, or it may be different from network device #1. Specifically, the UE may send the request message #1 to network device #2 through the appropriate cell.

[0339] It should be noted that the suitable community can be community #1 (i.e., the original community) or community #2 (another community besides community #1, i.e., the new community).

[0340] For example, when the suitable cell is the original cell, network device #2 is the same as network device #1.

[0341] For example, when the suitable cell is a new cell, cell #2 can belong to the same network device as cell #1 (i.e., network device #2 is the same as network device #1. For example, cell #1 and cell #2 are different cells of the same network device); cell #2 can also belong to different network devices than cell #1 (i.e., network device #2 is different from network device #1. For example, cell #1 and cell #2 are different cells of different network devices).

[0342] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), invalidating resource #1 also includes:

[0343] (1) If the cell selected by the UE is the original cell (i.e., the suitable cell is the original cell), the UE continues to reserve resource #1.

[0344] In other words, in this case, invalid resource #1 can be understood as the UE suspending the use of resource #1, but not releasing resource #1.

[0345] For example, when resource #1 is configured by implementation method 1, invalid resource #1 can be understood as the UE suspending the use of resource #1, but not releasing resource #1.

[0346] For example, if resource #1 is configured by implementation method 2 (e.g., the duration of resource #1 is maintained by timer #2), and if step S602 is implemented based on sub-implementation method #1, and in S602, timer #2 times out or stops, then "reserving resource #1" can be understood as timer #2 still being in the state of timeout or stopped when the UE sends request message #1.

[0347] For example, if resource #1 is configured by implementation method 2 (the effective duration of resource #1 is maintained by timer #2), and if step S602 is implemented based on sub-implementation method #2, that is, in S602, timer #2 continues to run, then the "reserve resource #1" can be understood as timer #2 still continuing to run, but resource #1 is not used.

[0348] (2) If the cell selected by the UE is a new cell (i.e., the suitable cell is a new cell), the UE releases resource #1.

[0349] For example, if resource #1 is configured by implementation method 1, and the UE selects a new cell, the UE releases resource #1.

[0350] For example, if resource #1 is configured by implementation method 2 (the effective duration of resource #1 is maintained by timer #2), and if step S602 is implemented based on sub-implementation method #1, and in S602, timer #2 times out or stops, then "releasing resource #1" can be understood as timer #2 still being in the state of timeout or stopped when the UE sends request message #1.

[0351] For example, if resource #1 is configured by implementation method 2 (the effective duration of resource #1 is maintained by timer #2), and if step S602 is implemented based on sub-implementation method #2, that is, in S602, timer #2 continues to run, then the "release resource #1" may also include: the UE releases resource #1 and considers timer #2 to have timed out or stopped, or the UE releases resource #1 and stops timer #2.

[0352] It should be understood that S603 can also be interpreted as follows: The UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE stops timer #3. Furthermore, the UE can confirm whether the selected cell is the original cell. If it is the original cell, the UE continues to retain resource #1; if it is not the original cell, the UE releases resource #1. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending the first request message, the UE confirms whether the selected cell is the original cell. If it is the original cell, the UE continues to retain resource #1; if it is not the original cell, the UE releases resource #1.

[0353] Optionally, the UE can start timer #4 at time T2#3 (timer #4 can be T301 in the current technology, which will not be described in detail), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0354] It should be understood that S603 can also be understood as: the UE sends a request message #1 and considers resource #1 invalid; and / or, the UE starts timer #4 and considers resource #1 invalid during the execution of timer #4; and / or, the UE considers resource #1 invalid while waiting to receive response message #1 sent by the network device.

[0355] Optionally, S603 can also be understood as: when the UE stops timer #3, and / or the UE selects a suitable cell, and / or the UE sends a request message #1, and / or the UE starts timer #4, if the selected cell is the original cell, the UE continues to retain resource #1; if the selected cell is not the original cell, the UE releases resource #1.

[0356] It should be noted that regardless of whether the UE selects the original cell or the new cell, if resource #1 has already been deemed invalid in step S602, then resource #1 can continue to be deemed invalid when and / or after the UE sends request message #1. That is, the description of "resource #1 remains invalid" in step S603 is used to indicate that resource #1 is still unavailable to the UE. Therefore, the UE simply continues the state of resource #1 being invalid in step S602, and there is no need to further define the behavior of the UE considering "resource #1 invalid".

[0357] For example, when and / or after sending request message #1, the UE continues to consider resource #1 invalid until the UE receives response message #1 from the network device.

[0358] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0359] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#3 in Figure 6), then optionally, method 600 further includes step S604: the UE resumes using resource #1.

[0360] Optionally, restoring the use of resource #1 can be understood as resource #1 being valid, or the UE being able to use resource #1 to perform service #1. It should be noted that the description "restoring the use of resource #1" is used to describe the situation where resource #1 was used before step S604 (resource #1 was valid before T1#3, invalid from T1#3 to T3#3, and valid from T3#3 onwards). Therefore, the UE restoring the use of resource #1 can also be referred to as the UE using resource #1, which will not be elaborated further in this embodiment.

[0361] It should be noted that the execution of step S604 is based on the condition that the cell selected by the UE in step S603 is the original cell. That is, after the UE initiates RRC connection reconstruction, the UE may choose the original cell or a new cell for RRC connection reconstruction. If the UE successfully reconstructs the connection in the original cell, it can continue to use the resource #1 corresponding to the original cell. In other words, if the UE experiences a problem with the radio link corresponding to cell #1, but then re-establishes the connection with network device #1 in cell #1, the UE can continue to use the resource #1 corresponding to cell #1.

[0362] In one possible implementation, the UE can directly use resource #1 if the above conditions are met. For example, if the UE successfully rebuilds in cell #1, the UE can directly resume using resource #1.

[0363] In another possible implementation, the UE can use resource #1 at the instruction of the network device (or it can also be enabled by the network device). For example, network device #1 can send information #1 to the UE, and correspondingly, the UE receives information #1 sent by network device #1.

[0364] Optionally, the information #1 may indicate one or more of the following: the UE resumes using the resources #1 configured in the original cell; the UE successfully rebuilds in the original cell and resumes using the resources #1 configured in the original cell, etc.

[0365] Optionally, the method of carrying the information #1 may include one or more of the following:

[0366] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1.

[0367] For example, before step S601, when the UE is in RRC connected state, network device 1# can send an RRC reconfiguration message to the UE, the RRC reconfiguration message including information #1.

[0368] Optionally, network device #1 may also simultaneously send the resource configuration of service #1 (e.g., configuration information of resource #1 (e.g., message #1 in step S601)) and information #1 to the UE.

[0369] Optionally, message #1 and information #1 can be two different messages, or they can be carried in the same RRC reconfiguration message.

[0370] It should be understood that the content of the RRC reconfiguration message can be found in the relevant descriptions in the current technology, and will not be repeated here in the embodiments of this application.

[0371] In this case, information #1 can be UE-level, meaning that network device #1 can send the corresponding information #1 to each UE.

[0372] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1.

[0373] For example, network device #1 can send information #1 to all (or some) UEs under its coverage through system information; or, network device #1 can send information #1 to all (or some) UEs with which it has established a connection through system information.

[0374] For example, network device #1 sends information #1 to all (or some) UEs covered by cell #1 through system information; or, network device #1 sends information #1 to all (or some) UEs that have established a connection with network device #1 through cell #1 through system information.

[0375] It should be understood that the content of the cell system information can be referred to the relevant descriptions in the current technology, and will not be repeated here in the embodiments of this application.

[0376] In this case, information #1 can be at the cell or base station granularity.

[0377] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1.

[0378] In this situation, network device #1 can instruct the UE whether it can resume using resource #1 when the UE successfully rebuilds in the original cell.

[0379] It should be noted that the above three methods of carrying information #1 are not limited to the resource #1 configured based on implementation method 1 and implementation method 2 in step S601, but can also be applied to resource #1 configured based on other methods. This application embodiment does not limit this.

[0380] Furthermore, if in step S601 resource #1 is configured by implementation method 2 (the duration of resource #1's effectiveness is maintained by timer #2), and if steps S602 and S603 are implemented based on sub-implementation method #2, i.e., timer #2 continues to run in step S602, then step S604 can also be understood as: the UE can determine whether resource #1 is available based on whether timer #2 is running; or, the UE can determine whether resource #1 can be restored based on whether timer #2 is running. For example, if timer #2 is running, the UE uses resource #1 (e.g., the UE uses resource #1 to perform service #1); if timer #2 is not running or has expired, the UE does not use resource #1 (e.g., the UE does not use resource #1 to perform service #1, or the UE does not perform service #1).

[0381] Optionally, after the UE successfully rebuilds in the original cell (i.e., the UE establishes a connection with network device #1 through the original cell), network device #1 can also send message #2 to the UE. Message #2 is used to configure resource #2, and the UE can execute service #1 through resource #2. Resource #2 can be the same as or different from resource #1.

[0382] For example, message #2 can be an RRC reconfiguration message. After successful reconstruction, network device #1 can send message #2 via the RRC reconfiguration message. Thus, after receiving message #2, the UE can use resource #2 to perform service #1.

[0383] Optionally, if the UE does not receive message #2 from network device #1 after the original cell is successfully rebuilt (for example, the RRC reconfiguration message sent by network device #1 to the UE after the successful reconstruction does not include message #2), the UE can continue to use resource #1 to perform service #1.

[0384] In other words, the UE can determine whether to continue using resource #1 to perform service #1 based on whether there is a new resource configuration for performing service #1.

[0385] It should be noted that the specific configuration method of resource #2 and the specific content of message #2 can be referred to the relevant description of resource #1 and message #1 in step S601. Resource #1 and message #1 can be replaced with resource #2 and message #2 respectively. This application embodiment will not be described in detail here.

[0386] If the UE selects a new cell (i.e., step S604 is not executed), then after the UE establishes a connection with network device #2 through the new cell, network device #2 can send message #3 (e.g., RRC reconfiguration message) to the UE. Message #3 is used to configure resource #3, so that after the UE receives message #3, it can use resource #3 to perform service #1.

[0387] It should be noted that the specific configuration method of resource #3 and the specific content of message #3 can be referred to the relevant description of resource #1 and message #1 in step S601. Resource #1 and message #1 can be replaced with resource #3 and message #3 respectively. This application embodiment will not be described in detail here.

[0388] It should be noted that in method 600, the UE can use resource #1 when re-establishing the connection through the original cell, avoiding the need to wait for the RRC reconfiguration instruction after re-establishing the connection before configuring the corresponding resources to execute service #1, reducing the impact of failure on service #1, and improving the flexibility of resource usage while ensuring service transmission.

[0389] Figure 7 is a schematic diagram of a communication method 700 applicable to an embodiment of this application.

[0390] It should be understood that method 700 can be applied to the UE (or, or a unit (e.g., a chip) in the UE) and network device #1 (or, or a unit (e.g., a chip) in network device #1).

[0391] It should be noted that method 700 can be regarded as a specific implementation of method B in method 400.

[0392] S701: The UE detected a physical layer problem.

[0393] Specifically, the UE detected a physical layer problem at time T0#4 and restored the radio link.

[0394] Optionally, the UE can start timer #1 at time T0#4 (timer #1 can be T310, which will not be elaborated here).

[0395] It should be noted that the specific content of step S701 can be referred to the relevant description of step S601 in method 600, and "T0#3" can be replaced with "T0#4" accordingly. The embodiments of this application will not be described in detail here.

[0396] In one possible implementation, if the physical layer problem is resolved during the operation of timer #1, the UE can remain in the RRC connected state, and thus the UE can continue to use resource #1 to perform service #1.

[0397] In another possible implementation, if the physical layer problem is not resolved during the operation of timer #1, method 700 may optionally include step S702: the UE initiates a connection reconstruction process.

[0398] Specifically, the UE initiates a connection re-establishment process at time T1#4. During this process, the UE can perform cell selection or cell reselection. Resource #1 is invalid during the connection re-establishment process.

[0399] Optionally, time T1#4 can be the time when timer #1 times out.

[0400] Optionally, the UE may declare an RLF at time T1#4.

[0401] Optionally, the UE can start timer #3 at time T1#4 (timer #3 can be T311, which will not be elaborated here).

[0402] It should be noted that the specific content of step S702 can be referred to the relevant description of step S602 in method 600, and "T1#3" can be replaced with "T1#4" accordingly. The embodiments of this application will not be described in detail here.

[0403] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0404] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#4 in Figure 7), then optionally, method 700 further includes step S703: the UE sends request message #1.

[0405] Specifically, the UE sends a request message #1 at time T2#4 and waits to receive a response message #1 from the network device.

[0406] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0407] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0408] Optionally, the UE may send a request message #1 to network device #2. Network device #2 may be the same as network device #1, or it may be different from network device #1. Specifically, the UE may send the request message #1 to network device #2 through the appropriate cell.

[0409] It should be noted that the suitable community can be community #1 (i.e., the original community) or community #2 (another community besides community #1, i.e., the new community).

[0410] For example, when the suitable cell is the original cell, network device #2 is the same as network device #1.

[0411] For example, when the suitable cell is a new cell, cell #2 can belong to the same network device as cell #1 (i.e., network device #2 is the same as network device #1); cell #2 can belong to different network devices than cell #1 (i.e., network device #2 is different from network device #1).

[0412] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), the UE's processing of resource #1 includes the following two cases:

[0413] (1) If the cell selected by the UE is the original cell (i.e., the suitable cell is the original cell), the UE resumes using resource #1.

[0414] In other words, if the cell selected by the UE is the original cell, the UE can resume using resource #1 at the same time as sending request message #1 (i.e., at time T2#4).

[0415] Optionally, restoring the use of resource #1 can be understood as resource #1 being valid, or the UE being able to use resource #1 to perform service #1.

[0416] That is, if the UE encounters a problem with the radio link corresponding to cell #1, and the UE selects cell #1 again through cell selection or cell reselection, the UE can resume using resource #1, for example, continue to use resource #1 corresponding to cell #1 (to perform service #1).

[0417] In this situation, the UE has a high probability of being able to successfully rebuild in the original cell, and the UE can resume using resource #1 first.

[0418] (2) If the cell selected by the UE is a new cell (i.e., the suitable cell is a new cell), the UE releases resource #1.

[0419] For example, if resource #1 is configured by implementation method 1, and the UE selects a new cell, the UE releases resource #1.

[0420] For example, if resource #1 is configured by implementation method 2 (the effective duration of resource #1 is maintained by timer #2), and if step S702 is implemented based on sub-implementation method #1, and in S702, timer #2 times out or stops, then the "release resource #1" can be understood as timer #2 still being in the state of timeout or stopped when the UE sends request message #1.

[0421] For example, if resource #1 is configured by implementation method 2 (the effective duration of resource #1 is maintained by timer #2), and if step S702 is implemented based on sub-implementation method #2, that is, in S702, timer #2 continues to run, then the "release resource #1" may also include: the UE releases resource #1 and considers timer #2 to have timed out or stopped, or the UE releases resource #1 and stops timer #2.

[0422] It should be understood that S703 can also be interpreted as follows: The UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE stops timer #3. Furthermore, the UE can confirm whether the selected cell is the original cell. If it is the original cell, the UE resumes using resource #1; if it is not the original cell, the UE releases resource #1. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending the request message #1, if the selected cell is the original cell, the UE resumes using resource #1; if the selected cell is not the original cell, the UE releases resource #1.

[0423] Optionally, the UE can start timer #4 at time T2#4 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0424] It should be understood that S703 can also be understood as follows: if the selected cell is the original cell, the UE sends a request message #1 and resumes the use of resource #1; and / or, if the selected cell is the original cell, the UE starts timer #4 and resumes the use of resource #1 during the execution of timer #4; and / or, if the selected cell is the original cell, the UE resumes the use of resource #1 while waiting to receive the response message #1 sent by the network device.

[0425] Optionally, S703 can also be understood as: when the UE stops timer #3, and / or when the UE selects a suitable cell, and / or when the UE sends request message #1, and / or when the UE starts timer #4, if the selected cell is the original cell, the UE resumes using resources #1; if the selected cell is not the original cell, the UE releases resources #1.

[0426] In one possible implementation, the UE can directly use resource #1 if the above conditions are met. For example, if the cell selected by the UE is the original cell, the UE can directly resume using resource #1.

[0427] In another possible implementation, the UE can use resource #1 at the instruction of the network device (or it can also be enabled by the network device). For example, network device #1 can send information #1 to the UE, and correspondingly, the UE receives information #1 sent by network device #1.

[0428] Optionally, the information #1 may indicate one or more of the following: the UE resumes using the resources #1 configured in the original cell; if the cell selected by the UE is the original cell, then the resources #1 configured in the original cell are resumed; if the UE sends a request message #1 in the original cell, then the resources #1 configured in the original cell are resumed; if the UE starts timer #4, then the resources #1 configured in the original cell are resumed, etc.

[0429] Optionally, the method of carrying the information #1 may include one or more of the following:

[0430] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1;

[0431] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1;

[0432] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1;

[0433] It should be noted that for the specific details of the above-mentioned bearing methods (1)-(3), please refer to the relevant description of the three bearing methods in step S604 of method 600 above. This application embodiment will not repeat the details here.

[0434] It should be noted that the above three methods of carrying information #1 are not limited to the resource #1 configured based on implementation method 1 and implementation method 2 in step S701, but can also be applied to resource #1 configured based on other methods. This application embodiment does not limit this.

[0435] Furthermore, if in step S701 resource #1 is configured by implementation method 2 (the duration of resource #1's effectiveness is maintained by timer #2), and if step S702 is implemented based on sub-implementation method #2, i.e., timer #2 continues to run in step S702, then step S703 can also be understood as: the UE can determine whether resource #1 is available based on whether timer #2 is running; or, the UE can determine whether resource #1 can be restored based on whether timer #2 is running. For example, if timer #2 is running, the UE uses resource #1 (e.g., the UE uses resource #1 to perform service #1); if timer #2 is not running or has expired, the UE does not use resource #1 (e.g., the UE does not use resource #1 to perform service #1, or the UE does not perform service #1).

[0436] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0437] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#4 in Figure 7), then optionally, method 700 further includes step S704: the UE successfully rebuilds in cell #1.

[0438] It should be noted that the execution of step S704 is based on the condition that the cell selected by the UE in step S703 is the original cell. That is, after the UE initiates RRC connection reconstruction, the UE may choose the original cell for RRC connection reconstruction or it may choose a new cell for RRC connection reconstruction.

[0439] Optionally, if the UE successfully rebuilds in the original cell, it can continue to use resource #1 corresponding to the original cell (to perform service #1). That is, if the UE experiences a problem with the radio link corresponding to cell #1 but then re-establishes its connection with network device #1 in cell #1, and if the UE receives response message #1 from network device #1, the UE can continue to use resource #1 to perform service #1. In other words, the content indicated by information #1 can also be understood as: the UE can start using resource #1 from selecting the original cell (and / or, starting timer #4; and / or, sending request message #1 in the original cell; and / or, stopping timer #3) until network device #1 issues a new command, or until the UE fails to rebuild.

[0440] Optionally, after the UE successfully rebuilds in the original cell (i.e., the UE establishes a connection with network device #1 through the original cell), network device #1 can also send message #2 to the UE. Message #2 is used to configure resource #2, and the UE can execute service #1 through resource #2. Resource #2 can be the same as or different from resource #1.

[0441] It should be understood that the specific content of message #2 can be referred to the relevant description of message #2 in step S604 of method 600, and will not be repeated here in the embodiments of this application.

[0442] If the UE selects a new cell (i.e., step S704 is not executed), then after the UE establishes a connection with network device #2 through the new cell, network device #2 can send message #3 (e.g., an RRC reconfiguration message) to the UE. Message #3 is used to configure resource #3, so that after receiving message #3, the UE can use resource #3 to perform service #1. For details, please refer to the relevant content of step S604 in method 600, which will not be repeated here in this embodiment.

[0443] It should be noted that in method 700, the UE can use resource #1 when reselecting the original cell, allowing the UE to execute service #1 before re-establishing the connection through the original cell. This reduces the impact of failures on service #1 and improves the flexibility of resource utilization while ensuring service transmission.

[0444] Figure 8 is a schematic diagram of a communication method 800 applicable to an embodiment of this application.

[0445] It should be understood that method 800 can be applied to the UE (or, or a unit (e.g., a chip) in the UE) and network device #1 (or, or a unit (e.g., a chip) in network device #1).

[0446] It should be noted that method 800 can be regarded as a specific implementation of method A in method 400.

[0447] S801: The UE detected a physical layer problem.

[0448] Specifically, the UE detected a physical layer problem at time T0#5 and restored the radio link.

[0449] Optionally, the UE can start timer #1 at time T0#5 (timer #1 can be T310, which will not be elaborated here).

[0450] It should be noted that the specific content of step S801 can be referred to the relevant description of step S601 in method 600, and "T0#3" can be replaced with "T0#5" accordingly. The embodiments of this application will not be described in detail here.

[0451] In one possible implementation, if the physical layer problem is resolved during the operation of timer #1, the UE can remain in the RRC connected state, and thus the UE can continue to use resource #1 to perform service #1.

[0452] In another possible implementation, if the physical layer problem is not resolved during the operation of timer #1, method 800 may optionally include step S802: the UE initiates a connection reconstruction process.

[0453] Specifically, the UE initiates a connection re-establishment process at time T1#5. During this process, the UE can perform cell selection or cell reselection. Resource #1 is used during the connection re-establishment process.

[0454] It should be noted that using resource #1 can be understood as resource #1 being valid, or the UE being able to use resource #1 to perform service #1.

[0455] Optionally, time T1#5 can be the time when timer #1 times out.

[0456] Optionally, the UE may declare an RLF at time T1#5.

[0457] Optionally, the UE can start timer #3 at time T1#5 (timer #3 can be T311, which will not be elaborated here).

[0458] Optionally, S802 can also be understood as: the UE initiates a connection reconstruction process and uses resource #1; and / or, the UE starts timer #3 and uses resource #1 during the operation of timer #3; and / or, the UE performs cell selection or cell reselection and uses resource #1.

[0459] It should be noted that the resource #1 corresponding to "using resource #1" can be configured through the two implementation methods in step S801, which will not be elaborated here; or, it can be configured through other methods, which will not be limited in the embodiments of this application.

[0460] In one possible implementation, the UE can directly use resource #1 if the above conditions are met. For example, if the UE initiates a connection reconstruction process (and / or starts timer #3; and / or performs cell selection or cell reselection), the UE can directly use resource #1.

[0461] In another possible implementation, the UE can use resource #1 at the instruction of the network device (or it can also be enabled by the network device). For example, network device #1 can send information #1 to the UE, and correspondingly, the UE receives information #1 sent by network device #1.

[0462] Optionally, the information #1 may indicate one or more of the following: the UE uses the resource #1 configured in the original cell; the UE uses the resource #1 configured in the original cell when initiating a reconstruction process; the UE uses the resource #1 configured in the original cell when starting timer #3; the UE uses the resource #1 configured in the original cell when performing cell reselection or cell selection, etc.

[0463] Optionally, the method of carrying the information #1 may include one or more of the following:

[0464] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1;

[0465] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1;

[0466] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1;

[0467] It should be noted that for the specific details of the above-mentioned bearing methods (1)-(3), please refer to the relevant description of the three bearing methods in step S604 of method 600 above. This application embodiment will not repeat the details here.

[0468] It should be noted that the above three methods of carrying information #1 are not limited to the resource #1 configured based on implementation method 1 and implementation method 2 in step S801, but can also be applied to resource #1 configured based on other methods. This application embodiment does not limit this.

[0469] Furthermore, if in step S801 resource #1 is configured by implementation method 2 (the duration of resource #1's effectiveness is maintained by timer #2), then step S802 can also be understood as follows: the UE can determine whether resource #1 is available based on whether timer #2 is running; or, the UE can determine whether resource #1 can be used based on whether timer #2 is running. For example, if timer #2 is running, the UE uses resource #1 (e.g., the UE uses resource #1 to perform service #1); if timer #2 is not running or has expired, the UE does not use resource #1 (e.g., the UE does not use resource #1 to perform service #1, or the UE does not perform service #1).

[0470] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0471] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#5 in Figure 8), then optionally, method 800 further includes step S803: the UE sends request message #1.

[0472] Specifically, the UE sends a request message #1 at time T2#5 and waits to receive a response message #1 from network device #2.

[0473] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0474] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0475] Optionally, the UE may send a request message #1 to network device #2. Network device #2 may be the same as network device #1, or it may be different from network device #1. Specifically, the UE may send the request message #1 to network device #2 through the appropriate cell.

[0476] It should be noted that the suitable community can be community #1 (i.e., the original community) or community #2 (another community besides community #1, i.e., the new community).

[0477] For example, when the suitable cell is the original cell, network device #2 is the same as network device #1.

[0478] For example, when the suitable cell is a new cell, cell #2 can belong to the same network device as cell #1 (i.e., network device #2 is the same as network device #1); cell #2 can belong to different network devices than cell #1 (i.e., network device #2 is different from network device #1).

[0479] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), the UE may perform the following processing based on resource #1:

[0480] (1) If the cell selected by the UE is the original cell (i.e., the suitable cell is the original cell), the UE continues to use resource #1.

[0481] It is understandable that, in step S802, although the UE is selecting a cell (i.e., the UE has not determined the cell to be selected), the UE has not stopped using resource #1 (for example, the UE continues to use resource #1 to perform service #1). Therefore, at time T2#5, since the UE has still selected the original cell, the UE can continue to maintain its previous behavior (i.e., continue to use resource #1).

[0482] In other words, the content indicated by information #1 can also be understood as: the UE can start using resource #1 from the beginning of the connection reconstruction process (and / or, start timer #3; and / or, perform cell selection or cell reselection) until the network device #1 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell.

[0483] (2) If the cell selected by the UE is a new cell (i.e., the suitable cell is a new cell), the UE releases resource #1.

[0484] For example, if resource #1 is configured by implementation method 2 (the duration of resource #1 is maintained by timer #2), in step S802, if timer #2 continues to run, then "releasing resource #1" may also include: the UE releasing resource #1 and considering timer #2 to have timed out or stopped, or the UE releasing resource #1 and stopping timer #2.

[0485] It should be understood that S803 can also be interpreted as follows: During the operation of timer #3, the UE can select a suitable cell. If the UE selects a suitable cell and it is the original cell, the UE continues to use resource #1. If the suitable cell is a new cell, the UE releases resource #1. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending the request message #1, if the selected cell is the original cell, the UE continues to use resource #1. If the selected cell is not the original cell, the UE releases resource #1.

[0486] Similarly, if resource #1 in step S801 is configured using implementation method 2 (the duration of resource #1's effectiveness is maintained by timer #2), then step S803 can also be understood as follows: the UE can determine whether resource #1 is available based on whether timer #2 is running; or, the UE can determine whether it can continue to use resource #1 based on whether timer #2 is running. For example, if timer #2 is running, the UE continues to use resource #1 (e.g., the UE continues to use resource #1 to perform service #1); if timer #2 is not running or has expired, the UE does not use resource #1 (e.g., the UE does not use resource #1 to perform service #1, or the UE does not perform service #1).

[0487] Optionally, the UE can start timer #4 at time T2#5 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0488] Optionally, S803 can also be understood as: during the operation of timer #4 (or when timer #4 is started), if the cell selected by the UE is the original cell, resource #1 is valid (the UE can continue to use resource #1).

[0489] Optionally, S803 can also be understood as: when the UE stops timer #3, and / or the UE selects a suitable cell, and / or the UE sends request message #1, and / or the UE starts timer #4, if the selected cell is the original cell, the UE continues to use resource #1; if the selected cell is not the original cell, the UE releases resource #1.

[0490] It should be noted that since resource #1 is already considered valid in step S802, the description of "continue to use resource #1 (or resource #1 continues to be valid)" in step S803 is used to explain that resource #1 is still available to the UE. Therefore, the UE simply continues the state of resource #1 being valid in step S802, and there is no need to further define the behavior of the UE considering "resource #1 to be valid (or the UE continues to use resource #1)".

[0491] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0492] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#5 in Figure 8), then optionally, method 800 further includes step S804: the UE successfully rebuilds in cell #1.

[0493] It should be noted that the execution of step S804 is based on the condition that the cell selected by the UE in step S803 is the original cell. That is, after the UE initiates RRC connection reconstruction, the UE may choose the original cell or a new cell for RRC connection reconstruction. If the cell selected by the UE is the original cell, it can continue to use the resource #1 corresponding to the original cell (to perform service #1). In other words, if the UE experiences a problem with the radio link corresponding to cell #1 and then re-establishes the connection with network device #1 in cell #1, the UE can continue to use resource #1 (i.e., the UE's performance of service #1 will not be affected by the radio link problem) until network device #1 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell.

[0494] Optionally, after the UE successfully rebuilds in the original cell (i.e., the UE establishes a connection with network device #1 through the original cell), network device #1 can also send message #2 to the UE. Message #2 is used to configure resource #2, and the UE can execute service #1 through resource #2. Resource #2 can be the same as or different from resource #1.

[0495] It should be understood that the specific content of message #2 can be referred to the relevant description of message #2 in step S604 of method 600, and will not be repeated here in the embodiments of this application.

[0496] If the UE selects a new cell (i.e., step S804 is not executed), then after the UE establishes a connection with network device #2 through the new cell, network device #2 sends message #3 (e.g., an RRC reconfiguration message) to the UE. Message #3 is used to configure resource #3, so that after receiving message #3, the UE can use resource #3 to perform service #1. For details, please refer to the relevant content of step S604 in method 600, which will not be repeated here in this embodiment.

[0497] It should be noted that in method 800, the UE can use resource #1 when initiating the RRC connection reconstruction process. That is, if the UE experiences a link failure in the original cell, but then re-establishes a connection with network device #1 in the original cell (meaning the UE's execution of service #1 will not be affected by the failure), this connection will continue until network device #1 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell. If the UE does not select the original cell, it can also use resource #1 before selecting a new cell. This avoids the inability to execute service #1 after a failure, improving resource utilization flexibility while ensuring service transmission.

[0498] Figure 9 is a schematic diagram of a communication method 900 applicable to an embodiment of this application.

[0499] It should be understood that method 900 can be applied to the UE (or, or a unit (e.g., a chip) in the UE) and network device #1, network device #2 and / or network device #3 (or, or a unit (e.g., a chip) in network device #1, network device #2 and / or network device #3).

[0500] It should be noted that method 900 can be regarded as a specific implementation of method F in method 500.

[0501] Optionally, resource #1 can be used as an example of the first resource in method 500 above.

[0502] Alternatively, resource #4 can be used as an example of the second resource in method 500 above.

[0503] Optionally, cell #1 (or the original cell) can be used as an example of the first cell in Method 500 above.

[0504] Alternatively, the target cell can be an example of the third cell in Method 500 above.

[0505] Optionally, switching information #1 can be used as an example of the second message in method 500 above.

[0506] Alternatively, timer #3 can be used as an example of the first timer in method 500 above.

[0507] Alternatively, timer #4 can be used as an example of the second timer in method 500 above.

[0508] Alternatively, timer #2.1 can be used as an example of the third timer in method 500 above.

[0509] Optionally, information #1 can be used as an example of the second information in method 500 above.

[0510] Optionally, message #1 can be used as an example of the third message in method 500 above.

[0511] It should also be noted that the above optional content also applies to methods 1000-1200, which will not be repeated below.

[0512] S901: The UE has received handover information #1.

[0513] Specifically, the UE receives handover information #1 at time T0#6 and performs handover based on handover information #1. Handover information #1 is used to instruct the UE to handover to the target cell.

[0514] Optionally, before step S901, the UE is in RRC connection state (i.e., the UE establishes an RRC connection with network device #1). Therefore, when the UE in RRC connection state receives handover information #1 (e.g., an RRC reconfiguration message carrying reconfigurationWithSync (RRCReconfiguration message)) (corresponding to time T0#6), the UE can perform a handover.

[0515] For example, the UE can start timer #5 at time T0#6 (for example, timer #5 can be T304 in the current technology) and perform handover during the operation of timer #5 (for example, handover to the target cell, or initiate random access in the target cell).

[0516] Optionally, before step S901, the UE in the RRC connected state can execute service #1. Specifically, the UE can use resource #1 to execute service #1, wherein resource #1 can be configured by network device #1, and resource #1 can be a resource of cell #1 (for example, a resource dedicated to executing service #1, or a resource that can be used to execute multiple services (including service #1)). Cell #1 belongs to network device #1, and under the coverage of cell #1, the UE can establish an RRC connection with network device #1 through cell #1. Cell #1 can also be referred to as the original cell.

[0517] Optionally, the resources involved in the embodiments of this application can be understood as time-domain, frequency-domain, and / or spatial-domain resources, without limitation.

[0518] Optionally, if service #1 is an AIoT service, the UE can act as a reader to perform the AIoT service.

[0519] For example, the UE can execute AIoT services after receiving an AIoT service request from a network device (such as a core network device or network device #1). For example, the UE can execute AIoT services when it has established an RRC connection with network device #1 (in RRC connection state).

[0520] It should be noted that the method by which network device #1 configures resource #1 for the UE can be referred to the relevant description in method 600 above, and will not be repeated here. For example, network device #1 can configure resource #1 for the UE based on message #1 through implementation method 1 and / or implementation method 2.

[0521] Optionally, the target cell belongs to network device #2, which may be the same as or different from network device #1. Therefore, the target cell may be the same as or different from the original cell. This application does not impose any limitations on the embodiments thereof.

[0522] For example, when the target cell is the original cell, network device #2 is the same as network device #1.

[0523] For example, when the target cell is not the original cell, the target cell can belong to the same network device as cell #1 (i.e., network device #2 is the same as network device #1. For example, cell #1 and the target cell are different cells of the same network device); the target cell can also belong to different network devices than cell #1 (i.e., network device #2 is different from network device #1. For example, cell #1 and the target cell are different cells of different network devices).

[0524] Optionally, the handover information #1 can be sent by network device #1. Alternatively, the handover information #1 can be generated by network device #2 and then sent to the UE via network device #1.

[0525] Optionally, network device #2 can configure resource #4 for the UE. Resource #4 is a resource of the target cell (or target station, i.e., network device #2) (e.g., a resource dedicated to performing service #1, or a resource capable of performing multiple services (including service #1)). If network device #1 is different from network device #2, network device #2 can send resource #4 to network device #1 (e.g., network device #2 can indicate resource #4 to network device #1 via the Xn interface), and then network device #1 will send resource #4 to the UE; in other words, network device #1 will configure resource #4 for the UE.

[0526] It should be understood that the specific configuration method can refer to the relevant description of network device #1 configuring resource #1 for UE in method 600 above. Simply replace network device #1 with network device #2 and resource #1 with resource #4. Further details will not be provided here. It should be noted that network device #2 can configure resource #4 for UE based on message #1#3 through implementation method 1 and / or implementation method 2 (e.g., the validity period (Duration2) of resource #4 is maintained by timer #2.1).

[0527] Optionally, the handover information #1 may include information about resource #4, meaning that resource #4 can be configured for the UE through the handover information #1. In other words, the handover information #1 may include the content of message #1#3.

[0528] For example, the handover information #1 may include the specific range of the time domain, frequency domain and / or spatial domain resources corresponding to resource #4; or, the handover information #1 may include an identifier #2 (identifier #2 is used to uniquely indicate resource #4); or, the handover information #1 may include an index #2 (for example, the UE and network device #2 may jointly maintain a list #2, which includes multiple resources and an index corresponding to each resource, and the index #2 is used to indicate resource #4).

[0529] Optionally, resource #4 may override resource #1. For example, after receiving the configuration information for resource #4, the UE saves and overrides the configuration information for resource #1. For example, after receiving handover information #1, the UE saves and overrides the already saved RRC configuration information. For example, if handover information #1 includes the configuration information for resource #4, the UE may override the configuration information for resource #1 with the configuration information for resource #4 included in the handover information #1.

[0530] Optionally, resource #4 can be the same as resource #1 (e.g., if the target cell is the original cell), or it can be different from resource #1.

[0531] In one possible implementation, if the UE is aware of the information of resource #4 (e.g., has been configured with the resources of the target cell that can be used by the UE through messages #1#3 and / or handover information #1 (resource #4)), then the UE can use resource #4 for a period of time (perform service #1) during subsequent processing. For details, please refer to the description below, which will not be repeated here.

[0532] The following explanation uses "Switch information #1 includes information about resource #4" as an example.

[0533] Optionally, the UE may release resource #1 at time T0#6. For example, if resource #1 is configured by implementation method 2 (the duration of resource #1 is maintained by timer #2), the UE releases resource #1 and considers that the timer #2 corresponding to resource #1 has timed out or stopped, or stops considering that the timer #2 corresponding to resource #1 is stopped.

[0534] If the UE successfully hands over (i.e. successfully accesses the target cell) during the operation of timer #5, for example, if the UE establishes an RRC connection with network device #2 through the target cell, then after successfully accessing the cell, the UE can use resource #4 (resource #4 is valid).

[0535] If the UE fails to switch successfully during the operation of timer #5, the method 900 may optionally include step S902: the UE initiates a connection reconstruction process.

[0536] Specifically, the UE initiates a connection re-establishment process at time T1#6. During this process, the UE can perform cell selection or cell reselection. Resource #4 is invalid during the connection re-establishment process.

[0537] Optionally, time T1#6 can be the time when timer #5 times out.

[0538] Optionally, the UE can start timer #3 at time T1#6 (timer #3 can be T311, which will not be elaborated here). Thus, the UE can perform cell selection or cell reselection during the operation of timer #3.

[0539] It should be noted that invalidating resource #4 can be understood as the UE suspending the use of resource #4, but not releasing resource #4. In other words, during the connection reconstruction process, the UE can retain the configuration information related to resource #4, but will no longer use resource #4 to perform service #1.

[0540] Optionally, S602 can also be understood as: the UE initiates a connection reconstruction process and considers resource #4 invalid; and / or, the UE starts timer #3 and considers resource #4 invalid during the operation of timer #3; and / or, the UE performs cell selection or cell reselection and considers resource #4 invalid.

[0541] It should be noted that the resource #4 corresponding to "resource #4 invalid" can be configured through the two implementation methods in step S901, or it can be configured through other methods. This application embodiment does not limit it.

[0542] For example, when resource #4 is configured using implementation method 2 (the duration of resource #4's effectiveness is maintained by timers #2 and #1), the "resource #4 invalid" can include the following two implementation methods:

[0543] (1) Sub-implementation method #1: Timer #2.1 times out or stops when the UE initiates the connection reconstruction process.

[0544] For example, the UE initiates a connection reconstruction process, deeming timer #2.1 to have timed out or stopped, or stops timer #2.1, and deems resource #4 invalid.

[0545] For example, the UE starts timer #3, considers timer #2.1 to have timed out or stopped, or stops timer #2.1 and considers resource #4 invalid.

[0546] For example, when the UE performs cell selection or cell reselection, it considers that timer #2.1 has timed out or stopped, or stops timer #2.1 and considers resource #4 invalid.

[0547] (2) Sub-implementation method #2: Timer #2.1 continues to run during the connection reconstruction process initiated by the UE.

[0548] For example, when the UE initiates a connection reconstruction process, timer #2.1 continues to run and considers resource #4 invalid.

[0549] For example, the UE starts timer #3, timer #2.1 continues to run, and considers resource #4 invalid.

[0550] For example, when the UE performs cell selection or cell reselection, timer #2.1 continues to run and resource #4 is considered invalid.

[0551] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0552] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#6 in Figure 9), then optionally, method 900 further includes step S903: the UE sends request message #1.

[0553] Specifically, at time T2#6, the UE sends request message #1 through the selected cell (appropriate cell) and waits to receive response message #1 from the network device. During this process, resource #4 remains invalid.

[0554] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0555] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0556] Optionally, the UE may send a request message #1 to network device #3. Network device #3 may be the same as network device #2, or it may be different from network device #2. Specifically, the UE may send the request message #1 to network device #3 through the appropriate cell.

[0557] It should be noted that the suitable cell may be the target cell, or it may be a non-target cell (a cell other than the target cell).

[0558] For example, when the suitable cell is the target cell, network device #3 is the same as network device #2.

[0559] For example, if the suitable cell is not the target cell, network device #3 can be the same as network device #2 (e.g., the target cell and the suitable cell are different cells of the same network device), or network device #3 can be different from network device #2 (e.g., the target cell and the suitable cell are different cells of different network devices).

[0560] It should be understood that network device #3 can be the same as network device #1 (e.g., the suitable cell is the cell of network device #1 (e.g., cell #1 or other cells)); network device #3 can also be different from network device #1 (e.g., the suitable cell is not the cell of network device #1).

[0561] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), invalidating resource #4 also includes:

[0562] (1) If the cell selected by the UE is the target cell, the UE continues to reserve resource #4.

[0563] In other words, in this case, the invalidity of resource #4 can be understood as the UE suspending the use of resource #4, but not releasing resource #4.

[0564] For example, if resource #4 is configured by implementation method 1, invalid resource #4 can be understood as the UE suspending the use of resource #4, but not releasing resource #4.

[0565] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), and if step S902 is implemented based on sub-implementation method #1, and in S902, timer #2.1 times out or stops, then "reserving resource #4" can be understood as timer #2.1 still being in the state of timeout or stopped when the UE sends request message #1.

[0566] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), and if step S902 is implemented based on sub-implementation method #2, that is, in S902, timer #2.1 continues to run, then "reserving resource #4" can be understood as timer #2.1 continuing to run, but not using resource #4.

[0567] (2) If the cell selected by the UE is not the target cell, the UE releases resource #4.

[0568] For example, if resource #4 is configured in implementation method 1, and the cell selected by the UE is not the target cell, the UE releases resource #4.

[0569] For example, if resource #4 is configured by implementation method 2 (the effective duration of resource #4 is maintained by timer #2.1), and if step S902 is implemented based on sub-implementation method #1, and in S902, timer #2.1 times out or stops, then "releasing resource #4" can be understood as timer #2.1 still being in the state of timeout or stopped when the UE sends request message #1.

[0570] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), and if step S902 is implemented based on sub-implementation method #2, that is, in S902, timer #2.1 continues to run, then "releasing resource #4" may also include: the UE releases resource #4 and considers timer #2.1 to have timed out or stopped, or the UE releases resource #4 and stops timer #2.1.

[0571] It should be understood that S903 can also be interpreted as follows: The UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE stops timer #3. Furthermore, the UE can confirm whether the selected cell is the target cell. If it is the target cell, the UE continues to reserve resources #4; if it is not the target cell, the UE releases resources #4. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending the first request message, the UE confirms whether the selected cell is the target cell. If it is the target cell, the UE continues to reserve resources #4; if it is not the target cell, the UE releases resources #4.

[0572] Optionally, the UE can start timer #4 at time T2#6 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0573] It should be understood that S903 can also be understood as: the UE sends a request message #1 and considers resource #4 invalid; and / or, the UE starts timer #4 and considers resource #4 invalid during the execution of timer #4; and / or, the UE considers resource #4 invalid while waiting to receive response message #1 sent by the network device.

[0574] Optionally, S903 can also be understood as: when the UE stops timer #3, and / or the UE selects a suitable cell, and / or the UE sends a request message #1, and / or the UE starts timer #4, if the selected cell is the target cell, the UE continues to retain resources #4; if the selected cell is not the target cell, the UE releases resources #4.

[0575] It should be noted that regardless of whether the UE selects the target cell or a non-target cell, if resource #4 has already been deemed invalid in step S902, then when and / or after the UE sends request message #1, resource #4 can continue to be deemed invalid. That is, the description of "resource #4 remains invalid" in step S903 is used to indicate that resource #4 is still unavailable to the UE. Therefore, the UE simply continues the state of resource #4 being invalid in step S902, and there is no need to further define the behavior of the UE considering "resource #4 to be invalid".

[0576] For example, when and / or after sending request message #1, the UE continues to consider resource #4 invalid until the UE receives response message #1 from the network device.

[0577] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0578] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#6 in Figure 9), then optionally, method 900 further includes step S904: the UE uses resource #4.

[0579] Optionally, using resource #4 can be understood as resource #4 being valid, or the UE being able to use resource #4 to perform service #1.

[0580] It should be noted that the execution of step S904 is based on the condition that the cell selected by the UE in step S903 is the target cell. That is, after the UE initiates RRC connection reconstruction, the UE may choose the target cell or a non-target cell for RRC connection reconstruction. If the UE successfully reconstructs the connection in the target cell, it can use the resource #4 corresponding to the target cell.

[0581] In one possible implementation, the UE can directly use resource #4 if the above conditions are met. For example, if the UE successfully rebuilds at the target location, the UE can directly use resource #4.

[0582] In another possible implementation, the UE can use resource #4 at the instruction of the network device (or at the enablement of the network device). For example, the network device can send information #1 to the UE, and the UE can receive information #1 sent by the network device.

[0583] Optionally, the information #1 may indicate one or more of the following: the UE uses resource #4 corresponding to the target cell; the UE successfully rebuilds in the target cell and uses resource #4 corresponding to the target cell, etc.

[0584] Optionally, the method of carrying the information #1 may include one or more of the following:

[0585] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1.

[0586] In one possible implementation, the RRC reconfiguration message is sent by network device #1. For example, before step S901, when the UE is in RRC connected state, network device #1 can send an RRC reconfiguration message to the UE, the RRC reconfiguration message including information #1. Alternatively, network device #1 sends information #1 via handover information #1.

[0587] In another possible implementation, the RRC reconfiguration message is sent by network device #2.

[0588] Optionally, network device #1 or network device #2 may also simultaneously send the resource configuration of service #1 (e.g., configuration information of resource #4 (e.g., messages #1 and #3 in step S901)) and information #1 to the UE.

[0589] Optionally, message #1 and information #1 can be two different messages, or they can be carried in the same RRC reconfiguration message.

[0590] It should be understood that the content of the RRC reconfiguration message can be found in the relevant descriptions in the current technology, and will not be repeated here in the embodiments of this application.

[0591] In this case, information #1 can be UE-level, meaning that network device #1 can send the corresponding information #1 to each UE.

[0592] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1.

[0593] In one possible implementation, the cell system information is sent by network device #1.

[0594] In another possible implementation, the cell system information is sent by network device #2.

[0595] For example, network device #1 can send information #1 to all (or some) UEs under its coverage through system information; or, network device #1 can send information #1 to all (or some) UEs with which it has established a connection through system information.

[0596] For example, network device #2 sends information #1 to all (or some) UEs covered by the target cell through system information; or, network device #2 sends information #1 to all (or some) UEs that have established a connection with network device #2 through the target cell through system information.

[0597] It should be understood that the content of the cell system information can be referred to the relevant descriptions in the current technology, and will not be repeated here in the embodiments of this application.

[0598] In this case, information #1 can be at the cell or base station granularity.

[0599] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1.

[0600] In this situation, network device #2 can instruct the UE whether it can use resource #4 when the UE successfully rebuilds the target cell.

[0601] It should be noted that the above three methods of carrying information #1 are not limited to the resource #4 configured based on implementation method 1 and implementation method 2 in step S901, but can also be applied to the resource #4 configured based on other methods. This application embodiment does not limit this.

[0602] Furthermore, if in step S901 resource #4 is configured using implementation method 2 (the duration of resource #4's effectiveness is maintained by timers #2 and #1), and if steps S902 and S903 are implemented based on sub-implementation method #2, i.e., timer #2.1 continues to run in step S902, then step S904 can also be understood as follows: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether resource #4 can be used based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0603] Optionally, after the UE successfully rebuilds the target cell (i.e., the UE establishes a connection with network device #2 through the target cell), network device #2 can also send message #2 to the UE. Message #2 is used to configure resource #5, through which the UE can execute service #1. Resource #5 can be the same as or different from resource #4.

[0604] For example, message #2 can be an RRC reconfiguration message. After successful reconstruction, network device #2 can send message #2 via the RRC reconfiguration message. Therefore, after receiving message #2, the UE can use resource #5 to perform service #1.

[0605] Optionally, if the UE does not receive message #2 from network device #2 after the target cell is successfully rebuilt (for example, the RRC reconfiguration message sent by network device #2 to the UE after the successful reconstruction does not include message #2), the UE can continue to use resource #4 to perform service #1.

[0606] In other words, the UE can determine whether to continue using resource #4 to execute service #1 based on whether there is a new resource configuration for executing service #1.

[0607] It should be noted that the specific configuration method of resource #5 and the specific content of message #2 can be referred to the relevant description of resource #4 and message #1 in step S901. Network device #1, resource #4 and message #1 can be replaced with network device #2, resource #2 and message #2 respectively. This application embodiment will not be described in detail here.

[0608] If the cell selected by the UE is a non-target cell (i.e. step S904 is not executed), then after the UE establishes a connection with the network device #3 through the non-target cell, the network device #3 sends message #3 (e.g., RRC reconfiguration message) to the UE. Message #3 is used to configure resource #6, so that after the UE receives message #3, it can use resource #6 to perform service #1.

[0609] It should be noted that the specific configuration method of resource #6 and the specific content of message #3 can be referred to the relevant description of resource #4 and message #1 in step S901. Network device #1, resource #4 and message #1 can be replaced with network device #3, resource #6 and message #3 respectively. This application embodiment will not be described in detail here.

[0610] It should be noted that in method 900, the UE can use resource #4 when establishing a connection through the target cell, avoiding the need for the UE to wait for the RRC reconfiguration instruction after re-establishing the connection before configuring the corresponding resources to execute service #1. This reduces the impact of cell handover or RRC reconstruction on service #1, and improves the flexibility of resource usage while ensuring service transmission.

[0611] In another possible implementation, if the UE is unaware of the information for resource #4 (for example, in step S901, the target cell resource (resource #4) was not configured for the UE via message #1; or the handover information #1 does not include information for resource #4; or resource #4 is configured, but resource #4 cannot cover resource #1), then the UE can continue to use resource #1 for a period of time during subsequent processing (i.e., use the original cell's resources to perform service #1). For example, if the selected cell is the original cell, the UE retains resource #1 and resource #1 is invalid. If the UE successfully rebuilds in the original cell, then the UE can use resource #1 in step S904. For details, refer to the descriptions of S902-S904 above; simply replace the target cell with the original cell, replace the non-target cell with a non-original cell (or a new cell), and replace resource #4 with resource #1. This application will not elaborate further here.

[0612] Figure 10 is a schematic diagram of a communication method 1000 applicable to an embodiment of this application.

[0613] It should be understood that method 1000 can be applied to the UE (or, a unit within the UE, such as a chip) and network device #1, network device #2, and / or network device #3 (or, a unit within network device #1, network device #2, and / or network device #3, such as a chip). It should be noted that method 1000 can be considered a specific implementation of mode E in method 500.

[0614] S1001: The UE has received handover information #1.

[0615] Specifically, the UE receives handover information #1 at time T0#7 and performs handover based on handover information #1. Handover information #1 is used to instruct the UE to handover to the target cell.

[0616] For example, the UE can start timer #5 at time T0#7 (timer #5 can be T304) and perform handover during the execution of timer #5 (e.g., handover to the target cell, or initiate random access in the target cell).

[0617] It should be noted that the specific content of step S1001 can be found in the description of step S901 in method 900, simply by replacing "T0#6" with "T0#7". This embodiment will not elaborate further. Resource #4 is a resource of the target cell (or target station, i.e., network device #2) (for example, it can be a resource dedicated to performing service #1, or it can be a resource capable of performing multiple services (including service #1)).

[0618] If the handover is successful (i.e., successful access to the target cell) during the operation of timer #5, for example, if the UE establishes an RRC connection with network device #2 through the target cell, then the UE can use resource #4 (resource #4 is valid) after successfully accessing the cell.

[0619] If the handover fails during the operation of timer #5, method 1000 may optionally include step S1002: the UE initiates a connection reconstruction process.

[0620] Specifically, the UE initiates a connection re-establishment process at time T1#7. During this process, the UE can perform cell selection or cell reselection. Resource #4 is invalid during the connection re-establishment process.

[0621] Optionally, time T1#7 can be the time when timer #5 times out.

[0622] Optionally, the UE can start timer #3 at time T1#7 (timer #3 can be T311, which will not be elaborated here). Thus, the UE can perform cell selection or cell reselection during the operation of timer #3.

[0623] It should be noted that the specific content of step S1002 can be referred to the relevant description of step S902 in method 900, and "T1#6" can be replaced with "T1#7" accordingly. The embodiments of this application will not be described in detail here.

[0624] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0625] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#7 in Figure 10), then optionally, method 1000 further includes step S1003: the UE sends request message #1.

[0626] Specifically, at time T2#7, the UE sends a request message #1 through the selected cell (the appropriate cell) and waits to receive a response message #1 from the network device.

[0627] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0628] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0629] Optionally, the UE may send a request message #1 to network device #3. Network device #3 may be the same as network device #2, or it may be different from network device #2. Specifically, the UE may send the request message #1 to network device #3 through the appropriate cell.

[0630] It should be noted that the suitable cell may be the target cell, or it may be a non-target cell (a cell other than the target cell).

[0631] For example, when the suitable cell is the target cell, network device #3 is the same as network device #2.

[0632] For example, if the suitable cell is not the target cell, network device #3 can be the same as network device #2 (e.g., the target cell and the suitable cell are different cells of the same network device), or network device #3 can be different from network device #2 (e.g., the target cell and the suitable cell are different cells of different network devices).

[0633] It should be understood that network device #3 can be the same as network device #1 (e.g., the suitable cell is the cell of network device #1 (e.g., cell #1 or other cells)); network device #3 can also be different from network device #1 (e.g., the suitable cell is not the cell of network device #1).

[0634] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), the UE's processing of resource #4 includes the following two cases:

[0635] (1) If the cell selected by the UE is the target cell, the UE uses resource #4.

[0636] In other words, if the cell selected by the UE is the target cell, the UE can resume using resource #4 at the same time as sending request message #1 (i.e., at time T2#7).

[0637] Optionally, restoring the use of resource #4 can be understood as resource #4 being valid, or the UE being able to use resource #4 to perform service #1.

[0638] In this situation, the UE has a high probability of successfully rebuilding in the target cell, so the UE can use resource #4 first.

[0639] (2) If the cell selected by the UE is not the target cell, the UE releases resource #4.

[0640] For example, if resource #4 is configured in implementation method 1, and the cell selected by the UE is not the target cell, the UE releases resource #4.

[0641] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), and if step S1002 is implemented based on sub-implementation method #1, and in S1002, timer #2.1 times out or stops, then "releasing resource #4" can be understood as timer #2.1 still being in the state of timeout or stopped when the UE sends request message #1.

[0642] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), and if step S1002 is implemented based on sub-implementation method #2, that is, in S1002, timer #2.1 continues to run, then the "release resource #4" may also include: the UE releases resource #4 and considers timer #2.1 to have timed out or stopped, or the UE releases resource #4 and stops timer #2.1.

[0643] It should be understood that S1003 can also be interpreted as follows: The UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE stops timer #3. Furthermore, the UE can confirm whether the selected cell is the target cell. If it is the target cell, the UE uses resource #4; if it is not the target cell, the UE releases resource #4. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending request message #1, if the selected cell is the target cell, the UE uses resource #4; if the selected cell is not the target cell, the UE releases resource #4.

[0644] Optionally, the UE can start timer #4 at time T2#7 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0645] It should be understood that S1003 can also be understood as follows: if the selected cell is the target cell, the UE sends a request message #1 and uses resource #4; and / or, if the selected cell is the target cell, the UE starts timer #4 and uses resource #4 during the execution of timer #4; and / or, if the selected cell is the target cell, the UE uses resource #4 while waiting to receive the response message #1 sent by the network device.

[0646] Optionally, S1003 can also be understood as: when the UE stops timer #3, and / or when the UE selects a suitable cell, and / or when the UE sends a request message #1, and / or when the UE starts timer #4, if the selected cell is the target cell, the UE resumes using resource #4; if the selected cell is not the target cell, the UE releases resource #4.

[0647] In one possible implementation, the UE can directly use resource #4 if the above conditions are met. For example, if the cell selected by the UE is the original cell, the UE can directly resume using resource #4.

[0648] In another possible implementation, the UE may use resource #4 at the instruction of the network device (or at the enablement of the network device).

[0649] For example, a network device can send information #1 to a UE, and the UE can receive information #1 sent by the network device.

[0650] Optionally, the information #1 may indicate one or more of the following: the UE uses resource #4 corresponding to the target cell; the UE successfully rebuilds in the target cell and uses resource #4 corresponding to the target cell, etc.

[0651] Optionally, the method of carrying the information #1 may include one or more of the following:

[0652] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1.

[0653] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1.

[0654] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1.

[0655] It should be noted that for the specific details of the above-mentioned bearing methods (1)-(3), please refer to the relevant description of the three bearing methods in step S904 of method 900 above. This application embodiment will not repeat the details here.

[0656] It should be noted that the above three methods of carrying information #1 are not limited to the resource #4 configured based on implementation method 1 and implementation method 2 in step S1001, but can also be applied to the resource #4 configured based on other methods. This application embodiment does not limit this.

[0657] Furthermore, if in step S1001 resource #4 is configured by implementation method 2 (the duration of resource #4's effectiveness is maintained by timers #2 and #1), and if step S1002 is implemented based on sub-implementation method #2, i.e., timer #2.1 continues to run in step S1002, then step S1003 can also be understood as: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether resource #4 can be restored based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0658] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0659] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#7 in Figure 10), then optionally, method 1000 further includes step S1004: the UE successfully rebuilds in the target cell.

[0660] It should be noted that the execution of step S1004 is based on the condition that the cell selected by the UE in step S1003 is the target cell. That is, after the UE initiates RRC connection reconstruction, the UE may select the target cell for RRC connection reconstruction or may select a non-target cell for RRC connection reconstruction.

[0661] Optionally, if the UE successfully rebuilds in the target cell, it can continue to use resource #4 corresponding to the target cell (to perform service #1). That is, if the UE receives response message #1 sent by network device #2, the UE can continue to use resource #4 to perform service #1. In other words, the content indicated by information #1 can also be understood as: the UE can start using resource #4 from the moment it selects the target cell (and / or starts timer #4; and / or sends request message #1 in the target cell; and / or stops timer #3) until network device #2 issues a new command, or until the UE fails to rebuild.

[0662] Optionally, after the UE successfully rebuilds the target cell (i.e., the UE establishes a connection with network device #2 through the target cell), network device #2 can also send message #2 to the UE. Message #2 is used to configure resource #5, through which the UE can execute service #1. Resource #5 can be the same as or different from resource #4.

[0663] It should be understood that the specific content of message #2 can be referred to the relevant description of message #2 in step S904 of method 900, and will not be repeated here in the embodiments of this application.

[0664] If the cell selected by the UE is not the target cell (i.e., step S1004 is not executed), then after the UE establishes a connection with network device #3 through the non-target cell, network device #3 sends message #3 (e.g., an RRC reconfiguration message) to the UE. Message #3 is used to configure resource #6, so that after receiving message #3, the UE can use resource #6 to perform service #1. For details, please refer to the relevant content of step S904 in method 900, which will not be repeated here in this embodiment.

[0665] It should be noted that in method 1000, the UE can use resource #4 when selecting the target cell, so that the UE can execute service #1 before establishing a connection through the target cell, reducing the impact of cell handover or RRC reconstruction on service #1, and improving the flexibility of resource usage while ensuring service transmission.

[0666] In another possible implementation, if the UE is unaware of the information for resource #4 (for example, in step S1001, the target cell resource (resource #4) was not configured for the UE via message #1; or the handover information #1 does not include information for resource #4; or resource #4 is configured, but resource #4 cannot cover resource #1), then the UE can continue to use resource #1 for a period of time during subsequent processing (i.e., use the original cell's resources to perform service #1). For example, if the selected cell is the original cell, the UE can use resource #1 in step S1003. For details, refer to the descriptions in S1002-S1004 above; simply replace the target cell with the original cell, replace the non-target cell with a non-original cell (or a new cell), and replace resource #4 with resource #1. This application will not elaborate further here.

[0667] Figure 11 is a schematic diagram of a communication method 1100 applicable to an embodiment of this application.

[0668] It should be understood that method 1100 can be applied to the UE (or, a unit within the UE, such as a chip) and network device #1, network device #2, and / or network device #3 (or, a unit within network device #1, network device #2, and / or network device #3, such as a chip). It should be noted that method 1100 can be considered a specific implementation of mode D in method 500.

[0669] S1101: The UE received handover information #1.

[0670] Specifically, the UE receives handover information #1 at time T0#8 and performs handover based on handover information #1. Handover information #1 is used to instruct the UE to handover to the target cell.

[0671] For example, the UE can start timer #5 at time T0#8 (timer #5 can be T304) and perform handover during the execution of timer #5 (e.g., handover to the target cell, or initiate random access in the target cell).

[0672] It should be noted that the specific content of step S1101 can be found in the description of step S901 in method 900, by simply replacing "T0#6" with "T0#8". This embodiment will not elaborate further. Resource #4 is a resource of the target cell (or target station, i.e., network device #2) (for example, it can be a resource dedicated to performing service #1, or it can be a resource capable of performing multiple services (including service #1)).

[0673] If the handover is successful (i.e., successful access to the target cell) during the operation of timer #5, for example, if the UE establishes an RRC connection with network device #2 through the target cell, the UE can use resource #4 (resource #4 is valid) after successfully accessing the cell.

[0674] If the handover fails during the operation of timer #5, method 1100 may optionally include step S1102: the UE initiates a connection reconstruction process.

[0675] Specifically, the UE initiates a connection re-establishment process at time T1#8. During this process, the UE can perform cell selection or cell reselection. Resource #4 is used during the connection re-establishment process.

[0676] It should be noted that using resource #4 can be understood as resource #4 being valid, or the UE being able to use resource #4 to perform service #1.

[0677] Optionally, time T1#8 can be the time when timer #5 times out.

[0678] Optionally, the UE can start timer #3 at time T1#8 (timer #3 can be T311, which will not be elaborated here). Thus, the UE can perform cell selection or cell reselection during the operation of timer #3.

[0679] Optionally, S1102 can also be understood as: the UE initiates a connection reconstruction process and uses resource #4; and / or, the UE starts timer #3 and uses resource #4 during the operation of timer #3; and / or, the UE performs cell selection or cell reselection and uses resource #4 to recover.

[0680] It should be noted that the resource #4 corresponding to "using resource #4" can be configured through the two implementation methods in step S1101, which will not be elaborated here; or it can be configured through other methods, which will not be limited in the embodiments of this application.

[0681] In one possible implementation, the UE can directly use resource #4 if the above conditions are met. For example, if the UE initiates a connection re-establishment process (and / or starts timer #3; and / or performs cell selection or cell reselection), the UE can directly use resource #4.

[0682] In another possible implementation, the UE may use resource #4 at the instruction of the network device (or at the enablement of the network device).

[0683] For example, a network device can send information #1 to a UE, and the UE can receive information #1 sent by the network device.

[0684] Optionally, the information #1 may indicate one or more of the following: the UE uses resource #4 corresponding to the target cell; the UE uses resource #4 corresponding to the target cell when initiating a reconstruction process; the UE uses resource #4 corresponding to the target cell when starting timer #3; the UE uses resource #4 corresponding to the target cell when performing cell reselection or cell selection, etc.

[0685] Optionally, the method of carrying the information #1 may include one or more of the following:

[0686] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1.

[0687] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1.

[0688] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1.

[0689] It should be noted that for the specific details of the above-mentioned bearing methods (1)-(3), please refer to the relevant description of the three bearing methods in step S904 of method 900 above. This application embodiment will not repeat the details here.

[0690] It should be noted that the above three methods of carrying information #1 are not limited to the resource #4 configured based on implementation method 1 and implementation method 2 in step S1101, but can also be applied to the resource #4 configured based on other methods. This application embodiment does not limit this.

[0691] Furthermore, if in step S1101 resource #4 is configured by implementation method 2 (the duration of resource #4's effectiveness is maintained by timer #2.1), and if step S1102 is implemented based on sub-implementation method #2, i.e., timer #2.1 continues to run in step S1102, then step S1103 can also be understood as: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether resource #4 can be restored based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0692] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0693] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#8 in Figure 11), then optionally, method 1100 further includes step S1103: the UE sends request message #1.

[0694] Specifically, the UE sends a request message #1 at time T2#8 and waits to receive a response message #1 from network device #2.

[0695] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0696] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0697] Optionally, the UE may send a request message #1 to network device #3. Network device #3 may be the same as network device #2, or it may be different from network device #2. Specifically, the UE may send the request message #1 to network device #3 through the appropriate cell.

[0698] It should be noted that the suitable cell may be the target cell, or it may be a non-target cell (a cell other than the target cell).

[0699] For example, when the suitable cell is the target cell, network device #3 is the same as network device #2.

[0700] For example, if the suitable cell is not the target cell, network device #3 can be the same as network device #2 (e.g., the target cell and the suitable cell are different cells of the same network device), or network device #3 can be different from network device #2 (e.g., the target cell and the suitable cell are different cells of different network devices).

[0701] It should be understood that network device #3 can be the same as network device #1 (e.g., the suitable cell is the cell of network device #1 (e.g., cell #1 or other cells)); network device #3 can also be different from network device #1 (e.g., the suitable cell is not the cell of network device #1).

[0702] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), the UE's processing of resource #4 includes the following two cases:

[0703] (1) If the cell selected by the UE is the target cell, the UE continues to use resource #4.

[0704] It is understandable that, in step S1102, although the UE is selecting a cell (i.e., the UE has not determined the selected cell), the UE has not stopped using resource #4 (for example, the UE continues to use resource #4 to perform service #1). Therefore, at time T2#8, since the UE has still selected the target cell, the UE can continue to maintain its previous behavior (i.e., continue to use resource #4).

[0705] In other words, the content indicated by information #1 can also be understood as: the UE can start using resource #4 from the beginning of the connection reconstruction process (and / or, start timer #3; and / or, perform cell selection or cell reselection) until the network device #2 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell.

[0706] (2) If the cell selected by the UE is not the target cell, the UE releases resource #4.

[0707] For example, if resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), in step S1102, if timer #2.1 continues to run, then "releasing resource #4" may also include: the UE releasing resource #4 and considering that timer #2.1 has timed out or stopped, or the UE releasing resource #4 and stopping timer #2.1.

[0708] It should be understood that S1103 can also be interpreted as follows: During the operation of timer #3, the UE can select a suitable cell. If the UE selects a suitable cell and the suitable cell is the target cell, the UE continues to use resource #4. If the suitable cell is not the target cell, the UE releases resource #4. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending request message #1, if the selected cell is the target cell, the UE continues to use resource #4. If the selected cell is not the target cell, the UE releases resource #4.

[0709] Similarly, if resource #4 in step S1101 is configured by implementation method 2 (the duration of resource #4's effectiveness is maintained by timers #2 and #1), then step S1103 can also be understood as: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether resource #4 can be used based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0710] Optionally, the UE can start timer #4 at time T2#8 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0711] Optionally, S1103 can also be understood as: during the operation of timer #4 (or when timer #4 is started), if the cell selected by the UE is the target cell, resource #4 is valid (the UE can continue to use resource #4).

[0712] Optionally, S1103 can also be understood as: when the UE stops timer #3, and / or the UE selects a suitable cell, and / or the UE sends a request message #1, and / or the UE starts timer #4, if the selected cell is the target cell, the UE continues to use resource #4; if the selected cell is not the target cell, the UE releases resource #4.

[0713] It should be noted that since resource #4 has been deemed valid in step S1102, the description of "continue to use resource #4 (or resource #4 remains valid)" in step S1103 is used to indicate that resource #4 is still available to the UE. Therefore, the UE simply continues the state of resource #4 being valid in step S1102, and there is no need to further define the behavior of the UE considering "resource #4 to be valid (or continue to use resource #4)".

[0714] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0715] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#8 in Figure 11), then optionally, method 1100 further includes step S1104: the UE successfully rebuilds in the target cell.

[0716] It should be noted that the execution of step S1104 is based on the condition that the cell selected by the UE in step S1103 is the target cell. That is, after initiating RRC connection reconstruction, the UE may choose the target cell or a non-target cell for RRC connection reconstruction. Regardless of whether the selected cell is the target cell, the UE can use resource #4 to perform service #1 after initiating RRC connection reconstruction. If the selected cell is the target cell, the UE can continue to use resource #4 until the network device #2 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell.

[0717] Optionally, after the UE successfully rebuilds the target cell (i.e., the UE establishes a connection with network device #2 through the target cell), network device #2 can also send message #2 to the UE. Message #2 is used to configure resource #5, through which the UE can execute service #1. Resource #5 can be the same as or different from resource #4.

[0718] It should be understood that the specific content of message #2 can be referred to the relevant description of message #2 in step S904 of method 900, and will not be repeated here in the embodiments of this application.

[0719] If the cell selected by the UE is not the target cell (i.e., step S1104 is not executed), then after the UE establishes a connection with network device #3 through the non-target cell, network device #3 sends message #3 (e.g., an RRC reconfiguration message) to the UE. Message #3 is used to configure resource #6, so that after receiving message #3, the UE can use resource #6 to perform service #1. For details, please refer to the relevant content of step S904 in method 900, which will not be repeated here in this embodiment.

[0720] It should be noted that in method 1100, the UE can use resource #4 when initiating the RRC connection re-establishment process. That is, if the UE eventually establishes a connection through the target cell during cell handover or after a handover failure, the UE can use resource #4 after initiating the RRC connection re-establishment until the network device issues a new command, or until the re-establishment fails. If the UE does not select a target cell, it can also use resource #4 between initiating the connection re-establishment and selecting a cell. This avoids the inability to execute service #1 during handover or RRC re-establishment, improving the flexibility of resource usage while ensuring service transmission.

[0721] In another possible implementation, if the UE is unaware of the information for resource #4 (for example, in step S1101, the target cell resource (resource #4) that the UE can use was not configured via message #1; or the handover information #1 does not include information for resource #4; or resource #4 is configured, but resource #4 cannot cover resource #1), then the UE can continue to use resource #1 for a period of time during subsequent processing (i.e., use the original cell's resources to perform service #1). For example, during the connection reconstruction process, the UE can use resource #1 in step S1102. For details, refer to the descriptions of S1102-S1104 above; simply replace the target cell with the original cell, replace the non-target cell with a non-original cell (or a new cell), and replace resource #4 with resource #1. This application will not elaborate further here.

[0722] Figure 12 is a schematic diagram of a communication method 1200 applicable to an embodiment of this application.

[0723] It should be understood that method 1200 can be applied to the UE (or, a unit within the UE, such as a chip) and network devices #1, #2, and / or #3 (or, a unit within network devices #1, #2, and / or #3, such as a chip). It should be noted that method 1200 can be considered a specific implementation of mode G in method 500.

[0724] S1201: The UE received handover information #1.

[0725] Specifically, the UE receives handover information #1 at time T0#9 and performs a handover based on handover information #1. Handover information #1 instructs the UE to handover to the target cell. Additionally, upon receiving handover information #1, resource #4 is used. Resource #4 is a resource of the target cell (or target station, i.e., network device #2) (for example, it can be a resource dedicated to performing service #1, or it can be a resource capable of performing multiple services (including service #1)).

[0726] It should be noted that using resource #4 can be understood as resource #4 being valid, or the UE being able to use resource #4 to perform service #1.

[0727] Optionally, before step S1201, the UE is in RRC connection state (i.e., the UE establishes an RRC connection with network device #1). Therefore, when the UE in RRC connection state receives handover information #1 (e.g., an RRC reconfiguration message carrying reconfigurationWithSync (RRCReconfiguration message)) (corresponding to time T0#9), the UE can perform a handover.

[0728] For example, the UE can start timer #5 at time T0#9 (e.g., timer #5 can be T304 in the current technology) and perform handover during the execution of timer #5 (e.g., handover to the target cell, or initiating random access in the target cell). When timer #5 is started, resource #4 is used.

[0729] It should be noted that the specific content of step S1201 (e.g., the configuration method of resource #1 (implementation method 1, implementation method 2), the configuration method of resource #4 (implementation method 1, implementation method 2), the relevant content of switching information #1, the release of resource #1, etc.) can also be referred to the relevant description of step S901 in method 900, and "T0#6" can be replaced with "T0#9" accordingly. This application embodiment will not be described in detail here.

[0730] Optionally, before step S1201, the UE in RRC connected state can execute service #1. Optionally, if service #1 is an AIoT service, the UE can act as a reader to execute the AIoT service. For details regarding the UE's ability to execute service #1 in step S1201, please refer to the relevant description of step S901 in method 900; this embodiment will not be repeated here.

[0731] Optionally, S1201 can also be understood as: when the UE receives handover information #1, and / or when the UE starts timer #5, and / or when the UE performs cell handover, resource #4 is used.

[0732] It should be noted that the resource #4 corresponding to “using resource #4” can be configured through the two implementation methods in step S1201 (refer to S901), which will not be elaborated here; or, it can be configured through other methods, which will not be limited in the embodiments of this application.

[0733] In one possible implementation, the UE can directly use resource #4 if the above conditions are met. For example, if the UE receives handover information #1 (and / or starts timer #5, and / or performs cell handover), the UE can directly use resource #4.

[0734] In another possible implementation, the UE may use resource #4 at the instruction of the network device (or at the enablement of the network device).

[0735] For example, a network device can send information #1 to a UE, and the UE can receive information #1 sent by the network device.

[0736] Optionally, the information #1 may indicate one or more of the following: the UE uses the resource #4 corresponding to the target cell; the UE uses the resource #4 corresponding to the target cell when it receives the handover information #1; the UE uses the resource #4 corresponding to the target cell when it starts the timer #5; the UE uses the resource #4 corresponding to the target cell when it performs a cell handover, etc.

[0737] Optionally, the method of carrying the information #1 may include one or more of the following:

[0738] (1) Message #1 can be carried in an RRC reconfiguration message, that is, an RRC reconfiguration message can include message #1.

[0739] (2) Information #1 can be carried in the cell system information, that is, the cell system information can include information #1.

[0740] (3) Information #1 can be carried in response message #1, that is, response message #1 can include information #1.

[0741] It should be noted that for the specific details of the above-mentioned bearing methods (1)-(3), please refer to the relevant description of the three bearing methods in step S904 of method 900 above. This application embodiment will not repeat the details here.

[0742] It should be noted that the above three methods of carrying information #1 are not limited to the resource #4 configured based on implementation method 1 and implementation method 2 in step S1201, but can also be applied to the resource #4 configured based on other methods. This application embodiment does not limit this.

[0743] Furthermore, if resource #4 in step S1201 is configured using implementation method 2 (the duration of resource #4's effectiveness is maintained by timer #2.1), then step S1201 can also be understood as follows: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether resource #4 can be used based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0744] If the UE successfully hands over (i.e. successfully accesses the target cell) during the operation of timer #5, for example, if the UE establishes an RRC connection with network device #2 through the target cell, then after successfully accessing the cell, the UE can continue to use resource #4 (resource #4 is valid).

[0745] If the UE fails to switch successfully during the operation of timer #5, the method 1200 may optionally include step S1202: the UE initiates a connection reconstruction process.

[0746] Specifically, the UE initiates a connection re-establishment process at time T1#9. During this process, the UE can perform cell selection or cell reselection. Resource #4 continues to be used during the connection re-establishment process.

[0747] Optionally, time T1#9 can be the time when timer #5 times out.

[0748] Optionally, the UE can start timer #3 at time T1#9 (timer #3 can be T311, which will not be elaborated here). Thus, the UE can perform cell selection or cell reselection during the operation of timer #3.

[0749] Optionally, S1202 can also be understood as: the UE initiates a connection reconstruction process and continues to use resource #4; and / or, the UE starts timer #3 and continues to use resource #4; and / or, the UE performs cell selection or cell reselection and continues to use resource #4.

[0750] In one possible implementation, if the UE fails to select a suitable cell during the execution of timer #3, the UE can enter the RRC idle state when timer #3 times out.

[0751] In another possible implementation, if the UE selects a suitable cell during the operation of timer #3 (e.g., time T2#9 in Figure 12), then optionally, method 1200 further includes step S1203: the UE sends request message #1.

[0752] Specifically, at time T2#9, the UE sends a request message #1 through the selected cell (suitable cell) and waits to receive a response message #1 sent by the network device #2.

[0753] Optionally, request message #1 can be an RRC reconstruction request message (e.g., an RRCReestablishmentRequest message).

[0754] Optionally, response message #1 can be an RRC reconstruction message (e.g., an RRCReestablishment message) or an RRC setup message (e.g., an RRCSetup message).

[0755] Optionally, the UE may send a request message #1 to network device #3. Network device #3 may be the same as network device #2, or it may be different from network device #2. Specifically, the UE may send the request message #1 to network device #3 through the appropriate cell.

[0756] It should be noted that the suitable cell may be the target cell, or it may be a non-target cell (a cell other than the target cell).

[0757] For example, when the suitable cell is the target cell, network device #3 is the same as network device #2.

[0758] For example, if the suitable cell is not the target cell, network device #3 can be the same as network device #2 (e.g., the target cell and the suitable cell are different cells of the same network device), or network device #3 can be different from network device #2 (e.g., the target cell and the suitable cell are different cells of different network devices).

[0759] It should be understood that network device #3 can be the same as network device #1 (e.g., the suitable cell is the cell of network device #1 (e.g., cell #1 or other cells)); network device #3 can also be different from network device #1 (e.g., the suitable cell is not the cell of network device #1).

[0760] Optionally, depending on the cell selected by the UE (i.e., the specific details of the suitable cell), the UE's processing of resource #4 includes the following two cases:

[0761] (1) If the cell selected by the UE is the target cell, the UE continues to use resource #4.

[0762] It is understandable that, since the UE can use resource #4 in steps S1201 and S1202, even though the UE is performing cell handover, cell selection and / or cell reselection (for example, the UE uses resource #4 to perform service #1), at time T2#9, since the UE has still selected the target cell, the UE can continue to maintain its previous behavior (i.e., continue to use resource #4).

[0763] In other words, the content indicated by information #1 can also be understood as: the UE can use resource #4 from the moment it receives handover information #1 (and / or, start timer #5; and / or, perform cell handover) until the network device #2 issues a new command, or until the UE fails to rebuild, or until the UE selects another cell.

[0764] (2) If the cell selected by the UE is not the target cell, the UE releases resource #4.

[0765] For example, if resource #4 is configured in implementation method 1, and the cell selected by the UE is not the target cell, the UE releases resource #4.

[0766] For example, when resource #4 is configured by implementation method 2 (the duration of resource #4 is maintained by timer #2.1), the "release resource #4" may also include: the UE releases resource #4 and considers timer #2.1 to have timed out or stopped, or the UE releases resource #4 and stops timer #2.1.

[0767] It should be understood that S1203 can also be interpreted as follows: During the operation of timer #3, the UE can select a suitable cell. If the UE selects a suitable cell and the suitable cell is the target cell, the UE continues to use resource #4. If the suitable cell is not the target cell, the UE releases resource #4. Alternatively, the UE can select a suitable cell during the operation of timer #3. If the UE selects a suitable cell, the UE sends a request message #1 through the selected cell. When sending request message #1, if the selected cell is the target cell, the UE continues to use resource #4. If the selected cell is not the target cell, the UE releases resource #4.

[0768] Optionally, if resource #4 in step S1201 is configured by implementation method 2 (the duration of resource #4's effectiveness is maintained by timer #2.1), step S1203 can also be understood as follows: the UE can determine whether resource #4 is available based on whether timer #2.1 is running; or, the UE can determine whether it can continue to use resource #4 based on whether timer #2.1 is running. For example, if timer #2.1 is running, the UE uses resource #4 (e.g., the UE uses resource #4 to perform service #1); if timer #2.1 is not running or has expired, the UE does not use resource #4 (e.g., the UE does not use resource #4 to perform service #1, or the UE does not perform service #1).

[0769] Optionally, the UE can start timer #4 at time T2#9 (timer #4 can be T301, which will not be elaborated here), and wait to receive response message #1 sent by the network device during the operation of timer #4.

[0770] Optionally, S1203 can also be understood as: when the UE stops timer #3, and / or the UE selects a suitable cell, and / or the UE sends a request message #1, and / or the UE starts timer #4, if the selected cell is the target cell, the UE continues to use resource #4; if the selected cell is not the target cell, the UE releases resource #4.

[0771] It should be noted that since resource #4 has been deemed valid in step S1201, the description of "continue to use resource #4" in steps S1202-S1203 is used to indicate that resource #4 is still available to the UE. Therefore, the UE simply continues the state of resource #4 being valid in step S1201, and there is no need to further define the behavior of the UE considering "resource #4 to be valid (or continue to use resource #4)".

[0772] In one possible implementation, if the UE does not receive the corresponding response message #1 during the execution of timer #4, the UE can enter the RRC idle state when timer #4 times out.

[0773] In another possible implementation, if the UE receives the corresponding response message #1 during the operation of timer #4 (for example, at time T3#9 in Figure 12), then optionally, method 1200 further includes step S1204: the UE successfully rebuilds in the target cell.

[0774] It should be noted that the execution of step S1204 is based on the condition that the cell selected by the UE in step S1203 is the target cell. That is, if the cell selected by the UE is the target cell, the UE can use the resource #4 (execute service #1) corresponding to the target cell from the start of cell handover. After the UE initiates RRC connection reconstruction, the UE may choose the target cell for RRC connection reconstruction or a non-target cell. If the selected cell is the target cell, the UE can continue to use resource #4 until the network device #2 issues a new command, or until the UE reconstruction fails, or until the UE selects another cell.

[0775] Optionally, after the UE successfully rebuilds the target cell (i.e., the UE establishes a connection with network device #2 through the target cell), network device #2 can also send message #2 to the UE. Message #2 is used to configure resource #5, through which the UE can execute service #1. Resource #5 can be the same as or different from resource #4.

[0776] It should be understood that the specific content of message #2 can be referred to the relevant description of message #2 in step S904 of method 900, and will not be repeated here in the embodiments of this application.

[0777] If the cell selected by the UE is not the target cell (i.e., step S1204 is not executed), then after the UE establishes a connection with network device #3 through the non-target cell, network device #3 sends message #3 (e.g., an RRC reconfiguration message) to the UE. Message #3 is used to configure resource #6, so that after receiving message #3, the UE can use resource #6 to perform service #1. For details, please refer to the relevant content of step S904 in method 900, which will not be repeated here in this embodiment.

[0778] It should be noted that in method 1200, the UE can use resource #4 upon receiving handover information #1. That is, during cell handover, the UE can use resource #4 after receiving handover information #1 until the network device issues a new command, until reconstruction fails, or until another cell is selected. If the UE does not select a target cell, it can also use resource #4 between receiving handover information #1 and selecting a cell. This avoids the inability to execute service #4 during handover or RRC reconstruction, improving resource utilization flexibility while ensuring service transmission.

[0779] In another possible implementation, if the UE is unaware of the information for resource #4 (e.g., in step S1201, the target cell resource (resource #4) was not configured for the UE via message #1#3; or the handover information #1 does not include information for resource #4; or resource #4 is configured, but resource #4 cannot cover resource #1), then the UE can continue to use resource #1 for a period of time during subsequent processing (i.e., use the original cell's resources to perform service #1). For example, if the selected cell is the original cell, the UE can use resource #1 in step S1201. For details, refer to the descriptions of S1201-S1204 above; simply replace the target cell with the original cell, replace the non-target cell with a non-original cell (or a new cell), and replace resource #4 with resource #1. This application will not elaborate further here.

[0780] To facilitate understanding of the above embodiments provided in this application, the following points are made.

[0781] (1) In the embodiments of this application, "instruction" may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for indicating A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the instruction information is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or the index of the information to be instructed. It is also possible to indirectly indicate the information to be instructed by indicating other information, wherein there is an association between the other information and the information to be instructed. It is also possible to indicate only a part of the information to be instructed, while the other parts of the information to be instructed are known or agreed in advance. For example, the instruction of specific information can also be achieved by using the arrangement order of various information agreed in advance (e.g., stipulated by the protocol), thereby reducing the instruction overhead to a certain extent. In addition, the information to be instructed can be sent as a whole or divided into multiple sub-information to be sent separately, and the sending period and / or sending time of these sub-information can be the same or different.

[0782] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0783] (3) The same or similar parts between the various embodiments of this application can be referred to each other. In the various embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0784] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0785] (5) In this application, “predefined” can be achieved by pre-storing the corresponding code, table or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method.

[0786] (6) In this application, the “protocol” may refer to standard protocols in the field of communications, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied to future communication systems. This application does not limit the scope of the term.

[0787] (7) In this application, the words “exemplary,” “for example,” “exemplary,” “as another example,” etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as an “exemplary” in this application should not be construed as being more preferred or advantageous than other embodiments or designs.

[0788] (8) In this application, “comprising,” “including,” “having,” and variations thereof mean “including but not limited to,” unless otherwise specifically emphasized. “At least one” means one or more, and “more” means two or more.

[0789] (9) In this application, "and / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple.

[0790] (10) Some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0791] (11) In this application, the term "embodiment" as used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0792] (12) It is understood that in this application, “…when” and “if” can be used to limit the time; or “…when” and “if” both refer to the corresponding processing that will be done under certain objective circumstances, not to limit the time, and do not require a judgment action when implemented, nor do they mean that there are other limitations.

[0793] The methods of the embodiments of this application have been described in detail above with reference to Figures 4 to 12. In order to implement the functions of the methods provided in this application, both the transmitting device and the receiving device may include hardware structures and / or software modules, and the above functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a certain function is implemented in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0794] The communication device of the present application embodiment is described below with reference to Figures 13 to 15.

[0795] Figure 13 is a schematic diagram of the structure of a communication device 1300 provided in an embodiment of this application.

[0796] The device 1300 includes a transceiver unit 1310 and a processing unit 1320. The transceiver unit 1310 can communicate with the outside world, and the processing unit 1320 is used for data processing. The transceiver unit 1310 can also be referred to as a communication interface or a communication unit.

[0797] Optionally, the transceiver unit 1310 may also be referred to as a communication interface or communication unit, including a transmitting unit and / or a receiving unit. The transceiver unit 1310 may be a transceiver (including a transmitter and / or receiver), an input / output interface (including input and / or output interfaces), or pins or circuits, etc. The transceiver unit 1310 can be used to perform the transmitting and / or receiving steps in the above method embodiments.

[0798] Optionally, the processing unit 1320 may be a processor (which may include one or more) or a processing circuit with processor functions, and may be used to perform other steps in the above method embodiments besides sending and receiving.

[0799] Optionally, the device 1300 further includes a storage unit, which may be a memory, an internal storage unit (e.g., a register or cache), or an external storage unit (e.g., a read-only memory or a random access memory). The storage unit stores instructions, and the processing unit 1320 executes the instructions stored in the storage unit to cause the communication device to perform the aforementioned method.

[0800] In addition, the transceiver unit 1310 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit 1320 may be a processing circuit.

[0801] It should be noted that the device in Figure 13 can also be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. This application does not impose any limitations on this.

[0802] The device 1300 can be used to perform the actions performed by the first communication device (or UE) in the above method embodiment. In this case, the device 1300 can be the first communication device or a component that can be configured in the first communication device.

[0803] The processing unit 1320 is used to perform processing-related operations on the first communication device side in the above method embodiment. For example, it is used to execute a first service through a first resource, where the first resource is the resource of a first cell. The first communication device is under the coverage of the first cell, and the first communication device establishes a radio resource control (RRC) connection with the first network device through the first cell. During the execution of the first service, a failure occurs, which includes at least one of the following: radio link failure (RLF), RRC connection reconfiguration failure, integrity verification failure, or RRC connection reconstruction: initiating an RRC connection reconstruction process and using the first resource to execute the first service.

[0804] The device 1300 can be used to perform the actions performed by the first communication device (or UE) in the above method embodiment. In this case, the device 1300 can be the first communication device or a component that can be configured in the first communication device.

[0805] The processing unit 1320 is used to perform processing-related operations on the first communication device side in the above method embodiment. For example, it is used to execute a first service through a first resource, where the first resource is the resource of the first cell. Under the coverage of the first cell, the first communication device establishes a Radio Resource Control (RRC) connection with the first network device through the first cell; initiates an RRC connection reconstruction process; and uses a second resource to execute the first service, where the second resource is the resource of the third cell.

[0806] The transceiver unit 1310 is used to perform transceiver-related operations on the first communication device side in the above method embodiment, for example, to receive a second message, the second message being used to instruct the first communication device to switch from the first cell to the third cell.

[0807] Alternatively, the device 1300 can be used to perform the actions performed by the first network device (or network device #1) in the above method embodiments. In this case, the device 1300 can be the first network device or a component configurable on the first network device.

[0808] The transceiver unit 1310 is used to perform transceiver-related operations on the first network device side in the above method embodiment. For example, it is used to send first information, which is used to indicate at least one of the following: when the first communication device initiates a Radio Resource Control (RRC) connection reconstruction process, it uses the first resource to perform a first service; or, when the first communication device initiates an RRC connection reconstruction process, if the selected cell is the first cell, it uses the first resource to perform the first service; or, when the first communication device initiates an RRC connection reconstruction process, if the selected cell is the first cell and the RRC connection reconstruction is completed through the first cell, it uses the first resource to perform the first service; wherein, the first resource is the resource of the first cell, and the first communication device establishes an RRC connection with the first network device through the first cell under the coverage of the first cell.

[0809] Alternatively, the transceiver unit 1310 may perform transceiver-related operations on the first network device side in the above method embodiments, for example, by sending second information, the second information indicating at least one of the following: when the first communication device initiates an RRC connection reconstruction process, it uses the second resource to perform the first service; or, during the RRC connection reconstruction process, if the selected cell is the third cell, the first communication device uses the second resource to perform the first service; or, during the RRC connection reconstruction process, if the selected cell is the third cell and the RRC connection reconstruction is completed through the third cell, the first communication device uses the second resource to perform the first service; or, when the first communication device receives a second message, it uses the second resource to perform the first service; wherein, the first communication device establishes a Radio Resource Control (RRC) connection with the first network device.

[0810] It should be understood that the device 1300 here is embodied in the form of a functional unit. The term "unit" here may refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memories for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functions.

[0811] The apparatus 1300 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as the first communication device, or the first network device) in the above-described methods. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0812] Figure 14 is a schematic diagram of the structure of a communication device 1400 provided in an embodiment of this application.

[0813] As shown in Figure 14, the device 1400 includes a processor 1410 and a transceiver 1420. The processor 1410 and the transceiver 1420 communicate with each other through an internal connection path. The processor 1410 is used to execute instructions to control the transceiver 1420 to send and / or receive signals.

[0814] Optionally, the device 1400 may further include a memory 1430, which communicates with the processor 1410 and the transceiver 1420 via internal interconnection paths. The memory 1430 is used to store instructions, and the processor 1410 can execute the instructions stored in the memory 1430.

[0815] In one possible implementation, the device 1400 is used to implement the various processes and steps corresponding to the first communication device (or UE) in the above method embodiments.

[0816] It should be understood that the device 1400 may specifically be the first communication device (or UE) in the above embodiments, or it may be a chip or a chip system. Correspondingly, the transceiver 1420 may be the transceiver circuit of the chip, which is not limited here. For example, the device 1400 may be used to execute the various steps and / or processes corresponding to the first communication device (or UE) in the above method embodiments.

[0817] In one possible implementation, the device 1400 is used to implement the various processes and steps corresponding to the first network device (or network device #1) in the above method embodiments.

[0818] It should be understood that the device 1400 may specifically be the first network device (or network device #1) in the above embodiments, or it may be a chip or a chip system. Correspondingly, the transceiver 1420 may be the transceiver circuit of the chip, which is not limited here. For example, the device 1400 may be used to execute the various steps and / or processes corresponding to the first network device (or network device #1) in the above method embodiments.

[0819] Optionally, the memory 1430 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1410 may be used to execute instructions stored in the memory, and when the processor 1410 executes instructions stored in the memory, the processor 1410 is used to perform the various steps and / or processes of the method embodiments corresponding to the first communication device (or UE) described above.

[0820] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0821] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The processor in the embodiments of this application can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0822] It is understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous linked dynamic random access memory, and direct memory bus random access memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0823] Figure 15 is a schematic diagram of the structure of a chip system 1500 provided in an embodiment of this application.

[0824] As shown in Figure 15, the chip system 1500 (or processing system) includes logic circuits 1510 and input / output interface 1520.

[0825] The logic circuit 1510 can be a processing circuit in the chip system 1500. The logic circuit 1510 can be coupled to the storage unit, calling instructions in the storage unit, enabling the chip system 1500 to implement the methods and functions of the embodiments of this application. The input / output interface 1520 can be an input / output circuit in the chip system 1500, outputting processed information from the chip system 1500, or inputting data or signaling information to be processed into the chip system 1500 for processing.

[0826] As one option, the chip system 1500 is used to implement the operations performed by the first communication device (or UE) in the various method embodiments described above.

[0827] As one option, the chip system 1500 is used to implement the operations performed by the first network device (or network device #1) in the various method embodiments described above.

[0828] This application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0829] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0830] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0831] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0832] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0833] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0834] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0835] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0836] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0837] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method, applied to a first communication device, characterized in that, include: The first service is performed through the first resource, which is the resource of the first cell. The first communication device is under the coverage of the first cell, and the first communication device establishes a Radio Resource Control (RRC) connection with the first network device through the first cell. During the execution of the first service, a failure occurs, including at least one of the following: radio link failure (RLF), RRC connection reconfiguration failure, integrity verification failure, or RRC connection reconstruction. Initiate an RRC connection reconstruction process and use the first resource to execute the first service. The method of claim 1, wherein The initiation of the RRC connection reconstruction process, using the first resource to execute the first service, includes: When initiating the RRC connection reconstruction process, the first service is executed using the first resource; Select a residential community; If the selected cell is the first cell, continue to use the first resource to perform the first service; If the selected cell is the second cell, release the first resource. The second cell is different from the first cell. The method of claim 1, wherein The initiation of the RRC connection reconstruction process, using the first resource to execute the first service, includes: Select a residential community; If the selected cell is the first cell, the first service is executed using the first resource; If the selected cell is the second cell, release the first resource. The second cell is different from the first cell. The method of claim 1, wherein The initiation of the RRC connection reconstruction process, using the first resource to execute the first service, includes: Select a residential community; If the selected cell is the first cell, and the RRC connection reconstruction is completed through the first cell, the first resource is used to execute the first service; If the selected cell is the second cell, release the first resource. The second cell is different from the first cell. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive first information, the first information being used to instruct the first communication device to use the first resource to execute the first service when initiating the RRC connection reconstruction process; Alternatively, the first information is used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the first cell, to use the first resources to perform the first service; Alternatively, the first information may be used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the first cell and the RRC connection reconstruction is completed through the first cell, to use the first resources to execute the first service. The method according to claim 5, characterized in that The method further includes: The first information is contained in the first message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message. The method according to any one of claims 2 to 6, characterized in that, The method of initiating RRC connection reconstruction further includes: starting a first timer and performing cell selection during the operation of the first timer; The cell selection process further includes: if a cell is selected, starting a second timer, and sending an RRC request message through the selected cell during the operation of the second timer. The method according to any one of claims 2 to 7, characterized in that The execution of the first service through the first resource also includes: Receive third information, the third information indicating the first resource and the third timer, and execute the first service through the first resource during the operation of the third timer; The release of the first resource also includes: the third timer timeout or stopping the third timer. The method according to any one of claims 1 to 8, characterized in that The first business is the Environmental Internet of Things (AIoT) business. A communication method applied to a first communication device, characterized in that, include: The first service is performed through the first resource, which is the resource of the first cell. The first communication device is under the coverage of the first cell, and the first communication device establishes a radio resource control (RRC) connection with the first network device through the first cell. Receive a second message, the second message being used to instruct the first communication device to switch from the first cell to the third cell; Initiate an RRC connection reconstruction process, and use the second resource to execute the first service, wherein the second resource is the resource of the third cell. The method of claim 10, wherein The initiation of the RRC connection reconstruction process, using the second resource to execute the first service, includes: When initiating the RRC connection reconstruction process, the second resource is used to execute the first service; Select a residential community; If the selected cell is the third cell, the second resource will continue to be used to perform the first service; If the selected cell is the second cell, release the second resource. The second cell is different from the third cell. The method of claim 10, wherein The initiation of the RRC connection reconstruction process, using the second resource to execute the first service, includes: Select a residential community; If the selected cell is the third cell, the first service is executed using the second resource; If the selected cell is the second cell, release the second resource. The second cell is different from the third cell. The method of claim 10, wherein The initiation of the RRC connection reconstruction process, using the second resource to execute the first service, includes: Select a residential community; If the selected cell is the third cell, and the RRC connection reconstruction is completed through the third cell, the second resource is used to execute the first service; If the selected cell is the second cell, release the second resource. The second cell is different from the third cell. The method according to any one of claims 10 to 13, characterized in that, The method further includes: Upon receiving the second message, the first service is executed using the second resource. The method according to any one of claims 12 to 14, characterized in that The method further includes: Receive second information, the second information being used to instruct the first communication device to use the second resource to perform the first service when initiating the RRC connection reconstruction process; Alternatively, the second information is used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the third cell, to use the second resource to execute the first service; Alternatively, the second information may be used to instruct the first communication device, during the RRC connection reconstruction process, if the selected cell is the third cell and the RRC connection reconstruction is completed through the third cell, to use the second resource to execute the first service; Alternatively, the second information may be used to instruct the first communication device to use the second resource to perform the first service when it receives the second message. The method of claim 15, wherein The method further includes: The second information is contained in the third message, which is the second message, system information, RRC reconfiguration message, or RRC connection reconstruction message. The method according to any one of claims 11 to 16, characterized in that, The method of initiating RRC connection reconstruction further includes: starting a first timer and performing cell selection during the operation of the first timer; The cell selection process further includes: if a cell is selected, starting a second timer, and sending an RRC request message through the selected cell during the operation of the second timer. The method according to any one of claims 11 to 17, characterized in that The step of using the second resource to perform the first service also includes: Receive third information, the third information indicating the second resource and the third timer, and use the second resource to execute the first service during the operation of the third timer; The release of the second resource also includes: the third timer timeout or stopping the third timer. The method according to any one of claims 10 to 18, characterized in that The first business is the Environmental Internet of Things (AIoT) business. A communication method applied to a first network device, characterized in that, include: Send a first message, the first message being used to indicate at least one of the following: When the first communication device initiates the Radio Resource Control (RRC) connection reconstruction process, it uses the first resource to perform the first service. Alternatively, if the selected cell is the first cell during the RRC connection reconstruction process, the first communication device may use the first resource to execute the first service. Alternatively, if the first communication device selects the first cell during the RRC connection reconstruction process and completes the RRC connection reconstruction through the first cell, it may use the first resource to execute the first service. Wherein, the first resource is the resource of the first cell, the first communication device is under the coverage of the first cell, and the first communication device establishes an RRC connection with the first network device through the first cell. The method of claim 20, wherein: The first information is contained in the first message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message. A communication method applied to a first network device, characterized in that, include: Send a second message, the second message being used to indicate at least one of the following: When the first communication device initiates the Radio Resource Control (RRC) connection re-establishment process, it uses the second resource to perform the first service. Alternatively, if the selected cell is the third cell during the RRC connection reconstruction process, the first communication device may use the second resource to execute the first service. Alternatively, if the first communication device selects the third cell during the RRC connection reconstruction process and completes the RRC connection reconstruction through the third cell, it may use the second resource to execute the first service. Alternatively, when the first communication device receives the second message, it may use the second resource to perform the first service. The first communication device establishes a Radio Resource Control (RRC) connection with the first network device. The method of claim 22, wherein: The second information is contained in the third message, which is system information, an RRC reconfiguration message, or an RRC connection reconstruction message. The method according to claim 22 or 23, characterized in that The method further includes: Send the second message, which instructs the first communication device to switch to the third cell. A communication device, characterized by The apparatus includes a unit for performing the method as described in any one of claims 1 to 9; or, includes a unit for performing the method as described in any one of claims 10 to 19; or, includes a unit for performing the method as described in claim 20 or 21; or, includes a unit for performing the method as described in any one of claims 22 to 24. A communication device, characterized by The method includes a processor coupled to a memory for storing computer programs or instructions, the processor for executing the computer programs or instructions in the memory such that the method of any one of claims 1 to 9 is performed; or the method of any one of claims 10 to 19 is performed; or the method of any one of claims 20 or 21 is performed; or the method of any one of claims 22 to 24 is performed. A computer-readable storage medium, characterized by, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1 to 24 to be performed. A computer program product, characterized in that When the computer program product is run on a computer, the method as described in any one of claims 1 to 24 is performed. A chip or chip system, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a communication device equipped with the chip system to perform the method of any one of claims 1 to 24.

Images