Method and system for exchanging information for sidelink communication

Abstract

Methods, apparatuses, and systems for selecting and establishing sidelink resources in a UE. The present disclosure provides various systems and methods of exchanging parameters between groups of networked UEs in order to schedule resources.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications. Background Technology

[0002] Mobile communication technology is propelling the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in mobile communications have led to greater demands for capacity and connectivity. Other factors, such as energy consumption, device cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Various technologies are being discussed, including new approaches to provide higher service quality, longer battery life, and improved performance. Summary of the Invention

[0003] This patent document also describes, among other things, techniques for communication in the sidelink deployment of new radio (NR).

[0004] The following aspects may preferably be implemented in various embodiments.

[0005] In one aspect, the first wireless device transmits a request for scheduling information to the second wireless device and receives scheduling information from the second wireless device.

[0006] In one aspect, the scheduling information request or response includes: (a) the scheduling capability of the second wireless device; or (b) the coverage status of the second wireless device, including being within or outside coverage; or (c) the RRC status of the second wireless device, including idle, inactive, or connected; or (d) the transmission resource set of the second wireless device, including being pre-configured, configured by system information, or configured by the base station of the second wireless device; or (e) the coverage status of the second wireless device; or (f) the Radio Resource Control (RRC) status of the second wireless device. In yet another aspect, the scheduling information includes the capabilities of the second wireless device, including: (a) whether the second wireless device can provide a resource pool; or (b) whether the second wireless device can provide transmission grants; or (c) the transmission resource selection method supported by the second wireless device, including random selection, sensing, partial sensing, or dynamic scheduling; or (d) whether the second wireless device can provide transmission resources for the first wireless device to transmit data to the second wireless device; or (e) whether the second wireless device can provide transmissions for the second wireless device to transmit to any destination. In another aspect, scheduling information includes: PC5 RRC signaling, or PC5 MAC control element (MAC CE), or PC5 NAS signaling, or sidelink control information (SCI).

[0007] In another aspect, the first wireless device receives a request for scheduling information from the base station before transmitting scheduling information to the second wireless device. In yet another aspect, the first wireless device is configured to transmit the scheduling information for the second wireless device to the base station after receiving the scheduling information from the second wireless device. In yet another aspect, the first wireless device transmits a list including scheduling information for more than one device. In yet another aspect, the first wireless device is a first user equipment (UE), and the second wireless device is a second UE. In yet another embodiment, the first wireless device is a base station, and the second wireless device is a UE.

[0008] In one aspect, a first wireless device transmits a scheduling configuration to a second wireless device and receives a configuration response message from the second wireless device. In another aspect, the scheduling configuration includes: (a) a resource pool configuration, or (b) service packet information, or (c) service information, or (d) a scheduling request resource configuration, or (e) a radio bearer configuration, or (f) resource selection information including sensing parameters. In another aspect, the first wireless device connects to multiple devices, and the first wireless device transmits non-overlapping SR resource configurations to the multiple devices. In another aspect, the scheduling configuration includes: (a) a resource pool configuration, or (b) a scheduling request configuration, or (c) an acquired radio bearer configuration. In another aspect, the scheduling configuration is obtained via at least one of: pre-configuration, or system information, or RRC signaling. In another aspect, the configuration response message includes: (a) a failure indication related to whether the corresponding configuration failed, or (b) a conflict indication related to whether the scheduling request resource conflicts with another device, or (c) a scheduling request resource configuration related to whether the SR resource configuration is recommended by the second wireless device.

[0009] In another aspect, the first wireless device sends a configuration response message to the base station. In yet another aspect, the second wireless device is configured to send scheduling configuration to the base station.

[0010] In one aspect, a first wireless device receives a scheduling request (SR) configuration including an sr-ProhibitTimer and an sr-TransMax, where an SR_COUNTER is used for the scheduling process of the first wireless device. In another aspect, (a.1) if the logical channel scheduled by the UE is configured with a different SR for the SR configuration corresponding to the pending SR, or (a.2) if the logical channel scheduled by the UE is configured with the same SR configuration for the SR configuration corresponding to the pending SR configuration, and the sr-ProhibitTimer and SR_COUNTER corresponding to the UE-scheduled channel trigger the pending SR configuration, and (c) if the sr-ProhibitTimer is not running at the time of SR transmission, and (d) if SR_COUNTER < sr-TransMax, the sr-Prohibit timer is started, SR_COUNTER is incremented by 1, and the physical layer is instructed to signal the SR to the scheduling logical channel of the second wireless device. In yet another aspect, the second wireless device is configured to provide a sidelink grant received from the base station after receiving the SR configuration from the first wireless device, where the second wireless device is further configured to send an SR to the base station. In yet another aspect, the first wireless device is configured to associate one sr-ProbihitTimer and one SR_COUNTER to one SR configuration if the logical channel scheduled by the UE is configured via different SR configurations. In yet another aspect, the first wireless device is configured to associate one sr-PorhibitTimer and one SR_COUNTER to one SR configuration for each UE if the logical channel scheduled by the UE is configured via the same SR configuration.

[0011] In one aspect, a first wireless device receives a sidelink grant from a second wireless device and selects a destination for each new transmission based on the highest priority of the logical channel or the MAC CE of the logical channel and selects the data belonging to the selected destination to create a MAC PDU. In yet another aspect, the destination is one of the following: unicast, or broadcast or multicast. In yet another aspect, the sidelink grant is created by the second wireless device via the following: sensing, or partial sensing or random selection. In yet another aspect, the sidelink grant has been received by the second wireless device via the base station. In yet another aspect, the destination is selected based on the logical channel having a priority or MAC CE, where the logical channel is scheduled by the second wireless device providing the sidelink grant.

