User equipment (UE) control method and apparatus, UE configuration method and apparatus, and communication device

Abstract

The present application relates to the technical field of communications, and discloses a user equipment (UE) control method and apparatus, a UE configuration method and apparatus, and a communication device. The UE control method in embodiments of the present application comprises: when a first UE is associated with a second UE, the first UE executes uplink synchronization on the basis of the second UE, or the first UE does not execute random access or suspends random access in a first process, wherein the first process comprises at least one of the following: a radio resource control (RRC) connection establishment process; an RRC connection recovery process; an RRC connection reestablishment process; and a switching process.

Description

User equipment UE control method, UE configuration method, device and communication equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202311274103.2 filed in China on September 27, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a user equipment (UE) control method, UE configuration method, device and communication equipment. Background Art

[0004] In related technologies, the initial access, handover, radio resource control (RRC) connection reestablishment, and uplink synchronization maintenance processes of different user equipment (UE) are independent of each other. Thus, at least two UEs on the same terminal device need to perform their own initial access, handover, RRC connection reestablishment, and uplink synchronization maintenance processes respectively. That is, the same terminal needs to perform at least two initial access, handover, RRC connection reestablishment, and uplink synchronization maintenance processes, which consumes a large amount of network-side resources or increases the control plane latency on the terminal side.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a user equipment (UE) control method, a UE configuration method, an apparatus, and a communication device, which can solve the problem of resource waste on the network side and long control plane delay on the terminal side caused by at least two mutually related terminals performing a random access (RA) process or an uplink synchronization maintenance process respectively.

[0007] In a first aspect, a UE method is provided, which is performed by a first UE. The method includes:

[0008] In a case where a first UE is associated with a second UE, the first UE performs uplink synchronization based on the second UE, or the first UE does not perform random access or suspends random access in a first process, and the first process includes at least one of the following:

[0009] RRC connection establishment process;

[0010] RRC connection recovery process;

[0011] RRC connection reestablishment process;

[0012] Switch process.

[0013] In a second aspect, a UE control method is provided, which is performed by a second UE. The method includes:

[0014] When the second UE is in an RRC connected state and is associated with the first UE, the second UE performs one of the following:

[0015] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a cell radio network temporary identifier (Cell Radio Network Temporary Identifier, C-RNTI) or a first resource to the first UE;

[0016] Sending the C-RNTI of the first UE to a network-side device;

[0017] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0018] In a third aspect, a UE configuration method is provided, which is performed by a network-side device. The method includes:

[0019] The network-side device performs a second operation, where the second operation includes at least one of the following:

[0020] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0021] receiving a C-RNTI of the first UE from the second UE;

[0022] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0023] The first UE is associated with the second UE.

[0024] In a fourth aspect, a UE control device is provided, for use with a first UE, the device including:

[0025] A first execution module is configured to, when the first UE is associated with a second UE, perform uplink synchronization based on the second UE, or not perform random access or suspend random access in a first process, where the first process includes at least one of the following:

[0026] Radio Resource Control RRC connection establishment process;

[0027] RRC connection recovery process;

[0028] RRC connection reestablishment process;

[0029] Switch process.

[0030] In a fifth aspect, a UE control device is provided for a second UE, the device including:

[0031] The second execution module is configured to, when the second UE is in an RRC connected state and is associated with the first UE, execute one of the following:

[0032] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a C-RNTI or a first resource to the first UE;

[0033] Sending the C-RNTI of the first UE to a network-side device;

[0034] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0035] In a sixth aspect, a UE configuration apparatus is provided for a network-side device, the apparatus including:

[0036] The third execution module is configured to execute a second operation, where the second operation includes at least one of the following:

[0037] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0038] receiving a C-RNTI of the first UE from the second UE;

[0039] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0040] The first UE is associated with the second UE.

[0041] In a seventh aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0042] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface;

[0043] When the terminal includes a first UE, the processor is configured to, when the first UE is associated with a second UE, perform uplink synchronization based on the second UE, or not perform random access or suspend random access in a first process, where the first process includes at least one of the following:

[0044] RRC connection establishment process;

[0045] RRC connection recovery process;

[0046] RRC connection reestablishment process;

[0047] Switch process; or,

[0048] When the terminal includes a second UE, the communication interface is configured to, when the second UE is in an RRC connected state and the second UE is associated with the first UE, perform one of the following:

[0049] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a C-RNTI or a first resource to the first UE;

[0050] Sending the C-RNTI of the first UE to a network-side device;

[0051] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0052] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect are implemented.

[0053] In an eighth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to perform a second operation, the second operation including at least one of the following:

[0054] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0055] receiving a C-RNTI of the first UE from the second UE;

[0056] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0057] The first UE is associated with the second UE.

[0058] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0059] In the tenth aspect, a wireless communication system is provided, including: a first UE, a second UE and a network side device, wherein the first UE can be used to execute the steps of the method described in the first aspect, the second UE can be used to execute the steps of the method described in the second aspect, and the network side device can be used to execute the steps of the method described in the third aspect.

[0060] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0061] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and is executed by at least one processor to implement the steps of the UE control method as described in the first aspect, or the steps of the UE control method as described in the second aspect, or the steps of the UE configuration method as described in the third aspect.

[0062] In an embodiment of the present application, when a first UE is associated with a second UE, the first UE performs uplink synchronization based on the second UE, or the first UE does not perform random access or suspends random access in a first process, and the first process includes at least one of the following: a radio resource control RRC connection establishment process; an RRC connection recovery process; an RRC connection reestablishment process; a switching process. When a first UE is associated with a second UE, when the first UE initiates initial access, switching, RRC connection reestablishment, uplink synchronization maintenance, etc., if the second UE it is associated with has completed a random access (Random Access Channel, RAC) process or is initiating a random access process or has established uplink synchronization, the terminal can perform uplink synchronization based on the associated terminal, or omit the random access process. In this way, the problem of network-side resource waste and long control plane delay on the terminal side caused by the first UE and the second UE performing the random access process or the uplink synchronization maintenance process respectively can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] FIG1 is a schematic structural diagram of a wireless communication system to which an embodiment of the present application can be applied;

[0064] FIG2 is a flowchart of a UE control method performed by a first UE according to an embodiment of the present application;

[0065] FIG3 is a schematic diagram of the interaction of a contention-based random access (CBRA) process in the related art;

[0066] FIG4 is a schematic diagram of an interaction process of a contention-free random access (CFRA) process in the related art;

[0067] FIG5 is a flowchart of a UE control method performed by a second UE according to an embodiment of the present application;

[0068] FIG6 is a flowchart of a UE configuration method provided in an embodiment of the present application;

[0069] FIG7 is a structural diagram of a UE control device provided in an embodiment of the present application;

[0070] FIG8 is a structural diagram of another UE control device provided in an embodiment of the present application;

[0071] FIG9 is a structural diagram of a UE configuration device provided in an embodiment of the present application;

[0072] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0073] FIG11 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0074] FIG12 is a schematic structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0076] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0077] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0078] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0079] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0080] The following, in combination with the accompanying drawings, describes in detail the UE control method, UE configuration method, UE control device, UE configuration device and communication equipment provided in the embodiments of the present application through some embodiments and their application scenarios.

[0081] Referring to FIG2 , an embodiment of the present application provides a UE control method, the execution subject of which is a first UE. As shown in FIG2 , the UE control method executed by the first UE includes the following steps:

[0082] Step 201: When a first UE is associated with a second UE, the first UE performs uplink synchronization based on the second UE, or the first UE does not perform random access or suspends random access in a first process, where the first process includes at least one of the following:

[0083] Radio Resource Control RRC connection establishment process;

[0084] RRC connection recovery process;

[0085] RRC connection reestablishment process;

[0086] Switch process.

[0087] In some embodiments, the first UE is associated with the second UE, which may be that there is an association relationship between the first UE and the second UE, or the first UE and the second UE support association operations, or the first UE and the second UE have association conditions (for example, the communication status is the same or partially the same), so that the second UE can interact with the network side device with information or signaling related to the first UE, so that the first UE can execute the above-mentioned first process while omitting the random access process; or, the first UE can achieve uplink synchronization based on the uplink synchronization maintenance process of the second UE.

[0088] It should be noted that the terminal in the embodiments of the present application may be a user equipment (UE) entity corresponding to a universal subscriber identity module (USIM) card or other type of subscriber identity module (SIM) card. It is understood that the UE is a logical entity in the terminal that corresponds to a USIM card or SIM card and has 4G, 5G and / or next-generation wireless communication capabilities.

[0089] In some embodiments, the second UE includes at least one of the following:

[0090] a UE corresponding to a different USIM card in the same device as the first UE;

[0091] UEs corresponding to different registrations in the same device as the first UE.

[0092] For example, assuming that the first UE is UE1 and the second UE is UE2, UE1 and UE2 are UE entities corresponding to two SIM cards in the same device (such as a terminal or a mobile phone) and belonging to the same operator.

[0093] For another example, the first UE and the second UE may be UE entities corresponding to SIM cards of the same device but belonging to different operators, and both the first UE and the second UE reside in a cell or network shared by a Radio Access Network (RAN).

[0094] For another example, the first UE and the second UE may be in a case where a SIM card in the same device initiates dual registration, and the UE entities corresponding to each registration.

[0095] For ease of explanation, in the embodiments of the present application, an example is generally given in which the first UE is UE1, the second UE is UE2, and UE1 and UE2 are UE entities corresponding to different USIM cards on the same device, which does not constitute a specific limitation.

[0096] In some embodiments, the first UE performs uplink synchronization based on the second UE, that is, the first UE can obtain its own uplink synchronization status and information through the second UE, thereby saving network resource overhead generated by establishing and maintaining uplink synchronization between the first UE and the network side.

[0097] In some embodiments, the first UE does not perform random access or suspend random access in the first process. The first UE may implement the first process through interaction between the second UE and the network side device in the first process. In this way, the first UE can omit the random access process and reduce the control plane delay of the first UE.

[0098] It is worth mentioning that the random access in the embodiment of the present application may include 4-step CBRA, 2-step CFRA and improved 2-step CBRA.

[0099] The difference between 4-step CBRA and 2-step CFRA is that 4-step CBRA has a certain probability of random access collision and random access failure. In most application scenarios, the slight delay caused by 4-step CBRA can be tolerated. However, some scenarios with very stringent latency requirements, such as handover or downlink recovery, can use 2-step CFRA to avoid the additional delay and the possibility of random access failure. In such scenarios, the UE will use the pre-assigned dedicated Message 1 (Msg1) (including the preamble sequence) to initiate random access.

[0100] As shown in Figure 3, the 4-step CBRA process includes the following steps:

[0101] Step 1: The UE sends Msg1 to the network (e.g., via a physical random access channel (PRACH)).

[0102] Step 2: The UE receives a message 2 (Msg2) (such as a Random Access Response (RAR) message) sent by the network.

[0103] Step 3: The UE sends Msg3 according to the uplink grant provided in the random access response message;

[0104] Step 4: The UE determines whether the contention of the random access process is resolved based on the content of the received Msg4.

[0105] As shown in Figure 4, the 2-step CFRA process includes the following steps:

[0106] Step 0: The network side allocates a random access preamble to the UE;

[0107] Step 1: The UE sends Msg1 (e.g., based on PRACH).

[0108] Step 2: The UE determines whether the contention of the random access process is resolved based on the content of the received Msg2.

[0109] In some implementations, the first process may be a process that requires initiating a random access process in the related art. In the embodiment of the present application, the first UE may not perform or suspend the random access process in at least one of the following processes:

[0110] 1) Initial access from RRC_IDLE;

[0111] 2)RRC Connection Re-establishment Procedure in Connected State

[0112] 3) Handover;

[0113] 4) DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is "non-synchronised";

[0114] 5) When uplink data arrives but there is no Physical Uplink Control Channel (PUCCH) resource to send a Scheduling Request (SR);

[0115] 6) Scheduling request (SR) failed;

[0116] 7) Obtain uplink synchronization when adding a secondary cell (SCell);

