Method, device, apparatus and storage medium for reestablishing RRC connection

Abstract

The embodiment of the present invention provides a method, device, apparatus and storage medium for reestablishing an RRC connection. The method for reestablishing an RRC connection by a user equipment includes: obtaining a C-RNTI; determining that a link of the user equipment is in an RLF state; and sending an RRC reestablishment request to a network device, wherein the request includes a device information field indicating whether the user equipment is a remote user equipment or a non-remote user equipment. In the technical solution of the embodiment of the present invention, the C-RNTI can be reused by the remote UE and the non-remote UE, thereby saving C-RNTI resources.

Description

Technical Field

[0001] The present invention relates to the field of wireless communications, and in particular to a method, device, apparatus and storage medium for reestablishing an RRC connection. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) introduced the sidelink communication technology, in which the User Equipment (UE) includes remote UE and non-remote UE, and the non-remote UE includes relay UE. The remote UE establishes a PC5 sidelink with the relay UE through the PC5 interface, and then accesses the network device through the relay UE.

[0003] There are two modes for the remote UE to access the network device through the relay UE, namely, Layer 2 UE-to-Network Relay mode and Layer 3 UE-to-UE Relay mode. In the Layer 2 relay mode, an RRC connection is directly established between the remote UE and the network device, so the remote UE will enter the RRC_CONNECTED state after accessing the network through the relay UE, and the remote UE will be assigned a Cell-Radio Network Temporary Identifier (C-RNTI); in the Layer 3 relay mode, the remote UE establishes a PC5 connection with the relay UE, but no RRC connection is directly established with the network device.

[0004] In scenarios with a large number of UE applications, such as the Internet of Things (IOT), many remote UEs access network devices through relay UEs. However, in layer 2 relay mode, there may not be enough C-RNTIs allocated to remote UEs entering the connected state. Summary of the invention

[0005] The purpose of the embodiments of the present invention is to provide a method, device, apparatus and storage medium for reestablishing an RRC connection.

[0006] An embodiment of the present invention provides a method for user equipment to reestablish an RRC connection, wherein the user equipment includes an edge link remote user equipment and a non-edge link remote user equipment, including: S110, obtaining a C-RNTI; S120, determining that a link of the user equipment is in an RLF state; S130, sending an RRC reconstruction request to a network device, including a device information field indicating whether the user equipment is an edge link remote user equipment or a non-edge link remote user equipment.

[0007] Optionally, the method for user equipment to reestablish RRC connection also includes: S120 includes determining that the PC5 side link of the user equipment is in an RLF state; S130 includes sending an RRC reestablishment request to a network device, wherein the device information field indicates that the user equipment is a side link remote user equipment.

[0008] Optionally, the method for user equipment to reestablish RRC connection also includes: S120 includes determining that the Uu link of the user equipment is in an RLF state; S130 includes sending an RRC reestablishment request to a network device, wherein the device information field indicates that the user equipment is a non-side link remote user equipment.

[0009] Optionally, the device information field includes a spare bit in the RRC reestablishment request, which is set to one of 0 and 1 to indicate that the user equipment is a side link remote user equipment and the other to indicate that the user equipment is a non-side link remote user equipment.

[0010] Optionally, the device information field includes an extended field, which includes a layer 2 identifier of the side link relay user equipment, indicating that the user equipment is a side link remote user equipment.

[0011] An embodiment of the present invention further provides a user equipment, comprising a memory and a processor, wherein the memory stores computer instructions executable on the processor, and the processor executes the steps of a method for reestablishing an RRC connection of the user equipment when executing the computer instructions.

[0012] An embodiment of the present invention further provides a storage medium on which computer instructions are stored. When the computer instructions are executed, the steps of the method for user equipment to reestablish an RRC connection are executed.

[0013] An embodiment of the present invention also provides a user device, comprising: a first acquisition module, which is suitable for acquiring C-RNTI; a first determination module, which is suitable for determining that the link of the user equipment is in an RLF state; a sending module, which is suitable for sending an RRC reconstruction request to a network device, including a device information field indicating whether the user equipment is an edge link remote user equipment or a non-edge link remote user equipment.

[0014] Optionally, the above-mentioned user device also includes: a first determination module suitable for determining that the PC5 side link of the user equipment is in an RLF state; a sending module suitable for sending an RRC reconstruction request to a network device, wherein the device information field indicates that the user equipment is a side link remote user equipment.

[0015] Optionally, the above-mentioned user device also includes: a first determination module suitable for determining that the Uu link of the user equipment is in an RLF state; a sending module suitable for sending an RRC reconstruction request to a network device, wherein the device information field indicates that the user equipment is a non-side link remote user equipment.

[0016] Optionally, the device information field includes a spare bit in the RRC reestablishment request, which is suitable for being set to one of 0 and 1 to indicate that the user equipment is a side link remote user equipment and the other to indicate that the user equipment is a non-side link remote user equipment.

[0017] Optionally, the device information field includes an extended field, which includes a layer 2 identifier of the side link relay user equipment, indicating that the user equipment is a side link remote user equipment.