[0012] In one aspect, a first wireless device transmits an indication relating to transmission grants from one or more devices, wherein the one or more devices are configured to provide transmission grant capabilities to the first wireless device receiving transmission grant capabilities. In another aspect, if one of the one or more wireless devices is capable of scheduling only its own data, then sidelink grants are provided by one of the one or more wireless devices and can be used only by logical channels having data transmitted to one of the one or more wireless devices. In yet another aspect, if one of the one or more wireless devices is capable of scheduling both its own data and the data of the first wireless device, then sidelink grants are provided by one of the one or more wireless devices and can be used by all logical channels of the first wireless device. In yet another aspect, if one of the one or more wireless devices is unable to schedule, and the first wireless device finds another device to schedule all of its traffic, then sidelink grants are provided by one of the one or more wireless devices and can be used by logical channels having data transmitted to one of the one or more wireless devices.

[0013] In one aspect, a first wireless device broadcasts an auxiliary scheduling request and receives a response to the broadcast from a second wireless device, and establishes a unicast connection between the first and second wireless devices. In another aspect, the auxiliary scheduling request includes an indication that scheduling measurements for all traffic of the first wireless device will be provided or provided. In yet another aspect, the broadcast is a multicast within a device connected to the first wireless device. In yet another aspect, the first wireless device checks whether a device has a unicast link with the first wireless device and is capable of providing auxiliary scheduling information; if not, it sends the auxiliary scheduling request as a multicast within the first wireless device group, and if no response is received, it broadcasts the request. In yet another aspect, the response includes: (a) the second wireless device can provide an indication for scheduling all traffic of the first wireless device, or (b) the destination layer 2 ID of the second wireless device, or (c) a resource selection mode, including sensing or partial sensing or scheduling via a base station, or (d) a coverage status, including within or outside coverage, or (e) an RRC status, including RRC connected or RRC idle, or RRC inactive. In another aspect, a first wireless device receives multiple response messages from multiple wireless devices, wherein the first wireless device selects one of the multiple wireless devices to establish a unicast connection based on a sorting priority, wherein the multiple wireless devices include a second wireless device. In another aspect, the sorting priority is: (1) RRC connected, (2) RRC inactive, and then (3) RRC idle, wherein RRC connected is the highest priority, RRC inactive is the second highest priority, and RRC idle is the third highest priority. In another aspect, the sorting priority is: (1) sensing, and then (2) partial sensing, wherein sensing is the highest priority, and partial sensing is the second highest priority. In yet another aspect, the sorting priority is: (1) within coverage, and then (2) outside coverage, wherein within coverage is the highest priority, and outside coverage is the second highest priority. In another aspect, the second wireless device shall be selected in order of priority (first listed with the highest priority): (1) the head UE in the same group as the first wireless device, (2) the second wireless device in the same group as the first wireless device, and (3) the second wireless device that has no unicast or multicast connection with the first wireless device.

[0014] In one aspect, the first wireless device obtains resource authorization and performs logical channel priority ordering. In another aspect, the first wireless device obtains authorization from a base station. In yet another aspect, the first wireless device obtains authorization through its own creation. In yet another aspect, the first wireless device obtains authorization from a UE that can schedule for itself. In yet another aspect, the first wireless device obtains authorization from a UE that can schedule for itself and another UE.

[0015] In another aspect, the first wireless device selects a unicast, multicast, or broadcast logical channel having the highest priority or MAC CE among logical channels that satisfy certain conditions and are used for an authorized MAC CE associated with the SCI, wherein the conditions include: (a) the logical channel is configured or determined to be scheduled by the base station providing the authorization, or (b) the logical channel is configured or determined to be scheduled by the base station providing the authorization, or (c) the logical channel is configured or determined to be used by the first wireless device. In yet another aspect, the first wireless device selects a logical channel among logical channels belonging to the selected destination that satisfies all of the following conditions: (a) the logical channel is configured or determined to be scheduled by the second wireless device providing the authorization, (b) the logical channel is configured or determined to be scheduled by the base station providing the authorization, or (c) the logical channel is configured or determined to be used by the first wireless device.

[0016] In another aspect, the first wireless device was configured to use MAC CE.

[0017] In this disclosure, the sending and receiving of messages are performed by various devices, including MT, UE, and base station.

[0018] These and other aspects are described in this disclosure. Attached Figure Description

[0019] Figure 1 This illustrates a sample V2X communication system.

[0020] Figure 2 This explains the exchange of scheduling information.

[0021] Figure 3 This explains the scheduling information from the base station.

[0022] Figure 4 This describes the multiple UEs connected to the UE.

[0023] Figure 5 This indicates that UE-B is querying UE-A for scheduling information.

[0024] Figure 6 This explains something similar to Figure 5 The flowchart.

[0025] Figure 7 This explains something similar to Figure 5 The flowchart.

[0026] Figure 8 A flowchart illustrating the UE-A's transmission of scheduling information is provided.

[0027] Figure 9 The flowchart illustrates the process of UE-B sending scheduling configuration to UE-A.

[0028] Figure 10 This explains something similar to Figure 9 The flowchart.

[0029] Figure 11 The flowchart for UE-B sending SR is explained.

[0030] Figure 12 This describes UE-B using Logical Channel Priority (LCP).

[0031] Figure 13 This describes multiple UEs.

[0032] Figure 14 The flowchart illustrates how UE-B finds another UE-A with scheduling capabilities.

[0033] Figure 15 This indicates that UE-B is trying to find another UE to schedule traffic first.

[0034] Figure 16 The flowchart of LCP is explained.

[0035] Figure 17 Examples of wireless communication systems in which one or more embodiments of the present technology can be applied are illustrated.

[0036] Figure 18 This is a block diagram representation of a portion of a radio station according to one or more embodiments to which the present technology may be applied. Detailed Implementation

