Managing sidelink and non-sidelink information

Abstract

To manage sidelink information and non-sidelink information, a user equipment obtains, by processing hardware in a user equipment communicating with a radio access network (RAN), a first set of information (504A) for sidelink communications with another user equipment, and obtains, by the processing hardware, a second set of information (504B) for non-sidelink communications. The user equipment transmits, by the processing hardware, a first message (1010A) including the first set of information to the RAN, and transmits, by the processing hardware, a second message (1010B) including the second set of information to the RAN, the first message and the second message being separate messages.

Description

[0001] This application is a divisional application of the patent application filed on July 1, 2021, with application number 202180006470.7 and invention title "Management Sidelink Information and Non-Sidelink Information".

[0002] Cross-references to related applications

[0003] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 062,073, filed August 6, 2020, entitled “Managing Sidelink and Non-Sidelink Information,” the entire disclosure of which is expressly incorporated herein by reference. Technical Field

[0004] This disclosure generally relates to wireless communication, and more specifically to sidelink and non-sidelink communication operations. Background Technology

[0005] This background description is provided for the purpose of presenting the background of this disclosure in general. The work of the currently named inventors (within the scope described in this background section) and aspects of the description that may not otherwise conform to the prior art at the time of filing are neither explicitly nor implicitly acknowledged as prior art in contrast to this disclosure.

[0006] In telecommunications systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as user plane data delivery, encryption, and integrity protection. For example, the PDCP layer, defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS36.323) and New Radio (NR) (see 3GPP specification TS38.323), provides the ordering of Protocol Data Units (PDUs) in the uplink direction (from the User Equipment (UE) to the base station) and the downlink direction (from the base station to the UE). Furthermore, the PDCP sublayer provides Signaling Radio Bearer (SRB) services to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides Data Radio Bearer (DRB) services to the Serving Data Adaptation Protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IP) layer, Ethernet layer, and Internet Control Message Protocol (ICMP) layer. Generally, the UE and base station can use SRBs to exchange RRC messages and Non-Access Stratum (NAS) messages, and can use DRBs to transmit data on the user plane.

[0007] UEs can use various types of SRBs and DRBs. When operating in dual connectivity (DC), the cell associated with the base station operating as the primary node (MN) defines the primary cell group (MCG), and the cell associated with the base station operating as the secondary node (SN) defines the secondary cell group (SCG). The so-called SRB1 resource carries RRC messages, which in some cases include NAS messages on the dedicated control channel (DCCH), while the SRB2 resource supports RRC messages or NAS messages including measurement information input to the computer, also on the DCCH, but the SRB2 resource has a lower priority than the SRB1 resource. More generally, SRB1 and SRB2 resources allow the UE and MN to exchange MN-related RRC messages as well as SN-related embedded RRC messages, and can also be called MCG SRBs. SRB3 resources allow the UE and SN to exchange SN-related RRC messages, and can also be called SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via the lower-layer resources of the MN and SN. Furthermore, a DRB that terminates at MN and uses only the lower-level resources of MN can be called an MCG DRB, a DRB that terminates at SN and uses only the lower-level resources of SN can be called an SCG DRB, and a DRB that terminates at MCG but uses the lower-level resources of MN, SN, or both MN and SN can be called a split DRB.

[0008] In some scenarios, a UE can simultaneously utilize the resources of multiple nodes (e.g., base stations or components of a distributed base station) in a backhaul-interconnected radio access network (RAN). This type of connection is called Multiple Radio Dual Connectivity (MR-DC) when these network nodes support different radio access technologies (RATs). When the UE operates in an MR-DC, one base station operates as the MN covering the primary cell (PCell), while another base station operates as the SN covering the primary secondary cell (PSCell). The UE communicates with both the MN (via the PCell) and the SN (via the PSCell). In other scenarios, the UE utilizes the resources of one base station at a time. One base station and / or the UE determines that the UE should establish a radio connection with another base station. For example, one base station might determine to hand over the UE to a second base station and initiate a handover procedure. In other scenarios, the UE can simultaneously utilize the resources of RAN nodes (e.g., single base stations or components of a distributed base station) interconnected via backhaul.

[0009] A UE in the RRC_CONNECTED state communicates with the base station of the Radio Access Network (RAN) using a single connection. Alternatively, a UE in the RRC_CONNECTED state communicates with both the primary and secondary base stations of the RAN using a dual connection.

[0010] When the UE determines to send a measurement report for sidelink communication, it includes a first measurement result related to the sidelink communication in the measurement report. According to 3GPP TS 38.331 or 36.331 v16.1.0, the UE also includes a second measurement result related to downlink or uplink (DL / UL) communication in the measurement report. The UE then transmits the measurement report to the RAN. When the measurement report contains both the first and second measurement results, the UE clears, deletes, or releases both the first and second measurement results to prevent the UE from sending duplicate or obsolete measurement results to the RAN. However, the UE evaluates the sidelink-related measurement results differently from the measurement results related to DL / UL communication. That is, the UE evaluates the DL / UL communication-related measurement results against one or more thresholds configured for the RAN. Clearing the DL / UL communication-related measurement results may cause the evaluation to restart, which may result in the UE spending more time reporting measurement events to the RAN.

[0011] A UE in an (NG)EN-DC with both the MeNB and SgNB can transmit a MeasurementReport message for sidelink communication to the SgNB according to Section 5.5.5.1 of 3GPP TS 38.331 v 16.1.0 (2020-07). Given that the SgNB does not expect to receive MeasurementReport messages for sidelink communication from the UE on SRB3, the SgNB may determine a protocol error due to receiving an invalid MeasurementReport message. In response to the protocol error, the SgNB can initiate an SNRelease procedure with the MeNB to disconnect from the UE. As a result of the SN Release procedure, the MeNB sends an RRCConnectionReconfiguration message to the UE to release the (NG)EN-DC. The UE responds to the RRCConnectionReconfiguration message and switches to single connectivity, thus preventing the UE from benefiting from the higher data rates offered by the SgNB in ​​dual connectivity.

[0012] In some scenarios, according to Section 5.7.4.3 of 3GPP TS 38.331 v16.1.0 (2020-07), a UE in an (NG)EN-DC with both the MeNB and SgNB can transmit a UEAssistanceInformation message for sidelink communication to the SgNB via SRB3, and can also transmit a MeasurementReport message to the SgNB. Given that the SgNB does not expect to receive the UEAssistanceInformation message for sidelink communication from the UE on SRB3, the SgNB may generate a protocol error due to receiving an invalid UEAssistanceInformation message. In response to the protocol error, the SgNB can initiate an SN Release procedure with the MeNB to disconnect from the UE. As a result of the SN Release procedure, the MeNB sends an RRCConnectionReconfiguration message to the UE to release the (NG)EN-DC. Therefore, the UE switches to single connectivity in response to the RRCConnectionReconfiguration message, and the UE does not benefit from the higher data rate offered by the SgNB in ​​dual connectivity. Summary of the Invention

[0013] An example embodiment of these technologies is a method for managing sidelink and non-sidelink information in a user equipment. The method can be executed by processing hardware and includes obtaining, by the processing hardware in the user equipment communicating with a radio access network (RAN), a first set of information for sidelink communication with another user equipment, and obtaining, by the processing hardware, a second set of information for non-sidelink communication. The method further includes transmitting, by the processing hardware, a first message including the first set of information to the RAN, and a second message including the second set of information to the RAN, wherein the first and second messages are separate messages.

[0014] Another example embodiment of these technologies is a user equipment that includes processing hardware and is configured to perform the methods described above.

[0015] Another example embodiment of these technologies is a method for managing sidelink and non-sidelink information in a base station. The method can be executed by processing hardware and includes receiving a first instance of a message having a message format and a first payload having a first payload type by the processing hardware in the base station communicating with a user equipment, and receiving a second instance of the message having the same message format as the first instance of the message and a second payload having a second payload type. In response to determining that the first payload and the second payload have different payload types, the method includes retaining the first instance of the message by the processing hardware.