[0018] An embodiment of the present invention also provides a method for a network device to reestablish an RRC connection, comprising: allocating a C-RNTI to a user device, the user device comprising an edge link remote user device and a non-edge link remote user device, the C-RNTI being multiplexed by the edge link remote user device and the non-edge link remote user device; receiving an RRC reconstruction request sent by the user device; obtaining a device information field in the RRC reconstruction request; and determining whether the user device is an edge link remote user device or a non-edge link remote user device based on information in the device information field.

[0019] Optionally, the device information field includes a spare bit, and the method includes: if the spare bit is one of 0 and 1, determining that the user equipment is an edge link remote user equipment; if the spare bit is the other of 0 and 1, determining that the user equipment is a non-edge link remote user equipment.

[0020] Optionally, the device information field includes an extended field, which includes a layer 2 identifier for an edge link relay user device. The method includes: if the device information field includes the layer 2 identifier, determining that the user device is an edge link remote user device; if the device information field does not include the layer 2 identifier, determining that the user device is a non-edge link remote user device.

[0021] Optionally, the method for the network device to reestablish the RRC connection also includes: obtaining the PCI and C-RNTI corresponding to the user equipment from the RRC reconstruction request; communicating with the original network device based on the PCI, C-RNTI and the user equipment information determined by the device information field, the original network device being the network device with which the user equipment last established an RRC connection before the PC5 side link RLF or Uu link RLF occurred; obtaining from the original network device the configuration information and / or capability information of the user equipment obtained based on the PCI, C-RNTI and the user equipment information; and establishing an RRC connection with the user equipment based on the configuration information and / or capability information.

[0022] An embodiment of the present invention further provides a network device, including a memory and a processor, wherein the memory stores computer instructions that can be executed on the processor, and when the processor executes the computer instructions, the steps of the method for reestablishing an RRC connection of the network device are executed.

[0023] An embodiment of the present invention also provides a storage medium on which computer instructions are stored. When the computer instructions are executed, the steps of the method for reestablishing an RRC connection by a network device are executed.

[0024] An embodiment of the present invention also provides a network device, including: an allocation module, which is suitable for allocating C-RNTI to user equipment, the user equipment includes an edge link remote user equipment and a non-edge link remote user equipment, and the C-RNTI can be multiplexed by the edge link remote user equipment and the non-edge link remote user equipment; a receiving module, which is suitable for receiving an RRC reconstruction request sent by the user equipment; a second acquisition module, which is suitable for acquiring a device information field in the RRC reconstruction request; and a second determination module, which is suitable for determining whether the user equipment is an edge link remote user equipment or a non-edge link remote user equipment based on information in the device information field.

[0025] Optionally, the device information field includes a spare bit, and the network apparatus includes a third determination module, which is suitable for determining that the user equipment is a side link remote user equipment if the spare bit is one of 0 and 1, and determining that the user equipment is a non-side link remote user equipment if the other is 0 and 1.

[0026] Optionally, the device information field includes an extended field, which includes a layer 2 identifier for the edge link relay user equipment, and the network device includes a fourth determination module, which is suitable for determining that the user equipment is an edge link remote user equipment if the device information field includes the layer 2 identifier, and determining that the user equipment is a non-edge link remote user equipment if the layer 2 identifier is not included.

[0027] Optionally, the above-mentioned network device includes: a third acquisition module, which is suitable for obtaining the PCI and C-RNTI corresponding to the user equipment from the RRC reconstruction request; a first connection module, which is suitable for communicating with the original network device based on the PCI, C-RNTI and the user equipment information determined by the device information field, and the original network device is the network device with which the user equipment last established an RRC connection before the PC5 side link RLF or Uu link RLF occurred; a fourth acquisition module, which is suitable for obtaining the configuration information and / or capability information of the user equipment from the original network device; a second connection module, which is suitable for establishing an RRC connection with the user equipment based on the configuration information and / or capability information.

[0028] Compared with the prior art, the technical solution of the embodiment of the present invention has beneficial effects. For example, C-RNTI is multiplexed by remote UE and non-remote UE, thereby saving C-RNTI resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a flowchart of a UE reestablishing an RRC connection in an embodiment of the present invention;

[0030] Figure 2is a schematic diagram of a communication system in an embodiment of the present invention;

[0031] Figure 3 This is a schematic diagram of reestablishing an RRC connection in the first embodiment of the present invention;

[0032] Figure 4 A schematic diagram of reestablishing an RRC connection in a second embodiment of the present invention;

[0033] Figure 5 is a schematic diagram of the structure of a user device in an embodiment of the present invention;

[0034] Figure 6 This is a flow chart of a network device reestablishing an RRC connection in an embodiment of the present invention;

[0035] Figure 7 FIG. 4 is a schematic diagram of the structure of a network device in an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In an embodiment of the present invention, a layer 2 relay mode is used. In the layer 2 relay mode, although the network device does not need to schedule the wireless air interface resources of the remote UE through C-RNTI, the network device in the embodiment of the present invention can still allocate C-RNTI to the remote UE. The relevant data of the remote UE in a connected state (such as capability information, the capability information includes the frequency bands and transmission power supported by the UE, etc.) can be indexed by C-RNTI, and mobility management such as UE switching can be performed through C-RNTI. After a PC5 sidelink radio link failure (Radio Link Failure, RLF) occurs, the remote UE can re-establish the RRC connection with the network device through C-RNTI.