[0037] This disclosure relates to wireless systems. More specifically, it relates to communication between UEs for sidelink communication and for resource scheduling. Parameters are exchanged from one UE to another so that the UEs can be configured.

[0038] Figure 1 This is a block diagram of an example V2X communication system. In the LTE (Long Term Evolution) based V2X communication research organized by 3GPP, user-based devices (user equipment) can communicate using V2X communication between direct link / side link links. For example, data can be transmitted directly from the source UE to the target UE without being forwarded by the base station and core network, and can be transmitted directly from the source UE to the target UE via the air interface (PC5 interface), such as... Figure 1 As shown.

[0039] With the advancement of communication technology and the development of the automation industry, V2X communication scenarios have been further expanded and have higher performance requirements. 3GPP has established research on vehicle-to-everything (V2X) communication based on fifth-generation mobile communication technology (5G), including V2X communication based on the 5G air interface and V2X communication based on 5G direct links (side links).

[0040] For NR-based vehicle-to-everything (V2X) sidelink communication, PC5 interface RRC signaling interaction can be supported. Specifically, PC5 RRC signaling may include messages for the UE's transmission capabilities. This embodiment involves obtaining the capability information of the peer UE and interacting for PC5 UE capability information exchange to select sidelink transmission parameters. Furthermore, PC5 RRC signaling may not be transmitted without security protection, and this embodiment can provide a security protection mechanism for protecting PC5 RRC signaling at the access-stratum (AS) layer.

[0041] It should be understood that, as is known in the art, any type of UE can be used, and the specific hardware is not limited to the configuration described herein. It should also be understood that any configuration and number of networking devices can be used.

[0042] Figure 2 The exchange of scheduling information is illustrated. UE 202 transmits a request for scheduling information to UE 204 and receives scheduling information 206 from UE 204. The scheduling information request and response include information that includes any one of the following: (a) the scheduling capability of UE 204, or (b) the coverage status of UE 204, including being within or outside coverage, or (c) the RRC status of UE 204, including being idle, inactive, or connected, or (d) the transmission resource set of UE 204, including being pre-configured, configured by system information, or configured by the base station of UE 204, or (e) the coverage status of UE 204, or (f) the Radio Resource Control (RRC) status of UE 204. In another aspect, the scheduling information includes the capabilities of UE 204, including: (a) whether UE 204 can provide a resource pool, or (b) whether UE 204 can provide transmission grants, or (c) the transmission resource selection methods supported by UE 204, including random selection, sensing, partial sensing, or dynamic scheduling, or (d) whether UE 204 can provide transmission resources for UE 202 to send data to UE 204, or (e) whether UE 204 can provide transmissions for UE 204 to be sent to any destination. In yet another aspect, the scheduling information includes: PC5 RRC signaling, or PC5 MAC control element (MAC CE), or PC5 NAS signaling, or sidelink control information (SCI).

[0043] In an embodiment, UE 202 transmits a scheduling configuration to UE 204 and receives a configuration response message from UE 204. On the other hand, the scheduling configuration includes: (a) a resource pool configuration, or (b) service package information, or (c) service information, or (d) a scheduling request resource configuration, or (e) a radio bearer configuration, or (f) resource selection information including sensing parameters. On the other hand, UE 202 is connected to multiple devices, and UE 202 sends non-overlapping SR resource configurations to the multiple devices. On the other hand, the scheduling configuration includes: (a) a resource pool configuration, or (b) a scheduling request configuration, or (c) an obtained radio bearer configuration. The scheduling configuration is obtained via at least one of the following: pre-configuration, or system information or RRC signaling. On the other hand, the configuration response message includes: (a) a failure indication related to whether the corresponding configuration fails, or (b) a conflict indication related to whether the scheduling request resource conflicts with another device, or (c) a scheduling request resource configuration related to whether the SR resource configuration is recommended by UE 204.

[0044] In an embodiment, UE 202 has an SR configuration including sr-ProhibitTimer and sr-TransMax, where SR_COUNTER is used for the scheduling process of UE 202. This SR configuration can be received from other UEs or the base station. Here, (a.1) if the logical channel scheduled by the UE is configured with a different SR for the SR configuration corresponding to the pending SR, or (a.2) if the logical channel scheduled by the UE is configured with the same SR configuration for the SR configuration corresponding to the pending SR configuration, and the sr-ProhibitTimer and SR_COUNTER corresponding to the UE-scheduled channel trigger the pending SR configuration, and (c) if the sr-ProhibitTimer is not running at the time of SR transmission, and (d) if SR_COUNTER < sr-TransMax, then the sr-Prohibit timer is started, SR_COUNTER is incremented by 1, and the physical layer is instructed to signal the SR to UE 204. In an embodiment, UE 202 is configured to associate one sr-PorhibitTimer and one SR_COUNTER to one SR configuration of each UE if the logical channels scheduled by the UE are configured via the same SR configuration. In yet another embodiment, UE 302 is configured to associate one sr-ProbihitTimer and one SR_COUNTER to one SR configuration if the logical channels scheduled by the UE are configured via different SR configurations.

[0045] In one aspect, UE 202 receives a sidelink grant from UE 204 and selects a destination that has the highest priority or MAC CE among logical channels satisfying specific conditions and MAC CE. In one embodiment, UE 202 selects a logical channel belonging to the selected destination and satisfying specific conditions to create a MAC PDU. In another aspect, the destination is associated with one of the following: unicast, broadcast, or multicast. In yet another aspect, the sidelink grant is created by UE 204 via sensing, partial sensing, or random selection. In yet another aspect, the sidelink grant has been received by UE 204 via a base station. In yet another aspect, the specific condition is: a logical channel scheduled by the UE or base station providing the sidelink grant, or by itself.

[0046] Figure 3 The diagram illustrates scheduling information from a base station. UE 302 receives a request for scheduling information from base station 306 before transmitting the request to UE 304. After receiving the scheduling information from UE 304, UE 302 sends scheduling information 308 of UE 304 to base station 306. UE 302 may also send a list of scheduling information for more than one device. In another embodiment, UE 304 is configured to provide a sidelink grant received from base station 306 after receiving an SR configuration from UE 302, wherein UE 304 is also configured to send an SR to base station 306.

[0047] Figure 4 Multiple UEs connected to a UE are illustrated. In one embodiment, sidelink granting is provided by UE 404, UE 406, or UE 406. In another embodiment, if UE 404, UE 406, or UE 406 is capable of scheduling only their own data, then granting is used by logical channels having data respectively transmitted to UE 404, UE 406, or UE 406. In yet another embodiment, if UE 404, UE 406, or UE 406 is capable of scheduling their own data and data from other UEs 402, then sidelink granting is provided by UE 404, UE 406, or UE 406, and can be used by all logical channels of UE 402. In another embodiment, if UE 404, UE 406 or UE 406 cannot be scheduled, and UE 402 finds another device to schedule all traffic of UE 402, then the sidelink grant is provided by UE 404, UE 406 or UE 406 and can be used by a logical channel having data transmitted to UE 404, UE 406 or UE 406.

[0048] In another embodiment, UE 402 broadcasts an auxiliary scheduling request and receives a response to the broadcast from one of UE 404, UE 406, or UE 406, and establishes a unicast connection with the responding UE. In another embodiment, the scheduling request includes an indication that scheduling measurements for all traffic of UE 402 will be provided or will be provided. In yet another aspect, the broadcast is a multicast within a device connected to UE 402. In yet another aspect, UE 402 checks whether UE 404, UE 406, or UE 406 has a unicast link with UE 202 and is capable of providing auxiliary scheduling information, and if not, sends the auxiliary scheduling request as a multicast within UE 402's group (UE 404, UE 406, or UE 406), and broadcasts the request if no response is received. A response from any UE includes any of the following: (a) the UE can provide an indication of scheduling for all traffic for UE 202, or (b) the UE’s destination layer 2 ID, or (c) the resource selection mode, including sensing or partial sensing or scheduling via the base station, or (d) the coverage status, including within or outside the coverage area, or (e) the RRC status, including RRC connected or RRC idle or RRC inactive.

[0049] In some embodiments, UE 402 receives multiple response messages from UE 404, UE 406, and UE 406. Here, UE 402 selects one of UE 404, UE 406, or UE 406 to establish a unicast connection based on ordered priorities. The priorities may be: (1) RRC connected, (2) RRC inactive, and then (3) RRC idle, or may be: (1) sensed, and then (2) partially sensed, wherein sensed is the highest priority and partially sensed is the second highest priority, or the ordered priorities may be: (1) within coverage, and then (2) outside coverage, wherein within coverage is the highest priority and outside coverage is the second highest priority. In yet another embodiment, UE 404, UE 406, or UE 406 shall be selected in order of priority (first listed with the highest priority): (1) the head UE in the same group as UE 402, (2) UE 404, UE 406, or UE 406 in the same group as UE 406, and (3) UE 404, UE 406, or UE 406 that has no unicast or multicast connection to UE 402.

[0050] In one embodiment, UE 402 obtains resource grants and performs logical channel priority ordering. In another embodiment, UE 402 obtains grants from a base station. In yet another embodiment, UE 402 obtains grants via its own self-creation. In yet another aspect, UE 402 obtains grants from UE 404, UE 406, or UE 406 that can schedule for itself. In yet another aspect, UE 402 obtains grants from a UE that can schedule for itself and another UE.

[0051] In one embodiment, UE 402 selects a destination associated with unicast, multicast, or broadcast, having a logical channel with the highest priority or MACCE among logical channels that satisfy specific conditions and a MAC CE (if any) for authorization associated with the SCI, wherein the conditions include: (a) the logical channel is configured or determined by the authorization-providing UE 404, UE 406, or UE 406; or (b) the logical channel is configured or determined to be scheduled by the authorization-providing base station; or (c) the logical channel is configured or determined to be used by UE 402. In another embodiment, UE 402 selects a logical channel among logical channels belonging to the selected destination that satisfies all of the following conditions: (a) the logical channel is configured or determined to be scheduled by the authorization-providing UE 404, UE 406, or UE 406; (b) the logical channel is configured or determined to be scheduled by the authorization-providing base station; or (c) the logical channel is configured or determined to be used by UE 402. In this embodiment, UE 402 is configured to use a MAC CE.

[0052] Figure 5 The diagram illustrates UE-B querying UE-A for scheduling information. In step 502, UE-B sends a scheduling information query request to UE-A. In step 504, UE-B receives scheduling information from UE-A.

[0053] In this embodiment, the scheduling information query request includes any one of the following: the scheduling capability of UE-A, or the coverage status of UE-A: within coverage area, outside coverage area; or the RRC status of UE-A: idle, inactive, connected; or the transmission resource set of UE-A is (pre)configured, configured by system information, or configured by the base station of UE-A. In this embodiment, the scheduling capability of UE-A includes any one of the following:

[0054] Can UE-A provide a resource pool?

[0055] • Whether UE-A can provide transport authorization.

[0056] • UE-A supports the following transmission resource selection methods: random selection, sensing, partial sensing, and base station dynamic scheduling.

[0057] Can UE-A provide transmission resources for UE-B to send data to UE-A?

[0058] Can UE-A provide transmission resources for UE-B to send data to any UE?

[0059] In this embodiment, the response information regarding step 504 may include any of the following:

[0060] UE-A's scheduling capabilities

[0061] • UE-A coverage status: Within coverage area, Outside coverage area

