WO2023040969A1 - 用户设备能力交互的方法及用户设备 - Google Patents

用户设备能力交互的方法及用户设备 Download PDF

Info

Publication number
WO2023040969A1
WO2023040969A1 PCT/CN2022/119055 CN2022119055W WO2023040969A1 WO 2023040969 A1 WO2023040969 A1 WO 2023040969A1 CN 2022119055 W CN2022119055 W CN 2022119055W WO 2023040969 A1 WO2023040969 A1 WO 2023040969A1
Authority
WO
WIPO (PCT)
Prior art keywords
remote
relay
message
capabilities
user equipment
Prior art date
Application number
PCT/CN2022/119055
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 WO2023040969A1 publication Critical patent/WO2023040969A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • 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 UE capability interaction in a sidelink communication relay architecture 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 sideline 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 literature: RP-211050 reivised WID NR sidelink relay.
  • One of the goals of this work item is to standardize the sidebound communication control plane procedures, such as management of RRC connections, reception of system messages and reception of pages.
  • a remote UE may need to select a relay UE (relay UE) to provide it with relay services.
  • a relay UE relay UE
  • an RRC connection can be established between the remote UE and the base station.
  • the remote UE needs to obtain system information from the base station and paging from the network side.
  • the relay UE can replace the remote UE to request system information from the base station, receive the system information from the base station, and forward the system information to the remote UE.
  • the relay UE can monitor and receive the paging message sent by the base station instead of the remote UE.
  • the relay UE needs to have the corresponding ability to support requesting and receiving a certain (certain) system message requested by the remote UE from the base station and monitor and receive paging messages according to the paging time of the remote UE. If the relay UE does not have the corresponding capability, it will It cannot replace the remote UE to complete the relevant process.
  • the present invention discusses the problem and processing method of air interface capability mismatch between remote UE and relay UE in the process of requesting system information and receiving paging.
  • the purpose of the present invention is to provide a method for processing the air interface capability mismatch between the remote UE and the relay UE during the process of requesting system information and receiving paging.
  • the remote UE sends a UECapabilityEnquirySidelink message to the relay UE,
  • the relay UE receives the UECapabilityEnquirySidelink message
  • the relay UE feeds back its own capabilities to the remote UE through the UECapabilityInformationSidelink message, and the capabilities include part or all of the Uu port UE capabilities of the relay UE,
  • the remote UE receives the UECapabilityInformationSidelink message sent by the relay UE, and handles the Uu port UE capability mismatch between the remote UE and the relay UE.
  • the method performed by the user equipment according to the first aspect of the present invention is characterized in that,
  • the remote UE includes its own part in the UECapabilityEnquirySidelink message or
  • the method performed by the user equipment according to the first aspect of the present invention is characterized in that,
  • the remote UE requests the relay UE to report part or all of the Uu interface UE capabilities of the relay UE.
  • the method performed by the user equipment according to the first aspect of the present invention is characterized in that,
  • the relay UE reports part or all of its Uu interface UE capabilities according to the request of the remote UE for the part or all of the Uu interface UE capabilities of the relay UE.
  • the method performed by the user equipment according to the first aspect of the present invention is characterized in that,
  • the Uu port UE capability reported by the relay UE includes one or more of the following capabilities: eDRX capability, positioning capability, and RRC_CONNECTED on-demand SI capability of the relay UE.
  • the method performed by the user equipment according to the first aspect of the present invention is characterized in that,
  • the discovery message of the PC5 interface of the relay UE carries part or all of the Uu interface UE capabilities of the relay UE.
  • the remote UE sends a newly defined PC5-RRC message to the relay UE, which is used to convey the Uu interface UE capability of the remote UE and/or the request for the Uu interface UE capability of the relay UE,
  • the relay UE receives the UuUECapabilityEnquiry sent by the remote remote UE,
  • the relay UE sends a newly defined PC5-RRC message, which is used to feed back its own Uu interface UE capabilities to the remote remote UE,
  • the remote remote UE receives the UuUECapabilityInformation message sent by the relay relay UE.
  • the remote UE sends a UECapabilityEnquirySidelink message to the relay UE,
  • the relay UE receives the UECapabilityEnquirySidelink sent by the remote UE,
  • the relay UE feeds back its ability to support certain or certain functions of the remote UE to the remote UE through the UECapabilityInformationSidelink message.
  • the source side remote UE requests the sidelink UE capability of the target remote UE from the relay UE through the UECapabilityEnquirySidelink message,
  • the relay UE does not have the sidelink UE capability of the target remote UE, send a UECapabilityEnquirySidelink message to the target remote UE,
  • the relay UE After receiving the UECapabilityInformationSidelink message sent by the target remote UE, the relay UE sends the UECapabilityInformationSidelink message to the source-side remote UE.
  • the user equipment according to the fifth aspect of the present invention includes:
  • a memory storing instructions
  • a method for processing air interface capability mismatch between a remote UE and a relay UE in the process of requesting system information and receiving paging is provided.
  • Fig. 1 is a flowchart representing a method executed by a user equipment in a relay scenario according to an embodiment of the present invention.
  • Fig. 2 is a flow chart showing a method executed by a user equipment in a relay scenario according to other embodiments of the present invention.
  • Fig. 3 is a flowchart showing a method executed by a user equipment in a relay scenario according to yet another embodiment of the present invention.
  • Fig. 4 is a flowchart showing a method executed by a user equipment in a relay scenario according to yet another embodiment of the present invention.
  • Fig. 5 is a flowchart representing a method executed by a user equipment in a relay scenario according to another embodiment of the present invention.
  • 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 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 radio 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 radio bearer
  • SRB Signaling Radio Bearer, signaling radio bearer
  • 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.
  • “Feedback”, “report”, “escalation”, “send”, notification are used interchangeably.
  • “Instead of listening to and/or receiving paging for the remote UE”, “listening and/or receiving paging for the remote UE” and “listening and/or receiving paging for the remote UE” may be used interchangeably.
  • “Enable”, “adopt”, “apply”, “enable”, “activate”, “implement” and the like are 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.
  • UE-to-UE relay is shown in the figure below, with remote UEs on the left and right sides and relay UE in the middle.
  • the remote UE and the relay UE are respectively connected through the PC5 interface. Since the two remote UEs are far away or the communication environment is not good, the relay UE needs to relay and forward the signaling and data between the two remote UEs.
  • Scenarios for UE-to-UE relay include:
  • two remote UEs ie, the source UE and the target UE
  • the relay UE are within the coverage
  • Partial coverage among the two remote UEs and the relay UE, at least one UE is within the coverage area, and at least one UE is outside the coverage area.
  • the UE-to-Network relay is as shown in the figure below.
  • 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 left to The right ones are the remote UE and the relay UE respectively.
  • 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.
  • Scenario 1 Remote UE is out of coverage
  • Scenario 2 Remote UE is within coverage
  • 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 reference point between the UE and the radio access network is called Uu, so the connection between the UE and the radio access network is called a Uu connection.
  • Uu connection according to the state of the Uu RRC connection, the state of the UE can be divided into an idle state (RRC_IDLE state), an inactive state (RRC_INACTIVE state), and a connected state (RRC_CONNECTED state). After the RRC connection is established, the UE can be in the INACTIVE or CONNECTED state. If no RRC connection is established, the UE is in IDLE state.
  • the remote UE can be in the INACTIVE or CONNECTED state; if the RRC connection is not established, then the UE is in the IDLE state. Similarly, the relay UE can also be in one of these three states.
  • the relay UE when the remote UE is in RRC CONNECTED, the relay UE must be in RRC CONNECTED; when the remote UE is in RRC INACTIVE/IDLE, the relay UE can be in any of the three states of RRC CONNECTED/INACTIVE/IDLE.
  • the system information block is divided into two types: broadcasted or not broadcasted.
  • the indication information corresponding to a SIB will indicate whether the SIB is currently being broadcast or not.
  • the UE can obtain the corresponding SIB according to the scheduling information of the SIB provided in SIB1.
  • the scheduling information includes the time and frequency information of SIB reception, so the UE can receive the broadcasted SIB at the corresponding time and frequency.
  • the UE For the SIB that is indicated not to be currently broadcast, if the UE needs to acquire the SIB, there may be different methods according to the RRC connection state of the UE, which can be collectively referred to as the on-demand SI process.
  • the UE can generate an RRC system information request message (RRCSystemInfoRequest message) and send it to the base station.
  • RRCSystemInfoRequest message contains the list information of the SIB requested by the UE.
  • acknowledgement information acknowledgement
  • the UE can obtain the corresponding SIB according to the SIB scheduling information provided in SIB1.
  • the UE can generate a dedicated SIB request message (DedicatedSIBRequest message) and send it to the base station.
  • the DedicatedSIBRequest message contains the list information of the SIB requested by the UE. Then the UE can obtain the corresponding SIB according to the SIB scheduling information provided in SIB1, or receive the RRC reconfiguration message sent by the base station, which carries the SIB requested by the UE.
  • the remote UE For the remote UE in RRC_CONNECTED, if the remote UE needs a certain (or some) base station to indicate the SIB that is not currently being broadcast, it can send a DedicatedSIBRequest message request, and the relay UE forwards it to the base station. If the base station sends the SIB to the relay UE through the RRC reconfiguration message, the relay UE will forward it to the remote UE; if the base station sends the SIB by broadcast, the relay UE will go to the corresponding time and frequency position according to the SIB scheduling information in SIB1 Receive SIB and forward it to remote UE.
  • the remote UE For the remote UE in RRC_IDLE/INACTIVE, if the remote UE needs a certain (or some) base station to indicate the SIB that is not currently being broadcast, the remote UE will notify the relay UE of the type of system information that needs to be requested through the PC5RRC message. If the relay UE is in the RRC_CONNECTED state, the relay UE requests the base station through the DedicatedSIBRequest message message; if the relay UE is in the RRC_IDLE/INACTIVE state, the relay UE sends the RRCSystemInfoRequest message to the base station to request. The subsequent system message receiving process is as described above.
  • the relay UE If the relay UE does not support the function of the on-demand SI in the RRC_CONNECTED state, or the relay UE does not support the SIB type requested by the remote UE, the relay UE cannot replace the remote UE to request and obtain the SIB.
  • UEs in RRC_IDLE/RRC_INACTIVE can be configured with eDRX, ie longer discontinuous reception, to save power consumption.
  • the eDRX cycle is several H-SFNs, and the cycle boundary is a fixed H-SFN number.
  • a UE configured with an eDRX cycle can be configured with a periodic PTW at the same time.
  • PTW is a period of paging monitoring time in the eDRX cycle. In each eDRX cycle, the UE monitors POs and receives paging according to the PTW.
  • the remote UE in RRC_IDLE/RRC_INACTIVE notifies the relay UE of its Uu port eDRX cycle (cycle) information, and the relay UE listens to the corresponding PO to receive paging messages instead of the remote UE according to the eDRX cycle information of the remote UE. If the remote UE supports eDRX, but the relay UE does not support the eDRX function, the relay UE cannot monitor and receive paging messages instead of the remote UE.
  • the remote UE when the capabilities of the remote UE and the relay UE do not match, the remote UE is informed in time and related processing is performed, thereby reducing unnecessary signaling interactions and avoiding process abnormalities.
  • This embodiment is aimed at the UE-to-Network relay scenario, including steps 101, 103, 105 and 107.
  • Fig. 1 is a flowchart representing a method executed by a user equipment in a relay scenario according to an embodiment of the present invention.
  • the remote UE sends a UECapabilityEnquirySidelink message to the relay UE.
  • the message may contain one or more of the following information:
  • the Uu port UE capabilities of the remote UE may carry one or more of the following capabilities including but not limited to: eDRX capability of remote UE, positioning (positioning) capability, RRC_CONNECTED on-demand SI capability, etc.
  • the relay UE Request the relay UE to report part or all of the Uu interface UE capabilities of the relay UE.
  • one or more of the following capabilities may be requested including but not limited to: eDRX capability, positioning (positioning) capability, RRC_CONNECTED on-demand SI capability, etc.
  • the relay UE receives the UECapabilityEnquirySidelink message.
  • the relay UE feeds back its capability to the remote UE through a UECapabilityInformationSidelink message.
  • the message may contain one or more of the following information: part or all of the Uu port UE capabilities of the relay UE. In particular, it may carry one or more of the following capabilities including but not limited to: eDRX capability of relay UE, positioning (positioning) capability, RRC CONNECTED on-demand SI capability, etc.
  • the Uu port UE capabilities of these relay UEs are encoded in a unified IE, for example, the IE name: UECapabilityUu.
  • the relay UE can think that the Uu interface UE capabilities of the relay UE and the remote UE do not match.
  • the Relay UE may perform one or more of the following operations:
  • the remote UE receives the UECapabilityInformationSidelink message sent by the relay UE.
  • the remote UE may consider that the Uu port UE capabilities of the relay UE and the remote UE do not match.
  • Scenario 1 The relay UE does not support the RRC_CONNECTED on-demand SI function, and the remote UE supports the RRC_CONNECTED on-demand SI function.
  • the remote UE can perform one or more of the following judgments and operations:
  • the remote UE When the remote UE needs to request a certain or some SIBs from the base station, if the remote UE is within the coverage (in-coverage), the remote UE directly requests the SIB from the base station.
  • the remote UE if the remote UE is in RRC_CONNECTED, it can directly request the base station through the DedicatedSIBRequest message and receive the SIB directly from the base station.
  • the remote UE If the remote UE is in RRC_IDLE/INACTIVE, it can request the base station through the RRCSystemInfoRequest message and receive the SIB directly from the base station.
  • the remote UE may also determine that it directly requests the SIB from the base station only when the relay UE is in the RRC_CONNECTED state.
  • Scenario 1 can also be changed to, as long as the relay UE does not support the RRC_CONNECTED on-demand SI function, the remote UE will perform the above judgment and operation.
  • Scenario 2 The relay UE does not support the positioning function, and the remote UE supports the positioning function.
  • the remote UE can perform one or more of the following judgments and operations:
  • the remote UE When the remote UE needs to request the positioning-related SIB (such as posSIB) from the base station, if the remote UE is within the coverage (in-coverage), the remote UE directly requests the posSIB from the base station.
  • the positioning-related SIB such as posSIB
  • the remote UE can directly request the base station through the DedicatedSIBRequest message, and receive posSIB directly from the base station. If the remote UE is in RRC_IDLE/INACTIVE, it can request the base station through the RRCSystemInfoRequest message and receive posSIB directly from the base station.
  • the remote UE can also determine that it directly requests the posSIB from the base station only when the relay UE is in the RRC_CONNECTED state.
  • Scenario 3 The relay UE does not support the eDRX function, and the remote UE supports the eDRX function.
  • the remote UE can perform one or more of the following operations:
  • the eDRX function is not enabled (optionally, the core network is notified that the eDRX function is not enabled).
  • This embodiment is aimed at a UE-to-Network relay scenario.
  • Fig. 2 is a flow chart showing a method executed by a user equipment in a relay scenario according to other embodiments of the present invention.
  • the relay UE carries part or all of the Uu port UE capabilities of the relay UE in the Discovery message of the PC5 port.
  • it may carry one or more of the following capabilities including but not limited to: eDRX capability of relay UE, positioning (positioning) capability, RRC_CONNECTED on-demand SI capability, etc.
  • the remote UE can consider the relay UE and the remote UE The UE capabilities of the Uu interface do not match.
  • the subsequent processing of the Remote UE is the same as the processing after receiving the UECapabilityInformationSidelink message sent by the relay UE in step 107 of the first embodiment.
  • the Discovery message here refers to a general term for a class of PC5 messages used to complete the relay discovery function, including but not limited to: Discovery Solicitation, Discovery Response, Discovery Announcement, Relay Discovery Additional Information, etc.
  • This embodiment is aimed at the UE-to-Network relay scenario, including steps 301, 303, 305 and 307.
  • Fig. 3 is a flowchart showing a method executed by a user equipment in a relay scenario according to yet another embodiment of the present invention.
  • the remote UE sends a newly defined PC5-RRC message (message name example: UuUECapabilityEnquiry) to the relay UE, which is used to transfer the Uu port UE capability of the remote UE and/or to the relay UE Uu A request for UE capabilities.
  • PC5-RRC message messages name example: UuUECapabilityEnquiry
  • the information that may be included in the message is as described in step 101 of the first embodiment.
  • the relay UE receives the Uu UECapabilityEnquiry sent by the remote UE.
  • the relay UE sends a newly defined PC5-RRC message (message name example: UuUECapabilityInformation), which is used to feed back its own Uu port UE capability to the remote UE.
  • the information that may be included in the message is as described in step 105 of the first embodiment. If the Uu interface UE capabilities of the relay UE and the remote UE do not match, the subsequent processing of the relay UE is the same as that described in step 105 of the first embodiment.
  • the remote UE receives the UuUECapabilityInformation message sent by the relay UE.
  • the subsequent processing of the Remote UE is the same as the processing after receiving the UECapabilityInformationSidelink message in step 107 of the first embodiment.
  • This embodiment is aimed at the UE-to-Network relay scenario, including steps 401, 403, 405 and 407.
  • Fig. 4 is a flowchart showing a method executed by a user equipment in a relay scenario according to yet another embodiment of the present invention.
  • the remote UE sends a UECapabilityEnquirySidelink message to the relay UE.
  • the message may contain one or more of the following information:
  • the Uu port UE capabilities of the remote UE may carry one or more of the following capabilities including but not limited to: eDRX capability of remote UE, positioning (positioning) capability, RRC_CONNECTED on-demand SI capability, etc.
  • the relay UE to report the ability of the relay UE to support certain or certain functions of the remote UE.
  • one or more of the following capabilities may be requested, including but not limited to: the ability to support remote UEs to implement eDRX, the ability to support remote UEs to achieve positioning (positioning), the ability to support remote UEs to obtain posSIB, and the ability to support remote UEs to obtain on -demand SI capabilities, etc.
  • the relay UE receives the UECapabilityEnquirySidelink sent by the remote UE.
  • the relay UE feeds back to the remote UE its ability to support certain or certain functions of the remote UE through a UECapabilityInformationSidelink message.
  • the message may include but not limited to one or more of the following capabilities: the ability to support remote UEs to implement eDRX, the ability to support remote UEs to implement positioning (positioning), the ability to support remote UEs to obtain posSIB, and the ability to support remote UEs to obtain on- demand SI capabilities, etc.
  • the Relay UE can perform one or more of the following operations:
  • Relay UE does not support remote UE to implement eDRX function processing.
  • step 407 the operation of the remote UE after receiving the UECapabilityInformationSidelink message sent by the relay UE, optionally, if the UECapabilityInformationSidelink message shows that the relay UE does not support a certain function of the remote UE, and the remote UE supports this function Or expect the relay UE to support this function, it can be considered that the UE capabilities of the relay UE and the remote UE do not match.
  • the subsequent processing of the Remote UE is the same as that described in step 107 of the first embodiment.
  • This embodiment is aimed at a UE-to-UE relay scenario, including steps 501, 503, 505 and 507.
  • Fig. 5 is a flowchart representing a method executed by a user equipment in a relay scenario according to another embodiment of the present invention.
  • the source remote UE requests the relay UE for the sidelink UE capability of the target remote UE through a UECapabilityEnquirySidelink message.
  • This message can contain one or more of the sidelink UE capabilities that request the target remote UE, for example:
  • Target remote UE supports application frequency band filter information (appliedFreqBandListFilter).
  • step 503 if the relay UE does not have the sidelink UE capability of the target remote UE, send a UECapabilityEnquirySidelink message to the target remote UE.
  • step 505 after receiving the UECapabilityInformationSidelink message sent by the target remote UE, the relay UE sends the UECapabilityInformationSidelink message to the source remote UE.
  • the message may carry one or more sidelink UE capabilities of the target remote UE, for example:
  • Target remote UE supports application frequency band filter information (appliedFreqBandListFilter).
  • the relay UE may carry the sidelink UE capability of the target remote UE requested by the source remote UE in the UECapabilityInformationSidelink message.
  • the relay UE if it already has the sidelink UE capability of the target remote UE, it will directly send the UECapabilityInformationSidelink message to the source remote UE without requesting the target remote UE again.
  • step 507 after the source remote UE receives the UECapabilityInformationSidelink message sent by the relay UE, if the Sidelink UE capability of the target remote UE is different from the Sidelink UE capability of the source remote UE, or if the Sidelink UE capability of the target remote UE is not In line with the expectations of the source remote UE, it can be considered that the Sidelink UE capabilities of the source remote UE and the target remote UE do not match.
  • the source remote UE can initiate relay reselection.
  • the UECapabilityEnquirySidelink and UECapabilityInformationSidelink messages in this embodiment may also be replaced by other PC5-RRC messages, such as message 1 and message 2, as long as the same functions as those in this embodiment are completed.
  • message 1 carries source remote UE's request for target remote UE's sidelink UE capability to relay UE
  • relay UE sends response message 2 to source remote UE and carries target remote UE's sidelink UE capability in message 2 (or carries message 1 request The sidelink UE capability of the target remote UE).
  • Fig. 6 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • the user equipment UE700 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 short-term dynamic storage program recording medium, 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)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种由用户设备执行的方法及用户设备。远端UE向中继UE发送UECapabilityEnquirySidelink消息，中继UE接收UECapabilityEnquirySidelink消息，中继UE通过UECapabilityInformationSidelink消息向远端UE反馈自己的能力，所述能力包括中继UE的部分或者全部Uu口UE能力，远端UE收到中继UE发送的UECapabilityInformationSidelink消息，进行远端UE和中继UE的Uu口UE能力不匹配的处理。