[0117] 8) Synchronous reconfiguration via RRC (e.g., Primary cell (PCell) change, Primary Secondary Cell (PSCell) addition / change);

[0118] 9) Small Data Transmission (SDT) process;

[0119] 10) Request for Other System Information (OSI);

[0120] 11) Beam failure recovery

[0121] For ease of explanation, in the embodiments of the present application, an example is mainly taken where the first UE does not perform or suspend random access in the initial access, handover or RRC connection reestablishment process, or omits the uplink synchronization maintenance process of the first UE.

[0122] As an optional implementation manner, the first UE does not perform random access or suspends random access in the first process, including:

[0123] In a case where the first UE is configured to obtain uplink synchronization based on the second UE, or in a case where the first UE is configured not to perform random access or suspend random access in the first process, the first UE does not perform random access or suspend random access in the first process.

[0124] In some embodiments, when the first UE is in an RRC connection state with the network side, the network side device may configure the first UE to obtain uplink synchronization based on the second UE, or random access is not performed or suspended in the first process.

[0125] In other embodiments, when the first process includes an RRC connection recovery process, the network side device can configure the first UE to obtain uplink synchronization based on the second UE through an RRC release message, or not perform random access or suspend random access in the first process.

[0126] In some other implementations, when the first process includes an initial access process, the network side device can configure the first UE to obtain uplink synchronization based on the second UE through a broadcast message, or, not perform random access or suspend random access in the first process.

[0127] In addition, when the network side configures the second UE to obtain uplink synchronization based on the associated UE (first UE), or does not perform random access or suspend random access in the first process, the first UE can determine that the first UE obtains the corresponding configuration based on the second UE being configured to obtain uplink synchronization based on the associated UE, or does not perform random access or suspend random access in the first process, that is, it is considered that the first UE is configured to obtain uplink synchronization based on the second UE, or the first UE is configured not to perform random access or suspend random access in the first process.

[0128] In this embodiment, the first UE can be configured by the network side device so that the first UE can not perform random access or suspend random access in the first process only when it is configured to obtain uplink synchronization based on the second UE, or when the first UE is configured not to perform random access or suspend random access in the first process.

[0129] In other words, if the first UE is not configured to obtain uplink synchronization based on the second UE or is not configured not to perform random access or suspend random access in the first process, the first UE shall perform random access in the first process according to the random access trigger conditions specified in the relevant technology.

[0130] Of course, in some implementations, it may be agreed in a protocol that the first UE associated with the second UE is permitted not to perform random access or suspend random access in the first process, which is not specifically limited herein. Specifically, it may be agreed in the protocol that when the network side knows that the first UE and the second UE are associated, the first UE is permitted not to perform random access or suspend random access in the first process.

[0131] Scenario 1: The first UE does not perform or suspends random access in the initial access or RRC connection reestablishment process.

[0132] As an optional implementation manner, when the first process is an RRC connection establishment process or an RRC connection recovery process, the first UE does not perform random access or suspends random access in the first process, including:

[0133] When at least one of the following conditions is met, the first UE does not perform random access or suspends random access in the first procedure:

[0134] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0135] The first UE and the second UE have related transmission beams;

[0136] The first UE and the second UE have the same serving cell;

[0137] The second UE is in an RRC connected state, or is establishing an RRC connection, or is restoring an RRC connection.

[0138] In some embodiments, the first UE and the second UE have related transmission beams, which may be the same or similar beams that the first UE and the second UE have, wherein similar beams may include beams with a spatial correlation relationship, such as beams that are spatially close.

[0139] In related technologies, during the process of random access performed by a UE, uplink synchronization and a transmission beam of a terminal synchronized with the network side can be established. In some embodiments, when a first UE and a second UE reside in the same serving cell, or the first UE can use the same uplink synchronization as the second UE, or the first UE and the second UE use the same transmission beam, it can be indicated that the first UE does not need to perform random access. For example, assuming that UE1 and UE2 are UE entities corresponding to different SIM cards of the same operator on the same device, at this time, if UE1 and UE2 reside in the same cell, UE1 and UE2 often have the same uplink synchronization and use the same transmission beam.

[0140] In this embodiment, the second UE is required to be in an RRC connection state, or to be establishing an RRC connection, or to be restoring an RRC connection. In this way, at least one of the processes of initial access, RRC connection reconstruction, uplink synchronization maintenance, etc. of the first UE associated with the second UE can be simplified, that is, the random access process of the first UE in the processes of initial access, RRC connection reconstruction, uplink synchronization maintenance, etc. is omitted to save resources on the network side or reduce the control plane delay on the terminal side.

[0141] As an optional implementation manner, when the first UE does not perform random access or suspend random access in the first process, and the first process is an RRC connection establishment process or an RRC connection recovery process, the method further includes:

[0142] The first UE completes a first operation on a first resource, or the first UE monitors network scheduling according to a C-RNTI configured by the network side to complete the first operation, where the first operation includes at least one of the following:

[0143] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0144] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0145] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0146] In some embodiments, the method further comprises:

[0147] The first UE obtains the C-RNTI of the first UE or the first resource from the second UE.

[0148] In this embodiment, when the first UE determines not to perform random access or suspend random access in the RRC connection establishment process or the RRC connection recovery process, the first resource or the C-RNTI configured by the network side for the first UE can be obtained from the network side device through the second UE. In this way, the first UE can perform the first operation based on the first resource or C-RNTI.

[0149] In other embodiments, when the first UE determines not to perform random access or suspend random access in the RRC connection establishment process or the RRC connection recovery process, the relevant information of the first UE can be sent to the network side device through the second UE, so that the network side device allocates a first resource or C-RNTI to the first UE based on the relevant information of the first UE.

[0150] In some implementations, when the first UE acquires the first resource, the first UE performs the first operation on the first resource.

[0151] In some other implementations, the first UE monitors network scheduling according to the C-RNTI configured by the network side to complete the first operation, including:

[0152] If the first UE fails to acquire the first resource, the first UE monitors network scheduling according to the C-RNTI to complete the first operation.

[0153] Optionally, the first UE monitors network scheduling according to the C-RNTI to complete the first operation, which may be that the first UE monitors network-side dynamic scheduling resources according to the C-RNTI to perform the first operation on the monitored resources.

[0154] In this embodiment, the first UE can preferentially use the first resource configured by the network side for the first UE to perform the first operation, and only when the first UE fails to obtain the first resource, it monitors the network scheduling according to the C-RNTI to complete the first operation.

[0155] As an optional implementation, the method further includes:

[0156] Starting from the moment when the first UE determines not to perform random access or suspend random access in the first process, if the first UE fails to obtain the first resource or the C-RNTI within a preset time, the first UE initiates random access.

[0157] In this embodiment, the first UE may suspend the random access process at the moment of determining that random access is not performed or random access is suspended in the first process, and wait for obtaining the first resource or the C-RNTI. If the first resource or the C-RNTI is obtained within the preset time, the first operation is performed based on the first resource or the C-RNTI. At this time, the first UE does not perform the random access process in the first process; if the first UE does not obtain the first resource or the C-RNTI within the preset time, the terminal initiates a random access process in the first process. At this time, the implementation method of the first process is the same as the implementation method of the first process in the related technology, and will not be repeated here.

[0158] Scenario 2: The first UE does not perform or suspends random access during the handover process.

[0159] As an optional implementation manner, when the first process is a handover process, the first UE does not perform random access or suspends random access in the first process, including:

[0160] When at least one of the following conditions is met, the first UE does not perform random access or suspends random access in the first procedure:

[0161] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0162] The first UE and the second UE have related transmission beams;

[0163] The second UE is in an RRC connected state;

[0164] The serving cell after the switching of the first UE is the same as the current or switched serving cell of the second UE;

[0165] The second UE is performing a handover procedure or has completed the handover procedure;

[0166] The RRC reconfiguration message received by the first UE for performing handover does not carry a synchronization reconfiguration parameter.

[0167] In some embodiments, when the first process is a switching process, the first UE and the second UE that are associated with each other are usually switched from the source cell to the same target cell. Based on this feature, when the first UE can obtain uplink synchronization based on the second UE; or, the first UE and the second UE have related transmission beams; or, the service cell after the first UE is switched is the same as the current or switched service cell of the second UE, it means that the second UE and the first UE switch to the same target service cell.

[0168] In some embodiments, the first UE may not perform random access or suspend random access based on the fact that the received RRC reconfiguration message does not carry the synchronization reconfiguration parameters. Specifically, in the case where the first process is a handover process, the target base station may only send an RRC reconfiguration message carrying the synchronization reconfiguration parameters to the second UE based on the association information between the first UE and the second UE, while the RRC reconfiguration message sent to the first UE does not carry the synchronization reconfiguration parameters. In this case, the second UE performs random access based on the synchronization reconfiguration parameters in the RRC reconfiguration message, while the first UE does not perform random access or suspend random access based on the fact that the received RRC reconfiguration message does not carry the synchronization reconfiguration parameters.

[0169] In some implementations, when the RRC reconfiguration message received by the first UE carries a synchronization reconfiguration parameter, the first UE may also be configured not to perform or suspend random access.

[0170] For example: assuming that the first UE is UE1, the second UE is UE2, and UE1 and UE2 are UE entities corresponding to two different SIM cards on the same device, if UE2 has established uplink synchronization or completed random access; and UE1 is configured not to initiate random access, or is configured to apply UE2's uplink synchronization, then UE1 may not initiate random access to the target cell, but instead monitor the scheduling of the target cell based on the C-RNTI to send an RRC reconfiguration completion message.

[0171] In some implementations, when the first process is a handover process, the second UE is required to be in an RRC connected state.

[0172] Optionally, the first UE may acquire uplink synchronization based on the second UE after the random access of the second UE is completed.

[0173] Optionally, the second UE can send relevant information of the first UE to the network side in the RRC connected state. For example, the second UE sends the C-RNTI of the first UE to the network side. The network side can then learn the association relationship between the first UE and the second UE based on the C-RNTI of the first UE received from the second UE. In this way, the network side can select the second UE to perform random access based on the association relationship between the first UE and the second UE, and omit random access for the first UE.

[0174] In this embodiment, during the mobility process, the first UE and the second UE that are associated with each other often switch from the same source cell to the same target cell. During the handover process, the terminal must initiate random access to the target base station to obtain uplink synchronization. Since the first UE and the second UE are associated with each other, such as the first UE and the second UE are UE entities corresponding to two SIM cards on the same mobile phone, the uplink synchronization of the first UE and the second UE is the same. Therefore, only one terminal (i.e., the second UE) needs to perform random access, and the other terminal (i.e., the first UE) can be exempted from the random access process.

[0175] As an optional implementation manner, when the first UE does not perform random access or suspends random access in the first process, and the first process is a handover process, the method further includes:

[0176] The first UE sends an RRC reconfiguration complete message of the first UE in one of the following ways, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE:

[0177] In a first manner, an RRC reconfiguration complete message of the first UE is sent on a second resource allocated by a network side device to the first UE;

[0178] In a second manner, monitoring network scheduling according to the C-RNTI of the first UE to send an RRC reconfiguration complete message of the first UE;

[0179] A third method is to carry the RRC reconfiguration complete message of the first UE in the RRC reconfiguration complete message of the second UE and send it.

[0180] In some implementations, the second resource may be carried in an RRC reconfiguration message sent by the network side to the first UE. The second resource may also be sent by the network side to the second UE (e.g., via an RRC reconfiguration message). This application does not limit the method for obtaining the second resource.

[0181] In other implementations, the first UE may monitor the scheduling of the target serving cell based on the C-RNTI in the received RRC reconfiguration message, so as to send the RRC reconfiguration complete message on the uplink resources scheduled by the target serving cell.

[0182] In some other implementations, the RRC reconfiguration message of the first UE may be included in the RRC reconfiguration message of the second UE and sent to the second UE. Correspondingly, the RRC reconfiguration complete message of the first UE may be included in the RRC reconfiguration complete message of the second UE and reported to the network side.