[0016] Another example embodiment of these technologies is a base station that includes processing hardware and is configured to implement the methods described above. Attached Figure Description

[0017] Figure 1A This is a block diagram of an example system in which the RAN and UE can implement the techniques disclosed herein for managing sidelink auxiliary information reporting;

[0018] Figure 1B This is a block diagram of an example base station, in which centralized units (CUs) and distributed units (DUs) can be located... Figure 1A Operating within the system;

[0019] Figure 2A This is a block diagram of an example protocol stack. Based on this protocol stack, Figure 1A The UE can be with Figure 1A Communicate with base stations;

[0020] Figure 2B This is a block diagram of an example protocol stack. Based on this protocol stack, Figure 1A The UE can directly interact with Figure 1A Communicate with another UE;

[0021] Figure 3 This is a message passing diagram for an example scenario, in which the UE transmits separate measurement reports to the RAN, including sidelink information and non-sidelink information.

[0022] Figure 4A This is a message passing diagram for an example scenario. In this scenario, the UE in dual connectivity (DC) transmits an RRC message containing sidelink information from the first container message to the master node (MN), and transmits an RRC message containing non-sidelink information from the second container message to the MN.

[0023] Figure 4BHere is a message passing diagram for another example scenario, in which the UE in dual connectivity (DC) transmits an RRC message including sidelink information to the MN and an RRC message including non-sidelink information to the secondary node (SN);

[0024] Figure 5A This is a flowchart of an example method for obtaining measurement results, including side-link information and non-side-link information, and transmitting the measurement results to the RAN, which can be implemented in the UE of this disclosure;

[0025] Figure 5B This is a flowchart of another example method for obtaining measurement results, including side-link information and non-side-link information, and transmitting the measurement results to the RAN, which can be implemented in the UE of this disclosure;

[0026] Figure 6 This is a flowchart of yet another example method for obtaining measurement results, including side-link information and non-side-link information, and transmitting the measurement results to the RAN, which can be implemented in the UE of this disclosure;

[0027] Figure 7 This is a flowchart of another example method for obtaining measurement results, including side-link information and non-side-link information, and transmitting the measurement results to the RAN, which can be implemented in the UE of this disclosure;

[0028] Figure 8 This is a flowchart of an example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting the sidelink information and non-sidelink information to a RAN operating in an MR-DC and including an MN and an SN, which can be implemented in a UE of this disclosure;

[0029] Figure 9 This is a flowchart of another example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting the sidelink information and non-sidelink information to a RAN operating in an MR-DC and including an MN and an SN, which can be implemented in the UE of this disclosure;

[0030] Figure 10A This is a flowchart of an example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting the information to the RAN, which can be implemented in the UE of this disclosure;

[0031] Figure 10B This is a flowchart of another example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting said information to the RAN, which can be implemented in the UE of this disclosure;

[0032] Figure 11 This is a flowchart of yet another example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting said information to the RAN, which can be implemented in the UE of this disclosure;

[0033] Figure 12 This is a flowchart of another example method for obtaining information for sidelink communication and information for non-sidelink communication and transmitting said information to the RAN, a method that can be implemented in the UE of this disclosure; and

[0034] Figure 13 This is a flowchart of an example method for receiving information from a UE regarding sidelink communication and information regarding non-sidelink communication, which can be implemented in a base station of this disclosure. Detailed Implementation

[0035] Figure 1A An example wireless communication system 100 capable of implementing the DAPS operation techniques of this disclosure is depicted. The wireless communication system 100 includes UEs 102A and 102B and base stations 104 and 106 connected to a core network (CN) 110. For example, base stations 104 and 106 can be any one or more suitable types of base stations, such as evolved Node B (eNB), next-generation eNB (ng-eNB), or 5G Node B (gNB). As a more specific example, base station 104 can be an eNB or a gNB, and base station 106 can be a gNB. For the sake of simplicity in the following description, unless otherwise specified, UE 102 can refer to UE 102A or UE 102B, or both UE 102A and UE 102B.

[0036] Base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 partially overlap, allowing UE 102 to communicate with both base station 104 and base station 106 (or to detect or measure signals from base station 106, etc.). For example, this overlap enables UE 102A to handover between cells (e.g., from cell 124 to cell 126) or base stations (e.g., from base station 104 to base station 106) before experiencing a radio link failure. Furthermore, this overlap allows for various dual connectivity (DC) scenarios discussed below.

[0037] More specifically, when UE 102 is in DC with base stations 104 and 106, base station 104 operates as a primary eNB (MeNB), primary ng-eNB (Mng-eNB), or primary gNB (MgNB), and base station 106 operates as a secondary gNB (SgNB) or secondary ng-eNB (Sng-eNB). In implementations and scenarios where UE 102 and base station 104 are in SC but can operate in DC, base station 104 operates as a MeNB, Mng-eNB, or MgNB, and base station 106 operates as a candidate SgNB (C-SgNB) or candidate Sng-eNB (C-Sng-eNB). Although various scenarios are described below where base station 104 operates as MN and base station 106 operates as SN, either base station 104 or 106 can typically operate as MN or SN in different scenarios. Therefore, in some implementations, base station 104 and base station 106 can implement similar groups of functions and each support MN and SN operations.

[0038] In operation, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to MN (e.g., base station 104) or SN (e.g., base station 106). For example, after handover to base station 106, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to base station 106. When communicating on radio bearers, in the uplink (from UE 102 to the base station) and / or downlink (from the base station to UE 102) directions, UE 102 may apply one or more security keys.

[0039] In some scenarios, UE 102A, in the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state, can perform sidelink communication with UE 102B (e.g., for V2X or proximity services). Sidelink communication can be NR or LTE sidelink communication and / or V2X sidelink communication. When UE 102 is within the coverage area of ​​RAN 105, RAN 105 can configure and control sidelink communication via dedicated signaling (e.g., RRC reconfiguration messages) or broadcast system information (e.g., one or more system information blocks). When UE 102 is in the RRC_CONNECTED state, UE 102 can send a SidelinkUEInformation message to RAN 105 to request or release sidelink resources for sidelink communication and / or report QoS information for each destination in the sidelink communication. For example, after RAN 105 receives the SidelinkUEInformation message, RAN 105 provides UE 102 with an RRC reconfiguration message to provide the UE with dedicated sidelink configuration. RRC reconfiguration may include SLRB configuration for NR sidelink communication, as well as sidelink scheduling configuration or resource pool configuration. If UE 102 has already received the sidelink radio bearer (SLRB) configuration via system information, UE 102 should continue to use that configuration to perform sidelink data transmission and reception until a new configuration is received in the RRC reconfiguration message transmitted to UE 102 via RAN 105. During handover, UE 102 performs sidelink communication (e.g., transmission and / or reception) based on the receive resource pool of the target cell and / or the configured sidelink grant type 1 or abnormal transmission resource pool as provided in the handover command message. RAN 105 may also configure the UE to report measurement and channel busy rate (CRB) and / or location information via the RRC reconfiguration message transmitted to UE 102 via RAN 105. RAN 105 may also configure UE 102 with grant assistance information to provide sidelink communication configuration via the RRC reconfiguration message transmitted to UE 105.

[0040] Base station 104 includes processing hardware 130, which may include one or more general-purpose processors (e.g., central processing unit (CPU)) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. Figure 1AIn the example implementation, the processing hardware 130 includes a base station sidelink controller 132 configured to manage or control sidelink configurations and procedures. For example, the base station sidelink controller 132 may be configured to support RRC messaging associated with sidelink configurations and procedures. The processing hardware 130 includes a base station Uu link controller 134 configured to manage or control the Uu link (i.e., the link between UE 102 and base station 104). For example, the base station Uu link controller 134 may be configured to support RRC messaging associated with RRC procedures, manage or control radio resources for communication between UE 102 and base station 104, and / or support necessary operations when base station 104 operates as an MN, as discussed below.