[0037] In an embodiment of the present invention, a network device may allocate a C-RNTI to a UE, and the C-RNTI is multiplexed by a remote UE and a non-remote UE. For example, one C-RNTI is allocated to both a remote UE and a non-remote UE. Thus, in a scenario where a large number of remote UEs are used, such as IOT, these remote UEs occupy C-RNTI resources without affecting the C-RNTI resources of non-remote user equipment, thereby avoiding major changes to the 3GPP protocol caused by extending the C-RNTI (for example, from 16 bits to 24 bits), avoiding complex implementation processes at the network device and the UE, and avoiding upgrading a large number of existing network devices and UEs.

[0038] In the case where C-RNTI is multiplexed by a remote UE and a non-remote UE, after RLF (e.g., PC5sidelink RLF, Uu RLF) occurs, the UE sends a message of an RRC reestablishment request (e.g., RRCReestablishmentRequest) to the network device, and the network device parses the message and can obtain the C-RNTI. Since the C-RNTI is multiplexed by the remote UE and the non-remote UE, the network device cannot determine whether the RRC reestablishment request comes from the remote UE or the non-remote UE based on the C-RNTI.

[0039] In an embodiment of the present invention, after RLF occurs, the message of RRC re-establishment request sent by the UE to the network device may include a device information field, which indicates whether the UE is a remote UE or a non-remote UE.

[0040] In the embodiments of the present invention, various technical solutions can be applied to 3G, 4G, 5G systems and future evolved public land mobile communication networks (Public Land Mobile Network, PLMN) and other systems, wherein the 5G system includes two types of networking, namely non-standalone networking (Non-Standalone, NSA) and standalone networking (Standalone, SA).

[0041] In the embodiments of the present invention, the UE may be an access terminal, a user unit, a user station, a mobile station, a mobile station (Mobile Station, MS), a remote station, a remote terminal, a mobile device, a user terminal, a terminal equipment (Terminal Equipment), a wireless communication device or a user agent; the UE may also be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, IP) phone, a Wireless Local Loop (Wireless Local Loop, WLL) station, a Personal Digital Assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a UE in a future 5G network or a UE in a future evolved PLMN, etc.

[0042] In an embodiment of the present invention, a network device may be a device deployed in a radio access network (RAN) to provide wireless communication functions, including but not limited to devices that provide base station functions in 3G, 4G, 5G systems and future evolved PLMN systems. For example, devices that provide base station functions in 3G networks include NodeBs, devices that provide base station functions in 4G networks include evolved NodeBs (evolved NodeBs), devices that provide base station functions in wireless local area networks (WLANs) (i.e., access points, Access Points, APs), devices that provide base station functions in 5G NRs include gNBs, and further evolved NodeBs (ng-eNBs), etc.

[0043] In the embodiments of the present invention, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0044] In an embodiment of the present invention, the memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. 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 a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 (DR|RAM).

[0045] In the embodiment of the present invention, the storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk.

[0046] In the embodiments of the present invention, the device embodiments are only illustrative. For example, the division of modules is only a logical function division, and there may be other division methods in actual implementation. The modules may be stored in a storage medium, including several instructions for enabling a computer device (which may be a personal computer, a server, or a device connected to a network, etc.) to execute the steps of the relevant methods in the embodiments of the present invention.

[0047] In order to make the purpose, features and beneficial effects of the embodiments of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are described in detail below with reference to the accompanying drawings.

[0048] like Figure 1 As shown, the embodiment of the present invention provides a method 100 for UE to reestablish RRC connection, which may include:

[0049] S110, obtaining C-RNTI;

[0050] S120, determining that the link of the UE is in an RLF state;

[0051] S130: Send an RRC reestablishment request to a network device, including a device information field indicating whether the UE is a remote UE or a non-remote UE.

[0052] Method 100 involves a network device and a UE, wherein the UE includes a non-remote UE (which may be referred to as a non-side link remote UE) and a remote UE (which may be referred to as a side link remote UE), wherein the non-remote UE includes a relay UE (which may be referred to as a side link relay UE), and the non-remote UE accesses the network device via a Uu link. A PC5 sidelink is established between the remote UE and the relay UE via a PC5 interface, a Uu link is established between the relay UE and the network device via a Uu interface, and the remote UE accesses the network device via the PC5 sidelink and the Uu link between the relay UE and the network device.

[0053] like Figure 2 As shown, the system 200 includes a network device 201 and UEs in a connected state, including non-remote UEs 211 and 212 and remote UE 213, wherein the non-remote UE 212 can be used as a relay UE of the remote UE 213. The non-remote UEs 211 and 212 are within the coverage (In Coverage, IC) of the network device, and establish a connection with the network device 201 based on the Uu interface; the remote UE 213 may be within the coverage or outside the coverage (out of coverage, OOC) of the network device, and the remote UE 213 establishes a connection with the relay UE 212 based on the PC5 interface, and then connects to the network device 201 through the relay UE 212.

