Beam management for new radio vehicle communications

Abstract

A user equipment (UE) determines sidelink resources for use in vehicle wireless communications. Initial beam establishment uses a sidelink synchronization signal (SLSS), a sidelink channel state information reference signal (SL-CSI-RS), or a sidelink demodulation reference signal (SL-DMRS). Beam refinement can then be performed by the UEs communicating with each other, or by only one of the UEs. A base station, such as a gNB, can allocate resources for a dedicated sidelink carrier or a shared grant sidelink carrier, for example, dynamically, preconfigured through RRC, or based on activation and deactivation. In such cases, initial beam establishment and refinement can include beamforming controlled by the gNB in a connectionless phase, beamforming controlled by the gNB in a connected phase where scheduling DCI is sent only to the Tx UE, or beamforming controlled by the gNB in a connected phase where scheduling DCI is sent to both the Tx UE and the Rx UE.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 888,0002, filed August 16, 2019, entitled “BEAM MANAGEMENT FOR NEW RADIOVEHICLE COMMUNICATIONS,” the contents of which are incorporated herein by reference. Background Technology

[0003] This disclosure relates to beamforming, for example, in vehicle wireless communications for new radios, as described in 3GPP TR 22.886 Study on enhancement of 3GPP Support for 5G V2X Services, Release 15, V15.2.0 and 3GPP TS22.186 Enhancement of 3GPP support for V2X scenarios (Stage 1), Release 15, V15.3.0. Summary of the Invention

[0004] In the new radio, once the user equipment (UE) determines the sidelink resources for vehicle wireless communication, initial beamforming can be achieved, for example, using a sidelink synchronization signal (SLSS), a sidelink channel state information reference signal (SL-CSI-RS), or a sidelink demodulation reference signal (SL-DMRS). Beam refinement can then be performed by either of the two communicating UEs or by only one of the two UEs.

[0005] Base stations such as gNBs can dynamically allocate resources for dedicated-side walkway carriers or shared-licensed-side walkway carriers, for example, by pre-configuring via RRC or based on activation and deactivation. In such cases, initial beamforming and refinement can include beamforming controlled by the gNB during the connectionless phase, beamforming controlled by the gNB during the connection phase where the scheduling DCI is sent only to the Tx UE, or beamforming controlled by the gNB during the connection phase where the scheduling DCI is sent to both the Tx UE and the Rx UE.

[0006] This summary is provided to present, in a simplified form, a set of concepts further described below in the detailed description section. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to addressing any or all of the deficiencies mentioned in any part of this disclosure. Attached Figure Description

[0007] A more detailed understanding can be obtained from the following description, which is given in conjunction with the accompanying drawings.

[0008] Figure 1A This is a flowchart of an example beamforming process in the case of beam refinement in a UE.

[0009] Figure 1B This is a flowchart of an example beamforming process in the case of beam refinement for two UEs.

[0010] Figure 2 This is the call flow for the example initial beamforming process during the connectionless phase.

[0011] Figure 3A An example of initial beam scanning based on SL-DMRS is shown in the case of slot-level scanning.

[0012] Figure 3B An example of initial beam scanning based on SL-DMRS is shown in the case of micro-timeslot level scanning.

[0013] Figure 4 An illustration of an example of initial beam scanning based on SL-CSI-RS.

[0014] Figure 5A The diagram illustrates an example of a beam index indicated by RS when SL-DMRS indicates the beam index used for SL-DMRS-based beam measurements.

[0015] Figure 5B The illustration shows an example of a beam index indicated by RS when the SL-CSI-RS indicates the beam index used for SL-CSI-RS-based beam measurements.

[0016] Figure 5C The illustration shows an example of a beam index indicated by RS in the case of SL-DMRS indicating the beam index used for SL-CSI-RS-based beam measurements.

[0017] Figure 6 This is a call flow for an example of the initial beam establishment process initiated by the UE during the connection phase.

[0018] Figure 7A This represents an example of initiating beam pair establishment and scheduling beam scanning when an initiation instruction is sent in FR1 and beam scanning is scheduled in FR2.

[0019] Figure 7B This represents an example of initiating beam pair establishment and scheduling beam scanning in FR1, where an initiation instruction is sent and beam scanning is scheduled.

[0020] Figure 7C This represents an example of initiating beam pair establishment and scheduling beam scanning in FR2, where an initiation instruction is sent and beam scanning is scheduled.

[0021] Figure 8A This indicates an example where UE1 sends reservation signaling in FR1 and UE2 sends a response in FR1, where separate reservation signaling is used for beam scanning and response.

[0022] Figure 8B This indicates an example where UE1 sends a reservation signaling in FR1 and UE2 sends a response in FR1, where the same reservation signaling is used for beam scanning and response.

[0023] Figure 9 This indicates an example where UE1 sends a reservation signaling in FR1 and UE2 sends a response in FR2.

[0024] Figure 10 This indicates an example where UE1 sends a reservation signaling in FR2, and UE2 sends a response in FR2.

[0025] Figure 11 This indicates an example where UE1 sends a reservation signaling in FR2 and UE2 sends a response in FR1.

[0026] Figure 12A This represents an example where UE2 sends a reservation signaling and a response in FR1.

[0027] Figure 12B This represents an example where UE2 sends a reservation signaling and a response in FR2.

[0028] Figure 13 This is a call flow for an example process of beam refinement on both UE sides.

[0029] Figure 14A The diagram illustrates an example of beam repetition used for beam refinement on the Rx UE side, where one SCI schedules multiple RS transmissions.

[0030] Figure 14B The diagram illustrates an example of beam repetition used for beam refinement on the Rx UE side, where an SCI schedules an RS transmission.

[0031] Figure 15 This is a call flow for an example procedure of beam refinement only on the Rx UE side.

[0032] Figure 16 This is a call flow for an example beamforming process controlled by the gNB during the connectionless phase, in the case of joint scheduling initial beamforming and fine-tuning.

[0033] Figure 17A This is a call flow for an example beamforming process controlled by the gNB during the connectionless phase, where the initial beamforming and fine-tuning are scheduled separately.

[0034] Figure 17B This is a call flow for an example beamforming process controlled by the gNB during the connectionless phase, where the initial beamforming and fine-tuning are scheduled separately.

[0035] Figure 18 This is a call flow example of the beamforming process controlled by the gNB during the connection phase, where only the scheduling DCI is sent to the Tx UE.

[0036] Figure 19 This is a call flow example of the beamforming process controlled by the gNB during the connection phase, in the case of sending scheduling DCI to both Tx UE and Rx UE.

[0037] Figure 20A Illustrated example of a communication system.

[0038] Figure 20B , 20C 20D is a system diagram of the example RAN and core network.

[0039] Figure 20E This diagram illustrates another example communication system.

[0040] Figure 20F This is a block diagram of an example device or apparatus, such as a WTRU.

[0041] Figure 20G This is a block diagram of an example computing system. Detailed Implementation

[0042] Table 1 includes many abbreviations used in this article.

[0043] Table 1 Abbreviations

[0044]

[0045]

[0046] LTE V2X

[0047] Vehicle communication services represented by LTE V2X services can consist of the following four different types: V2V, V2I, V2N, and V2P:

[0048] V2X services can be provided via the PC5 interface and / or the Uu interface. Support for V2X services via the PC5 interface is provided by V2X-side walkway communication, a communication mode in which UEs can communicate directly with each other via the PC5 interface. This communication mode is supported when the UE is served by E-UTRAN and when the UE is outside E-UTRA coverage. Only UEs authorized for V2X services can perform V2X-side walkway communication.

[0049] LTE-Uu can be unicast and / or MBMS. These two operating modes can be used independently by the UE for both transmission and reception; for example, the UE can use MBMS for reception but not LTE-Uu for transmission. The UE can also receive V2X messages via the LTE-Uu unicast downlink.

[0050] NR V2X use cases and requirements

[0051] With the significant advancements in vehicle-to-everything (V2X) applications, the transmission of short messages containing vehicle status data to ensure basic safety needs to be expanded to include the transmission of larger messages encompassing raw sensor data, vehicle intent data, coordination, and confirmation of future maneuvers. For these advanced applications, the expected requirements for data rates, latency, reliability, communication range, and speed become more stringent.

[0052] For enhanced V2X (eV2X) services, 3GPP identified 25 use cases and related requirements in 3GPP TR 22.886 Study on enhancement of 3GPP Support for 5G V2X Services, Release 15, V15.2.0.

[0053] 3GPP TS 22.186 Enhancement of 3GPP support for V2X scenarios (Stage 1), Release 15, V15.3.0 specifies a set of requirements, in which use cases are divided into four groups: vehicle platooning, extended sensors, advanced driving, and remote driving.

[0054] Of the 25 identified use cases, the following require high data rates and / or long communication ranges: sensor and state map sharing, information sharing for highly / fully automated driving, information sharing for highly / fully automated formation driving, and video data sharing for assisted and improved automated driving.

[0055] TS 22.186 specifies a detailed description of the performance requirements for each use case group.

[0056] Resource allocation patterns in NR V2X

[0057] In NR V2X, two sidelink resource allocation modes are supported: Mode 1 and Mode 2. In Mode 1, the base station schedules sidelink resources for the UE to use for sidelink transmission. In Mode 2, the UE determines the sidelink resources for sidelink transmission within the sidelink resources configured by the base station or pre-configured sidelink resources.

[0058] Mode 1 allows the gNB to allocate sidelink resources for both dedicated sidelink carriers and shared licensed carriers between the Uu interface and the sidelink. Resources used for sidelink transmissions can be dynamically allocated, or pre-configured by the RRC, or based on activation and deactivation.

[0059] In Mode 2, the resources used for sidelink transmission can be determined through the following resource allocation sub-modes: the UE autonomously selects the sidelink resources for transmission, the UE assists other UEs in selecting sidelink resources, the UE is configured with NR configuration authorization for sidelink transmission (similar to type-1), and the UE schedules the sidelink transmission of other UEs.

[0060] Example Challenge