[0041] Base station 106 includes processing hardware 140, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. Figure 1A In the example implementation, the processing hardware 140 includes a base station sidelink controller 142 configured to manage or control sidelink configurations and procedures. For example, the base station sidelink controller 142 may be configured to support RRC messaging associated with sidelink configurations and procedures. The processing hardware 140 includes a base station Uu link controller 144 configured to manage or control the Uu link (i.e., the link between UE 102 and base station 106). For example, the base station Uu link controller 144 may be configured to support RRC messaging associated with RRC procedures, manage or control radio resources for communication between UE 102 and base station 106, and / or support necessary operations when base station 106 operates as an MN or SN, as discussed below.

[0042] UE 102 includes processing hardware 150, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. Figure 1AThe processing hardware 150 in the example implementation includes a UE sidelink controller 152 configured to manage or control sidelink configurations and procedures. For example, the UE sidelink controller 152 may be configured to support RRC messaging associated with sidelink configurations and procedures. The processing hardware 150 includes a UE Uu link controller 154 configured to manage or control the Uu link (i.e., the link between UE 102 and RAN 105) based on configuration parameters received from RAN 105. For example, the UE Uu link controller 152 may be configured to support RRC messaging associated with RRC procedures for managing or controlling radio resources according to any of the implementations discussed below.

[0043] CN 110 can be either an Evolved Packet Core (EPC) 111 or a Generation 5 Core (5GC) 160, both of which are... Figure 1A The following description is provided. Base station 104 may be an eNB supporting an S1 interface for communication with EPC 111, an ng-eNB supporting an NG interface for communication with 5GC 160, or a gNB supporting both an NR radio interface and an NG interface for communication with 5GC 160. Base station 106 may be an EN-DC gNB (en-gNB) with an S1 interface to EPC 111, an en-gNB not connected to EPC 111, a gNB supporting both an NR radio interface and an NG interface to 5GC 160, or an ng-eNB supporting both an EUTRA radio interface and an NG interface to 5GC 160. Base stations 104 and 106 may support X2 or Xn interfaces to directly exchange messages with each other during the scenarios discussed below.

[0044] In addition to other components, EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network (PDN) Gateway (PGW) 116. SGW 112 and / or PGW 116 are typically configured to transmit user plane packets related to audio calls, video calls, internet traffic, etc., and MME 114 is configured to manage authentication, registration, paging, and other related functions. 5GC 160 includes a User Plane Function (UPF) 162 and Access and Mobility Management (AMF) 164 and / or Session Management Function (SMF) 166. UPF 162 is typically configured to transmit user plane packets related to audio calls, video calls, internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging, and other related functions, and SMF 166 is configured to manage PDU sessions.

[0045] Typically, the wireless communication network 100 may include any suitable number of base stations supporting NR cells and / or EUTRA cells. More specifically, the EPC 111 or 5GC 160 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells. Although the following examples specifically relate to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies, such as sixth-generation (6G) radio access and / or 6G core networks or 5G NR-6G DC, for example.

[0046] In different configurations or scenarios of the wireless communication system 100, base station 104 can operate as a MeNB, Mng-eNB, or MgNB, and base station 106 can operate as a MeNB, Mng-eNB, MgNB, SgNB, or Sng-eNB. UE 102 can communicate with base station 104 and base station 106 via the same radio access technology (RAT) (such as EUTRA or NR) or via different RATs.

[0047] When base station 104 is a MeNB and base station 106 is an SgNB, UE 102 can be in an EUTRA-NR DC (EN-DC) with MeNB 104 and SgNB 106. When base station 104 is a Mng-eNB and base station 106 is an SgNB, UE 102 can be in a Next Generation (NG) EUTRA-NR DC (NGEN-DC) with Mng-eNB 104 and SgNB 106. When base station 104 is a MgNB and base station 106 is an SgNB, UE 102 can be in an NR-NR DC (NR-DC) with MgNB 104 and SgNB 106. When base station 104 is a MgNB and base station 106 is a Sng-eNB, UE 102 can be in an NR-EUTRA DC (NE-DC) with MgNB 104 and Sng-eNB 106.

[0048] Figure 1B An example distributed implementation of one or more of base stations 104 and 106 is depicted. In this implementation, base station 104 or 106 includes a centralized unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on said one or more general-purpose processors, and / or dedicated processing units. For example, CU 172 may include... Figure 1AThe processing hardware 130 or 140. When the base station (e.g., base station 106) operates as an SN, the processing hardware may include a base station RRC controller (e.g., RRC controller 142) configured to manage or control one or more RRC configurations and / or RRC procedures.

[0049] Each of DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. For example, when a base station (e.g., base station 106) operates as an MN or SN, the processing hardware may include a MAC controller configured to manage or control one or more Media Access Control (MAC) operations or procedures (e.g., random access procedures), and an RLC controller configured to manage or control one or more Radio Link Control (RLC) operations or procedures. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0050] Figure 2A An example protocol stack 200 is illustrated in a simplified manner, according to which UE 102 can communicate with eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).

[0051] In example stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which in turn provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A then provides the RLC channel to the EUTRA PDCP sublayer 208, and in some cases, also provides the RLC channel to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides the RLC channel to the NR PDCP sublayer 210. In some implementations, UE 102 supports, for example... Figure 2A The EUTRA and NR stacks shown are designed to support handover between EUTRA and NR base stations and / or support DC on both the EUTRA and NR interfaces. Furthermore, as... Figure 2A As shown, UE 102 can support NR PDCP 210 layering on EUTRA RLC 206A.

[0052] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on PDCP layers 208 or 210) receive packets that can be referred to as Service Data Units (SDUs) and (e.g., to RLC layers 206A or 206B) output packets that can be referred to as Protocol Data Units (PDUs). Unless the difference between SDU and PDU is relevant, this disclosure refers to both SDU and PDU as "packets" for simplicity.

[0053] For example, on the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide SRBs to exchange RRC messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide DRBs to support data exchange.

[0054] In a scenario where UE 102 operates in EUTRA / NR DC (EN-DC), with base station 104 operating as a MeNB and base station 106 operating as an SgNB, wireless communication system 100 can provide UE 102 with a bearer terminating at MN using EUTRA PDCP sublayer 208, or a bearer terminating at MN using NR PDCP sublayer 210. In various scenarios, wireless communication system 100 can also provide UE 102 with a bearer terminating at SN, which uses only NR PDCP sublayer 210. The bearer terminating at MN can be an MCG bearer or a split bearer. The bearer terminating at SN can be an SCG bearer or a split bearer. The bearer terminating at MN can be an SRB (e.g., SRB1 or SRB2) or a DRB. The bearer terminating at SN can be an SRB or a DRB.

[0055] Figure 2B An example protocol stack 250 for sidelink communication between UE 102A and UE 102B is illustrated in a simplified manner.

[0056] In example stack 250, physical layer (PHY) 252 provides a transport channel to MAC sublayer 254, which in turn provides a logical channel to RLC sublayer 256. RLC sublayer 256, in turn, provides an RLC channel to PDCP sublayer 258. In some implementations, example stack 250 may conform to EUTRA or NR.

[0057] PDCP sublayer 258 (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on PDCP sublayer 258) receives packets that can be referred to as Service Data Units (SDUs) and (e.g., outputs packets that can be referred to as Protocol Data Units (PDUs) to RLC sublayer 256. Unless the difference between SDU and PDU is relevant, this disclosure refers to both SDU and PDU as "packets" for simplicity. For example, on the control plane, PDCP sublayer 258 may provide one or more sidelink SRBs to exchange RRC messages between UE 102A and UE 102B. On the user plane, PDCP sublayer 258 may provide one or more sidelink DRBs to support data exchange between UE 102A and UE 102B.

[0058] First refer to Figure 3 In scenario 300, initially, UE 102 communicates with RAN 105 302. In some embodiments, UE 102A communicates data with base station 104 of RAN 105 302. In other embodiments, base station 104 of RAN 105 includes, for example... Figure 1B The DU and CU are shown in the diagram. UE 102A communicates 302 data via the DU and CU. In some other embodiments, UE 102 communicates 302 data with base stations 104 and 106 of RAN 105, wherein one of base stations 104 and 106 can operate as an MN and the other as an SN. In some other embodiments, such as Figure 1B As shown, the base station 104 of RAN 105 includes two DUs and one CU, where one of the two DUs can operate as a primary DU and the other as a secondary DU. UE 102 can communicate 302 data with CU 172 via the two DUs. The data described above may include DL PDUs, UL PDUs, control signals, and / or messages described below.

[0059] During communication 302 with RAN 105, UE 102A obtains 304 one or more first measurement results of sidelink communication and one or more second measurement results of non-sidelink communication (i.e., DL / UL communication). Then, UE 102A transmits 306 a first Measurement Report message including one or more of the first measurement results to RAN 105 (e.g., base station 104 or base station 106), and transmits 308 a second Measurement Report message including one or more of the second measurement results to RAN 105 (e.g., base station 104 or base station 106).

[0060] In some implementations, UE 102A excludes one or more non-sidelink measurement results (e.g., one or more second measurement results) from the first Measurement Report message. Therefore, UE 102A continues to evaluate the non-sidelink measurement report by not including one or more non-sidelink measurement results (e.g., one or more second measurement results) in the first Measurement Report message.

[0061] In other implementations, UE 102A includes one or more non-sidelink measurement results (e.g., at least a portion of one or more second measurement results) in the first Measurement Report message. In this case, UE 102A avoids clearing the one or more non-sidelink measurement results or the original measurement results used to obtain the one or more non-sidelink measurement results. Therefore, UE 102A does not stop evaluating the non-sidelink measurement report simply because the first Measurement Report message includes one or more non-sidelink measurement results.

[0062] In some implementations, UE 102A excludes one or more sidelink measurement results (e.g., one or more first measurement results) from the second Measurement Report message. Therefore, UE 102A continues to evaluate the sidelink measurement report by not including one or more sidelink measurement results in the second Measurement Report message.

[0063] In other implementations, UE 102A includes one or more sidelink measurement results (e.g., at least a portion of one or more first measurement results) in the second Measurement Report message. In this case, UE 102A avoids clearing the one or more sidelink measurement results or the original measurement results used to obtain the one or more sidelink measurement results. Therefore, UE 102A does not stop evaluating the sidelink measurement report simply because the second Measurement Report message includes one or more sidelink measurement results.

[0064] In some implementations, UE 102A performs sidelink communication with UE 102B while communicating with RAN 105 302. During sidelink communication, UE 102A may transmit packets to or receive packets from UE 102B. To obtain one or more first measurement results, UE 102A may measure the sidelink carrier frequency on which UE 102A performs sidelink communication with UE 102B. In some implementations, UE 102A sends an RRC message (e.g., SidelinkUEInformation) to request or release sidelink resources and / or report QoS information for the sidelink communication. For example, the RRC message may include frequency information indicating the sidelink carrier frequency on which UE 102A is interested in performing sidelink communication. Upon receiving an RRC message requesting sidelink resources and / or QoS information reporting sidelink communication, RAN 105 may transmit a first measurement configuration to UE 102A, configuring UE 102A to measure the sidelink carrier frequency. UE 102A measures the sidelink carrier frequency according to the first measurement configuration to obtain one or more first measurement results.

[0065] In some implementations, RAN 105 may transmit a second measurement configuration to UE 102A, which configures UE 102A to measure the downlink (DL) carrier frequency. UE 102A measures the DL carrier frequency according to the second measurement configuration to obtain one or more second measurement results.

[0066] In some implementations, RAN 105 may transmit at least one RRC message to UE 102A, including a first measurement configuration and / or a second measurement configuration. In response to each of the at least one RRC message, UE 102A may transmit an RRC response message to RAN 105. The RRC message and the RRC response message may be an RRC reconfiguration message (e.g., an RRCReconfiguration or RRCConnectionReconfiguration message) and an RRC reconfiguration completion message (e.g., an RRCReconfigurationComplete or RRCConnectionReconfigurationComplete message), respectively.

[0067] In some embodiments, one or more first measurement results or sidelink measurement results may include or indicate one or more sidelink reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indication (RSSI), and / or signal-to-noise and interference ratio (SINR). In other embodiments, one or more first measurement results or sidelink measurement results may include or indicate one or more channel busy rate (CBR) values. In some embodiments, one or more second measurement results or non-sidelink measurement results may include or indicate one or more DL / UL RSRP, RSRQ, RSSI, and / or SINR values.

[0068] In some implementations, UE 102A transmits the 306 Measurement Report message without using the RRC container message that includes the Measurement Report message. In other implementations, UE 102A may transmit the 306 ULInformationTransferIRAT message that includes the Measurement Report message, as for... Figure 4A As described above. In some implementations, UE 102A may transmit a ULInformationTransferMRDC message including a Measurement Report message, as described above. Figure 4A As described above. In other embodiments, UE 102A transmits the 308 Measurement Report message without using the RRC container message that includes the Measurement Report message, such as for... Figure 4B As stated above.

[0069] Next reference Figure 4A In scenario 400A, base station 104 operates as the MN of the first RAT, and base station 106 operates as the SN of the second RAT. Initially, UE 102A communicates 402A data with MN 104 and SN 106. The data may include DL PDUs, UL PDUs, control signals, and / or messages described below.

[0070] Subsequently, UE 102A determines that 404A sends an RRC message containing the second RAT. UE 102A determines whether the 406A RRC message includes information regarding sidelink communication. If the RRC message includes information regarding sidelink communication, UE 102A transmits a 408A ULInformationTransferIRAT message (also referred to herein as the "first container message") containing the RRC message to MN 104 via a first SRB (e.g., SRB1). MN 104 can then send a 410A SNModification Request message containing the RRC message to SN 106. If the RRC message does not include information regarding sidelink communication, UE 102A transmits a 412A ULInformationTransferMRDC message (also referred to herein as the "second container message," which differs from the first container message) containing the RRC message to MN 104 via the first SRB. MN 104 can then send a 414A RRC Transfer message containing the RRC message to SN 106. If the second SRB (e.g., SRB3) between UE 102A and SN is unavailable, UE 102A transmits a ULInformationTransferMRDC message, including an RRC message, to MN 104 via the first SRB. The second SRB may be unavailable because UE 102A does not support it, RAN 105 (i.e., MN 104 or SN 106) has not configured the second SRB for UE 102A, or UE 102A has suspended the second SRB.

[0071] In some implementations, the format of the RRC message has been defined to optionally include first information (e.g., one or more information elements) for sidelink communication of the second RAT, and to include second information (e.g., one or more information elements) for non-sidelink communication of the second RAT.

[0072] In some implementations, the RRC message is a Measurement Report message, the first information of which includes measurement results of one or more sidelink communications, and the second information includes measurement results of one or more non-sidelink communications, such as for... Figure 3 As stated above.

[0073] In other implementations, the RRC message is a UEAssistanceInformation message, and the first information includes configured authorization assistance information. In such implementations, the second information includes information about enabling or disabling power saving, information about temporarily reduced (one or more) capabilities or releasing temporarily reduced (one or more) capabilities, overheat assistance information or information indicating that the overheating situation has disappeared, information about experiencing an in-device coexistence (IDC) problem or information indicating that the IDC problem has disappeared, and / or information about preferred configurations (e.g., preferred DRX configuration, preferred maximum aggregation bandwidth, preferred maximum number of component carriers (CCs), preferred maximum number of multiple-input multiple-output (MIMO) layers, preferred minimum scheduling offset, and / or preferred RRC state).

[0074] In some scenarios and implementations, UE 102A does not include the second information in the RRC message at event 408A. Alternatively, if UE 102 determines at event 404A to send the second information to RAN 105 (i.e., to MN 104 or via MN 104 to SN 106), then UE 102A may include the second information in the RRC message at event 408A.

[0075] In some scenarios and implementations, if UE 102 has available first and second information at event 404A, UE 102A can generate a first instance of an RRC message including the first information and a second instance of an RRC message including the second information. Both instances of the RRC message can use the same message format (e.g., MeasurementReport message format). UE 102A then transmits a ULInformationTransferIRAT message including the first instance of the RRC message, similar to event 408A, and a ULInformationTransferMRDC message including the second instance of the RRC message, similar to event 412A. When RAN 105 receives the first instance of the RRC message in the ULInformationTransferIRAT message, or if RAN 105 receives the first instance of the RRC message in the ULInformationTransferIRAT message, RAN 105 can identify and process the first instance of the RRC message for sidelink communication. When RAN 105 receives a second instance of an RRC message in a ULInformationTransferIRAT message, or if RAN 105 receives a second instance of an RRC message in a ULInformationTransferIRAT message, RAN 105 can identify and process the second instance of an RRC message for non-sidelink communication.

[0076] In other scenarios and implementations, if UE 102A has available first and second information at event 404A, UE 102A can include both the first and second information in the RRC message. Then, UE 102A transmits a ULInformationTransferIRAT message including the RRC message, similar to event 408A. When RAN 105 receives the RRC message in the ULInformationTransferIRAT message, or if RAN 105 receives the RRC message in the ULInformationTransferIRAT message, RAN 105 can identify and process the first information for sidelink communication and identify and process the second information for non-sidelink communication.

[0077] In some implementations, UE 102A can detect different triggers or conditions being met, which makes UE 102A have first and second information available at event 404A.

[0078] In some implementations, the first RAT is EUTRA and the second RAT is NR, and the RRC message is an NR RRC message that includes information for NR sidelink communication. For example, the NR RRC message is a SidelinkUEInformationNR, UEAssistanceInformation, or Measurement Report message conforming to 3GPP specification 38.331. In other implementations, the first RAT is NR and the second RAT is EUTRA, and the RRC message is an EUTRA RRC message that includes information for EUTRA sidelink communication. For example, the EUTRA RRC message is a SidelinkUEInformation, UEAssistanceInformation, or Measurement Report message conforming to 3GPP specification 36.331.

[0079] In some implementations, UE 102A performs sidelink communication with UE 102B while communicating 402 with MN 104 and SN 106, such as for... Figure 3As described above, UE 102A can send an RRC message at event 408A or 412A while simultaneously performing sidelink communication. In this way, this embodiment supports maintaining (NG) EN-DC when UE 102A is also in sidelink communication. In other embodiments, UE 102A may not perform sidelink communication while communicating with MN and SN at event 402A. UE 102A can send an RRC message at event 408A or 412A without performing sidelink communication.

[0080] Figure 4B The illustration is similar to Figure 4A Scene 400A and Scene 400B. Events in Scene 400B, which are similar to those discussed above regarding Scene 400A, are labeled with similar reference numerals (e.g., ...). Figure 4A Event 402A corresponds to Figure 4B (Event 402B). Besides Figure 4B Apart from the differences shown and described below, any alternative implementations (e.g. for messaging and processing) discussed above regarding scenario 400A can be applied to scenario 400B.

[0081] If the RRC message does not include information about sidelink communication and a second SRB is available, then UE 102A transmits the RRC message 411B to SN 106, for example, via the second SRB (e.g., SRB3). In this case, UE 102A transmits the RRC message to the SN without using an RRC container message to include the RRC message.

[0082] Figure 5A This is a flowchart depicting a method 500A for transmitting Measurement Report messages, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 502A, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0083] At block 504A, the UE obtains measurement results(s) of sidelink communication(s) and measurement results(s) of non-sidelink communication(s) (e.g., in event 304). At block 506A, the UE determines to send a Measurement Report message for sidelink communication. At block 508A, in response to this determination, the UE includes the measurement results(s) of sidelink communication(s) in the Measurement Report message and excludes the measurement results(s) of non-sidelink communication(s) from the Measurement Report message (i.e., avoids including the measurement results(s) of non-sidelink communication(s) in the Measurement Report message or does not include the measurement results(s) of non-sidelink communication(s) in the Measurement Report message) (e.g., in events 306, 408A, 408B). At block 510A, the UE sends the Measurement Report message to the RAN (e.g., in events 306, 408A, 408B).

[0084] Figure 5B This is a flowchart depicting a method 500B for transmitting Measurement Report messages, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 502B, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0085] At block 504B, the UE obtains measurement results(s) of sidelink communication(s) and measurement results(s) of non-sidelink communication(s) (e.g., in event 304). At block 506B, the UE determines to send a Measurement Report message for non-sidelink communication. At block 508B, in response to this determination, the UE includes the measurement results(s) of non-sidelink communication(s) in the Measurement Report message and excludes the measurement results(s) of sidelink communication(s) from the Measurement Report message (i.e., avoids including the measurement results(s) of sidelink communication(s) in the Measurement Report message or does not include the measurement results(s) of sidelink communication(s) in the Measurement Report message) (e.g., in events 308, 412A, 411B). At block 510B, the UE sends the Measurement Report message to the RAN (e.g., in events 308, 412A, 411B).

[0086] The Measurement Report for sidelink communication, as described in Method 500A, can be a first measurement report, and the Measurement Report for non-sidelink communication, as described in Method 500B, can be a second measurement report. The UE can send the first and second measurement reports as separate messages to the RAN.

[0087] Figure 6 This is a flowchart depicting a method 600 for transmitting Measurement Report messages, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 602, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0088] At box 604, the UE obtains measurement results for one or more sidelink communications and one or more non-sidelink communications (e.g., in event 304). At box 606, the UE determines whether to send a Measurement Report message. At box 608, the UE determines whether the Measurement Report message is for sidelink communications.

[0089] If the Measurement Report message is for sidelink communication, then at box 610, the UE includes one or more measurement results of the sidelink communication in the Measurement Report message and excludes one or more measurement results of non-sidelink communication from the Measurement Report message (i.e., avoids including one or more measurement results of non-sidelink communication in the Measurement Report message or does not include one or more measurement results of non-sidelink communication in the Measurement Report message) (e.g., in events 306, 408A, 408B). If the Measurement Report message is not for sidelink communication, then at box 612, the UE includes one or more measurement results of non-sidelink communication in the Measurement Report message and excludes one or more measurement results of sidelink communication from the Measurement Report message (i.e., avoids including one or more measurement results of sidelink communication in the Measurement Report message or does not include one or more measurement results of sidelink communication in the Measurement Report message) (e.g., in events 308, 412A, 411B). At box 614, the UE sends a Measurement Report message to the RAN (e.g., in events 306, 408A, 408B, 308, 412A, 411B).

[0090] Figure 7 This is a flowchart depicting a method 700 for transmitting Measurement Report messages, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 702, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0091] At block 704, the UE obtains measurement results(s) of sidelink communication(s) and non-sidelink communication(s) (e.g., in event 304). At block 706, the UE determines to send a MeasurementReport message for sidelink communication. At block 708, in response to this determination, the UE includes the measurement results(s) of sidelink communication(s) and non-sidelink communication(s) in a first Measurement Report message (e.g., in events 306, 408A, 408B). At block 710, the UE avoids removing the measurement results(s) of non-sidelink communication(s). At block 712, the UE sends the first Measurement Report message to the RAN (e.g., in events 306, 408A, 408B).

[0092] In some implementations, the UE transmits a second Measurement Report message to the RAN after transmitting the first Measurement Report message, which includes measurement results (one or more) from non-sidelink communication. In other implementations, the UE transmits a second Measurement Report message after transmitting the first Measurement Report message, which includes measurement results (one or more) updated based on the measurement results (one or more) from non-sidelink communication and new measurements performed by the UE.

[0093] In some implementations, the UE continues to evaluate one or more measurement report triggering conditions based on measurement results from non-sidelink communication(s) or measurements updated according to measurement results from non-sidelink communication(s) and new measurements performed by the UE. If the UE detects that one or more measurement report triggering conditions are met, the UE transmits a second Measurement Report message to the RAN, as described above.

[0094] Figure 8 This is a flowchart depicting a method 800 for transmitting RRC messages in a DC, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 802, the UE (e.g., in an SC or DC) communicates with the MN (e.g., MN 104) of a first RAT and the SN (e.g., SN 106) of a second RAT (e.g., in events 402A, 402B).

[0095] At box 804, the UE generates an RRC message for the second RAT (e.g., in events 404A and 404B). At box 806, the UE determines whether the RRC message includes information about sidelink communication for the second RAT. If the RRC message does not include information about sidelink communication for the second RAT, then at box 808, the UE transmits a ULInformationTransferMRDC message including the RRC message to the MN (e.g., in event 412A) or transmits the RRC message to the SN (e.g., in event 411B).

[0096] If the RRC message includes information about sidelink communication for the second RAT, then at block 810, the UE transmits a ULInformationTransferIRAT message including the RRC message to the MN (e.g., in events 408A, 408B). At block 812, UE 102 determines whether the RRC message includes information about non-sidelink communication. If the RRC message includes information about non-sidelink communication for the second RAT, then at block 808, the UE transmits a ULInformationTransferMRDC message including the RRC message to the MN (e.g., in events 412A, 411B). If the RRC message does not include information about non-sidelink communication for the second RAT, then at block 814, the UE takes no further action.

[0097] Figure 9 This is a flowchart depicting a method 900 for transmitting RRC messages in a DC, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 902, the UE (e.g., in an SC or DC) communicates with the MN (e.g., MN 104) of a first RAT and the SN (e.g., SN 106) of a second RAT (e.g., in events 402A, 402B).

[0098] At box 904, the UE generates an RRC message for the second RAT (e.g., in events 404A and 404B). At box 906, the UE determines whether the RRC message includes information about sidelink communication for the second RAT. If the RRC message includes information about sidelink communication for the second RAT, then at box 908, the UE transmits a ULInformationTransferIRAT message including the RRC message to the MN via SRB1 (e.g., in events 408A and 408B).

[0099] If the RRC message does not include information about sidelink communication for the second RAT, then at box 910, the UE determines whether SRB3 is configured. If SRB3 is configured, then at box 912, the UE transmits the RRC message to the SN via SRB3 (e.g., in event 411B). If SRB3 is not configured, then at box 914, the UE transmits a ULInformationTransferMRDC message including the RRC message to the MN via SRB1 (e.g., in event 412A).

[0100] Such as about Figure 8 and Figure 9 Combination Figure 4A and Figure 4B As shown, the UE can use different container messages (e.g., ULInformationTransferIRAT message and ULInformationTransferMRDC message) to indicate whether the included RRC message includes information for sidelink communication.

[0101] Figure 10A This is a flowchart depicting a method 1000A for transmitting messages including information for sidelink communication, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 1002A, the UE (e.g., in SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0102] At box 1004A, the UE determines to send information for sidelink communication that can be included in a message (e.g., in event 404A). The information for sidelink communication can be measurement results or auxiliary information. The UE can determine to send the information for sidelink communication based on triggering conditions for sidelink communication. If the UE detects that the triggering conditions for sidelink communication are met, the UE determines to send the information for sidelink communication. The triggering condition can be a threshold for the measurement results of sidelink communication or any other suitable triggering condition.

[0103] At block 1006A, the UE detects that a trigger condition for sending information for non-sidelink communication has been met. The trigger condition may be a threshold for a measurement result of non-sidelink communication (such as a measurement result of DL / UL communication) or any other suitable trigger condition. Then, at block 1008A, the UE generates an instance of a message (such as an RRC message) that, in response to determining to send information for sidelink communication, includes the information for sidelink communication in the message and excludes the information for non-sidelink communication from the message (i.e., avoids including the information for non-sidelink communication in the message or does not include the information for non-sidelink communication in the message) (e.g., in events 306, 408A, 408B). At block 1010A, the UE sends the message to the RAN (e.g., in events 306, 408A, 408B).

[0104] Figure 10B This is a flowchart depicting a method 1000B for transmitting messages including information for non-sidelink communication, which can be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 1002B, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0105] At box 1004B, the UE determines to send information for non-sidelink communication that can be included in a message (e.g., in event 404A). The UE may determine to send information for non-sidelink communication based on triggering conditions for non-sidelink communication. If the UE detects that the triggering conditions for non-sidelink communication are met, the UE determines to send information for non-sidelink communication. The triggering condition may be a threshold of a measurement result of non-sidelink communication (such as a measurement result of DL / UL communication) or any other suitable triggering condition.

[0106] At box 1006B, the UE detects that a trigger condition for sending information for sidelink communication has been met. The trigger condition may be a threshold for a measurement result of the sidelink communication or any other suitable trigger condition. Then, at box 1008B, the UE generates an instance of a message (such as an RRC message) that, in response to determining that information for non-sidelink communication is to be sent, includes information for non-sidelink communication in the message and excludes information for sidelink communication from the message (i.e., avoids including information for sidelink communication in the message or does not include information for sidelink communication in the message) (e.g., in events 308, 412A, 411B). At box 1010B, the UE sends the message to the RAN (e.g., in events 308, 412A, 411B).

[0107] An instance of a message including sidelink communication, as described in method 1000A, can be a first instance of the message, and an instance of a message including non-sidelink communication, as described in method 1000B, can be a second instance of the message. Both instances of the message can use the same message format (e.g., the Measurement Report message format). The UE can send the first and second instances of the message as separate messages to the RAN.

[0108] Figure 11 This is a flowchart depicting a method 1100 for transmitting messages including information for sidelink or non-sidelink communication, which may be implemented by a UE (e.g., UE 102) of this disclosure. Initially, at block 1102, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0109] Then, at box 1103, the UE detects that a trigger condition for transmitting information for sidelink communication and / or for transmitting information for non-sidelink communication has been met. The information for sidelink communication and / or for non-sidelink communication can be measurement results or auxiliary information. The trigger condition can be a threshold for the measurement results of sidelink communication or any other suitable trigger condition. Furthermore, the trigger condition can be a threshold for the measurement results of non-sidelink communication (such as measurement results of DL / UL communication) or any other suitable trigger condition.

[0110] At box 1104, the UE avoids including information for sidelink communication and information for non-sidelink communication in the same message. For example, if the UE detects that a triggering condition for sending information for sidelink communication is met, the UE generates an instance of a message (such as an RRC message) that includes the information for sidelink communication and excludes the information for non-sidelink communication from the message (i.e., avoids including or does not include the information for non-sidelink communication in the message) (e.g., in events 306, 408A, 408B). If the UE detects that a triggering condition for sending information for non-sidelink communication is met, the UE generates an instance of a message (such as an RRC message) that includes the information for non-sidelink communication and excludes the information for sidelink communication from the message (i.e., avoids including or does not include the information for sidelink communication in the message) (e.g., in events 308, 412A, 411B).

[0111] Figure 12This is a flowchart depicting a method 1200 for transmitting a first instance of a message including information for sidelink communication and a second instance of a message including information for non-sidelink communication, which can be implemented by a UE of this disclosure (e.g., UE 102). Initially, at block 1202, the UE (e.g., in an SC or DC) communicates with a radio access network (RAN) (e.g., RAN 105) (e.g., in events 302, 402A, 402B).

[0112] The UE can obtain information regarding sidelink communication, which may be measurement results or auxiliary information related to sidelink communication between the UE and another UE. The UE can also obtain information regarding non-sidelink communication, which may be measurement results or auxiliary information related to DL / UL communication with the RAN. At block 1204, the UE generates a first instance of a message (such as an RRC message) and transmits it to the RAN, which includes both information regarding sidelink communication and information regarding non-sidelink communication (e.g., in events 306, 408A, 408B). At block 1206, the UE generates a second instance of a message (such as an RRC message) and transmits it to the RAN, which includes information regarding non-sidelink communication (e.g., in events 308, 412A, 411B). Therefore, the UE repeats the information regarding non-sidelink communication in the second instance of the message.

[0113] Figure 13 This is a flowchart depicting an example method 1300 for receiving information from a UE for sidelink communication and information for non-sidelink communication, which can be implemented by a base station (e.g., base station 104) of this disclosure. Initially, at block 1302, the base station (e.g., in an SC or DC) communicates with the UE (e.g., UE 102) (e.g., in events 302, 402A, 402B).

[0114] At block 1304, the base station receives a first instance of a message (such as an RRC message), which has a first message format and includes a payload having a first payload type. The first payload type may be a non-sidelink information payload type that includes information for non-sidelink communication (e.g., in events 308, 410A, 411B). At block 1306, the base station receives a second instance of a message (such as an RRC message), which has the same message format as the first message format and includes a payload having a second payload type. The second payload type may be the same payload type as the first payload type (e.g., a non-sidelink information payload type that includes information for non-sidelink communication), or it may be a different payload type than the first payload type (e.g., a sidelink information payload type that includes information for sidelink communication).

[0115] At box 1308, the base station determines whether the second instance of the message has the same payload type as the first instance of the message or a different payload type. If the payload type is different (e.g., the second instance of the message includes information for sidelink communication), the base station retains the first instance of the message in response to receiving the second instance of the message (box 1310).

[0116] On the other hand, if the payload types are the same (e.g., the second instance of the message does not include information for sidelink communication), the base station releases the first instance of the message in response to receiving the second instance of the message (box 1312).

[0117] The following list of examples reflects additional embodiments explicitly considered in this disclosure.

[0118] Example 1. A method for managing sidelink information and non-sidelink information in a user equipment, the method comprising: obtaining, by processing hardware in the user equipment communicating with a radio access network (RAN), a first set of information for sidelink communication with another user equipment; obtaining, by the processing hardware, a second set of information for non-sidelink communication; transmitting, by the processing hardware, a first message including the first set of information to the RAN; and transmitting, by the processing hardware, a second message including the second set of information to the RAN, wherein the first message and the second message are separate messages.

[0119] Example 2. The method according to Example 1 further includes: the processing hardware excluding the second set of information from the first message.

[0120] Example 3. The method according to either Example 1 or Example 2 further includes: the processing hardware excluding the first set of information from the second message.

[0121] Example 4. The method according to any of the foregoing examples, wherein the first message further includes the second set of information.

[0122] Example 5. The method according to any of the foregoing examples, wherein the second message further includes the first set of information.

[0123] Example 6. The method according to any of the foregoing examples, wherein the first set of information and the second set of information include measurement results or UE assistance information.

[0124] Example 7. The method according to any of the preceding examples, wherein: transmitting the first message includes transmitting a first measurement report, the first measurement report including a first set of measurement results for sidelink communication with the other user equipment; and transmitting the second message includes transmitting a second measurement report, the second measurement report including a second set of measurement results for non-sidelink communication.

[0125] Example 8. The method according to any of the foregoing examples further includes: transmitting a radio resource control message from the processing hardware to the RAN to request or release sidelink resources or report quality of service information of the sidelink communication; receiving a first measurement configuration from the RAN by the processing hardware, the first measurement configuration configuring the user equipment to measure a first set of measurement results according to the first measurement configuration; and receiving a second measurement configuration from the RAN by the processing hardware, the second measurement configuration configuring the user equipment to measure a second set of measurement results according to the second measurement configuration.

[0126] Example 9. The method according to any of the preceding examples, wherein: the first set of measurement results includes at least one of the following: sidelink carrier frequency, sidelink reference signal received power (RSRP), sidelink reference signal received quality (RSRQ), sidelink received signal strength indication (RSSI), sidelink signal-to-noise and interference ratio (SINR), or sidelink channel busy rate (CBR) value, and the second set of measurement results includes at least one of the following: downlink or uplink carrier frequency, downlink or uplink RSRP, downlink or uplink RSRQ, downlink or uplink RSSI, or downlink or uplink SINR.

[0127] Example 10. The method according to any of the foregoing examples, further comprising: obtaining, by the processing hardware, a first trigger condition for transmitting the first measurement report, the first measurement report including a first set of measurement results for sidelink communication with the other user equipment; obtaining, by the processing hardware, a second trigger condition for transmitting the second measurement report, the second measurement report including a second set of measurement results for non-sidelink communication; transmitting the first measurement report to the RAN by the processing hardware in response to determining that the first trigger condition is met; and transmitting the second measurement report to the RAN by the processing hardware in response to determining that the second trigger condition is met.

[0128] Example 11. The method according to any of the preceding examples, wherein: the RAN operates in a multiple radio dual connectivity (MR-DC) and includes a primary node (MN) and a secondary node (SN); transmitting the first message includes transmitting a first radio resource control message to the MN, the first radio resource control message including the first set of information; and transmitting the second message includes transmitting a second radio resource control message to the MN or the SN, the second radio resource control message including the second set of information.

[0129] Example 12. The method according to any of the preceding examples, wherein the first radio resource control message is included in a first container message, and the second radio resource control message is included in a second container message different from the first container message.

[0130] Example 13. The method according to any of the preceding examples, wherein: transmitting the first radio resource control message includes transmitting the first radio resource control message to the MN via a first signaling radio bearer (SRB); and transmitting the second radio resource control message includes transmitting the second radio resource control message to the SN via a second SRB.

[0131] Example 14. The method according to any of the foregoing examples further includes: determining by the processing hardware that the second SRB is configured; and in response to determining that the second SRB is configured, transmitting the second radio resource control message to the SN via the second SRB by the processing hardware.

[0132] Example 15. The method according to any of the foregoing examples further includes: determining by the processing hardware that the second SRB is not configured; and in response to determining that the second SRB is not configured, transmitting the second radio resource control message to the MN via the first SRB by the processing hardware.

[0133] Example 16. The method according to any of the preceding examples, wherein: the first set of information includes configured authorization assistance information; and the second set of information includes at least one of the following: information on enabling or disabling power saving, information on temporarily reduced capability or releasing temporarily reduced capability, overheat assistance information, information indicating that the overheating condition has disappeared, information on experiencing an in-device coexistence (IDC) problem or the IDC problem has disappeared, preferred configuration, preferred maximum aggregation bandwidth, preferred maximum number of component carriers (CC), preferred maximum number of multiple-input multiple-output (MIMO) layers, preferred minimum scheduling offset, or preferred radio resource control state.

[0134] Example 17. A user equipment including processing hardware configured to implement the method according to any of the preceding examples.