Description

用户设备能力交互的方法及用户设备 技术领域
本发明涉及无线通信技术领域，更具体地，本发明涉及由用户设备执行侧行通信中继架构中UE能力交互的方法以及相应的用户设备。
背景技术
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-193253New Study Item on NR Sidelink Relaying)，并获批准。该研究项目的最新版本参见非专利文献：RP-201474reivised SID NR sidelink relay。该研究项目主要研究UE(用户设备)到网络和UE到UE的中继解决方案，用于扩展基于侧行通信的覆盖。该研究项目的目标之一是支持侧行通信控制面流程。
2020年3月，RAN#91次全会上，针对版本17的NR sidelink relaying(侧行通信中继)的工作项目被提出(参见非专利文献：RP-210904 New Study Item on NR Sidelink Relaying)，并获批准。该工作项目的最新版本参见非专利文献：RP-211050 reivised WID NR sidelink relay。该工作项目的目标之一是标准化侧行通信控制面流程，例如RRC连接的管理、系统消息的接收和寻呼的接收。
远端UE(remote UE)为了和基站或者另一个远端UE进行侧行通信，可能需要选择一个中继UE(relay UE)为它提供中继服务。在UE到基站的中继架构中remote UE和基站之间可以建立RRC连接。为了能够建立RRC连接，remote UE需要获取基站的系统消息以及网络侧的寻呼。对于系 统消息，relay UE可以代替remote UE向基站请求系统消息，接收基站的系统消息，并转发系统消息给remote UE。对于寻呼消息，当remote UE和基站的RRC连接被释放后，为了保证remote UE的可达性，relay UE可以代替remote UE监听并接收基站发送的寻呼消息。relay UE需要具有对应的能力支持向基站请求和接收remote UE所请求的某个(某些)系统消息和按remote UE的寻呼时刻监听和接收寻呼消息，如果relay UE没有对应的能力，就无法代替remote UE完成相关流程。
本发明讨论remote UE和relay UE在请求系统消息和接收寻呼的过程中空口能力不匹配的问题和处理方法。
发明内容
本发明的目的在于提供一种remote UE和relay UE在请求系统消息和接收寻呼的过程中空口能力不匹配的处理方法。
根据本发明的第一方面，包括：
远端UE向中继UE发送UECapabilityEnquirySidelink消息，
中继UE接收UECapabilityEnquirySidelink消息，
中继UE通过UECapabilityInformationSidelink消息向远端UE反馈自己的能力，所述能力包括中继UE的部分或者全部Uu口UE能力，
远端UE收到中继UE发送的UECapabilityInformationSidelink消息，进行远端UE和中继UE的Uu口UE能力不匹配的处理。
根据本发明的第一方面的由用户设备执行的方法，其特征在于，
所述远端UE在UECapabilityEnquirySidelink消息中包含自己的部分或
全部Uu口UE能力。
根据本发明的第一方面的由用户设备执行的方法，其特征在于，
所述远端UE请求所述中继UE上报所述中继UE的部分或者全部Uu口UE能力。
根据本发明的第一方面的由用户设备执行的方法，其特征在于，
所述中继UE根据远端UE请求的所述中继UE的部分或者全部Uu口UE能力，上报自己的部分或全部Uu口UE能力。
根据本发明的第一方面的由用户设备执行的方法，其特征在于，
所述中继UE上报的Uu口UE能力包括如下能力的一种或者多种：中继UE的eDRX能力、定位能力、RRC_CONNECTED on-demand SI能力。
根据本发明的第一方面的由用户设备执行的方法，其特征在于，
所述中继UE在PC5口的Discovery消息中携带所述中继UE的部分或全部Uu口UE能力。
根据本发明的第二方面，其特征在于，
远端UE向中继UE发送一条新定义的PC5-RRC消息，该消息用于传递远端UE的所述Uu口UE能力和/或对中继UE Uu口UE能力的请求，
中继UE接收远端remote UE发送的UuUECapabilityEnquiry，
中继UE发送一条新定义的PC5-RRC消息，该消息用于向远端remote UE反馈自己的Uu口UE能力，
远端remote UE收到中继relay UE发送的UuUECapabilityInformation消息。
根据本发明的第三方面，其特征在于，
远端UE向中继UE发送UECapabilityEnquirySidelink消息，
中继UE接收远端UE发送的UECapabilityEnquirySidelink，
中继UE通过UECapabilityInformationSidelink消息向远端UE反馈自己对远端UE某项或某些功能的支持能力。
根据本发明的第四方面，其特征在于，
源侧远端UE通过UECapabilityEnquirySidelink消息向中继UE请求目标远端UE的sidelink UE能力，
如果中继UE没有目标远端UE的sidelink UE能力，则向目标远端UE发送UECapabilityEnquirySidelink消息，
中继UE收到目标远端UE发送的UECapabilityInformationSidelink消息后，向源侧远端UE发送UECapabilityInformationSidelink消息。
根据本发明的第五方面的用户设备，包括：
处理器；以及
存储器，存储有指令；
其中，所述指令在由所述处理器运行时执行根据权利要求1至9中的任一项所述的方法。
发明效果
根据本发明，提供一种remote UE和relay UE在请求系统消息和接收寻呼的过程中空口能力不匹配的处理方法。
附图说明
图1是表示本发明涉及的一实施例的中继场景的由用户设备执行的方法的流程图。
图2是表示本发明涉及的其他实施例的中继场景的由用户设备执行的方法的流程图。
图3是表示本发明涉及的又一实施例的中继场景的由用户设备执行的方法的流程图。
图4是表示本发明涉及的又一实施例的中继场景的由用户设备执行的方法的流程图。
图5是表示本发明涉及的另一实施例的中继场景的由用户设备执行的方法的流程图。
图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，新无线电
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，信令无线承载
PO：Paging Occasion寻呼时刻
eDRX：Extended DRX扩展的不连续接收
Uu：空口
本发明中，网络、基站和RAN可互换使用，所述网络可以是长期演进LTE网络、新无线访问技术(New RAT，NR)网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
本发明中，用户设备UE可以指背景技术中所述的支持NR Sidelink中继功能的NR设备，也可以指支持NR sidelink中继架构的NR设备，也可以指其他类型的NR设备或者LTE设备。
本发明中，sidelink和PC5可以互换使用。“反馈”，“报告”，“上报”，“发送”，通知可以互换使用。“代替remote UE监听和/或接收寻呼”，“监 听和/或接收remote UE的寻呼”和“为remote UE监听和/或接收寻呼”可以互换使用。“启用”，“采用”，“应用”，“使能”，“激活”，“实现”等可以互换使用。
以下，对本发明的相关技术给出说明。
PC5接口是UE和UE之间进行控制面和用户面Sidelink通信的接口。对于Sidelink单播，PC5-RRC连接是一对源层二ID和目标层二ID之间的AS层逻辑连接。一个PC5单播链路建立就会对应有一个PC5-RRC连接建立。
UE-to-UE中继如下图所示，左右两侧为远端UE，中间为中继UE。远端UE和中继UE之间分别通过PC5接口连接。由于两个远端UE距离较远或者通信环境不佳，需要中继UE对两者间的信令和数据进行中继转发。
Figure PCTCN2022119055-appb-000001
UE-to-UE中继的场景包含：
1)覆盖范围内：两个远端UE(即源侧UE和目标侧UE)和中继UE都在覆盖范围内；
2)覆盖范围外：两个远端UE(即源侧UE和目标侧UE)和中继UE都在覆盖范围外；
3)部分覆盖：两个远端UE和中继UE中，至少有一个UE在覆盖范围内，并且至少有一个UE在覆盖范围外。
UE-to-Network中继如下图所述，场景1和场景2中，左侧为远端UE，中间为中继UE，右侧为网络；场景3中，两侧为网络，中间从左到右分别为远端UE和中继UE。远端UE和中继UE之间通过PC5接口连接，中继UE和网络通过Uu口连接。由于远端UE距离网络较远或者通信环境不佳，需要中继UE对两者间的信令和数据进行中继转发。
Figure PCTCN2022119055-appb-000002
场景1：Remote UE在覆盖范围外
Figure PCTCN2022119055-appb-000003
场景2：Remote UE在覆盖范围内
Figure PCTCN2022119055-appb-000004
场景3：Remote UE和Relay UE在不同小区
UE-to-Network中继的场景包含：
1)Remote UE在覆盖范围外，Relay UE在覆盖范围内；
2)Remote UE和Relay UE都在覆盖范围内，并且在同一个小区；
3)Remote UE和Relay UE都在覆盖范围内，但在不同小区。
Uu RRC连接及状态
UE和无线接入网络之间的参考点被称为Uu，因此UE和无线接入网络之间的连接被称为Uu连接。在Uu连接中，根据Uu RRC连接的状态，UE的状态可以分为空闲态(RRC_IDLE state)、非激活态(RRC_INACTIVE state)、连接态(RRC_CONNECTED state)。在RRC连接建立之后，UE可以处于INACTIVE或者CONNECTED state。如果没有建立RRC连接，那么UE处于IDLE state。
Remote UE与无线接入网络之间建立了RRC连接之后，那么remote UE可以处于INACTIVE或者CONNECTED state；如果没有建立RRC连接，那么UE处于IDLE state。类似地，relay UE也可以处于这三种状态之一。
需要说明的是，当remote UE处于RRC CONNECTED时，relay UE一定处于RRC CONNECTED；当remote UE处于RRC INACTIVE/IDLE时，relay UE可以处于RRC CONNECTED/INACTIVE/IDLE三种状态中的任意一种。
系统信息的获取
系统信息块分为被广播或者被不广播两种类型。一个SIB对应的指示信息会指示该SIB当前是被广播的，还是没有被广播的。对于指示当前被广播的SIB，UE可以根据SIB1中提供的该SIB的调度信息，去获取对应的SIB。调度信息中包含了SIB接收的时间和频率的信息，因此UE可以在对应的时刻和频率上接收到被广播的SIB。
对于被指示了当前没有被广播的SIB，如果UE需要获取该SIB，那么根据UE的RRC连接状态可以有不同的方式，可以统称为on-demand SI过程。
如果UE处于空闲态(IDLE)或者非激活态(INACTIVE)，那么UE可以生成RRC系统信息请求消息(RRCSystemInfoRequest message)，并发送给基站。在RRCSystemInfoRequest message中包含了UE所请求的SIB的列表信息。在接收到对该消息的确认信息(acknowledge)之后，UE可以根据SIB1中提供的SIB的调度信息，去获取对应的SIB。
如果UE处于连接态，那么UE可以生成专有SIB请求消息(DedicatedSIBRequest message)，并发送给基站。在DedicatedSIBRequest message中包含了UE所请求的SIB的列表信息。然后UE可以根据SIB1中提供的SIB的调度信息，去获取对应的SIB，或者是接收基站发送的RRC重配置消息，在该消息中携带了UE请求的SIB。
对于处于RRC_CONNECTED的remote UE，如果remote UE需要某个(或某些)基站指示了当前没有被广播的SIB，可以发送DedicatedSIBRequest message消息请求，relay UE将其转发给基站。如果基站通过RRC重配消息携带SIB发给relay UE，则relay UE转发给remote UE；如果基站通过广播的方式发送SIB，则relay UE根据SIB1中的该SIB调度信息去对应的时间和频率位置上接收SIB，并转发给remote UE。
对于处于RRC_IDLE/INACTIVE的remote UE，如果remote UE需要某 个(或某些)基站指示了当前没有被广播的SIB，remote UE将需要请求的系统消息类型通过PC5RRC消息通知给relay UE。如果relay UE处于RRC_CONNECTED状态，relay UE通过DedicatedSIBRequest message消息向基站请求；如果relay UE处于RRC_IDLE/INACTIVE状态，relay UE发送RRCSystemInfoRequest消息向基站请求。之后的系统消息接收过程如上文所述。如果relay UE不支持RRC_CONNECTED状态的on-demand SI这个Uu口的功能，或者relay UE不支持remote UE请求的SIB类型，则relay UE无法代替remote UE请求和获取SIB。
寻呼消息的监听和获取
处于RRC_IDLE/RRC_INACTIVE的UE可以被配置eDRX，即更长的不连续接收，从而节省功耗。eDRX周期为若干个H-SFN，并且该周期边界为固定的H-SFN号。配置了eDRX周期的UE可以同时被配置周期的PTW，PTW是eDRX周期内的一段寻呼监听时间，在每个eDRX周期内，UE根据PTW进行PO的监听和寻呼的接收。
处于RRC_IDLE/RRC_INACTIVE的remote UE将它的Uu口eDRX周期(cycle)信息通知给relay UE，relay UE根据remote UE的eDRX周期信息代替remote UE监听对应的PO接收寻呼消息。如果remote UE支持eDRX，而relay UE不支持eDRX功能，则relay UE无法代替remote UE监听和接收寻呼消息。
通过本发明，在remote UE和relay UE UE能力不匹配的情况下，让remote UE及时获知并进行相关处理，从而减少不必要的信令交互，以及避免流程异常。
以下，详细描述本发明对于上述问题的若干实施例。
实施例1
本实施例针对UE-to-Network中继场景，包含步骤101，103，105和107。
图1是表示本发明涉及的一实施例的中继场景的由用户设备执行的方法的流程图。
可选地，在步骤101中，remote UE向relay UE发送UECapabilityEnquirySidelink消息。该消息中可以包含如下信息的一种或多种：
1)remote UE的部分或全部Uu口UE能力。特别的，可以携带包括但不限于如下能力的一种或者多种：remote UE的eDRX能力，定位(positioning)能力，RRC_CONNECTED on-demand SI能力等。
2)请求relay UE上报relay UE的部分或者全部Uu口UE能力。特别的，可以请求包括但不限于如下能力的一种或者多种：eDRX能力，定位(positioning)能力，RRC_CONNECTED on-demand SI能力等。
可选地，在步骤103中，relay UE接收UECapabilityEnquirySidelink消息。
可选地，在步骤105中，relay UE通过UECapabilityInformationSidelink消息向remote UE反馈自己的能力。该消息中可以包含如下信息的一种或多种：relay UE的部分或全部Uu口UE能力。特别的，可以携带包括但不限于如下能力的一种或者多种：relay UE的eDRX能力，定位(positioning)能力，RRC CONNECTED on-demand SI能力等。可选地，这些relay UE的Uu口UE能力编码在一个统一的IE中，IE名称举例：UECapabilityUu。可选地，如果relay UE的全部或者部分Uu口UE能力和remote UE的Uu口UE能力不同(即relay UE支持某个功能而remote UE不支持该功能，或者反过来relay UE不支持某个功能而remote UE支持该功能)，relay UE可以认为relay UE和remote UE的Uu口UE能力不匹配。可选地，Relay UE可以执行如下操作的一种或者多种：
1)不代替remote UE监听和接收寻呼；
2)不代替remote UE请求和/或接收SIB；
3)按照remote UE的DRX信息(包括但不限于DRX cycle)为remote UE监听和接收寻呼。
可选地，在步骤107中，remote UE收到relay UE发送的UECapabilityInformationSidelink消息。可选地，如果relay UE的全部或者部分Uu口UE能力和remote UE的Uu口UE能力不同(即relay UE支持某 个功能而remote UE不支持该功能，或者反过来relay UE不支持某个功能而remote UE支持该功能，或者remote UE期望或预期relay UE具有某项功能而relay UE并不支持该功能)，remote UE可以认为relay UE和remote UE的Uu口UE能力不匹配。
如下举例其中三个可能的remote UE和relay UE的Uu口UE能力不匹配的场景。
场景一：relay UE不支持RRC_CONNECTED on-demand SI功能，remote UE支持RRC_CONNECTED on-demand SI功能。remote UE可以执行如下的判断和操作的一种或者多种：
1)触发relay重选；
2)在remote UE需要向基站请求某个或某些SIB时，如果remote UE处于覆盖范围内(in-coverage)，remote UE直接向基站请求SIB。可选地，如果remote UE处于RRC_CONNECTED，可以通过DedicatedSIBRequest message消息向基站直接请求，并从基站直接接收SIB。如果remote UE处于RRC_IDLE/INACTIVE，可以通过RRCSystemInfoRequest消息向基站请求，并从基站直接接收SIB。可选地，remote UE也可以判断只有relay UE处于RRC_CONNECTED状态下它才直接向基站请求SIB。
可选地，场景一也可变形为，只要relay UE不支持RRC_CONNECTED on-demand SI功能，remote UE就执行如上的判断和操作。
场景二：relay UE不支持positioning功能，remote UE支持positioning功能。remote UE可以执行如下的判断和操作的一种或者多种：
1)触发relay重选；
2)不启用positioning功能；
3)在remote UE需要向基站请求positioning相关SIB时(如posSIB)，如果remote UE处于覆盖范围内(in-coverage)，remote UE直接向基站请求posSIB。
可选地，如果remote UE处于RRC_CONNECTED，可以通过DedicatedSIBRequest message消息向基站直接请求，并从基站直接接收posSIB。如果remote UE处于RRC_IDLE/INACTIVE，可以通过RRCSystemInfoRequest消息向基站请求，并从基站直接接 收posSIB。
可选地，remote UE也可以判断只有relay UE处于RRC_CONNECTED状态下它才直接向基站请求posSIB。
场景三：relay UE不支持eDRX功能，remote UE支持eDRX功能。
可选地，remote UE可以执行如下操作的一种或者多种：
1)触发relay重选；
2)不启用eDRX功能(可选地，通知核心网eDRX功能不启用)。
实施例2
本实施例针对UE-to-Network中继场景。
图2是表示本发明涉及的其他实施例的中继场景的由用户设备执行的方法的流程图。
可选地，relay UE在PC5口的Discovery消息中携带relay UE的部分或全部Uu口UE能力。特别的，可以携带包括但不限于如下能力的一种或者多种：relay UE的eDRX能力，定位(positioning)能力，RRC_CONNECTED on-demand SI能力等。
可选地，remote UE收到relay UE发送的Discovery消息后，如果relay UE的全部或者部分Uu口UE能力和remote UE的Uu口UE能力不同(即relay UE支持某个功能而remote UE不支持该功能，或者反过来relay UE不支持某个功能而remote UE支持该功能，或者remote UE期望或预期relay UE具有某项功能而relay UE并不支持该功能)，remote UE可以认为relay UE和remote UE的Uu口UE能力不匹配。Remote UE的后续处理同实施例一步骤107中接收到relay UE发送的UECapabilityInformationSidelink消息后的处理。
需要说明的是，这里的Discovery消息是指一类用于完成relay discovery功能的PC5消息的统称，包括但不限于：Discovery Solicitation，Discovery Response，Discovery Announcement，Relay Discovery Additional Information等。
实施例3
本实施例针对UE-to-Network中继场景，包含步骤301，303，305和 307。
图3是表示本发明涉及的又一实施例的中继场景的由用户设备执行的方法的流程图。
可选地，在步骤301中，remote UE向relay UE发送一条新定义的PC5-RRC消息(消息名称举例：UuUECapabilityEnquiry)，该消息用于传递remote UE的Uu口UE能力和/或对relay UE Uu口UE能力的请求。该消息中可以包含的信息如实施例一的步骤101中所述。
可选地，在步骤303中，relay UE接收remote UE发送的Uu UECapab ilityEnqu iry。
可选地，在步骤305中，relay UE发送一条新定义的PC5-RRC消息(消息名称举例：UuUECapabilityInformation)，该消息用于向remote UE反馈自己的Uu口UE能力。该消息中可以包含的信息如实施例一步骤105所述。如果relay UE和remote UE的Uu口UE能力不匹配，Relay UE的后续处理同实施例一的步骤105中所述。
可选地，在步骤307中，remote UE收到relay UE发送的UuUECapabilityInformation消息。Remote UE的后续处理同实施例一的步骤107收到UECapabilityInformationSidelink消息后的处理。
实施例4
本实施例针对UE-to-Network中继场景，包含步骤401，403，405和407。
图4是表示本发明涉及的又一实施例的中继场景的由用户设备执行的方法的流程图。
可选地，在步骤401中，remote UE向relay UE发送UECapabilityEnquirySidelink消息。该消息中可以包含如下信息的一种或多种：
1)remote UE的部分或全部Uu口UE能力。特别的，可以携带包括但不限于如下能力的一种或者多种：remote UE的eDRX能力，定位(positioning)能力，RRC_CONNECTED on-demand SI能力等。
2)请求relay UE上报relay UE对remote UE某项或某些功能支持的 能力。特别的，可以请求包括但不限于如下能力的一种或者多种：支持remote UE实现eDRX的能力，支持remote UE实现定位(positioning)的能力，支持remote UE获取posSIB的能力，支持remote UE获取on-demand SI的能力等。
可选地，在步骤403中，relay UE接收remote UE发送的UECapabilityEnquirySidelink。
可选地，在步骤405中，relay UE通过UECapabilityInformationSidelink消息向remote UE反馈自己对remote UE某项或某些功能的支持能力。该消息中可以包含但不限于如下能力的一种或者多种：支持remote UE实现eDRX的能力，支持remote UE实现定位(positioning)的能力，支持remote UE获取posSIB的能力，支持remote UE获取on-demand SI的能力等。例如，如果relay UE不支持remote UE实现eDRX功能，Relay UE可以执行如下操作的一种或者多种：
1)将支持remote UE实现eDRX的能力置为“不支持”，例如将对应比特位置为0；
2)不代替remote UE监听和接收寻呼；
3)按照remote UE的DRX信息(包括但不限于DRX cycle)为remote UE监听和接收寻呼。
其他能力的处理方式均可参考relay UE不支持remote UE实现eDRX功能的处理。
可选地，在步骤407中，remote UE收到relay UE发送的UECapabilityInformationSidelink消息后的操作，可选地，如果UECapabilityInformationSidelink消息中显示relay UE不支持remote UE的某项功能，而remote UE支持该项功能或者期望relay UE支持该项功能，可以认为relay UE和remote UE的UE能力不匹配。Remote UE的后续处理同实施例一步骤107所述。
实施例5
本实施例针对UE-to-UE中继场景，包含步骤501，503，505和步骤507。
图5是表示本发明涉及的另一实施例的中继场景的由用户设备执行的方法的流程图。
可选地，在步骤501中，source remote UE通过UECapabilityEnquirySidelink消息向relay UE请求target remote UE的sidelink UE能力。该消息中可以包含请求target remote UE的sidelink UE能力的一种或多种，例如：
1)Target remote UE的Sidelink PDCP能力信息或相关参数；
2)Target remote UE的接入层版本能力信息或相关参数；
3)Target remote UE的sidelink RLC能力信息或相关参数；
4)Target remote UE的支持频段组合信息。
5)Target remote UE的支持应用频率频段滤波信息(appliedFreqBandListFilter)。
可选地，在步骤503中，如果relay UE没有target remote UE的sidelink UE能力，则向target remote UE发送UECapabilityEnquirySidelink消息。
可选地，在步骤505中，relay UE收到target remote UE发送的UECapabilityInformationSidelink消息后，向seurce remote UE发送UECapabilityInformationSidelink消息。可选地，该消息中可以携带target remote UE的sidelink UE能力的一种或多种，例如：
1)Target remote UE的Sidelink PDCP能力信息或相关参数；
2)Target remote UE的接入层版本能力信息或相关参数；
3)Target remote UE的sidelink RLC能力信息或相关参数；
4)Target remote UE的支持频段组合信息。
5)Target remote UE的支持应用频率频段滤波信息(appliedFreqBandListFilter)。
如果存在步骤501，则relay UE可以在UECapabilityInformationSidelink消息中携带soure remote UE请求的target remote UE的sidelink UE能力。
同时，如果在步骤501之后，如果relay UE已经有target remote UE的sidelink UE能力，则直接向source remote UE发送UECapabilityInformationSidelink消息，而不用再次向target remote UE请求。
可选地，在步骤507中，source remote UE收到relay UE发送的UECapabilityInformationSidelink消息后，如果target remote UE的Sidelink UE 能力和source remote UE的Sidelink UE能力不同，或者如果target remote UE的Sidelink UE能力不符合source remote UE的预期，可以认为source remote UE和target remote UE的Sidelink UE能力不匹配。可选地，source remote UE可以发起relay重选。
特别地，该实施例中的UECapabilityEnquirySidelink和UECapabilityInformationSidelink消息也可以由其他PC5-RRC消息代替，例如消息一和消息二，只要是完成和该实施例中相同的功能即可。例如消息一携带source remote UE对target remote UE的sidelink UE能力的请求给relay UE，relay UE发送响应消息二给source remote UE并在消息二中携带target remote UE的sidelink UE能力(或者携带消息一请求的target remote UE的sidelink UE能力)。
图6是本发明涉及的用户设备UE的简要结构框图。如图6所示，该用户设备UE700包括处理器601和存储器602。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器602上存储有程序指令。该指令在由处理器601运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时 动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备UE执行的方法，包括：
    远端UE向中继UE发送UECapabilityEnquirySidelink消息，
    中继UE接收UECapabilityEnquirySidelink消息，
    中继UE通过UECapabilityInformationSidelink消息向远端UE反馈自己的能力，所述能力包括中继UE的部分或者全部Uu口UE能力，
    远端UE收到中继UE发送的UECapabilityInformationSidelink消息，进行远端UE和中继UE的Uu口UE能力不匹配的处理。
  2. 根据权利要求1所述的由用户设备执行的方法，其特征在于，
    所述远端UE在UECapabilityEnquirySidelink消息中包含自己的部分或全部Uu口UE能力。
  3. 根据权利要求1所述的由用户设备执行的方法，其特征在于，
    所述远端UE请求所述中继UE上报所述中继UE的部分或者全部Uu口UE能力。
  4. 根据权利要求1所述的由用户设备执行的方法，其特征在于，
    所述中继UE根据远端UE请求的所述中继UE的部分或者全部Uu口UE能力，上报自己的部分或全部Uu口UE能力。
  5. 根据权利要求1所述的由用户设备执行的方法，其特征在于，
    所述中继UE上报的Uu口UE能力包括如下能力的一种或者多种：中继UE的eDRX能力、定位能力、RRC_CONNECTED on-demand SI能力。
  6. 根据权利要求1所述的由用户设备执行的方法，其特征在于，
    所述中继UE在PC5口的Discovery消息中携带所述中继UE的部分或全部Uu口UE能力。
  7. 一种由用户设备执行的方法，其特征在于，
    远端UE向中继UE发送一条新定义的PC5-RRC消息，该消息用于传递远端UE的所述Uu口UE能力和/或对中继UE Uu口UE能力的请求，
    中继UE接收远端remote UE发送的UuUECapabilityEnquiry，
    中继UE发送一条新定义的PC5-RRC消息，该消息用于向远端remote UE反馈自己的Uu口UE能力，
    远端remote UE收到中继relay UE发送的UuUECapabilityInformation消息。
  8. 一种由用户设备执行的方法，其特征在于，
    远端UE向中继UE发送UECapabilityEnquirySidelink消息，
    中继UE接收远端UE发送的UECapabilityEnquirySidelink，
    中继UE通过UECapabilityInformationSidelink消息向远端UE反馈自己对远端UE某项或某些功能的支持能力。
  9. 一种由用户设备执行的方法，其特征在于，
    源侧远端UE通过UECapabilityEnquirySidelink消息向中继UE请求目标侧远端UE的sidelink UE能力，
    如果中继UE没有目标侧远端UE的sidelink UE能力，则向目标侧远端UE发送UECapabilityEnquirySidelink消息，
    中继UE收到目标侧远端UE发送的UECapabilityInformationSidelink消息后，向源侧远端UE发送UECapabilityInformationSidelink消息。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中的任一项所述的方法。