[0062] UE-A's RRC status: Idle, Inactive, Connected

[0063] • The transmission resource set of UE-A is (pre)configured, either by system information or by the base station of UE-A.

[0064] · UE-A Coverage Status

[0065] · UE-A's RRC status

[0066] In this embodiment, the scheduling capability of UE-A may include:

[0067] Can UE-A provide a resource pool?

[0068] • Whether UE-A can provide transport authorization.

[0069] • UE-A supports the following transmission resource selection methods: random selection, sensing, partial sensing, and base station dynamic scheduling.

[0070] Can UE-A provide transmission resources for UE-B to send data to UE-A?

[0071] Can UE-A provide transmission resources for UE-B to send data to any UE?

[0072] In the embodiment, UE-B receives information in any of the following ways: PC5 RRC signaling, PC5 MAC CE, PC5 NAS signaling, SCI.

[0073] Figure 6 It shows something similar to Figure 5 The flowchart is as follows. However, before step 602, there is step 606, in which UE-B receives a scheduling information query request from UE-A from the gNB. After step 602, the content of the scheduling information is the same as that of the user. Figure 5 The described process is similar.

[0074] Figure 7It shows something similar to Figure 5 The flowchart is shown. However, after step 704, in step 708, UE-B sends the scheduling information of UE-A to gNB.

[0075] In one embodiment, UE-B sends a list that includes scheduling information for multiple UEs.

[0076] In this embodiment, the scheduling information includes any one of the following:

[0077] UE-A's scheduling capabilities

[0078] • UE-A coverage status: Within coverage area, Outside coverage area

[0079] UE-A's RRC status: Idle, Inactive, Connected

[0080] • The transmission resource set of UE-A is (pre)configured, either by system information or by the base station of UE-A.

[0081] · UE-A Coverage Status

[0082] · UE-A's RRC status

[0083] In this embodiment, the scheduling capability of UE-A includes any of the following:

[0084] Can UE-A provide a resource pool?

[0085] • Whether UE-A can provide transport authorization.

[0086] • UE-A supports the following transmission resource selection methods: random selection, sensing, partial sensing, and base station dynamic scheduling.

[0087] Can UE-A provide transmission resources for UE-B to send data to UE-A?

[0088] Can UE-A provide transmission resources for UE-B to send data to any UE?

[0089] Figure 8 A flowchart illustrating UE-A sending scheduling information is provided. In step 802, UE-A receives a scheduling information query request from the gNB. In step 804, UE-A sends a scheduling information query response. It should be understood that the scheduling information query request and response can be any publicly available content.

[0090] Figure 9 The flowchart illustrates a process where UE-B sends scheduling configuration to UE-A. In step 902, UE-B sends the scheduling configuration to UE-A. In step 904, UE-B receives a configuration response message from UE-A.

[0091] In this embodiment, the scheduling configuration includes any one of the following: resource pool configuration.

[0092] • Service Package Information (UAI)

[0093] Service Information (SUI)

[0094] • Scheduling request resource configuration

[0095] Radio bearer configuration

[0096] • Resource selection information (sensing parameters)

[0097] In another embodiment, when UE-B connects to multiple UE-A, UE-B sends non-overlapping SR resource configurations to different UE-A.

[0098] In another embodiment, the resource pool configuration, scheduling request configuration, and radio bearer configuration can be obtained by at least one of the following methods: (pre)configuration, system information, and RRC signaling.

[0099] In this embodiment, the configuration response message includes any one of the following:

[0100] • Fault indication: Has the corresponding configuration failed?

[0101] • Conflict indication: Whether the scheduled resource request conflicts with other UEs.

[0102] • Scheduling request resource configuration: UE-A recommended SR resource configuration

[0103] In one embodiment, the UE-B may send a configuration response message to the base station.

[0104] Figure 10 It shows something similar to Figure 9 The flowchart is shown, but it includes step 1006 whereby the UE-A sends a report on the scheduling configuration to the gNB.

[0105] Figure 11 A flowchart illustrating the UE-B sending an SR is shown. In step 1102, the UE-B receives an SR configuration including the following parameters. In step 1104, the UE-B associates an sr-ProbihitTimer and an SR_COUNTER with an SR configuration. In step 1106, if at least one SR is pending, the UE-B should perform an action for each pending SR.

[0106] In this embodiment, the SR configuration includes sr-ProhibitTimer and sr-TransMax. The following UE variable is used in the UE-B scheduling request procedure: SR_COUNTER.

[0107] In one embodiment, if logical channels scheduled by different UE-A are configured with different SR configurations, then UE-B associates an sr-ProbihitTimer and an SR_COUNTER with one SR configuration. In another embodiment, if logical channels scheduled by different UE-A are configured with the same SR configuration, then UE-B associates an sr-ProbihitTimer and an SR_COUNTER with one SR configuration for each UE-A.

[0108] In this embodiment, the following actions are performed:

[0109] • If logical channels scheduled by different UE-A are configured with different SR configurations, the SR configuration corresponding to the pending SR is: or;

[0110] • If logical channels scheduled by different UE-A are configured with the same SR configuration, the SR configuration corresponding to the pending SR is used, and the sr-ProhibitTimer and SR_COUNTER corresponding to the UE-A that schedules the logical channel are used to trigger the pending SR:

[0111] • And if sr-ProhibitTimer is not running during SR transmission:

[0112] And if SR_COUNTER <sr-TransMax:

[0113] • Then the physical layer is instructed to send a signal to the UE-A that is scheduling a logical channel that triggers an SR on a valid SR resource to notify the SR;

[0114] Then increment SR_COUNTER by 1;

[0115] Then start sr-ProhibitTimer.

[0116] In another embodiment, when UE-A determines that it is providing a sidelink grant received from the base station, UE-A sends an SR to the base station after receiving the SR from UE-B.

