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

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

Info

Publication number
WO2023280205A1
WO2023280205A1 PCT/CN2022/104121 CN2022104121W WO2023280205A1 WO 2023280205 A1 WO2023280205 A1 WO 2023280205A1 CN 2022104121 W CN2022104121 W CN 2022104121W WO 2023280205 A1 WO2023280205 A1 WO 2023280205A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
rlc
rlc entity
user equipment
established
Prior art date
Application number
PCT/CN2022/104121
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 夏普株式会社
Priority to US18/574,121 priority Critical patent/US20240244679A1/en
Publication of WO2023280205A1 publication Critical patent/WO2023280205A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection 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 directly establish an RRC connection with the base station (gNB) through the Uu interface.
  • the UE sends an RRC connection establishment 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 message transmitted on SRB0 may be referred to as SRB0 message (SRB0 message) for short.
  • the UE can also establish an RRC connection with the base station (gNB) through a relay UE (relay UE).
  • a relay UE relay UE
  • Such a UE may be called a remote UE (remote UE).
  • the remote UE communicates with the relay UE through a sidelink (sidelink), and the communication interface of the sidelink link is the PC5 interface.
  • the Uu interface is still used for communication between the Relay UE and the base station.
  • the remote UE In order to establish an RRC connection with the base station, the remote UE also needs to send an SRB0 message. Since the remote UE indirectly establishes a connection with the base station through the relay UE, in the protocol framework, the RLC entity associated with this SRB0 is the PC5 RLC entity.
  • the sending UE side when the sending UE side is configured with an RLC entity, the information can be received only when the same configuration information is used to configure the peer RLC entity (peer entity) on the receiving UE side.
  • the present invention discusses the establishment and management of the RLC entity in the RRC connection management process of the remote UE and the relay UE in order to transmit the SRB0 message.
  • the present invention provides a method executed by user equipment and the user equipment.
  • a method performed by user equipment is provided, which is a method for establishing and managing an RLC bearer/entity/channel during an RRC connection management process between a remote UE and a relay UE, including the following steps:
  • the relay UE receives an indication from the upper layer, and the information in the indication includes the information of using an established PC5 RRC connection for relay or relay service, or the information in the indication indicates a dedicated target address A PC5 RRC connection is established and the connection is used for relay or relay service;
  • the relay UE Based on the indication, or upon receiving the indication, the relay UE performs the following operations:
  • the established PC5 RLC bearer, PC5 RLC entity or logical channel is used to bear the SRB0 message, or bear the message transmitted by using the logical channel of the dedicated logical channel category.
  • the established PC5 RLC bearer, PC5 RLC entity or logical channel belongs to a specific sidelink SRB or sidelink DRB, or is associated with a specific sidelink SRB or sidelink DRB.
  • the above-mentioned specific sidelink SRB or sidelink DRB is a default sidelink SRB or sidelink DRB, which is used to carry SRB0 messages, or to carry messages transmitted using logical channels of the dedicated logical channel category.
  • the established PC5 RLC bearer, PC5 RLC entity or logical channel adopts the default configuration, which is used to configure the PC5 RLC bearer, PC5 RLC entity or logical channel used for the bearer/transmission of the SRB0 message.
  • the relay UE receives the PC5 RRC message sent from the remote UE, which carries a relay service request or relay related information;
  • the relay UE Based on the message, or upon receiving the message, the relay UE performs the above operations.
  • the relaying UE also establishes a Uu RLC entity and associates the Uu RLC entity with the established PC5 RLC entity,
  • the Uu RLC entity is used to transmit the SRB0 message from the remote UE.
  • the remote UE receives an indication from the upper layer, and the information in the indication includes the information of using an established PC5 RRC connection for relay or relay service, or the information in the indication indicates a dedicated target address A PC5 RRC connection is established and the connection is used for relay or relay service;
  • the remote UE performs the above operations based on the indication, or upon receiving the indication.
  • 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.
  • the RLC entity can be reliably established and managed in the RRC connection management process.
  • FIG. 1 is a schematic diagram showing that a UE directly establishes an RRC connection with a base station through a Uu interface.
  • FIG. 2 is a schematic diagram showing that a UE establishes an RRC connection with a base station through a relay UE.
  • Fig. 3 is a schematic diagram showing UE-to-Network relay.
  • Fig. 4 is a schematic diagram showing the control plane protocol stack of the UE-to-Network L2 architecture.
  • Fig. 5 is a flowchart representing a method performed by a user equipment UE.
  • Fig. 6 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
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • Evolved UMTS Terrestrial Radio Access Network Evolved UMTS Terrestrial Radio Access Network
  • 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
  • Enb evolved node base station
  • Gnb New generation node base station
  • 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 3.
  • the remote UE is on the left, the relay UE is in the middle, and the network is on the right; 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/base station 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 establishment (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, 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 encapsulates the message in the Uu message/data 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 sends the message Encapsulated in PC5 message/data and sent to remote UE.
  • the Remote UE When the Remote UE initiates RRC connection establishment, re-establishment, and recovery processes to the network, in order to receive and process data correctly, it needs to be established in time between the sending UE (remote UE) and the receiving UE (relay UE) on the PC5 interface. And manage the corresponding PC5 RLC entity.
  • 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 SRBO.
  • 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).
  • 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 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 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 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
  • 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 for the remote UE and the relay UE to establish and manage the RLC bearer (bearer)/RLC entity (entity)/RLC channel (channel) during the RRC connection management process. As shown in Figure 5, the method includes the following steps.
  • Step S501 the Relay UE receives an indication from an upper layer (upper layer), and the information in the indication may include information about using an established PC5 RRC connection for relay or relay service,
  • the indication information indicates that a PC5 RRC connection is established for a dedicated destination address (destination), and that the connection is used for relay or relay service.
  • Step S502 Relay UE performs one or more of the following operations based on the indication, or upon receiving such an indication:
  • the RLC bearer is a PC5 RLC bearer for a PC5 interface
  • the RLC entity is a PC5 RLC entity for the PC5 interface
  • a corresponding logical channel is established, preferably, the logical channel is a logical channel used for sidelink communication or PC5 interface.
  • the established RLC bearer is either an RLC entity or a logical channel, which will be used to carry SRB0 messages, or to carry messages transmitted using a logical channel (such as CCCH) of a dedicated logical channel category, or to be used for relay SRB0 transmission (for SRB0 via relay) in the same way.
  • a logical channel such as CCCH
  • the RLC bearer/RLC entity and logical channel established here may belong to a specific (specific) sidelink SRB or sidelink DRB, or be associated with a specific (specific) sidelink SRB or sidelink DRB.
  • such a specific sidelink SRB/DRB is a default sidelink SRB/DRB for carrying SRB0 messages, or for carrying messages transmitted using a logical channel (such as CCCH) of a dedicated logical channel category, or using For SRB0 transmission in relay mode (for SRB0 via relay).
  • a logical channel such as CCCH
  • the RLC bearer/RLC entity and logical channel established above may adopt a default configuration (default configuration).
  • the default configuration may be used to configure RLC bearers/RLC entities and logical channels for bearer/transmission of SRBO messages.
  • the default configuration can also be that this configuration is used to carry/transmit SRB0 messages, or this configuration is used for SRB0 transmission on PC5/Sidelink; or this configuration is used for SRB0 to transmit via relay (for SRB0 via relay) .
  • 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
  • the value (value) of the mode of the RLC entity is transparent mode (Transparent Mode, TM); the value (value) of the logical channel priority 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 Relay UE establishes a specific (specific) sidelink SRB or sidelink DRB based on the indication, or when receiving such an indication.
  • the specific (specific) sidelink SRB or sidelink DRB will be used to bear the SRB0 message, or bear the message transmitted by using a logical channel (such as CCCH) of a dedicated logical channel category.
  • the RLC bearer is a PC5 RLC bearer for a PC5 interface
  • the RLC entity is a PC5 RLC entity for the PC5 interface
  • a corresponding logical channel is established, preferably, the logical channel is a logical channel used for sidelink communication or PC5 interface.
  • the Relay UE Based on the indication, or when receiving such indication, the Relay UE applies (apply) a default configuration (default configuration).
  • the configuration is used to carry/transmit SRB0 messages, or the configuration is used for SRB0 transmission on PC5/Sidelink; or the configuration is used for SRB0 to transmit via relay (for SRB0 via relay).
  • the RLC bearer is a PC5 RLC bearer for a PC5 interface
  • the RLC entity is a PC5 RLC entity for the PC5 interface
  • a corresponding logical channel is established, preferably, the logical channel is a logical channel used for sidelink communication or PC5 interface.
  • the relay UE receives the PC5 RRC message sent by the remote UE, and the message carries a relay service request or a relay service-related request, or information about the relay,
  • the relay UE performs the operation in Embodiment 1 based on the received message, or when receiving the message, which may specifically include all the implementation manners in Embodiment 1.
  • Embodiment 2 can be implemented independently to achieve the purpose of establishing a PC5 RLC entity on the relay side.
  • the relay UE can also establish a Uu RLC entity while establishing the PC5 RLC entity/bearer, and associate the Uu RLC entity with the established PC5 RLC entity (association) .
  • association the mapping relationship between the Uu RLC entity and the PC5 RLC entity can be established or saved in an adaptation layer (adapt) of the relay UE.
  • This Uu RLC entity will be used to transmit the SRB0 message sent from the remote UE to the base station between the relay UE and the base station.
  • this Uu RLC entity can be associated with a dedicated destination address (destination), so that there is a one-to-one correspondence between the PC5 RLC entity and the Uu RLC entity.
  • the relay UE can also associate the established PC5 RLC entity with an already established, public Uu RLC entity. That is, the common Uu RLC entity can serve multiple remote UEs, and is used for transmission of SRB0 messages of at least one remote UE.
  • Embodiment 1 can also be performed on the remote UE side.
  • the specific execution method can be:
  • Embodiment 1 When the remote UE starts the RRC connection establishment process, the RRC connection recovery process, or the RRC connection re-establishment process, the operations described in Embodiment 1 are performed, which may specifically include all the implementation manners in Embodiment 1.
  • the remote UE when the remote UE starts the RRC connection establishment process, perform the operation of establishing an RLC entity/bearer/logical channel; or when the remote UE starts the RRC connection establishment process, establish a specific (specific) sidelink SRB or sidelink DRB; It may also be that when the remote UE starts the RRC connection establishment process, it applies (apply) the default configuration for the bearing/transmission of the SRB0 message.
  • the UE when the UE confirms the RRC connection with the network/base station through the relay UE, perform the above operation. Otherwise, if the UE directly establishes an RRC connection with the base station through the Uu interface, the above operations do not need to be performed.
  • the specific execution method can also be:
  • the information in the indication may include information about using an established PC5 RRC connection for relay or relay service,
  • the indication information indicates that a PC5 RRC connection is established for a dedicated destination address (destination), and that the connection is used for relay or relay service.
  • the remote UE executes the operations in Embodiment 1 based on the indication, or upon receiving such an indication, which may specifically include all the implementation manners in Embodiment 1.
  • the UE can re-establish the PC5 RLC bearer; if the PC5 RLC entity has been established, then the UE can re-establish the PC5 RLC entity.
  • the establishment of an RLC entity may include at least:
  • Re-establishment of RLC entities may include at least:
  • the upper layer mentioned in the foregoing embodiments may refer to the V2X layer, that is, the non-access layer/management layer responsible for UE's PC5 interface communication or sidelink communication, or the management control layer above the PC5 RRC.
  • Such an upper layer may also specifically be a V2X application server (V2X application server), and such a server provides instruction information to a lower layer of the UE.
  • V2X application server V2X application server
  • Such an upper layer may also be a specific application layer, such as a V2X application layer, or a relay service application layer.
  • Fig. 6 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • the user equipment UE600 includes a processor 601 and a memory 602 .
  • the processor 601 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 602 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 602 has program instructions stored thereon. When the instructions are executed by the processor 601, 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接收来自上层的指示，该指示中的信息包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，或者是，该指示中的信息指示为一个专有的目标地址建立了PC5 RRC连接以及该连接用于中继或者中继服务；中继UE基于该指示，或者是在接收到该指示时，执行建立PC5 RLC承载、建立PC5 RLC实体、或者建立相应的逻辑信道的操作，其中，所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道进行传输的消息。

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连接的管理。
如图1所示，UE可以通过Uu接口与基站(gNB)直接建立RRC连接。UE通过SRB0向基站发送RRC连接建立请求消息。其中，SRB0是用于承载采用逻辑信道类别为CCCH的逻辑信道进行传输的RRC消息(SRB0 is for RRC messages using the CCCH logical channel)。在SRB0上传输的RRC消息可以简称为SRB0消息(SRB0 message)。
如图2所示，UE还可以通过中继UE(relay UE)与基站(gNB)建立RRC连接。这样的UE可以被称为远端UE(remote UE)。Remote UE和relay UE之间通过侧行链路(sidelink)通信，侧行链路链路的通信接口为PC5接口。Relay UE和基站之间仍然采用Uu口进行通信。
远端UE为了和基站建立RRC连接，同样需要发送SRB0消息。由于远端UE是通过relay UE和基站间接建立连接，在协议架构中，与这个SRB0关联的RLC实体是PC5 RLC实体。
在sidelink通信中，当发送UE侧被配置了RLC实体，那么只有在接收UE侧也采用相同的配置信息来配置对等的RLC实体(peer entity)，才能实现信息的接收。本发明讨论为了传输SRB0消息，remote UE和relay UE在RRC连接管理流程中RLC实体的建立和管理。
发明内容
为了解决上述问题，本发明提供一种由用户设备执行的方法以及用户设备。
根据本发明的一个方面，提供了一种由用户设备执行的方法，是远端UE和中继UE在RRC连接管理过程中建立和管理RLC承载/实体/信道的方法，包括如下步骤：
中继UE接收来自上层的指示，该指示中的信息包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，或者是，该指示中的信息指示为一个专有的目标地址建立了PC5 RRC连接以及该连接用于中继或者中继服务；
中继UE基于该指示，或者是在接收到该指示时，执行下述操作：
建立PC5 RLC承载；
建立PC5 RLC实体；或者，
建立相应的逻辑信道，
其中，所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道进行传输的消息。
在上述的由用户设备执行的方法中，优选地，
所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道属于一个特定的sidelink SRB或者sidelink DRB，或者是与一个特定的sidelink SRB或者 sidelink DRB相关联。
在上述的由用户设备执行的方法中，优选地，
上述特定的sidelink SRB或者sidelink DRB是一个默认的sidelink SRB或者sidelink DRB，用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道进行传输的消息。
在上述的由用户设备执行的方法中，优选地，
所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道采用默认的配置，用来配置用于SRB0消息的承载/传输的PC5 RLC承载、PC5 RLC实体或者逻辑信道。
在上述的由用户设备执行的方法中，优选地，还包括如下步骤：
中继UE接收来自远端UE发送的PC5 RRC消息，在该消息中携带了中继服务的请求或者是中继的相关信息；
中继UE基于该消息，或者是在接收到该消息时，执行上述操作。
在上述的由用户设备执行的方法中，优选地，还包括如下步骤：
中继UE还建立一个Uu RLC实体，并且将该Uu RLC实体与所建立的PC5 RLC实体二者关联起来，
其中，该Uu RLC实体用于传输来自远端UE的SRB0消息。
在上述的由用户设备执行的方法中，优选地，还包括如下步骤：
远端UE接收来自上层的指示，该指示中的信息包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，或者是，该指示中的信息指示为一个专有的目标地址建立了PC5 RRC连接以及该连接用于中继或者中继服务；
远端UE基于该指示，或者是在接收到该指示时，执行上述操作。
在上述的由用户设备执行的方法中，优选地，
如果PC5 RLC承载已经建立，那么重新建立该PC5 RLC承载；
如果PC5 RLC实体已经建立，那么重新建立该PC5 RLC实体。
根据本发明的另一个方面，提供了一种用户设备，包括：
处理器；以及
存储器，上述存储器上存储有指令，
上述指令在由上述处理器运行时，使上述用户设备执行根据上文所描述的方法。
根据本发明所涉及的由用户设备执行的方法以及相应的用户设备，能够在RRC连接管理流程中可靠地建立和管理RLC实体。
附图说明
图1是表示UE通过Uu接口与基站直接建立RRC连接的示意图。
图2是表示UE通过中继UE与基站建立RRC连接的示意图。
图3是表示UE-to-Network中继的示意图。
图4是表示UE-to-Network L2架构控制面协议栈的示意图。
图5是表示由用户设备UE执行的方法的流程图。
图6是本发明涉及的用户设备UE的简要结构框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
下面描述本发明涉及的部分术语，术语的具体含义见3GPP最新标准规范。
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，新无线电
UMTS：Universal Mobile Telecommunications System通用移动通信系统
E-UTRAN：Evolved UMTS Terrestrial Radio Access Network，演进的UMTS陆地无线接入网
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车联网
Enb：evolved node base station演进的节点基站
Gnb：New generation node base station新一代节点基站
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中继如图3所示，场景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和基站的控制面协议栈如图4所示。
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连接建立、重建、恢复等流程时，为了能够正确接收和处理数据需要在在PC5接口上的发送UE(远端UE)和接收UE(relay UE)之间及时建立和管理对应的PC5 RLC实体。
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)。
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连接管理过程中建立和管理RLC承载(bearer)/RLC实体(entity)/RLC信道(channel)的方法。如图5所示，该方法包括如下步骤。
步骤S501：Relay UE接收来自上层(upper layer)的指示，指示中的信息可以包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，
或者是
指示信息指示为一个专有的目标地址(destination)建立了PC5 RRC连接，以及该连接用于中继或者中继服务。
步骤S502：Relay UE基于该指示，或者是接收到这样的指示时，执行下述操作之一或多：
建立RLC承载，优选的，该RLC承载是用于PC5接口的PC5 RLC承载；
建立RLC实体，优选的，该RLC实体是用于PC5接口的PC5 RLC实体；
建立相应的逻辑信道，优选的，该逻辑信道是用于sidelink通信或者PC5接口的逻辑信道。
其中，建立的RLC承载或者是RLC实体，以及逻辑信道，将用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道(例如CCCH)进行传输的消息，或者说是用于以relay方式的进行的SRB0传输(for SRB0 via relay)。
可选的，这里建立的RLC承载/RLC实体，以及逻辑信道可以属于一个特定的(specific)sidelink SRB或者sidelink DRB，或者是与一个特定的(specific)sidelink SRB或者sidelink DRB相关联。
优选的，这样特定的sidelink SRB/DRB是一个默认的sidelink SRB/DRB，用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道(例如 CCCH)进行传输的消息，或者说是用于以relay方式的进行的SRB0传输(for SRB0 via relay)。
优选的，前面所述建立的RLC承载/RLC实体，以及逻辑信道可以采用默认的配置(default configuration)。该默认配置可以是用来配置用于SRB0消息的承载/传输的RLC承载/RLC实体，以及逻辑信道。该默认配置还可以是该配置用于承载/传输SRB0消息，或者是该配置用于SRB0在PC5/Sidelink上的传输；又或者是该配置用于SRB0通过relay方式进行传输(for SRB0 via relay)。
这样的配置信息中可以至少包含RLC实体的模式(RLC mode)、逻辑信道的优先级、逻辑信道的分组编号等。例如RLC实体的模式的取值(value)为透传模式(Transparent Mode，TM)；逻辑信道优先级取值(value)为1；逻辑信道的分组编号取值为0。基于这样的配置信息，relay UE可以建立采用了这样的配置信息的RLC实体/承载以及逻辑信道。
上述方案的又一实施方式可以是：
Relay UE基于该指示，或者是接收到这样的指示时，建立一个特定的(specific)sidelink SRB或者sidelink DRB。该特定的(specific)sidelink SRB或者sidelink DRB将用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道(例如CCCH)进行传输的消息。
在建立该特定的(specific)sidelink SRB或者sidelink DRB的过程中，可以包括了下述操作之一或多：
建立RLC承载，优选的，该RLC承载是用于PC5接口的PC5 RLC承载；
建立RLC实体，优选的，该RLC实体是用于PC5接口的PC5 RLC实体；
建立相应的逻辑信道，优选的，该逻辑信道是用于sidelink通信或者PC5接口的逻辑信道。
上述方案的又一实施方式还可以是：
Relay UE基于该指示，或者是接收到这样的指示时，应用(apply)一种默认的配置(default configuration)。
优选的，该配置用于承载/传输SRB0消息，或者是该配置用于SRB0在PC5/Sidelink上的传输；又或者是该配置用于SRB0通过relay方式进行传输(for SRB0 via relay)。
在应用该配置的过程中，可以包括了下述操作之一或多：
建立RLC承载，优选的，该RLC承载是用于PC5接口的PC5 RLC承载；
建立RLC实体，优选的，该RLC实体是用于PC5接口的PC5 RLC实体；
建立相应的逻辑信道，优选的，该逻辑信道是用于sidelink通信或者PC5接口的逻辑信道。
实施例2
和实施例1的区别在于，
relay UE接收到来自remote UE发送的PC5 RRC消息，并在该消息中携带了relay服务请求或者relay业务相关的请求，或者是relay的相关信息，
那么relay UE基于接收到的消息，或者是在接收到所述消息时执行实施例1中的所述操作，具体可以包括实施例1中所有的实施方式。
实施例2可以单独实施，来实现在relay侧建立PC5 RLC实体的目的。
实施例3
在实施例1或者2的基础上，relay UE还可以在建立PC5 RLC实体/承载的同时，建立一个Uu RLC实体，并且将该Uu RLC实体与所建的PC5 RLC实体二者关联起来(association)。优选的，可以在relay UE的自适应层(adapt)建立或者保存Uu RLC实体与PC5 RLC实体的映射关系。
这个Uu RLC实体将用于在relay UE和基站之间传输来自remote UE发送给基站的SRB0消息。
可选的，这个Uu RLC实体可以与专有的目标地址(destination)相关联，从而使得PC5 RLC实体与Uu RLC实体一一对应。
除此之外，relay UE还可以将所建的PC5 RLC实体与一个已经建立的、公共的Uu RLC实体相关联。即该公共的Uu RLC实体可以服务于多个remote UE，用于至少一个remote UE的SRB0消息的传输。
实施例4
实施例1中的操作还可以在remote UE侧执行。
具体的执行方式可以是：
当remote UE启动RRC连接建立过程或者是RRC连接恢复过程，又或者是RRC连接重新建立过程时，执行实施例1中的所述操作，具体可以包括实施例1中所有的实施方式。
例如，在remote UE启动RRC连接建立过程时，执行建立RLC实体/承载/逻辑信道的操作；又或者是在remote UE启动RRC连接建立过程时，建立一个特定的(specific)sidelink SRB或者sidelink DRB；还可以是remote UE启动RRC连接建立过程时，应用(apply)用于SRB0消息的承载/传输的默认配置。
可选的，当UE确认通过relay UE与网络/基站进行RRC连接时，执行上述操作。否则，如果UE直接通过Uu口和基站建立RRC连接，则不需要执行上述操作。
具体的执行方式还可以是：
当remote UE接收来自上层(upper layer)的指示，指示中的信息可以包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，
或者是
指示信息指示为一个专有的目标地址(destination)建立了PC5 RRC连接，以及该连接用于中继或者中继服务。
remote UE基于该指示，或者是接收到这样的指示时，执行实施例1中的所述操作，具体可以包括实施例1中所有的实施方式。
实施例5
在前述实施例的操作中，如果PC5 RLC承载已经建立，那么UE可以重新建立该PC5 RLC承载；如果PC5 RLC实体已经建立，那么UE可以重新建立该PC5 RLC实体。
RLC实体的建立至少可以包括：
-建立一个RLC实体；
-设置该RLC实体的状态变量为初始值。
RLC实体的重新建立至少可以包括：
-丢弃所有的RLC SDU，RLC SDU的分段(RLC SDU segment)，RLC PDU；
-停止并且重置所有的定时器；
-重置该RLC实体的状态变量为初始值。
实施例6
在前述实施例中提到的upper layer可以是指V2X层，即负责UE的进行PC5接口通信或者是sidelink通信的非接入层/管理层，还可以是在PC5 RRC之上的管理控制层。
这样的upper layer还可以具体是V2X应用服务器(V2X application server)，由这样的服务器向UE的下层提供指示信息。
这样的upper layer还可以是特定的应用层(application layer)，例如V2X应用层，或者是中继业务应用层等。
图6是本发明涉及的用户设备UE的简要结构框图。如图6所示，该用户设备UE600包括处理器601和存储器602。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器602上存储有程序指令。该指令在由处理器601运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备 中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的方法，是远端UE和中继UE在RRC连接管理过程中建立和管理RLC承载/实体/信道的方法，包括如下步骤：
    中继UE接收来自上层的指示，该指示中的信息包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，或者是，该指示中的信息指示为一个专有的目标地址建立了PC5 RRC连接以及该连接用于中继或者中继服务；
    中继UE基于该指示，或者是在接收到该指示时，执行下述操作：
    建立PC5 RLC承载；
    建立PC5 RLC实体；或者，
    建立相应的逻辑信道，
    其中，所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道进行传输的消息。
  2. 根据权利要求1所述的由用户设备执行的方法，其中，
    所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道属于一个特定的sidelink SRB或者sidelink DRB，或者是与一个特定的sidelink SRB或者sidelink DRB相关联。
  3. 根据权利要求2所述的由用户设备执行的方法，其中，
    上述特定的sidelink SRB或者sidelink DRB是一个默认的sidelink SRB或者sidelink DRB，用于承载SRB0消息，或者是承载采用专有逻辑信道类别的逻辑信道进行传输的消息。
  4. 根据权利要求1所述的由用户设备执行的方法，其中，
    所建立的PC5 RLC承载、PC5 RLC实体或者逻辑信道采用默认的配置，用来配置用于SRB0消息的承载/传输的PC5 RLC承载、PC5 RLC实体或者逻辑信道。
  5. 根据权利要求1-4中任一项所述的由用户设备执行的方法，其中，还包括如下步骤：
    中继UE接收来自远端UE发送的PC5 RRC消息，在该消息中携带了中继服务的请求或者是中继的相关信息；
    中继UE基于该消息，或者是在接收到该消息时，执行上述操作。
  6. 根据权利要求1-4中任一项所述的由用户设备执行的方法，其中，还包括如下步骤：
    中继UE还建立一个Uu RLC实体，并且将该Uu RLC实体与所建立的PC5 RLC实体二者关联起来，
    其中，该Uu RLC实体用于传输来自远端UE的SRB0消息。
  7. 根据权利要求5所述的由用户设备执行的方法，其中，还包括如下步骤：
    中继UE还建立一个Uu RLC实体，并且将该Uu RLC实体与所建立的PC5 RLC实体二者关联起来，
    其中，该Uu RLC实体用于传输来自远端UE的SRB0消息。
  8. 根据权利要求1-4中任一项所述的由用户设备执行的方法，其中，还包括如下步骤：
    远端UE接收来自上层的指示，该指示中的信息包含将一个已经建立的PC5 RRC连接用于中继或者中继服务的信息，或者是，该指示中的信息指示为一个专有的目标地址建立了PC5 RRC连接以及该连接用于中继或者中继服务；
    远端UE基于该指示，或者是在接收到该指示时，执行上述操作。
  9. 根据权利要求1-4中任一项所述的由用户设备执行的方法，其中，
    如果PC5 RLC承载已经建立，那么重新建立该PC5 RLC承载；
    如果PC5 RLC实体已经建立，那么重新建立该PC5 RLC实体。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，上述存储器上存储有指令，
    上述指令在由上述处理器运行时，使上述用户设备执行根据权利要求1-9中任一项所述的方法。