[0061] In NR beam management P1, the gNB scans the beams and transmits different SSBs on each beam. The UE measures the SSB and indicates the preferred beam for initial beam establishment by performing a random access transmission associated with the selected SSB. In NR V2X, the UE can attempt to establish a beampup link with either a synchronous V2X UE or an asynchronous V2X UE, where only the synchronous V2X UE will transmit an SSB, while the asynchronous V2X UE will not. Additionally, PRACH is not supported in NR V2X. A mechanism for UEs to establish their beampup links in NR V2X needs to be addressed.

[0062] Example Solution

[0063] Beam management in NR V2X can be managed in several ways. For example, initial beamforming in NR V2X Mode 2 may include initial beamforming using, for example, SLSS, SL-CSI-RS, or SL-DMRS, as well as mechanisms for reporting preferred beams. The process for beam refinement in NR V2X Mode 2 may include refinement at both UEs, or refinement only at the RxUE side.

[0064] Similarly, in NR V2X Mode 1, there are also options regarding the initial beamforming and beam refinement process controlled by the gNB. These options include, for example: beamforming controlled by the gNB during the connectionless phase; beamforming controlled by the gNB during the connection phase, wherein the scheduling DCI is sent only to the Tx UE; and beamforming controlled by the gNB during the connection phase, wherein the scheduling DCI is sent to both the Tx UE and the Rx UE.

[0065] Beamforming and management in NR V2X Mode 2

[0066] In NR V2X Mode 2, two UEs (UE1 and UE2), such as two vehicle-mounted UEs, or one vehicle-mounted UE and one non-vehicle-mounted UE, can form a beampup link for sidelink communication. Figure 1A and Figure 1B The document provides a high-level overview of the beamforming process.

[0067] Figure 1A and Figure 1B Step 1 is the initial beam establishment during the connectionless or connected phase. One onboard UE, such as UE1, can scan the beams and transmit reference signals (RS) on each beam. Another UE, such as UE2, can monitor and measure the transmitted RS. Based on the measurement results, UE2 can identify the preferred beam and establish an initial beam pair with UE1.

[0068] Step 2 is beam refinement during the connection phase, where UE1 and UE2 can further refine the beam pair after establishing the initial beam pair to improve beam conditions. This can be accomplished in different ways, such as... Figure 1A and 1B As shown in the diagram. Figure 1A Step 2A involves beam refinement occurring only on the UE2 side. UE1 can use the beam identified during initial beamforming as the Tx beam for sidelink communication. Alternatively, UE1 can form a quasi-co-located (QCL-ed) beam with the beam identified during initial beamforming, for example, a narrow beam pointing in the same direction with a narrower beamwidth, as the Tx beam. UE2 can further refine its beam for better alignment with the beam used by UE1.

[0069] exist Figure 1B Step 2B first involves beam thinning on the UE1 side. Utilizing the knowledge of the beam identified during the initial beamforming, UE1 can further refine its beam; for example, UE1 can perform another beam scan with a narrower beam. UE2 can then measure and identify the preferred beam within the thinned UE1 beam. Figure 1BStep 2C, then beam refinement occurs on the UE2 side, so that UE2 can further refine its beam to have better alignment with the refined beam used by UE1.

[0070] Initial beamforming during the connectionless phase

[0071] In Example Scenario 1, UE1 and UE2 need to synchronize before they can communicate on the sidelink. UE1 can be the synchronization source and send a sidelink synchronization signal (SLSS). UE2 monitors and detects the SLSS to synchronize with UE1, and vice versa.

[0072] In another example scenario 2, UE1 and UE2 can synchronize with another synchronization source, which can be a Global Navigation Satellite System (GNSS), NR gNB, LTE eNB, NR V2X RSU, NR V2X synchronized UE, or LTE V2X synchronized UE. After UE1 and UE2 are synchronized, a discovery process is performed, and then they can communicate on the side link.

[0073] When UE1 and UE2 want to communicate on the side link via beam pair Figure 2 The document provides a high-level overview of the example initial beamforming process.

[0074] Figure 2 Step 1 is the initial beam scan. A vehicle-mounted UE, such as UE1, can scan the beams and transmit reference signals (RS) on each beam, where the RS can be the SLSS in case 1, the side-link channel state information reference signal (SL-CSI-RS) in cases 1 and / or 2, or the side-link demodulation reference signal (SL-DMRS).

[0075] RS can be sent independently, for example, SLSS in case 1, independent SL-CSI-RS in cases 1 and / or 2, where RS does not need to be sent along with the data.

[0076] RS can be transmitted along with data or sideline control information, such as SL-CSI-RS over PSSCH, PSCCH, or SL-DMRS over PSSCH. In other words, UE1 cannot transmit RS when it has no data or sideline control information to transmit. For example, RS can be transmitted along with discovery messages, regular data, or virtual data on the Physical Sideline Shared Channel (PSSCH). RS can also be transmitted along with sideline control information (SCI) on the PSCCH, such as SL-DMRS over the Physical Sideline Control Channel (PSCCH).

[0077] Step 2 involves measuring and identifying one or more preferred beams. UE2 monitors and measures the received RS. Based on the measurement results, UE2 identifies one or more preferred beams.

[0078] For example, UE2 can measure the reference signal received power (RSRP), reference signal received quality (RSRQ), or layer 1 signal-to-interference-to-noise ratio (L1-SINR) of the received RS.

[0079] UE2 can identify a preferred beam, such as the beam that transmits RS with the best measurement results. Alternatively, UE2 can identify multiple preferred beams and form a preferred beam list. The measurement results of one or more identified beams should be higher than a threshold, such as Q. thresh Otherwise, UE2 can declare that the preferred beam has not been identified.

[0080] Step 3 involves indicating one or more identified beams. UE2 indicates the preferred identified beams or a list of beams to UE1. Based on the response provided by UE2, UE1 can form one or more initial beam pair links with UE2.

[0081] Initial beam scan using SLSS

[0082] The initial beam pair link can be established based on the SLSS sent by UE1. This can be used when UE1 is the synchronization source, and when UE2 is synchronized with UE1 and UE2 wants to establish a beam pair with UE1.

[0083] As a synchronization source, UE1 can periodically scan beams in different directions, with each beam associated with an SLSS.

[0084] When UE2 determines that UE1 is a synchronization source in the vicinity by detecting SLSS transmitted from UE1, and if no other higher-priority synchronization source is available, such as GNSS, NR gNB, or LTE eNB, UE2 will synchronize with UE1. While UE1 is scanning its SLSS, UE2 can detect multiple SLSS from UE1 with varying measurement results. Based on the measurement results, UE2 can identify one or more beams as preferred beams. The measurement results of the identified one or more beams should be above a threshold, such as Q. thresh,SLSS Otherwise, UE2 can declare that the preferred beam has not been identified.

[0085] UE2 can periodically monitor and measure the SLSS transmitted by UE1 before establishing an initial beampup link with UE1. There are two possible scenarios in which UE1 and UE2 can establish a beampup link with each other.

[0086] In one scenario, UE2 can be triggered by UE1, for example, UE2 can receive an instruction from UE1 to establish a beampup link. In another scenario, UE2 can be triggered by its parent layer, UE2 has data to send to UE1 to establish a beampup link.

[0087] When UE2 is triggered to establish a beam pair link with UE1, UE2 can use the latest measurement results or the k most recent measurement results to determine one or more preferred beams and report one or more preferred beams to UE1.

[0088] Initial beam scan using SL-DMRS or SL-CSI-RS piggybacked via PSSCH

[0089] Initial beam scanning can use SL-DMRS or SL-CSI-RS piggybacked on the PSSCH. When the onboard UE, for example, UE1, initiates the first PSSCH transmission, such as during a discovery process, in one case, it can use an omnidirectional antenna to send a discovery message on the PSSCH, such as 'I am here' or 'Who is there?'. Alternatively, in another case, UE1 can use different beams to scan the discovery message on the PSSCH in different directions or one or more directions based on the direction or location of the potential discoverer in order to perform discovery.

[0090] Initial beam scanning based on SL-DMRS

[0091] When UE1 scans for discovery messages on the PSSCH, UE1 can send SL-DMRS via the PSSCH to assist other UEs in estimating the channel and decoding data, such as... Figure 3A and Figure 3B As shown in the image.

[0092] UE1 can send a discovery message in a time slot and scan the beam at the time slot level, such as Figure 3A As shown in the diagram. Alternatively, UE1 can send multiple discovery messages in a single time slot and scan the beam at the micro-time slot level, where a micro-time slot can contain 2 to 13 symbols, as shown in the diagram. Figure 3B As shown in the image.

[0093] The SL-DMRS carrying the discovery message in the PSSCH can also be used by other UEs to measure and identify one or more preferred beams.

[0094] For example, UE1 can transmit PSSCHs carrying discovery messages on k beams, such as beam 1, beam 2, ..., beam k. When UE2 monitors and detects the discovery messages, it can measure the received SL-DMRS on the PSSCH. Based on the measurement results, UE2 can identify one or more preferred beams. The measurement results of the identified one or more beams should be higher than a threshold, such as Q. thresh,DMRS Otherwise, UE2 can declare that the preferred beam has not been identified.

[0095] The SL-DMRS configuration used in the PSSCH carrying the discovery message can be beam-associated and vary depending on the beam. For example, the SL-DMRS used for beam 1 and beam 2 can have different ports (e.g., RE mappings in the time and / or frequency domains) and / or sequences.

[0096] Initial beam scanning based on SL-CSI-RS

[0097] When a UE sends a PSSCH carrying a discovery message, it can transmit SL-CSI-RS on the PSSCH for other UEs to measure and identify one or more preferred beams, such as... Figure 4 As shown in the image.

[0098] Figure 4 The example shown illustrates a time-slot-level beam scanning based on SL-CSI-RS. Similar to SL-DMRS-based beam scanning, micro-time-slot-level SL-CSI-RS-based beam scanning can also be performed.

[0099] For a UE receiving a discovery message, such as UE2, it can use SL-DMRS on the PSSCH to estimate the channel and decode data. UE2 can use SL-CSI-RS transmitted on the PSSCH to measure beam conditions and identify one or more preferred beams. The measurement results of the identified one or more beams should be higher than a threshold, such as Q. thresh,CSI-RS Otherwise, UE2 may require a declaration that the preferred beam has not been identified.