PCT/CN2022/119055 2021-09-16 2022-09-15 用户设备能力交互的方法及用户设备 WO2023040969A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111090219.1A CN115835181A (zh) 2021-09-16 2021-09-16 用户设备能力交互的方法及用户设备
CN202111090219.1 2021-09-16

Publications (1)

Publication Number Publication Date
WO2023040969A1 true WO2023040969A1 (zh) 2023-03-23

Family

ID=85515595

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/119055 WO2023040969A1 (zh) 2021-09-16 2022-09-15 用户设备能力交互的方法及用户设备

Country Status (2)

Country Link
CN (1) CN115835181A (zh)
WO (1) WO2023040969A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105228218A (zh) * 2015-09-25 2016-01-06 宇龙计算机通信科技(深圳)有限公司 D2d通信中远端终端的准入控制方法及相关装置
CN111800820A (zh) * 2019-08-21 2020-10-20 维沃移动通信有限公司 一种侧链路中继处理的方法和用户设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105228218A (zh) * 2015-09-25 2016-01-06 宇龙计算机通信科技(深圳)有限公司 D2d通信中远端终端的准入控制方法及相关装置
CN111800820A (zh) * 2019-08-21 2020-10-20 维沃移动通信有限公司 一种侧链路中继处理的方法和用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Corrections on sidelink UE capabilities", 3GPP DRAFT; R2-2010941, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic Meeting; 20201102 - 20201113, 16 November 2020 (2020-11-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052255556 *
SAMSUNG ELECTRONICS, OPPO: "Correction to UE actions related to reception of the UECapabilityEnquirySidelink", 3GPP DRAFT; R2-2100923, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973996 *