[0183] For example, assuming that the target base station learns the association between UE1 and UE2, it sends an RRC reconfiguration message for UE1 and an RRC reconfiguration message for UE2, wherein the RRC reconfiguration message for UE2 carries a synchronization reconfiguration parameter to trigger UE2 to initiate random access to the target base station. If the RRC reconfiguration message for UE1 does not carry the synchronization reconfiguration parameter, UE1 does not initiate random access to the target base station. After UE2's random access is completed, UE1 obtains uplink synchronization based on UE2, and UE1 sends an RRC reconfiguration completion message to the network side in the following manner:

[0184] A first manner is to send an RRC reconfiguration complete message on the second resource configured in the RRC reconfiguration message of the UE1;

[0185] The second method is to monitor the scheduling of the target base station according to the C-RNTI in the RRC reconfiguration message of the UE1, so as to send an RRC reconfiguration complete message on the uplink resources scheduled by the base station;

[0186] In a third manner, UE2 places UE1's RRC reconfiguration complete message in a container in UE2's RRC reconfiguration complete message and sends the message to the network side.

[0187] In some implementations, when the RRC reconfiguration complete message of the first UE is sent by the first manner or the second manner, the method further includes:

[0188] The first UE passes the RRC reconfiguration message of the first UE to the Medium Access Control (MAC) layer, wherein the MAC layer does not trigger a random access process or a buffer status report (BSR) according to the RRC reconfiguration message of the first UE.

[0189] It is worth mentioning that in the related art, when the terminal receives the RRC reconfiguration message, it passes the RRC reconfiguration message to the MAC, so that the MAC triggers the random access process according to the RRC reconfiguration message, or triggers the BSR report when there are available physical uplink shared channel (PUSCH) resources.

[0190] In the first or second manner described above, the MAC layer does not trigger a random access process or a BSR according to the RRC reconfiguration message of the first UE.

[0191] In this embodiment, when the first UE does not perform random access or suspend random access in the switching process, the first UE can use at least one of the above-mentioned first method, second method and third method to feedback the RRC reconfiguration completion message to the network side to implement the switching process.

[0192] In some implementations, the first UE may determine, based on applicable rules of at least one of the first, second, and third methods, which method to apply in an actual application scenario to feed back an RRC reconfiguration completion message to the network side.

[0193] Optionally, the first UE sends an RRC reconfiguration complete message of the first UE in one of the following ways, including at least one of the following:

[0194] In a case where the RRC reconfiguration message of the first UE includes the second resource, the first UE sends an RRC reconfiguration complete message of the first UE in the first manner;

[0195] In a case where the RRC reconfiguration message of the first UE does not include the second resource, the first UE sends an RRC reconfiguration complete message of the first UE in the second manner;

[0196] In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the first UE sends the RRC reconfiguration complete message of the first UE through the third manner.

[0197] For example: if the RRC reconfiguration message of UE2 carries the RRC reconfiguration message of UE1 in the form of a container, the RRC reconfiguration complete message of UE1 is sent in the third manner;

[0198] If the RRC reconfiguration message of UE1 carries the second resource, the RRC reconfiguration complete message of UE1 is sent in the first manner;

[0199] If the RRC reconfiguration message of UE1 does not carry the second resource, and the RRC reconfiguration message of UE1 is not carried in the RRC reconfiguration message of UE2, the RRC reconfiguration complete message of UE1 is sent in the second manner.

[0200] As an optional implementation, the method further includes:

[0201] When the first UE determines that the second UE has not successfully completed random access within a preset time or a preset number of times, the first UE initiates random access.

[0202] In some implementations, the preset time or preset number may be indicated by a network-side device, agreed upon in a protocol, or determined based on terminal settings, and is not specifically limited herein.

[0203] In this embodiment, in a scenario where a first UE and a second UE perform the same handover procedure, if the second UE fails to successfully complete random access within a preset time or a preset number of times, the first UE may initiate random access. Thereafter, if the first UE successfully completes random access, the second UE may not perform or suspend random access in the handover procedure.

[0204] In some implementations, the preset duration may be measured based on a timer.

[0205] Optionally, when the first UE determines that the second UE has not successfully completed random access within a preset time period, the first UE initiates random access, including:

[0206] When the first timer times out, if the first UE determines that the second UE has not successfully completed random access, the first UE initiates random access, wherein the start time of the first timer is the time when the first UE determines not to perform or suspend random access, and the first timer stops when the second UE successfully completes random access.

[0207] For example, assuming that the first UE is UE1 and the second UE is UE2, and UE1 and UE2 perform the same handover process, UE1 can suspend (pending) random access when receiving synchronization reconfiguration. At the same time, the UE does not start the T304 timer, but starts the first timer. During the running of the first timer, if UE2's random access is completed, UE1 stops the first timer; if the first timer times out, UE1 initiates random access. Optionally, when UE1 initiates random access, timer T304 is started.

[0208] Scenario 3: The first UE obtains uplink synchronization based on the second UE, and the uplink synchronization maintenance process of the first UE is omitted.

[0209] As an optional implementation, the method further includes:

[0210] The first UE receives first indication information from a network-side device, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE.

[0211] In some embodiments, the first indication information can be used to indicate that the first UE and the second UE share a timing advance (TA) parameter, so that the second UE can perform an uplink synchronization maintenance process to obtain the TA parameter and restart the time advance timer (TAT) of the second UE according to the TA parameter; the first UE does not perform the uplink synchronization maintenance process, but obtains the TA parameter of the second UE to restart the TAT of the first UE according to the TA parameter.

[0212] In some implementations, the first indication information is carried in a timing advance command (TAC).

[0213] For example: the second UE performs an uplink synchronization maintenance process to receive a TAC from the network side. The TAC includes a first indication information and a TA parameter, so that the first UE and the second UE adjust the TA according to the TA parameter and restart their respective TATs, thereby eliminating the need for the first UE to receive the TAC from the network side, saving network resources.

[0214] In some embodiments, the network side device can actively send a first indication message to the first UE when knowing the association relationship between the first UE and the second UE, so as to instruct the first UE to perform uplink synchronization based on the second UE, that is, to instruct the first UE to simplify the uplink synchronization maintenance process.

[0215] In other implementations, the network-side device may send the first indication information to the first UE based on a request of the first UE.

[0216] Optionally, before the first UE receives the first indication information from the network side device, the method further includes:

[0217] The first UE sends a first request message to the network side device, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

[0218] In some implementations, the first request message may carry identification information of the second UE, such as C-RNTI.

[0219] In this implementation, the uplink synchronization maintenance process of the first UE may be simplified based on the request of the first UE.

[0220] It should be noted that, in some possible implementations, the first UE may receive a TAC based on its own C-RNTI. For example, when the second UE is not in an RRC connected state, the first UE uses the TA parameters in the TAC it received to perform uplink synchronization operations.

[0221] As an optional implementation manner, the performing uplink synchronization based on the second UE includes:

[0222] Based on the second UE, the first UE performs at least one of the following:

[0223] Determining uplink synchronization information of the first UE, such as a TA parameter, according to the uplink synchronization information of the second UE;

[0224] Maintaining an uplink synchronization time advance timer TAT of the first UE according to a timing advance TA parameter in a timing advance command TAC of the second UE;

[0225] Determining whether the first UE is in an uplink synchronization state;

[0226] Determine whether the first UE initiates random access when the TAT times out and uplink or downlink data arrives at the first UE.

[0227] In some implementations, when the first UE performs uplink synchronization based on the second UE, if the second UE is in an uplink synchronization state, it can be determined that the first UE is in an uplink synchronization state.

[0228] In some embodiments, when the first UE performs uplink synchronization based on the second UE, if the TAT of the first UE times out and uplink or downlink data arrives for the first UE, the first UE determines whether to initiate random access based on the state of the second UE. For example, if the second UE initiates random access, the first UE determines not to perform or suspend random access. For another example, if the second UE does not initiate random access (for example, if the second UE loses uplink synchronization but no uplink data arrives, random access will not be triggered) or receives an RRC connection release message or enters an RRC non-connected state, the first UE initiates random access.

[0229] Optionally, when the second UE is in an uplink synchronization state or an RRC connection state, it can send a request message to the network side to request the network side to allocate uplink or downlink resources, or C-RNTI, to the first UE. In this way, the terminal can use the uplink or downlink resources allocated by the network side to transmit the uplink or downlink data of the first UE, or the terminal can use the C-RNTI allocated by the network side to monitor the network side scheduling to transmit the uplink or downlink data of the first UE.

[0230] As an optional implementation, the method further includes:

[0231] The first UE sends first capability information to a network side device, where the first capability information indicates that the first UE supports association operations with the second UE.

[0232] In some embodiments, the network side device can know that the first UE supports association operations with the associated terminal based on the capability information of the first UE, so that after determining the second UE associated with the first UE, the network side device can configure the first UE to apply the uplink synchronization of the associated second UE, such as sending a first indication information to the first UE, or the network side can configure the first UE not to perform or suspend random access in the first process.

[0233] In an embodiment of the present application, when a first UE is associated with a second UE, the first UE performs uplink synchronization based on the second UE, or the first UE does not perform random access or suspends random access in a first process, and the first process includes at least one of the following: a radio resource control RRC connection establishment process; an RRC connection recovery process; an RRC connection reestablishment process; a switching process. When a first UE is associated with a second UE, when the first UE initiates initial access, switching, RRC connection reestablishment, uplink synchronization maintenance, etc., if the second UE it is associated with has completed a random access (Random Access Channel, RAC) process or is initiating a random access process or has established uplink synchronization, the terminal can perform uplink synchronization based on the associated terminal, or omit the random access process. In this way, the problem of network-side resource waste and long control plane delay on the terminal side caused by the first UE and the second UE performing the random access process or the uplink synchronization maintenance process respectively can be reduced.

[0234] Referring to FIG5 , an embodiment of the present application provides a UE control method performed by a second UE, including the following steps:

[0235] Step 501: When a second UE is in an RRC connected state and is associated with a first UE, the second UE performs one of the following:

[0236] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a cell radio network temporary identifier C-RNTI or a first resource to the first UE;

[0237] Sending the C-RNTI of the first UE to a network-side device;

[0238] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0239] In an embodiment of the present application, the UE control method executed by the second UE corresponds to the UE control method executed by the first UE in the method embodiment shown in Figure 2, and the UE control method executed by the second UE is used to assist the first UE in simplifying the uplink synchronization maintenance process or random access in the first process.

[0240] Optionally, the second UE includes at least one of the following:

[0241] a UE corresponding to a different universal subscriber identity module (USIM) card in the same device as the first UE;

[0242] UEs corresponding to different registrations in the same device as the first UE.

[0243] Scenario 1: The second UE assists the first UE in not performing or suspending random access during the initial access or RRC connection reestablishment process.

[0244] In some embodiments, the second UE can send a second request message to the network side device to enable the network side device to allocate a C-RNTI or a first resource to the first UE. Thereafter, the first UE can use the first resource to interact with the network side device for data or signaling to simplify the random access process in the first process, or the first UE can use the C-RNTI to monitor the network side scheduling, and use the monitored network side scheduling resources to interact with the network side device for data or signaling to simplify the random access process in the first process.

[0245] Optionally, the C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following:

[0246] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0247] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0248] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0249] Optionally, after the second UE sends the second request message to the network side device, the method further includes:

[0250] The second UE receives a first response message from the network side device, wherein the first response message carries the C-RNTI of the first UE or the first resource, or,

[0251] The second UE receives a second response message from the network side device, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

[0252] In one implementation, the network side may allocate a C-RNTI or the first resource to the first UE according to the first request message sent by the second UE. At this time, the network side sends a first response message to the second UE.

[0253] In another embodiment, the network side may instruct the first UE to enter access backoff based on the first request message sent by the second UE (for example, the network side is currently in a congested or resource-scarce state). At this time, the network side sends a second response message to the second UE, so that the second UE performs backoff according to the target backoff time, and after the target backoff time arrives, sends the first request message again, and repeats this cycle until the first UE receives the first response message, and performs the first operation according to the C-RNTI or the first resource received by the second UE, or until the first UE initiates random access. Optionally, the backoff time may be a protocol agreement, or indicated by the network side, or determined by the terminal itself. The backoff time may be a determined value, or a random number within a determined interval, or a value determined according to a predefined algorithm, which is not specifically limited here.

[0254] For example: when the first UE determines not to perform or suspend random access, it starts the second timer. During the operation of the second timer, if the first UE obtains the C-RNTI or the first resource from the second UE, the first UE stops the second timer; if the second timer times out, the first UE initiates random access.

[0255] Optionally, the second request message also includes a reason why the first UE establishes or restores the RRC connection. In this way, the network side can determine whether to send the first response message or the second response message based on the reason why the first UE initiates the RRC connection.

[0256] Optionally, before the second UE sends the second request message to the network side device, the method further includes:

[0257] A first configuration is received, where the first configuration instructs the network-side device to allow the second UE to send the second request message.

[0258] In this implementation, the second UE may send a second request message based on network side configuration.

[0259] Of course, in other implementations, the second UE may send the second request message when it has an associated first UE, which is not specifically limited here.

[0260] Scenario 2: The second UE assists the first UE in not executing or suspending random access in the handover process.

[0261] In some embodiments, the second UE sends the C-RNTI of the first UE to the network side device, so that the network side device can be informed of the association relationship between the first UE and the second UE, thereby configuring the first UE to use the uplink synchronization of the second UE or configuring the first UE not to perform or suspend random access in the first process.

[0262] Optionally, the network side can allocate dynamic scheduling resources to the first UE based on the C-RNTI received from the first UE, so that the first UE can monitor the network side scheduling based on the C-RNTI to realize information or signaling interaction with the network side and implement the switching process.

[0263] Optionally, before the second UE sends the C-RNTI of the first UE to the network side device, the method further includes:

[0264] The second UE receives a second configuration, where the second configuration instructs the network-side device to allow or request the second UE to send the C-RNTI of the first UE.

[0265] Optionally, the second configuration may be carried in an RRC reconfiguration message of the second UE.

[0266] In this implementation manner, the second UE may send the C-RNTI of the first UE to the network side based on the network side configuration.

[0267] Of course, in some other implementations, the second UE may send the C-RNTI of the first UE to the network side when it has an associated first UE, which is not specifically limited here.

[0268] In some other implementations, in the handover process, the RRC reconfiguration message received by the second UE may carry the RRC reconfiguration message of the first UE, so that the first UE may be omitted from independently receiving the RRC reconfiguration message.

[0269] Correspondingly, when the RRC reconfiguration message received by the second UE carries the RRC reconfiguration message of the first UE, the RRC reconfiguration completion message sent by the second UE may also carry the RRC reconfiguration completion message of the first UE, so as to simplify the process of the first UE obtaining resources for sending the RRC reconfiguration completion message through a random access process.

[0270] Optionally, the method further includes:

[0271] The second UE receives a third configuration, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource;

[0272] In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resource; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resource.

[0273] In some embodiments, when the second configuration is carried in the RRC reconfiguration message of the second UE to request the second UE to report the information of the associated first UE, the second UE reports the C-RNTI of the first UE to the network side. The C-RNTI of the first UE can be reported through the RRC reconfiguration completion message of the second UE, or through UE Assistance Information (UAI).

[0274] Among them, if the C-RNTI of the first UE is reported using the RRC reconfiguration completion message of the second UE, the uplink resources scheduled by the network side specifically for the RRC reconfiguration completion message of the second UE may be insufficient, which may cause the failure of sending the RRC reconfiguration completion message of the second UE.

[0275] In this embodiment, two sets of RACH resources are configured for the second UE through the third configuration. The first RACH resource meets the second UE's transmission requirements for an RRC Reconfiguration Complete message that includes the first UE's C-RNTI, and the second RACH resource meets the second UE's transmission requirements for an RRC Reconfiguration Complete message that does not include the first UE's C-RNTI. In this way, when the second UE needs to send the first UE's C-RNTI, the first RACH resource can be used to transmit the RRC Reconfiguration Complete message; when the second UE does not need to send the first UE's C-RNTI, the second RACH resource can be used to transmit the RRC Reconfiguration Complete message. In this way, the third configuration can improve the reliability of the second UE's reporting of the RRC Reconfiguration Complete message.

[0276] Optionally, the method further includes:

[0277] The second UE sends second capability information to the network side device, where the second capability information indicates that the second UE supports association operations with the first UE.

[0278] In some embodiments, the network side device can know that the second UE supports association operations with the associated terminal based on the capability information of the second UE, so that after determining the first UE associated with the second UE, the second UE can be configured to assist the first UE in simplifying the uplink synchronization maintenance process or simplifying the random access in the first process.

[0279] Referring to FIG6 , the UE configuration method provided in an embodiment of the present application is executed by a network-side device. As shown in FIG6 , the UE configuration method includes the following steps:

[0280] Step 601: The network-side device performs a second operation, where the second operation includes at least one of the following:

[0281] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0282] receiving a cell radio network temporary identifier (C-RNTI) of the first UE from the second UE;

[0283] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0284] The first UE is associated with the second UE.

[0285] Scenario 1: The network side allocates a C-RNTI or a first resource to the first UE, so that the first UE does not perform or suspend random access in the initial access or RRC connection reestablishment process based on the C-RNTI or the first resource.

[0286] Optionally, the method further includes:

[0287] The network-side device receives a second request message from the second UE, wherein the second request message is used to request the network-side device to allocate the C-RNTI or the first resource to the first UE.

[0288] Optionally, before the network side device receives the second request message from the second UE, the method further includes:

[0289] The network-side device sends a first configuration to the second UE, where the first configuration instructs the network-side device to allow the second UE to send the second request message.

[0290] Optionally, after the network side device receives the second request message from the second UE, the method further includes:

[0291] The network-side device sends a first response message to the second UE, wherein the first response message carries the C-RNTI of the first UE or the first resource; or

[0292] The network side device sends a second response message to the second UE, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

[0293] Optionally, the second request message also includes the reason why the first UE establishes or restores the radio resource control RRC connection.

[0294] Optionally, the C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following:

[0295] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0296] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0297] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0298] Scenario 2: The network side receives the C-RNTI of the first UE sent by the second UE, so that the network side can know the association relationship between the first UE and the second UE, so that the random access process of the first UE can be simplified based on the second UE in the switching process.

[0299] Optionally, before the network-side device receives the C-RNTI of the first UE from the second UE, the method further includes:

[0300] The network-side device sends a second configuration to the second UE, where the second configuration instructs the network-side device to allow or request the second UE to send the C-RNTI of the first UE.

[0301] Optionally, the receiving the C-RNTI of the first UE from the second UE includes:

[0302] An RRC reconfiguration complete message or auxiliary information UAI of the second UE is received from the second UE, wherein the RRC reconfiguration complete message or UAI of the second UE includes the C-RNTI of the first UE.

[0303] Optionally, after receiving an RRC reconfiguration complete message or auxiliary information UAI of the second UE from the second UE, the method further includes:

[0304] The network side device sends an RRC reconfiguration message of the first UE or an RRC reconfiguration message of the second UE, wherein the RRC reconfiguration message of the first UE does not carry a synchronization reconfiguration parameter; or, the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE; or, the RRC reconfiguration message of the first UE carries a second resource, and the second resource is used by the first UE to report an RRC reconfiguration completion message to the network side device.

[0305] Optionally, the method further includes:

[0306] The network-side device receives the RRC reconfiguration complete message of the first UE in one of the following ways, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE:

[0307] In a fourth manner, the network-side device receives an RRC reconfiguration complete message of the first UE on the second resource allocated to the first UE;

[0308] In a fifth manner, the network-side device receives an RRC reconfiguration complete message of the first UE on the dynamically scheduled resources;

[0309] In a sixth manner, the network side device receives an RRC reconfiguration completion message of the second UE, wherein the RRC reconfiguration completion message of the second UE carries an RRC reconfiguration completion message of the first UE.

[0310] Optionally, the network-side device receives the RRC reconfiguration complete message of the first UE in one of the following ways, including at least one of the following:

[0311] In a case where the RRC reconfiguration message of the first UE includes the second resource, the network-side device receives the RRC reconfiguration complete message of the first UE through the fourth manner;

[0312] In a case where the RRC reconfiguration message of the first UE does not include the second resource, the network-side device receives the RRC reconfiguration complete message of the first UE through the fifth manner; or,

[0313] In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the network-side device receives the RRC reconfiguration completion message of the first UE through the sixth method.

[0314] Optionally, the method further includes:

[0315] The network side device sends a third configuration to the second UE, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource;

[0316] In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resource; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resource.

[0317] Optionally, the method further includes:

[0318] The network-side device sends or receives a handover request message, where the handover request message includes the C-RNTI of the first UE and the C-RNTI of the second UE.

[0319] In some implementations, the network-side device may include at least one of a source base station and a target base station in a handover process.

[0320] For example: assuming that the first UE is UE1 and the second UE is UE2, UE1 and UE2 are UE entities corresponding to two SIM cards in the same device and belonging to the same operator, then UE1 and UE2 are in the connected state and reside in the same source service cell. At this time, UE2 receives the second configuration sent by the network side, which is used to request or allow the UE2 to report the information of the associated UE (i.e., the C-RNTI of UE1). Based on the second configuration, UE2 can report the C-RNTI of UE1 to the source base station, for example, through UAI reporting. At this time, if the switching process is triggered, UE1 and UE2 will switch to the same target base station. At this time, the source base station can send a switching request message to the target base station, and the switching request message carries the C-RNTI of UE2 and UE1, so that the target base station obtains the association relationship between UE2 and UE1. The target base station sends a switching request response message to the source base station, which includes an RRC reconfiguration message to UE2 and an RRC reconfiguration message to UE1.

[0321] Optionally, the method further comprises at least one of the following:

[0322] The network-side device configures the first UE not to perform random access or to suspend random access in the first process;

[0323] The network side device configures the first UE to obtain uplink synchronization based on the second UE;

[0324] The first process includes at least one of the following:

[0325] Radio Resource Control RRC connection establishment process;

[0326] RRC connection recovery process;

[0327] RRC connection reestablishment process;

[0328] Switch process.

[0329] Scenario 3: The network side instructs the first UE to obtain uplink synchronization based on the second UE, and omits the uplink synchronization maintenance process of the first UE.

[0330] Optionally, before the network side device sends the first indication information to the first UE, the method further includes:

[0331] The network-side device receives a first request message from the first UE, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

[0332] Optionally, the first indication information is carried in a timing advance command TAC.

[0333] Optionally, the method further comprises at least one of the following:

[0334] The network-side device receives first capability information from the first UE, where the first capability information indicates that the first UE supports an association operation with the second UE;

[0335] The network-side device receives second capability information from the second UE, where the second capability information indicates that the second UE supports association operations with the first UE.

[0336] It should be noted that the implementation method of the above-mentioned network-side device receiving capability information from at least one of the first UE and the second UE can be applied to any scenario in the above scenario one, scenario two and scenario three, and is not specifically limited here.

[0337] To facilitate understanding of the UE control method and UE configuration method provided in the embodiments of the present application, the UE control method and UE configuration method provided in the embodiments of the present application are illustrated by the following four embodiments, taking the first UE as UE1, the second UE as UE2, and UE1 and UE2 as UE entities corresponding to two SIM cards of the same operator on the same mobile phone as an example:

[0338] Example 1

[0339] Simplifying the random access process of UE1 in the initial access or RRC connection re-establishment process includes the following steps:

[0340] Step 1: UE2 is in an RRC connected state and receives a second configuration, where the second configuration is used to request or allow UE2 to send MUSIM auxiliary information of the same operator.

[0341] Optionally, the MUSIM auxiliary information of the same operator is auxiliary information related to an associated terminal in an idle or deactivated (IDLE / INACTIVE) state, such as the C-RNTI of UE1.

[0342] Step 2: UE1 initiates an RRC connection establishment process in the RRC IDLE state. If UE1 determines that its associated UE (ie, UE2) is in an uplink synchronization state, or obtains uplink synchronization from the associated UE, the random access process is suspended.