[0100] The SL-CSI-RS configuration used in the PSSCH carrying discovery messages can be beam-associated and vary depending on the beam. For example, the SL-CSI-RS used for beam 1 and beam 2 can have different ports (e.g., RE mappings in the time and / or frequency domains) and / or sequences.

[0101] Beam index indicator

[0102] Each PSSCH carrying a discovery message is associated with a beam index. To enable other UEs to determine the beam index of the beam that sent the PSSCH, there are at least five alternative schemes.

[0103] First, beam index information can be indicated through the SCI scheduling of the PSSCH carrying the discovery message. Before UE1 sends the PSSCH carrying the discovery message, UE1 will first send the SCI scheduling the PSSCH. In the scheduling SCI, the SCI field can be used to carry the beam index of the beam used to send the scheduled PSSCH. For example, assuming a maximum supported beam count of 32, a 5-bit field, such as the beam index indicator field, can be used to explicitly indicate the beam index. When the secondary SCI is used to schedule the PSSCH carrying the discovery message, this field can be carried by the secondary SCI. After UE2 decodes this SCI field, UE2 can determine the transmitted beam index.

[0104] Secondly, beam index information can be carried in the data payload. This beam index information can be carried by the data channel, such as the PSSCH. It can also be carried in the data transmitted on the PSSCH. After UE2 decodes the data transmitted on the PSSCH, UE2 can determine the transmitted beam index.

[0105] Third, beam index information can be carried by the RS port. Beam index information can be carried by the RS port used in the PSSCH carrying the discovery message or the PSCCH carrying the SCI. For example, the RS ports used in beam 1 and beam 2 can have different ports, for example, RE mapping in the time and / or frequency domains. When SL-DMRS is used for beam measurement, such information can be carried by the SL-DMRS port, such as... Figure 5A As shown in the diagram. When the SL-CSI-RS is used for beam measurement, such information can be carried by the SL-CSI-RS port, as... Figure 5B As shown; or it can be carried by the SL-DMRS port, such as Figure 5C As shown in the diagram. UE1 can, for example, use the SCI field 'CSI-RS Port Indicator Field' or 'DMRS Port Indicator Field' to indicate RS port information in the SCI associated with the PSSCH. UE2 determines the RS port information and beam index information by decoding such an SCI field. Alternatively, UE1 may not indicate RS port information in the SCI. UE2 determines the RS port information and beam index information by blindly detecting the DMRS or CSI-RS transmitted in the PSSCH.

[0106] Fourth, beam index information can be carried by the RS sequence. Beam index information can be carried by the RS sequence used in the PSSCH carrying the discovery message or by the RS port used in the PSCCH carrying the SCI. For example, the RS used in beam 1 and beam 2 can use different initialization sequences. When SL-DMRS is used for beam measurement, such information can be carried by the SL-DMRS sequence. When SL-CSI-RS is used for beam measurement, such information can be carried by the SL-CSI-RS sequence; or it can be carried by the SL-DMRS sequence.

[0107] Fifth, beam index information can be carried by a combination of RS sequence and RS port. For example, suppose a total of N bits of information needs to be sent to indicate the beam index. The k most significant bits (MSBs) can be carried by the RS port, and the remaining Nk bits can be carried by the RS sequence, and vice versa.

[0108] The PHY layer may need to know the V2X communication status to determine the corresponding procedures to be performed, such as initiating an initial beamforming process or a beam refinement process. For example, if a UE (e.g., UE1) determines that it is in a state of discovery with another UE (e.g., UE2), UE1 can perform an initial beamforming process to establish a beam pair link with UE2.

[0109] The V2X communication status can be explicitly indicated to the UE. For example, when the UE receives a message from the upper layer to be sent on the sidelink, the upper layer can send an indication to let the UE know whether the message is a discovery message or another type of message. If the message is a discovery message, the UE determines that it is in the V2X discovery state. Alternatively, in another alternative, the V2X communication status can be implicitly indicated to the UE. For example, the UE can implicitly deduce the current V2X communication status from some known information.

[0110] When a UE sends a discovery message on a sidelink using the PSSCH, it can send an indication to notify other UEs whether the data they are sending on the PSSCH is a discovery message or other data. Such information can be indicated in at least three ways.

[0111] First, fields in the scheduling SCI can be used to indicate whether the scheduled PSSCH carries a discovery message or other data. For example, a 1-bit field, the discovery message indicator field, can be used. When the discovery message indicator field is set to '0', it indicates that the PSSCH carries other data; when the discovery message indicator field is set to '1', it indicates that the PSSCH carries a discovery message.

[0112] Secondly, the SL-DMRS in the PSSCH or PSCCH can be used to indicate whether the scheduled PSSCH carries a discovery message or other data by using different ports and / or different sequences. For example, the SL-DMRS in the PSSCH carrying a discovery message and the SL-DMRS in the PSSCH carrying other data can have different frequency offsets, such as one starting from RE0 and the other starting from RE1. Or they can have different initialization sequences, such as they can have different c init value.

[0113] Third, the PSSCH carrying the discovery message can be sent on pre-configured resources, such as resources or resource pools dedicated to discovery. Then, by detecting it, the UE knows that it is a discovery message.

[0114] Initial beamforming during the connection phase

[0115] In some cases, the initial beam pair may not be automatically established during the synchronization and discovery processes. This may apply when the discovery process is not beam-based, for example, when two UEs are using omnidirectional antennas for discovery.

[0116] After the two UEs complete the discovery process and establish a connection, one of the UEs can initiate the establishment of a beampup link. Figure 6 The document describes a high-level overview of the initial beamforming process, which may include the following steps:

[0117] Figure 6 Step 0 is discovery. The two UEs (UE1 and UE2) perform the discovery process and establish a connection on the side link.

[0118] Step 1 is the triggering of beam establishment. A UE, such as UE1, can receive a trigger to establish a beam link with another UE, such as UE2. The trigger can be an indication sent by the upper layer based on certain Quality of Service (QoS) requirements.

[0119] Step 2 is to initiate beam pair establishment. UE1 can initiate the initial beam pair link establishment process with UE2. For example, UE1 can send an initial beam pair link establishment indicator to UE2 to initiate this process.

[0120] Such an indication can be a reference signal, such as the SL-DMRS of the SCI transmitted on the PSCCH; or it can be side link control information; or it can be data transmitted on the PSSCH, such as MAC-CE. The indication can also include other information related to beam scanning, such as time and frequency domain resources used for beam scanning, RS configuration, etc.

[0121] Since UE1 may have already established other connections with UE2, such as connections using an omnidirectional antenna or within a frequency range 1 (FR1) using a very wide beam; or connections using a frequency range 2 (FR2) using a very wide beam, UE1 may send instructions and scheduling in one of three ways, for example.

[0122] First, there's the indication on FR1 and the scheduling on FR2. Thus, UE1 can, for example, send an indication of the established connection in FR1 and a beam scanning schedule in FR2. Then, UE1 scans the beam according to the schedule. An example is shown below. Figure 7A In this case, UE1 can use different signaling to send such instructions and beam scanning scheduling.

[0123] Secondly, there is the indication and scheduling on FR1, whereby UE1 can, for example, send indications and beam scanning schedules on the established connection in FR1. UE1 then scans the beams according to the schedule. An example is shown below. Figure 7B For example, such an instruction can be transmitted along with the SCI that schedules beam scanning. Such an instruction can be carried by the SCI or by the DMRS of the SCI.

[0124] Thirdly, there's the indication and scheduling on FR2, allowing UE1 to send indications and beam scanning schedules in FR2. UE1 then scans the beams according to the schedule. An example is shown below. Figure 7C For example, such an instruction can be transmitted along with the SCI that schedules beam scanning. Such an instruction can be carried by the SCI or by the DMRS of the SCI.

[0125] Step 3 is the initial beam scan. UE1 can scan the beams and transmit RS on each beam, where RS can be SL-CSI-RS or SL-DMRS.

[0126] RS can be sent independently, such as a standalone SL-CSI-RS, where the RS does not need to be sent along with the data.

[0127] RS can be transmitted along with data or sideline control information, such as SL-CSI-RS or SL-DMRS. In other words, UE1 cannot transmit RS when it has no data or sideline control information to transmit. For example, RS can be transmitted along with regular data or virtual data on the Physical Sideline Shared Channel (PSSCH). RS can also be transmitted along with SCI on the PSCCH, such as SL-DMRS on the PSCCH.

[0128] Unlike the synchronization and discovery processes where the UE can scan the beam in all directions, UE1 can scan the beam only within a certain range. UE1 can use information from the upper-level UE2, such as position, direction, angle, and relative velocity extracted from sensors, cameras, etc., to determine this range.

[0129] Step 4 involves measuring and identifying one or more preferred beams. UE2 monitors and measures the received RS. Based on the measurement results, UE2 identifies one or more preferred beams. For example, UE2 may measure the RSRP, RSRQ, or L1-SINR of the received RS. UE2 may identify a preferred beam, such as the beam that transmits the RS with the best measurement results. Alternatively, UE2 may identify multiple preferred beams and form a list of preferred beams. The measurement results of the identified one or more beams should be higher than a threshold, such as Q. thresh Otherwise, UE2 can declare that the preferred beam has not been identified.

[0130] Step 5 involves indicating one or more identified beams, whereby UE2 indicates the preferred identified beams or a list of beams to UE1. Based on the response provided by UE2, UE1 can form one or more initial beam pair links with UE2.

[0131] The report recommends the best beam.

[0132] After UE2 measures the RS on each beam, UE2 can identify the preferred beam and notify UE1, reporting during the connected or disconnected phase.

[0133] Regarding the reporting during the connection phase, when UE1 and UE2 attempt to establish a beampup link, they may have already established other connections, such as those in FR1 via omnidirectional or wide-beam communication. In this case, UE2 can use the existing connection to send a response to UE1. For example, UE1 can scan for beams with RS within FR2, and UE2 can indicate the preferred beam to UE1 via the connection in FR1.

[0134] For reports during the connectionless phase, the UE can indicate the preferred beam to UE1 via FR2. This can be applied when there are no other available connections between UE1 and UE2. In this case, UE1 can scan for beams with RS in FR2, and UE2 can also indicate the preferred beam to UE1 in FR2.

[0135] During beam scanning, the UE2 can identify one or more preferred beams.

[0136] The response sent from UE2 to UE1 may indicate only one or more preferred beams. For example, UE2 may indicate the beam ID / index, RS port number, RS configuration ID / index, or Transmission Configuration Indicator (TCI) status of the preferred beam to UE1. UE2 may indicate only one preferred beam in its response to UE1, for example, indicating the beam with the best measurement results. Alternatively, UE2 may indicate multiple preferred beams in its response to UE1; for example, UE2 may indicate k beam indices to UE1 in descending order of beam conditions.

[0137] The response sent from UE2 to UE1 may indicate one or more preferred beams and their corresponding measurement results. For example, UE2 may indicate the beam index of the preferred beam and its corresponding RSRP or RSRQ value to UE1. UE2 may indicate one or more preferred beams to UE1. When UE2 reports multiple preferred beams, UE2 may indicate the absolute value of the measurement result for each beam in the report. Alternatively, UE2 may indicate the absolute value of the measurement result for the best beam and the differences between the remaining beams in the report and the best beam.

[0138] UE2 can explicitly indicate the preferred beam to UE1 by sending a response carrying preferred beam information. UE2 can also implicitly indicate the preferred beam to UE1 by using the selected beam for side link transmission.

[0139] UE2 can indicate the preferred beam to UE1 by using the Physical Side Link Feedback Channel (PSFCH), PSSCH, or PSCCH.

[0140] To report on the PSFCH, a response carrying one or more preferred beams can be sent on the PSFCH. For example, via Side Link Feedback Control Information (SFCI); or via the DMRS of the SFCI, for example, preferred beam information can be carried by the DMRS port and / or DMRS sequence of the DMRS sent on the PSFCH.

[0141] To report on the PSSCH, a response carrying one or more preferred beams can be sent on the PSSCH. For example, via a MAC PDU; or via the PSSCH DMRS, for example, preferred beam information can be carried by the DMRS port and / or DMRS sequence of the DMRS sent on the PSSCH.

[0142] To report on the PSCCH, a response carrying one or more preferred beams can be sent on the PSCCH. For example, via a field in the SCI; or via the DMRS of the SCI, for example, preferred beam information can be carried by the DMRS port and / or DMRS sequence of the DMRS sent on the PSCCH.

[0143] Preferred beam report using UE1 reserved resources:

[0144] In NR V2X Mode 2, the UE needs to sense the channel and reserve resources before transmission. In one approach, the resources that UE2 uses to send a response to UE1 can be reserved by UE1. When UE1 reserves resources for beam scanning, it can also reserve resources for sending a response to UE2.

[0145] UE1 can reserve resources via reservation signaling on FR1, and the report is sent by UE2 on FR1. Thus, UE1 can send reservation signaling on existing connections in FR1, for example, scheduling SCI, and reserve resources on existing connections in FR1 for sending responses, such as... Figure 8A and 8B As shown in the diagram. UE1 can use different signaling to reserve resources for beam scanning and resources for sending responses, such as... Figure 8A As shown in the diagram. UE1 can use a single signaling signal to reserve resources for beam scanning and resources for sending responses, such as... Figure 8B As shown in the diagram. UE2 can indicate the preferred beam index or RS port number associated with the preferred beam in the response so that UE1 can know the preferred beam.

[0146] Alternatively, UE1 can reserve resources via reservation signaling sent on FR1, and report this to UE2 on FR2. UE1 can send reservation signaling on an existing connection in FR1, for example, by scheduling SCI, and reserve resources in FR2 for sending the response, such as... Figure 9 As shown in the diagram, UE1 can reserve multiple resources, each of which can be associated with a beam. When UE2 identifies the preferred beam, it can send a response on the resource associated with the preferred beam. By detecting the response on the associated reserved resource, UE1 can learn about the preferred beam.

[0147] Furthermore, UE1 can reserve resources via reservation signaling on FR2, and the report can be sent by UE2 on FR2. UE1 can send reservation signaling in FR2, for example, scheduling SCI, and reserve resources in FR2 for sending a response, such as... Figure 10 As shown in the diagram, UE1 can reserve multiple resources, each of which can be associated with a beam. When UE2 identifies the preferred beam, it can send a response on the resource associated with the preferred beam. By detecting the response on the associated reserved resource, UE1 can learn about the preferred beam.

[0148] Alternatively, UE1 can reserve resources via reservation signaling sent on FR2, and the report can be sent by UE2 on FR1. UE1 can send reservation signaling in FR2, for example, by scheduling SCI, and reserve resources for sending a response on an existing connection, such as in FR1. Figure 11 As shown in the diagram. For example, in FR2, the same resource can be associated with different beam scans. UE2 can indicate the preferred beam index or RS port number associated with the preferred beam in the response so that UE1 can know the preferred beam.

[0149] Preferred beam report scheduled by UE2

[0150] In another approach, the resources that UE2 uses to send a response to UE1 can be reserved by UE2. For example, UE1 can reserve only the resources for beam scanning. After UE2 measures the RS and identifies the preferred beam, UE2 can, for example, use SCI to reserve transmission to send a response to UE1, as shown in Figure 12. UE2 can reserve the transmission of the response in several ways.

[0151] First, UE2 can schedule the report on FR1. UE2 can reserve resources and send a response on an existing connection, such as FR1. Figure 12A As shown in the diagram. UE2 can indicate the preferred beam index or RS port number associated with the preferred beam in the response so that UE1 can know the preferred beam.

[0152] Secondly, UE2 can schedule the report on FR2, thereby reserving resources on the preferred beam and sending the response, such as... Figure 12B As shown in the diagram. For example, assuming UE2 identifies beam 2 as the optimal beam, UE2 can reserve resources on beam 2 and send a response. By detecting the response, UE1 can understand that beam 2 is the preferred beam.

[0153] Beam refinement in NR V2X mode 2

[0154] After UE1 and UE2 establish their initial beamp-to-link connection, they can undergo a beam refinement process to further improve beam conditions, such as fine-tuning the beams to improve alignment. This section describes two schemes for the beam refinement process.

[0155] Beam refinement on both UE sides

[0156] In one approach, beam refinement can occur on both UE sides. Figure 13 The document describes a high-level overview of the beam refinement process on both UE sides.

[0157] Figure 13Step 0 is initial beamforming. UE1 and UE2 perform initial beamforming. After this process, UE1 receives an indication from UE2 regarding one or more preferred beams. For example, UE1 may be indicated to UE2 that beam k is the preferred beam.

[0158] Step 1 is a more refined beam scan on the UE1 side. Using information from the initial beam scan, such as beamwidth, angle of rotation between each beam, etc., and information about the preferred beam indicated by UE2, such as beam k in this example, UE1 can perform another round of more refined beam scan around beam k using one or more of the following alternatives.

[0159] The first step is to use a more refined beam scan with narrower beams. The UE1 can form and scan beams with narrower beamwidths compared to the beams used in the initial beam scan.

[0160] Secondly, a finer beam scan is achieved using a smaller rotation angle. Assuming that in the initial beam scan, the beam rotates by θ each time... init In finer beam scanning, UE1 can rotate the beam by θ between each beam transmission. finer degrees, where θ finer <θ init .

[0161] Third, it employs a finer beam scan with a smaller scanning range. In the initial beam scan, UE1 can be in α... init Degree range, for example, α init =360° beam scanning. In finer beam scanning, the UE can scan the beam over a smaller area. For example, UE1 can scan the beam around the preferred beam k in the direction of α. finer The scanning beam is within the degree range, where α finer <α init .

[0162] Fourth, a more refined beam scan with fewer scanning beams is employed. Assuming that in the initial beam scan, UE1 scans beams in K directions, while in a more refined beam scan, UE1 can scan beams in only N directions, where N... <K。

[0163] The concept proposed for the RS used for initial beam scanning can also be applied here. For example, the RS could be SL-CSI-RS or SL-DMRS. The RS can be transmitted independently, or it can be transmitted together with data or side link control information.

[0164] Figure 13Step 2 involves measuring and identifying one or more preferred beams. UE2 monitors and measures the received RS. Based on the measurement results, UE2 identifies one or more preferred beams. Concepts proposed for measuring RS during initial beamforming can also be applied here. For example, UE2 can measure the RSRP, RSRQ, or L1-SINR of the received RS. UE2 can identify one or more beams as preferred beams. The measurement results of the identified beams should be above a threshold, such as Q. thresh Otherwise, UE2 can declare that the preferred beam has not been identified.

[0165] Step 3 involves indicating one or more identified beams. UE2 indicates the identified preferred beams or a list of beams to UE1. Concepts proposed for reporting preferred beams during initial beamforming can also be applied here. For example, UE2 may explicitly indicate the preferred beams, or UE2 may implicitly indicate the preferred beams. UE2 may indicate the preferred beams to UE1 using PSFCH, PSSCH, or PSCCH. UE2 may indicate the preferred beams to UE1 via existing connections, such as those in FR1; or via the identified beams.

[0166] Step 4 involves repeating the beam on the UE1 side. UE1 can fix the beam to the preferred beam indicated by UE2 and transmit RS multiple times on that beam. When multiple preferred beams are indicated to UE1, UE1 can autonomously select one beam and transmit RS multiple times on that beam. Similar to beam scanning, RS can be SL-CSI-RS or SL-DMRS. RS can be transmitted independently, or RS can be transmitted along with data or side link control information. UE1 can schedule a side link transmission that includes multiple RS transmissions, such as... Figure 14A As shown in the diagram; or UE1 can schedule multiple sidelink transmissions, where each sidelink transmission can include an RS transmission, as shown in the diagram. Figure 14B As shown in the figure, SL-CSI-RS is used as an example of an RS to be transmitted for beam refinement. Alternatively, the RS could also be SL-DMRS.

[0167] Step 5 is beam refinement on the UE2 side. UE2 can scan its beam and use the same beam to measure the RS transmitted by UE1. UE2 can determine the beam with the best measurement results as the beam aligned with UE1. UE2 can use the determined best beam to communicate with UE1, for example, to receive data from UE1 and / or send data to UE1.

[0168] Beam refinement only on UE2 side

[0169] In another approach, to reduce the complexity of the beam refinement process and thus reduce latency, the beam refinement process can be performed only on the UE2 side. Figure 15 The document describes a high-level overview of the beam refinement process only on the UE2 side.

[0170] Figure 15 Step 0 is initial beamforming. UE1 and UE2 perform initial beamforming. After this process, UE2 indicates one or more preferred beams to UE1. For example, beam k can be indicated to UE1 as the preferred beam.

[0171] Step 1 involves repeating the beam on the UE1 side. UE1 can fix beam k as the Tx beam and transmit RS multiple times on that beam. When multiple preferred beams are indicated to UE1, UE1 can autonomously select one beam and transmit RS multiple times on that beam. Similar to beam scanning, RS can be SL-CSI-RS or SL-DMRS. RS can be transmitted independently, or RS can be transmitted together with data or side-link control information.

[0172] Step 2 is beam refinement on the UE2 side. UE2 can scan its beam and use the same beam to measure the RS transmitted by UE1. UE2 can determine the beam with the best measurement results as the beam aligned with UE1. UE2 can use the determined best beam to communicate with UE1, for example, to receive data from UE1 and / or send data to UE1.

[0173] Beamforming and Management in NR V2X Mode 1

[0174] In NR V2X Mode 1, sidelink communication is controlled by the gNB. When two UEs (UE1 and UE2), such as two vehicle-mounted UEs, or one vehicle-mounted UE and one non-vehicle-mounted UE, want to form a beampup for sidelink communication, a beamforming process controlled by the gNB can be performed.

[0175] When a UE, such as UE1, wants to establish a beampup link with other UEs in the vicinity, beamforming can be performed in either the connectionless phase or the connection phase. For example, UE1 can form a beam with a known UE, such as UE2, which may already have a connection with UE1. In this case, beamforming can be performed in the connection phase. As another example, UE1 can form a beam with an unknown UE, such as any UE x in the vicinity, which may not have any connection with UE1. In this case, beamforming can be performed in the connection phase.

[0176] Under the joint scheduling of initial beamforming and fine-tuning, beamforming controlled by gNB during the connectionless phase.

[0177] Figure 16 The text describes a high-level overview of the beamforming process controlled by the gNB during the connectionless phase.

[0178] Figure 16 Step 1 is the triggering of beam pair establishment. A UE, such as UE1, may receive a trigger to establish a beam pair link with an unknown UE, or may want to establish a beam pair link with an unknown UE. The trigger can be an indication sent by the upper layer based on some Quality of Service (QoS) requirement.

[0179] Step 2 is to request resources from the gNB. UE1 can send signaling to the gNB to request resources, such as PSCCH, PSSCH, and / or PSFCH, to establish a beam pair with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0180] In step 3, the gNB schedules resources for initial beamforming and beam refinement. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to establish the initial beam and further refine it via DCI. The DCI can schedule multiple transmissions on the sidelink, one for establishing the initial beam and the other for further beam refinement. Since UE1 is in a connectionless phase, the gNB can send the scheduled DCI only to Tx UE (UE1). UE1 can then use SCI to forward the scheduled sidelink transmissions to another UE.

[0181] Step 4 is the initial beamforming during the connectionless phase. UE1 can use the resources scheduled by the gNB to perform the initial beamforming process with UE2. The concept proposed for establishing the initial beam in V2X mode 2 during the connectionless phase can also be applied here.

[0182] Step 5 is beam refinement. UE1 can use the resources scheduled by the gNB to perform the beam refinement process with UE2. The concept proposed for beam refinement in V2X Mode 2 can also be applied here.

[0183] Under separate scheduling of initial beamforming and fine-tuning, beamforming controlled by gNB during the connectionless phase.

[0184] In another approach, Figure 17A and 17B The text describes another set of beamforming processes controlled by gNB during the connectionless phase. Figure 17A and Figure 17B The example differs in step 6.

[0185] exist Figure 17A and Figure 17BIn both cases, step 1 is the triggering of beam pair establishment. A UE, such as UE1, may receive a trigger to establish a beam pair link with an unknown UE, such as UE2, or may want to establish a beam pair link with an unknown UE, such as UE2. The trigger can be an indication sent by a higher layer based on some quality of service (QoS) requirement.

[0186] Step 2 involves requesting resources from the gNB for initial beamforming. UE1 can send signaling to the gNB to request resources, such as PSCCH, PSSCH, and / or PSFCH, to establish an initial beam pair with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0187] In step 3, the gNB schedules resources for initial beamforming. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to establish the initial beam via DCI. Since UE1 is in a connectionless phase, the gNB can send the scheduled DCI only to Tx UE (UE1). UE1 can then use SCI to forward the scheduled sidelink transmissions to other UEs.

[0188] Step 4 is the initial beam establishment. UE1 can use the resources scheduled by the gNB to perform the initial beam establishment process with UE2. The concepts proposed for establishing the initial beam in V2X Mode 2 (during the connected phase and / or the disconnected phase) can also be applied here.

[0189] Step 5 involves requesting resources from the gNB for beam refinement. After establishing the initial beam pair link, UE1 can send signaling to the gNB to request resources for further beam refinement with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0190] Figure 17A and Figure 17B The example differs in step 6. Figure 17A In step 6a, the gNB schedules resources for beam refinement and sends the scheduling DCI only to the Tx UE. The gNB can schedule resources on the side walkways used by UE1 and UE2 to further refine the beam through the DCI. The gNB can send the scheduling DCI only to the Tx UE (UE1).

[0191] exist Figure 17A In step 6b, the TX UE uses SCI to forward scheduled sidelink transmissions to the Rx UE. UE1 can also use SCI to forward scheduled sidelink transmissions to the Rx UE.

[0192] exist Figure 17BIn steps 6c and 6d, the gNB schedules resources for beam refinement and sends the scheduling DCI to both the Tx UE and the Rx UE. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to further refine the beam via the DCI. The gNB can send the scheduling DCI to both the Tx UE (UE1) and the Rx UE (e.g., UE2). Note: Steps 6c and 6d can be performed simultaneously, or step 6c can be performed before step 6d, and vice versa.

[0193] Step 7 is beam thinning. Step 7 is... Figure 17A and Figure 17B The process is the same as in [previous context]. UE1 can use the resources scheduled by the gNB to perform the beam refinement process with UE2. The concept proposed for beam refinement in V2X Mode 2 can also be applied here.

[0194] When only the scheduling DCI is sent to the Tx UE, beamforming is controlled by the gNB during the connection phase.

[0195] Figure 18 The document describes a high-level overview of the beamforming process controlled by the gNB during the connection phase when only the scheduling DCI is sent to the Tx UE.

[0196] Figure 18 Step 1 is the triggering of beam pair establishment. A UE, such as UE1, may receive a trigger to establish a beam pair link with a known UE, such as UE2, or may want to establish a beam pair link with a known UE, such as UE2. The trigger can be an indication sent by the upper layer based on some quality of service (QoS) requirement.

[0197] Step 2 involves requesting resources from the gNB for initial beam pairing. UE1 can send signaling to the gNB to request resources, such as PSCCH, PSSCH, and / or PSFCH, for establishing an initial beam pair with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0198] In step 3, the gNB schedules resources for initial beam establishment and sends the scheduling DCI only to the Tx UE. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to establish the initial beam via DCI. The gNB can send the scheduling DCI only to the Tx UE (UE1).

[0199] Step 4 is the initiation of beam pair establishment. Step 4 is optional. UE1 can initiate the initial beam pair link establishment process with UE2. For example, UE1 can send an initial beam pair link establishment indicator to UE2 to initiate the process.

[0200] In step 5, the Tx UE uses the SCI to forward the scheduled side link transmission for initial beamforming to the Rx UE. The E1 can also use the SCI to forward the scheduled side link transmission for initial beamforming to the Rx UE.

[0201] Step 6 is the initial beam establishment during the connection phase. UE1 can use the resources scheduled by the gNB to perform the initial beam establishment process with UE2. The concept proposed for establishing the initial beam in V2X Mode 2 during the connection phase can also be applied here.

[0202] Step 7 involves requesting resources from the gNB for beam refinement. After establishing the initial beam pair link, UE1 can send signaling to the gNB to request resources for further beam refinement by UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0203] In step 8, the gNB schedules resources for beam refinement and sends the scheduling DCI only to the Tx UE. The gNB can schedule resources on the side walkways used by UE1 and UE2 to further refine the beam through the DCI. The gNB can send the scheduling DCI only to the Tx UE (UE1).

[0204] In step 9, the Tx UE uses the SCI to forward the scheduled sidelink transmissions for beam refinement to the Rx UE. UE1 can also use the SCI to forward the scheduled sidelink transmissions for beam refinement to the Rx UE.

[0205] Step 10 is beam refinement. UE1 can use the resources scheduled by the gNB to perform the beam refinement process with UE2. The concept proposed for beam refinement in V2X Mode 2 can also be applied here.

[0206] The procedure proposed here can be applied to situations where UE1 is within the coverage area of ​​the gNB but UE2 is outside the coverage area of ​​the gNB. The procedure proposed here can also be applied to situations where both UE1 and UE2 are within the coverage area of ​​the gNB.

[0207] Figure 18 The process in the example illustrates how the gNB schedules resources for initial beam scanning and further fine-tuning separately using different DCIs. In another example, similar to... Figure 16 The gNB can use a DCI to jointly schedule resources for initial beam scanning and for further fine-tuning.

[0208] When sending scheduling DCI to both Tx UE and Rx UE, beamforming controlled by gNB during the connection phase.

[0209] Figure 19 The document describes a high-level overview of the beamforming process controlled by the gNB during the connection phase when scheduling DCIs are sent to both Tx UEs and Rx UEs.

[0210] Figure 19 Step 1 is the triggering of beam pair establishment. A UE, such as UE1, may receive a trigger to establish a beam pair link with a known UE, such as UE2, or may want to establish a beam pair link with a known UE, such as UE2. The trigger can be an indication sent by the upper layer based on some quality of service (QoS) requirement.

[0211] Step 2 involves requesting resources from the gNB for initial beam pairing. UE1 can send signaling to the gNB to request resources, such as PSCCH, PSSCH, and / or PSFCH, for establishing an initial beam pair with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BRS).

[0212] In steps 3a and 3b, the gNB schedules resources for initial beamforming and sends the scheduled DCI to both the Tx UE and the Rx UE. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to establish the initial beam via the DCI. The gNB can send the scheduled DCI to both the Tx UE (UE1) and the Rx UE (e.g., UE2). Note: Steps 3a and 3b can be performed simultaneously, or step 3a can be performed before step 3b, and vice versa.

[0213] Step 4 is the initial beam establishment during the connection phase. UE1 can use the resources scheduled by the gNB to perform the initial beam establishment process with UE2. The concept proposed for establishing the initial beam in V2X Mode 2 during the connection phase can also be applied here.

[0214] Step 5 involves requesting resources from the gNB for beam refinement. After establishing the initial beam pair link, UE1 can send signaling to the gNB to request resources for further beam refinement with UE2. For example, the signaling could be a scheduling request (SR) or a buffer status report (BSR).

[0215] In steps 6a and 6b, the NB schedules resources for beam refinement and sends the scheduling DCI to both the Tx UE and the Rx UE. The gNB can schedule resources on the sidelinks used by UE1 and UE2 to further refine the beam via the DCI. The gNB can send the scheduling DCI to both the Tx UE (UE1) and the Rx UE (e.g., UE2). Note: Steps 6a and 6b can be performed simultaneously, or step 6a can be performed before step 6b, and vice versa.

[0216] Step 7 is beam refinement. UE1 can use the resources scheduled by the gNB to perform the beam refinement process with UE2. The concept proposed for beam refinement in V2X Mode 2 can also be applied here.

[0217] Figure 19 The procedure in the example can be applied when both UE1 and UE2 are within the coverage area of ​​the gNB.

[0218] Figure 19 The process in the example illustrates how the gNB schedules resources for initial beam scanning and further fine-tuning separately using different DCIs. In another example, similar to... Figure 16 For example, a gNB can use a DCI to jointly schedule resources for initial beam scanning and for further fine-tuning.

[0219] Example System

[0220] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities—including work on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced, and New Radio (NR), also known as “5G.” The development of 3GPP NR standards is expected to continue and include the definition of next-generation radio access technologies (new RATs), anticipated to include the provision of new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to consist of new non-backward-compatible radio access in the new spectrum below 7 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with varying requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for applications such as indoor spaces and hotspots. In particular, Ultra Mobile Broadband is expected to share a common design framework with Flexible Radio Access below 7 GHz, featuring design optimizations specific to cmWave and mmWave.

[0221] 3GPP has identified a wide range of use cases that NR is expected to support, resulting in diverse user experience requirements regarding data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications, which can include any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle-to-other-entities communications. To name just a few, specific services and applications within these categories include, for example, surveillance and sensor networks, remote device control, two-way remote control, personal cloud computing, video streaming, wireless cloud office, first responder connectivity, car eCall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones. All of these use cases, and others, are envisioned in this document.

[0222] Figure 20A The diagram illustrates an example communication system 100 in which the systems, methods, and devices described and claimed herein may be used. Communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, generally or collectively referred to as WTRU 102. Communication system 100 may include radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. Network services 113 may include, for example, V2X servers, V2X functions, ProSe servers, ProSe functions, IoT services, video streaming, and / or edge computing.

[0223] It should be understood that the concepts disclosed herein can be used with any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102 can be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Figure 20A In the example, each WTRU 102 in Figures 20A-20EThe device is described as a handheld wireless communication device. It should be understood that, for the various use cases envisioned for wireless communication, each WTRU may include, or be contained within, any type of device or apparatus configured to transmit and / or receive wireless signals. By way of example only, such devices or apparatuses include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, vehicles such as cars, buses, or trucks, trains, or airplanes, etc.

[0224] The communication system 100 may also include base station 114a and base station 114b. Figure 20A In the example, each base station 114a and 114b is depicted as a single element. In practice, base stations 114a and 114b may include any number of interconnected base stations and / or network elements. Base station 114a may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, network services 113, and / or other networks 112. Similarly, base station 114b can be any type of device configured to connect via wired and / or wireless interfaces to at least one of the Remote Radio Headers (RRHs) 118a, 118b, Transmit and Receive Points (TRPs) 119a, 119b, and / or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or network services 113. RRHs 118a, 118b can be any type of device configured to connect via wireless interfaces to at least one of the WTRUs 102, such as WTRU 102c, to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, network services 113, and / or other networks 112.

[0225] TRPs 119a and 119b can be any type of device configured to wirelessly interface with at least one of WTRUs 102d to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, network services 113, and / or other networks 112. RSUs 120a and 120b can be any type of device configured to wirelessly interface with at least one of WTRUs 102e or 102f to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or network services 113. For example, base stations 114a and 114b can be base transceiver stations (BTS), Node-B, eNode B, home node B, home eNode B, next-generation Node-B (gNode B), satellites, site controllers, access points (APs), wireless routers, etc.

[0226] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as Base Station Controller (BSC), Radio Network Controller (RNC), relay nodes, etc. Similarly, base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as BSC, RNC, relay nodes, etc. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographical area, which may be referred to as a cell (not shown). Similarly, base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area, which may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, for example, base station 114a may include three transceivers, for example, one transceiver per sector of the cell. Base station 114a may employ multiple-input multiple-output (MIMO) technology, thus, for example, multiple transceivers may be used for each sector of the cell.

[0227] Base station 114a can communicate with one or more of WTRUs 102a, 102b, 102c, and 102g via air interfaces 115 / 116 / 117, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115 / 116 / 117.

[0228] Base station 114b can communicate with one or more of RRH 118a and 118b, TRP 119a and 119b, and / or RSU 120a and 120b via wired or air interfaces 115b / 116b / 117b. Air interfaces 115b / 116b / 117b can be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). Any suitable RAT can be used to establish air interfaces 115b / 116b / 117b.

[0229] RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a, 120b can communicate with one or more of WTRU 102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which can be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). Any suitable RAT can be used to establish air interface 115c / 116c / 117c.

[0230] WTRU 102 can communicate with each other via direct air interfaces 115d / 116d / 117d, such as sidelink communication. Air interfaces 115d / 116d / 117d can be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). Any suitable RAT can be used to establish air interfaces 115d / 116d / 117d.

[0231] Communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN103 / 104 / 105 and WTRU 102a, 102b, 102c, or RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a and 120b in RAN103b / 104b / 105b and WTRU 102c, 102d, 102e and 102f can implement radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0232] Base station 114a in RAN 103 / 104 / 105 and WTRU 102a, 102b, 102c and 102g, or RRH 118a and 118b, TRP 119a and 119b and / or RSU 120a and 120b and WTRU 102c and 102d in RAN 103b / 104b / 105b, can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use, for example, Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. Air interfaces 115 / 116 / 117 or 115c / 116c / 117c can implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and / or V2X technologies and interfaces (such as sidelink communication). Similarly, 3GPP NR technologies may include NRV2X technologies and interfaces (such as sidelink communication).

[0233] Base station 114a in RAN 103 / 104 / 105 with WTRU 102a, 102b, 102c and 102g, or RRH 118a and 118b, TRP 119a and 119b and / or RSU 120a and 120b with WTRU 102c, 102d, 102e and 102f in RAN 103b / 104b / 105b, can implement radio technologies such as IEEE 802.16 (e.g., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE), and GSM. EDGE (GERAN) etc.

[0234] Figure 20A Base station 114c can be, for example, a wireless router, home node B, home eNode B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial locations, homes, vehicles, trains, airplanes, satellites, factories, campuses, etc. Base station 114c and WTRU 102, such as WTRU 102e, can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, base station 114c and WTRU 102, such as WTRU 102d, can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). Base station 114c and WTRU 102, such as WTRU 102e, can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish picocells or femtocells. Figure 20A As shown, base station 114c can have a direct connection to the Internet 110. Therefore, it is not required for base station 114c to access the Internet 110 via core network 106 / 107 / 109.

[0235] RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b can communicate with core networks 106 / 107 / 109, which can be any type of network configured to provide voice, data, messaging, authorization and authentication, application and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102. For example, core networks 106 / 107 / 109 can provide call control, billing services, location-based services, prepaid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, and / or advanced security features such as user authentication.

[0236] Although not in Figure 20A As shown, but it should be understood that RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs using the same RAT as or a different RAT than RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b. For example, in addition to being connected to RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b which can utilize E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) using GSM or NR radio technology.

[0237] Core networks 106 / 107 / 109 can also serve as gateways for WTRU 102 to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Other networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include any type of packet data network (e.g., IEEE 802.3 Ethernet) or another core network connected to one or more RANs, which may use the same RAT as RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0238] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capability. For example, WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 20A The WTRU 102g shown can be configured to communicate with a base station 114a that can employ cellular-based radio technology and with a base station 114c that can employ IEEE 802 radio technology.

[0239] Although not in Figure 20A As shown, however, it should be understood that user equipment can establish a wired connection to a gateway. The gateway can be a residential gateway (RG). The RG can provide connectivity to the core network 106 / 107 / 109. It should be understood that many of the concepts contained herein can be equally applied to UEs acting as WTRUs and UEs connecting to the network using wired connections. For example, concepts applied to radio interfaces 115, 116, 117, and 115c / 116c / 117c can be equally applied to wired connections.

[0240] Figure 20B This is a system diagram of example RAN 103 and core network 106. As described above, RAN 103 can communicate with WTRUs 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. Figure 20B As shown, RAN 103 may include Node-B 140a, 140b, and 140c, each of which may include one or more transceivers for communicating with WTRU 102a, 102b, and 102c via air interface 115. Node-B 140a, 140b, and 140c may be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNC 142a and 142b. It should be understood that RAN 103 may include any number of Node-Bs and Radio Network Controllers (RNCs).

[0241] like Figure 20BAs shown, Node-B 140a and 140b can communicate with RNC 142a. Additionally, Node-B 140c can communicate with RNC 142b. Node-B 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. RNCs 142a and 142b can be configured to control their respective connected Node-B 140a, 140b, and 140c. Furthermore, RNCs 142a and 142b can be configured to perform or support other functions, such as outer-loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0242] Figure 20B The core network 106 shown may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the above elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0243] RNC 142a in RAN 103 can be connected to MSC 146 in core network 106 via IuCS interface. MSC 146 can be connected to MGW 144. MSC 146 and MGW 144 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communication between WTRU 102a, 102b, and 102c and conventional landline communication equipment.

[0244] RNC 142a in RAN 103 can also be connected to SGSN 148 in core network 106 via IuPS interface. SGSN 148 can be connected to GGSN 150. SGSN 148 and GGSN 150 can provide WTRU 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

[0245] The core network 106 can also be connected to other networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0246] Figure 20CThis is a system diagram of example RAN 104 and core network 107. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0247] RAN 104 may include eNode-B 160a, 160b, and 160c, although it should be understood that RAN 104 may include any number of eNode-Bs. eNode-B 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRU 102a, 102b, and 102c via air interface 116. For example, eNode-B 160a, 160b, and 160c may implement MIMO technology. Thus, eNode-B 160a may, for example, use multiple antennas to transmit and receive radio signals from WTRU 102a.

[0248] eNode-B 160a, 160b, and 160c can each be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink and / or downlink. For example... Figure 20C As shown, eNode-B 160a, 160b and 160c can communicate with each other via the X2 interface.

[0249] Figure 20C The core network 107 shown may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the above elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0250] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, and selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies, such as GSM or WCDMA.

[0251] Serving Gateway 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. Serving Gateway 164 can typically route and forward user data packets to and from WTRUs 102a, 102b, and 102c. Serving Gateway 164 can also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0252] Service gateway 164 can also be connected to PDN gateway 166, which can provide WTRUs 102a, 102b and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communication between WTRUs 102a, 102b and 102c and devices with IP capabilities.

[0253] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication devices. For example, core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108, or can communicate with it. Additionally, core network 107 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0254] Figure 20D This is a system diagram of example RAN 105 and core network 109. RAN 105 can communicate with WTRU 102a and 102b via air interface 117 using NR radio technology. RAN 105 can also communicate with core network 109. Non-3GPP Interoperability Function (N3IWF) 199 can communicate with WTRU 102c via air interface 198 using non-3GPP radio technology. N3IWF 199 can also communicate with core network 109.

[0255] RAN 105 may include gNode-B 180a and 180b. It should be understood that RAN 105 may include any number of gNode-Bs. gNode-B 180a and 180b may each include one or more transceivers for communicating with WTRU 102a and 102b via air interface 117. When using integrated access and backhaul connections, the same air interface can be used between the WTRU and the gNode-B, which may be via the core network 109 of one or more gNBs. gNode-B 180a and 180b may implement MIMO, MU-MIMO, and / or digital beamforming technologies. Thus, gNode-B 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. It should be understood that RAN 105 may employ other types of base stations, such as eNode-Bs. It should also be understood that RAN 105 may employ more than one type of base station. For example, RAN may employ both eNode-Bs and gNode-Bs.

[0256] The N3IWF 199 may include a non-3GPP access point 180c. It should be understood that the N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with the WTRU 102c via air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c via air interface 198 using the 802.11 protocol.

[0257] gNode-B 180a and 180b can be associated with specific cells (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink or downlink. For example... Figure 20D As shown, gNode-B 180a and 180b can communicate with each other, for example, via the Xn interface.

[0258] Figure 20D The core network 109 shown may be a 5G core network (5GC). The core network 109 can provide numerous communication services to customers interconnected via a radio access network. The core network 109 includes multiple entities performing core network functions. As used herein, the terms "core network entity" or "network function" refer to any entity performing one or more functions of the core network. It should be understood that such a core network entity may be a logical entity implemented in the form of computer-executable instructions (software), which are stored in a device configured for wireless and / or network communications, or a computer system (e.g., Figure 20GThe system 90 shown in the diagram is stored in its memory and executed on its processor.

[0259] exist Figure 20D In this example, the 5G core network 109 may include Access and Mobility Management Functions (AMF) 172, Session Management Functions (SMF) 174, User Plane Functions (UPF) 176a and 176b, User Data Management Functions (UDM) 197, Authentication Server Functions (AUSF) 190, Network Openness Functions (NEF) 196, Policy Control Functions (PCF) 184, Non-3GPP Interoperability Functions (N3IWF) 199, and / or User Data Repository (UDR) 178. While each of these elements is depicted as part of the 5G core network 109, it is important to understand that any of these elements may be owned and / or operated by an entity other than the core network operator. It is also important to understand that the 5G core network may not consist of all of these elements; it may consist of additional elements, and it may consist of multiple instances of each of these elements. Figure 20D This indicates that network functions are directly interconnected; however, it should be recognized that they can communicate via routing proxies, such as diameter routing proxies or message buses.

[0260] exist Figure 20D In the example, connectivity between network functions is achieved through a set of interfaces or reference points. It's important to recognize that network functions can be simulated, described, or implemented as a set of services invoked or called by other network functions or services. Network function services can be enabled through direct connections between network functions, message exchange on a message bus, invoking software functions, etc.

[0261] The AMF 172 can connect to RAN 105 via the N2 interface and can act as a control node. For example, the AMF 172 can be responsible for registration management, connection management, reachability management, access authentication, and / or access authorization. The AMF can forward user plane tunnel configuration information to RAN 105 via the N2 interface. The AMF 172 can receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 can typically route and forward NAS packets to and from WTRU 102a, 102b, and 102c via the N1 interface. The N1 interface is not... Figure 20D The middle shows

[0262] SMF 174 can connect to AMF 172 via interface N11. Similarly, SMF 174 can connect to PCF184 via interface N7 and to UPF 176a and 176b via interface N4. SMF 174 can act as a control node. For example, SMF 174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, management and configuration of traffic routing rules in UPF 176a and UPF 176b, and generation of downlink data notifications to AMF 172.

[0263] UPF 176a and UPF 176b can provide WTRU 102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communication between WTRU 102a, 102b, and 102c and other devices. UPF 176a and UPF 176b can also provide WTRU 102a, 102b, and 102c with access to other types of packet data networks. For example, other networks 112 can be Ethernet or any type of network that switches data packets. UPF 176a and UPF 176b can receive traffic routing rules from SMF 174 via the N4 interface. UPF 176a and UPF 176b can provide access to packet data networks by connecting to the packet data network via the N6 interface, or by interconnecting with each other or connecting to other UPFs via the N9 interface. In addition to providing access to packet data networks, UPF 176 can also be responsible for packet routing and forwarding, policy and rule enforcement, quality of service processing for user plane traffic, and downlink packet caching.

[0264] The AMF 172 can also connect to the N3IWF 199, for example, via the N2 interface. The N3IWF facilitates connectivity between the WTRU 102c and the 5G core network 170, for example, via a radio interface technology not defined by 3GPP. The AMF can interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0265] The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF172 via the N15 interface, and to the Application Function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not... Figure 20DAs shown in the diagram, PCF 184 can provide policy rules to control plane nodes such as AMF 172 and SMF 174, allowing these control plane nodes to enforce these rules. PCF 184 can send policies to AMF 172 for WTRUs 102a, 102b, and 102c, enabling AMF to deliver policies to WTRUs 102a, 102b, and 102c via the N1 interface. The policies can then be enforced or applied on WTRUs 102a, 102b, and 102c.

[0266] UDR 178 can be used as a repository for authentication credentials and subscription information. The UDR can connect to network functions, allowing them to add, read, and modify data within the repository. For example, UDR 178 can be connected to PCF184 via interface N36. Similarly, UDR 178 can be connected to NEF196 via interface N37, and UDR 178 can be connected to UDM 197 via interface N35.

[0267] The UDM 197 can be used as an interface between the UDR 178 and other network functions. The UDM 197 can authorize network functions to access the UDR 178. For example, the UDM 197 can connect to the AMF 172 via interface N8, and to the SMF 174 via interface N10. Similarly, the UDM 197 can connect to the AUSF 190 via interface N13. The UDR 178 and UDM 197 can be tightly integrated.

[0268] The AUSF 190 performs authentication-related operations, connects to the UDM 178 via the N13 interface, and connects to the AMF 172 via the N12 interface.

[0269] The NEF 196 exposes the capabilities and services of the 5G core network 109 to the Application Function (AF) 188. This exposure can occur on the N33 API interface. The NEF can connect to the AF 188 via the N33 interface, and it can connect to other network functions to expose the capabilities and services of the 5G core network 109.

[0270] Application function 188 can interact with network functions in the 5G core network 109. The interaction between application function 188 and network functions can occur via a direct interface or via NEF 196. Application function 188 can be considered part of the 5G core network 109, or it can be outside the 5G core network 109 and deployed by an enterprise with a business relationship with the mobile network operator.

[0271] Network slicing is a mechanism that mobile network operators can use to support one or more 'virtual' core networks behind the operator's air interface. This involves 'slicing' the core network into one or more virtual networks to support different RANs or different service types operating across a single RAN. Network slicing enables operators to create customized networks to provide optimized solutions for different market scenarios with diverse requirements, such as functionality, performance, and isolation.

[0272] 3GPP designed the 5G core network to support network slicing. Network slicing is a powerful tool for network operators to support a diverse range of 5G use cases with highly varied and sometimes extreme requirements, such as massive IoT, critical communications, V2X, and enhanced mobile broadband. Without network slicing, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture may not be flexible and scalable enough to efficiently support a wider range of use case needs. Furthermore, the introduction of new network services should be made more efficient.

[0273] See you again Figure 20D In a network slicing scenario, WTRU 102a, 102b, or 102c can be connected to AMF 172 via the N1 interface. AMF 172 can logically be part of one or more slices. AMF 172 can coordinate connections or communication between WTRU 102a, 102b, or 102c and one or more UPF 176a and 176b, SMF 174, and other network functions. Each of UPF 176a and 176b, SMF 174, and other network functions can be part of the same slice or different slices. When they are part of different slices, they can be isolated from each other in terms of the different computing resources, security credentials, etc., they can utilize.

[0274] Core network 109 can facilitate communication with other networks. For example, core network 109 may include an IP gateway, such as an IP Multimedia Subsystem (IMS) server, serving as an interface between 5G core network 109 and PSTN 108, or may communicate with said IP gateway. For example, core network 109 may include a Short Message Service (SMS) service center facilitating communication via Short Message Service, or may communicate with said Short Message Service (SMS) service center. For example, 5G core network 109 can facilitate the exchange of non-IP data packets between WTRUs 102a, 102b, and 102c and server or application function 188. Additionally, core network 170 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned or operated by other service providers.

[0275] The descriptions in this article and Figure 20A , 20C The core network entities illustrated in 3GPP 20D and 20E are identified using the names assigned to these entities in certain existing 3GPP specifications. However, it should be understood that in the future, these entities and functions may be identified using other names, and some entities or functions may be combined in future 3GPP specifications, including future 3GPP NR specifications. Therefore, in Figure 20A , 20B The specific network entities and functions described and illustrated in 20C, 20D and 20E are provided only as examples, and it should be understood that the subject matter disclosed and claimed herein can be implemented or realized in any similar communication system, whether currently defined or to be defined in the future.

[0276] Figure 20E The diagram illustrates a forensic communication system 111 in which the systems, methods, and devices described herein can be used. Communication system 111 may include wireless transceiver units (WTRUs) A, B, C, D, E, and F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein can be applied to any number of WTRUs, base station gNBs, V2X networks, and / or other network elements. One or more, or all, of the WTRUs A, B, C, D, E, and F may be outside the coverage area 131 of the access network. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader, and WTRUs B and C are group members.

[0277] WTRUs A, B, C, D, E, and F can communicate with each other via gNB 121 through Uu interface 129 if they are within the access network coverage area 131. Figure 20E In the example, WTRUs B and F are represented within the access network coverage area 131. WTRUs A, B, C, D, E, and F can communicate directly with each other via sidelink interfaces (e.g., PC5 or NR PC5), such as interfaces 125a, 125b, or 128, regardless of whether they are within or outside the access network coverage area 131. For example, in Figure 20E In the example, WTRU D, which is outside the access network coverage area 131, communicates with WTRU F, which is within the coverage area 131.

[0278] WTRUs A, B, C, D, E, and F can communicate with RSUs 123a or 123b via Vehicle-to-Network (V2N) 133 or sidelink interface 125b. WTRUs A, B, C, D, E, and F can communicate with V2X server 124 via Vehicle-to-Infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F can communicate with other UEs via Vehicle-to-Person (V2P) interface 128.

[0279] Figure 20F Example device or apparatus WTRU 102, which can be configured for wireless communication and operation according to the systems, methods and devices described herein, such as... Figure 20A , 20B A block diagram of WTRU 102, model 20C, 20D, or 20E. (Example) Figure 20F As shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that WTRU 102 may include any sub-combination of the above-mentioned elements. Additionally, base stations 114a and 114b and / or base stations 114a and 114b may represent nodes such as, but not limited to, transceiver stations (BTS), Node-B, site controllers, access points (APs), home node-B, evolved home node-B (eNodeB), evolved home node-B (HeNB), evolved home node-B gateway, next-generation node-B (gNode-B), and proxy nodes, etc., and may include... Figure 20F Some or all of the elements depicted in and described herein.

[0280] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving element 122. Although Figure 20F The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 can be integrated together in an electronic package or chip.

[0281] The UE's transmit / receive element 122 can be configured to transmit data to the base station (e.g., via air interface 115 / 116 / 117). Figure 20A The base station 114a) sends signals or receives signals from the base station (e.g., Figure 20A The base station 114a) receives signals, or transmits signals to or receives signals from another UE via air interface 115d / 116d / 117d. For example, the transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. The transmitting / receiving element 122 may, for example, be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. The transmitting / receiving element 122 may be configured to transmit and receive both RF signals and optical signals. It should be appreciated that the transmitting / receiving element 122 may be configured to transmit and / or receive any combination of wireless signals or wired signals.

[0282] Additionally, although the transmitting / receiving element 122 is in Figure 20F While depicted as a single element, the WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interfaces 115 / 116 / 117.

[0283] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Thus, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 or NR and E-UTRA, or via multiple beams to different RRHs, TRPs, RSUs, or nodes using the same RAT.

[0284] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad / indicator 128. Additionally, the processor 118 can access and store information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identification module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. Processor 118 can access information and store data in memory that is not physically located in WTRU 102, such as memory hosted on a server in the cloud or edge computing platform or in a home computer (not shown).

[0285] The processor 118 may receive power from the power supply 134 and may be configured to distribute power to other components in the WTRU 102 and / or control the power supplied to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0286] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interfaces 115 / 116 / 117, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method.