PCT/CN2022/104121 2021-07-09 2022-07-06 由用户设备执行的方法及用户设备 WO2023280205A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/574,121 US20240244679A1 (en) 2021-07-09 2022-07-06 Method performed by user equipment, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110781784.6A CN115604675A (zh) 2021-07-09 2021-07-09 由用户设备执行的方法及用户设备
CN202110781784.6 2021-07-09

Publications (1)

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

Family

ID=84801286

Family Applications (1)

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

Country Status (3)

Country Link
US (1) US20240244679A1 (zh)
CN (1) CN115604675A (zh)
WO (1) WO2023280205A1 (zh)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307472A (zh) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307472A (zh) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on the CP procedures for L2 Relay", 3GPP DRAFT; R2-2104131, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210412 - 20210420, 2 April 2021 (2021-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052175394 *
MEDIATEK INC.: "Connection establishment for L2 UE-to-Network Relay", 3GPP DRAFT; R2-2102779, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210412 - 20210420, 2 April 2021 (2021-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052174369 *
ZTE: "Summary document of AI 8.7.4.1", 3GPP DRAFT; R2-2104503, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210412 - 20210420, 12 April 2021 (2021-04-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051995185 *

Also Published As

Publication number Publication date
CN115604675A (zh) 2023-01-13
US20240244679A1 (en) 2024-07-18

Similar Documents

Publication Publication Date Title
US20230180349A1 (en) Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device
EP3105957B1 (en) Method and apparatus for indicating qos of d2d data in wireless communication system
JP2021505023A (ja) 多重接続のための方法およびその装置
US9603186B2 (en) Mobility management entity, user equipment and methods for machine type communication
KR20200029617A (ko) 무선 단말, 무선국, 및 이들의 방법
KR20200019789A (ko) 무선 단말, 무선국, 코어 네트워크 노드, 및 그것들에서의 방법
WO2023134679A1 (zh) 由用户设备执行的方法及用户设备
WO2022083444A1 (zh) 系统信息获取方法及用户设备
TWI783715B (zh) 5gsm擁塞定時器的處理
US20230388863A1 (en) Communication method and apparatus
WO2023274225A1 (zh) 由用户设备执行的方法以及用户设备
WO2023093818A1 (zh) 由用户设备执行的方法及用户设备
WO2020091047A1 (ja) 端末装置、基地局装置、および方法
WO2023280205A1 (zh) 由用户设备执行的方法及用户设备
WO2023280203A1 (zh) 由用户设备执行的方法及用户设备
WO2023098865A1 (zh) 由用户设备执行的方法及用户设备
JP2023126994A (ja) 端末装置、基地局装置、方法、および、集積回路
JP2023130533A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2024001948A1 (zh) 由用户设备执行的方法及用户设备
WO2023213267A1 (zh) 由用户设备执行的方法及用户设备
WO2023213285A1 (zh) 由用户设备执行的方法及用户设备
WO2024051681A1 (zh) 由用户设备执行的方法及用户设备
WO2019031217A1 (ja) 端末装置、基地局装置、及び、これらの装置により実行される方法
WO2024067464A1 (zh) 由用户设备执行的方法及用户设备
WO2023001191A1 (zh) 由用户设备执行的方法及用户设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18574121

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

Country of ref document: EP

Kind code of ref document: A1