[0135] Example 18. A method for managing sidelink information and non-sidelink information in a base station, the method comprising: receiving a first instance of a message by processing hardware in the base station communicating with a user equipment, the first instance having a message format and a first payload having a first payload type; receiving a second instance of the message by the processing hardware, the second instance having the same message format as the first instance of the message and a second payload having a second payload type; and retaining the first instance of the message by the processing hardware in response to determining that the first payload and the second payload have different payload types.

[0136] Example 19. The method according to Example 18 further includes: in response to determining that the first payload and the second payload have the same payload type, the processing hardware releases a first instance of the message.

[0137] Example 20. The method according to either Example 18 or Example 19, wherein the first payload and the second payload include measurement results or UE assistance information.

[0138] Example 21. The method according to any one of Examples 18-20, wherein the first payload type is a non-sidelink information payload type that includes information for non-sidelink communication, and the second payload type is a sidelink information payload type that includes information for sidelink communication between the user equipment and another user equipment.

[0139] Example 22. A method according to any one of Examples 18-21, wherein the base station is a node in a radio access network (RAN) operating in multiple radio dual connectivity (MR-DC), the base station being a primary node (MN) in the RAN, the RAN including secondary nodes (SN), and the method further comprising: in response to receiving a first instance of the message having information for non-sidelink communication, the processing hardware transmitting a transport container message including the first instance of the message to the SN; and in response to receiving a second instance of the message having information for sidelink communication between the user equipment and another user equipment, the processing hardware transmitting a modification request container message including the second instance of the message to the SN.

[0140] Example 23. A method in a base station operating as a primary node (MN) in a RAN communicating with a user equipment, the RAN including secondary nodes (SN), the method comprising: in response to receiving a first container message containing information for non-sidelink communication, the processing hardware transmitting a transmission container message containing information for non-sidelink communication to the SN; and in response to receiving a second container message containing information for sidelink communication between the user equipment and another user equipment, the processing hardware transmitting a modification request container message containing information for sidelink communication to the SN.

[0141] Example 24. The method according to Example 23, wherein the information for non-sidelink communication includes UEAssistanceInformation messages or Measurement Report messages related to downlink / uplink communication.

[0142] Example 25. The method according to any one of Example 23 or Example 24, wherein the information for sidelink communication includes a SidelinkUEInformationNR message, a SidelinkUEInformation message, or a Measurement Report message relating to sidelink communication.

[0143] Example 26. A base station including processing hardware configured to implement the method according to any one of Examples 18-25.

[0144] The following description applies to the description above.

[0145] In some implementations, "message" is used and "information element (IE)" can be used instead of "message". In some implementations, "IE" is used and "domain" can be used instead of "IE".

[0146] User equipment implementing the technologies disclosed herein (e.g., UE 102) can be any suitable device capable of wireless communication, such as a smartphone, tablet, laptop, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, streaming dongle or other personal media device, wearable device (such as a smartwatch), wireless hotspot, femtocell, or broadband router. Furthermore, in some cases, the user equipment can be embedded in electronic systems such as a vehicle's head unit or an advanced driver assistance system (ADAS). Additionally, the user equipment can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0147] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain way. A hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., contained within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0148] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. The software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0149] Upon reading this disclosure, those skilled in the art will understand, through the principles disclosed herein, additional and alternative structural and functional designs for managing sidelink and non-sidelink information. Therefore, while specific embodiments and applications have been described and illustrated, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations that will be apparent to those skilled in the art may be made in the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined by the appended claims.

Claims

1. A method for managing sidelink information and non-sidelink information, the method comprising: The user equipment obtains the first set of information regarding sidelink communication with another user equipment. The user equipment obtains a second set of information for non-sidelink communication; The user equipment transmits a first container message, which includes a first radio resource control message, to the radio access network (RAN), wherein the first radio resource control message includes the first set of information. as well as The user equipment transmits a second container message to the RAN, which includes a second radio resource control message, the second radio resource control message including a second set of information, and the second container message is different from the first container message.

2. The method according to claim 1, further comprising: The user equipment excludes the second set of information from the first radio resource control message.

3. The method according to claim 1 or 2, further comprising: The user equipment excludes the first set of information from the second radio resource control message.

4. The method according to claim 1, wherein, The first set of information and the second set of information include measurement results.

5. The method according to claim 1, wherein, The first set of information and the second set of information include UE assistance information.

6. The method according to claim 1, wherein, Transmitting the first radio resource control message includes transmitting a first measurement report, the first measurement report including a first set of measurement results for sidelink communication with the other user equipment; as well as Transmitting the second radio resource control message includes transmitting a second measurement report, which includes a second set of measurement results for non-sidelink communications.

7. The method of claim 6, further comprising: The user equipment transmits a third radio resource control message to the RAN to request or release sidelink resources or report quality of service information for sidelink communication with the other user equipment; as well as The user equipment receives a first measurement configuration from the RAN, the first measurement configuration configuring the user equipment to measure a first set of measurement results according to the first measurement configuration; as well as The user equipment receives a second measurement configuration from the RAN, the second measurement configuration configuring the user equipment to measure a second set of measurement results according to the second measurement configuration.

8. The method according to claim 6, wherein: The first set of measurement results includes at least one of the following: sidelink carrier frequency, sidelink reference signal received power (RSRP), sidelink reference signal received quality (RSRQ), sidelink received signal strength indication (RSSI), sidelink signal-to-noise and interference ratio (SINR), or sidelink channel busy rate (CBR) value, and The second set of measurement results includes at least one of the following: downlink or uplink carrier frequency, downlink or uplink RSRP, downlink or uplink RSRQ, downlink or uplink RSSI, or downlink or uplink SINR.

9. The method of claim 6, further comprising: The user equipment obtains a first trigger condition for transmitting the first measurement report, the first measurement report including a first set of measurement results for sidelink communication with the other user equipment; The user equipment obtains a second triggering condition for transmitting the second measurement report, which includes a second set of measurement results for non-sidelink communication; In response to determining that the first triggering condition is met, the user equipment transmits the first measurement report to the RAN; as well as In response to determining that the second triggering condition is met, the user equipment transmits the second measurement report to the RAN.

10. The method according to claim 1, wherein, The user equipment operates using a multi-radio dual-connection MR-DC comprising a primary node MN and a secondary node SN.

11. The method of claim 10, wherein: Transmitting the first radio resource control message includes the user equipment transmitting the first radio resource control message to the MN via the first signaling radio bearer (SRB), and the first radio resource control message includes the first set of information. as well as Transmitting the second radio resource control message includes the user equipment transmitting the second radio resource control message to the SN via the second SRB, the second radio resource control message including the second set of information.

12. The method of claim 11, further comprising: The user equipment determines that the second SRB is configured; as well as In response to determining that the second SRB is configured, the user equipment transmits the second radio resource control message to the SN via the second SRB.

13. The method of claim 11, further comprising: The user equipment determines that the second SRB is not configured; as well as In response to determining that the second SRB is not configured, the user equipment transmits the second radio resource control message to the MN via the first SRB.

14. The method of claim 10, wherein, The user equipment operates using Evolved Universal Terrestrial Radio Access - New Radio EUTRA-NR DC (EN-DC) or Next Generation NG EUTRA-NR DC (NGEN-DC).

15. The method of claim 10, wherein: The first set of information includes configured authorization assistance information; and The second set of information includes at least one of the following: information about enabling or disabling power saving, information about temporarily reducing or releasing temporarily reduced capabilities, overheating assistance information, information indicating the disappearance of overheating conditions, information about experiencing or resolving in-device coexisting IDC problems, preferred configuration, preferred maximum aggregate bandwidth, preferred maximum number of component carriers (CCs), preferred maximum number of multiple-input multiple-output (MIMO) layers, preferred minimum scheduling offset, or preferred radio resource control status.

16. A user equipment comprising processing hardware configured to implement the method according to any one of claims 1-15.

Images