[0054] During the execution of step S110, the network device may allocate C-RNTI to the UE, for example, allocate C-RNTI to non-remote UE (including relay UE) via Uu link, and allocate C-RNTI to remote UE via Uu link and PC5 sidelink; the non-remote UE receives the allocation message sent by the network device via Uu link and obtains C-RNTI, and the remote UE receives the allocation message sent by the network device via Uu link and PC5 sidelink and obtains C-RNTI.

[0055] Specifically, since the network device can distinguish whether the accessed UE is a non-remote UE or a remote UE during the access process, the network device can reallocate the C-RNTI allocated to the non-remote UE to the remote UE again, so that the C-RNTI of at least some of the remote UEs is the same as the C-RNTI of at least some of the non-remote UEs, that is, one C-RNTI or each of the multiple C-RNTIs is multiplexed between its corresponding remote UE and non-remote UE.

[0056] For example, in Figure 2 In the example, the remote UE 213 has the same C-RNTI as one of the non-remote UE 211 and the non-remote UE 212, but has a different C-RNTI1 from the other of the non-remote UE 211 and the non-remote UE 212.

[0057] During the execution of step S120, the UE will detect the link to which it is connected (for example, the Uulink of the non-remote UE connecting to the network device, the PC5 sidelink of the remote UE connecting to the relay UE). When a link may fail, the UE will determine whether it is in the RLF state.

[0058] During the execution of step S130, if the UE determines that the link is in the RLF state, it may send an RRC reestablishment request message (eg, RRCReestablishmentRequest) to the network device, the message may include a device information field indicating whether the UE is a remote UE or a non-remote UE.

[0059] For example, the UE sends an RRC reestablishment request including a device information field, and the device information field includes a spare bit, which is set to one of 0 and 1 to indicate that the UE is a remote UE, and the other to indicate that the UE is a non-remote UE. The network device receives the message of the RRC reestablishment request, and determines that the UE is a remote UE if the spare bit is one of 0 and 1, and determines that the UE is a non-remote UE if the spare bit is the other of 0 and 1; for example, if the spare bit is 1, it is determined that the UE is a remote UE, and if the spare bit is 0, it is determined that the UE is a non-remote UE.

[0060] For another example, the UE sends an RRC reestablishment request including a device information field, and the device information field includes an extended field, including a layer 2 ID of the relay UE (relay UE L2 ID), which indicates that the UE is a remote UE. The network device receives the message of the RRC reestablishment request, and determines that the UE is a remote UE if the device information field includes the layer 2 ID, and determines that the UE is a non-remote UE if the device information field does not include the layer 2 ID.

[0061] For another example, the UE sends an RRC reconstruction request including a device information field, which does not include the device information field, for example, the RRC reconstruction request does not include an extended field and the spare bit of the RRC reconstruction request is not configured, then the UE is determined to be a non-remote UE.

[0062] In some embodiments, if the UE determines that the PC5 sidelink connected to it is in the RLF state, it sends an RRC reestablishment request message to the network device, and the device information field in the message indicates that the UE is a remote UE.

[0063] In some other embodiments, if the UE determines that the Uu link connected to it is in the RLF state, it sends an RRC reestablishment request message to the network device, and the device information field in the message indicates that the UE is a non-remote UE.

[0064] The following combination Figure 3 A first embodiment of the present invention is described.

[0065] like Figure 3 As shown, the network 300 includes a network device 301 and a network device 302 adjacent to each other, and UEs 311, 312, and 313 in a connected state. The non-remote UEs 311 and 312 are connected to the network device 301 via a Uu interface, and the remote UE 313 is located outside the coverage of the network device 301. It is connected to the non-remote UE 312 (i.e., a relay UE) via a PC5 interface, and then accesses the network device 301 via the non-remote UE 312.

[0066] The cell of the network device 301 has a physical cell identifier (PCI), represented by PCI1; the network device 301 stores relevant information of UE 311, 312, and 313, such as configuration information and capability information. The configuration information may be bearer information or quality of service (QoS) information, and the capability information may be a frequency band or transmit power supported by the UE.

[0067] The cell of network device 302 is denoted as PCI2.

[0068] UE 311 and UE 313 are allocated the same C-RNTI (ie, C-RNTI1), while UE 312 is allocated a different C-RNTI (ie, C-RNTI2).

[0069] The remote UE 313 gradually moves away from the cell PCI1 of the relay UE 312 and the network device 301, and moves toward the cell PCI2 of the network device 302, as indicated by arrow 314. During the movement, the sidelink connected between the remote UE 313 and the relay UE 312 has a PC5 sidelink RLF, and the remote UE 313 sends an RRC reestablishment request message to the network device 302. In this scenario, the network device 301 can be called the original network device, and the network device 302 can be called the target network device.