[0343] Step 3: UE2 sends a first request message to the network (e.g., via UAI), where the first request message is used to request at least one of the following:

[0344] Request the network side device to allocate a UE identifier, such as C-RNTI, to UE1;

[0345] Request the network-side device to allocate uplink resources to UE1, where the uplink resources are used by UE1 to send an RRC connection establishment request message;

[0346] Optionally, the first request message may further indicate the reason for establishing the RRC connection of UE1.

[0347] Step 4: UE2 receives a response message (such as an RRC reconfiguration message) from the network side to the first request message, where the response message indicates at least one of the following:

[0348] UE1's C-RNTI;

[0349] Uplink resources used for UE1 to send an RRC connection establishment request message;

[0350] Instruct UE2 to back off (for example, due to resource shortage on the network side).

[0351] Step 5:

[0352] 1) If uplink resources are obtained in step 4, UE1 sends an RRC connection establishment request message on the uplink resources.

[0353] 2) If no uplink resources are obtained in step 4, UE1 uses the C-RNTI in step 4 to monitor dynamic resource scheduling to obtain resources for sending the RRC connection establishment request message.

[0354] 3) If UE2 is instructed to back off in step 4, UE2 randomly selects a back off time or performs back off according to the back off time indicated by the network side. After the back off time expires, UE2 performs step 3 again.

[0355] 4) If UE2 does not receive the response message in step 4 within a preset time, UE1 initiates random access.

[0356] Optionally, in step 2, when UE1 is pending random access, a timer is started. If the timer times out, UE1 initiates random access. During the timer running, UE1 obtains a C-RNTI from an associated UE, and the UE stops the timer.

[0357] Step 6: UE1 receives the RRC connection establishment message.

[0358] Step 7: UE1 sends an RRC connection establishment complete message.

[0359] It should be noted that in the above embodiment 1, the RRC connection establishment process of UE1 is used as an example for explanation. In some embodiments, the interaction process in the above RRC connection establishment process is also applicable to the RRC connection reestablishment process, such as replacing the above RRC connection establishment request, RRC connection establishment message, and RRC connection establishment complete message with RRC connection recovery request, RRC connection recovery message, and RRC connection recovery complete message, and replacing the RRC connection establishment cause with the RRC connection recovery cause. In this way, the process of the above embodiment 1 can be used to simplify the random access of UE1 in initiating the RRC connection recovery process.

[0360] Example 2

[0361] During mobility, UE1 and UE2 often switch from the same source cell to the same target cell. During this handover, the UE initiates a random access request to the target base station to obtain uplink synchronization. Since both SIM cards are in the same phone, their uplink synchronization is identical. Therefore, only one SIM card needs to perform the random access request, while the other SIM card is not required to perform the random access request.

[0362] Specifically, the random access of UE1 in the handover process can be simplified by the following steps:

[0363] Step 1: UE2 and UE1 are in connected state and reside in the same serving cell.

[0364] Step 2: UE2 receives a second configuration sent by the network side, where the second configuration is used to request or allow the UE to report information of associated UEs, such as reporting the C-RNTI of UE1.

[0365] Step 3: UE2 reports the C-RNTI of UE1 to the network side, for example, through UAI reporting.

[0366] Optionally, after receiving the C-RNTI of UE1 reported by UE2, if the handover process is triggered, the source base station may send a handover request message to the target base station, where the handover request message carries the C-RNTIs of UE2 and UE1, so that the target base station obtains the association relationship between UE2 and UE1. The target base station sends a handover request response message to the source base station, which includes an RRC reconfiguration message for UE2 and an RRC reconfiguration message for UE1.

[0367] Step 4: UE2 receives a handover command, which is an RRC reconfiguration message generated by the target base station. The RRC reconfiguration message carries synchronization reconfiguration parameters, triggering UE2 to initiate random access to the target cell.

[0368] Step 5: UE1 receives the handover command, i.e., the RRC reconfiguration message generated by the target base station. If the RRC reconfiguration message does not include the synchronization reconfiguration parameter, UE1 does not initiate random access to the target cell.

[0369] Step 6: After UE2 completes random access, UE1 acquires uplink synchronization based on UE2 and sends an RRC reconfiguration complete message to the network in the following manner:

[0370] Method 1: Send an RRC reconfiguration complete message on the uplink resources configured in the RRC reconfiguration message in step 5;

[0371] Method 2: The RRC layer monitors the scheduling of the target base station based on the C-RNTI in the RRC reconfiguration message and sends an RRC reconfiguration complete message on the uplink resources scheduled by the base station. Specifically, the RRC layer passes the RRC reconfiguration complete message to the MAC layer, which does not trigger random access or BSR.

[0372] Method 3: UE2 places UE1's RRC reconfiguration complete message in its own RRC reconfiguration complete message in the form of a container and sends the message to the network side.

[0373] Optionally, if the RRC reconfiguration message of UE2 carries the RRC reconfiguration message of UE1 in the form of a container, the RRC reconfiguration complete message of UE1 is sent in mode 3.

[0374] Optionally, UE1 determines whether to use Method 1, Method 2, or Method 3 based on the content of the RRC reconfiguration message. Specifically, if UE1's RRC reconfiguration message includes a configured grant for uplink resources, Method 1 is used; if UE1's RRC reconfiguration message is transparently transmitted in the form of a container, Method 3 is used; if UE1's RRC reconfiguration message does not include a configured grant for uplink resources and UE1's RRC reconfiguration message is not transparently transmitted in the form of a container, Method 2 is used.

[0375] Example 3:

[0376] The following steps are used to simplify the random access of UE1 in the handover process:

[0377] Step 0: UE2 and UE1 each indicate that they support dual-SIM association when reporting UE capabilities.

[0378] Step 1: UE2 and UE1 are in connected state and reside in the same serving cell.

[0379] Step 2: The current serving cell does not support dual-SIM association, so UE2 and UE1 work independently in the current cell;

[0380] In a mobile scenario, in this step, based on the measurement results of UE2 and UE1, the source base station sends a handover request command to the target base station for UE2 and UE1 respectively. When preparing the handover command, the target base station can know based on the UE capability information that UE2 and UE1 support dual-SIM association operation, but does not know the associated UEs of each. Therefore, the target base station performs independent handover operations for UE2 and UE1 while configuring the UEs to report possible association information.

[0381] Step 3: UE2 and UE1 receive the RRC reconfiguration message generated by the target base station for each of them, which carries the synchronization reconfiguration parameter.

[0382] Step 4a: UE1 may not initiate random access to the target cell if the following conditions are met:

[0383] 1) UE2 has established uplink synchronization or completed random access;

[0384] 2) UE1 is configured not to initiate random access, or is configured to apply uplink synchronization of the associated UE.

[0385] Optionally, when UE1 receives synchronization reconfiguration, UE1 is pending random access. If the associated UE fails to successfully complete random access within a preset time and a preset number of times, UE1 initiates random access. Specifically, when the UE is pending random access, the UE does not start the T304 timer. A first timer is started. If UE2 completes random access during the running of the first timer, UE1 stops the first timer. If the first timer expires, UE1 initiates random access.

[0386] Step 4b: For UE2, if the RRC reconfiguration message requests the UE to report the information of the associated UE, UE2 reports the C-RNTI of UE1.

[0387] Optionally, UE1's C-RNTI can be reported via UE2's RRC Reconfiguration Complete message or via UAI. If UE2's RRC Reconfiguration Complete message is used, the network-scheduled uplink resources for UE2's RRC Reconfiguration Complete message may be insufficient. To address this issue, the target base station can configure two sets of RACH resources for UE2. If UE2 does not need to send UE1's C-RNTI, the second set of RACH resources is used; otherwise, the first set of RACH resources is used.

[0388] Step 5: UE1 monitors the scheduling of the target cell based on the C-RNTI to send an RRC reconfiguration complete message.

[0389] Example 4:

[0390] The following steps simplify the uplink synchronization maintenance process of UE1:

[0391] Step 1: UE2 and UE1 are in connected state and reside in the same serving cell.

[0392] Step 2: UE1 receives first indication information, where the first indication information instructs UE1 and UE2 to share TA parameters.

[0393] It should be noted that, before step 2, the network side needs to know the association relationship between UE2 and UE1, such as UE2 reporting the R-RNTI of UE1.

[0394] Step 3: At some point, UE2 receives the TAC, and UE2 and UE1 apply the parameters in the TAC and restart their respective TATs.

[0395] Optionally, the first indication information may be carried in a TAC.

[0396] Step 4: When UE1 receives a TAC using its own C-RNTI (such as UE2 leaving the connected state), the TA value in the TAC is applied.

[0397] The UE control method provided in the embodiment of the present application may be executed by a UE control device. In the embodiment of the present application, the UE control device provided in the embodiment of the present application is described by taking the UE control method executed by the UE control device as an example.

[0398] Referring to FIG7 , an embodiment of the present application provides a UE control device, which may be a device corresponding to a first UE. As shown in FIG7 , the UE control device 700 includes the following modules:

[0399] The first execution module 701 is configured to, when the first UE is associated with a second UE, perform uplink synchronization based on the second UE, or not perform random access or suspend random access in a first process, where the first process includes at least one of the following:

[0400] Radio Resource Control RRC connection establishment process;

[0401] RRC connection recovery process;

[0402] RRC connection reestablishment process;

[0403] Switch process.

[0404] Optionally, the second UE includes at least one of the following:

[0405] a UE corresponding to a different universal subscriber identity module (USIM) card in the same device as the first UE;

[0406] UEs corresponding to different registrations in the same device as the first UE.

[0407] Optionally, the first execution module 701 is configured to:

[0408] In a case where the first UE is configured to obtain uplink synchronization based on the second UE, or in a case where the first UE is configured not to perform random access or suspend random access in the first process, random access is not performed or suspended in the first process.

[0409] Optionally, when the first process is an RRC connection establishment process or an RRC connection recovery process, the first execution module 701 is specifically configured to:

[0410] When at least one of the following conditions is met, random access is not performed or is suspended in the first procedure:

[0411] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0412] The first UE and the second UE have related transmission beams;

[0413] The first UE and the second UE have the same serving cell;

[0414] The second UE is in an RRC connected state, or is establishing an RRC connection, or is restoring an RRC connection.

[0415] Optionally, when the first execution module 701 does not perform random access or suspend random access in the first process, and the first process is an RRC connection establishment process or an RRC connection recovery process, the UE control device 700 further includes:

[0416] A fourth execution module is configured to complete a first operation on a first resource, or to monitor network scheduling according to a cell radio network temporary identifier C-RNTI configured on the network side to complete the first operation, where the first operation includes at least one of the following:

[0417] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0418] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0419] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0420] Optionally, the UE control device 700 further includes:

[0421] The first acquisition module is configured to acquire the C-RNTI of the first UE or the first resource from the second UE.

[0422] Optionally, the fourth execution module is configured to:

[0423] If the first acquisition module fails to acquire the first resource, it monitors network scheduling according to the C-RNTI to complete the first operation.

[0424] Optionally, the UE control device 700 further includes:

[0425] The first random access module is configured to initiate random access starting from the moment when the first execution module 701 determines not to perform random access or suspend random access in the first process, if the first acquisition module fails to acquire the first resource or the C-RNTI within a preset time.

[0426] Optionally, when the first process is a switching process, the first execution module 701 is configured to:

[0427] When at least one of the following conditions is met, random access is not performed or random access is suspended in the first process:

[0428] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0429] The first UE and the second UE have related transmission beams;

[0430] The second UE is in an RRC connected state;

[0431] The serving cell after the switching of the first UE is the same as the current or switched serving cell of the second UE;

[0432] The second UE is performing a handover procedure or has completed the handover procedure;

[0433] The RRC reconfiguration message received by the first UE for performing handover does not carry a synchronization reconfiguration parameter.

[0434] Optionally, when the first execution module 701 does not perform random access or suspend random access in the first process, and the first process is a handover process, the UE control device 700 further includes:

[0435] A first sending module is configured to send an RRC reconfiguration complete message of the first UE in one of the following ways, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE:

[0436] In a first manner, an RRC reconfiguration complete message of the first UE is sent on a second resource allocated by a network side device to the first UE;

