WO2023213285A1 - 由用户设备执行的方法及用户设备 - Google Patents
由用户设备执行的方法及用户设备 Download PDFInfo
- Publication number
- WO2023213285A1 WO2023213285A1 PCT/CN2023/092183 CN2023092183W WO2023213285A1 WO 2023213285 A1 WO2023213285 A1 WO 2023213285A1 CN 2023092183 W CN2023092183 W CN 2023092183W WO 2023213285 A1 WO2023213285 A1 WO 2023213285A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- configuration
- rlc
- source
- remote
- relay
- Prior art date
- Legal status (The legal status 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 status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- 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
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- 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
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
Definitions
- the present invention relates to the field of wireless communication technology, and more specifically, the present invention relates to a method for user equipment to perform parameter configuration in a sideline communication relay architecture and the corresponding user equipment.
- NR sidelink relaying sidelink communication relay
- RP-210904 New Study Item on NR Sidelink Relaying The latest version of this work item can be found in the non-patent document: RP-212601 reivised WID NR sidelink relay.
- One of the goals of this work item is to standardize sideline communication control plane processes, such as management of RRC connections, reception of system messages and reception of paging.
- the goal of this work item is also to standardize the selection and reselection process for sideline communication relay UEs.
- This invention discusses the configuration process of relevant parameters required by the source-side UE and the target-side UE for data and signaling transmission through the relay UE.
- the method performed by the user equipment UE includes: establishing a PC5-RRC connection between the first user equipment UE1 and the second user equipment UE2, or between the UE1 and the third user equipment UE3.
- the PC5 radio resource control PC5-RRC connection between Configuration of the link control SL-RLC; initiating the configuration of the wireless link control SL-RLC for the first side-link communication; initiating the configuration of the second side-link communication Radio link control SL-RLC configuration; and initiating the configuration of the remote UE local ID, where if the UE1 is the source UE, the UE2 is the relay UE, and the UE3 is the target side UE; if the UE1 is a target side UE, then the UE2 is a relay UE, and the UE3 is a source side UE; if the UE1 is a relay UE, then the UE2 is a source side UE, and the UE3 For the target side UE, the
- the side-link communication radio link control is used to carry SL-SRB3 between the source side UE and the target side UE, and the SL-SRB3 is used to carry PC5 Radio Resource Control PC5-RRC message.
- the SL-RLC configures wireless link control RLC configuration and/or multimedia access control MAC configuration information, wherein the RLC configuration includes a logical channel identifier and a sequence number length,
- the MAC configuration information includes priorities and logical channel groups.
- the configuration of the SL-RLC is specified by the protocol; or is default; or is configured by the UE1, the UE2, or the UE3.
- the logical channel identifier is a fixed value specified by the protocol, and the logical channel group is a fixed value specified by the protocol. Value; if the SL-RLC is default, the logical channel identifier is a default value, and the logical channel group is a default value.
- the SL-RLC configuration specified by the protocol is used for at least one of the following messages; if the SL-RLC configuration is By default, the default SL-RLC configuration is used for at least one of the following messages: the first side-link communication RRC reconfiguration RRCReconfigurationSidelink message; the first since the PC5-RRC connection is established. A side-link communication RRC reconfiguration RRCReconfigurationSidelink message; and a PC-RRC message before the first side-link communication RRC reconfiguration RRCReconfigurationSidelink message since the PC5-RRC connection was established.
- the method performed by user equipment UE includes: the first user equipment UE1 configures the remote UE local identity remote UE local ID for the second user equipment UE2 and the third user equipment UE3; and the UE1 Receive the configuration completion message sent by the UE2, where if the UE1 is the source UE, the UE2 is the relay UE, and the UE3 is the destination UE.
- the UE1 sends a configuration message to the UE2 and the UE3 respectively to configure the remote UE local identifier remote UE local ID
- the configuration message carries at least the following information: One: the remote UE local ID of the source side UE and/or the remote UE local ID information of the target side UE; the source layer two identification Source L2 ID of the source side UE; the source layer of the target side UE The second identifier Source L2 ID; and the source layer two identifier Source L2 ID of the relay UE.
- the UE1 when at least one of the following conditions is met, the UE1 considers the remote UE local ID configuration and/or the remote UE local ID configuration of the source side UE in the corresponding configuration message.
- the remote UE local ID configuration of the target side UE needs to be applied, and the at least one condition is: the side-link communication RRC reconfiguration failure RRCReconfigurationFailureSidelink message sent by the UE3 has not been received; and the side-link communication RRC sent by the UE3 has been received Reconfiguration completes the RRCReconfigurationCompleteSidelink message, or when at least one of the following conditions is met, the UE1 continues to use the remote UE local ID of the source side UE and/or the remote UE local ID of the target side UE before the corresponding configuration message.
- the at least one condition is: the side-link communication RRC reconfiguration failure RRCReconfigurationFailureSidelink message sent by the UE3 has been received; the side-link communication RRC reconfiguration complete RRCReconfigurationCompleteSidelink message sent by the UE3 has not been received; and corresponding to The timer of the UE3 for monitoring whether it responds to the sidelink communication RRC reconfiguration RRCReconfigurationSidelink message is running.
- a user equipment includes: a processor; and a memory storing instructions; wherein the instructions execute the steps according to the first aspect and the second aspect when executed by the processor. Any of the methods described.
- the parameters required for L2U2U data and signaling transmission can be correctly configured for the relay UE and the remote UE, thereby realizing normal transmission of data and signaling.
- Figure 1 is a schematic diagram showing UE-to-UE relay.
- FIG. 2 is a schematic diagram illustrating the control plane protocol stacks of a source-side UE, a relay UE, and a target-side UE of a U2N sidelink communication layer two (L2) relay architecture.
- L2N sidelink communication layer two
- FIG. 3 is a flowchart showing the basic process of the method performed by the user equipment UE in Embodiment 1 of the present invention.
- FIG. 4 is a flowchart showing the basic process of the method performed by the user equipment UE in Embodiment 2 of the present invention.
- Figure 5 is a schematic 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 layer
- SCI Sidelink Control Information, side 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 wireless access network
- DCI Downlink Control Information, downlink control information
- ADAPT Adaptation layer, side communication adaptation layer
- PHY physical layer, physical layer
- RB radio bearer, wireless bearer
- DRB Data Radio Bearer, data wireless bearer
- SRB Signalling Radio Bearer, signaling wireless bearer
- ProSe Proximity based Services: Proximity services
- V2X Vehicle-to-Everything, vehicles to everything
- NAS Non-Access-Stratum, non-access layer
- PC5-S PC5 signaling, PC5 signaling
- SRAP Sidelink Relay Adaptation Protocol, sidelink communication relay adaptation protocol
- SL-SRB Sidelink Signalling Radio Bearer, sidelink communication signaling wireless bearer
- U2U UE-to-UE, UE to UE
- RSRP Reference Signal Received Power reference signal received power
- SL-RSRP sidelink RSRP, sidelink communication reference signal received power
- SD-RSRP sidelink discovery RSRP, sidelink communication discovery message reference signal received power
- 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 evolved 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 Sidelink-supporting device described in the background art.
- NR equipment with relay function can also refer to NR equipment that supports NR sidelink relay architecture, or other types of NR equipment or LTE equipment.
- the source-side UE and the target-side UE may refer to two UEs connected to each other through Relay UE in the UE-to-UE relay architecture. One of them is the source-side UE, and the other is the target-side UE.
- the source UE (source UE) may also be called an initiation UE (initiation UE), and the target UE (target UE) may also be called a destination UE (destination UE).
- Relay UE For U2U scenarios, "Relay UE”, “U2U Relay UE” and “L2 U2U Relay UE” can be used interchangeably.
- “Remote UE”, “U2U Remote UE” and “L2 U2U Remote UE” can be used interchangeably.
- “source UE”, “source remote UE”, “U2U source UE”, “U2U source remote UE”, “L2 U2U source UE” and “L2 U2U source remote UE” can be used interchangeably.
- target UE “target remote UE”, “U2U target UE”, “U2U target remote UE”, “L2 U2U target remote UE”, and “L2 U2U target remote UE” can be used interchangeably.
- sidelink, SL and PC5 can be used interchangeably.
- “Feedback”, “report”, “escalate”, “send”, and “notify” can be used interchangeably.
- “Use”, “enable”, “adopt”, “apply”, “enable”, “activate”, “implement”, etc. may be used interchangeably.
- upper layer may refer to ProSe layer, or V2X layer, or NAS layer, or PC5-S protocol layer.
- ProSe layer, V2X layer, NAS layer and PC5-S protocol layer can be used interchangeably.
- RLC channel, RLC entity and RLC bearer can be used interchangeably.
- these names can be preceded by the qualification "Relay” and/or "PC5 Relay”.
- SL-RLC refers to the PC5 RLC bearer or PC5 RLC channel used to carry data and signaling transmission between the source side UE and the target side UE.
- SL-RLC can be between the source side UE and the Relay UE and/or in the Relay UE and the target side UE.
- the PC5 interface is the interface for control plane and user plane Sidelink communication between UE and UE.
- Sidelink unicast the PC5-RRC connection is between a source layer 2 ID and a destination layer 2 ID. AS layer logical connection.
- a PC5 unicast link is established, a PC5-RRC connection will be established.
- SL-SRB is used to carry PC5-S messages and PC5-RRC messages.
- SL-SRB0 is used to carry PC5-S messages before PC5-S security is established
- SL-SRB1 is used to carry PC5-S messages of the PC5-S security establishment process
- SL-SRB2 is used to carry PC5-S messages after PC5-S security is established.
- PC5-S message SL-SRB3 is used to carry PC5-RRC message.
- the UE-to-UE relay is shown in Figure 1.
- the left and right sides are remote UEs and the middle is the relay UE.
- the remote UE and the relay UE are connected through the PC5 interface respectively. Because the distance between the two remote UEs is long or the communication environment is poor, the relay UE needs to relay and forward the signaling and data between them.
- UE-to-UE relay scenarios include:
- both remote UEs i.e., source side UE and target side UE
- the relay UE are within the coverage area;
- both remote UEs i.e., source side UE and target side UE
- relay UE are outside coverage
- Partial coverage Among the two remote UEs and the relay UE, at least one UE is within the coverage range, and at least one UE is outside the coverage range.
- two Remote UEs i.e., source side UE and target side UE
- PC5-RRC connections with Relay UE respectively.
- a PC5-RRC connection will also be established.
- Two Remote UEs i.e., source side UE and target side UE
- the control plane protocol stacks of the source side UE, Relay UE and target side UE are shown in Figure 2.
- PC5 RLC channel refers to the RLC channel used for PC5 interface communication.
- the PC5 relay RLC channel between the source side UE and the relay UE when the source side UE is connected to the target side UE through Relay UE, the PC5 relay RLC channel between the source side UE and the relay UE, and the PC5 relay RLC channel between the relay UE and the target side UE It can be used to carry data and signaling between the source side UE and the target side UE, that is, it can be used to carry SL-SRB and SL-DRB between the source side UE and the target side UE.
- PC5-SRAP entity refers to the SRAP entity used for PC5 interface communication.
- PC5-SRAP is the adaptation layer used for L2 U2U architecture.
- the source UE communicates with the target UE through Relay UE.
- the PC5-SRAP of the source side UE determines the uplink data/signaling according to the mapping relationship between the configured end-to-end bearer (that is, the bearer between the source side UE and the target side UE) to the PC5 relay RLC channel.
- PC5-SRAP (Data sent from the source side UE to the target side UE) corresponding PC5 relay RLC channel, and determine the PC5 relay RLC channel corresponding to the downlink data from the target side UE and forwarded by the Relay UE.
- PC5-SRAP entities corresponding to the source side UE and the target side UE respectively in the Relay UE.
- PC5-SRAP also exists in the target side UE, and its function is the same as PC5-SRAP in the source side UE.
- entity and layer can be used interchangeably, such as SRAP entity or SRAP layer.
- This invention discusses the configuration process of relevant parameters required by the source-side UE and the target-side UE to transmit data and signaling through the relay UE in the L2 U2U scenario.
- the parameters required for L2 U2U data and signaling transmission can be correctly configured, thereby realizing normal transmission of data and signaling.
- step S101 the PC5-RRC connection between the source side UE (UE1) and the Relay UE (can be set to UE2) is established. or when the PC5-RRC connection between the source side UE (UE1) and the target side UE (can be set to UE3) is established (that is, the determination is "yes"), the first operation is performed.
- the first operation includes at least one of the following operations:
- remote UE local ID remote UE local identification
- step S101 for the target side UE (can be set to UE1), as shown in Figure 3, in step S101, a PC5-RRC connection is established between the target side UE (UE1) and the Relay UE (can be set to UE2) or when the PC5-RRC connection between the target side UE (UE1) and the source side UE (can be set to UE3) is established (that is, the determination is "yes"), the first operation is performed.
- step S101 for the Relay UE (can be set to UE1), as shown in Figure 3, in step S101, a PC5-RRC connection is established between the Relay UE (UE1) and the source UE (can be set to UE2) or when the PC5-RRC connection between the Relay UE (UE1) and the target side UE (which can be set to UE3) is established (that is, the determination is "yes"), the first operation is performed.
- the first SL-RLC refers to the SL-RLC between the target side UE and the Relay UE
- the second SL-RLC refers to the SL-RLC between the Relay UE and the source side UE.
- SL-RLC is used to carry SL-SRB3 including but not limited to source-side UE and target-side UE.
- the SL-RLC configuration includes but is not limited to RLC configuration and/or MAC configuration information.
- the RLC configuration includes but is not limited to: logical channel identifier, sequence number length and other information.
- MAC configuration information includes but is not limited to: priority, logical channel group and other information.
- the UE initiates the configuration of the first SL-RLC, and/or the UE initiates the configuration of the second SL-RLC, through the RRCReconfigurationSidelink (sidelink communication RRC reconfiguration) message, or through other PC5-RRC messages.
- the UE carries SL-RLC configuration.
- the configuration of SL-RLC can be specified by the protocol, or default, or configured by the UE (it can be a source-side UE, a target-side UE, or a Relay UE).
- the logical channel identifier can be a fixed value specified by the protocol, and the logical channel group can also be a fixed value specified by the protocol.
- the SL-RLC configuration specified by the protocol may also be used for at least one of the following messages:
- the logical channel identifier can be a default value (that is, it can be reconfigured later), and the logical channel group can also be a default value (that is, it can be reconfigured subsequently).
- the default SL-RLC configuration may also be used for at least one of the following messages:
- the remote UE local ID may include: the remote UE local ID of the source side UE, and/or the remote UE local ID of the target side UE.
- the UE initiates the configuration of the remote UE local ID of the source side UE, and/or the UE initiates the configuration of the remote UE local ID of the target side UE, either through the RRCReconfigurationSidelink (Sidelink Communication RRC Reconfiguration) message, or via other PC5-RRC messages.
- the message carries at least one of the following information: the remote UE local ID of the source side UE and/or the remote UE local ID information of the target side UE, the Source L2 ID and/or destination L2 ID of the source side UE, and the Source of the target side UE. L2 ID and/or destination L2 ID, Source L2 ID and/or destination L2 ID of Relay UE.
- the RRC layer establishes the PC5-RRC connection through instructions from the upper layer. That is, after receiving instructions from the upper layer, the RRC layer will consider that the PC5-RRC connection is established. Therefore "PC5-RRC connection establishment is instructed by the upper layer” and "PC5-RRC connection establishment” can be used interchangeably.
- this embodiment includes steps S201 and S202.
- UE1 is the source side UE, then UE2 is the Relay UE, and UE3 is the target side UE; if UE1 is the target side UE, then UE2 is the Relay UE, and UE3 is the source side UE; if UE1 is the Relay UE, then UE2 is the source side UE , UE3 is the target side UE.
- step S201 UE1 configures remote UE local ID for UE2 and UE3.
- UE1 sends configuration messages (such as the first RRCReconfigurationSidelink message and the second RRCReconfigurationSidelink message) to UE2 and UE3 to configure remote UE local ID, and the message carries at least one of the following information: remote UE local of the source side UE ID and/or the remote UE local ID information of the target side UE, the Source L2 ID of the source side UE, the Source L2 ID of the target side UE, and the Source L2 ID of the Relay UE.
- a timer can be started to monitor whether the peer UE replies with a response message. If the timer expires and the peer UE does not reply with a response, the link is considered abnormal and the PC5-RRC connection with the peer UE is released.
- the first RRCReconfigurationSidelink message is the RRCReconfigurationSidelink message sent by UE1 to UE2, and the second RRCReconfigurationSidelink message is the RRCReconfigurationSidelink message sent by UE1 to UE3.
- step S202 UE1 receives the configuration completion message sent by UE2 (for example RRCReconfigurationCompleteSidelink (sidelink communication RRC reconfiguration complete) message).
- UE2 for example RRCReconfigurationCompleteSidelink (sidelink communication RRC reconfiguration complete) message.
- UE1 considers the remote UE local ID configuration of the source side UE and/or the remote UE local ID configuration of the target side UE in the corresponding (corresponding) RRCReconfigurationSidelink message (i.e., the first RRCReconfigurationSidelink message). Need to be applied:
- UE1 continues to use the remote UE local ID of the source side UE and/or the remote UE local ID of the target side UE before the corresponding (corresponding) RRCReconfigurationSidelink message (i.e., the first RRCReconfigurationSidelink message):
- the remote UE local ID of the source side UE before the RRCReconfigurationSidelink message and /Or the remote UE local ID of the target side UE can be the default value.
- step S202 may also include UE1 receiving the RRCReconfigurationFailureSidelink message sent by UE2. Then UE1 continues to use the remote UE local ID of the source side UE and/or the remote UE local ID of the target side UE before the RRCReconfigurationSidelink message (i.e. the first RRCReconfigurationSidelink message), and at the same time sends a new second RRCReconfigurationSidelink message to UE3, carrying the second RRCReconfigurationSidelink The remote UE local ID of the source side UE and/or the remote UE local ID of the target side UE before the message.
- Step S202 can also be transformed into UE1 receiving the RRCReconfigurationCompleteSidelink message sent by UE3, or receiving the RRCReconfigurationFailureSidelink message from UE3.
- UE1 receiving the RRCReconfigurationCompleteSidelink message sent by UE3, or receiving the RRCReconfigurationFailureSidelink message from UE3.
- UE2 and/or UE3 may send a PC5-RRC message (such as but not limited to: RemoteUELocalIdRequest remote UE local identity request message) to UE1 to request configuration of remote UE local ID.
- PC5-RRC message such as but not limited to: RemoteUELocalIdRequest remote UE local identity request message
- UE1 configures remote UE local ID for UE2 and UE3, and executes step S201.
- the remote UE local ID in this invention is only used as an example.
- Other parameters that require the source side UE, Relay UE and target side UE to be consistent, equal or affect each other are also applicable to the above.
- FIG. 5 is a schematic structural block diagram of the user equipment UE involved in the present invention.
- the user equipment UE700 includes a processor 701 and a memory 702.
- the processor 701 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
- the memory 702 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory.
- Memory 702 stores program instructions. When this instruction is executed by the processor 701, it can execute the above method executed by the user equipment as described in detail in the present invention.
- the program running on the device according to the present invention may be a program that causes the computer to implement 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.
- Programs for realizing the functions of each embodiment of the present invention can be recorded on a computer-readable recording medium.
- Corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute these 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).
- “Computer readable “Recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for short-term dynamic storage of programs, or any other recording medium readable by a computer.
- circuits eg, single-chip or multi-chip integrated circuits.
- Circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
- DSP digital signal processor
- ASIC application-specific integrated circuit
- FPGA field-programmable gate array
- a general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine.
- the above circuit may be a digital circuit or an analog circuit.
- the present invention is not limited to the above-described embodiment. Although various examples of the embodiments have been described, the 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
Description
Claims (10)
- 一种由用户设备UE执行的方法,包括:在第一用户设备UE1与第二用户设备UE2之间的PC5-RRC连接建立、或者所述UE1与第三用户设备UE3之间的PC5无线资源控制PC5-RRC连接建立的情况下,所述UE1执行包括如下操作的至少一种:应用第一侧行通信无线链路控制SL-RLC的配置;应用第二侧行通信无线链路控制SL-RLC的配置;发起对第一侧行通信无线链路控制SL-RLC的配置;发起对第二侧行通信无线链路控制SL-RLC的配置;以及发起对远端UE局部标识remote UE local ID的配置,其中,如果所述UE1为源侧UE,则所述UE2为中继UE,所述UE3为目标侧UE;如果所述UE1为目标侧UE,则所述UE2为中继UE,所述UE3为源侧UE;如果所述UE1为中继UE,则所述UE2为源侧UE,所述UE3为目标侧UE,所述第一SL-RLC是指所述目标侧UE和所述中继UE之间的侧行通信无线链路控制SL-RLC,所述第二SL-RLC是指所述中继UE和所述源侧UE之间的侧行通信无线链路控制SL-RLC。
- 根据权利要求1所述的方法,其特征在于,所述侧行通信无线链路控制用于承载所述源侧UE和所述目标侧UE之间的SL-SRB3,所述SL-SRB3用于承载PC5无线资源控制PC5-RRC消息。
- 根据权利要求2所述的方法,其特征在于,所述SL-RLC配置无线链路控制RLC配置和/或多媒体接入控制MAC配置信息,其中,所述RLC配置中包括逻辑信道标识、序号长度,所述MAC配置信息包括优先级、逻辑信道组。
- 根据权利要求3所述的方法,其特征在于,所述SL-RLC的配置是协议规定的;或者是默认的;或者是由所述UE1或所述UE2或所述UE3配置的。
- 根据权利要求4所述的方法,其特征在于,若所述SL-RLC配置为协议规定的,则所述逻辑信道标识为协议规定的一个固定取值,所述逻辑信道组为协议规定的一个固定取值;若所述SL-RLC为默认的,则所述逻辑信道标识为一个默认取值,所述逻辑信道组为一个默认取值。
- 根据权利要求4所述的方法,其特征在于,若所述SL-RLC配置为协议规定的,则是对于如下消息的至少一种采用协议规定的SL-RLC配置;若所述SL-RLC配置为默认的,则是对于如下消息的至少一种采用默认的SL-RLC配置,所述如下消息为:第一条侧行通信RRC重配置RRCReconfigurationSidelink消息;自从所述PC5-RRC连接建立后的第一条侧行通信RRC重配置RRCReconfigurationSidelink消息;以及自从所述PC5-RRC连接建立后,在第一条侧行通信RRC重配置RRCReconfigurationSidelink消息之前的PC-RRC消息。
- 一种由用户设备UE执行的方法,包括:第一用户设备UE1为第二用户设备UE2和第三用户设备UE3配置远端UE局部标识remote UE local ID;以及所述UE1接收所述UE2发送的配置完成消息,其中,如果所述UE1为源侧UE,则所述UE2为中继UE,所述UE3为目标侧UE;如果所述UE1为目标侧UE,则所述UE2为中继UE,所述UE3为源侧UE;如果所述UE1为中继UE,则所述UE2为源侧UE,所述UE3为目标侧UE。
- 根据权利要求7所述的方法,其特征在于,所述UE1分别发送配置消息给所述UE2和所述UE3,以配置远端UE局部标识remote UE local ID,所述配置消息中携带如下信息的至少一种:所述源侧UE的remote UE local ID和/或所述目标侧UE的remote UE local ID信息;所述源侧UE的源层二标识Source L2 ID;所述目标侧UE的源层二标识Source L2 ID;以及所述中继UE的源层二标识Source L2 ID。
- 根据权利要求8所述的方法,其特征在于,在满足如下至少一条件的情况下,所述UE1认为对应的所述配置消息中的所述源侧UE的remote UE local ID配置和/或所述目标侧UE的remote UE local ID配置需要应用,所述至少一条件为:没有收到所述UE3发送的侧行通信RRC重配置失败RRCReconfigurationFailureSidelink消息;以及已经收到所述UE3发送的侧行通信RRC重配置完成RRCReconfigurationCompleteSidelink消息,或者在满足如下至少一条件的情况下,所述UE1继续使用对应的所述配置消息之前的所述源侧UE的remote UE local ID和/或所述目标侧UE的remote UE local ID,所述至少一条件为:已经收到所述UE3发送的侧行通信RRC重配置失败RRCReconfigurationFailureSidelink消息;没有收到所述UE3发送的侧行通信RRC重配置完成RRCReconfigurationCompleteSidelink消息;以及对应于所述UE3的用于监控是否对侧行通信RRC重配置RRCReconfigurationSidelink消息回复了响应的定时器在运行。
- 一种用户设备,包括:处理器;以及存储器,存储有指令;其中,所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP23799271.4A EP4521824A4 (en) | 2022-05-06 | 2023-05-05 | METHOD PERFORMED BY USER EQUIPMENT, AND USER EQUIPMENT |
| US18/861,933 US20250294626A1 (en) | 2022-05-06 | 2023-05-05 | Method performed by user equipment and user equipment |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210489396.5 | 2022-05-06 | ||
| CN202210489396.5A CN117062108A (zh) | 2022-05-06 | 2022-05-06 | 由用户设备执行的方法及用户设备 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023213285A1 true WO2023213285A1 (zh) | 2023-11-09 |
Family
ID=88646277
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/092183 Ceased WO2023213285A1 (zh) | 2022-05-06 | 2023-05-05 | 由用户设备执行的方法及用户设备 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US20250294626A1 (zh) |
| EP (1) | EP4521824A4 (zh) |
| CN (1) | CN117062108A (zh) |
| WO (1) | WO2023213285A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2025137899A1 (zh) * | 2023-12-26 | 2025-07-03 | 北京小米移动软件有限公司 | 通信方法、终端、通信系统及存储介质 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20260040952A (ko) * | 2024-09-19 | 2026-03-26 | 아서스 테크놀러지 라이센싱 아이엔씨. | 무선 통신 시스템에서 진출 링크 결정을 위한 방법 및 장치 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111901847A (zh) * | 2020-02-13 | 2020-11-06 | 中兴通讯股份有限公司 | sidelink中继通信方法、装置、设备及介质 |
| CN113938982A (zh) * | 2020-06-29 | 2022-01-14 | 华硕电脑股份有限公司 | 无线通信系统中侧链路数据无线电承载建立的方法和设备 |
| US20220095411A1 (en) * | 2020-09-22 | 2022-03-24 | Mediatek Inc. | Methods and Apparatus for Signalling Transmission in L2 UE-to-Network Relay Operation |
| CN114390532A (zh) * | 2020-10-21 | 2022-04-22 | 华硕电脑股份有限公司 | 无线通信系统中用户设备到网络中继的适配层配置的方法和设备 |
| WO2022089318A1 (zh) * | 2020-10-27 | 2022-05-05 | 夏普株式会社 | 发现中继ue的方法、搜索中继ue的方法及用户设备 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4224900A4 (en) * | 2020-10-21 | 2023-11-01 | Huawei Technologies Co., Ltd. | ROUTING METHOD AND APPARATUS |
| EP4221438A4 (en) * | 2020-10-23 | 2023-11-29 | Huawei Technologies Co., Ltd. | COMMUNICATION METHOD AND DEVICE |
-
2022
- 2022-05-06 CN CN202210489396.5A patent/CN117062108A/zh active Pending
-
2023
- 2023-05-05 US US18/861,933 patent/US20250294626A1/en active Pending
- 2023-05-05 EP EP23799271.4A patent/EP4521824A4/en active Pending
- 2023-05-05 WO PCT/CN2023/092183 patent/WO2023213285A1/zh not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111901847A (zh) * | 2020-02-13 | 2020-11-06 | 中兴通讯股份有限公司 | sidelink中继通信方法、装置、设备及介质 |
| CN113938982A (zh) * | 2020-06-29 | 2022-01-14 | 华硕电脑股份有限公司 | 无线通信系统中侧链路数据无线电承载建立的方法和设备 |
| US20220095411A1 (en) * | 2020-09-22 | 2022-03-24 | Mediatek Inc. | Methods and Apparatus for Signalling Transmission in L2 UE-to-Network Relay Operation |
| CN114390532A (zh) * | 2020-10-21 | 2022-04-22 | 华硕电脑股份有限公司 | 无线通信系统中用户设备到网络中继的适配层配置的方法和设备 |
| WO2022089318A1 (zh) * | 2020-10-27 | 2022-05-05 | 夏普株式会社 | 发现中继ue的方法、搜索中继ue的方法及用户设备 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP4521824A4 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2025137899A1 (zh) * | 2023-12-26 | 2025-07-03 | 北京小米移动软件有限公司 | 通信方法、终端、通信系统及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| US20250294626A1 (en) | 2025-09-18 |
| CN117062108A (zh) | 2023-11-14 |
| EP4521824A1 (en) | 2025-03-12 |
| EP4521824A4 (en) | 2026-04-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP2021505023A (ja) | 多重接続のための方法およびその装置 | |
| US20240040438A1 (en) | Qos splitting and carrying methods, object side qos determination method, and ue | |
| US20250056649A1 (en) | Method performed by user equipment, and user equipment | |
| WO2023274225A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2023213285A1 (zh) | 由用户设备执行的方法及用户设备 | |
| EP4550910A1 (en) | Method executed by user equipment, and user equipment | |
| US20240292484A1 (en) | Method performed by user equipment and user equipment | |
| WO2023131231A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2022007925A1 (zh) | 流量控制方法及设备 | |
| WO2024230725A1 (zh) | 由用户设备执行的方法及用户设备 | |
| WO2022233300A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2023001172A1 (zh) | 推荐比特率确定方法、装置及相关设备 | |
| JP2023113065A (ja) | 端末装置、方法、および、集積回路 | |
| WO2024051648A1 (zh) | 由用户设备执行的方法及用户设备 | |
| US20240244679A1 (en) | Method performed by user equipment, and user equipment | |
| WO2025130767A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2023098865A1 (zh) | 由用户设备执行的方法及用户设备 | |
| WO2025146068A1 (zh) | 执行a2x通信的方法以及用户设备 | |
| WO2024067623A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| CN116261116A (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2024125499A1 (zh) | 由用户设备执行的方法以及用户设备 | |
| WO2025031353A1 (zh) | 由用户设备执行的方法及用户设备 | |
| JP2023113064A (ja) | 端末装置、基地局装置、および、方法 | |
| WO2023213267A1 (zh) | 由用户设备执行的方法及用户设备 | |
| CN121418843A (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: 23799271 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 18861933 Country of ref document: US |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2023799271 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| ENP | Entry into the national phase |
Ref document number: 2023799271 Country of ref document: EP Effective date: 20241206 |
|
| WWP | Wipo information: published in national office |
Ref document number: 18861933 Country of ref document: US |