[0070] The message of the RRC reestablishment request sent by the remote UE 313 to the network device 302 includes a PCI field, a C-RNTI field and a device information field. Among them, the information in the PCI field indicates that the cell where the remote UE 313 is located is PCI1; the information in the C-RNTI field indicates that the C-RNTI possessed by the remote UE 313 is C-RNTI1; the device information field can be a spare bit (which is set to one of 0 and 1 to indicate that the remote UE 313 is a remote UE type), or an extended field (which includes a layer 2 identifier about the relay UE 312, thereby indicating that the remote UE 313 is a remote UE type).

[0071] After receiving the RRC reestablishment request message, network device 302 obtains PCI1, C-RNTI1 corresponding to remote UE 313 and user equipment information determined by the device information field (which indicates that remote UE 313 is a remote UE type); then, network device 302 communicates with network device 301 based on PCI1, C-RNTI1 and user equipment information, for example, network device 302 establishes a connection with network device 301 through PCI1, and sends C-RNTI1 and user equipment information to network device 301.

[0072] After receiving C-RNTI1 and user equipment information, network device 301 can uniquely determine that the UE initiating the RRC reestablishment request is remote UE 313; then, it sends configuration information and / or capability information related to remote UE 313 to network device 302.

[0073] The network device 302 receives the configuration information and / or capability information related to the remote UE 313 sent by the network device 301, and establishes an RRC connection with the remote UE 313 through the Uu interface based on the information.

[0074] After completing the RRC connection, the remote UE 313 sends the RRC connection establishment completion information to the network device 302 through the Uu interface; at this time, the remote UE 313 is a non-remote UE of the network device 302.

[0075] In the first embodiment, the remote UE 313 establishes an RRC connection with the network device 302 via the Uu interface. It should be understood that the first embodiment can be varied, wherein the remote UE 313 can be connected to a non-remote UE in the network device 302 via the PC5 interface, which acts as a relay UE to access the remote UE 313 to the network device 302.

[0076] The following combination Figure 4 A second embodiment of the present invention is described.

[0077] like Figure 4As shown, the network 400 includes a network device 401 and a network device 402 adjacent to each other, and UEs 411, 412, and 313 in a connected state. Non-remote UEs 411 and 412 are connected to the network device 401 via a Uu interface, and a remote UE 413 is located outside the coverage of the network device 301. It is connected to the non-remote UE 412 (i.e., a relay UE) via a PC5 interface, and then accesses the network device 401 via the non-remote UE 412.

[0078] The physical cell identifier of the network device 401 is represented as PCI3; the network device 401 stores relevant information of UE411, 412, 413, such as configuration information and capability information. The configuration information may be bearer information or QoS information, and the capability information may be frequency bands or transmission powers supported by the UE.

[0079] The cell of network device 402 is denoted as PCI4.

[0080] UE 411 and UE 413 are allocated the same C-RNTI (ie, C-RNTI3), while UE 412 is allocated a different C-RNTI (ie, C-RNTI4).

[0081] The non-remote UE 411 gradually moves away from the cell PCI3 of the network device 401, and moves toward the cell PCI4 of the network device 402 (not shown), as indicated by arrow 414. During the movement, the Uu link RLF occurs in the Uulink connected between the non-remote UE 411 and the network device 401, and the non-remote UE 411 sends an RRC reestablishment request message to the network device 402. In this scenario, the network device 401 can be called the original network device, and the network device 402 can be called the target network device.

[0082] The RRC reestablishment request message sent by the non-remote UE 411 to the network device 402 includes a PCI field, a C-RNTI field, and information related to the UE type. The information in the PCI field indicates that the cell where the non-remote UE 411 is located is PCI3. The information in the C-RNTI field indicates that the C-RNTI of the non-remote UE 411 is C-RNTI3. The information related to the UE type may be a device information field, which is used to determine that the non-remote UE 411 is a non-remote UE type. For example, the device information field may be a spare bit (which is set to one of 1 and 0 to indicate that the non-remote UE 411 is a non-remote UE type), or an extended field (which does not include a layer 2 identifier about the relay UE, thereby indicating that the non-remote UE 411 is a non-remote UE type); the information related to the UE type may also be that the device information field is not included in the RRC reconstruction request (for example, the RRC reconstruction request does not include the extended field and the spare bit of the RRC reconstruction request is not configured), which can be used to determine that the non-remote UE 411 is a non-remote UE type.

[0083] After receiving the message of the RRC reestablishment request, the network device 402 obtains the PCI3, C-RNTI3 and the information related to the UE type corresponding to the non-remote UE 411 (it determines that the non-remote UE 411 is a non-remote UE type). Then, the network device 402 communicates with the network device 401 based on the PCI3, C-RNTI3 and the information related to the UE type. For example, the network device 402 establishes a connection with the network device 401 through the PCI3, and sends the C-RNTI3 and the information related to the UE type to the network device 401.

[0084] After receiving C-RNTI3 and information related to the UE type, network device 401 can uniquely determine that the UE initiating the RRC reestablishment request is non-remote UE 411; then, configuration information and / or capability information related to non-remote UE 411 is sent to network device 402.