[0437] In a second manner, monitoring network scheduling according to the C-RNTI of the first UE to send an RRC reconfiguration complete message of the first UE;

[0438] A third method is to carry the RRC reconfiguration complete message of the first UE in the RRC reconfiguration complete message of the second UE and send it.

[0439] Optionally, the first sending module is configured to perform at least one of the following:

[0440] When the RRC reconfiguration message of the first UE includes the second resource, sending an RRC reconfiguration complete message of the first UE in the first manner;

[0441] When the RRC reconfiguration message of the first UE does not include the second resource, sending an RRC reconfiguration complete message of the first UE in the second manner;

[0442] In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the RRC reconfiguration complete message of the first UE is sent through the third method.

[0443] Optionally, when the RRC reconfiguration complete message of the first UE is sent through the first method or the second method, the UE control device 700 further includes:

[0444] A processing module is used to transmit the RRC reconfiguration message of the first UE to the media access control MAC layer, wherein the MAC layer does not trigger a random access process or a buffer status report BSR according to the RRC reconfiguration message of the first UE.

[0445] Optionally, the UE control device 700 further includes:

[0446] The second random access module is configured to initiate random access if it is determined that the second UE has not successfully completed random access within a preset time or a preset number of times.

[0447] Optionally, the second random access module is configured to:

[0448] When the first timer times out, if it is determined that the second UE has not successfully completed random access, random access is initiated, wherein the start time of the first timer is the time when the first UE determines not to perform or suspend random access, and the first timer is stopped when the second UE successfully completes random access.

[0449] Optionally, the UE control device 700 further includes:

[0450] The first receiving module is used to receive first indication information from a network side device, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE.

[0451] Optionally, the UE control device 700 further includes:

[0452] The second sending module is used to send a first request message to the network side device, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

[0453] Optionally, the first indication information is carried in a timing advance command TAC.

[0454] Optionally, the first execution module 701 is configured to:

[0455] Based on the second UE, perform at least one of the following:

[0456] Determining the uplink synchronization information of the first UE according to the uplink synchronization information of the second UE;

[0457] Maintaining the uplink synchronization TAT of the first UE according to the TA parameter in the TAC of the second UE;

[0458] Determining whether the first UE is in an uplink synchronization state;

[0459] Determine whether to initiate random access when the TAT times out and uplink or downlink data arrives for the first UE.

[0460] Optionally, the UE control device 700 further includes:

[0461] The third sending module is used to send first capability information to the network side device, where the first capability information indicates that the first UE supports the association operation with the second UE.

[0462] Referring to FIG8 , an embodiment of the present application provides a UE control device, which may be a device corresponding to a second UE. As shown in FIG8 , the UE control device 800 includes the following modules:

[0463] The second execution module 801 is configured to, when the second UE is in a radio resource control (RRC) connected state and is associated with the first UE, execute one of the following:

[0464] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a cell radio network temporary identifier C-RNTI or a first resource to the first UE;

[0465] Sending the C-RNTI of the first UE to a network-side device;

[0466] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0467] Optionally, the second UE includes at least one of the following:

[0468] a UE corresponding to a different universal subscriber identity module (USIM) card in the same device as the first UE;

[0469] UEs corresponding to different registrations in the same device as the first UE.

[0470] Optionally, the C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following:

[0471] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0472] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0473] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0474] Optionally, the UE control device 800 further includes:

[0475] a second receiving module, configured to receive a first response message from the network-side device, wherein the first response message carries the C-RNTI of the first UE or the first resource, or

[0476] The third receiving module is used to receive a second response message from the network side device, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

[0477] Optionally, the second request message also includes the reason why the first UE establishes or restores the RRC connection.

[0478] Optionally, the UE control device 800 further includes:

[0479] The fourth receiving module is used to receive a first configuration, where the first configuration instructs the network side device to allow the second UE to send the second request message.

[0480] Optionally, the UE control device 800 further includes:

[0481] The fifth receiving module is used to receive a second configuration, where the second configuration instructs the network side device to allow or request the second UE to send the C-RNTI of the first UE.

[0482] Optionally, the UE control device 800 further includes:

[0483] A sixth receiving module, configured to receive a third configuration, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource;

[0484] In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resource; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resource.

[0485] Optionally, the UE control device 800 further includes:

[0486] The fourth sending module is used to send second capability information to the network side device, where the second capability information indicates that the second UE supports association operations with the first UE.

[0487] The UE control device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0488] The UE control device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment shown in Figure 2 or Figure 5, and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0489] The UE configuration method provided in the embodiment of the present application can be executed by a UE configuration device. In the embodiment of the present application, the UE configuration device provided in the embodiment of the present application is described by taking the UE configuration method executed by the UE configuration device as an example.

[0490] Referring to FIG9 , an embodiment of the present application provides a UE configuration apparatus, which may be an apparatus corresponding to a network-side device. As shown in FIG9 , the UE configuration apparatus 900 includes the following modules:

[0491] The third execution module 901 is configured to execute a second operation, where the second operation includes at least one of the following:

[0492] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0493] receiving a cell radio network temporary identifier (C-RNTI) of the first UE from the second UE;

[0494] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0495] The first UE is associated with the second UE.

[0496] Optionally, the UE configuration device 900 further includes:

[0497] A seventh receiving module is used to receive a second request message from the second UE, wherein the second request message is used to request the network side device to allocate the C-RNTI or the first resource to the first UE.

[0498] Optionally, the UE configuration device 900 further includes:

[0499] The fifth sending module is used to send a first configuration to the second UE, where the first configuration instructs the network side device to allow the second UE to send the second request message.

[0500] Optionally, the UE configuration device 900 further includes:

[0501] a sixth sending module, configured to send a first response message to the second UE, wherein the first response message carries the C-RNTI of the first UE or the first resource; or

[0502] The seventh sending module is used to send a second response message to the second UE, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

[0503] Optionally, the second request message also includes the reason why the first UE establishes or restores the radio resource control RRC connection.

[0504] Optionally, the C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following:

[0505] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0506] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0507] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0508] Optionally, the UE configuration device 900 further includes:

[0509] An eighth sending module is configured to send a second configuration to the second UE, where the second configuration instructs the network side device to allow or request the second UE to send the C-RNTI of the first UE.

[0510] Optionally, the third execution module 901 is configured to:

[0511] An RRC reconfiguration complete message or auxiliary information UAI of the second UE is received from the second UE, wherein the RRC reconfiguration complete message or UAI of the second UE includes the C-RNTI of the first UE.

[0512] Optionally, the UE configuration device 900 further includes:

[0513] A ninth sending module is used to send the RRC reconfiguration message of the first UE or the RRC reconfiguration message of the second UE, wherein the RRC reconfiguration message of the first UE does not carry a synchronization reconfiguration parameter; or, the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE; or, the RRC reconfiguration message of the first UE carries a second resource, and the second resource is used by the first UE to report an RRC reconfiguration completion message to the network side device.

[0514] Optionally, the UE configuration device 900 further includes:

[0515] an eighth receiving module, configured to receive an RRC reconfiguration complete message of the first UE in one of the following manners, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE:

[0516] In a fourth manner, the network-side device receives an RRC reconfiguration complete message of the first UE on the second resource allocated to the first UE;

[0517] In a fifth manner, the network-side device receives an RRC reconfiguration complete message of the first UE on the dynamically scheduled resources;

[0518] In a sixth manner, the network side device receives an RRC reconfiguration completion message of the second UE, wherein the RRC reconfiguration completion message of the second UE carries an RRC reconfiguration completion message of the first UE.

[0519] Optionally, the eighth receiving module is configured to perform at least one of the following:

[0520] In a case where the RRC reconfiguration message of the first UE includes the second resource, the network-side device receives the RRC reconfiguration complete message of the first UE through the fourth manner;

[0521] In a case where the RRC reconfiguration message of the first UE does not include the second resource, the network-side device receives the RRC reconfiguration complete message of the first UE through the fifth manner; or,

[0522] In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the network-side device receives the RRC reconfiguration completion message of the first UE through the sixth method.

[0523] Optionally, the UE configuration device 900 further includes:

[0524] a tenth sending module, configured to send a third configuration to the second UE, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource;

[0525] In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resource; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resource.

[0526] Optionally, the UE configuration device 900 further includes:

[0527] The transmission module is configured to send or receive a handover request message, where the handover request message includes the C-RNTI of the first UE and the C-RNTI of the second UE.

[0528] Optionally, the UE configuration apparatus 900 further includes at least one of the following:

[0529] A first configuration module, configured to configure the first UE not to perform random access or to suspend random access in a first process;

[0530] A second configuration module, configured to configure the first UE to obtain uplink synchronization based on the second UE;

[0531] The first process includes at least one of the following:

[0532] Radio Resource Control RRC connection establishment process;

[0533] RRC connection recovery process;

[0534] RRC connection reestablishment process;

[0535] Switch process.

[0536] Optionally, the UE configuration device 900 further includes:

[0537] A ninth receiving module is configured to receive a first request message from the first UE, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

[0538] Optionally, the first indication information is carried in a timing advance command TAC.

[0539] Optionally, the UE configuration apparatus 900 further includes at least one of the following:

[0540] a tenth receiving module, configured to receive first capability information from the first UE, where the first capability information indicates that the first UE supports an association operation with the second UE;

[0541] An eleventh receiving module is configured to receive second capability information from the second UE, where the second capability information indicates that the second UE supports association operations with the first UE.

[0542] The UE configuration device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment shown in Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0543] As shown in Figure 10, an embodiment of the present application also provides a communication device 1000, including a processor 1001 and a memory 1002, and the memory 1002 stores a program or instruction that can be run on the processor 1001. For example, when the communication device 1000 includes a first UE, the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in Figure 2, and can achieve the same technical effect; when the communication device 1000 includes a second UE, the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in Figure 5, and can achieve the same technical effect; when the communication device 1000 is a network side device, the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in Figure 6, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0544] An embodiment of the present application further provides a terminal, including a processor and a communication interface, wherein, when the terminal includes a first UE, the processor is configured to, when the first UE is associated with a second UE, perform uplink synchronization based on the second UE, or not perform random access or suspend random access in a first process, where the first process includes at least one of the following:

[0545] RRC connection establishment process;

[0546] RRC connection recovery process;

[0547] RRC connection reestablishment process;

[0548] Switch process; or,

[0549] When the terminal includes a second UE, the communication interface is configured to, when the second UE is in an RRC connected state and the second UE is associated with the first UE, perform one of the following:

[0550] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a C-RNTI or a first resource to the first UE;

[0551] Sending the C-RNTI of the first UE to a network-side device;

[0552] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0553] This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal implementing the embodiment of this application.

[0554] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

[0555] Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0556] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0557] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0558] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1109 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0559] Processor 1110 may include one or more processing units. Optionally, processor 1110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1110.

[0560] In one embodiment, terminal 1100 includes a first UE.

[0561] At this time, the processor 1110 is configured to, when the first UE is associated with the second UE, perform uplink synchronization based on the second UE, or not perform random access or suspend random access in a first process, where the first process includes at least one of the following:

[0562] RRC connection establishment process;

[0563] RRC connection recovery process;

[0564] RRC connection reestablishment process;

[0565] Switch process.

[0566] Optionally, the second UE includes at least one of the following:

[0567] a UE corresponding to a different universal subscriber identity module (USIM) card in the same device as the first UE;

[0568] UEs corresponding to different registrations in the same device as the first UE.

[0569] Optionally, the not performing random access or suspending random access in the first process performed by the processor 1110 includes:

[0570] In a case where the first UE is configured to obtain uplink synchronization based on the second UE, or in a case where the first UE is configured not to perform random access or suspend random access in the first process, random access is not performed or suspended in the first process.

[0571] Optionally, when the first process is an RRC connection establishment process or an RRC connection recovery process, the not performing random access or suspending random access in the first process, performed by the processor 1110, includes:

[0572] When at least one of the following conditions is met, random access is not performed or is suspended in the first procedure:

[0573] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0574] The first UE and the second UE have related transmission beams;