[0117] Figure 12The illustration shows UE-B using Logical Channel Priority (LCP). In step 1202, UE-B receives an SL grant from UE-A. In step 1204, UE-B selects a destination associated with one of unicast, multicast, or broadcast, having a logical channel with the highest priority or MAC CE among logical channels that satisfy all of the following conditions and MAC CE (if any) for the SL grant associated with the SCI: this logical channel is scheduled by UE-A, which provided the SL grant. In step 1206, UE-B selects data belonging to the selected destination to create a MAC PDU.

[0118] Figure 13 Multiple UEs are shown.

[0119] In this embodiment, UE-B determines which logical channel will be scheduled by a specific UE-A according to the following rules:

[0120] • If UE-A is able to schedule only its own data, then the sidelink license provided by UE-A can only be used by logical channels that have data to be transmitted to UE-A.

[0121] • If UE-A is able to schedule its own data and the data of other UEs, then the sidelink license provided by UE-A can be used by all logical channels of UE-B.

[0122] If UE-A cannot be scheduled, and UE-B finds another UE-A to schedule all of UE-B's traffic, then the sidelink grant provided by UE-A can be used by the logical channel that has data to be transmitted to UE-A.

[0123] If UE-A cannot be scheduled, and UE-B cannot find another UE-A that can schedule all of UE-B's traffic, and UE-B

[0124] In this embodiment, UE-A4 only provides auxiliary resources for other UEs, and UE-B wants to transmit data to UE-A1, A2, and A3, but UE-B has no data to transmit to UE-A4. Here:

[0125] The logical channel in UE-B is used to store data that will be transmitted to UE-A1 with destination 1.

[0126] The logical channel in UE-B is used to store data that will be transmitted to UE-A1 with destination 2.

[0127] The logical channel in UE-B is used to store data that will be transmitted to UE-A1 with destination 3.

[0128] The following are exemplary scenarios.

[0129] Scene 1: UE-B wants to transmit data to UE-A1, A2, and A3.

[0130] UE-A1, A2, and A3 cannot be scheduled, but UE-A4 can schedule itself and other UEs. Therefore, UE-B can determine that data on logical channels with destinations 1, 2, and 3 will be scheduled by UE-A4.

[0131] Scene 2: UE-B wants to transmit data to UE-A1, A2, and A3.

[0132] UE-A1 and A2 cannot be scheduled, but UE-A3 can schedule itself and other UEs. Therefore, UE-B can determine that data with logical channels to destinations 1, 2, and 3 will be scheduled by UE-A3.

[0133] Scenario 3: UE-B wants to transmit data to UE-A1, A2, and A3.

[0134] UE-A1 and A2 can schedule data for themselves, but UE-A3 cannot. UE-A4 can schedule data for itself and other UEs. Therefore, UE-B can determine that data on a logical channel with destination 1 will be scheduled by UE-A. Furthermore, UE-B can determine that data on a logical channel with destination 2 will be scheduled by UE-A2. Additionally, UE-B can determine that data on a logical channel with destination 3 will be scheduled by UE-A4.

[0135] Figure 14 The flowchart illustrates how UE-B finds another UE-A with scheduling capabilities. In step 1402, UE-B broadcasts an auxiliary scheduling request. In step 1404, UE-A sends a response message. In step 1406, UE-B establishes a unicast connection with UE-A.

[0136] In one embodiment, UE-B multicasts the auxiliary scheduling request within the group of all UE-Bs. In another embodiment, UE-B first checks whether it has a unicast link with a UE-B capable of providing auxiliary scheduling. If not, it multicasts the auxiliary scheduling request within the group of all UE-Bs, and if no response is received, UE-B broadcasts the request.

[0137] In one embodiment, the auxiliary scheduling request includes one of the following: providing an indication for auxiliary scheduling of traffic for all UE-Bs.

[0138] Regarding step 1404, the response information includes: an indication to provide auxiliary scheduling for traffic of all UE-Bs, and the destination layer 2 ID of UE-A for unicast links; resource selection mode: sensing / partial sensing / scheduling via base station; coverage status: within coverage, outside coverage; or RRC status: RRC connected, RRC idle, RRC inactive.

[0139] Regarding step 1406, in one embodiment, UE-B can receive multiple response messages from UE-A, and UE-B selects one UE-A to establish a connection with. UE-A should be selected in order of priority (highest priority listed first): RRC connected, RRC inactive, RRC idle. In another embodiment, UE-A should be selected in order of priority (highest priority listed first): sensed, partially sensed. In one embodiment, UE-A should be selected in order of priority (highest priority listed first): within coverage area, outside coverage area. In one embodiment, UE-A should be selected in order of priority (highest priority listed first): head UE in the same group as UE-B, UE-A in the same group as UE-B, UE-A with no unicast or multicast link connection to UE-A.

[0140] In this embodiment, UE-B randomly selects a UE-A to establish a unicast connection.

[0141] Figure 15 The illustration shows UE-B attempting to find another UE to schedule traffic first. In step 1502, UE-B receives an indication from the base station. In step 1504, UE-B sends an indication to the base station to indicate that the corresponding data will be scheduled by the base station, sensed by UE-B, or scheduled according to configuration.

[0142] Regarding step 1502, in the embodiment, the instructions include:

[0143] If no UE-A can be scheduled, will the traffic of UE-B be scheduled by the base station?

[0144] If no UE-A can be scheduled, will UE-B's traffic be automatically sensed?

[0145] Will the traffic of UE-B be scheduled by UE-A?

[0146] In another embodiment, the instruction will be

[0147] • Per Priority / Logical Channel / Per DRB / Destination: Indicates whether data with a specified priority / logical channel / per DRB / destination will be scheduled by the base station, sensed by the UE-B itself, or scheduled by the UE-A.