[0085] The network device 402 receives the configuration information and / or capability information related to the non-remote UE 411 sent by the network device 401, and establishes an RRC connection with the non-remote UE 411 through the Uu interface based on the information.

[0086] After completing the RRC connection, the non-remote UE 411 sends the RRC connection establishment completion information to the network device 402 through the Uu interface; at this time, the non-remote UE 411 is a non-remote UE of the network device 402.

[0087] In the second embodiment, the non-remote UE 411 establishes an RRC connection with the network device 402 via the Uu interface. It should be understood that the second embodiment can be varied, wherein the UE 411 can be connected to a non-remote UE in the network device 402 via the PC5 interface, which acts as a relay UE to access the UE 411 to the network device 402.

[0088] An embodiment of the present invention further provides a user equipment, including a memory and a processor, wherein the memory stores computer instructions that can be executed on the processor, and when the processor executes the computer instructions, the steps of any of the above-mentioned UE reestablishing RRC connection methods are executed.

[0089] An embodiment of the present invention further provides a storage medium on which computer instructions are stored. When the computer instructions are executed, the steps of any one of the above-mentioned methods for UE to reestablish RRC connection are executed.

[0090] like Figure 5 As shown, an embodiment of the present invention further provides a user device 500, including: a first acquisition module 510, which is suitable for acquiring a C-RNTI; a first determination module 520, which is suitable for determining that the link of the UE is in an RLF state; a sending module 530, which is suitable for sending an RRC reconstruction request to a network device, including a device information field indicating whether the UE is a remote UE or a non-remote UE.

[0091] In a specific implementation, the first determination module 520 is adapted to determine that the PC5 edge link of the UE is in an RLF state; the sending module 530 is adapted to send an RRC reconstruction request to a network device, wherein the device information field indicates that the UE is a remote UE.

[0092] In a specific implementation, the first determining module 520 is adapted to determine that the Uu link of the UE is in the RLF state; the sending module 530 is adapted to send an RRC reestablishment request to the network device, wherein the device information field indicates that the UE is a non-remote UE.

[0093] In a specific implementation, the device information field includes a spare bit, which is suitable for being set to one of 0 and 1 to indicate that the UE is a remote UE and the other to indicate that the UE is a non-remote UE.

[0094] In a specific implementation, the device information field includes an extended field, which includes a layer 2 identifier of the relay UE, indicating that the UE is a remote UE.

[0095] The modules of the user device and their related relationships in the embodiment of the present invention can refer to the above-mentioned combination Figures 1 to 4 Relevant description of the UE reestablishing RRC connection method.

[0096] like Figure 6As shown, the embodiment of the present invention provides a method 600 for a network device to reestablish an RRC connection, which may include:

[0097] S610, allocating a C-RNTI to a UE, where the UE includes a remote UE and a non-remote UE, and the C-RNTI can be multiplexed by the remote UE and the non-remote UE;

[0098] S620, receiving an RRC reestablishment request sent by the UE;

[0099] S630, obtaining a device information field in the RRC reestablishment request;

[0100] S640: Determine whether the UE is a remote UE or a non-remote UE based on the information in the device information field.

[0101] During the execution of step S610, the network device may allocate C-RNTI to the UE, for example, allocate C-RNTI to non-remote UE (which may include relay UE) via Uu link, and allocate C-RNTI to remote UE via Uu link and PC5 sidelink.

[0102] During the execution of step S620, after the UE's link (e.g., the UE's PC5 sidelink or the UE's Uu link) is in the RLF state, the UE will send an RRC re-establishment request message to the network device, which includes a device information field indicating whether the UE is a remote UE or a non-remote UE; accordingly, the network device will receive the RRC re-establishment request message.

[0103] During the execution of step S630, the network device may parse the received RRC reestablishment request message and obtain the device information field therein.

[0104] During the execution of step S640 , the network device may determine whether the UE is a remote UE or a non-remote UE based on the information in the device information field.

[0105] In a specific implementation, the device information field may include a spare bit; if the network device detects that the spare bit is one of 0 and 1, it determines that the UE is a remote UE; if it is the other of 0 and 1, it determines that the UE is a non-remote UE.

[0106] In a specific implementation, the device information field may include an extended field, which includes a layer 2 identifier for the relay UE, indicating that the UE is a remote UE; if the network device detects that the device information field includes a layer 2 identifier, it determines that the UE is a remote UE; if it does not include a layer 2 identifier, it determines that the UE is a non-remote UE.

[0107] In a specific implementation, the network device (i.e., the current network device that receives the RRC reconstruction request) may also perform the following steps: obtain the PCI and C-RNTI corresponding to the UE from the RRC reconstruction request; communicate with the original network device based on the PCI, C-RNTI and the user equipment information determined by the device information field, where the original network device is the network device with which the UE last established an RRC connection before the PC5 side link RLF or Uu link RLF occurred; obtain the UE's configuration information and / or capability information obtained from the original network device based on the PCI, C-RNTI and the user equipment information; and establish an RRC connection with the UE based on the configuration information and / or capability information.

