WO2023280203A1 - 由用户设备执行的方法及用户设备 - Google Patents

由用户设备执行的方法及用户设备 Download PDF

Info

Publication number
WO2023280203A1
WO2023280203A1 PCT/CN2022/104118 CN2022104118W WO2023280203A1 WO 2023280203 A1 WO2023280203 A1 WO 2023280203A1 CN 2022104118 W CN2022104118 W CN 2022104118W WO 2023280203 A1 WO2023280203 A1 WO 2023280203A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc entity
remote
srb1
relay
current serving
Prior art date
Application number
PCT/CN2022/104118
Other languages
English (en)
French (fr)
Inventor
张崇铭
山田升平
Original Assignee
夏普株式会社
张崇铭
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 张崇铭 filed Critical 夏普株式会社
Publication of WO2023280203A1 publication Critical patent/WO2023280203A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment

Definitions

  • the present invention relates to the technical field of wireless communication, and more specifically, the present invention relates to a method for performing RLC in a sidelink communication relay architecture by user equipment and the corresponding user equipment.
  • version 16 was based on the V2X feasibility research topic of 5G NR network technology (see non-patent literature: RP-181480, New SID Proposal: Study on NR V2X) was approved.
  • the main functions included in version 16 of NR V2X are to support unicast, multicast and broadcast in scenarios with and without network coverage.
  • NR sidelink relaying sidelink communication relay
  • RP-210904 New Study Item on NR Sidelink Relaying a work item for NR sidelink relaying (sidelink communication relay) of version 17 was proposed (see non-patent literature: RP-210904 New Study Item on NR Sidelink Relaying) , and is approved.
  • One of the objectives of this work item is to standardize sidelink communication control plane procedures, such as the management of RRC connections.
  • the UE can establish an RRC connection with the base station through a relay UE (relay UE).
  • a relay UE may be called a remote UE (remote UE).
  • the remote UE communicates with the relay UE through a sidelink link (sidelink), and the communication interface of the sidelink link is a PC5 interface.
  • the Uu interface is still used for communication between the Relay UE and the base station.
  • the PC5 RLC entity associated with SRB1 corresponds to the currently serving relay UE, which is denoted as relay UE-A here.
  • the remote UE When the remote UE receives the RRC connection release message carrying the suspend information sent by the base station, the UE suspends SRB1 (suspend SRB1), and re-establishes the RLC entities associated with SRB1 (re-establish RLC entities for SRB1), and then enter the RRC INACTIVE state.
  • the UE can start the RRC connection resume (RRC connection resume) process.
  • the UE Before the UE enters the connected state, the UE may undergo relay reselection, that is, the currently serving relay (denoted as relay UE-B) is no longer the previous relay UE-A.
  • the PC5 RLC entity associated with SRB1 still corresponds to the relay UE-A, which will cause the remote UE to be unable to receive the SRB1 message sent by the base station, thus unable to communicate with the base station normally.
  • the present invention provides a method executed by user equipment and the user equipment.
  • a method performed by a user equipment is provided, which is a method performed by a remote UE and a relay UE during the RRC connection management process, including the following steps:
  • the remote UE starts the RRC connection recovery process to determine whether SRB1 has an associated PC5 RLC entity,
  • the remote UE establishes a PC5 RLC entity associated with SRB1,
  • the remote UE reconstructs the PC5 RLC entity, and further determines whether the reconstructed PC5 RLC entity corresponds to the current serving relay UE, or corresponds to the current serving relay as destination address of the target,
  • the remote UE If the re-established PC5 RLC entity does not correspond to the current serving relay UE, or does not correspond to the destination address targeting the current serving relay, the remote UE combines the re-established PC5 RLC entity with the current serving relay associated with the relay UE, or associated with the destination address targeting the current serving relay.
  • a method performed by a user equipment is provided, which is a method performed by a remote UE and a relay UE during the RRC connection management process, including the following steps:
  • the remote UE starts the RRC connection recovery process to determine whether SRB1 has an associated PC5 RLC entity,
  • the remote UE establishes a PC5 RLC entity associated with SRB1,
  • the remote UE judges whether the relay UE corresponding to the PC5 RLC entity is the current serving relay UE, or whether the destination address corresponding to the PC5 RLC entity corresponds to the current serving Relay UE,
  • the remote UE releases the PC5 RLC entity and is SRB1 Create a PC5 RLC entity, or, re-establish the PC5 RLC entity.
  • the PC5 RLC entity established by the remote UE corresponds to the current serving relay UE, or corresponds to the destination address targeting the current serving relay,
  • the PC5 RLC entity recreated by the remote UE is associated with the current serving relay UE, or is associated with the destination address targeting the current serving relay.
  • the remote UE receives an RRC connection release message from the base station, in which the pending configuration information is carried;
  • the remote UE Based on the received pending configuration information, the remote UE releases the PC5 RLC entity associated with SRB1.
  • the remote UE releases the PC5 RLC entity associated with SRB1, and establishes a PC5 RLC entity associated with SRB1, and the PC5 RLC entity corresponds to the selected relay UE,
  • the remote UE If the remote UE is in an idle state, the remote UE does not perform the above operations.
  • the remote UE When the remote UE starts the RRC connection recovery process, it also performs the following operations:
  • the establishment of an RLC entity includes at least:
  • Reconstruction of RLC entities includes at least:
  • the PC5 RLC entity adopts the default configuration, which is the default configuration used for SRB1 transmission on the PC5 interface.
  • a user equipment including:
  • the above-mentioned instructions when executed by the above-mentioned processor, cause the above-mentioned user equipment to perform the method according to the above-mentioned description.
  • FIG. 1 is a schematic diagram showing UE-to-Network relay.
  • Fig. 2 is a schematic diagram showing the control plane protocol stack of UE-to-Network L2 architecture.
  • Fig. 3 is a flowchart representing a method performed by a UE.
  • Fig. 4 is a flowchart representing another method performed by a UE.
  • Fig. 5 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • UE User Equipment user equipment
  • MAC CE MAC control element
  • RLC Radio Link Control wireless link control
  • SDAP Service Data Adaptation Protocol Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol Packet Data Convergence Protocol
  • RRC Radio Resource Control radio resource control
  • RRC_IDLE RRC idle state
  • RAN Radio Access Network, wireless access network
  • SCI Sidelink Control Information, side link communication control information
  • MIB Master Information Block, master information block
  • New Radio new radio
  • SIB System Information Block, system information block
  • NG-RAN NG Radio Access Network, a new generation of radio access network
  • DCI Downlink Control Information, downlink control information
  • ADAPT Adaptation layer, side link communication adaptation layer
  • PHY physical layer, physical layer
  • RB radio bearer, wireless bearer
  • DRB Data Radio Bearer, data radio bearer
  • SRB Signaling Radio Bearer, signaling radio bearer
  • SDU Service Data Unit service data unit
  • V2X Vehicle-to-Everything Internet of Vehicles
  • CCCH Common Control Channel public control channel
  • DCCH Dedicated Control Channel dedicated control channel
  • the network, base station and RAN can be used interchangeably, and the network can be a long-term evolution LTE network, a new radio access technology (New RAT, NR) network, an enhanced long-term evolution eLTE network, or a subsequent evolution version of 3GPP Other networks defined in .
  • New RAT new radio access technology
  • eLTE enhanced long-term evolution eLTE network
  • the user equipment UE may refer to the NR equipment supporting the NR Sidelink relay function described in the background technology, or may refer to the NR equipment supporting the NR sidelink relay architecture, or may refer to other types of NR equipment or LTE equipment.
  • sidelink and PC5 can be used interchangeably, and RLC channel (channel), RLC entity and RLC bearer (bearer) can be used interchangeably.
  • the PC5 interface is an interface for Sidelink communication between the UE and the UE on the control plane and the user plane.
  • the PC5-RRC connection is an AS layer logical connection between a pair of source layer 2 IDs and target layer 2 IDs.
  • the establishment of a PC5 unicast link corresponds to the establishment of a PC5-RRC connection.
  • the remote UE-to-Network relay is shown in Figure 1.
  • the remote UE is on the left, the relay UE is in the middle, and the network is on the right; in scenario 3, the networks are on both sides, and the middle is from the left To the right are the remote UE and the relay UE.
  • the remote UE is connected to the relay UE through the PC5 interface, and the relay UE is connected to the network through the Uu interface. Since the remote UE is far away from the network or the communication environment is not good, the relay UE needs to relay and forward the signaling and data between the two.
  • Both the Remote UE and the Relay UE are within the coverage area and are in the same cell;
  • Both the Remote UE and the Relay UE are within the coverage area, but in different cells.
  • the Remote UE After the Remote UE selects a relay UE to provide relay services for itself, it will establish a PC5-RRC connection with the relay UE to communicate with the network through the relay UE.
  • the remote UE can establish an air interface RRC connection with the network through the relay UE for data transmission between the remote UE and the network.
  • the Remote UE will send the air interface RRC connection setup (setup), re-establishment (re-establish), and resume (resume) messages to the network to encapsulate the data through the Uu PDCP layer, and then submit it to the PC5 RLC entity for further encapsulation, and carry it on the PC5 RLC On the channel, it is submitted layer by layer through PC5-MAC and PC5-PHY.
  • the relay UE After the relay UE receives the data carrying the message, it submits it layer by layer through the PC5-PHY and PC5-MAC.
  • the relay UE finds the Uu RLC channel carrying the message through the mapping relationship between the PC5 RLC channel and the Uu RLC channel, and sends the Messages are encapsulated in Uu messages/data and sent to the network.
  • the base station encapsulates the RRC message returned by the network into the Uu message/data and sends it to the relay UE.
  • the relay UE finds the PC5 RLC channel carrying the message through the mapping relationship between the PC5 RLC channel and the Uu RLC channel, and transmits the message Encapsulated in PC5 message/data and sent to remote UE.
  • Uu RLC/MAC and PC5 RLC/MAC When the Remote UE initiates RRC connection establishment, reconstruction, and recovery processes to the network, Uu RLC/MAC and PC5 RLC/MAC also need to perform corresponding processing in order to correctly transmit data when needed and stop data transmission in time when not needed. . Conversely, the network can also release and suspend the air interface RRC connection to the remote UE through the relay UE. In these processes, Uu RLC/MAC and PC5 RLC/MAC also need to be processed accordingly.
  • the UE sends an RRC connection establishment request message, an RRC connection re-establishment request message, and an RRC connection recovery request message to the base station through SRB0.
  • SRB0 is used to carry RRC messages transmitted using a logical channel whose logical channel type is CCCH (SRB0 is for RRC messages using the CCCH logical channel).
  • the RRC connection establishment request message, the RRC connection re-establishment request message, and the RRC connection recovery request message all belong to such RRC messages transmitted by using a logical channel whose logical channel type is CCCH.
  • the RRC message transmitted on SRB0 may be referred to as SRB0 message (SRB0 message) for short.
  • the UE sends an RRC connection recovery request message to the base station through SRBO.
  • the base station may send an RRC connection recovery message to the UE through SRB1.
  • the UE sends an RRC connection re-establishment request message to the base station through SRB0.
  • the base station can send an RRC connection reestablishment message to the UE through SRB1.
  • SRB1 is used to carry RRC messages transmitted using a logical channel whose logical channel type is DCCH (SRB1 is for RRC messages using the DCCH logical channel).
  • both the RRC connection recovery message and the RRC connection re-establishment message belong to such RRC messages transmitted using a logical channel whose logical channel type is CCCH.
  • the RRC message transmitted on SRB1 may be referred to as SRB1 message (SRB1 message) for short.
  • the wireless communication interface between Remote UE and relay UE The remote UE and the relay UE communicate through a sidelink (sidelink), and the communication interface of the sidelink link is the PC5 interface, so the descriptions of sidelink and PC5 in this article can be replaced with each other.
  • sidelink sidelink
  • PC5 interface the communication interface of the sidelink link
  • the PC5 RLC entity refers to the RLC entity used for PC5 interface communication.
  • UE can use E-UTRAN to communicate with eNB on Uu interface.
  • UE can also use NR to communicate with gNB on Uu interface.
  • the Uu RLC entity refers to the RLC entity used for Uu interface communication.
  • both the PC5 RLC entity and the Uu RCL entity refer to the RLC entity that complies with the RLC protocol stack, but the communication interfaces used by the two are different.
  • the remote UE and the relay UE can correctly process the PC5 RLC and Uu RLC in the air interface RRC connection related process between the remote UE and the base station, so as to correctly set the variables of the RLC layer in the air interface RRC connection establishment and other processes, ensuring The correctness of data transmission to avoid abnormal process.
  • This embodiment provides a method performed by the UE, which is a method performed by the remote UE and the relay UE during the RRC connection management process. As shown in Figure 3, the method includes the following steps.
  • Step S301 the Remote UE starts the RRC connection recovery (resume) flow (process).
  • the Remote UE determines whether SRB1 has an associated PC5 RLC entity:
  • the remote UE establishes a PC5 RLC entity associated with SRB1 (step S302), and preferably, the PC5 RLC entity corresponds to The current serving relay UE, or the destination address corresponding to the current serving relay.
  • the remote UE can rebuild the PC5 RLC entity, and preferably, continue to determine whether the PC5 RLC entity corresponds to the current serving relay UE, or corresponding to the destination address targeting the current service relay (step S303):
  • the PC5 RLC entity is associated with the current serving relayUE associated (or associated with the destination address targeting the current service relay) (step S304).
  • step S305 if the judgment result is that the PC5 RLC entity corresponds to the current serving relay UE (Yes in step S303), then perform other operations (step S305).
  • Yet another implementation manner of the above solution may be: as shown in FIG. 4 , the method performed by the UE includes the following steps.
  • Step S401 the Remote UE starts the RRC connection recovery process (process).
  • the Remote UE determines whether SRB1 has an associated PC5 RLC entity:
  • the remote UE establishes a PC5 RLC entity associated with SRB1 (step S402), and preferably, the PC5 RLC entity corresponds to The current serving relay UE, or the destination address corresponding to the current serving relay.
  • step S401 If the judgment result is that there is a PC5 RLC entity associated with SRB1 (Yes in step S401), then the remote UE judges whether the relay UE corresponding to the PC5 RLC entity is the current serving relay UE, or judges whether the PC5 RLC entity corresponds to the Whether the destination address points to/corresponds to the current service relay UE (step S403):
  • step S403 In the case that the relay UE corresponding to the PC5 RLC entity is not the current serving relay UE (or the destination address corresponding to the PC5 RLC entity does not point to/corresponds to the current serving relay UE) (step S403 is No),
  • the Remote UE can release the PC5 RLC entity, and establish a PC5 RLC entity for SRB1, and preferably, the PC5 RLC entity corresponds to the current serving relay UE, or corresponds to the destination address targeting the current serving relay; or,
  • the Remote UE can also re-establish the PC5 RLC entity, and preferably associate the PC5 RLC entity with the current serving relay UE (or associate with the destination address targeting the current serving relay) (step S404).
  • step S403 In the case that the relay UE corresponding to the PC5 RLC entity is the current serving relay UE (or the destination address corresponding to the PC5 RLC entity points to/corresponds to the current serving relay UE) (step S403 is yes), then perform other operations (step S405).
  • the remote UE restores SRB1.
  • the remote UE re-establishes the PDCP entity associated with SRB1.
  • a default configuration (default configuration) is adopted for the PC5 RLC entity, and the default configuration may be the default configuration used for SRB1 transmission on the PC5 interface.
  • Such configuration information may at least include the RLC entity mode (RLC mode), the priority of the logical channel, the group number of the logical channel, and the like.
  • RLC mode the RLC entity mode
  • AM Acknowledged Mode
  • the value (value) of the priority of the logical channel is 1
  • the value of the group number of the logical channel is 0.
  • the relay UE can establish RLC entities/bearers and logical channels using such configuration information.
  • Remote UE can establish a specific sidelink SRB/DRB to carry SRB1 messages, or to carry messages transmitted using a logical channel of a dedicated logical channel category (such as DCCH), or to carry out SRB1 in relay mode Transmission (for SRB1 via relay).
  • a sidelink SRB/DRB may be called RB-X.
  • the Remote UE starts the RRC connection recovery (resume) procedure (process).
  • Remote UE judges whether RB-X has been established:
  • the remote UE establishes an RB-X, and preferably, the RB-X corresponds to the current serving relay UE, or corresponds to the destination address targeting the current serving relay.
  • the remote UE can rebuild the PDCP entity of RB-X and the RLC entity of the RB-X, and preferably, after rebuilding the PDCP and RLC entity, correspond to the RB-X For the current serving relay UE, or corresponding to the destination address targeting the current serving relay.
  • the Remote UE starts the RRC connection recovery (resume) procedure (process).
  • Remote UE judges whether RB-X has been established:
  • the remote UE establishes an RB-X, and preferably, the RB-X corresponds to the current serving relay UE, or corresponds to the destination address targeting the current serving relay.
  • the remote UE can continue to judge whether the RB-X corresponds to the current serving relay UE, or corresponds to the destination address targeting the current serving relay:
  • the remote UE rebuilds the RLC entity of the RB-X, and preferably, The RB-X is associated with the current service relay UE (or is associated with the destination address targeting the current service relay); or releases the PC5 RLC entity of the RB-X, and then establishes a new PC5 RLC entity, And preferably, make the RB-X or the PC5 RLC entity of the RB-X correspond to the current serving relay UE, or correspond to the destination address targeting the current serving relay.
  • the remote UE restores RB-X.
  • the remote UE re-establishes the PDCP entity of the RB-X.
  • a default configuration (default configuration) is adopted for the PC5 RLC entity, and the default configuration may be the default configuration used for SRB1 transmission on the PC5 interface.
  • Such configuration information may at least include the RLC entity mode (RLC mode), the priority of the logical channel, the group number of the logical channel, and the like.
  • RLC mode the RLC entity mode
  • AM Acknowledged Mode
  • the value (value) of the priority of the logical channel is 1
  • the value of the group number of the logical channel is 0.
  • the relay UE can establish RLC entities/bearers and logical channels using such configuration information.
  • the Remote UE receives the RRC connection release message from the base station, and the message carries configuration information of suspend.
  • the remote UE releases the PC5 RLC entity associated with SRB1.
  • the remote UE releases (release) RB-X
  • the remote UE releases the RLC entity of RB-X, and suspends RB-X.
  • the remote UE can reselect a relay UE, that is, relay reselection (relay reselection) occurs.
  • the remote UE If the remote UE is in the INACTIVE state, then the remote UE releases the PC5 RLC entity associated with SRB1. And optionally, establish a PC5 RLC entity associated with SRB1, and the PC5 RLC entity corresponds to the selected relay UE.
  • the remote UE If the remote UE is in an idle state (IDLE state), then the remote UE does not perform the above operations.
  • the remote UE When the remote UE undergoes relay reselection, if the remote UE is in the INACTIVE state, then the remote UE releases the PC5 RLC entity associated with SRB1. And optionally, establish an associated PC5 RLC entity for SRB1, and the PC5 RLC entity corresponds to the selected relay UE.
  • the establishment of an RLC entity may include at least
  • the re-establishment of the RLC entity may include at least
  • the operation of establishing or rebuilding the RLC entity may also include adopting a default configuration (default configuration) for the PC5 RLC entity, which may be the default configuration used for SRB1 transmission on the PC5 interface .
  • a default configuration default configuration
  • the operations in the foregoing embodiments may be performed during the RRC connection re-establishment process as well as during the RRC connection recovery process/process.
  • the Remote UE starts the RRC connection recovery (resume) process (process) and the Remote UE starts the RRC connection recovery process (process) can be replaced by the Remote UE starts the RRC connection reestablishment (reestablish) process (process) ).
  • Fig. 5 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • the user equipment UE500 includes a processor 501 and a memory 502 .
  • the processor 501 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 502 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memories.
  • Memory 502 has program instructions stored thereon. When the instructions are executed by the processor 501, the above method described in detail in the present invention and executed by the user equipment may be executed.
  • the program running on the device according to the present invention may be a program that causes a computer to realize the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • a program for realizing the functions of the various embodiments of the present invention can be recorded on a computer-readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called “computer system” here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium in which a short-term dynamic storage program is stored, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • a general-purpose processor can be a microprocessor, or it can be any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuits may be digital circuits or analog circuits. Where advances in semiconductor technology have resulted in new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of the invention may also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本发明提供一种由用户设备执行的方法及用户设备,该方法包括如下步骤:远端UE启动RRC连接恢复过程,判断SRB1是否有相关联的PC5 RLC实体,如果不存在与SRB1相关联的PC5 RLC实体,那么远端UE建立一个与SRB1相关联的PC5 RLC实体,如果存在与SRB1相关联的PC5 RLC实体,那么远端UE重建该PC5 RLC实体,进一步判断该重建的PC5 RLC实体是否对应于当前的服务中继UE,或者是对应于以当前的服务中继为目标的目的地址,若不对应于,则远端UE将该重建的PC5 RLC实体与当前的服务中继UE相关联,或者是与以当前的服务中继为目标的目的地址相关联。

Description

由用户设备执行的方法及用户设备 技术领域
本发明涉及无线通信技术领域,更具体地,本发明涉及由用户设备执行侧行链路通信中继架构中RLC的方法以及相应的用户设备。
背景技术
2018年6月,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#80次全会上,版本16基于5G NR网络技术的V2X可行性研究课题(参见非专利文献:RP-181480,New SID Proposal:Study on NR V2X)获得批准。版本16的NR V2X包含的主要功能为支持无网络覆盖和有网络覆盖场景下的单播、组播和广播。
2019年12月,RAN#86次全会上,针对版本17的NR sidelink relaying(侧行链路通信中继)的研究项目被提出(参见非专利文献:RP-193253 New Study Item on NR Sidelink Relaying),并获批准。该研究项目的最新版本参见非专利文献:RP-201474 reivsed SID NR sidelink relay。该研究项目主要研究UE(用户设备)到网络和UE到UE的中继解决方案,用于扩展基于侧行链路通信的覆盖。该研究项目的目标之一是支持侧行链路通信控制面流程。
2020年3月,RAN#91次全会上,针对版本17的NR sidelink relaying(侧行链路通信中继)的工作项目被提出(参见非专利文献:RP-210904 New Study Item on NR Sidelink Relaying),并获批准。该工作项目的目标之一是标准化侧行链路通信控制面流程,例如RRC连接的管理。
UE可以通过中继UE(relay UE)与基站建立RRC连接。这样的UE可以被称为远端UE(remote UE)。Remote UE和relay UE之间通过侧行链路链路(sidelink)通信,侧行链路链路的通信接口为PC5接口。Relay UE和基站之间仍然采用Uu口进行通信。
远端UE通过relay UE和基站建立RRC连接之后,与SRB1相关联的PC5 RLC实体对应于当前服务的relay UE,这里记为relay UE-A。
当远端UE接收到基站发送的、携带挂起(suspend)信息的RRC连接释放消息时,UE将SRB1挂起(suspend SRB1),并且重建与SRB1相关联的RLC实体(re-establish RLC entities for SRB1),然后进入RRC INACTIVE state。
UE为了重新进入RRC连接态,可以启动RRC连接恢复(RRC connection resume)过程。
在UE进入连接态之前,UE可能发生了relay重选,即当前服务的relay(记为relay UE-B)不再是之前的relay UE-A。
但是与SRB1相关联的PC5 RLC实体对应的仍然是relay UE-A,这将导致remote UE无法接收基站发送的SRB1消息,从而无法和基站正常通信。
发明内容
为了解决上述问题,本发明提供一种由用户设备执行的方法以及用户设备。
根据本发明的一个方面,提供了一种由用户设备执行的方法,是远端UE和中继UE在RRC连接管理过程中执行的方法,包括如下步骤:
远端UE启动RRC连接恢复过程,判断SRB1是否有相关联的PC5 RLC实体,
如果不存在与SRB1相关联的PC5 RLC实体,那么远端UE建立一个与SRB1相关联的PC5 RLC实体,
如果存在与SRB1相关联的PC5 RLC实体,那么远端UE重建该PC5 RLC实体,进一步判断该重建的PC5 RLC实体是否对应于当前的服务中继UE,或者是对应于以当前的服务中继为目标的目的地址,
若该重建的PC5 RLC实体不对应于当前的服务中继UE,或者是不对应于以当前的服务中继为目标的目的地址,则远端UE将该重建的PC5 RLC实体与当前的服务中继UE相关联,或者是与以当前的服务中继为目标的目的地址相关联。
根据本发明的另一个方面,提供了一种由用户设备执行的方法,是远端UE和中继UE在RRC连接管理过程中执行的方法,包括如下步骤:
远端UE启动RRC连接恢复过程,判断SRB1是否有相关联的PC5 RLC实体,
如果不存在与SRB1相关联的PC5 RLC实体,那么远端UE建立一个与SRB1相关联的PC5 RLC实体,
如果存在与SRB1相关联的PC5 RLC实体,那么远端UE判断该PC5 RLC实体对应的中继UE是否为当前的服务中继UE,或者是该PC5 RLC实体对应的目的地址是否对应于当前的服务中继UE,
若该PC5 RLC实体对应的中继UE不是当前的服务中继UE,或者是该PC5 RLC实体对应的目的地址不对应于当前的服务中继UE,则远端UE释放该PC5 RLC实体并且为SRB1建立一个PC5 RLC实体,或者是,重建该PC5 RLC实体。
在上述的由用户设备执行的方法中,优选地,
远端UE所建立的PC5 RLC实体对应于当前的服务中继UE,或者是对应于以当前的服务中继为目标的目的地址,
远端UE所重建的PC5 RLC实体与当前的服务中继UE相关联,或者是与以当前的服务中继为目标的目的地址相关联。
在上述的由用户设备执行的方法中,优选地,还包括如下步骤:
远端UE接收来自基站的RRC连接释放消息,在该消息中携带了挂起的配置信息;
基于接收到的挂起的配置信息,远端UE释放与SRB1相关联的PC5 RLC实体。
在上述的由用户设备执行的方法中,优选地,
在发生了中继重选的情况下,
如果远端UE处于非激活态,那么远端UE释放与SRB1相关联的PC5 RLC实体,并且为SRB1建立一个与之关联的PC5 RLC实体,且该PC5 RLC实体对应于被选中的中继UE,
如果远端UE处于空闲态,那么远端UE不执行上述操作。
在上述的由用户设备执行的方法中,优选地,
当远端UE启动RRC连接恢复过程时,还执行下述操作:
重建与SRB1相关联的PDCP实体;
建立与SRB1关联的PC5 RLC实体:或者,
恢复SRB1。
在上述的由用户设备执行的方法中,优选地,
RLC实体的建立至少包括:
建立一个RLC实体;
设置该RLC实体的状态变量为初始值,
RLC实体的重建至少包括:
丢弃所有的RLC SDU、RLC SDU的分段、RLC PDU;
停止并且重置所有的定时器;
重置该RLC实体的状态变量为初始值。
在上述的由用户设备执行的方法中,优选地,
在建立或者重建RLC实体的操作中,对PC5 RLC实体采用默认配置,该默认配置是用于SRB1在PC5接口上传输的默认配置。
根据本发明的另一个方面,提供了一种用户设备,包括:
处理器;以及
存储器,上述存储器上存储有指令,
上述指令在由上述处理器运行时,使上述用户设备执行根据上文所描述的方法。
根据本发明所涉及的由用户设备执行的方法以及相应的用户设备,能够实现与基站的正常通信。
附图说明
图1是表示UE-to-Network中继的示意图。
图2是表示UE-to-Network L2架构控制面协议栈的示意图。
图3是表示由UE执行的一种方法的流程图。
图4是表示由UE执行的另一种方法的流程图。
图5是本发明涉及的用户设备UE的简要结构框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意,本发明不应局限于下文所述的具体实施方式。另外,为了简便起见,省略了对与本发明没有直接关联的公知技术的详细描述,以防止对本发明的理解 造成混淆。
下面描述本发明涉及的部分术语,术语的具体含义见3GPP最新标准规范。
RedCap:Reduced capability功能下降
UE:User Equipment用户设备
NR:New Radio新一代无线技术
MAC:Medium Access Control多媒体接入控制
MAC CE:MAC control element MAC控制元素
RLC:Radio Link Control无线链路控制
SDAP:Service Data Adaptation Protocol服务数据适配协议
PDCP:Packet Data Convergence Protocol分组数据汇聚协议
RRC:Radio Resource Control无线资源控制
RRC_CONNECTED:RRC连接态
RRC_INACTIVE:RRC非激活态
RRC_IDLE:RRC空闲态
RAN:Radio Access Network,无线接入网络
Sidelink:侧行链路通信
SCI:Sidelink Control Information,侧行链路通信控制信息
AS:Access Stratum,接入层
IE:Information Element,信息元素
CE:Control Element,控制元素
MIB:Master Information Block,主信息块
NR:New Radio,新无线电
SIB:System Information Block,***信息块
NG-RAN:NG Radio Access Network,新一代无线接入网络
DCI:Downlink Control Information,下行控制信息
ADAPT:Adaptation layer,侧行链路通信适配层
PHY:physical layer,物理层
RB:radio bearer,无线承载
DRB:Data Radio Bearer,数据无线承载
SRB:Signalling Radio Bearer,信令无线承载
PDU:Protocol Data Unit协议数据单元
SDU:Service Data Unit服务数据单元
V2X:Vehicle-to-Everything车联网
CCCH:Common Control Channel公共控制信道
DCCH:Dedicated Control Channel专有控制信道
本发明中,网络、基站和RAN可互换使用,所述网络可以是长期演进LTE网络、新无线访问技术(New RAT,NR)网络、增强的长期演进eLTE网络,也可以是3GPP后续演进版本中定义的其他网络。
本发明中,用户设备UE可以指背景技术中所述的支持NR Sidelink中继功能的NR设备,也可以指支持NR sidelink中继架构的NR设备,也可以指其他类型的NR设备或者LTE设备。
本发明中,sidelink和PC5可以互换使用,RLC信道(channel)、RLC实体和RLC承载(bearer)可以互换使用。
以下,对本发明的相关技术给出说明。
PC5接口是UE和UE之间进行控制面和用户面Sidelink通信的接口。对于Sidelink单播,PC5-RRC连接是一对源层二ID和目标层二ID之间的AS层逻辑连接。一个PC5单播链路建立就会对应有一个PC5-RRC连接建立。
UE-to-Network中继如图1所示,场景1和场景2中,左侧为远端UE,中间为中继UE,右侧为网络;场景3中,两侧为网络,中间从左到右分别为远端UE和中继UE。远端UE和中继UE之间通过PC5接口连接,中继UE和网络通过Uu口连接。由于远端UE距离网络较远或者通信环境不佳,需要中继UE对两者间的信令和数据进行中继转发。
UE-to-Network中继的场景包含:
1)Remote UE在覆盖范围外,Relay UE在覆盖范围内;
2)Remote UE和Relay UE都在覆盖范围内,并且在同一个小区;
3)Remote UE和Relay UE都在覆盖范围内,但在不同小区。
对于侧行链路通信层二(L2)中继架构,remote UE、relay UE和基站的控制面协议栈如图2所示。
Remote UE选定了一个relay UE为自己提供中继服务后,会和relay UE建立PC5-RRC连接,以便通过relay UE和网络进行通信。Remote UE可以通过relay UE和网络建立空口RRC连接用于remote UE和网络间的数据传输。Remote UE将向网络进行空口RRC连接建立(setup)、重建(re-establish)、恢复(resume)等消息通过Uu PDCP层对数据进行封装,然后递交到PC5 RLC实体进一步封装,并承载在PC5 RLC信道上,通过PC5-MAC和PC5-PHY逐层向下递交。relay UE收到携带该消息的数据后后,通过PC5-PHY和PC5-MAC逐层向上递交,relay UE通过PC5 RLC信道和Uu RLC信道间的映射关系找到承载该消息的Uu RLC信道,将该消息封装在Uu消息/数据中发送给网络。反过来,网络回复的RRC消息由基站将其封装在Uu消息/数据中发送给relay UE,relay UE通过PC5 RLC信道和Uu RLC信道间的映射关系找到承载该消息的PC5 RLC信道,将该消息封装在PC5消息/数据中发送给remote UE。在Remote UE在向网络发起RRC连接建立、重建、恢复等流程时,为了能够在需要时正确传输数据和不需要时及时停止数据传输,Uu RLC/MAC和PC5 RLC/MAC也需要进行相应的处理。反过来,网络也可以通过relay UE向remote UE释放、挂起空口RRC连接,在这些流程中Uu RLC/MAC和PC5 RLC/MAC也需要进行相应的处理。
SRB0消息
在Uu接口上,UE通过SRB0向基站发送RRC连接建立请求消息,RRC连接重建立请求消息,RRC连接恢复请求消息。其中,SRB0是用于承载采用逻辑信道类别为CCCH的逻辑信道进行传输的RRC消息(SRB0 is for RRC messages using the CCCH logical channel)。可见,RRC连接建立请求消息,RRC连接重建立请求消息,RRC连接恢复请求消息都属于这样的采用逻辑信道类别为CCCH的逻辑信道进行传输的RRC消息。在本文中,在SRB0上传输的RRC消息可以简称为SRB0消息(SRB0 message)。
SRB1消息
在Uu接口上,UE通过SRB0向基站发送RRC连接恢复请求消息。作为响应消息,基站可以通过SRB1向UE发送RRC连接恢复消息。或者是UE通过SRB0向基站发送RRC连接重建立请求消息。作为响应消息,基 站可以通过SRB1向UE发送RRC连接重建消息。其中,SRB1是用于承载采用逻辑信道类别为DCCH的逻辑信道进行传输的RRC消息(SRB1 is for RRC messages using the DCCH logical channel)。可见,RRC连接恢复消息以及RRC连接重建立消息都属于这样的采用逻辑信道类别为CCCH的逻辑信道进行传输的RRC消息。在本文中,在SRB1上传输的RRC消息可以简称为SRB1消息(SRB1message)。
PC5接口
Remote UE和relay UE之间的无线通信接口。Remote UE和relay UE之间通过侧行链路(sidelink)通信,侧行链路链路的通信接口为PC5接口,因此在本文中sidelink与PC5的描述可以相互替换。
PC5 RLC实体是指用于PC5接口通信的RLC实体。
Uu接口
UE和基站之间的无线通信接口。UE可以在Uu接口上采用E-UTRAN和eNB通信。UE还可以在Uu接口上采用NR和gNB通信。
Uu RLC实体是指用于Uu接口通信的RLC实体。
在本质上PC5 RLC实体和Uu RCL实体都是指遵从RLC协议栈的RLC实体,只是两者用于的通信接口不同。
通过本发明,remote UE和relay UE可以在remote UE和基站之间空口RRC连接相关流程中,正确处理PC5 RLC和Uu RLC,从而达到在空口RRC连接建立等流程中正确设置RLC层的变量,保证数据传输的正确性,避免流程异常。
以下,详细描述本发明对于上述问题的若干实施例。
实施例1
本实施例给出了一种由UE执行的方法,是remote UE和relay UE在RRC连接管理过程中执行的方法。如图3所示,该方法包括如下步骤。
步骤S301:Remote UE启动RRC连接恢复(resume)流程(过程)。
在这一过程中,Remote UE判断SRB1是否有相关联的PC5 RLC实体:
-如果判断结果是不存在与SRB1相关联的PC5 RLC实体(步骤S301 为否),那么remote UE建立一个与SRB1相关联的PC5 RLC实体(步骤S302),并且优选的,该PC5 RLC实体对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
-如果判断结果是存在与SRB1相关联的PC5 RLC实体(步骤S301为是),那么remote UE可以重建该PC5 RLC实体,以及优选的,继续判断该PC5 RLC实体是否对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址(步骤S303):
-如果判断结果是该PC5 RLC实体不对应于当前的服务relayUE,或者是不对应于以当前服务relay为目标的目的地址(步骤S303为否),那么将该PC5 RLC实体与当前的服务relayUE相关联(或者是与以当前服务relay为目标的目的地址相关联)(步骤S304)。
-如果判断结果是该PC5 RLC实体对应于当前的服务relay UE(步骤S303为是),则执行其它的操作(步骤S305)。
上述方案的又一实施方式可以是:如图4所示,由UE执行的方法包括如下步骤。
步骤S401:Remote UE启动RRC连接恢复流程(过程)。
在这一过程中,Remote UE判断SRB1是否有相关联的PC5 RLC实体:
-如果判断结果是不存在与SRB1相关联的PC5 RLC实体(步骤S401为否),那么remote UE建立一个与SRB1相关联的PC5 RLC实体(步骤S402),并且优选的,该PC5 RLC实体对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
-如果判断结果是存在与SRB1相关联的PC5 RLC实体(步骤S401为是),那么remote UE判断该PC5 RLC实体对应的relay UE是否是当前的服务relay UE,或者是判断该PC5 RLC实体对应的目的地址是否指向/对应于当前的服务relay UE(步骤S403):
在该PC5 RLC实体对应的relay UE不是当前的服务relay UE(或者该PC5 RLC实体对应的目的地址不指向/对应于当前的服务relay UE)的情况下(步骤S403为否),
Remote UE可以释放该PC5 RLC实体,并且为SRB1建立一个PC5 RLC实体,并且优选的,该PC5 RLC实体对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址;或者,
Remote UE还可以重新建立该PC5 RLC实体,并且优选的,将该PC5 RLC实体与当前的服务relay UE相关联(或者是与以当前服务relay为目标的目的地址相关联)(步骤S404)。
在该PC5 RLC实体对应的relay UE是当前的服务relay UE(或者该PC5 RLC实体对应的目的地址指向/对应于当前的服务relay UE)的情况下(步骤S403为是),则执行其它的操作(步骤S405)。
优选的,在remote UE执行上述判断及对应的操作完成之后,remote UE恢复SRB1。
优选的,在remote UE执行上述判断及对应的操作之前,remote UE重建与SRB1相关联的PDCP实体。
优选的,在remote UE执行上述判断及对应的操作时,对PC5 RLC实体采用了默认的配置(default configuration),该默认配置可以是用于SRB1在PC5接口上传输的默认配置。
这样的配置信息中可以至少包含RLC实体的模式(RLC mode)、逻辑信道的优先级、逻辑信道的分组编号等。例如RLC实体的模式的取值(value)为确认模式(Acknowledged Mode,AM);逻辑信道优先级取值(value)为1;逻辑信道的分组编号取值为0。基于这样的配置信息,relay UE可以建立采用了这样的配置信息的RLC实体/承载以及逻辑信道。
实施例2
Remote UE可以建立特定的sidelink SRB/DRB,用于承载SRB1消息,或者是承载采用专有逻辑信道类别的逻辑信道(例如DCCH)进行传输的消息,或者说是用于以relay方式的进行的SRB1传输(for SRB1via relay)。这样的sidelink SRB/DRB可以被称为RB-X。
因此一种实施方案可以是
Remote UE启动RRC连接恢复(resume)流程(过程)。
在这一过程中,Remote UE判断是否已经建立了RB-X:
-如果判断结果是不存在RB-X,那么remote UE建立一个RB-X,并且优选的,该RB-X对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
-如果判断结果是存在RB-X,那么remote UE可以重建RB-X的PDCP实体,以及重建该RB-X的RLC实体,并且优选的,在重建PDCP以及RLC实体之后,将该RB-X对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
另外一种实施方案可以是
Remote UE启动RRC连接恢复(resume)流程(过程)。
在这一过程中,Remote UE判断是否已经建立了RB-X:
-如果判断结果是不存在RB-X,那么remote UE建立一个RB-X,并且优选的,该RB-X对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
-如果判断结果是存在RB-X,那么remote UE还可以继续判断该RB-X是否对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址:
-如果判断结果是该RB-X不对应于当前的服务relay UE,或者是不对应于以当前服务relay为目标的目的地址,那么remote UE重建该RB-X的RLC实体,以及优选的,将该RB-X与当前的服务relay UE相关联(或者是与以当前服务relay为目标的目的地址相关联);或者是释放该RB-X的PC5 RLC实体,然后建立一个新的PC5 RLC实体,并且优选的,使得该RB-X或者该RB-X的PC5 RLC实体对应于当前的服务relay UE,或者是对应于以当前服务relay为目标的目的地址。
-如果判断结果是该RB-X实体对应于当前的服务relay UE,则执行其它的操作。
优选的,在remote UE执行上述判断及对应的操作完成之后,remote UE恢复RB-X。
优选的,在remote UE执行上述判断及对应的操作之前,remote UE重 建RB-X的PDCP实体。
优选的,在remote UE执行上述判断及对应的操作时,对PC5 RLC实体采用了默认的配置(default configuration),该默认配置可以是用于SRB1在PC5接口上传输的默认配置。
这样的配置信息中可以至少包含RLC实体的模式(RLC mode)、逻辑信道的优先级、逻辑信道的分组编号等。例如RLC实体的模式的取值(value)为确认模式(Acknowledged Mode,AM);逻辑信道优先级取值(value)为1;逻辑信道的分组编号取值为0。基于这样的配置信息,relay UE可以建立采用了这样的配置信息的RLC实体/承载以及逻辑信道。
实施例3
Remote UE接收来自基站的RRC连接释放消息,在该消息中携带了挂起(suspend)的配置信息。
基于接收到的挂起的配置信息,
remote UE释放(release)与SRB1相关联的PC5 RLC实体。
或者,remote UE释放(release)RB-X,
或者,remote UE释放RB-X的RLC实体,以及挂起RB-X。
实施例4
依据relay UE和remote UE之间的信号质量或者是电平测量值等,remote UE可以重新选择的一个relay UE,即发生了relay重选(relay reselection)。
如果remote UE处于INACTIVE state,那么remote UE释放与SRB1相关联的PC5 RLC实体。以及可选的,为SRB1建立一个与之关联的PC5 RLC实体,且该PC5 RLC实体对应于被选中的relay UE。
如果remote UE处于空闲态(IDLE state),那么remote UE不执行上述操作。
上述方案的又一实施方式可以是
当remote UE发生了relay重选时,如果remote UE处于INACTIVE state,那么remote UE释放与SRB1相关联的PC5 RLC实体。以及可选的,为SRB1建立一个与之关联的PC5 RLC实体,且该PC5 RLC实体对应于被 选中的relay UE。
实施例5
在实施例3或者4的基础上,当Remote UE启动RRC连接恢复流程时,执行下述操作之一或者多:
-重建与SRB1相关联的PDCP实体;
-建立与SRB1关联的PC5 RLC实体;
-恢复SRB1;
-重建RB-X的PDCP实体;
-建立RB-X的RLC实体;
-恢复RB-X。
实施例6
在前述实施例的操作中,
RLC实体的建立至少可以包括
-建立一个RLC实体
-设置该RLC实体的状态变量为初始值
RLC实体的重新建立至少可以包括
-丢弃所有的RLC SDU,RLC SDU的分段(RLC SDU segment),RLC PDU
-停止并且重置所有的定时器
-重置该RLC实体的状态变量为初始值
实施例7
在前述实施例的操作中,在建立或者重建RLC实体的操作中,还可以包括对PC5 RLC实体采用默认的配置(default configuration),该默认配置可以是用于SRB1在PC5接口上传输的默认配置。
实施例8
前述实施例的操作除了可以在RRC连接恢复流程/过程中进行,还可以在RRC连接重建立过程中进行。
例如在实施例1或者2中的Remote UE启动RRC连接恢复(resume)流程(过程)以及Remote UE启动RRC连接恢复流程(过程)可以被替换为Remote UE启动RRC连接重建立(reestablish)流程(过程)。
图5是本发明涉及的用户设备UE的简要结构框图。如图5所示,该用户设备UE500包括处理器501和存储器502。处理器501例如可以包括微处理器、微控制器、嵌入式处理器等。存储器502例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器502上存储有程序指令。该指令在由处理器501运行时,可以执行本发明详细描述的由用户设备执行的上述方法。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机***读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机***”可以是嵌入在该设备中的计算机***,可以包括操作***或硬件(如***设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如,单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本发明的一个 或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本发明的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本发明也包括不偏离本发明主旨的任何设计改动。另外,可以在权利要求的范围内对本发明进行多种改动,通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的方法,是远端UE和中继UE在RRC连接管理过程中执行的方法,包括如下步骤:
    远端UE启动RRC连接恢复过程,判断SRB1是否有相关联的PC5 RLC实体,
    如果不存在与SRB1相关联的PC5 RLC实体,那么远端UE建立一个与SRB1相关联的PC5 RLC实体,
    如果存在与SRB1相关联的PC5 RLC实体,那么远端UE重建该PC5 RLC实体,进一步判断该重建的PC5 RLC实体是否对应于当前的服务中继UE,或者是对应于以当前的服务中继为目标的目的地址,
    若该重建的PC5 RLC实体不对应于当前的服务中继UE,或者是不对应于以当前的服务中继为目标的目的地址,则远端UE将该重建的PC5 RLC实体与当前的服务中继UE相关联,或者是与以当前的服务中继为目标的目的地址相关联。
  2. 一种由用户设备执行的方法,是远端UE和中继UE在RRC连接管理过程中执行的方法,包括如下步骤:
    远端UE启动RRC连接恢复过程,判断SRB1是否有相关联的PC5 RLC实体,
    如果不存在与SRB1相关联的PC5 RLC实体,那么远端UE建立一个与SRB1相关联的PC5 RLC实体,
    如果存在与SRB1相关联的PC5 RLC实体,那么远端UE判断该PC5 RLC实体对应的中继UE是否为当前的服务中继UE,或者是该PC5 RLC实体对应的目的地址是否对应于当前的服务中继UE,
    若该PC5 RLC实体对应的中继UE不是当前的服务中继UE,或者是该PC5 RLC实体对应的目的地址不对应于当前的服务中继UE,则远端UE释放该PC5 RLC实体并且为SRB1建立一个PC5 RLC实体,或者是,重建该PC5 RLC实体。
  3. 根据权利要求1或2所述的由用户设备执行的方法,其中,
    远端UE所建立的PC5 RLC实体对应于当前的服务中继UE,或者是对应于以当前的服务中继为目标的目的地址,
    远端UE所重建的PC5 RLC实体与当前的服务中继UE相关联,或者是与以当前的服务中继为目标的目的地址相关联。
  4. 根据权利要求1或2所述的由用户设备执行的方法,其中,还包括如下步骤:
    远端UE接收来自基站的RRC连接释放消息,在该消息中携带了挂起的配置信息;
    基于接收到的挂起的配置信息,远端UE释放与SRB1相关联的PC5 RLC实体。
  5. 根据权利要求1或2所述的由用户设备执行的方法,其中,
    在发生了中继重选的情况下,
    如果远端UE处于非激活态,那么远端UE释放与SRB1相关联的PC5 RLC实体,并且为SRB1建立一个与之关联的PC5 RLC实体,且该PC5 RLC实体对应于被选中的中继UE,
    如果远端UE处于空闲态,那么远端UE不执行上述操作。
  6. 根据权利要求4所述的由用户设备执行的方法,其中,
    当远端UE启动RRC连接恢复过程时,还执行下述操作:
    重建与SRB1相关联的PDCP实体;
    建立与SRB1关联的PC5 RLC实体:或者,
    恢复SRB1。
  7. 根据权利要求5所述的由用户设备执行的方法,其中,
    当远端UE启动RRC连接恢复过程时,还执行下述操作:
    重建与SRB1相关联的PDCP实体;
    建立与SRB1关联的PC5 RLC实体:或者,
    恢复SRB1。
  8. 根据权利要求6或7所述的由用户设备执行的方法,其中,
    RLC实体的建立至少包括:
    建立一个RLC实体;
    设置该RLC实体的状态变量为初始值,
    RLC实体的重建至少包括:
    丢弃所有的RLC SDU、RLC SDU的分段、RLC PDU;
    停止并且重置所有的定时器;
    重置该RLC实体的状态变量为初始值。
  9. 根据权利要求8所述的由用户设备执行的方法,其中,
    在建立或者重建RLC实体的操作中,对PC5 RLC实体采用默认配置,该默认配置是用于SRB1在PC5接口上传输的默认配置。
  10. 一种用户设备,包括:
    处理器;以及
    存储器,上述存储器上存储有指令,
    上述指令在由上述处理器运行时,使上述用户设备执行根据权利要求1-9中任一项所述的方法。
PCT/CN2022/104118 2021-07-09 2022-07-06 由用户设备执行的方法及用户设备 WO2023280203A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110781875.X 2021-07-09
CN202110781875.XA CN115604863A (zh) 2021-07-09 2021-07-09 由用户设备执行的方法及用户设备

Publications (1)

Publication Number Publication Date
WO2023280203A1 true WO2023280203A1 (zh) 2023-01-12

Family

ID=84801304

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/104118 WO2023280203A1 (zh) 2021-07-09 2022-07-06 由用户设备执行的方法及用户设备

Country Status (2)

Country Link
CN (1) CN115604863A (zh)
WO (1) WO2023280203A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180077618A1 (en) * 2015-04-09 2018-03-15 Lg Electronics Inc. Method and apparatus for handling l2 entity in channel change for relaying in wireless communication system
CN110831250A (zh) * 2018-08-07 2020-02-21 维沃移动通信有限公司 一种处理方法及终端
CN111465115A (zh) * 2019-01-22 2020-07-28 夏普株式会社 无线链路控制层的重置方法和用户设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180077618A1 (en) * 2015-04-09 2018-03-15 Lg Electronics Inc. Method and apparatus for handling l2 entity in channel change for relaying in wireless communication system
CN110831250A (zh) * 2018-08-07 2020-02-21 维沃移动通信有限公司 一种处理方法及终端
CN111465115A (zh) * 2019-01-22 2020-07-28 夏普株式会社 无线链路控制层的重置方法和用户设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC. (EMAIL DISCUSSION RAPPORTEUR): "Phase 1 [Post111-e][627][Relay] Remaining issues on L2 architecture", 3GPP DRAFT; R2-2009122, vol. RAN WG2, 23 October 2020 (2020-10-23), pages 1 - 86, XP051942146 *

Also Published As

Publication number Publication date
CN115604863A (zh) 2023-01-13

Similar Documents

Publication Publication Date Title
TWI678124B (zh) 使用者設備和相關方法
WO2018171546A1 (zh) 用户设备和基站处执行的方法及相应的设备
WO2020151653A1 (zh) 由用户设备执行的切换方法以及用户设备
WO2020011157A1 (zh) 用户设备的控制方法以及用户设备
WO2023134679A1 (zh) 由用户设备执行的方法及用户设备
AU2018329060A1 (en) Session establishment method and apparatus
WO2022257975A1 (zh) 由用户设备执行的方法及用户设备
WO2023093818A1 (zh) 由用户设备执行的方法及用户设备
WO2023280203A1 (zh) 由用户设备执行的方法及用户设备
JP2020072422A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2023280205A1 (zh) 由用户设备执行的方法及用户设备
WO2023274225A1 (zh) 由用户设备执行的方法以及用户设备
WO2024055956A1 (zh) 由用户设备执行的方法及用户设备
WO2023098865A1 (zh) 由用户设备执行的方法及用户设备
WO2024051681A1 (zh) 由用户设备执行的方法及用户设备
WO2023232070A1 (zh) 由用户设备执行的方法及用户设备
WO2023125294A1 (zh) 由用户设备执行的方法以及用户设备
WO2024067464A1 (zh) 由用户设备执行的方法及用户设备
WO2023001191A1 (zh) 由用户设备执行的方法及用户设备
WO2023246766A1 (zh) 由用户设备执行的方法及用户设备
WO2024125550A1 (zh) 由用户设备执行的方法及用户设备
WO2024067623A1 (zh) 由用户设备执行的方法以及用户设备
WO2023131231A1 (zh) 由用户设备执行的方法以及用户设备
WO2024001948A1 (zh) 由用户设备执行的方法及用户设备
WO2023106315A1 (ja) 端末装置、基地局装置、および、方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22836949

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18573011

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22836949

Country of ref document: EP

Kind code of ref document: A1