[0575] The first UE and the second UE have the same serving cell;

[0576] The second UE is in an RRC connected state, or is establishing an RRC connection, or is restoring an RRC connection.

[0577] Optionally, when the processor 1110 does not perform random access or suspend random access in the first process, and the first process is an RRC connection establishment process or an RRC connection recovery process:

[0578] The radio frequency unit 1101 is configured to perform a first operation on a first resource, or monitor network scheduling according to a C-RNTI configured on the network side to complete the first operation, where the first operation includes at least one of the following:

[0579] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0580] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0581] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0582] Optionally, the processor 1110 is further configured to obtain the C-RNTI of the first UE or the first resource from the second UE.

[0583] Optionally, the radio frequency unit 1101 performs the monitoring of network scheduling according to the C-RNTI configured on the network side to complete the first operation, including:

[0584] If the radio frequency unit 1101 fails to obtain the first resource, the radio frequency unit 1101 monitors network scheduling according to the C-RNTI to complete the first operation.

[0585] Optionally, the processor 1110 is further configured to initiate random access starting from the moment when it is determined that random access is not performed or random access is suspended in the first process, if the radio frequency unit 1101 fails to obtain the first resource or the C-RNTI within a preset time.

[0586] Optionally, when the first process is a handover process, the not performing random access or suspending random access in the first process, performed by the processor 1110, includes:

[0587] When at least one of the following conditions is met, random access is not performed or random access is suspended in the first process:

[0588] The first UE is capable of acquiring uplink synchronization based on the second UE;

[0589] The first UE and the second UE have related transmission beams;

[0590] The second UE is in an RRC connected state;

[0591] The serving cell after the switching of the first UE is the same as the current or switched serving cell of the second UE;

[0592] The second UE is performing a handover procedure or has completed the handover procedure;

[0593] The RRC reconfiguration message received by the first UE for performing handover does not carry a synchronization reconfiguration parameter.

[0594] Optionally, when the processor 1110 does not perform random access or suspend random access in the first process, and the first process is a handover process:

[0595] The radio frequency unit 1101 is further configured to send an RRC reconfiguration complete message of the first UE in one of the following manners, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE:

[0596] In a first manner, an RRC reconfiguration complete message of the first UE is sent on a second resource allocated by a network side device to the first UE;

[0597] In a second manner, monitoring network scheduling according to the C-RNTI of the first UE to send an RRC reconfiguration complete message of the first UE;

[0598] A third method is to carry the RRC reconfiguration complete message of the first UE in the RRC reconfiguration complete message of the second UE and send it.

[0599] Optionally, the radio frequency unit 1101 is configured to perform at least one of the following:

[0600] When the RRC reconfiguration message of the first UE includes the second resource, sending an RRC reconfiguration complete message of the first UE in the first manner;

[0601] When the RRC reconfiguration message of the first UE does not include the second resource, sending an RRC reconfiguration complete message of the first UE in the second manner;

[0602] In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the RRC reconfiguration complete message of the first UE is sent through the third method.

[0603] Optionally, when the radio frequency unit 1101 sends the RRC reconfiguration complete message of the first UE through the first method or the second method:

[0604] Processor 1110 is further configured to transmit the RRC reconfiguration message of the first UE to a media access control MAC layer, wherein the MAC layer does not trigger a random access process or a buffer status report BSR according to the RRC reconfiguration message of the first UE.

[0605] Optionally, the processor 1110 is further configured to initiate random access if it is determined that the second UE has not successfully completed random access within a preset time or a preset number of times.

[0606] Optionally, the initiating random access when determining that the second UE fails to successfully complete random access within a preset duration, performed by the processor 1110, includes:

[0607] When the first timer times out, if it is determined that the second UE has not successfully completed random access, random access is initiated, wherein the start time of the first timer is the time when the processor 1110 determines not to perform or suspend random access, and the first timer stops when the second UE successfully completes random access.

[0608] Optionally, the radio frequency unit 1101 is further used to receive first indication information from a network side device, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE.

[0609] Optionally, before executing the receiving of the first indication information from the network side device, the radio frequency unit 1101 is further used to send a first request message to the network side device, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

[0610] Optionally, the first indication information is carried in a timing advance command TAC.

[0611] Optionally, the performing uplink synchronization based on the second UE performed by the processor 1110 includes:

[0612] Based on the second UE, perform at least one of the following:

[0613] Determining the uplink synchronization information of the first UE according to the uplink synchronization information of the second UE;

[0614] Maintaining the uplink synchronization TAT of the first UE according to the TA parameter in the TAC of the second UE;

[0615] Determining whether the first UE is in an uplink synchronization state;

[0616] Determine whether to initiate random access of the first UE when the TAT times out and uplink or downlink data arrives for the first UE.

[0617] Optionally, the radio frequency unit 1101 is further used to send first capability information to the network side device, where the first capability information indicates that the first UE supports association operations with the second UE.

[0618] In another embodiment, terminal 1100 includes a second UE.

[0619] At this time, the radio frequency unit 1101 is configured to, when the terminal is a second UE, perform one of the following when the second UE is in an RRC connected state and the second UE is associated with the first UE:

[0620] Sending a second request message to a network-side device, where the second request message is used to request the network-side device to allocate a C-RNTI or a first resource to the first UE;

[0621] Sending the C-RNTI of the first UE to a network-side device;

[0622] An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

[0623] Optionally, the second UE includes at least one of the following:

[0624] a UE corresponding to a different universal subscriber identity module (USIM) card in the same device as the first UE;

[0625] UEs corresponding to different registrations in the same device as the first UE.

[0626] Optionally, the C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following:

[0627] Send an RRC connection establishment request message or an RRC connection recovery request message;

[0628] Receiving an RRC connection establishment message or an RRC connection recovery message;

[0629] Send an RRC connection establishment complete message or an RRC connection recovery complete message.

[0630] Optionally, after executing the sending of the second request message to the network side device, the radio frequency unit 1101 is further configured to:

[0631] receiving a first response message from the network side device, wherein the first response message carries the C-RNTI of the first UE or the first resource, or,

[0632] Receive a second response message from the network side device, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

[0633] Optionally, the second request message also includes the reason why the first UE establishes or restores the RRC connection.

[0634] Optionally, before executing the sending of the second request message to the network side device, the radio frequency unit 1101 is further configured to:

[0635] A first configuration is received, where the first configuration instructs the network-side device to allow the second UE to send the second request message.

[0636] Optionally, before executing the sending of the C-RNTI of the first UE to the network side device, the radio frequency unit 1101 is further configured to:

[0637] A second configuration is received, where the second configuration instructs the network side device to allow or request the second UE to send the C-RNTI of the first UE.

[0638] Optionally, the radio frequency unit 1101 is further configured to receive a third configuration, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource;

[0639] In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resource; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resource.

[0640] Optionally, the radio frequency unit 1101 is further used to send second capability information to the network side device, where the second capability information indicates that the second UE supports association operations with the first UE.

[0641] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 2 or Figure 5, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0642] An embodiment of the present application further provides a network-side device, including a processor and a communication interface, wherein the communication interface is configured to perform a second operation, where the second operation includes at least one of the following:

[0643] Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE;

[0644] receiving a C-RNTI of the first UE from the second UE;

[0645] Sending the C-RNTI or first resource allocated to the first UE to the second UE;

[0646] The first UE is associated with the second UE.

[0647] This network side device embodiment corresponds to the above-mentioned network side device method embodiment. Each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.

[0648] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 12, the network-side device 1200 includes an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. Antenna 121 is connected to radio frequency device 122. In the uplink direction, radio frequency device 122 receives information via antenna 121 and sends the received information to baseband device 123 for processing. In the downlink direction, baseband device 123 processes the information to be transmitted and sends it to radio frequency device 122. Radio frequency device 122 processes the received information and then sends it through antenna 121.

[0649] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 123 , which includes a baseband processor.

[0650] The baseband device 123 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 12, one of the chips is, for example, a baseband processor, which is connected to the memory 125 through a bus interface to call the program in the memory 125 and execute the network device operations shown in the above method embodiment.

[0651] The network side device may further include a network interface 126 , which is, for example, a Common Public Radio Interface (CPRI).

[0652] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 125 and executable on the processor 124. The processor 124 calls the instructions or programs in the memory 125 to execute the methods of execution of each module shown in Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0653] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned UE control method and UE configuration method embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, they are not repeated here.

[0654] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0655] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned UE control method and UE configuration method embodiments, and can achieve the same technical effects. To avoid repetition, they are not repeated here.

[0656] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0657] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned UE control method and UE configuration method embodiments, and can achieve the same technical effects. To avoid repetition, they are not repeated here.

[0658] An embodiment of the present application also provides a wireless communication system, including: a first UE, a second UE and a network side device, wherein the first UE can be used to execute the steps of the method embodiment shown in Figure 2, the second UE can be used to execute the steps of the method embodiment shown in Figure 5, and the network side device can be used to execute the steps of the method embodiment shown in Figure 6.

[0659] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0660] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0661] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for controlling a user equipment UE, comprising: In a case where a first UE is associated with a second UE, the first UE performs uplink synchronization based on the second UE, or the first UE does not perform random access or suspends random access in a first process, and the first process includes at least one of the following: Radio resource control RRC connection establishment process; RRC connection recovery process; RRC connection reestablishment process; Switch process.

2. The method according to claim 1, wherein: The second UE includes at least one of the following: A UE corresponding to a different universal subscriber identity module USIM card in the same device as the first UE; UEs corresponding to different registrations in the same device as the first UE.

3. The method according to claim 1 or 2, wherein: The first UE does not perform random access or suspends random access in a first process, including: In a case where the first UE is configured to acquire uplink synchronization based on the second UE, or in a case where the first UE is configured not to perform random access or suspend random access in the first process, the first UE does not perform random access or suspend random access in the first process.

4. The method according to any one of claims 1 to 3, wherein: In a case where the first process is an RRC connection establishment process or an RRC connection recovery process, the first UE does not perform random access or suspends random access in the first process, including: When at least one of the following conditions is met, the first UE does not perform random access or suspends random access in the first process: The first UE can acquire uplink synchronization based on the second UE; The first UE and the second UE have related transmission beams; The first UE and the second UE have the same serving cell; The second UE is in an RRC connected state, or is establishing an RRC connection, or is restoring an RRC connection.

5. The method according to any one of claims 1 to 4, wherein: In a case where the first UE does not perform random access or suspend random access in a first process, and the first process is an RRC connection establishment process or an RRC connection recovery process, the method further includes: The first UE completes a first operation on a first resource, or the first UE monitors network scheduling according to a cell radio network temporary identifier C-RNTI configured by a network side to complete the first operation, where the first operation includes at least one of the following: Sending an RRC connection establishment request message or an RRC connection recovery request message; Receiving an RRC connection establishment message or an RRC connection recovery message; Send an RRC connection establishment complete message or an RRC connection recovery complete message.

6. The method according to claim 5, wherein: The method further comprises: The first UE obtains the C-RNTI of the first UE or the first resource from the second UE.

7. The method according to claim 6, wherein: The first UE monitors network scheduling according to the C-RNTI configured by the network side to complete the first operation, including: If the first UE fails to acquire the first resource, the first UE monitors network scheduling according to the C-RNTI to complete the first operation.

8. The method according to claim 5, wherein: The method further comprises: Starting from the moment when the first UE determines not to perform random access or suspend random access in the first process, if the first UE fails to obtain the first resource or the C-RNTI within a preset time, the first UE initiates random access.

9. The method according to any one of claims 1 to 3, wherein: In a case where the first process is a handover process, the first UE does not perform random access or suspends random access in the first process, including: When at least one of the following conditions is met, the first UE does not perform random access or suspends random access in the first process: The first UE can acquire uplink synchronization based on the second UE; The first UE and the second UE have related transmission beams; The second UE is in an RRC connected state; The serving cell after the switching of the first UE is the same as the current or switched serving cell of the second UE; The second UE is performing a handover procedure or has completed a handover procedure; The RRC reconfiguration message for performing handover received by the first UE does not carry a synchronization reconfiguration parameter.