[0108] The various steps and their correlations of the method for reestablishing an RRC connection by a network device in the embodiment of the present invention can refer to the above-mentioned combination Figures 1 to 4 Relevant description of the UE reestablishing RRC connection method.

[0109] An embodiment of the present invention further provides a network device, including a memory and a processor, wherein the memory stores computer instructions that can be executed on the processor, and when the processor executes the computer instructions, the steps of any of the above-mentioned methods for reestablishing an RRC connection of a network device are executed.

[0110] An embodiment of the present invention further provides a storage medium on which computer instructions are stored. When the computer instructions are executed, the steps of any of the above-mentioned methods for reestablishing an RRC connection by a network device are executed.

[0111] like Figure 7 As shown, the embodiment of the present invention further provides a network device 700, including:

[0112] An allocation module 710 is adapted to allocate a C-RNTI to a UE, wherein the UE includes a remote UE and a non-remote UE, and the C-RNTI can be multiplexed by the remote UE and the non-remote UE; a receiving module 720 is adapted to receive an RRC reconstruction request sent by the UE; a second acquisition module 730 is adapted to obtain a device information field in the RRC reconstruction request; and a second determination module 740 is adapted to determine whether the UE is a remote UE or a non-remote UE based on information in the device information field.

[0113] In a specific implementation, the device information field includes a spare bit, and the network apparatus includes a third determination module, which is adapted to determine that the UE is a remote UE if the spare bit is one of 0 and 1, and determine that the UE is a non-remote UE if the spare bit is the same as 0 or 1.

[0114] In a specific implementation, the device information field includes an extended field, which includes a layer 2 identifier about the relay UE, and the network device includes a fourth determination module, which is suitable for determining that the UE is a remote UE if the device information field includes the layer 2 identifier, and determining that the UE is a non-remote UE if the layer 2 identifier is not included.

[0115] In a specific implementation, the network device 700 also includes: a third acquisition module, which is suitable for obtaining the PCI and C-RNTI corresponding to the UE from the RRC reconstruction request; a first connection module, which is suitable for communicating with the original network device based on the PCI, C-RNTI and the user equipment information determined by the device information field, and the original network device is the network device with which the UE last established an RRC connection before the PC5 side link RLF or Uu link RLF occurred; a fourth acquisition module, which is suitable for obtaining the configuration information and / or capability information of the UE from the original network device; a second connection module, which is suitable for establishing an RRC connection with the UE based on the configuration information and / or capability information.

[0116] The modules of the network device in the embodiment of the present invention and their related relationships may refer to the related description in the above-mentioned method for reestablishing an RRC connection by a network device.

[0117] Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the scope defined by the claims.

Claims

1. A method for reestablishing an RRC connection by a user equipment, wherein the user equipment comprises a side link remote user equipment and a non-side link remote user equipment, characterized in that: The side link remote user equipment and the non-side link remote user equipment multiplex a cell radio network temporary identifier C-RNTI, and the method comprises: S110, obtaining a C-RNTI, wherein one C-RNTI or each of the multiple C-RNTIs is multiplexed between its corresponding edge link remote user equipment and non-edge link remote user equipment; S120, determining that the link of the user equipment is in an RLF state; S130: Send an RRC reestablishment request to a network device, wherein the request includes a device information field indicating whether the user equipment is the side link remote user equipment or the non-side link remote user equipment.

2. The method according to claim 1, characterized in that include: The S120 includes determining that the PC5 side link of the user equipment is in the RLF state; The S130 includes sending an RRC reestablishment request to the network device, wherein the device information field indicates that the user equipment is the side link remote user equipment.

3. The method according to claim 1, characterized in that: include: The S120 includes determining that the Uu link of the user equipment is in a RLF state; The S130 includes sending an RRC reestablishment request to the network device, wherein the device information field indicates that the user equipment is the non-side link remote user equipment.

4. The method according to claim 1, characterized in that The device information field includes a spare bit in the RRC reestablishment request, which is set to one of 0 and 1 to indicate that the user equipment is a side link remote user equipment and the other to indicate that the user equipment is a non-side link remote user equipment.

5. The method according to claim 1, characterized in that The device information field includes an extended field, which includes a layer 2 identifier of a side link relay user equipment, indicating that the user equipment is a side link remote user equipment.

6. A user device comprising a memory and a processor, wherein the memory stores computer instructions executable on the processor, characterized in that: When the processor executes the computer instructions, the steps of the method according to any one of claims 1 to 5 are performed.

7. A storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed, the steps of the method according to any one of claims 1 to 5 are executed.

8. A user device, characterized in that: The side link remote user equipment and the non-side link remote user equipment multiplex a cell radio network temporary identifier C-RNTI, and the device includes: A first acquisition module, which is adapted to acquire a C-RNTI, one C-RNTI or each of the multiple C-RNTIs is multiplexed between its corresponding side link remote user equipment and non-side link remote user equipment; A first determining module, adapted to determine that a link of the user equipment is in an RLF state; The sending module is adapted to send an RRC reestablishment request to a network device, wherein the request includes a device information field indicating whether the user equipment is a side link remote user equipment or a non-side link remote user equipment.

9. The user device according to claim 8, characterized in that include: The first determination module is adapted to determine that the PC5 edge link of the user equipment is in an RLF state; The sending module is adapted to send an RRC reestablishment request to the network device, wherein the device information field indicates that the user equipment is the side link remote user equipment.

10. The user device according to claim 8, characterized in that include: The first determining module is adapted to determine that the Uu link of the user equipment is in an RLF state; The sending module is adapted to send an RRC reestablishment request to the network device, wherein the device information field indicates that the user equipment is the non-side link remote user equipment.

11. The user device according to claim 8, characterized in that The device information field includes a spare bit in the RRC reestablishment request, which is suitable for being set to one of 0 and 1 to indicate that the user equipment is a side link remote user equipment and the other to indicate that the user equipment is a non-side link remote user equipment.

12. The user device according to claim 8, characterized in that The device information field includes an extended field, which includes a layer 2 identifier of a side link relay user equipment, indicating that the user equipment is a side link remote user equipment.

13. A method for reestablishing an RRC connection by a network device, characterized in that: include: Allocating a C-RNTI to a user equipment, the user equipment comprising an edge link remote user equipment and a non-edge link remote user equipment, the C-RNTI being multiplexed by the edge link remote user equipment and the non-edge link remote user equipment, one C-RNTI or each of the multiple C-RNTIs being multiplexed between the edge link remote user equipment and the non-edge link remote user equipment corresponding thereto; Receiving an RRC reestablishment request sent by the user equipment; Obtaining the device information field in the RRC reestablishment request; Based on the information in the device information field, it is determined whether the user equipment is the side link remote user equipment or the non-side link remote user equipment.

14. The method according to claim 13, characterized in that The device information field includes a spare bit, and the method includes: if the spare bit is one of 0 and 1, determining that the user equipment is an edge link remote user equipment; if the spare bit is the other of 0 and 1, determining that the user equipment is a non-edge link remote user equipment.

15. The method according to claim 13, characterized in that The device information field includes an extended field, which includes a layer 2 identifier for an edge link relay user device. The method includes: if the device information field includes the layer 2 identifier, determining that the user device is an edge link remote user device; if the device information field does not include the layer 2 identifier, determining that the user device is a non-edge link remote user device.

16. The method according to claim 13, characterized in that include: Acquire a PCI and a C-RNTI corresponding to the user equipment from the RRC reestablishment request; Communicate with an original network device based on the PCI, the C-RNTI and the user equipment information determined by the device information field, the original network device being the network device with which the user equipment established an RRC connection most recently before the PC5 edge link RLF or the Uu link RLF occurred; Acquire, from the original network device, configuration information and / or capability information of the user equipment obtained based on the PCI, the C-RNTI and the user equipment information; An RRC connection is established with the user equipment based on the configuration information and / or the capability information.

17. A network device comprising a memory and a processor, wherein the memory stores computer instructions that can be executed on the processor, characterized in that: When the processor executes the computer instructions, the steps of the method according to any one of claims 13 to 16 are performed.

18. A storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed, the steps of the method according to any one of claims 13 to 16 are performed.

19. A network device, characterized in that: include: An allocation module, which is adapted to allocate a C-RNTI to a user equipment, wherein the user equipment includes an edge link remote user equipment and a non-edge link remote user equipment, wherein the C-RNTI can be multiplexed by the edge link remote user equipment and the non-edge link remote user equipment, and each C-RNTI in one or more C-RNTIs is multiplexed between its corresponding edge link remote user equipment and the non-edge link remote user equipment; A receiving module, adapted to receive an RRC reestablishment request sent by a user equipment; A second acquisition module, adapted to acquire a device information field in the RRC reconstruction request; The second determination module is adapted to determine whether the user equipment is a side-link remote user equipment or a non-side-link remote user equipment based on the information in the device information field.

20. The network device according to claim 19, characterized in that: The device information field includes a spare bit, and the network device includes a third determination module, which is suitable for determining that the user equipment is a side link remote user equipment if the spare bit is one of 0 and 1, and determining that the user equipment is a non-side link remote user equipment if the other is 0 or 1.

21. The network device according to claim 19, characterized in that: The device information field includes an extended field, which includes a layer 2 identifier for an edge link relay user equipment. The network device includes a fourth determination module, which is suitable for determining that the user equipment is an edge link remote user equipment if the device information field includes the layer 2 identifier, and determining that the user equipment is a non-edge link remote user equipment if the layer 2 identifier is not included.

22. The network device according to claim 19, characterized in that: include: A third acquisition module, adapted to acquire a PCI and a C-RNTI corresponding to the user equipment from the RRC reconstruction request; A first connection module, which is adapted to communicate with an original network device based on the PCI, the C-RNTI and the user equipment information determined by the device information field, the original network device being the network device with which the user equipment established an RRC connection most recently before the PC5 edge link RLF or the Uu link RLF occurred; a fourth acquisition module, adapted to acquire configuration information and / or capability information of the user equipment from the original network device; A second connection module is adapted to establish an RRC connection with the user equipment based on the configuration information and / or the capability information.

Images