[0287] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0288] WTRU 102 may be included in other devices or apparatuses, such as sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, or vehicles such as cars, trucks, trains, or airplanes. WTRU 102 may be connected to other components, modules, or systems of such devices or apparatuses via one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.

[0289] Figure 20G This is a block diagram of example computing system 90, which can include... Figure 20A , 20C The computing system 90 may include one or more devices in the communication network illustrated in Figures 20D and 20E, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, other network 112, or network service 113. The computing system 90 may include a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software, regardless of where or in what way such software is stored or accessed. These computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to function. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable the computing system 90 to operate within the communication network. The coprocessor 81 is an optional processor, distinct from the main processor 91, that can perform additional functions or assist the main processor 91. The processor 91 and / or the coprocessor 81 can receive, generate, and process data relating to the methods and apparatus disclosed herein.

[0290] During operation, processor 91 fetches, decodes, and executes instructions, and transmits information to other resources via system bus 80 through the main data transfer path of the computing system. This system bus connects components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for the operating system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0291] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. This memory includes circuitry that allows for the storage and retrieval of information. ROM 93 typically contains stored data that cannot be easily modified. Data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 can provide address translation functionality, converting virtual addresses to physical addresses when instructions are executed. The memory controller 92 can also provide memory protection functionality that isolates processes within the system and separates system processes from user processes. Thus, a program running in first mode can only access memory mapped by its own process virtual address space; unless inter-process memory sharing is configured, it cannot access memory in another process's virtual address space.

[0292] Additionally, the computing system 90 may include a peripheral device controller 83, which is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0293] A display 86, controlled by a display controller 96, is used to display visual output generated by a computing system 90. This visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components required to generate the video signals sent to the display 86.

[0294] Furthermore, the computing system 90 may include features for connecting the computing system 90 to an external communication network or device, such as... Figure 20A , 20BThe communication circuitry, such as wireless or wired network adapter 97, enables the computing system 90 to communicate with other nodes or functional entities of these networks, including RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, the Internet 110, WTRU 102, or other networks 112 of 20C, 20D, and 20E. This communication circuitry can be used alone or in conjunction with processor 91 to perform certain transmission and reception steps of the devices, nodes, or functional entities described herein.

[0295] It should be understood that any or all devices, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor, such as processor 118 or 91, cause the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer-executable instructions that execute on a processor of a device or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storing information, although such computer-readable storage media do not include signals. Computer-readable storage media include (but are not limited to) RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, Digital Universal Disc (DVD) or other optical disc storage devices, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, or any other tangible or physical medium that can be used to store desired information and can be accessed by a computing system.

Claims

1. A first user equipment (UE), comprising: a processor, the processor configured to: transmit, to a second UE, an initial beam pair link setup indicator, wherein the initial beam pair link setup indicator includes information indicating time and frequency resources to be used for an initial beam sweep, and wherein the initial beam pair link setup indicator is a sidelink demodulation reference signal (SL-DMRS) transmitted on a physical sidelink control channel (PSCCH); transmit a first set of sweep beams through the time and frequency resources indicated by the initial beam pair link setup indicator, each beam of the first set of sweep beams including a reference signal, and wherein the reference signal transmitted on each sweep beam of the first set of sweep beams is a SL-DMRS; and receive, from the second UE, an indication of one or more preferred beams including one or more beams selected from the first set of sweep beams.

2. The first UE of claim 1, wherein the initial beam pair link setup indicator is a medium access control-control element (MAC-CE) transmitted on a physical sidelink control channel (PSCCH).

3. The first UE of claim 1, wherein the initial beam pair link setup indicator includes a reference signal configuration to be used for the initial beam sweep.

4. The first UE of claim 1, wherein the processor is further configured to: initiate a beam pair link setup with the second UE in response to a trigger from a higher layer of the first UE.

5. The first UE of claim 4, wherein the trigger is based on a quality of service (QoS) requirement.

6. The first UE of claim 1, wherein the processor is further configured to: transmit the initial beam pair link setup indicator to the second UE in a first frequency range; and transmit the first set of sweep beams in a second frequency range.

7. The first UE of claim 6, wherein the processor is configured to receive, from the second UE in a connectionless state, the indication of one or more preferred beams via the first frequency range.

8. A second user equipment (UE), comprising: a processor, the processor configured to: receive, from a first UE, an initial beam pair link setup indicator, wherein the initial beam pair link setup indicator includes information indicating time and frequency resources to be used for an initial beam sweep, and wherein the initial beam pair link setup indicator is a sidelink demodulation reference signal (SL-DMRS) transmitted on a physical sidelink control channel (PSCCH); receive, from the first UE, one or more beams of a first set of sweep beams through the time and frequency resources indicated by the initial beam pair link setup indicator, each received beam including a reference signal, and wherein the reference signal transmitted on each sweep beam of the first set of beams is a SL-DMRS; ​ selecting one or more preferred beams from the one or more received beams; and transmitting an indication of the one or more preferred beams to the first UE.

9. The second UE of claim 8, wherein the processor is further configured to indicate to the first UE that none of the received beams satisfy a minimum quality threshold.

10. The second UE of claim 8, wherein the processor is configured to select the one or more preferred beams based on one or more of a reference signal received power (RSRP), a reference signal received quality (RSRQ), a layer 1 signal to interference noise ratio (Ll-SINR).

11. The second UE of claim 8, wherein the initial beam pair link setup indicator is a medium access control-control element (MAC-CE) transmitted on a physical sidelink control channel (PSCCH).

12. The second UE of claim 8, wherein the initial beam pair link setup indicator includes a reference signal configuration to be used for initial beam sweeping.

13. The second UE of claim 8, wherein the processor is further configured to: receive the initial beam pair link setup indicator from the first UE in a first frequency range; and receive one or more beams of the first set of sweeping beams from the first UE in a second frequency range.

14. The second UE of claim 13, wherein the processor is further configured to transmit an indication of one or more preferred beams to the first UE in a connectionless state via the first frequency range.

Images