10. The method according to claim 9, wherein: In a case where the first UE does not perform random access or suspends random access in a first process, and the first process is a handover process, the method further includes: The first UE sends an RRC reconfiguration complete message of the first UE in one of the following ways, wherein the RRC reconfiguration complete message of the first UE is a response message to the RRC reconfiguration message of the first UE: In a first manner, an RRC reconfiguration completion message of the first UE is sent on a second resource allocated by a network side device to the first UE; A second manner is to monitor network scheduling according to the C-RNTI of the first UE to send an RRC reconfiguration completion message of the first UE; A third method is to carry the RRC reconfiguration complete message of the first UE in the RRC reconfiguration complete message of the second UE and send it.

11. The method according to claim 10, wherein: The first UE sends an RRC reconfiguration complete message of the first UE in one of the following ways, including at least one of the following: In the case where the RRC reconfiguration message of the first UE includes the second resource, the first UE Sending an RRC reconfiguration completion message of the first UE in a first manner; In a case where the RRC reconfiguration message of the first UE does not include the second resource, the first UE sends an RRC reconfiguration completion message of the first UE in the second manner; In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the first UE sends the RRC reconfiguration complete message of the first UE through the third method.

12. The method according to claim 10, wherein: In the case where the RRC reconfiguration completion message of the first UE is sent by using the first manner or the second manner, the method further includes: The first UE passes the RRC reconfiguration message of the first UE to the media access control MAC layer, wherein the MAC layer does not trigger a random access process or a buffer status report BSR according to the RRC reconfiguration message of the first UE.

13. The method according to claim 9, wherein: The method further comprises: When the first UE determines that the second UE has not successfully completed random access within a preset time or a preset number of times, the first UE initiates random access.

14. The method according to claim 13, wherein: When the first UE determines that the second UE has not successfully completed random access within a preset time period, the first UE initiates random access, including: When the first timer times out, if the first UE determines that the second UE has not successfully completed the random access, the first UE initiates random access, wherein the start time of the first timer is the time when the first UE determines not to perform or suspend the random access, and the first timer stops when the second UE successfully completes the random access.

15. The method according to claim 1 or 2, wherein: The method further comprises: The first UE receives first indication information from a network side device, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE.

16. The method according to claim 15, wherein: Before the first UE receives the first indication information from the network side device, the method further includes: The first UE sends a first request message to the network side device, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

17. The method according to claim 15, wherein: The first indication information is carried in a timing advance command TAC.

18. The method according to any one of claims 1 to 17, wherein: The performing uplink synchronization based on the second UE includes: Based on the second UE, the first UE performs at least one of the following: Determine the uplink synchronization information of the first UE according to the uplink synchronization information of the second UE; Maintaining an uplink synchronization time advance timer TAT of the first UE according to a TA parameter in a timing advance command TAC of the second UE; Determining whether the first UE is in an uplink synchronization state; Determine whether the first UE initiates random access when the TAT times out and uplink or downlink data arrives at the first UE.

19. The method according to any one of claims 1 to 18, wherein: The method further comprises: The first UE sends first capability information to a network side device, where the first capability information indicates that the first UE supports association operations with the second UE.

20. A method for controlling a user equipment UE, comprising: When the second UE is in a radio resource control (RRC) connected state and the second UE is associated with the first UE, the second UE performs one of the following: Sending a second request message to a network side device, where the second request message is used to request the network side device to allocate a cell radio network temporary identifier C-RNTI or a first resource to the first UE; Sending the C-RNTI of the first UE to a network side device; An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

21. The method according to claim 20, wherein: The second UE includes at least one of the following: A UE corresponding to a different universal subscriber identity module USIM card in the same device as the first UE; UEs corresponding to different registrations in the same device as the first UE.

22. The method according to claim 20 or 21, wherein: The C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following: Sending an RRC connection establishment request message or an RRC connection recovery request message; Receiving an RRC connection establishment message or an RRC connection recovery message; Send an RRC connection establishment complete message or an RRC connection recovery complete message.

23. The method according to claim 20, wherein: After the second UE sends a second request message to the network side device, the method further includes: The second UE receives a first response message from the network side device, wherein the first response message carries the C-RNTI of the first UE or the first resource, or, The second UE receives a second response message from the network side device, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

24. The method according to claim 20, wherein: The second request message also includes the reason why the first UE establishes or restores the RRC connection.

25. The method according to claim 20, wherein: Before the second UE sends a second request message to the network side device, the method further includes: A first configuration is received, where the first configuration indicates that the network side device allows the second UE to send the second request message.

26. The method of claim 20, wherein: Before the second UE sends the C-RNTI of the first UE to the network side device, the method further includes: The second UE receives a second configuration, wherein the second configuration indicates that the network side device allows or requests the first The second UE sends the C-RNTI of the first UE.

27. The method according to claim 20, wherein: The method further comprises: The second UE receives a third configuration, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource; In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resources; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resources.

28. The method according to any one of claims 20 to 27, wherein: The method further comprises: The second UE sends second capability information to the network side device, where the second capability information indicates that the second UE supports association operations with the first UE.

29. A method for configuring a user equipment UE, comprising: The network-side device performs a second operation, where the second operation includes at least one of the following: Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE; Receiving a cell radio network temporary identifier C-RNTI of the first UE from the second UE; Sending the C-RNTI or the first resource allocated to the first UE to the second UE; The first UE is associated with the second UE.

30. The method of claim 29, wherein: The method further comprises: The network side device receives a second request message from the second UE, wherein the second request message is used to request the network side device to allocate the C-RNTI or the first resource to the first UE.

31. The method according to claim 30, wherein: Before the network side device receives the second request message from the second UE, the method further includes: The network side device sends a first configuration to the second UE, where the first configuration indicates that the network side device allows the second UE to send the second request message.

32. The method according to claim 30 or 31, wherein: After the network side device receives the second request message from the second UE, the method further includes: The network side device sends a first response message to the second UE, wherein the first response message carries the C-RNTI of the first UE or the first resource; or, The network side device sends a second response message to the second UE, where the second response message carries second indication information, and the second indication information is used to instruct the second UE to send the second request message to the network side device again when the target backoff time arrives.

33. The method of claim 30, wherein: The second request message also includes the reason why the first UE establishes or restores a radio resource control RRC connection.

34. A method according to any one of claims 29 to 33, wherein: The C-RNTI or the first resource is used by the first UE to perform a first operation, where the first operation includes at least one of the following: Sending an RRC connection establishment request message or an RRC connection recovery request message; Receiving an RRC connection establishment message or an RRC connection recovery message; Send an RRC connection establishment complete message or an RRC connection recovery complete message.

35. The method of claim 29, wherein: Before the network side device receives the C-RNTI of the first UE from the second UE, the method further includes: The network side device sends a second configuration to the second UE, where the second configuration indicates that the network side device allows or requests the second UE to send the C-RNTI of the first UE.

36. The method of claim 35, wherein: The receiving the C-RNTI of the first UE from the second UE includes: An RRC reconfiguration complete message or auxiliary information UAI of the second UE is received from the second UE, wherein the RRC reconfiguration complete message or UAI of the second UE includes the C-RNTI of the first UE.

37. The method of claim 36, wherein: After receiving the RRC reconfiguration complete message or auxiliary information UAI of the second UE from the second UE, the method further includes: The network side device sends an RRC reconfiguration message of the first UE or an RRC reconfiguration message of the second UE, wherein the RRC reconfiguration message of the first UE does not carry a synchronization reconfiguration parameter; or, the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE; or, the RRC reconfiguration message of the first UE carries a second resource, and the second resource is used by the first UE to report an RRC reconfiguration completion message to the network side device.

38. The method of claim 37, wherein: The method further comprises: The network side device receives the RRC reconfiguration completion message of the first UE in one of the following ways, wherein the RRC reconfiguration completion message of the first UE is a response message to the RRC reconfiguration message of the first UE: In a fourth manner, the network side device receives an RRC reconfiguration completion message of the first UE on the second resource allocated to the first UE; In a fifth manner, the network side device receives an RRC reconfiguration completion message of the first UE on the dynamically scheduled resources; In a sixth manner, the network side device receives an RRC reconfiguration completion message of the second UE, wherein the RRC reconfiguration completion message of the second UE carries an RRC reconfiguration completion message of the first UE.

39. The method of claim 38, wherein: The network side device receives the RRC reconfiguration completion message of the first UE in one of the following ways, including at least one of the following: In a case where the RRC reconfiguration message of the first UE includes the second resource, the network side device receives the RRC reconfiguration completion message of the first UE through the fourth method; In a case where the RRC reconfiguration message of the first UE does not include the second resource, the network side device receives the RRC reconfiguration completion message of the first UE through the fifth method; or, In a case where the RRC reconfiguration message of the first UE is carried in the RRC reconfiguration message of the second UE, the network side device receives the RRC reconfiguration completion message of the first UE through the sixth method.

40. The method according to any one of claims 37 to 39, wherein: The method further comprises: The network side device sends a third configuration to the second UE, where the third configuration is used to configure a first random access channel RACH resource and a second RACH resource; In which, when the RRC reconfiguration completion message of the second UE includes the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the first RACH resources; when the RRC reconfiguration completion message of the second UE does not include the C-RNTI of the first UE, the RRC reconfiguration completion message of the second UE is transmitted through the second RACH resources.

41. The method of claim 29, wherein: The method further comprises: The network side device sends or receives a handover request message, where the handover request message includes the C-RNTI of the first UE and the C-RNTI of the second UE.

42. The method according to any one of claims 35 to 41, wherein: The method further comprises at least one of the following: The network side device configures the first UE not to perform random access or to suspend random access in the first process; The network side device configures the first UE to obtain uplink synchronization based on the second UE; Wherein, the first process includes at least one of the following: Radio resource control RRC connection establishment process; RRC connection recovery process; RRC connection reestablishment process; Switch process.

43. The method of claim 29, wherein: Before the network side device sends the first indication information to the first UE, the method further includes: The network side device receives a first request message from the first UE, where the first request message is used to request the first UE to perform uplink synchronization based on the second UE.

44. The method of claim 43, wherein: The first indication information is carried in a timing advance command TAC.

45. A method according to any one of claims 29 to 44, wherein: The method further comprises at least one of the following: The network side device receives first capability information from the first UE, where the first capability information indicates that the first UE supports performing an association operation with the second UE; The network side device receives second capability information from the second UE, where the second capability information indicates that the second UE supports association operations with the first UE.

46. ​​A user equipment UE control device, used for a first UE, the device comprising: A first execution module is configured to perform uplink synchronization based on a second UE when the first UE is associated with the second UE, or not perform random access or suspend random access in a first process, wherein the first process includes at least one of the following: Radio resource control RRC connection establishment process; RRC connection recovery process; RRC connection reestablishment process; Switch process.

47. A user equipment UE control device, used for a second UE, the device comprising: The second execution module is configured to execute one of the following when the second UE is in a radio resource control RRC connected state and the second UE is associated with the first UE: Sending a second request message to a network side device, where the second request message is used to request the network side device to allocate a cell radio network temporary identifier C-RNTI or a first resource to the first UE; Sending the C-RNTI of the first UE to a network side device; An RRC reconfiguration message of the second UE is received, where the RRC reconfiguration message of the second UE carries the RRC reconfiguration message of the first UE.

48. A user equipment UE configuration device, used for a network side device, the device comprising: The third execution module is configured to execute a second operation, where the second operation includes at least one of the following: Sending first indication information to the first UE, where the first indication information is used to instruct the first UE to perform uplink synchronization based on the second UE; Receiving a cell radio network temporary identifier C-RNTI of the first UE from the second UE; Sending the C-RNTI or the first resource allocated to the first UE to the second UE; The first UE is associated with the second UE.

49. A terminal, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the user equipment UE control method according to any one of claims 1 to 28 are implemented.

50. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the user equipment (UE) configuration method described in any one of claims 29 to 45 are implemented.

51. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the user equipment UE control method as described in any one of claims 1 to 28, or implements the steps of the user equipment UE configuration method as described in any one of claims 29 to 45.

Images