[0148] • Each CBR: Indicates whether the data will be scheduled by the base station, sensed by the UE-B itself, or scheduled by the UE-A.

[0149] • Each resource pool: Indicates whether the resource pool supports: UE-B being scheduled by the base station, sensed by UE-B itself, or scheduled by UE-A.

[0150] In another embodiment, the selection of the indication, whether it is scheduled by the base station, sensed by the UE-B itself, or scheduled by the UE-A, depends on the specific implementation of the UE-B.

[0151] Figure 16 A flowchart for LCP is shown.

[0152] In step 1602, UE-B is granted authorization. In step 1604, UE-B performs logical channel priority sorting.

[0153] In this embodiment, UE-B is authorized from: a base station created by UE-B, a UE-A that can schedule for itself, and a UE-A that can schedule for itself and another UE.

[0154] In this embodiment, logical channel priority sorting is performed according to the following:

[0155] • Select a destination associated with one of unicast, multicast, or broadcast, having the highest priority or logical channel among logical channels that meet all of the following conditions and the MAC CE (if any) authorized for association with SCI:

[0156] • The logical channel is configured or determined to be scheduled by the UE-A that provides the license.

[0157] • Logical channels are configured or determined to be scheduled by the base station providing the license.

[0158] • Logical channels are configured or determined to use authorizations they create themselves.

[0159] In this embodiment, logical channel priority sorting is performed according to the following:

[0160] • Select a logical channel from the logical channels belonging to the selected destination that meets all of the following conditions:

[0161] • The logical channel is configured or determined to be scheduled by the UE-A that provides the license.

[0162] • Logical channels are configured or determined to be scheduled by the base station providing the license.

[0163] • Logical channels are configured or determined to use authorizations they create themselves.

[0164] It should be understood that the currently disclosed non-logic channel embodiments can be applied to MAC CE.

[0165] Figure 17 An example of a wireless communication system 1700 in which one or more embodiments of the present technology can be applied is shown. The wireless communication system 1700 may include one or more base stations (BS) 1705a, 1705b, one or more wireless devices 1710a, 1710b, 1710c, 1710d, and a core network 1725. Base stations 1705a and 1705b may provide wireless services to wireless devices 1710a, 1710b, 1710c, and 1710d in one or more wireless sectors. In some embodiments, base stations 1705a and 1705b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

[0166] The core network 1725 can communicate with one or more base stations 1405a and 1705b. The core network 1725 provides connectivity with other wireless and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1710a, 1710b, 1710c, and 1710d. The first base station 1705a can provide wireless services based on a first radio access technology, while the second base station 1705b can provide wireless services based on a second radio access technology. Base stations 1705a and 1705b may be located in the same location or may be installed separately in the field, depending on the deployment scenario. Wireless devices 1710a, 1710b, 1710c, and 1710d can support a variety of different radio access technologies. The technologies and embodiments described in this document can be implemented by base stations of the wireless devices described in this document.

[0167] Figure 18This is a block diagram representation of a portion of a radio station according to one or more embodiments of the present technology to which it may be applied. Radio station 1805, such as a base station or wireless device (or UE) or MT, may include processor electronics 1810, such as a microprocessor, which implements one or more wireless technologies presented in this document. Radio station 1805 may include transceiver electronics 1815 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as antenna 1820. Radio station 1805 may include additional communication interfaces for transmitting and receiving data. Radio station 1805 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, processor electronics 1810 may include at least a portion of transceiver electronics 1815. In some embodiments, at least some of the disclosed technologies, modules, or functions are implemented using radio station 1805. In some embodiments, radio station 1805 may be configured to perform the methods described herein.

[0168] It will be understood that this document discloses techniques that can be embodied in various embodiments and configurations. It should be understood that concepts from some embodiments can be used in other embodiments. The disclosure and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuits, or in computer software, firmware, or hardware (including the structures disclosed in this document and their structural equivalents), or in combinations of one or more of them. The disclosure and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by or control of the operation of a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition of substances affecting machine-readable propagation signals, or one or more combinations thereof. The term "data processing apparatus" covers all means, devices, and machines for processing data, including, for example, a programmable processor, a computer, or a plurality of processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, for example, code constituting processor firmware, a protocol stack, a database management system, an operating system, or one or more combinations thereof. A propagation signal is a man-made signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0169] Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units suitable for use in a computing environment. A computer program does not necessarily correspond to a document in a documenting system. A program can be stored as part of a document containing other programs or data (e.g., one or more scripts stored in a markup language document), in a single document dedicated to the program in question, or in multiple coordinating documents (e.g., a document storing one or more modules, subroutines, or code sections). A computer program can be deployed to be executed on one or more computers located at a single site or distributed across multiple sites interconnected by a communications network.

[0170] The processes and logic flows described in this document can be executed by one or more programmable processors that execute one or more computer programs to perform functions by manipulating input data and producing outputs. Processing and logic flows can also be executed by dedicated logic circuitry, and the devices can be implemented as dedicated logic circuitry, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits).

[0171] For example, processors suitable for executing computer programs include, for instance, both general-purpose and special-purpose microprocessors, and any one or more processors in any kind of digital computer. Typically, a processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or operatively coupled to receive data from or transfer data to one or more mass storage devices for storing data, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. The processor and memory may be supplemented by or incorporated into special-purpose logic circuitry.

[0172] While this patent document contains numerous details, these details should not be construed as limiting the scope of any invention or the scope of any possible claims, but rather as descriptions of features specific to particular embodiments of a particular invention. Certain features described in this patent document within the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as functioning in certain combinations, and even initially claimed in this way, in some cases one or more features from a claimed combination may be removed from the combination, and the claimed combination may refer to a sub-combination or a variation of a sub-combination.

[0173] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or requiring all shown operations to be performed to achieve the desired result. Furthermore, the separation of various system components in the embodiments described in this patent document should not be construed as requiring such separation in all embodiments.

[0174] Only some implementation methods and examples are described, and other implementation methods, enhancements and variations can be made based on the content described and illustrated in this patent document.

Claims

1. An information transmission method performed by a first wireless device, comprising: The first wireless device receives a request for scheduling information from the second wireless device. The scheduling information is transmitted from the first wireless device to the second wireless device. The scheduling information includes the scheduling capabilities of the first wireless device, which includes the transmission resource selection methods supported by the first wireless device: random selection or partial sensing. Wherein, the first wireless device and the second wireless device are peer wireless devices. The first wireless device receives the scheduling configuration from the second wireless device; and The first wireless device sends a configuration response message to the second wireless device. The configuration response message includes a scheduling request resource configuration related to whether the scheduling request SR resource configuration is recommended by the first wireless device.

2. The method according to claim 1, wherein, The scheduling information also includes: PC5 RRC signaling, or PC5 MAC control element MAC CE, or PC5 NAS signaling, or sidelink control information SCI.

3. The method according to claim 1, wherein, Before the second wireless device transmits the request for scheduling information to the first wireless device, the second wireless device is configured to receive a request for scheduling information from the base station.

4. The method according to claim 1, wherein, The second wireless device is configured to send the scheduling information of the first wireless device to the base station after receiving the scheduling information from the first wireless device.

5. The method according to claim 4, wherein, The second wireless device is configured to send a list that includes scheduling information for more than one device.

6. The method according to claim 1, wherein, The first wireless device is a first user equipment (UE), and the second wireless device is a second UE.

7. The method according to claim 1, wherein, The second wireless device is a base station, and the first wireless device is a UE.

8. The method according to claim 1, wherein, The scheduling configuration includes: resource pool configuration, or service package information, or service information, or scheduling request (SR) resource configuration, or radio bearer configuration, or resource selection information including sensing parameters, or scheduling request configuration, or radio bearer configuration.

9. The method according to claim 1, wherein, The second wireless device is configured to connect to multiple devices, and the second wireless device is configured to send non-overlapping SR resource configurations to the multiple devices.

10. The method according to claim 1, wherein, The scheduling configuration is obtained via at least one of the following: pre-configuration, system information, or RRC signaling.

11. The method according to claim 1, wherein, The configuration response message also includes: a failure indication related to whether the corresponding configuration has failed, or a conflict indication related to whether the scheduled resource conflicts with another device.

12. The method according to claim 1, wherein, The second wireless device is configured to transmit the configuration response message to the base station.

13. The method of claim 1, further comprising sending the scheduling configuration to the base station at the first wireless device.

14. The method according to claim 1, wherein, The second wireless device is configured to receive an SR configuration including sr-ProhibitTimer and sr-TransMax, wherein SR_COUNTER is used in the scheduling process of the second wireless device.

15. The method according to claim 14, wherein, a.1 If the logical channel scheduled by the UE is configured with a different SR for the SR configuration corresponding to the pending SR, or a.2 if the logical channel scheduled by the UE is configured with the same SR configuration of the SR configuration corresponding to the pending SR configuration, and the sr-ProhibitTimer and SR_COUNTER corresponding to the UE scheduling the channel trigger the pending SR configuration, and c if the sr-ProhibitTimer is not running at the time of SR transmission, and d if the SR_COUNTER < sr-TransMax, then the sr-Prohibit timer is started, the SR_COUNTER is incremented by 1, and the physical layer is instructed to signal the SR to the scheduled logical channel of the first wireless device.

16. The method of claim 14, wherein, The first wireless device is configured to provide a sidelink grant received from the base station after receiving the SR configuration from the second wireless device, wherein the first wireless device is further configured to send the SR to the base station.

17. The method of claim 14, wherein, The second wireless device is configured to associate one sr-ProbihitTimer and one SR_COUNTER to one SR configuration if the logical channel scheduled by the UE is configured via different SR configurations.

18. The method according to claim 14, wherein, The second wireless device is configured to associate one sr-PorhibitTimer and one SR_COUNTER to one SR configuration for each UE if the logical channel scheduled by the UE is configured via the same SR configuration.

19. A wireless communication device, comprising a processor and a memory, the processor being configured to read instructions from the memory to implement the method according to any one or more of claims 1-18.

20. An information transmission method performed by a second wireless device, comprising: Transmitting a request for scheduling information from the second wireless device to the first wireless device; Receiving the scheduling information at the second wireless device from the first wireless device, wherein the scheduling information includes the scheduling capabilities of the first wireless device, and the scheduling capabilities of the first wireless device include the transmission resource selection methods supported by the first wireless device: random selection, or partial sensing, and wherein the first wireless device and the second wireless device are peer wireless devices, Receiving, by the first wireless device, a scheduling configuration from the second wireless device; and Sending, by the first wireless device, a configuration response message to the second wireless device, wherein the configuration response message includes a scheduling request resource configuration related to whether the scheduling request SR resource configuration is recommended by the first wireless device.

21. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory to cause the wireless communication device to perform the following operations: Receiving a request for scheduling information from a second wireless device; The scheduling information is sent to the second wireless device, wherein the scheduling information includes the scheduling capabilities of the wireless device, and the scheduling capabilities of the wireless device include the transmission resource selection methods supported by the wireless device: random selection or partial sensing. In this context, the first wireless device and the second wireless device are peer wireless devices. The first wireless device receives the scheduling configuration from the second wireless device; and The first wireless device sends a configuration response message to the second wireless device. The configuration response message includes a scheduling request resource configuration related to whether the scheduling request SR resource configuration is recommended by the first wireless device.

Images