Also Published As

Publication number Publication date
CN115835181A (zh) 2023-03-21

Similar Documents

Publication Publication Date Title
CN106165479B (zh) 用于机器类型通信的移动性管理实体、用户设备及方法
US9313812B2 (en) User equipment and evolved node-B supporting machine type communication and small data communication
WO2021077434A1 (zh) 一种通信方法及装置
US11395256B2 (en) Communication method, device, and system
WO2018010694A1 (zh) 发送和接收系统消息的方法、基站和用户设备
WO2022001495A1 (zh) 状态转换方法及链接态mtch的指示方法、装置、存储介质、终端、基站
US11019462B2 (en) User equipment, base station, and related methods
WO2022083444A1 (zh) 系统信息获取方法及用户设备
JP2022501951A (ja) Ｐｄｃｐ重複の設定方法及び端末機器
WO2022078384A1 (zh) 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
WO2022078328A1 (zh) 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
KR102381375B1 (ko) 이동통신 시스템에서 Cellular IoT 서비스를 제공하는 방법 및 장치
WO2023040969A1 (zh) 用户设备能力交互的方法及用户设备
WO2022135336A1 (zh) QoS分割和携带方法、对象侧QoS确定方法及UE
WO2022127492A1 (zh) 寻呼方法及装置、存储介质、终端、基站
WO2022237602A1 (zh) QoE测量报告的上报方法、设备、装置及存储介质
US20230239901A1 (en) Method for receiving multicast service data, terminal device, and non-transitory computer-readable storage medium
WO2022193134A1 (zh) 寻呼监听方法、装置、设备及存储介质
WO2022233300A1 (zh) 由用户设备执行的方法以及用户设备
WO2023125294A1 (zh) 由用户设备执行的方法以及用户设备
WO2023131231A1 (zh) 由用户设备执行的方法以及用户设备
WO2023098865A1 (zh) 由用户设备执行的方法及用户设备
WO2024067602A1 (zh) 由用户设备执行的方法以及用户设备
WO2023274225A1 (zh) 由用户设备执行的方法以及用户设备
WO2023103950A1 (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: 22869337

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE