Wireless device sidelink information

Abstract

The first wireless device receives from the second wireless device at least one parameter indicating assistance information for time-domain resource allocation for a sidelink between the first wireless device and the second wireless device. The first wireless device transmits to the first base station a message including the at least one parameter. In one embodiment, the method includes receiving, by the first wireless device from the first base station, a resource grant indicating at least one radio resource for the sidelink, where the time-domain resource allocation for the at least one radio resource is based on the at least one parameter.

Description

【Background Art】 【0001】 Cross - Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 62 / 886,291, filed on August 13, 2019, which is hereby incorporated by reference in its entirety. 【Summary of the Invention】 【Means for Solving the Problems】 【0002】 In the present disclosure, various embodiments are presented as examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made without departing from the scope. Indeed, after reading the specification, methods of implementing alternative embodiments will be apparent to those skilled in the relevant art. The present embodiments should not be limited by any of the exemplary embodiments. Embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of the present disclosure. Figures highlighting functions and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, any action listed in any flowchart can be rearranged or used only optionally in some embodiments. The present invention provides, for example, the following: (Item 1) Receiving from a second wireless device by a first wireless device at least one sidelink message containing gap request information, wherein the gap request information indicates at least one period during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink. The first wireless device transmits to the first base station at least one uplink wireless resource control message, which includes the gap request information of the second wireless device. The first base station receives a resource authorization indicating a sidelink radio resource based on the gap request information via the first wireless device, A method comprising transmitting a transport block via the sidelink radio resource to the second wireless device by the first wireless device. (Item 2) The second wireless device receives from the first wireless device at least one parameter indicating at least one period of time during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink, The first wireless device transmits at least one parameter to the first base station, Receiving resource permission indicating the sidelink radio resources from the first base station by the first radio device, wherein the time-domain resource allocation of the radio resources is received based on the at least one parameter, A method comprising transmitting a transport block via the sidelink's wireless resources to the second wireless device by the first wireless device. (Item 3) The second wireless device receives from the first wireless device at least one parameter indicating at least one period of time during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink, The first wireless device transmits at least one parameter to the first base station, A method comprising receiving a resource permission indicating the sidelink radio resources from the first base station by the first radio device, wherein the time-domain resource allocation of the radio resources is based on the at least one parameter. (Item 4) The second wireless device receives from the first wireless device at least one parameter indicating at least one period of time during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink, A method comprising transmitting a message containing the at least one parameter to a first base station using the first wireless device. (Item 5) The second wireless device receives from the first wireless device at least one parameter indicating information supporting time-domain resource allocation by the first base station for a side link between the first wireless device and the second wireless device, The first wireless device transmits the at least one parameter to the first base station, A method comprising receiving a resource permission from the first base station by the first radio device indicating at least one radio resource of the sidelink, wherein a time-domain resource allocation of the at least one radio resource is received based on the at least one parameter. (Item 6) The second wireless device receives from the first wireless device at least one parameter indicating information supporting the time-domain resource allocation of the side link between the first wireless device and the second wireless device, A method comprising transmitting a message containing the at least one parameter to a first base station using the first wireless device. (Item 7) The method according to item 6, wherein the support information for time-domain resource allocation is for time-domain resource allocation by the first base station. (Item 8) The method according to any one of items 6 to 7, wherein the support information indicates at least one period during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink. (Item 9) The first wireless device further includes receiving a resource permission from the first base station indicating at least one wireless resource of the sidelink, wherein the time-domain resource allocation of the at least one wireless resource is determined according to any one of items 6 to 8, based on the at least one parameter. (Item 10) The method according to item 9, further comprising transmitting a transport block via the at least one wireless resource of the sidelink to the second wireless device by the first wireless device. (Item 11) The method according to any one of items 9 to 10, wherein the resource authorization includes at least one radio resource control configuration message indicating at least one configured authorized resource based on the support information, and the at least one configured authorized resource includes the at least one radio resource of the side link. (Item 12) The method according to any one of items 9 to 11, wherein the resource authorization includes at least one wireless resource control configuration message indicating a sidelink resource pool based on the support information, and the sidelink resource pool includes the at least one wireless resource of the sidelink. (Item 13) The method according to any one of items 9 to 12, further comprising transmitting a buffer status report or scheduling request to the first base station by the first wireless device, wherein the receipt of the resource permission is in response to the buffer status report or scheduling request. (Item 14) The method according to any one of items 6 to 13, wherein the message includes a wireless resource control message. (Item 15) The method according to any one of items 6 to 14, further comprising receiving a radio resource control information request message for the support information of the second radio device from the first base station by the first radio device, wherein the message is based on the radio resource control information request message. (Item 16) The aforementioned wireless resource control information request message is: The device identifier of the second wireless device, A destination identifier indicating the second wireless device, The bearer identifier of the sidelink bearer associated with the second wireless device, The logical channel identifier of the sidelink logical channel associated with the second wireless device, The quality of service (QoS) flow identifier of the sidelink QoS flow associated with the second wireless device, or The method described in item 15, which includes at least one of the priority levels. (Item 17) The first wireless device receives network information from the second wireless device, wherein the network information is The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool index of the resource pool used by the second wireless device, The zone identifier of the zone in which the second wireless device is located, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, or Receiving includes at least one of the priority information of the synchronization reference source in the serving cell of the second wireless device, The method according to any one of items 15 to 16, further comprising transmitting the network information of the second wireless device to the first base station using the first wireless device. (Item 18) The wireless resource control information request message is the method described in item 17, based on the network information. (Item 19) The first wireless device further includes transmitting a side-link information request message for the support information to the second wireless device, wherein the at least one parameter is the method according to any one of items 6 to 18, based on the side-link information request message. (Item 20) The method according to item 19, wherein the transmission of the sidelink information request message is based on a radio resource control information request message from the first base station. (Item 21) The aforementioned side link information request message is The device identifier of the second wireless device, A destination identifier indicating the second wireless device, The bearer identifier of the sidelink bearer associated with the second wireless device, The logical channel identifier of the sidelink logical channel associated with the second wireless device, The quality of service (QoS) flow identifier of the sidelink QoS flow associated with the second wireless device, or The method described in any one of items 19-20, including at least one of the priority levels. (Item 22) The first wireless device controls the PC5 wireless resource with the second wireless device. The method according to any one of items 6 to 21, further comprising establishing a connection and receiving the at least one parameter based on the PC5 wireless resource control connection. (Item 23) Receiving at least one of the aforementioned parameters PC5 Wireless Resource Control Message, Direct communication request message, Direct communication response message, or The method according to any one of items 6 to 22, comprising receiving the at least one parameter via at least one sidelink message which includes at least one functional information message. (Item 24) The method according to any one of items 6 to 23, further comprising determining the traffic pattern of packets to be transmitted or received by the second wireless device, wherein the supporting information is based on the traffic pattern of the packets. (Item 25) The method according to item 24, further comprising receiving resource scheduling information from a network node by the second wireless device, and determining the traffic pattern based on the resource scheduling information. (Item 26) The aforementioned network node, Second base station, A third wireless device, or The method of item 25, comprising at least one of the first wireless devices. (Item 27) Through the time domain gap associated with the aforementioned support information, the second wireless device provides at least one transport block, Second base station, A third wireless device, or The method according to any one of items 6 to 26, further comprising transmitting to at least one of the first wireless devices. (Item 28) The second wireless device, via the time-domain gap associated with the aforementioned support information, Second base station, or The method according to any one of items 6 to 27, further comprising receiving at least one transport block to at least one third wireless device. (Item 29) The aforementioned support information, Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, Priority information of the synchronization reference source in the serving cell of the second wireless device, or The method described in any one of items 6 to 28, which indicates at least one of the bearer identifiers of a sidelink bearer. (Item 30) The method according to any one of items 6 to 29, wherein the support information includes the priority level of the resource gap requested by the second wireless device. (Item 31) The first base station determines whether the priority level of the resource gap is higher than the logical channel of the side link between the first wireless device and the second wireless device. Based on the decision, the first base station said, In response to the priority level of the resource gap being higher than that of the logical channel, determine the wireless resources for the sidelink so as not to overlap with the resource gap, or The method of item 30, further comprising determining a wireless resource for the side link regardless of the resource gap in response that the priority level of the resource gap is less than or equal to the logical channel. (Item 32) The first wireless device determines whether the priority level of the resource gap associated with the support information is higher than the logical channel of the side link between the first wireless device and the second wireless device. Based on the decision, the first wireless device communicates to the second wireless device: In response to the priority level of the resource gap being higher than that of the logical channel, transmit a transport block over a wireless resource that does not overlap with the resource gap, or The method according to any one of items 30 to 31, further comprising transmitting a transport block over the wireless resources of the side link, regardless of the resource gap, in response that the priority level of the resource gap is less than or equal to the logical channel. (Item 33) Receiving a message from a first wireless device to a first base station, which includes support information for a second wireless device, wherein the support information is for time-domain resource allocation of a side link between the first wireless device and the second wireless device; A method comprising transmitting a resource permission to the first wireless device by the first base station, indicating at least one wireless resource of the sidelink, wherein the time-domain resource allocation of the at least one wireless resource is transmitted based on the support information. (Item 34) The method according to item 33, further comprising determining the at least one radio resource of the side link based on the support information by the first base station. (Item 35) The support information requests that the second wireless device not receive a transport block from the first wireless device via the sidelink during at least one period. The method described in any one of items 33-34, indicating the interval. (Item 36) The aforementioned support information, Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, Priority information of the synchronization reference source in the serving cell of the second wireless device, or The method described in any one of items 33-35, which indicates at least one of the bearer identifiers of a sidelink bearer. (Item 37) The method according to any one of items 33 to 36, wherein the support information includes the priority level of the resource gap requested by the second wireless device. (Item 38) The first base station determines whether the priority level of the resource gap is higher than the logical channel of the side link between the first wireless device and the second wireless device. Based on the decision, the first base station said, In response to the priority level of the resource gap being higher than that of the logical channel, determine the at least one wireless resource for the side link so as not to overlap with the resource gap, or The method of item 37, further comprising determining the at least one wireless resource for the side link regardless of the resource gap, in response that the priority level of the resource gap is less than or equal to the logical channel. (Item 39) The at least one wireless resource, At least one regular resource, At least one dynamic permission, or The method described in any one of items 33 to 38, comprising at least one of at least one resource pool. (Item 40) The network node receives scheduling information indicating wireless resources via a second wireless device, The second wireless device transmits to the first wireless device, and at least one parameter indicating support information regarding the time-domain resource allocation of the side link between the first wireless device and the second wireless device, based on the scheduling information. A method comprising receiving the transport block of the sidelink from the first wireless device via at least one wireless resource based on the support information. (Item 41) The aforementioned network node, Second base station, A third wireless device, or The method according to item 40, comprising at least one of the first wireless devices described above. (Item 42) The method according to any one of items 40 to 41, further comprising determining the support information based on the scheduling information using the second wireless device. (Item 43) The method according to any one of items 40 to 42, further comprising determining the support information based on the traffic pattern of packets transmitted or received by the second wireless device. (Item 44) The wireless resource in the scheduling information is Periodic resources for transmission by the second wireless device, or The method described in any one of items 40 to 43, comprising at least one of the periodic resources for reception by a second wireless device. (Item 45) The method according to any one of items 40 to 44, wherein the support information indicates at least one period during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink. (Item 46) The aforementioned support information, Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, Priority information of the synchronization reference source in the serving cell of the second wireless device, or The method described in any one of items 40-45, which indicates at least one of the bearer identifiers of a sidelink bearer. (Item 47) The method according to any one of items 40 to 46, wherein the support information includes the priority level of the resource gap requested by the second wireless device. (Item 48) The first wireless device receives the sidelink resource pool, The first wireless device receives from the second wireless device at least one parameter indicating information supporting the time-domain resource allocation of the side link between the first wireless device and the second wireless device, The first wireless device transmits a transport block to the second wireless device via at least one wireless resource of the sidelink, The sidelink resource pool includes the at least one wireless resource, A method for assigning time-domain resources of at least one wireless resource, including transmitting based on at least one parameter. (Item 49) Receiving the aforementioned side link resource pool base station, or The method of item 48, which includes receiving the sidelink resource pool from at least one network operating server. (Item 50) The method according to any one of items 48 to 49, further comprising determining the at least one wireless resource of the side link based on the at least one parameter using the first wireless device. (Item 51) The method according to any one of items 48 to 50, wherein the support information indicates at least one period during which the second wireless device requests that the first wireless device not receive a transport block via the sidelink. (Item 52) The aforementioned support information, Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, Priority information of the synchronization reference source in the serving cell of the second wireless device, or The method described in any one of items 48-51, which indicates at least one of the bearer identifiers of a sidelink bearer. (Item 53) The method according to any one of items 48 to 52, wherein the support information includes the priority level of the resource gap requested by the second wireless device. (Item 54) The first wireless device determines whether the priority level of the resource gap is higher than the logical channel of the side link between the first wireless device and the second wireless device. Based on the decision, the first wireless device, In response to the priority level of the resource gap being higher than that of the logical channel, determine the at least one wireless resource for the side link so as not to overlap with the resource gap, or The method of item 53, further comprising determining the at least one wireless resource for the side link regardless of the resource gap, in response that the priority level of the resource gap is less than or equal to the logical channel. (Item 55) The first base station receives a message from the second base station containing support information for time-domain resource allocation of the side link between the first radio device and the second radio device, A method comprising transmitting a resource permission to the first wireless device by the first base station, indicating at least one wireless resource of the sidelink, wherein the time-domain resource allocation of the at least one wireless resource is transmitted based on the support information. (Item 56) The method according to item 55, wherein the second base station corresponds to the second wireless device. (Item 57) The method according to any one of items 55 to 56, further comprising determining the at least one radio resource of the side link based on the support information by the first base station. (Item 58) The method according to any one of items 55 to 57, wherein the support information indicates at least one period during which the second base station requests that the first radio device refrain from transmitting a transport block from the first radio device to the second radio device via the sidelink. (Item 59) The aforementioned support information, Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, Priority information of the synchronization reference source in the serving cell of the second wireless device, or The method described in any one of items 55-58, which indicates at least one of the bearer identifiers of a sidelink bearer. (Item 60) The method according to any one of items 55 to 59, wherein the support information includes the priority level of the resource gap required for the second wireless device. (Item 61) The first base station determines whether the priority level of the resource gap is higher than the logical channel of the side link between the first wireless device and the second wireless device. Based on the decision, the first base station said, In response to the priority level of the resource gap being higher than that of the logical channel, determine the at least one wireless resource for the side link so as not to overlap with the resource gap, or The method of item 60, further comprising determining the at least one wireless resource for the side link regardless of the resource gap, in response that the priority level of the resource gap is less than or equal to the logical channel. (Item 62) The at least one wireless resource, At least one regular resource, At least one dynamic permission, or The method described in any one of items 55 to 61, comprising at least one of at least one resource pool. (Item 63) The first base station receives network information of the second wireless device from the first wireless device, The first base station identifies the second base station corresponding to the second wireless device based on the network information, The method according to any one of items 55 to 62, further comprising transmitting a request for the support information for the second wireless device to the second base station by the first base station, wherein the reception of the message containing the support information is based on the request. (Item 64) The aforementioned network information, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the second base station, The resource pool index of the resource pool used by the second wireless device, The zone identifier of the zone in which the second wireless device is located, The second wireless device uses a synchronization reference source for sidelink communication, base station, or A synchronization reference source including at least one of the global navigation satellite systems, or The method of item 63, comprising at least one of the priority information of the synchronization reference source in the serving cell of the second wireless device. (Item 65) The first wireless device, One or more processors, A first wireless device, which includes a memory that, when executed by one or more processors, stores instructions causing the first wireless device to perform the method described in any one of items 1 to 32 and 48 to 54. (Item 66) It is a second wireless device, One or more processors, A second wireless device, comprising: a memory that, when executed by one or more processors, stores instructions causing the second wireless device to perform the method described in any one of items 40 to 47. (Item 67) It is a base station, One or more processors, A base station comprising: a memory that, when executed by one or more processors, stores instructions causing the base station to perform the method described in any one of items 33-39 and 55-64. (Item 68) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing the one or more processors to perform the method described in any one of items 1 to 64. (Item 69) The second wireless device, The first wireless device, One or more processors, A system comprising: a first wireless device, which, when executed by one or more processors, includes a memory that stores instructions causing the first wireless device to perform the method described in any one of items 1 to 32 and 48 to 54. (Item 70) The first wireless device and It is a second wireless device, One or more processors, A system including a second wireless device, which, when executed by one or more processors, stores instructions causing the second wireless device to perform the method described in any one of items 40 to 47. (Item 71) The first wireless device and The second wireless device, It is a base station, One or more processors, A system including a base station, which, when executed by one or more processors, stores instructions that cause the base station to perform the method described in any one of items 33-39 and 55-64. [Brief explanation of the drawing] 【0003】 Some embodiments of the various embodiments of this disclosure are described herein with reference to the drawings. 【0004】 [Figure 1] Figures 1A and 1B show an embodiment of a mobile communication network in which an embodiment of the present disclosure may be implemented. 【0005】 [Figure 2] Figures 2A and 2B show the new radio (NR) user plane and control plane protocol stacks, respectively. 【0006】 [Figure 3] Figure 3 shows an example of the services provided between the protocol layers of the NR user plane protocol stack in Figure 2A. 【0007】 [Figure 4A] Figure 4A shows an exemplary downlink data flow through the NR user plane protocol stack shown in Figure 2A. 【0008】 [Figure 4B] Figure 4B shows an example of the MAC subheader format in a MAC PDU. 【0009】 [Figure 5] Figures 5A and 5B show the mapping between the logical channels, transport channels, and physical channels of the downlink and uplink, respectively. 【0010】 [Figure 6] Figure 6 is an illustrative diagram showing the RRC state transitions of the UE. 【0011】 [Figure 7] Figure 7 shows an example of an NR frame structure where OFDM symbols are grouped together. 【0012】 [Figure 8] Figure 8 shows an example of slot configuration in the time and frequency domains of the NR carrier. 【0013】 [Figure 9] Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. 【0014】 [Figure 10A] Figure 10A shows three carrier aggregation configurations, each having two component carriers. 【0015】 [Figure 10B] Figure 10B shows an example of how aggregation cells can be configured into one or more PUCCH groups. 【0016】 [Figure 11A] Figure 11A shows an example of the SS / PBCH block structure and location. 【0017】 [Figure 11B] Figure 11B shows an example of CSI-RS mapped to the time and frequency domains. 【0018】 [Figure 12] Figures 12A and 12B show three examples of downlink and uplink beam management procedures, respectively. 【0019】 [Figure 13] Figures 13A, 13B, and 13C show a 4-step competition-based random access procedure, a 2-step non-competitive random access procedure, and another 2-step random access procedure, respectively. 【0020】 [Figure 14A] Figure 14A shows an example of a CORESET configuration for the bandwidth portion. 【0021】 [Figure 14B] Figure 14B shows an example of CCE-REG mapping for DCI transmissions during CORESET and PDCCH processing. 【0022】 [Figure 15] Figure 15 shows an example of a wireless device that communicates with a base station. 【0023】 [Figure 16]Figures 16A, 16B, 16C, and 16D show exemplary structures for uplink and downlink transmission. 【0024】 [Figure 17] Figure 17 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0025】 [Figure 18] Figure 18 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0026】 [Figure 19] Figure 19 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0027】 [Figure 20] Figure 20 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0028】 [Figure 21] Figure 21 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0029】 [Figure 22] Figure 22 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0030】 [Figure 23] Figure 23 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0031】 [Figure 24] Figure 24 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0032】 [Figure 25] Figure 25 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0033】 [Figure 26] Figure 26 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0034】 [Figure 27] Figure 27 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0035】 [Figure 28] Figure 28 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0036】 [Figure 29] Figures 29A, 29B, 29C, and 29D are diagrams of aspects of an exemplary embodiment of the present disclosure. 【0037】 [Figure 30] Figures 30A and 30B are diagrams of one aspect of an exemplary embodiment of the present disclosure. 【0038】 [Figure 31] Figure 31 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0039】 [Figure 32] Figure 32 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0040】 [Figure 33] Figure 33 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0041】 [Figure 34] Figure 34 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0042】 [Figure 35] Figure 35 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0043】 [Figure 36] Figure 36 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0044】 [Figure 37] Figure 37 is a diagram of one aspect of an exemplary embodiment of the present disclosure. 【0045】 [Figure 38] Figure 38 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. 【0046】 [Figure 39] Figure 39 is a diagram illustrating one embodiment of an exemplary example of the present disclosure. [Modes for carrying out the invention] 【0047】 The embodiments may be configured to operate as needed. The disclosed mechanisms may be executed, for example, in a wireless device, base station, wireless environment, network, or a combination thereof, when certain criteria are met. Illustrative criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system configuration, packet size, traffic characteristics, or a combination thereof. Various exemplary embodiments can be applied when one or more criteria are met. Therefore, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols. 【0048】 A base station can communicate with a mixture of radio devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Radio devices may have certain capabilities depending on the category and / or capabilities of the radio device. Where this disclosure refers to a base station communicating with multiple radio devices, this disclosure may refer to a subset of all radio devices in a coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release that have a given capability and are located in a given sector of a base station. Multiple radio devices in this disclosure may refer to a selection of multiple radio devices and / or a subset of all radio devices in a coverage area that operate according to the disclosed method, etc. Multiple base stations or multiple radio devices may exist in a coverage area that cannot comply with the disclosed method. For example, those radio devices or base stations may be running on an older release of LTE or 5G technology. 【0049】 In this specification, “a” and “an” and similar phrases are interpreted as “at least one” and “one or more.” Similarly, any term ending in the suffix “(s)” should be interpreted as “at least one” and “one or more.” In this specification, the term “may” is interpreted as “for example, may be.” In other words, the term “may” indicates that the phrase following the term “may” is one embodiment of several suitable possibilities, which may or may not be used by one or more of the various embodiments. Where used herein, the terms “comprises” and “consists of” enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unlisted components included in the element being described. In contrast, “consists of” provides a complete enumeration of one or more components of the element being described. Where used herein, the term “based on” should be interpreted as “at least partially based” rather than, for example, “based only on.” As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" could mean A, B, C, A and B, A and C, B and C, or A, B, and C. 【0050】 If A and B are a set and all elements of A are also elements of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase "according to" (or equivalently "at least in accordance with") indicates that the phrase following the phrase "according to" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase following the phrase “adopt / use” is an embodiment of one of many appropriate possibilities, in which one or more of the various embodiments may or may not be used. 【0051】 The term “configured” can relate to the capacity of a device, regardless of whether the device is operational or non-operating. “Configured” can also refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operating. In other words, hardware, software, firmware, registers, memory values, etc., can be “configured” within a device, regardless of whether the device is operational or non-operating, in order for the device to provide certain characteristics. Terms such as “control messages generated in the device” may mean that, regardless of whether the device is operational or non-operating, control messages have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device. 【0052】 In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then for example, N contains K and N contains J. In exemplary embodiments, when one or more messages contain multiple parameters, it means that one of the multiple parameters is contained in at least one of the one or more messages, but not in each of the one or more messages. 【0053】 Furthermore, many of the features presented above are described as optional by the use of "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe all possible changes that may result from selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven ways: by just one of the three possible features, by any two of the three features, or by three of the three features. 【0054】 Many of the elements described in the disclosed embodiments can be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, and they can be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab®) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Modules may also be implemented using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex-programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which constitute connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the results of the functional modules. 【0055】 Figure 1A shows an embodiment of a mobile communications network 100 in which embodiments of the present disclosure may be implemented. The mobile communications network 100 may be, for example, a public land mobile network (PLMN) operated by a network operator. As shown in Figure 1A, the mobile communications network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and radio devices 106. 【0056】 CN102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interface function, CN102 may set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging capabilities. 【0057】 RAN104 can connect CN102 to radio device 106 via radio communication over the air interface. As part of the radio communication, RAN104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN104 to radio device 106 over the air interface is known as the downlink, and the communication direction from radio device 106 to RAN104 over the air interface is known as the uplink. Downlink transmissions can be isolated from uplink transmissions using frequency division duplication (FDD), time division duplication (TDD), and / or some combination of the two duplication techniques. 【0058】 The term "wireless device" may be used throughout this disclosure to mean and include any mobile or fixed (non-portable) device that requires or is capable of wireless communication. For example, a wireless device could be a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also includes other terms, including user equipment (UE), user terminal (UT), access terminal (AT), portable station, handset, wireless transceiver unit (WTRU), and / or wireless communication device. 【0059】 RAN104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to include and encompass Node B (associated with UMTS and / or 3G standards), evolved Node B (associated with eNB, E-UTRA and / or 4G standards), remote radio head (RRH), baseband processing unit coupled to one or more RRHs, repeater or relay node used to extend the coverage area of ​​a donor node, next-generation evolved Node B (ng-eNB), generating Node B (associated with gNB, NR and / or 5G standards), access point (AP, associated with e.g., WiFi or other appropriate wireless communication standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU). 【0060】 The base stations included in RAN104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more base stations may include three sets of antennas for controlling three cells (or sectors) respectively. The size of a cell may be determined by the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base station may provide wireless coverage to the wireless device 106 over a wide geographical area to support wireless device mobility. 【0061】 In addition to three-sector sites, other implementations of base stations are possible. For example, one or more base stations of RAN104 may be implemented as sector sites having more than three or less than three sectors. One or more base stations of RAN104 may be implemented as an access point, as a baseband processing unit coupled to a plurality of remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, and the baseband processing unit may be centralized within a pool of baseband processing units or may be virtualized. A repeater node may amplify and rebroadcast a wireless signal received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode the wireless signal received from the donor node and remove noise before amplifying and rebroadcasting the wireless signal. 【0062】 RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmit power. RAN104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide smaller coverage areas, for example, overlapping with the relatively large coverage areas provided by macrocell base stations. Smaller coverage areas can be provided in areas with high data traffic (or so-called hotspots) or in areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations. 【0063】 The Third Generation Partnership Project (3GPP®) was formed in 1998 to provide global standardization for mobile communication network specifications, similar to mobile communication network 100 in Figure 1A. To date, 3GPP® has produced specifications for three generations of mobile networks: third-generation (3G) networks known as Universal Mobile Communications Systems (UMTS), fourth-generation (4G) networks known as Long-Term Evolution (LTE), and fifth-generation (5G) networks known as 5G Systems (5GS). Embodiments of this disclosure are described with reference to the RAN of a 3GPP® 5G network, referred to as Next Generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as RAN 104 in Figure 1A, earlier RANs of 3G and 4G networks, and future networks that have not yet been specified (e.g., 3GPP® 6G networks). NG-RAN can be supplied to implement 5G radio access technology, also known as New Radio (NR), and other radio access technologies, including 4G radio access technology or non-3GPP® radio access technology. 【0064】 Figure 1B shows a mobile communications network 150 of another embodiment in which embodiments of the present disclosure may be implemented. The mobile communications network 150 may be, for example, a PLMN operated by a network operator. As shown in Figure 1B, the mobile communications network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UE156A and UE156B (collectively referred to as UE156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A. 【0065】 5G-CN152 provides UE156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface function, 5G-CN152 may set up end-to-end connectivity between UE156 and one or more DNs, authenticate UE156, and provide charging capabilities. Compared to CNs in 3GPP® 4G networks, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN152 may be defined as network functions that provide services through interfaces to other network functions. Network functions of 5G-CN152 may be implemented in several ways, such as network elements on dedicated or shared hardware, software instances running on dedicated or shared hardware, or virtualized functions instantiated on a platform (e.g., a cloud-based platform). 【0066】 As shown in Figure 1B, the 5G-CN152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B, as shown in Figure 1B as a single component AMF / UPF158, for brevity of explanation. UPF158B can function as a gateway between NG-RAN154 and one or more DNs. UPF158B can perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification supporting routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggering. UPF158B can support multi-homed PDU sessions by functioning as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branch point. UE156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN. 【0067】 The AMF158A can perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registered area management, intra-system and inter-system mobility support, access authentication, access permissions including roaming privilege checks, mobility management controls (subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN. 【0068】 For clarity, 5G-CN152 may include one or more additional network functions not shown in Figure 1B. For example, 5G-CN152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF). 【0069】 NG-RAN154 can connect 5G-CN 152 to UE156 via radio communication over the air interface. NG-RAN154 may include one or more gNBs (collectively gNBs160) illustrated as gNB160A and gNB160B and / or one or more ng-eNBs (collectively ng-eNBs162) illustrated as ng-eNB162A and ng-eNB162B. gNBs160 and ng-eNBs162 may more generally be referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 over the air interface. For example, one or more gNB160s and / or one or more ng-eNB162s may include three sets of antennas for controlling three cells (or sectors), each. In addition, the gNBs160 and ng-eNBs162 cells can provide wireless coverage to the UE156 over a wide geographical area to support UE mobility. 【0070】 As shown in Figure 1B, gNB160 and / or ng-eNB162 may be connected to 5G-CN152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. gNBs160 and / or ng-eNBs162 may be connected to UE156 via the Uu interface. For example, as shown in Figure 1B, gNB160A may be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with an interface may be used by the network elements in Figure 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements. 【0071】 The gNB160 and / or ng-eNB162 may be connected to one or more AMF / UPF functions of the 5G-CN152, such as the AMF / UPF158, by one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF / UPF158 by an NG user plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between the gNB160A and the UPF158B (e.g., unguaranteed supply). The gNB160A may be connected to the AMF158A using an NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, NAS message forwarding, paging, PDU session management and configuration forwarding, and / or sending warning messages. 【0072】 The gNB160 may provide NR user plane and control plane protocol termination to UE156 on a Uu interface. For example, the gNB160A may provide NR user plane and control plane protocol termination to UE156A on a Uu interface associated with a first protocol stack. The ng-eNBs162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE156 on a Uu interface, where E-UTRA refers to 3GPP® 4G radio access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocol termination to UE156B on a Uu interface associated with a second protocol stack. 【0073】 The 5G-CN152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for NR to connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF158 is shown in Figure 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load shares across multiple AMF / UPF nodes. 【0074】 As will be discussed, in Figure 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes, namely a user plane and a control plane. The user plane may process data of interest to the user, and the control plane may process signaling messages of interest to the network elements. 【0075】 Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE210 and gNB220, respectively. The protocol stacks shown in Figures 2A and 2B may be the same or similar to those used for the Uu interface between UE156A and gNB160A shown in Figure 1B, for example. 【0076】 Figure 2A shows the NR user plane protocol stack, which includes five layers, implemented in the UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The following four protocols above PHYs 211 and 221 include the Media Access Control Layer (MAC) 212 and 222, the Radio Link Control Layer (RLC) 213 and 223, the Packet Data Convergence Protocol Layer (PDCP) 214 and 224, and the Service Data Application Protocol Layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model. 【0077】 Figure 3 shows an example of services provided between the protocol layers of the NR user plane protocol stack. Starting from the top of Figures 2A and 3, SDAP215 and 225 may perform QoS flow processing. UE210 may receive services via a PDU session, which may be a logical connection between UE210 and DN. A PDU session may have one or more QoS flows. CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows in the PDU session based on QoS requirements (e.g., with respect to delay, data rate, and / or error rate). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows and one or more data radio bearers. Mapping / unmapping between QoS flows and data radio bearers may be determined by SDAP225 at gNB220. SDAP215 at UE210 may be notified about the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from gNB220. Regarding reflection mapping, the SDAP225 on the gNB220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP215 on the UE210 to determine mapping / unmapping between QoS flows and data radio bearers. 【0078】 PDCP214 and PDCP224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP214 and 224 may perform, for example, retransmission of unsent packets, intra-sequence delivery and rearrangement of packets, and removal of duplicate received packets for handover within gNB. PDCP214 and 224 may perform packet duplication to improve the likelihood of received packets and to remove any duplicate packets at the receiver. Packet duplication may be useful for services requiring high reliability. 【0079】 Although not shown in Figure 3, PDCP214 and 224 can perform mapping / unmapping between split radio bearers and RLC channels in a dual-connection scenario. Dual connectivity is a technique that allows a UE to connect to two cells, or more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split radio bearer is when a single radio bearer, such as one of the radio bearers provided by PDCP214 and 224 as a service to SDAP215 and 225, is handled by a cell group in a dual-connection. PDCP214 and 224 can map / unmap split radio bearers between RLC channels belonging to the cell group. 【0080】 RLC213 and 223 can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of replicated data units received from MAC212 and 222, respectively. RLC213 and 223 can support three transmission modes: Transparent Mode (TM), Unacknowledged Response Mode (UM), and Acknowledged Response Mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the indicated functions. This RLC configuration can be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As shown in Figure 3, RLC213 and 223 can provide RLC channels as a service to PDCP214 and 224, respectively. 【0081】 MAC212 and MAC222 may perform logical channel multiplexing / demultiplexing and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from PHY211 and 221. MAC222 may be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by dynamic scheduling. Scheduling may be performed by gNB220 (on MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, priority processing between logical channels of UE210 by logical channel prioritization, and / or padding through Hybrid Automatic Repeating Requests (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)). MAC212 and MAC222 may support one or more numerology and / or transmit timings. In one embodiment, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as a service. 【0082】 PHY211 and 221 can perform transport channel mapping to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY211 and 221 can perform multi-antenna mapping. As shown in Figure 3, PHY211 and 221 may provide one or more transport channels to MAC212 and 222 as a service. 【0083】 Figure 4A shows an example of downlink data flow through the NR user plane protocol stack. Figure 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs on the gNB220. Uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A. 【0084】 The downlink data flow in Figure 4A begins when SDAP225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, SDAP225 maps IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in Figure 4A) is added to the IP packets. Data units from / to higher protocol layers are called service data units (SDUs) at lower protocol layers, and data units to / from lower protocol layers are called protocol data units (PDUs) at higher protocol layers. As shown in Figure 4A, the data unit from AP225 is an SDU at the lower protocol layer PDCP224 and a PDU at SDAP225. 【0085】 The remaining protocol layers in Figure 4A may perform relevant functions (e.g., with respect to Figure 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP224 may perform IP header compression and encryption and forward its output to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A) and forward its output to MAC222. MAC222 may multiplex several RLC PDUs and attach MAC subheaders to the RLC PDUs to form transport blocks. In NR, as shown in Figure 4A, MAC subheaders may be distributed throughout the MAC PDU. In LTE, MAC subheaders may be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated delays because the MAC PDU subheaders may be computed before the complete MAC PDU is assembled. 【0086】 Figure 4B shows an example of the MAC subheader format in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (in bytes, etc.) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCD) field to identify the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use. 【0087】 Figure 4B further illustrates MAC control elements (CEs) inserted into a MAC PDU by MACs such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, on / off MAC CEs for PDCP duplicate detection on / off, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and pre-configured components, discontinuous receive (DRX)-related MAC CEs, timing progression MAC CEs, and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader in a format similar to that described for MAC SDUs and may be identified by a reserved value in the LCID field, which indicates the type of control information contained in the MAC CE. 【0088】 Before describing the NR control plane protocol stack, we will first explain the logical channels, transport channels, and physical channels, as well as the mapping between channel types. One or more channels can be used to perform functions related to the NR control plane protocol stack, which will be discussed later. 【0089】 Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels that transmit control and configuration information within the NR control plane, or as traffic channels that transmit data within the NR user plane. Logical channels can be classified as dedicated logical channels for a particular UE, or as common logical channels that can be used by multiple UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - A paging control channel (PCCH) for displaying paging messages used to page UEs whose location is not known to the network at the cell level, - A broadcast control channel (BCCH) for transmitting system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs), wherein the system information messages are used by the UE to obtain information about how the cell is configured and how it operates within the cell. - A common control channel (CCCH) for sending control messages along with random access, - To configure the UE, a dedicated control channel (DCCH) is provided for sending control messages to and from a specific UE. - Includes a dedicated traffic channel (DTCH) for transmitting user data to and from a specific UE. 【0090】 A transport channel is used between the MAC layer and the PHY layer and can be defined by how they transmit the information they send over the air interface. The set of transport channels defined by NR includes, for example, - A paging channel (PCH) for sending paging messages originating from the PCCH, - Broadcast Channel (BCH) for carrying MIBs from BCCH, - Downlink Shared Channel (DL-SCH) for sending downlink data and signaling messages, including SIBs from BCCH. - Uplink Shared Channel (UL-SCH) for transmitting uplink data and signaling messages, - Includes Random Access Channels (RACH) that allow UEs to connect to the network without prior scheduling. 【0091】 A PHY can pass information between its processing levels using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY may generate control information to support its low-level operation and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR is, for example, - A physical broadcast channel (PBCH) for carrying MIBs from the BCH, - A physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH, - A physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorization, and uplink power control commands. - UL-SCH and, in some examples, a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from uplink control information (UCI), as described below. - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR), - Includes a physical random access channel (PRACH) for random access. 【0092】 Similar to the physical control channel, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by the NR include the primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMSR), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below. 【0093】 Figure 2B shows an example of an NR control plane protocol stack. In Figure 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as in the example of the NR user plane protocol stack. These four protocol layers include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. Instead of having SDAP215 and 225 at the top of the stack, as in the NR user plane protocol stack, the NR control plane stack has Radio Resource Control (RRC)216 and 226, and NAS protocols217 and 237 at the top of the NR control plane protocol stack. 【0094】 NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 (e.g., AMF158A), or more generally, between the UE210 and the CN. NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 via signaling messages called NAS messages. There is no direct path between the UE210 and the AMF230 to send NAS messages. NAS messages can be sent using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management. 【0095】 RRC216 and 226 may provide control plane functionality between UE210 and gNB220, or more generally, between UE210 and RAN. RRC216 and 226 may provide control plane functionality between UE210 and gNB220 via signaling messages called RRC messages. RRC messages may be transmitted between UE210 and RAN using a signaling radio bearer and identical / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data within the same transport block (TB). The RRC216 and 226 can provide control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the UE210 and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, UE measurement reporting and reporting control, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing the RRC connection, the RRC216 and 226 can establish an RRC context, which may involve setting parameters for communication between the UE210 and the RAN. 【0096】 Figure 6 is an exemplary diagram illustrating the RRC state transitions of a UE. The UE may be identical or similar to the wireless device 106 shown in Figure 1A, the UE 210 shown in Figures 2A and 2B, or any other wireless device described herein. As shown in Figure 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE). 【0097】 In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be one or more base stations included in RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, gNB220 shown in Figures 2A and 2B, or any other base station similar to any other base station described herein. The base station to which the UE is connected may have the UE's RRC context. The RRC context, called the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN104 or NG-RAN154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently serving the UE. Based on the reported measurements, the UE's serving base station may request a handover to one of the adjacent base stations' cells. The RRC state may transition from RRC connection 602 to RRC idle 604 via connection release procedure 608, or to RRC inactive 606 via connection deactivation procedure 610. 【0098】 During RRC idle 604, an RRC context cannot be established for the UE. During RRC idle 604, the UE cannot have an RRC connection with the base station. During RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous receive cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connection 602 via a connection establishment procedure 612, which may involve a random access procedure, as will be discussed in more detail below. 【0099】 In RRC inactive 606, the previously established RRC context is maintained at the UE and base station. This reduces signaling overhead compared to the transition from RRC idle 604 to RRC connected 602, enabling a faster transition to RRC connected 602. In RRC inactive 606, the UE is in a sleep state, and the UE's mobility can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 via connection restart procedure 614, or to RRC idle 604 via connection release procedure 616, which is identical or similar to connection release procedure 608. 【0100】 The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to enable the network to notify the UE of events via paging messages without broadcasting paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 may enable the network to track the UE at the cell group level so that paging messages can be broadcast on the cells of the cell group in which the UE currently resides, instead of across the entire mobile communications network. The mobility management mechanisms in RRC idle 604 and RRC inactive 606 track the UE at the cell group level. They can do so using grouping at different granularities. For example, there may be three levels of granularity for cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas, called a tracking area, identified by a Tracking Area Identifier (TAI). 【0101】 A tracking area can be used to track a UE at the CN level. The CN (e.g., CN102 or 5G-CN152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area through cell reselection, the UE may perform a registration update in the CN so that the CN can update the UE's location and provide the UE with a new UE registration area. 【0102】 RAN areas can be used to track UEs at the RAN level. For UEs in the RRC inactive 606 state, a RAN notification area can be assigned to the UE. A RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In one embodiment, a base station may belong to one or more RAN notification areas. In one embodiment, a cell may belong to one or more RAN notification areas. If a UE moves to a cell that is not included in the RAN notification area assigned to the UE through cell reselection, the UE can perform a notification area update in the RAN to update the UE's RAN notification area. 【0103】 A base station that stores the RRC context for a UE, or the last serving base station of the UE, may be called an anchor base station. The anchor base station can maintain the RRC context for the UE for at least the duration that the UE remains in the anchor base station's RAN notification area and / or the duration that the UE remains in an RRRC inactive 606. 【0104】 A gNB, such as the gNB160 in Figure 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include an RRC, PDCP, and SDAP. The gNB-DU may include an RLC, MAC, and PHY. 【0105】 In NR, physical signals and physical channels (Figures 5A and 5B) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) or M phase shift keying (M-PSK) symbols) called source symbols, which are divided into F parallel symbol streams. The F parallel symbol streams can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain as if they were in the frequency domain. The IFFT block can take one from each of the F parallel symbol streams at a time into an F source symbol, and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be an F time domain sample representing the sum of the F orthogonal subcarriers. The F time domain sample can form a single OFDM symbol. After some processing (e.g., adding cyclic prefixes) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface on the carrier frequency. The parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This process generates OFDM symbols pre-encoded with a discrete Fourier transform (DFT), which can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse process can be performed at the receiver using an FFT block on the OFDM symbols to reconstruct the data mapped to the source symbols. 【0106】 Figure 7 shows an example of the structure of an NR frame in which OFDM symbols are grouped. An NR frame can be identified by a system frame number (SFN). An SFN may repeat over a period of 1024 frames. As shown in the figure, a single NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into slots, for example, each containing 14 OFDM symbols. 【0107】 The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to a maximum of mm-wavelengths). Numerology can be defined with respect to subcarrier spacing and cyclic prefix duration. For numerology in NR, the subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 ums. ​​For example, NR defines numerology using the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ums, 30 kHz / 2.3 ums, 60 kHz / 1.2 ums, 120 kHz / 0.59 ums, and 240 kHz / 0.29 ums. 【0108】 A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier intervals have shorter slot durations and, accordingly, more slots per subframe. Figure 7 shows this numerology-dependent slot duration and slot transmission structure per subframe (for ease of illustration, numerologies with a 240 kHz subcarrier interval are not shown in Figure 7). Subframes within the NR can be used as a numerology-independent time reference, while slots can be used as units on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in the NR may be separated from slot duration and may start with any OFDM symbol and end with as many symbols as needed for transmission. These partial slot transmissions may be called mini-slot transmissions or sub-slot transmissions. 【0109】 Figure 8 shows an example of slot configuration in the time and frequency domains of an NR carrier. A slot contains resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in the NR. As shown in Figure 8, an RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain. An RB spans 12 consecutive REs in the frequency domain, as shown in Figure 8. The NR carrier may be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. These limitations, when used, may also limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, with the 400 MHz bandwidth being set based on a carrier bandwidth limit of 400 MHz per unit. 【0110】 Figure 8 shows a single numerology used across the entire bandwidth of the NR carrier. In other exemplary configurations, multiple numerologies may be supported on the same carrier. 【0111】 NR can support a wide range of carrier bandwidths (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibited from a power consumption perspective for the UE. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its receiving bandwidth based on the amount of traffic the UE is expected to receive. This is called bandwidth adaptation. 【0112】 NR supports UEs that cannot receive the entire carrier bandwidth and defines a Bandwidth Portion (BWP) that supports bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of consecutive RBs on the carrier. A UE may consist of one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell) (e.g., via the RRC layer). At a given time, one or more of the BWPs configured for a serving cell may be active. These one or more BWPs may be called the active BWPs of the serving cell. When a serving cell consists of a secondary uplink carrier, the serving cell may have one or more primary active BWPs on the uplink carrier and one or more secondary active BWPs on the secondary uplink carrier. 【0113】 For unpaired spectra, a downlink BWP from a set of configured downlink BWPs can be linked to an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectra, the UE can expect that the center frequency of the downlink BWP is the same as the center frequency of the uplink BWP. 【0114】 For downlink BWPs within a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE for at least one search space with one or more control resource sets (CORESETs). A search space is a set of locations in the time and frequency domains from which a UE can find control information. A search space can be UE-specific or a common search space (potentially available to multiple UEs). For example, a base station may configure a UE in a common search space on an active downlink BWP, either on a PCell or on a primary-secondary cell (PSCell). 【0115】 For an uplink BWP within a set of configured uplink BWPs, the BS can configure the UE with one or more resource sets for one or more PUCCH transmissions. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) within the downlink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix duration). The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) within the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP). 【0116】 One or more BWP indicator fields may be provided to the Downlink Control Information (DCI). The value of a BWP indicator field may indicate which BWP in the configured set is the active downlink BWP for one or more downlink receptions. The value of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions. 【0117】 The base station may semi-statically configure the UE with the default downlink BWP in the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP can be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH. 【0118】 A base station can configure the UE with a PCell BWP inactive timer value. The UE can start or restart the BWP inactive timer at any appropriate time. For example, the UE may start or restart the BWP inactive timer when (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for a paired spectral operation, or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for a non-paired spectral operation. If the UE does not detect a DCI for a certain period (e.g., 1 millisecond or 0.5 milliseconds), the UE may run the BWP inactive timer toward expiration (e.g., increasing from zero to the BWP inactive timer value, or decreasing from the BWP inactive timer value to zero). When the BWP inactive timer expires, the UE may switch from the active downlink BWP to the default downlink BWP. 【0119】 In one embodiment, a base station can semi-statically configure a UE having one or more BWPs. The UE can switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating the second BWP as the active BWP, and / or in response to the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP). 【0120】 Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a BWP that is not currently active) may occur independently in a paired spectrum. In a non-paired spectrum, downlink and uplink BWP switching may occur simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or the initiation of random access. 【0121】 Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. The UE, consisting of the three BWPs, may switch from one BWP to another at a switching point. In the example shown in Figure 9, the BWPs include BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 may be the initial active BWP, and BWP904 may be the default BWP. The UE can switch between BWPs at a switching point. In the example in Figure 9, the UE may switch from BWP902 to BWP904 at switching point 908. The switch at switching point 908 may occur for any suitable reason, for example, in response to the expiration of a BWP inactive timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP906 at switching point 910 in response to receiving a DCI indicating BWP906 as the active BWP. The UE may switch from active BWP906 to BWP904 at switching point 912 in response to the expiration of the BWP inactive timer and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP902 at switching point 914 in response to receiving a DCI indicating BWP902 as the active BWP. 【0122】 If a UE is configured for a secondary cell with a set of configured downlink BWPs and a default downlink BWP in the timer value, the UE procedure for switching the BWP on the secondary cell may be identical / similar to that for the primary cell. For example, the UE may use the timer value and default downlink BWP for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell. 【0123】 To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to the same UE. The aggregated carriers in CA may also be called component carriers (CCs). When using CA, there are multiple serving cells for the UE and one cell for the CC. A CC can have three configurations within the frequency domain. 【0124】 Figure 10A shows three CA configurations with two CCs. In the in-band, continuous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are positioned directly adjacent to each other within that frequency band. In the in-band, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and separated into frequency bands by a gap. In the in-band configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B). 【0125】 In one embodiment, up to 32 CCs may be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD or FDD). A serving cell of a UE using a CA may have downlink CCs. For FDD, one or more uplink CCs may optionally be configured for the serving cell. Aggregating more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic on the downlink than on the uplink. 【0126】 When using a Carrier Aggregation (CA), one of the aggregation cells of the UE may be called the Primary Cell (PCell). The PCell may be the serving cell to which the UE first connects during RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. The UE may have different PCells. On the downlink, the carrier corresponding to the PCell may be called the Downlink Primary CC (DL PCC). On the uplink, the carrier corresponding to the PCell may be called the Uplink Primary CC (UL PCC). Other aggregation cells of the UE may be called Secondary Cells (SCells). In one embodiment, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. On the downlink, the carrier corresponding to the SCell may be called the Downlink Secondary CC (DL SCC). On the uplink, the carrier corresponding to the SCell may be called the Uplink Secondary CC (UL SCC). 【0127】 SCells configured for a UE can be started and stopped, for example, based on traffic and channel conditions. Stopping a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. Configured SCells can be started and stopped using MAC CEs with respect to Figure 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., from a subset of configured SCells) for the UE are started or stopped. Configured SCells can be stopped in response to the expiration of a SCell stop timer (e.g., one SCell stop timer per SCell). 【0128】 Downlink control information, such as cell scheduling assignments and scheduling authorizations, may be transmitted on the cell corresponding to the assignment and authorization, known as self-scheduling. DCIs for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PCell's PUCCH. A large number of aggregated downlink CCs may overload the PCell's PUCCH. A cell may be divided into multiple PUCCH groups. 【0129】 Figure 10B shows an example of how an aggregation cell may be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. In the example in Figure 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary S cells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CC of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, may be transmitted on the uplink of PSCell 1061. In one embodiment, if the aggregation cell depicted in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI related to downlink CC may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061. 【0130】 A cell containing a downlink carrier and an optional uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, depending on the context in which the physical cell ID is used, identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined using synchronization signals transmitted on the downlink component carrier. The cell index may be determined using RRC messages. In this disclosure, the physical cell ID may be referred to as the carrier ID. The cell index may be referred to as the carrier index. For example, if this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for the cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. If this disclosure indicates that a first carrier is activated, this specification may mean that the cell containing the first carrier is activated. 【0131】 In a CA, the multi-carrier nature of the PHY may be exposed to MAC. In one embodiment, HARQ entities may operate on a serving cell. Transport blocks may be generated per allocation / authorization per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to serving cells. 【0132】 On the downlink, the base station may transmit one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in Figure 5A) to the UE (e.g., unicast, multicast, and / or broadcast). On the uplink, the UE may transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in Figure 5B). PSS and SSS are transmitted by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS may be provided within a synchronization signal (SS) / physical broadcast channel (PBCH) block containing PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks. 【0133】 Figure 11A shows an embodiment of the structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half frames (e.g., the first half frame having a duration of 5 milliseconds). Figure 11A is an example, and it will be understood that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, location of bursts within a frame) may be configured based on, for example, the carrier frequency of the cell from which the SS / PBCH block is transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), or any other appropriate factor. In one embodiment, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the radio network is configured to assume a different subcarrier spacing. 【0134】 The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the example in Figure 11A) or one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., the next two symbols) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., the next three OFDM symbols) and may span 240 subcarriers. 【0135】 The location of the SS / PBCH block in the time and frequency domains is not known to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain period (e.g., 20 milliseconds), the UE may search for the PSS at a different frequency position within the carrier, as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In one embodiment, the primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB. 【0136】 SS / PBCH blocks can be used by the UE to determine one or more parameters of a cell. For example, the UE may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS sequences, respectively. The UE may determine the position of a cell's frame boundary based on the position of the SS / PBCH block. For example, the SS / PBCH block may indicate that it was transmitted according to a transmission pattern, and the SS / PBCH block in the transmission pattern is at a known distance from the frame boundary. 【0137】 The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include a representation of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB can be used by the UE to find the Remaining Minimum System Information (RSSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may contain information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may point to a frequency. The UE may then search for the SS / PBCH block at the frequency pointed to by the UE. 【0138】 A UE can assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index will be quasi-identical (QCL) (e.g., have the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). A UE cannot assume that QCL for SS / PBCH block transmissions will have different SS / PBCH block indices. 【0139】 SS / PBCH blocks (e.g., blocks within a half-frame) can be transmitted in a spatial direction (e.g., using different beams across the cell's coverage area). In one embodiment, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam. 【0140】 In one embodiment, within the carrier frequency span, a base station may transmit multiple SS / PBCH blocks. In one embodiment, the first PCI of the first SS / PBCH block of the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or identical. 【0141】 CSI-RS can be transmitted by a base station and used by an UE to obtain channel status information (CSI). A base station may configure an UE with one or more CSI-RS for channel estimation or any other appropriate purpose. A base station may configure an UE with one or more identical / similar CSI-RS. An UE can measure one or more CSI-RS. Based on the measurement of one or more downlink CSI-RS, an UE can estimate the downlink channel status and / or generate a CSI report. An UE may provide the CSI report to the base station. The base station may perform link fitting using feedback provided by the UE (e.g., estimated downlink channel status). 【0142】 A base station can semi-statically configure a UE with one or more sets of CSI-RS resources. CSI-RS resources may be associated with location and periodicity within the time and frequency domains. A base station can selectively activate and / or deactivate CSI-RS resources. A base station can indicate to the UE that CSI-RS resources within a set of CSI-RS resources are being activated and / or deactivated. 【0143】 A base station can configure a UE to report CSI measurements. The base station can configure a UE to provide CSI reports periodically, irregularly, or semi-permanently. For periodic CSI reports, the UE can consist of multiple CSI reports with varying timing and / or periodicity. For irregular CSI reports, the base station can request the CSI report. For example, the base station can instruct a UE to measure configured CSI-RS resources and provide a CSI report on the measurements. For semi-permanent CSI reports, the base station can configure a UE to periodically send periodic reports and selectively start or stop resources. The base station can use RRC signaling to configure a UE with CSI-RS resource sets and CSI reports. 【0144】 A CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for the downlink CSI-RS and the control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for the downlink CSI-RS and the SS / PBCH block if the downlink CSI-RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block. 【0145】 Downlink DMRS may be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number of front-loaded DMRS symbols (e.g., maximum number) of the PDSCH. A DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, a DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. A wireless network can support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). The DMRS location, DMRS pattern, and / or scrambling sequence may be the same or different. A base station may transmit downlink DMS and the corresponding PDSCH using the same precoding matrix. A UE may use one or more downlink DMRs for coherent demodulation / channel estimation of the PDSCH. 【0146】 In one embodiment, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ based on the fact that the first bandwidth is different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. A set of PRBs may be represented as a precoding resource block group (PRG). 【0147】 A PDSCH may include one or more layers. The UE may assume that at least one symbol having a DMS exists on one or more layers of the PDSCH. The upper layers may constitute up to three DMRSs with respect to the PDSCH. 【0148】 Downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by DCI. If configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters, including at least the MCS. An NR network may support multiple PT-RS densities defined in the time and / or frequency domains. Frequency domain densities, if present, can be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS may be limited to the UE's scheduled time / frequency period. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver. 【0149】 The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit uplink DMR on PUSCH and / or PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. The NR network may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or DMRS scramble array may be identical or different. 【0150】 PUSCH may include one or more layers, and UE may transmit at least one symbol having a DMS present on one or more layers of PUSCH. In one embodiment, the upper layers may constitute up to three DMRSs relative to PUSCH. 【0151】 Uplink PT-RS (which may be used by base stations for phase tracking and / or phase noise compensation) may or may not be present depending on the UE's RRC configuration. The presence and / or pattern of uplink PT-RS can be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters, including at least the MCS. A radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, can be associated with at least one configuration of the scheduled bandwidth. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the UE's scheduled time / frequency period. 【0152】 SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link fitting. The SRS transmitted by the UE may enable the base station to estimate the uplink channel state at one or more frequencies. The base station's scheduler can use the estimated uplink channel state to allocate one or more resource blocks for uplink push transmissions from the UE. The base station can semi-statically configure the UE with one or more SRS resource sets. In the case of an SRS resource set, the base station can configure the UE with one or more SRS resources. The applicability of an SRS resource set can be determined by higher-layer (e.g., RRC) parameters. For example, if higher-layer parameters indicate beam management, SRS resources within one or more SRS resource sets (e.g., having identical / similar time-domain behavior, periodicity, aperiodicity, and / or homogeneous characteristics) can be transmitted instantaneously (e.g., simultaneously). The UE can transmit one or more SRS resources within an SRS resource set. NR networks may support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, which may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In one embodiment, at least one DCI format may be used for the UE to select at least one of one or more configured sets of SRS resources. SRS trigger type 0 may refer to an SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In one embodiment, if a PUSCH and an SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the PUSCH and the corresponding uplink DMRS transmission. 【0153】 A base station can quasi-statistically configure a UE using one or more SRS configuration parameters that indicate at least one of the following: SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., representation of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, cyclic shift, and / or SRS sequence ID. 【0154】 Antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. When a first and second symbol are transmitted on the same antenna port, a receiver can infer the channel for carrying the second symbol on the antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying the first symbol on the antenna port. The first and second antenna ports may be said to be quasi-coordinated (QCL) if one or more large-scale properties of the channel on which the first symbol on the first antenna port is transmitted can be inferred from the channel on which the second symbol on the second antenna port is transmitted. One or more large-scale properties may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters. 【0155】 In channels using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam display. The beam may be associated with one or more reference signals. For example, the beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., Channel Status Information Reference Signal (CSI-RS)) and generate a beam measurement report. The UE can perform downlink beam measurement procedures after the RRC connection is set up at the base station. 【0156】 Figure 11B shows an example of a Channel State Information Reference Signal (CSI-RS) mapped to time and frequency domains. The square shown in Figure 11B may span resource blocks (RBs) within the cell bandwidth. A base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RSs. One or more of the following parameters can be set by higher-layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration. CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., position of symbols and resource elements (REs) within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-identical location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters. 【0157】 The three beams shown in Figure 11B can be configured for a UE with a UE-specific configuration. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), and more or fewer beams can be configured. Beam #1 may be assigned as CSI-RS1101 transmitted on one or more subcarriers within the RB of a first symbol. Beam #2 may be assigned as CSI-RS1102 transmitted on one or more subcarriers within the RB of a second symbol. Beam #3 may be assigned as CSI-RS1103 transmitted on one or more subcarriers within the RB of a third symbol. By using frequency division multiplexing (FDM), a base station may transmit another CSI-RS associated with another UE's beam using other subcarriers within the same RB (e.g., those not used to transmit CSI-RS1101). By using time-domain multiplexing (TDM), the beam used for a UE may be configured so that the UE's beam uses symbols from other UEs' beams. 【0158】 The CSI-RS (e.g., CSI-RS1101, 1102, 1103) shown in Figure 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, a UE may measure the reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In one embodiment, the base station may determine one or more transmit configuration indication (TCI) states, including several reference signals, based on the reported measurement results. In one embodiment, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission with a received (Rx) beam determined based on one or more TCI states. In one embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, it may determine the spatial domain filter of the transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, it may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and display an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE. 【0159】 In beam management procedures, the UE may evaluate (e.g., measure) the channel quality of one or more beampair links, including a transmit beam transmitted by a base station and a receive beam received by the UE. Based on the evaluation, the UE may send a beam measurement report indicating one or more beampair quality parameters, including, for example, one or more beam identities (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI). 【0160】 Figure 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements on the transmit (Tx) beam of a transmit / receive point (TRP) (or multiple TRPs) to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP may include a Tx beam sweep of the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE may include an Rx beam sweep for the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows, as shown in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements on the Tx beam of a TRP (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top row of P2). The UE and / or base station may perform step P2 using a smaller set of beams than those used in step P1, or using a narrower beam than those used in step P1. This may be called beam refinement. The UE may perform step P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE. 【0161】 Figure 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used to allow a base station to perform measurements on a UE's Tx beam to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotated around a measurement, indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station may include, for example, an Rx beam sweep from a set of beams (shown as ellipses rotated counterclockwise, as indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to allow a base station to adjust its Rx beam when the UE is using a fixed Tx beam. The UE and / or base station may perform procedure U2 using a smaller set of beams than used in procedure P1, or using a narrower beam than the beam used in procedure P1. This can also be called beam refinement. The UE can perform procedure U3 to adjust the Tx beam when the base station is using a fixed Rx beam. 【0162】 Based on the detection of a beam fault, the UE may initiate a beam fault recovery (BFR) procedure. Based on the initiation of the BFR procedure, the UE may send a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or similar). The UE may detect a beam fault based on the determination that the quality of the beam pair link of the relevant control channel is unsatisfactory (e.g., having an error rate higher than the error rate threshold, a received signal power lower than the received signal power threshold, a timer expiring, and / or similar). 【0163】 A UE may measure the quality of a beampair link using one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulated reference signals (DMRS). The quality of a beampair link may be based on one or more of the block error rate (BLER), RSRP value, signal-to-interference plus noise ratio (SINR) value, reference signal received quality (RSRQ) value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource is quasi-coordinated (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DMRS of a channel may be QCLed if the channel characteristics from a transmission to the UE via the RS resource (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics from a transmission to the UE via the channel. 【0164】 A network (e.g., the network's gNB and / or ng-eNB) and / or UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or the RRC_INACTIVE state may initiate a random access procedure to request network connection setup. A UE may initiate a random access procedure from the RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or obtain uplink timing (e.g., if the uplink synchronization state is not synchronized). A UE may initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar ones). A UE may initiate a random access procedure for beam fault recovery requests. A network may initiate a random access procedure to establish time alignment for handover and / or SCell addition. 【0165】 Figure 13A shows a four-step competition-based random access procedure. Before the procedure begins, the base station may send a configuration message 1310 to the UE. Figure 13A includes the sending of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include a preamble (or random access preamble) and / or may be referred to as a preamble. Msg2 1312 may include a random access response (RAR) and / or may be referred to as a random access response (RAR). 【0166】 Configuration message 1310 may be transmitted, for example, using one or more RRC messages. One or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. One or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-configCommon), and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast one or more RRC messages to one or more UEs. One or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). Based on one or more RACH parameters, the UE may determine the time-frequency resources and / or uplink transmit power for transmitting Msg1 1311 and / or Msg3 1313. Based on one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314. 【0167】 One or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for sending Msg1 1311. One or more PRACH opportunities may be predefined. One or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH opportunities and / or the number of preambles mapped to SS / PBCH blocks. 【0168】 One or more RACH parameters provided in configuration message 1310 may be used to determine the uplink transmit power for Msg1 1311 and / or Msg3 1313. For example, one or more RACH parameters may indicate reference power for preamble transmission (e.g., received target power and / or initial power for preamble transmission). One or more power offsets may be indicated by one or more RACH parameters. For example, one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. One or more RACH parameters may indicate one or more thresholds for the UE to determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., normal uplink (NUL) carrier and / or complementary uplink (SUL) carrier). 【0169】 Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). RRC messages may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble groups based on the path loss measurement and / or the size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may, for example, select at least one preamble to be associated with one or more reference signals and / or the selected preamble group, if the association between one or more preambles and at least one reference signal is constituted by an RRC message. 【0170】 The UE may determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE may determine the preamble based on path loss measurements, RSRP measurements, and / or the size of Msg3 1313. In another embodiment, one or more RACH parameters may indicate the preamble format, the maximum number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure the UE with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). If associations are configured, the UE may determine, based on the associations, to include the preamble in Msg1 1311. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and one or more reference signals. 【0171】 The UE may perform a preamble retransmission if no response is received after a preamble transmission. The UE may increase the uplink transmit power for preamble retransmission. The UE may select an initial preamble transmit power based on path loss measurements and / or target received preamble power configured by the network. The UE may decide to retransmit the preamble and ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramping step for preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmit power for retransmission. The UE may ramp up the uplink transmit power if it determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_STATEER). The UE may determine that a random access procedure has failed and completed if, for example, the number of preamble transmissions exceeds a threshold determined by one or more RACH parameters (e.g., preambleTransMax). 【0172】 Msg2 1312 received by the UE may include RARs. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and displayed on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may include time alignment commands that the UE can use to adjust the UE's transmission timing, scheduling permission for the transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg2 1312. A UE may determine when to start a time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, a UE may start a time window after one or more symbols of the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of preamble transmission). One or more symbols may be determined based on numerology. PDCCH may be in a common lookup space composed of RRC messages (e.g., a Type1-PDCCH common lookup space). A UE may identify a RAR based on a Radio Network Temporary Identifier (RNTI). An RNTI may be used in response to one or more events that initiate a Random Access Procedure. A UE may use a Random Access RNTI (RA-RNTI). An RA-RNTI may be associated with a PRACH opportunity that the UE uses to transmit the preamble. For example, a UE may determine an RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicators of the PRACH opportunity. An example of an RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier). A UE may send Msg3 1313 in response to the successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312). Msg3 1313 may be used for conflict resolution in a conflict-based random access procedure, for example, as shown in Figure 13A. In some scenarios, multiple UEs may send the same preamble to a base station, and the base station may provide a RAR corresponding to the UEs. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Conflict resolution (e.g., using Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To implement conflict resolution, a UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other appropriate identifier). 【0173】 Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is found on the PDCCH, the random access procedure is determined to have completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., if the UE is in the RRC_IDLE state or otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted in Msg3 1313 (e.g., transmitted) or otherwise contains the corresponding UE conflict resolution identity .'' CE, the UE may determine that conflict resolution was successful, and / or the UE may determine that the random access procedure has completed successfully. 【0174】 A UE may consist of a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedures) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, i.e., one for the SUL carrier and the other for the NUL carrier. For random access within a cell configured with SUL carriers, the network may indicate which carrier (NUL or SUL) to use. A UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is below the broadcast threshold. Uplink transmissions of random access procedures (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more instances, a UE may switch uplink carriers during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch the uplink carrier for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listening before speaking). 【0175】 Figure 13B illustrates a two-step, non-conflict random access procedure. Similar to the four-step, conflict-based random access procedure shown in Figure 13A, the base station may send a configuration message 1320 to the UE before the procedure begins. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B includes the sending of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312 shown in Figure 13A, respectively. As can be understood from Figures 13A and 13B, a non-conflict random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314. 【0176】 The uncontested random access procedure shown in Figure 13B may be initiated for beam fault recovery, other SI requests, SCell additions, and / or handovers. For example, the base station may display or assign the preamble to be used for Msg1 1321 to the UE. The UE may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via the PDCCH and / or RRC. 【0177】 After sending the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the RAR's PDCCH. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to Cell RNTI (C-RNTI) in the search space. In the uncontested random access procedure shown in Figure 13B, the UE may determine that the random access procedure has completed successfully after sending Msg1 1321 and receiving the corresponding Msg2 1322, or in response to it. The UE may determine that the random access procedure has completed successfully, for example, if a PDCCH transmission is addressed to C-RNTI. The UE may determine that the random access procedure has completed successfully, for example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble sent by the UE, and / or if the RAR contains a MAC sub-PDU containing the preamble identifier. The UE may determine the response as an indicator of confirmation for the SI request. 【0178】 Figure 13C illustrates another two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may send a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 may be similar in some respects to configuration messages 1310 and / or 1320. Figure 13C includes the transmission of two messages, namely Msg A 1331 and Msg B 1332. 【0179】 Msg A 1331 may be transmitted by the UE via uplink transmission. Msg A 1331 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. Transport block 1342 may include content similar to and / or equivalent to the content of Msg 3 1313 shown in Figure 13A. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after transmitting Msg A 1331 or in response to such transmission. Msg B 1332 may include content similar to and / or equivalent to the content of Msg 2 1312 (e.g., RAR) shown in Figures 13A and 13B, and / or Msg 4 1314 shown in Figure 13A. 【0180】 A UE may initiate the two-step random access procedure shown in Figure 13C for licensed and / or unlicensed spectra. The UE may decide whether to initiate the two-step random access procedure based on one or more factors. One or more factors may be the radio access technology in use (e.g., LTE, NR, and / or similar), whether the UE has a valid TA, cell size, the UE's RRC status, the type of spectrum (e.g., licensed versus unlicensed), and / or any other appropriate factors. 【0181】 The UE may determine the radio resources and / or uplink transmit power for the transport block 1342 contained in the preamble 1341 and / or Msg A 1331 based on the two-step RACH parameters contained in configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmitting the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332. 【0182】 Transport block 1342 may include data (e.g., latency-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier, timing advance commands, power control commands, uplink authorization (e.g., radio resource allocation and / or MCS), a UE identifier for conflict resolution, and / or RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure has been successfully completed if the preamble identifier in Msg B 1332 matches a preamble sent by the UE, and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342). 【0183】 UEs and base stations may exchange control signaling. Control signaling may also be called L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). Control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station. 【0184】 Downlink control signaling may include downlink scheduling assignments, uplink scheduling authorizations indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or other appropriate signaling. A UE may receive downlink control signaling in a payload transmitted by a base station on a physical downlink control channel (PDCCH). The payload transmitted on a PDCCH may be called downlink control information (DCI). In some scenarios, the PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of UEs. 【0185】 A base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate the detection of transmission errors. If the DCI is intended for a UE (or group of UEs), the base station may scramble the CRC parity bits with the UE identifier (or identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may involve a Modulo-2 append (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a Radio Network Temporary Identifier (RNTI). 【0186】 DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. A P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. A SI-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of a dynamic schedule and / or a random access trigger for a PDCCH sequence. A DCI with a scrambled CRC parity bit in a temporary cell RNTI (TC-RNTI) may exhibit conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTI encodings configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or similar. 【0187】 Depending on the purpose and / or content of the DCI, the base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 can be used for scheduling pushes within a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling pushes within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for scheduling PDSCHs within a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCHs within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format representation to a group of UEs. DCI format 2_1 may be used to notify a group of UEs of physical resource blocks and / or OFDM symbols that the UEs assume are not intended to be transmitted to the UEs. DCI format 2_2 may be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used to transmit a group of TPC commands for SRS transmission by one or more UEs. New DCI formats may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size. 【0188】 After scrambling the DCI with RNTI, the base station may process the DCI using channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the DCI payload size and / or base station coverage, the base station may transmit the DCI over a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (called the aggregate level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may include a number of resource-element groups (REGs) (e.g., 6). A REG may include resource blocks within OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mappings of CCEs and REGs (e.g., CCE-to-REG mappings). 【0189】 Figure 14A shows an embodiment of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources that the UE attempts to decode the DCI using one or more lookup spaces. A base station may configure a CORESET within a time-frequency domain. In the embodiment of Figure 14A, the first CORESET 1401 and the second CORESET 1402 occur in the first symbol in the slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 occurs in the third symbol in the slot. The fourth CORESET 1404 occurs in the seventh symbol in the slot. A CORESET may have a different number of resource blocks within the frequency domain. 【0190】 Figure 14B shows an example of CCE-to-REG mapping for DCI transmissions on CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings on different CORESETs. A CORESET may be associated with CCE-to-REG mappings in an RRC configuration. A CORESET may consist of antenna port quasi-identical location (QCL) parameters. The antenna port QCL parameters may indicate QCL information for demodulated reference signals (DMRS) for PDCCH reception within the CORESET. 【0191】 A base station can send an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters may indicate the relationship between the search space set and the CORESET. A search space set may include a set of PDCCH candidates formed by CCEs at a given aggregate level. The configuration parameters may indicate the number of PDCCH candidates monitored per aggregate level, the PDCCH monitoring period and PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in a common search space set may be predefined and known to the UE. The set of CCEs in a UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI). 【0192】 As shown in Figure 14B, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE-REG mapping to the CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based on the CORESET configuration parameters. The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs in a common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. Decoding may be called blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., a scramble bit against the CRC parity bit of a DCI that matches an RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink permission, power control, slot format indication, downlink preemption, and / or similar). 【0193】 The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. After receiving the DL-SCH transport block, the UE may transmit a HARQ acknowledgment. The uplink control signaling may include channel status information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters for downlink transmission (e.g., including multi-antenna and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) over the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats. 【0194】 Five PUCCH formats are possible, and a UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and the number of UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 0 to transmit a UCI on a PUCCH resource if the transmission exceeds one or two symbols and has one or two HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits). PUCCH format 1 may occupy a number between 4 and 14 OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 1 if the transmission consists of four or more symbols and has one or two HARQ-ACK / SR bits. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A UE may use PUCCH format 2 if the transmission exceeds one or two symbols and has two or more UCI bits. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource does not contain orthogonal cover codes. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource contains orthogonal cover codes. 【0195】 A base station may, for example, use an RRC message to send configuration parameters for multiple PUCCH resource sets to the UE. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the cell's uplink BWP. A PUCCH resource set may consist of multiple PUCCH resources, each having a PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number of UCI information bits (e.g., maximum number) that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is 2 or less, the UE may select the first PUCCH resource set whose PUCCH resource set index is equal to "0". If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first set value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first set value and less than or equal to the second set value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second set value and less than or equal to the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3". 【0196】 After determining a PUCCH resource set from multiple PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine a PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., DCI format 1_0 or DCI format 1_1) received on the PDCCH. A 3-bit PUCCH resource indicator in a DCI may indicate one of eight PUCCH resources in a PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit a UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI. 【0197】 Figure 15 shows an embodiment of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in Figure 1A, the mobile communication network 150 shown in Figure 1B, or other communication networks. Only one wireless device 1502 and one base station 1504 are shown in Figure 15. However, it will be understood that a mobile communication network may include multiple UEs and / or multiple base stations having the same or similar configuration as shown in Figure 15. 【0198】 Base station 1504 may connect radio device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The communication direction from base station 1504 to radio device 1502 over air interface 1506 is known as the downlink, and the communication direction from radio device 1502 to base station 1504 over air interface is known as the uplink. Downlink transmissions may be isolated from uplink transmissions using FDD, TDD, and / or some combination of the two redundancy techniques. 【0199】 In the downlink, data transmitted from base station 1504 to radio device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, the core network. In the uplink, data transmitted from radio device 1502 to base station 1504 may be provided to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B. 【0200】 Data that has been processed by processing system 1508 and is to be transmitted to radio device 1502 may be provided to the transmission processing system 1510 of base station 1504. Similarly, data that has been processed by processing system 1518 and is to be transmitted to base station 1504 may be provided to the transmission processing system 1520 of radio device 1502. Transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple input multiple output (MIMO) or multi-antenna processing, and / or similar. 【0201】 At base station 1504, receiving processing system 1512 may receive uplink transmissions from radio device 1502. At radio device 1502, receiving processing system 1522 may receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For receiving processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or similar. 【0202】 As shown in Figure 15, the wireless device 1502 and the base station 1504 may include multiple antennas. Multiple antennas may be used to implement one or more MIMO or multi-antenna techniques such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other embodiments, the wireless device 1502 and / or the base station 1504 may have a single antenna. 【0203】 Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although not shown in Figure 15, transmitting processing systems 1510, 1520, receiving processing system 1512, and / or receiving processing system 1522 may be coupled to memories (e.g., one or more non-temporary computer-readable media) that store computer program instructions or code that can be executed to perform one or more of their respective functions. 【0204】 Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. One or more controllers and / or one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and base station 1504 to operate in a wireless environment. 【0205】 Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and / or one or more peripheral devices 1526, respectively. One or more peripheral devices 1516 and / or one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functions, such as speakers, microphones, keypads, display devices, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, electronic control units (e.g., for vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, and / or similar). Processing system 1508 and / or processing system 1518 may receive user input data from one or more peripheral devices 1516 and / or one or more peripheral devices 1526, and / or provide user output data. The processing system 1518 within the wireless device 1502 can receive power from a power source and / or be configured to distribute power to other components within the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipsets 1517 and 1527, respectively. The GPS chipsets 1517 and 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively. 【0206】 Figure 16A shows an exemplary structure for uplink transmission. A baseband signal representing a physical uplink shared channel can perform one or more functions. These functions may include scrambling, modulating scrambled bits to generate complex-valued symbols, mapping complex-valued modulated symbols onto one or more transmit layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency-division multiplexed access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or at least one of the same. In one embodiment, if conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one embodiment, if conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by Figure 16A. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments. 【0207】 Figure 16B shows an exemplary structure for modulation and upconversion of a baseband signal to the carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal to the antenna port. Filtering may be used before transmission. 【0208】 Figure 16C shows an exemplary structure of a downlink transmit. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include scrambling the encoded bits in the codeword to be transmitted over the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmit layers, precoding the complex-valued modulation symbol on the layer for transmission over the antenna port, mapping the complex-valued modulation symbol to resource elements at the antenna port, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments. 【0209】 Figure 16D shows another exemplary implementation structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for the antenna port. Filtering may be used before transmission. 【0210】 A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in a dual connection) via multiple cells. One or more messages (e.g., as part of configuration parameters) may include parameters for the physical, MAC, RLC, PCDP, SDAP, and RRC layers to configure the wireless device. For example, configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, configuration parameters may include parameters indicating timer values ​​for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels. 【0211】 A timer, once started, begins execution and may continue execution until stopped or expired. A timer may be started if it is not running, or restarted if it is running. A timer may be associated with a value (for example, a timer may start or restart from a certain value, or start from zero and expire when a value is reached). The duration of a timer may not be updated until the timer is stopped or expires (for example, by BWP switching). Timers can be used to measure the duration / window of a process. Where this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways of implementing one or more timers. For example, it will be understood that one or more of the multiple ways of implementing a timer may be used to measure the duration / window of a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In one embodiment, instead of the start and expiration of a random access response window timer, a time difference between two timestamps may be used. When the timer is restarted, the process for measuring the time window may be restarted. Other exemplary implementations may be provided for restarting the measurement of a time window. 【0212】 In existing sidelink technologies, a transmitter radio device may select a radio resource for transmitting sidelink packets based on radio resource sensing results or resource allocation from a base station. In one embodiment, a second radio device may communicate with a first radio device while communicating with a third network node (e.g., gNB, eNB, UE, etc.). If the first radio device transmits a packet to the second radio device while the second radio device is transmitting / receiving signals to / from the third network node, as shown in Figure 17, the second radio device may not be able to reliably receive the packet from the first radio device, or it may be interfered with by the first radio device receiving signals from the third network node via the packet. Existing technologies can increase the packet loss rate of radio devices during sidelink communication, reducing service reliability. 【0213】 Exemplary embodiments may support a transmitter radio device receiving resource coordination information (e.g., resource gap requests, support information) from a receiver radio device (e.g., a peer radio device). The transmitter radio device may transmit resource coordination information to a base station to help the base station consider the receiver radio device's resource coordination requests when allocating sidelink radio resources for communication between the transmitter radio device and the receiver radio device. Exemplary embodiments may support the transmitter radio device in avoiding packet transmission when the receiver radio device sends and receives signals to and from another network node by selecting packet transmission resources that do not overlap with the radio resources indicated in the resource coordination information from the receiver radio device. Exemplary embodiments may support a base station of a transmitter radio device receiving resource coordination information (e.g., resource gap requests, support information) via the transmitter radio device from the receiver radio device (e.g., a peer radio device) or from another base station corresponding to the receiver radio device. The base station may consider the receiver radio device's resource coordination information when allocating sidelink radio resources for communication between the transmitter radio device and the receiver radio device. The resource coordination information may indicate the priority level of resource gaps for the receiver radio device. A base station or transmitter radio device may allocate resources that may overlap with the resource gap requested by a receiver radio device if the priority of the packets to be transmitted to the receiver radio device is higher (e.g., more important) than the priority level of the resource gap requested by the receiver radio device. Exemplary embodiments may reduce the packet loss rate during sidelink communication and increase the reliability of the communication service. 【0214】 In one embodiment, D2D (device-to-device) communication literally means communication between electronic devices. According to a D2D communication scheme or UE-to-UE communication scheme, data can be exchanged between UEs without passing through a base station. A link established directly between devices may be called a D2D link or side link. D2D communication can have advantages in that it reduces latency and requires fewer radio resources compared to legacy base station-centric communication schemes. In this case, the UE corresponds to a user's terminal, but if a network device such as an eNB or gNB transmits and receives signals according to an UE-to-UE communication scheme, the network device can be considered a type of UE. 【0215】 Figure 29 shows an example of a UE type deployment performing D2D communication and cell coverage. Referring to Figure 29A, UE types A and B may be located outside the cell coverage. Referring to Figure 29B, UE A may be located inside the cell coverage, and UE B may be located outside the cell coverage. Referring to Figure 29C, UE types A and B may be located within a single cell coverage. Referring to Figure 29D, UE A may be located within the coverage of a first cell, and UE B may be located within the coverage of a second cell. 【0216】 In one embodiment, D2D transmission signals transmitted over a sidelink may be divided into discovery and communication signals. Discovery signals correspond to signals used by a UE to determine multiple UEs adjacent to it. An example of a sidelink channel for sending and receiving discovery signals is the Physical Sidelink Discovery Channel (PSDCH). Communication signals correspond to signals for transmitting general data (e.g., voice, images, video, safety information, etc.) transmitted by the UE. Examples of sidelink channels for sending and receiving communication signals include the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). 【0217】 Figure 30 shows an embodiment of UE A, UE B, and the radio resources used by UE A and UE B to perform D2D communication. In Figure 30A, a UE corresponds to such a network device, either as a terminal or a base station that sends and receives signals according to a D2D communication scheme. A UE selects a resource unit corresponding to a specific resource from a resource pool corresponding to a resource set, and the UE uses the selected resource unit to transmit a D2D signal. UE B, corresponding to a receiving UE, receives the configuration of the resource pool from which UE A can transmit a signal and from which UE B can detect UE A's signal in the resource pool. In this case, if UE A is located inside the base station's network coverage, the base station may inform UE A of the resource pool. If UE A is located outside the base station's network coverage, the resource pool may be informed by a different UE or may be determined by a pre-configured resource pool. Generally, a resource pool contains multiple resource units. A single resource unit may consist of a group of resource blocks. A UE may select one or more resource units from multiple resource units and use the selected resource units for D2D signal transmission. Figure 30B shows an example of how a resource unit is configured. Referring to Figure 30B, all frequency resources are divided into Nf resource units per unit time resource (e.g., a slot or a group of slots). The resource pool may repeat with unit time resources of period k, and the resource pool may be configured within a bandwidth portion for D2D or sidelink communication. Specifically, as shown in Figure 30, a single resource unit may repeat periodically, or the index of the physical resource unit to which a logical resource unit is mapped may change in a predetermined pattern over time to obtain diversity gains in the time domain and / or frequency domain. In this resource unit structure, the resource pool may correspond to a set of resource units that can be used by a UE intended to transmit or receive D2D signals. 【0218】 In one embodiment, resource pools can be classified into various types. Resource pools can be classified according to the content of the D2D signals transmitted through each resource pool. For example, the content of D2D signals may be classified into various signals, and separate resource pools can be configured according to each of these contents. The content of D2D signals may include a D2D control channel, a D2D data channel, and / or a discovery channel. A D2D control channel may correspond to signals containing information about the resource location of the D2D data channel, information about the MCS required for modulation and demodulation of the data channel, information about the MIMO transmission scheme, information about packet priority, information about target coverage, and information about QoS requirements. A D2D control channel may be transmitted on the same resource unit in a manner that is multiplexed with the D2D data channel. In this case, a D2D control and data channel resource pool may correspond to a pool of resources transmitted in a manner that multiplexes D2D control and D2D data. As shown in Figure 34, a D2D control channel may also be called a PSCCH (Physical Sidelink Control Channel). A D2D data channel (or PSSCH (Physical Sidelink Shared Channel)) corresponds to a resource pool used by a transmitting UE to transmit user data. When D2D control and D2D data are transmitted in a way that multiplexes within the same resource unit, the D2D data channel, excluding the D2D control information, can only be transmitted within the D2D data channel resource pool. In other words, a resource element (RE) used to transmit D2D control information within a specific resource unit of the D2D control resource pool can also be used to transmit D2D data within the D2D data channel resource pool. A discovery channel may correspond to a resource pool of messages that allows neighboring UEs to discover a transmitting UE transmitting information such as the UE's ID. 【0219】 In one embodiment, resource pools may be categorized to support different QoS levels or different services. For example, the priority level of each resource pool may be configured by the base station, or the services supported for each resource pool may have different configurations. Alternatively, a particular resource pool may be configured to use only a specific unicast or groupcast UE. The content of D2D signals may be identical to each other, but different resource pools may be used depending on the transmit and receive attributes of the D2D signals. For example, for the same D2D data channel or the same discovery message, the D2D data channel or discovery signal may be categorized into different resource pools according to the D2D signal transmission timing determination scheme (e.g., whether the D2D signal is transmitted with a predetermined timing advance added when a synchronization reference signal is received), resource allocation scheme (e.g., whether the transmit resources for individual signals are specified by the base station, or whether individual transmit UEs select individual signal transmit resources from a pool), signal format (e.g., the number of symbols occupied by the D2D signal in a subframe, the number of subframes used to transmit the D2D signal), signal strength from the base station, the transmit power strength of the D2D UE, etc. To clarify, the method by which a base station directly specifies the transmit resources for a D2D transmitting UE is called Mode 1 (e.g., Mode 1 operation). In Mode 1, a base station such as an eNB or gNB may transmit a DCI to schedule D2D signal transmission. When a transmit resource area (or resource pool) is (pre)configured, or when the base station specifies a transmit resource area or resource pool, and the UE directly selects a transmit resource from the transmit resource area (or resource pool), it is called Mode 2 (e.g., Mode 2 operation). When D2D discovery is performed and the base station directly indicates the transmit resources, it is called Type 2. When the UE directly selects a transmit resource from a predetermined resource pool or resource pool indicated by the base station, it is called Type 1. 【0220】 In one embodiment, time and frequency synchronization may be required between two UEs for D2D communication. If the two UEs belong to cell coverage, they may be synchronized by PSS / SSS or similar signals transmitted by a base station, and time / frequency synchronization may be maintained between the two UEs at a level that allows the two UEs to directly transmit and receive signals. Alternatively, one UE may transmit a synchronization signal, and the other UE may be synchronized to the synchronization signal transmitted by the other UE. This synchronization signal transmitted by the other UE may be called a sidelink synchronization signal (SLSS). SLSS may include a sidelink primary synchronization signal (S-PSS) and a sidelink secondary synchronization signal (S-SSS). SLSS may be transmitted over a physical sidelink broadcast channel (PSBCH) to convey some basic or initial system information. Furthermore, UEs may use Global Navigation Satellite System (GNSS) timing to synchronize or derive the timing of transmission time intervals (e.g., frames, subframes, slots, and / or similar). S-PSS, S-SSS, and PSBCH may be structured in a block format (sidelink synchronization signal block (S-SSB)) that can support periodic transmission. The S-SSB may have the same numerology (i.e., SCS and CP lengths) as the sidelink data channel and sidelink control channel in the carrier, and the transmit bandwidth may be within the (pre)configured sidelink BWP, and its frequency position may be (pre)configured as shown in Figures 35 and / or 36. This may lead to the need for the UE to perform hypothetical detection at frequency to find the S-SSB in the carrier. The sidelink synchronization source may be a GNSS, gNB, eNB, or NR UE. Each sidelink synchronization source may be associated with a synchronization priority level, which may have a (pre)configured priority. 【0221】 In one embodiment, as shown in Figure 31, the D2D resource pool may divide the bandwidth into multiple subchannels, and each transmitter of multiple neighboring transmitters may select one or more subchannels to transmit its signal. Subchannel selection may be based on received energy measurements and / or control channel decoding. For example, a UE may identify which subchannels are used by other UEs based on control channel decoding and energy measurements for each subchannel. Here, system performance limitations may be imposed by in-band radiation. In-band radiation (IBE) is interference caused by one transmitter transmitting on one subchannel and imposed on another transmitter transmitting to a receiver on another subchannel. Figure 31 shows an in-band radiation model. Referring to Figure 31, the plot of the in-band radiation model shows that nearby subchannels as well as other subchannels (e.g., I / Q or image subchannels) experience more interference. 【0222】 In one embodiment, when a D2D UE operates within a cellular network, the power radiated by the D2D UE can cause serious interference to cellular communications. In particular, if the D2D UE uses only a portion of the frequency resources in a specific slot or subframe, the in-band radiation of power radiated by the D2D UE can cause serious interference to the frequency resources used by the cellular UE. To prevent this problem, the D2D UE may implement cellular path loss-based power control. At this point, the parameters used for power control (e.g., P0 or alpha) may be configured by the base station. 【0223】 In one embodiment, in D2D communication, a transmitting UE may accommodate a half-duplex UE that cannot receive at the time of transmission. In particular, a transmitting UE may not be able to receive transmissions from different UEs due to the half-duplex problem. To mitigate the half-duplex problem, different D2D UEs communicating must transmit signals using at least one or more different time resources. 【0224】 In one embodiment, D2D operation can offer various advantages in that it involves communication between nearby devices. For example, a D2D UE may have high transfer speeds and low latency for data communication. Furthermore, D2D operation can distribute traffic that is concentrated on the base station. If the D2D UE acts as a relay, it can also extend the coverage of the base station. 【0225】 In one embodiment, as shown in Figure 32, D2D communication may be extended and / or applied to vehicle-to-vehicle signal transmission and / or reception. Vehicle-related communication may also be called vehicle-to-anything (V2X) communication. In V2X, the term "X" refers to pedestrians (communication between a vehicle and a device carried by an individual (e.g., a handheld terminal carried by a pedestrian, cyclist, driver, or passenger)) (in this case, V2X may be denoted as V2P), vehicles (communication between vehicles) (V2V), infrastructure / networks (communication between a vehicle and a roadside unit (RSU) / network (e.g., an RSU is a traffic infrastructure entity implemented in a base station or stationary UE (e.g., an entity that transmits speed notifications))) (V2I / N), etc. For V2X communication, vehicles, RSUs, and handheld devices may include transceivers. Figure 31 shows a diagram of V2X communication. 【0226】 In one embodiment, V2X communication can be used to provide warnings for various events, such as safety concerns. For example, information about events occurring on a vehicle or road can be communicated to another vehicle or pedestrian via V2X communication. For instance, information about traffic accidents, changes in road conditions, or warnings of accidents can be transmitted to another vehicle or pedestrian. For example, pedestrians adjacent to or crossing a road can be informed about vehicle approaches. 【0227】 In one embodiment, in V2X communication, one challenge may be to avoid collisions and ensure a minimum level of communication quality even in high-density UE scenarios. Radio congestion control may represent a family of mechanisms that mitigate such collisions by adjusting communication parameters to control congestion levels on vehicle radio channels and ensure reliable V2X communication. In one embodiment, a radio device may measure the following two metrics to characterize the channel state and enable the radio device to take necessary actions: 1) Channel Busy Radio (CBR): Defined as the portion (or number) of subchannels in a resource pool where the measured RSSI exceeds a pre-configured threshold, and the total frequency resources may be divided into a given number of subchannels. Such metrics may be perceived over the last 100 subframes (the definition of “subframe” in LTE may be used). This may provide an estimate of the overall state of the channel. 2) Channel Occupancy (CR): Calculated in subframe n, defined as the total number of subchannels used for its transmission in subframe [na, n-1] and permitted in subframe [n, n+b], which is obtained by dividing by the total number of subchannels in [na, n+b]. a and b are determined by the station with the limits a+b+1=1000 and a≧500. CR may provide an indication of channel utilization by the transmitter itself. For each interval of CBR values, the CR limit may be defined as a footprint that the transmitter must not exceed. This CR limit may be configured by the base station for each CBR range and packet priority. For example, if a high CBR is observed, a low CR limit may be configured, and a low CR limit may be configured for a low packet priority. When a station decides to transmit a packet, it maps its CBR value to the correct interval to obtain the corresponding CR limit value. If the CR is higher than the CR limit, the radio device may have to reduce its CR to below that limit. It may be left to each implementation to decide which techniques to use to reduce the CR. In one embodiment, the following options for accommodating the CR limit may be considered: 1) Dropped packet retransmission: If the retransmission function is enabled, the station may disable it.2) Dropping packet transmission: The station simply drops packet transmission (including retransmission, if enabled). This is one of the simplest techniques. 3) Adapting MCS: A wireless device can reduce its CR by increasing the MCS index used. This can reduce the number of subchannels used for transmission. However, increasing the MCS reduces message robustness and therefore the message range. 4) Adapting transmit power: The station can reduce its transmit power. As a result, the overall CBR in the region may decrease, and the CR limit value may increase. 【0228】 In one embodiment, in open-loop MIMO, the preferred PMI may not be shown by the receiver. In this case, periodic delay diversity (CDD) may be considered to improve decoding performance. CDD may involve transmitting the same set of different delays on each antenna. The delay may be applied before the periodic prefix is ​​added, thereby ensuring that the delay can be periodic over the FFT size. This gives CDD its name. The addition of the time delay may be equivalent to the application of a phase shift in the frequency domain. Since the same time delay is applied to all subcarriers, the phase shift increases linearly across the subcarriers as the subcarrier frequency increases. Thus, each subcarrier may experience a different beamforming pattern because an undelayed subcarrier from one antenna constructively and destructively interferes with the delayed version from another antenna. Thus, the diversity effect of CDD arises from the fact that different subcarriers pick up different spatial paths within the propagation channel, thereby increasing the frequency selectivity of the channel. Channel coding applied to the entire transport block across subcarriers ensures that the entire transport block benefits from the diversity of spatial paths. The general principle of CDD technique is shown in Figure 33. The fact that the delay is added before the CP means that any delay value can be used without increasing the overall delay spread of the channel. If the delay value is greater than the CP length, an additional RS must be sent to estimate the delayed version of the channel differently. To distinguish between the two cases, a scheme that uses a delay shorter than the CP length is called a small-delay CDD (SD-CDD), and another scheme that requires an additional RS with a delay greater than the CP length is called a large-delay CDD (LD-CDD). 【0229】 In one embodiment, as shown in Figure 17 and / or Figure 20, a first wireless device (e.g., UE1, a first vehicle, a first side-link wireless device, a first inter-device communication wireless device, etc.) may communicate with a second wireless device (e.g., UE2, a second vehicle, a second side-link wireless device, a second inter-device communication wireless device, etc.). The first wireless device may have a PC5-RRC connection with the second wireless device. The first wireless device may have a direct connection (e.g., a side-link direct communication connection), a PC5 connection, a side-link connection, and / or similar connections with the second wireless device. In one embodiment, the second wireless device may communicate with a network node (e.g., a fourth wireless device, a second base station, another node, one or more network nodes, base stations, wireless devices, etc.). 【0230】 In one embodiment, a first wireless device may communicate with a third wireless device (e.g., a UE3, a third vehicle, a third sidelink wireless device, a third inter-device communication wireless device, etc.). The first wireless device may be connected to the third wireless device via at least one of a second PC5-RRC connection, a second direct connection (e.g., a sidelink direct communication connection), a second PC5 connection, a second sidelink connection, and / or similar. The first wireless device may multicast / broadcast / transmit transport blocks to the second wireless device and / or the third wireless device. The first wireless device, the second wireless device, and / or the third wireless device may belong to the same sidelink multicast group. 【0231】 In one embodiment, as shown in Figures 18 and / or 19, a first radio device may have an RRC connection with a first base station (e.g., gNB1, gNB, eNB, RNC, IAB-node, IAB-donor, gNB-DU, gNB-CU, access node, etc.). The first base station may be a serving base station for the first radio device. The first base station may serve the first radio device via at least one serving cell (e.g., including at least one of a first primary cell, one or more first secondary cells, etc.). The first base station may be a camp-on base station for the first radio device (e.g., when the first radio device is in an RRC inactive state and / or an RRC idle state). The first radio device may communicate with a second radio device based on mode 1 operation or mode 2 operation. 【0232】 In one embodiment, as shown in Figures 21 and / or 22, the second radio device may be connected to a second base station (e.g., gNB2, gNB, eNB, RNC, IAB-node, IAB-donor, gNB-DU, gNB-CU, access node, etc.). The second radio device may have an RRC connection with the second base station. In one embodiment, the second radio device may be in an RRC idle state or an RRC inactive state in the cell of the second base station. In one embodiment, the first base station may have a direct connection (e.g., Xn interface, X2 interface, etc.) and / or an indirect connection (e.g., via one or more N2 / S1 interfaces, one or more AMF / MME, etc.). 【0233】 In one embodiment, as shown in Figures 18 and / or 19, the first radio device may receive at least one sidelink message from the second radio device containing gap request information for the second radio device. The gap request information may indicate at least one of the following: gap periodicity, gap time offset, gap priority level, and / or similar. In one embodiment, the second radio device may receive resource scheduling information indicating a radio resource from a network node (e.g., a serving base station, a second base station, another radio device). The second radio device may determine the gap request information based on the resource scheduling information and / or data generation information of the second radio device. In one embodiment, the first radio device may transmit at least one uplink RRC message containing the gap request information for the second radio device to the first base station. The first base station may determine the sidelink radio resource for the first radio device based on the gap request information. The sidelink radio resource may be for transmission from the first radio device to the second radio device. The first radio device may receive a resource authorization from the first base station indicating the sidelink radio resource determined based on the gap request information. The first wireless device may transmit a transport block to the second wireless device via a sidelink wireless resource. 【0234】 In one embodiment, as shown in Figure 20, a first radio device (e.g., operating in mode 2 or mode 1 with a configured authorized resource) may determine whether the priority level of a gap is equal to or higher than the logical channel associated with the transport block. Based on this determination, in response that the priority level of the gap is higher than the logical channel, the first radio device may transmit the transport block over a radio resource that does not overlap with the gap, and in response that the priority level of the gap is equal to or lower than the logical channel, the first radio device may transmit the transport block over a radio resource determined independently of the gap. 【0235】 In one embodiment, as shown in Figures 21 and / or 22, a first base station may receive device information for a second radio device from a first radio device. The device information may indicate a serving cell, a serving base station, a resource pool, a zone, and / or at least one of the same. Based on the device information, the first base station may identify the second base station corresponding to the second radio device. The first base station may send a request for resource coordination information for the second radio device to the second base station. The first base station may receive resource coordination information, including gap request information, from the second base station. Based on the gap request information, the first base station may determine the sidelink radio resources to transmit from the first radio device to the second radio device. The first base station may send a resource authorization to the first radio device indicating the sidelink radio resources. 【0236】 In one embodiment, a first wireless device may establish a PC5 RRC connection with a second wireless device. For direct sidelink communication, the first wireless device may send a direct communication request to the second wireless device, and the first wireless device may receive a direct communication response in response to the direct communication request. For direct sidelink communication, the first wireless device may receive a direct communication request from the second wireless device, and the first wireless device may receive a direct communication response in response to the direct communication request. Based on direct sidelink communication, the first wireless device may transmit first sidelink function information of the first wireless device to the second wireless device, and / or receive second sidelink function information of the second wireless device from the second wireless device. Based on direct sidelink communication, the first wireless device may transmit one or more first PC5-RRC configuration parameters to the second wireless device in order to configure a PC5 RRC connection between the first wireless device and the second wireless device. Based on direct sidelink communication, the first wireless device may receive one or more second PC5-RRC configuration parameters from the second wireless device and establish a PC5 RRC connection. 【0237】 In one embodiment, a first wireless device may establish one or more sidelink wireless bearers (e.g., one or more sidelink logical channels, one or more QoS flows, one or more sidelink PDU sessions, etc.) between the first wireless device and a second wireless device. One or more sidelink wireless bearers may be based on a PC5-RRC connection between the first wireless device and the second wireless device. Establishing one or more sidelink wireless bearers may include the first wireless device sending an RRC bearer configuration request (e.g., a PC5-RRC bearer configuration request) and receiving an RRC bearer configuration response (e.g., a PC5-RRC bearer configuration response) in response to the RRC bearer configuration request. In one embodiment, the first wireless device may send an RRC bearer configuration request to the second wireless device requesting one or more sidelink wireless bearers. The RRC bearer configuration request may include QoS parameters for one or more sidelink wireless bearers. In one embodiment, one or more first PC5-RRC configuration parameters may include parameters of the RRC bearer configuration request for one or more sidelink wireless bearers. A first wireless device may receive an RRC bearer configuration response from a second wireless device that indicates the configuration of one or more sidelink wireless bearers. In one embodiment, one or more second PC5-RRC configuration parameters may include parameters of the RRC bearer configuration response for one or more sidelink wireless bearers. 【0238】 In one embodiment, the QoS parameters of one or more sidelink radio bearers (e.g., one or more sidelink logical channels, one or more QoS flows, etc.) may indicate the priority level of the sidelink bearers. In one embodiment, the QoS parameters of one or more sidelink radio bearers may include at least one of the following: PC5 QoS flow identifier (PFI), PC5 5QI (e.g., PQI or range, etc.), V2X service type (e.g., PSID or ITS-AID), QoS class identifier (QCI), 5G QoS indicators (5QI: dynamic and / or non-dynamic), priority level, allocation and retention priority (ARP: priority level, preemption function, preemption vulnerability, etc.), latency requirements (e.g., acceptable packet transmission latency / delay), reliability requirements (e.g., maximum error rate), session aggregated maximum bitrate (AMBR), bearer type (e.g., PDU session type, QoS flow type, bearer type indicating at least one of IP, non-IP, Ethernet®, IPv4, IPv6, IPv4v6, unstructured, etc.), QoS flow identifier, bearer identifier, QoS flow level QoS parameters, bearer level QoS parameters, averaging window, maximum data burst volume, packet delay budget, packet error rate, delay critical indication (e.g., critical or non-critical), maximum flow bitrate, guaranteed flow bitrate, notification control (e.g., indicating notifications requested to the first base station based on events), maximum packet loss rate, etc. As shown in Figure 25, one or more QoS flows and / or one or more sidelink radio bearers may be configured based on QoS parameters (e.g., PC5 QoS rules). 【0239】 In one embodiment, establishing one or more sidelink radio bearers includes sending a sidelink bearer configuration request to the first base station and receiving a sidelink bearer configuration response from the first base station by the first radio device, where (for example, if the first radio device determines sidelink radio resources based on mode 2 operation; if the first base station allocates sidelink radio resources for sidelink communication (e.g., dynamic grant or configured grant)). The first radio device may send a sidelink bearer configuration request to the first base station indicating one or more sidelink radio bearers for establishment. The sidelink bearer configuration request (e.g., via an uplink RRC message) may include QoS parameters for one or more sidelink radio bearers. In response to the sidelink bearer configuration request, the first radio device may receive a sidelink bearer configuration response from the first base station (e.g., via a downlink RRC message) which includes configuration parameters for one or more sidelink radio bearers. The configuration parameters may include QoS parameters for one or more sidelink radio bearers. A first radio device may configure one or more sidelink radio bearers having a second radio device based on the configuration parameters in the sidelink bearer configuration response from a first base station. The first radio device may send an RRC bearer configuration request (e.g., a PC5-RRC bearer configuration request) to the second radio device based on the configuration parameters in the sidelink bearer configuration response from the first base station. 【0240】 In one embodiment, a second radio device may determine the traffic pattern of packets it transmits or receives (e.g., to / from another network node, such as a network node). The network node may be a fourth radio device, a second base station, a serving base station of the second radio device, another node, one or more network nodes, base stations, radio devices, and / or at least one of the same. In one embodiment, the second radio device may determine gap request information based on the traffic pattern of packets it transmits or receives (e.g., to / from a network node). The gap request information may be a request from the first radio device to avoid a gap (e.g., a radio resource indicated in the gap request information for the second radio device to transmit or receive a packet) when the first radio device transmits a sidelink transport block (e.g., a sidelink packet) to the second radio device. 【0241】 In one embodiment, a second wireless device may receive resource scheduling information from a network node. Determining the traffic pattern of packets transmitted or received by the second wireless device may be based on the resource scheduling information. The resource scheduling information may indicate wireless resources including at least one of the following: authorized resources configured for transmission by the second wireless device (e.g., Type 1 configured authorizations, Type 2 configured authorizations, SPS configurations, etc.), semi-persistent scheduling (SPS) resources for reception by the second wireless device, resource pool configuration parameters for the resource pool used by the second wireless device, and / or similar. In one embodiment, the resource scheduling information may indicate the traffic pattern of packets transmitted by the network node to the second wireless device (e.g., periodicity, time offset, data size, etc.). Based on the resource scheduling information, the second wireless device may determine gap request information. 【0242】 In one embodiment, a second wireless device may determine a traffic pattern based on the data generation pattern of the second wireless device. The second wireless device may determine data generation information based on application layer traffic pattern estimation of one or more services. Based on the data generation information, the second wireless device may determine a data generation pattern. The second wireless device may determine gap request information based on resource scheduling information received from a network node and / or at least one of the data generation information of the second wireless device. 【0243】 In one embodiment, gap request information may indicate at least one of the following: gap periodicity of the gap, gap time offset of the gap, gap size of the gap, gap priority level of the gap, and / or similar. A gap includes a periodically occurring radio resource having gap periodicity and a gap time offset from a reference timing, and each occurrence of the radio resource has a gap size. In one embodiment, the gap periodicity of the gap may indicate the time interval at which the gap occurs (e.g., the time interval between consecutive gaps). The gap periodicity of the gap may include at least one of the following: the number of slots (e.g., 200 slots, 300 slots, etc., and / or a numerology / TTI related to the number of slots) indicating the gap periodicity (e.g., indicating that the gap occurs at time intervals of that number of slots), the period (e.g., 100ms, 200ms, 1000ms, etc.) indicating the gap periodicity (e.g., indicating that the gap occurs at time intervals of that period), the number of subframes (e.g., 10 subframes, 50 subframes, etc.) indicating the gap periodicity (e.g., indicating that the gap occurs at time intervals of that number of subframes), and / or similar. 【0244】 In one embodiment, the gap time offset of a gap may indicate when the gap begins. The gap time offset of a gap may include at least one of the following: the number of slots from a reference timing (e.g., 10 slots, 120 slots, etc., and / or numerology / TTI related to the number of slots), the time distance from the reference timing (e.g., 20ms, 150ms, etc.), the number of subframes from the reference timing (e.g., 10 subframes, 50 subframes, etc.), and / or similar. 【0245】 In one embodiment, the gap size of a gap may represent the size of each occurrence of the gap (e.g., duration). The gap size of a gap may include at least one of the following: the number of slots (e.g., 3 slots, 10 slots, etc., and / or numerology / TTI related to the number of slots), the duration (e.g., 0.5 ms, 1 ms, 2 ms, etc.), the number of subframes (e.g., 0.5 subframes, 1 subframe, 2 subframes, etc.), and / or similar. 【0246】 In one embodiment, the priority level of a gap may indicate the priority level that the gap possesses. The priority level of a gap may indicate that packets transmitted and received by a second radio device to and from another network node (e.g., a network node, a second base station, a fourth radio device, etc.) through the gap have a priority level. The priority level of a gap may indicate that a first base station may authorize / permit / agree to transmit a transport block to the second radio device through the radio resources indicated by the gap if the priority level of the transport block (e.g., the priority level of the sidelink bearer between the first and second radio devices) is equal to or greater than the priority level of the gap. The priority level of a gap may include an indicator indicating the priority level. The priority level of a gap may include at least one of an integer value from 0 to 15, an integer value from 0 to 7, ProSe Per-Packet Priority (PPPP), and / or similar. 【0247】 In one embodiment, the gap request information includes the Numerology / TTI used by the second radio device to indicate the gap, the frequency of the gap (e.g., the frequency affected by the gap), the bandwidth of the gap (e.g., the bandwidth affected by the gap), the RRC state of the second radio device (e.g., at the second base station: RRC connected state, RRC inactive state, RRC idle state, etc.), the cell identifier of the serving cell of the second radio device (e.g., at the second base station) (e.g., physical cell identifier, PCI, global cell identifier, GCI, CGI, etc.), and the base station identifier of the serving base station of the second radio device (e.g., the second base station) (e.g., gNB ID, eNB ID, gNB-DU ID, gNB-CUResource pools used by the second wireless device (e.g., resource pool index / identifier, resource pool for mode 1 operation, resource pool for mode 2 operation, etc., for sidelinks, V2X, inter-device communication, etc.), affected resource pools (e.g., resource pool to which the second wireless device requests the first wireless device to apply a gap), preferred resource pools (e.g., resource pool to which the first wireless device is recommended to be used when the second wireless device sends a transport block to the second wireless device), the zone of the second wireless device (e.g., if the zone of the second wireless device is different from that of the first wireless device, the transmission of the first wireless device will be affected in communication between the second wireless device and the network node). The first radio device may indicate at least one of the following: (which may not have any effect), a synchronization reference source that the second radio device uses to synchronize for sidelink communication (e.g., a base station (e.g., the second base station), a global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.), priority information of the synchronization reference source of the second radio device (e.g., between the second base station, GNSS, etc.), target sidelink bearer information (e.g., a sidelink bearer identifier of the target sidelink bearer between the first and second radio devices, which the second radio device may request the first radio device to apply a gap to the target sidelink bearer), and / or similar information. In one embodiment, the gap request information may indicate whether the gap is for transmission or reception by a second wireless device (for example, if the gap is for reception by a second wireless device, the first wireless device may be authorized / permitted to transmit a transport block to the second wireless device during the time overlapping with the gap; if the gap is for transmission by a second wireless device, the first wireless device may not be authorized / permitted to transmit a transport block to the second wireless device during the time overlapping with the gap, for example, due to half-duplex issues). 【0248】 In one embodiment, as shown in Figure 23 and / or Figure 24, the second wireless device may transmit at least one sidelink message containing gap request information to the first wireless device. In one embodiment, the first wireless device may receive at least one sidelink message from the second wireless device containing gap request information for the second wireless device. At least one sidelink message may be associated with a PC5-RRC connection. At least one sidelink message may be at least one of a PC5-RRC message (e.g., a PC5-RRC configuration message, a PC5-RRC UE information message, a PC5-RRC UE function message, etc.), a direct communication request message, a function information message, and / or similar. In one embodiment, at least one sidelink message includes at least one of the following: a radio device identifier for a second radio device (e.g., IMSI, TMSI, C-RNTI, V2X node index, etc.), a radio device identifier for a first radio device (e.g., IMSI, TMSI, C-RNTI, V2X node index, etc.), a destination identifier indicating the first radio device (e.g., a destination Layer 2 identifier, IP address, UE identifier, etc.), and / or similar. 【0249】 In one embodiment, a first wireless device may receive second gap request information from a third wireless device. The second gap request information may indicate a second gap requested by the third wireless device for communication with another network node. The second gap request information may indicate at least one of the second gap periodicity of the second gap, the second gap time offset of the second gap, the second gap size of the second gap, the second priority level of the second gap, and / or similar. The first wireless device, the second wireless device, and / or the third wireless device may belong to a sidelink multicast group. The first wireless device may multicast / broadcast transport blocks to the second and third wireless devices. The first wireless device may multicast / broadcast transport blocks to the second and third wireless devices via wireless resources determined based on the gap request information of the second wireless device and / or the second gap request information of the third wireless device (e.g., wireless resources to bypass the gap indicated in the gap request information and / or the second gap request information). 【0250】 In one embodiment, the gap request information of the second wireless device may be based on an information request from the first wireless device (e.g., in response to an information request from the first wireless device). In one embodiment, the transmission of the gap request information by the second wireless device to the first wireless device may be based on an information request from the first base station (e.g., in response to an information request from the first wireless device). In one embodiment, the first wireless device may transmit a sidelink information request message to the second wireless device for the gap request information. The sidelink information request message may indicate a request for the gap request information. At least one sidelink message (from the second wireless device) containing the gap request information may be based on a sidelink information request message (e.g., in response to a sidelink information request message). In one embodiment, the sidelink information request message may be associated with a PC5-RRC connection. The sidelink information request message may be at least one of a PC5-RRC message (e.g., a PC5-RRC configuration message, a PC5-RRC UE information message, a PC5-RRC UE functionality message, etc.), a direct communication request message, a functionality information message, and / or similar. In one embodiment, a first wireless device may send a sidelink information request message to a second wireless device based on a request from a first base station. 【0251】 In one embodiment, a sidelink information request message may include at least one of the following: a radio device identifier for a second radio device (e.g., IMSI, TMSI, C-RNTI, V2X node index, etc.), a radio device identifier for a first radio device (e.g., IMSI, TMSI, C-RNTI, V2X node index, etc.), a destination identifier indicating the second radio device (e.g., destination Layer 2 identifier, IP address, UE identifier, etc.), a bearer identifier for a sidelink bearer associated with the second radio device, a logical channel identifier for a sidelink logical channel associated with the second radio device, a QoS flow identifier for a sidelink QoS flow associated with the second radio device (e.g., sidelink session, sidelink PDU session, etc.), a priority level for the gap required to notify the first radio device, and / or similar. In one embodiment, a sidelink information request message may include at least one of the following: the priority level of a packet flow (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with a second radio device), the traffic pattern of the packet flow (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with a second radio device), the availability of gap allocations for resources that may be used for packet flows associated with the second radio device, and / or similar. The priority level of the gap required to notify the first radio device may indicate the minimum priority of traffic for which a gap request to the first radio device will be permitted / approved. In one embodiment, the second radio device may send to the first radio device a gap request (e.g., gap request information) for communication of traffic (e.g., with another network node by the second radio device) having a priority level equal to and / or higher than the gap priority level indicated in the sidelink information request message. 【0252】 In one embodiment, the transmission of a sidelink information request message from a first radio device to a second radio device may be based on an information request from a first base station (e.g., in response to an information request from the first base station). In one embodiment, the first radio device may receive an RRC information request message from the first base station for gap request information of the second radio device. Based on the RRC information request message received from the first base station, the first radio device may transmit gap request information of the second radio device to the first base station (e.g., via at least one uplink RRC message). In one embodiment, the RRC information request message may be at least one of a UE information request message, a UE support information request message, an RRC reconfiguration message, an RRC rebuild message, an RRC setup message, an RRC re-establishment message, and / or similar. 【0253】 In one embodiment, the RRC information request message may include at least one of the following: a radio device identifier (e.g., IMSI, TMSI, C-RNTI, V2X node index, etc.) of a second radio device (e.g., a target radio device for which the first radio device needs to provide gap information); a destination identifier (e.g., destination Layer 2 identifier, IP address, UE identifier, etc.) indicating the second radio device (e.g., a target radio device for which the first radio device needs to provide gap information); a bearer identifier of a sidelink bearer associated with the second radio device; a logical channel identifier of a sidelink logical channel associated with the second radio device; a QoS flow identifier (e.g., session identifier, PDU session identifier, etc.) of a sidelink QoS flow associated with the second radio device (e.g., sidelink session, sidelink PDU session, etc.); the priority level of the gap required to be notified to the first base station; and / or similar. In one embodiment, the first radio device may use a packet flow identifier (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with the second radio device) to identify target radio devices (e.g., a second radio device and / or a third radio device) that need to provide gap information to the first base station. The packet flow identifier (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with the second radio device) may be unique among multiple receiver radio devices (e.g., a second radio device, a third radio device, etc.) of the first radio device (e.g., a transmitter radio device). 【0254】 In one embodiment, the RRC information request message may include at least one of the following: the priority level of a packet flow (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with a second radio device), the traffic pattern of the packet flow (e.g., a sidelink bearer, a sidelink logical channel, and / or a sidelink QoS flow associated with a second radio device), the availability of gap allocations for resources that may be used for packet flows associated with the second radio device, and / or similar. The priority level of the gap required to notify the first base station may indicate the lowest traffic priority that would authorize / approve a gap request to the first radio device and / or the first base station. In one embodiment, the first radio device and / or the second radio device may send a gap request (e.g., gap request information from the second radio device) to the first base station for communication of traffic (e.g., with another network node by the second radio device) having a priority level equal to and / or higher than the gap priority level indicated in the RRC information request message. In one embodiment, a second wireless device may send a gap request (e.g., gap request information) to the first wireless device for communication of traffic (e.g., with another network node by the second wireless device) having a priority level equal to and / or higher than the priority level of the gap indicated in the sidelink information request message. 【0255】 In one embodiment, the first base station may send an RRC information request message to the first radio device for gap request information of the second radio device, based on the network information of the second radio device. In one embodiment, the first base station may send an RRC information request message to the first radio device based on the network information of the second radio device if the second radio device is not addressed by the first base station, if the second radio device is an out-of-coverage radio device, or if the RRC is idle / inactive, and / or similar. In one embodiment, depending on whether the second radio device is addressed by the first base station, the first base station may request gap request information of the second radio device from the first radio device (e.g., if the second radio device is not addressed by the first base station). In one embodiment, the first radio device may receive network information of the second radio device from the second radio device. A second wireless device may transmit network information to a first wireless device via at least one of PC5-RRC messages (e.g., PC5-RRC configuration messages, PC5-RRC UE information messages, PC5-RRC UE function messages, etc.), direct communication messages, function information messages, and / or similar. In one embodiment, a first wireless device may transmit network information of a second wireless device to a first base station via at least one of uplink RRC messages, UE support information messages, UE information, RRC re-establishment complete messages, RRC reconfiguration complete messages, RRC restart complete messages, RRC setup complete messages, and / or similar. 【0256】 In one embodiment, the first radio device may send a sidelink information request message to the second radio device for gap request information based on the network information of the second radio device. In one embodiment, the first radio device may send a sidelink information request message to the second radio device based on the network information of the second radio device if the second radio device is not addressed by the first base station, if the second radio device is an out-of-coverage radio device, or is in an idle / inactive state of the RRC, and / or similar. In one embodiment, depending on whether the second radio device is addressed by the first base station, the first radio device may request gap request information for the second radio device from the first radio device (for example, if the second radio device is not addressed by the first base station). 【0257】 In one embodiment, the network information includes the cell identifier of the serving cell of the second wireless device (e.g., camp-on cell) (e.g., physical cell identifier, PCI, global cell identifier, GCI, CGI, carrier index, etc.), the base station identifier of the serving base station of the second wireless device (e.g., second base station) (e.g., gNB identifier, eNB identifier, gNB-DU identifier, gNB-CU identifier, etc.), the resource pool index of the resource pool used by the second wireless device (e.g., if the second wireless device uses the same resource pool as the first wireless device, the first base station and / or the first wireless device may require the gap request information of the second wireless device to select / configure / coordinate sidelink resources for transmitting the first wireless device to the second wireless device) (e.g., sidelink, V2X, inter-device communication, etc.), and the zone of the second wireless device where it is located (e.g., the zone of the second wireless device). If the zone is different from that of the first radio device, the transmission of the first radio device may not affect communication between the second radio device and the network node, and / or the first base station and / or the first radio device may not require gap information from the second radio device.) Zone identifier of the zone (such as physical location), used by the second radio device (for example, if the second radio device uses the same band as the first radio device, the first base station and / or the first radio device may require gap request information from the second radio device in order to select / configure / adjust sidelink resources for transmitting the first radio device to the second radio device.) Band index of the serving band, second radio device (for example, if the second radio device is in an RRC connection state, the first base station may request resource adjustment information and / or gap request information from the serving base station of the second radio device.)The RRC status of the first radio device (e.g., RRC idle state, RRC inactive state, RRC connected state, etc.), the synchronization reference source used by the second radio device for sidelink communication (e.g., the synchronization reference source may include at least one of a base station or a global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.)), priority information of the synchronization reference source in the serving cell (camp-on cell, etc.) of the second radio device (e.g., between the second base station, GNSS, etc.), and / or at least one of the same. In one embodiment, based on the synchronization reference source and / or priority information of the synchronization reference source, the first base station and / or the first radio device may determine whether the gap request information of the second radio device is necessary / useful for sidelink resource selection. In one embodiment, if a second wireless device uses a different synchronization reference source than the first wireless device and / or the first base station, gap request information formatted / presented based on the different synchronization reference source may be unsuitable (e.g., inaccurate and / or not very useful) for determining the sidelink resources by the first wireless device and / or the first base station. 【0258】 In one embodiment, a first radio device may determine / select sidelink radio resources to transmit to a second radio device based on gap request information. In one embodiment, a first radio device (e.g., Mode 1 operation: configured authorized resources, SPS resources, and / or resource allocation based on dynamic authorization) may transmit gap request information to a first base station and receive a sidelink resource configuration (e.g., configured authorized resource allocation, SPS resources, dynamic authorization, etc.) from the first base station based on the gap request information. In one embodiment, a first radio device (e.g., Mode 2 operation, or Mode 1 operation with configured authorized resources) may determine sidelink radio resources from a resource pool configured by the network or a pre-configured resource pool (e.g., Mode 2 operation) based on gap request information. 【0259】 In one embodiment, as shown in Figure 20, a first radio device (e.g., in Mode 2 operation, or Mode 1 operation with configured authorized resources) may determine, based on gap request information from a second radio device, sidelink radio resources, resource pools, and / or authorized resources configured for sidelink communication (e.g., for transmission to the second radio device) from a plurality of resource pools. Determining sidelink radio resources may involve determining at least one of one or more resource segments in the time / frequency domain (e.g., including at least one combination of resource blocks, slots, minislots, symbols, subframes, time periods, time opportunities, and / or subcarriers, carriers, bandwidth portions, and bandwidth segments in frequency), and one or more resource pools (e.g., configured for V2X / inter-device / sidelink communication Mode 1 / Mode 1 operation, etc.). The sidelink radio resources determined by the first radio device may include at least one of the following in the time / frequency domain: one or more resource segments (e.g., including at least one combination of resource blocks, slots, minislots, symbols, subframes, time periods, time opportunities, and / or subcarriers, carriers, bandwidth portions, and bandwidth segments in frequency); and one or more resource pools (e.g., configured for V2X / device-to-device / sidelink communication mode 1 / mode 1 operation, etc.). The first radio device may transmit transport blocks and / or signals (e.g., PSSCH, PSCCH, etc.) via the sidelink radio resources determined / selected based on gap request information. 【0260】 In one embodiment, the first wireless device may select / determine the timing and / or size of a sidelink wireless resource that does not overlap with the gap indicated in the gap request information (e.g., based on gap periodicity, gap time offset, gap size, numerology / TTI used by the second wireless device, synchronization reference source, priority information of the synchronization reference source, etc.). In one embodiment, if the gap requested by the second wireless device is for the second wireless device to transmit, the first wireless device does not have to determine / select a sidelink wireless resource (e.g., for transmission to the second wireless device) that overlaps with the gap in the time domain (e.g., due to half-duplex issues, etc.). In one embodiment, if the gap requested by the second wireless device is for the second wireless device to receive, the first wireless device may determine / select a sidelink wireless resource (e.g., for transmission to the second wireless device) that overlaps with the gap in the time domain. 【0261】 In one embodiment, the first wireless device may, based on gap request information (e.g., based on resource pools and / or affected resource pools indicated by gap request information), avoid using a resource pool used by the second wireless device (e.g., for transmission to the second wireless device). In one embodiment, the first wireless device may, based on gap request information (e.g., based on preferred resource pools indicated by gap request information), use a resource pool recommended by the second wireless device (e.g., for transmission to the second wireless device). 【0262】 In one embodiment, the first wireless device (based on, for example, the gap frequency, gap bandwidth, the cell identifier of the serving cell of the second wireless device, the resource pool used by the second wireless device, the synchronization reference source, and the priority information of the synchronization reference source) does not have to select / determine a sidelink wireless resource (e.g., a resource block) that overlaps with the gap indicated in the gap request information of the second wireless device in the time domain and / or frequency domain for transmission to the second wireless device. In one embodiment, based on the zone of the second wireless device indicated in the gap request information, if the zone of the second wireless device is the same as that of the first wireless device, the first wireless device may determine / select a sidelink wireless resource that does not overlap with the gap. If the zone of the second wireless device is different from that of the first wireless device, the first wireless device may determine / select a sidelink wireless resource regardless of the gap. In one embodiment, the first wireless device may take the gap into consideration when selecting / determining a sidelink wireless resource for transmission to the second wireless device of a transport block associated with a bearer indicated by the target sidelink bearer information. 【0263】 In one embodiment, the first wireless device may determine whether the priority level of the gap indicated in the gap request information is higher than that of the transport block and / or the logical channel of the transport block (e.g., a sidelink logical channel between the first and second wireless devices, a sidelink QoS flow, a sidelink session, and / or a sidelink bearer) for transmission to the second wireless device. Based on the determination by the first wireless device, in response that the priority level of the gap is equal to or higher than that of the transport block and / or the logical channel, the first wireless device may determine / select a sidelink wireless resource that does not overlap with the gap and / or transmit the transport block over the sidelink wireless resource that does not overlap with the gap. Based on the determination by the first wireless device, in response that the priority level of the gap is less than or equal to that of the transport block and / or the logical channel, the first wireless device may determine / select a sidelink wireless resource regardless of the gap and / or transmit the transport block over the sidelink wireless resource that is determined regardless of the gap. 【0264】 In one embodiment, as shown in Figures 18, 19, and / or 23, a first radio device may transmit to a first base station at least one uplink RRC message containing gap request information for a second radio device. The at least one uplink RRC message may contain second gap request information for a third radio device. In one embodiment, the transmission of at least one uplink RRC message by the first radio device to the first radio device may be based on the reception of an RRC information request message from the first base station by the first radio device for gap request information for a second radio device. In one embodiment, based on the RRC information request message (e.g., in response to the RRC information request message), the first radio device may transmit to the first base station at least one uplink RRC message containing gap request information for a second radio device. In one embodiment, the at least one uplink RRC message may be at least one of an uplink RRC message, a UE support information message, UE information, an RRC re-establishment complete message, an RRC reconfiguration complete message, an RRC restart complete message, an RRC setup complete message, and / or similar. 【0265】 In one embodiment, based on network information, a first base station may determine whether a second radio device is served by the first base station (for example, based on at least one of the cell identifier of the serving cell of the second radio device, the base station identifier of the serving base station of the second radio device, the band index of the serving band of the second radio device, the resource pool index of the resource pool of the second radio device, the RRC state of the second radio device, the zone of the second radio device, and / or similar information indicated by network information). If the first base station determines that the second radio device is not served by the first base station, the first base station may, based on network information, identify the serving base station of the second radio device (e.g., the second base station). The serving base station (e.g., the second base station) may serve the second radio device. The second radio device (e.g., in an idle / inactive RRC state) may camp on the cell of the serving base station (e.g., the second base station). In one embodiment, as shown in Figures 21, 22, and / or 24, a first base station may transmit a request for resource coordination information (e.g., gap request information) for a second radio device to the second base station (e.g., via a direct interface and / or an indirect interface). The first base station may receive resource coordination information, including gap request information, from the second base station (e.g., via a direct interface and / or an indirect interface). The gap request information received from the second base station may include elements of gap request information that the first radio device receives from the second radio device and transmits to the first base station. The gap request information received from the second base station may include elements that are described as elements / parameters of gap request information that the first radio device receives from the second radio device and transmits to the first base station. The gap request information received from the second base station may include elements that are described as elements / parameters included in gap request information from the second radio device. 【0266】 In one embodiment, a first base station may determine sidelink radio resources for the first radio device based on gap request information of a second radio device (e.g., based on second gap request information of a third radio device). The first base station may determine sidelink radio resources for the first radio device's transmission to the second radio device based on gap request information received from the first radio device (e.g., from the second radio device via the first radio device) and / or from the second base station. The sidelink radio resources determined by the first base station may be used by the first radio device to transmit transport blocks and / or signals to the second radio device (e.g., and / or third radio device). The sidelink radio resources may be for transmission from the first radio device to the second radio device. In one embodiment, the first base station (e.g., for the first radio device's transmission to the second radio device) may determine sidelink radio resources, resource pools, and / or radio resources for sidelink and / or uplink / downlink communication from a plurality of resource pools based on gap request information of the second radio device. Determining sidelink radio resources may involve determining at least one of the following in the time / frequency domain: one or more resource segments (e.g., including at least one combination of resource blocks, slots, minislots, symbols, subframes, time periods, time opportunities, and / or subcarriers, carriers, bandwidth portions, and bandwidth segments in frequency); and one or more resource pools (e.g., configured for V2X / device-to-device / sidelink communication mode 1 / mode 1 operation, etc.).The sidelink radio resources determined by the first base station may include at least one of the following in the time / frequency domain: one or more resource segments (e.g., including at least one combination of resource blocks, slots, minislots, symbols, subframes, time periods, time opportunities, and / or subcarriers, carriers, bandwidth portions, and bandwidth segments in frequency), and one or more resource pools (e.g., configured for V2X / device-to-device / sidelink communication mode 1 / mode 1 operation, etc.). Based on gap request information, the first radio device may transmit / multicast / broadcast transport blocks and / or signals (e.g., PSSCH, PSCCH, etc.) to the second radio device and / or third radio device via the sidelink radio resources identified / selected and / or displayed / assigned by the first base station. 【0267】 In one embodiment, the first base station can allocate / determine the timing and / or size of sidelink radio resources that do not overlap with the gap indicated in the gap request information (e.g., based on gap periodicity, gap time offset, gap size, numerology / TTI used by the second radio device, synchronization reference source, priority information of the synchronization reference source, etc.) (e.g., for transmitting the first radio device to the second radio device). In one embodiment, if the gap requested by the second radio device is for the second radio device to transmit, the first base station does not have to determine / allocate sidelink radio resources (e.g., for transmitting the first radio device to the second radio device) that overlap with the gap in the time domain (e.g., due to half-duplex issues, etc.). In one embodiment, if the gap requested by the second radio device is for the second radio device to receive, the first base station may determine / allocate sidelink radio resources (e.g., for transmitting the first radio device to the second radio device) that overlap with the gap in the time domain. 【0268】 In one embodiment, the first base station may avoid allocating to the first radio device a resource pool used by the second radio device (e.g., for transmission to the second radio device) based on gap request information (e.g., based on the resource pools and / or affected resource pools indicated by the gap request information). In one embodiment, the first base station may allocate to the first radio device a resource pool recommended by the second radio device (e.g., for transmission to the second radio device) based on gap request information (e.g., based on the preferred resource pools indicated by the gap request information). 【0269】 In one embodiment, the first base station may not have to allocate / determine sidelink radio resources (e.g., resource blocks, resource pools) to transmit the first radio device to the second radio device that overlaps with the gap indicated in the gap request information of the second radio device, in the time domain and / or frequency domain (based on, for example, the frequency of the gap, the bandwidth of the gap, the cell identifier of the serving cell of the second radio device, the resource pool used by the second radio device, the synchronization reference source, the priority information of the synchronization reference source, etc.). In one embodiment, based on the zone of the second radio device indicated in the gap request information, if the zone of the second radio device is the same as that of the first radio device, the first base station may determine / allocate sidelink radio resources that do not overlap with the gap. If the zone of the second radio device is different from that of the first radio device, the first base station may determine / allocate sidelink radio resources regardless of the gap. In one embodiment, the first base station may take the gap into consideration when allocating / determining sidelink radio resources for the transmission of a transport block associated with a bearer indicated by the target sidelink bearer information of the gap request information (e.g., the first radio device to the second radio device). 【0270】 In one embodiment, the first base station may determine whether the priority level of the gap indicated in the gap request information is higher than that of a logical channel (e.g., a sidelink logical channel, a sidelink QoS flow, a sidelink session, and / or a sidelink bearer between the first and second radio devices) associated with resource authorization and / or transport blocks for transmission from the first radio device to the second radio device. Based on the determination by the first base station, in response that the priority level of the gap is higher than that of the logical channel, the first base station may determine / allocate sidelink radio resources so as not to overlap with the gap. Based on the determination by the first base station, in response that the priority level of the gap is less than or equal to that of the logical channel, the first base station may determine / allocate sidelink radio resources regardless of the gap. 【0271】 In one embodiment, a first base station may transmit a resource authorization to a first radio device indicating a sidelink radio resource determined / allocated based on gap request information. In one embodiment, the first radio device may receive a resource authorization from the first base station indicating a sidelink radio resource based on gap request information. The sidelink radio resource indicated by the resource authorization may include at least one of the following: resource segments in a time / frequency domain (e.g., including resource blocks, slots, minislots, symbols, subframes, durations, time opportunities, and / or at least one combination of subcarriers, carriers, bandwidth portions, and bandwidth segments of a frequency band), or one or more resource pools (e.g., configured for V2X / device-to-device / sidelink communication mode 1 / mode 1 operation, etc.). In one embodiment, the resource authorization may include at least one RRC configuration message (e.g., an RRC reconfiguration message) indicating the authorized resources to be configured based on gap request information (e.g., a type 1 authorized, a type 2 authorized, an SPS resource, etc.). The authorized resources to be configured may include sidelink radio resources. In one embodiment, resource authorization may include at least one RRC configuration message (e.g., an RRC reconfiguration message) indicating a sidelink resource pool selected based on gap request information. The sidelink resource pool may include sidelink radio resources. 【0272】 In one embodiment, the first radio device may send a buffer status report or scheduling request to the first base station for logical channels (e.g., packet flows, sidelink logical channels, sidelink QoS flows, sidelink sessions, and / or sidelink bearers between the first and second radio devices) associated with transport blocks that the first radio device transmits to the second radio device. The first radio device may receive resource authorization (e.g., via DCI, PDCCH, MAC CE, etc.) from the first base station in response to the buffer status report and / or scheduling request. Based on the buffer status report, scheduling request, and / or gap request information of the second radio device, the first base station may determine and transmit resource authorization (indicating sidelink radio resources) to the first radio device. In one embodiment, the buffer status report may include identifiers for logical channels (e.g., packet flows, sidelink logical channels, sidelink QoS flows, sidelink sessions, and / or sidelink bearers between the first and second radio devices). 【0273】 In one embodiment, a first radio device may transmit a transport block (e.g., associated with a logical channel) and / or a signal (e.g., PSSCH, PSCCH, etc.) to a second radio device via a sidelink radio resource determined by and / or the first radio device. The sidelink radio resource for transmitting the transport block may be determined / selected by the first radio device based on the gap request information of the second radio device (e.g., based on the second gap request information of the third radio device). The sidelink radio resource for transmitting the transport block may also be determined / allocated by the first base station based on the gap request information of the second radio device (e.g., transmitted by the first radio device to the first base station) (e.g., based on the second gap request information of the third radio device). The first radio device may multicast / broadcast the transport block via the sidelink radio resources to the second and third radio devices. 【0274】 In one embodiment, the second wireless device may transmit transport blocks and / or signals to a network node (e.g., another network node including at least one of one or more wireless devices, a first wireless device, a second base station, a fourth wireless device, etc.) through a gap indicated by the gap request information of the second wireless device. The second wireless device may receive transport blocks and / or signals from a network node (e.g., another network node including at least one of one or more wireless devices, a first wireless device, a second base station, a fourth wireless device, etc.) through a gap indicated by the gap request information of the second wireless device. 【0275】 In one embodiment, as shown in Figure 20, a first wireless device may receive at least one sidelink message from a second wireless device, which includes gap request information from the second wireless device. The gap request information may indicate at least one of the following: gap periodicity, gap time offset, gap priority level, and / or similar. The first wireless device may determine whether the gap priority level is equal to or higher than the logical channel associated with the transport block. Based on this determination, in response that the gap priority level is higher than the logical channel, the first wireless device may transmit the transport block over a wireless resource that does not overlap with the gap, and in response that the gap priority level is equal to or lower than the logical channel, the first wireless device may transmit the transport block over a wireless resource that is determined independently of the gap. 【0276】 In one embodiment, as shown in Figure 24, a first base station may receive device information for a second radio device from a first radio device. The device information may indicate a serving cell, a serving base station, a resource pool, a zone, and / or at least one of the same. Based on the device information, the first base station may identify the second base station corresponding to the second radio device. The first base station may send a request for resource coordination information for the second radio device to the second base station. The first base station may receive resource coordination information, including gap request information, from the second base station. Based on the gap request information, the first base station may determine the sidelink radio resources to transmit from the first radio device to the second radio device. The first base station may send a resource authorization to the first radio device indicating the sidelink radio resources. 【0277】 In one embodiment, the gap request information may include at least one of the following: gap periodicity, gap time offset, gap size, affected frequency, affected bandwidth, RRC status of the second radio device, cell identifier of the serving cell of the second radio device, base station identifier of the serving base station of the second radio device, resource pool used by the second radio device, affected resource pool, preferred resource pool, zone of the second radio device (e.g., if the zone of the second radio device is different from that of the first radio device, the transmission of the first radio device may not affect the communication of the second radio device), synchronization reference source used by the second radio device for sidelink communication (e.g., base station (e.g., second base station), global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.)), priority information of the synchronization reference source in the serving cell of the second radio device, target sidelink bearer information, and / or similar. 【0278】 In one embodiment, as shown in Figure 26, the first radio device may receive at least one sidelink message from the second radio device, which includes gap request information for the second radio device. The gap request information may indicate at least one of the following: gap periodicity, gap time offset, and / or similar. The first radio device may transmit at least one uplink radio resource control (RRC) message to the first base station, which includes the gap request information for the second radio device. The first radio device may receive a resource permission from the first base station indicating a sidelink radio resource based on the gap request information. The sidelink radio resource may be for transmission from the first radio device to the second radio device. In one embodiment, the first radio device may transmit a transport block to the second radio device via the sidelink radio resource. 【0279】 In one embodiment, a first radio device may receive an RRC information request message from a first base station for gap request information of a second radio device. Sending at least one uplink RRC message may be based on the RRC information request message. In one embodiment, the RRC information request message may include a radio device identifier for the second radio device, a destination identifier indicating the second radio device, a bearer identifier for a sidelink bearer associated with the second radio device, a logical channel identifier for a sidelink logical channel associated with the second radio device, a QoS flow identifier for a sidelink QoS flow associated with the second radio device (e.g., a sidelink session, a sidelink PDU session, etc.) (for selective gap information and / or destination identification), a priority level for the gap to be notified to the first base station, and / or at least one of the same. 【0280】 In one embodiment, the first radio device may receive network information for the second radio device from the second radio device. The network information may include the cell identifier of the serving cell of the second radio device, the base station identifier of the serving base station of the second radio device, the resource pool index of the resource pool used by the second radio device, the zone identifier of the zone in which the second radio device is located, the synchronization reference source used by the second radio device for sidelink communication (for example, the synchronization reference source may include at least one of a base station or a global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.)), priority information of the synchronization reference source in the serving cell of the second radio device, and / or at least one of the same. The first radio device may transmit the network information for the second radio device to the first base station. An RRC information request message from the first base station may be based on the network information for the second radio device. In one embodiment, depending on whether the second wireless device is supported by the first base station, the first base station may request gap request information for the second wireless device from the first wireless device (for example, if the second wireless device is not supported by the first base station). 【0281】 In one embodiment, a first radio device may send a sidelink information request message to a second radio device for gap request information. At least one sidelink message containing gap request information may be based on the sidelink information request message. The first radio device may send a sidelink information request message to the second radio device based on an RRC information request message from the first base station. The sidelink information request message may include at least one of the following: the radio device identifier of the second radio device, a destination identifier indicating the second radio device, a bearer identifier of a sidelink bearer associated with the second radio device, a logical channel identifier of a sidelink logical channel associated with the second radio device, a QoS flow identifier of a sidelink QoS flow associated with the second radio device (e.g., for selective gap information), the priority level of the gap required to notify the first radio device, and / or similar. 【0282】 In one embodiment, a first wireless device may establish a PC5 RRC connection with a second wireless device. At least one sidelink message may be associated with the PC5 RRC connection. The at least one sidelink message may be at least one of a PCPC5 RRC message (e.g., a PCPC5-RRC configuration message, a PCPC5-RRC UE information message, etc.), a direct communication request message, a function information message, and / or similar. 【0283】 In one embodiment, a second wireless device may determine the traffic pattern of packets to send or receive (e.g., to / from another network node). Gap request information may be based on the packet traffic pattern. The second wireless device may receive resource scheduling information from a network node. The determination of the traffic pattern may be based on the resource scheduling information. The resource scheduling information may indicate at least one of the authorized resources configured for transmission by the second wireless device (e.g., Type 1 configured authorizations and / or Type 2 configured authorizations), semi-persistent scheduling (SPS) resources for reception by the second wireless device, and / or similar. 【0284】 In one embodiment, a second wireless device may transmit a transport block to at least one of one or more wireless devices, a first wireless device, a second base station, and / or similar devices, via a gap associated with gap request information. The second wireless device may receive a transport block from at least one of one or more wireless devices, a second base station, and / or similar devices, via a gap associated with gap request information. 【0285】 In one embodiment, the gap request information may include at least one of the following: gap size, affected frequency, affected bandwidth, RRC status of the second radio device, cell identifier of the serving cell of the second radio device, base station identifier of the serving base station of the second radio device, resource pool used by the second radio device, affected resource pool, preferred resource pool, zone of the second radio device (e.g., if the zone of the second radio device is different from that of the first radio device, the transmission of the first radio device may not affect the communication of the second radio device), synchronization reference source used by the second radio device for sidelink communication (e.g., base station (e.g., second base station), global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.), etc.), priority information of the synchronization reference source in the serving cell of the second radio device, target sidelink bearer information, and / or similar. 【0286】 In one embodiment, gap request information may include a priority level for the gap associated with the gap request information. In one embodiment, a first base station may determine whether the priority level for the gap associated with the gap request information is higher than that for the logical channel associated with the resource grant. Based on the determination by the first base station, in response that the gap's priority level is higher than that for the logical channel, the first base station may determine a sidelink radio resource that does not overlap with the gap. Based on the determination by the first base station, in response that the gap's priority level is less than or equal to that of the logical channel, the first base station may determine a sidelink radio resource that is not affected by the gap. In one embodiment, a first radio device may determine whether the priority level for the gap associated with the gap request information is higher than that for the logical channel associated with the transport block. Based on the determination by the first radio device, in response that the gap's priority level is higher than that for the logical channel associated with the transport block, the first radio device may transmit the transport block of the logical channel over a radio resource that does not overlap with the gap. Based on a decision made by the first wireless device, in response that the priority level of the gap is less than or equal to the logical channel associated with the transport block, the first wireless device may transmit the transport block over the wireless resource regardless of the gap. 【0287】 In one embodiment, a first wireless device may receive second gap request information from a third wireless device. At least one uplink RRC message may include the second gap request information. A sidelink wireless resource indicated by resource authorization may be based on the second gap request information. The first wireless device may multicast a transport block to the second and third wireless devices via the sidelink wireless resource. 【0288】 In one embodiment, resource authorization may include at least one RRC configuration message indicating authorized resources configured based on gap request information. The configured authorized resources may include sidelink radio resources. In one embodiment, resource authorization may include at least one RRC configuration message indicating a sidelink resource pool based on gap request information (e.g., resource pool information). The sidelink resource pool may include sidelink radio resources. In one embodiment, a first radio device may send a buffer status report or scheduling request to a first base station for one or more logical channels (e.g., one or more sidelink radio bearers). The first radio device may receive resource authorization from the first base station in response to the buffer status report. 【0289】 In one embodiment, a first wireless device may establish one or more sidelink wireless bearers between the first wireless device and a second wireless device. Establishing one or more sidelink wireless bearers may include transmitting an RRC bearer configuration request and receiving an RRC bearer configuration response to the RRC bearer configuration request. The first wireless device may transmit an RRC bearer configuration request to the second wireless device requesting one or more sidelink wireless bearers. The RRC bearer configuration request may include QoS parameters for one or more sidelink wireless bearers. The first wireless device may receive an RRC bearer configuration response from the second wireless device indicating the configuration of one or more sidelink wireless bearers. In one embodiment, establishing one or more sidelink wireless bearers may include transmitting a sidelink bearer configuration request and receiving a sidelink bearer configuration response. The first wireless device may transmit a sidelink bearer configuration request to the first base station indicating one or more sidelink wireless bearers. The sidelink bearer configuration request may include QoS parameters for one or more sidelink wireless bearers. A first radio device may receive a sidelink bearer configuration response from a first base station, which includes configuration parameters for one or more sidelink radio bearers. Based on the configuration parameters of the sidelink bearer configuration response from the first base station, the first radio device may configure one or more sidelink radio bearers having a second radio device. 【0290】 In one embodiment, as shown in Figure 28, a first base station may receive at least one uplink RRC message from a first radio device containing gap request information for a second radio device. The gap request information may indicate at least one of the following: gap periodicity, gap time offset, and / or similar. Based on the gap request information, the first base station may determine a sidelink radio resource for the first radio device. The sidelink radio resource may be for transmission from the first radio device to the second radio device. The first base station may transmit a resource permission to the first radio device indicating the sidelink radio resource. 【0291】 In one embodiment, as shown in Figure 27, a second wireless device may receive resource scheduling information from a network node indicating wireless resources. The wireless resources in the resource scheduling information may include at least one of an authorized resource configured for transmission by the second wireless device, a semi-persistent scheduling (SPS) resource for reception by the second wireless device, and / or similar. The second wireless device may determine gap request information based on the resource scheduling information. The gap request information may indicate at least one of a gap periodicity, a gap time offset, and / or similar. The second wireless device may transmit at least one sidelink message containing the gap request information to the first wireless device. The second wireless device may transmit a transport block from the first wireless device via the sidelink wireless resources based on the gap request information. 【0292】 In one embodiment, a first wireless device may receive at least one sidelink message from a second wireless device, which includes gap request information from the second wireless device. The gap request information may indicate at least one of the following: gap periodicity, gap time offset, gap priority level, and / or similar. The first wireless device may determine whether the gap priority level is equal to or higher than the logical channel associated with the transport block. Based on this determination, in response that the gap priority level is higher than the logical channel, the first wireless device may transmit the transport block over a wireless resource that does not overlap with the gap, and in response that the gap priority level is equal to or lower than the logical channel, the first wireless device may transmit the transport block over a wireless resource that is determined independently of the gap. 【0293】 In one embodiment, as shown in Figure 28, a first base station may receive device information for a second radio device from a first radio device. The device information may indicate a serving cell, a serving base station, a resource pool, a zone, and / or at least one of the same. Based on the device information, the first base station may identify the second base station corresponding to the second radio device. The first base station may send a request for resource coordination information for the second radio device to the second base station. The first base station may receive resource coordination information, including gap request information, from the second base station. Based on the gap request information, the first base station may determine the sidelink radio resources to transmit from the first radio device to the second radio device. The first base station may send a resource authorization to the first radio device indicating the sidelink radio resources. 【0294】 In one embodiment, the gap request information may include at least one of the following: gap periodicity, gap time offset, gap size, affected frequency, affected bandwidth, RRC status of the second radio device, cell identifier of the serving cell of the second radio device, base station identifier of the serving base station of the second radio device, resource pool used by the second radio device, affected resource pool, preferred resource pool, zone of the second radio device (e.g., if the zone of the second radio device is different from that of the first radio device, the transmission of the first radio device may not affect the communication of the second radio device), synchronization reference source used by the second radio device for sidelink communication (e.g., base station (e.g., second base station), global navigation satellite system (GNSS) (e.g., GPS, GLONASS, Galileo, Beidou, etc.)), priority information of the synchronization reference source in the serving cell of the second radio device, target sidelink bearer information, and / or similar.

Claims

[Claim 1] It is a method, The first wireless device receives from the second wireless device at least one sidelink message which includes one or more parameters indicating time-domain information, The first wireless device provides a first time-domain sidelink resource for transmitting to the second wireless device, The first wireless device shall not transmit a second time-domain side-link resource to the second wireless device. This indicates that the time domain information includes periodicity and time offset, The first wireless device transmits an uplink support information message containing one or more parameters to the base station. A method that includes this. [Claim 2] The method according to claim 1, wherein the uplink support information message indicates that the second time-domain sidelink resource not to transmit is for not receiving a transport block between the first wireless device and the second wireless device. [Claim 3] The method according to any one of claims 1 to 2, further comprising the first wireless device receiving a resource permission from the base station indicating at least one wireless resource of the first time-domain sidelink resource, wherein the time-domain resource allocation of the at least one wireless resource is based on the uplink support information message. [Claim 4] The resource authorization includes at least one radio resource control configuration message, The at least one wireless resource control configuration message indicates one or more of the at least one configured authorized resource based on the uplink support information message, or one or more of the sidelink resource pools based on the uplink support information message. The at least one configured authorization resource includes the at least one radio resource of the first time-domain sidelink resource, The method according to claim 3, wherein the sidelink resource pool includes the at least one wireless resource of the first time-domain sidelink resource. [Claim 5] The aforementioned uplink support information message is: Gap size, Gap periodicity, Timing offset, Affected frequencies, Affected bandwidth, The wireless resource control state of the second wireless device, The device identifier of the second wireless device, The cell identifier of the serving cell of the second wireless device, The base station identifier of the serving base station of the second wireless device, The resource pool used by the second wireless device, Affected resource pools, Preferred resource pool, The zone of the second wireless device, The synchronization reference source used by the second wireless device for sidelink communication, wherein the synchronization reference source includes at least one of the second base station or a global navigation satellite system. Priority information of the synchronization reference source in the serving cell of the second wireless device, or Side link bearer bearer identifier The method according to any one of claims 1 to 4, wherein at least one of the following is represented. [Claim 6] It is a method, The second wireless device transmits to the first wireless device at least one sidelink message including one or more parameters indicating time-domain information, The first wireless device provides a first time-domain sidelink resource for transmitting to the second wireless device, The first wireless device shall not transmit a second time-domain side-link resource to the second wireless device. This indicates that the time domain information includes periodicity and time offset. A method that includes this. [Claim 7] The first wireless device transmits an uplink support information message to a base station, The method according to claim 6, wherein the uplink support information message indicates that the second time-domain sidelink resource not to transmit is for not receiving a transport block between the first wireless device and the second wireless device. [Claim 8] A wireless device, The wireless device comprises one or more processors and a memory that stores instructions. A wireless device wherein, when the instruction is executed by one or more processors, it causes the wireless device to perform the method according to any one of claims 1 to 7. [Claim 9] A non-temporary computer-readable medium containing instructions, wherein, when executed by one or more processors of a wireless device, the instructions cause the wireless device to perform the method according to any one of claims 1 to 7. [Claim 10] It is a method, The base station receives an uplink support information message from a first radio device, which includes one or more parameters indicating time-domain information, and the time-domain information is The first wireless device provides a first time-domain sidelink resource for transmission to a second wireless device, The first wireless device shall not transmit a second time-domain side-link resource to the second wireless device. This indicates that the time domain information includes periodicity and time offset. A method that includes this. [Claim 11] The method according to claim 10, wherein the uplink support information message indicates that the second time-domain sidelink resource not to transmit is for not receiving a transport block between the first wireless device and the second wireless device. [Claim 12] The method according to any one of claims 10 to 11, further comprising the base station transmitting a resource permission to the first radio device indicating at least one radio resource of the first time-domain sidelink resource, wherein the time-domain resource allocation of the at least one radio resource is based on the uplink support information message. [Claim 13] It is a base station, The base station comprises one or more processors and memory that stores instructions. The instruction, when executed by one or more processors, causes the base station to perform the method according to any one of claims 10 to 12. [Claim 14] A non-temporary computer-readable medium containing instructions, wherein, when executed by one or more processors of a base station, the instructions cause the base station to perform the method according to any one of claims 10 to 12. [Claim 15] It is a system, The system comprises a first wireless device, a second wireless device, and a base station. The first wireless device comprises one or more processors and a memory that stores instructions. When the instruction is executed by one or more processors, Receiving at least one sidelink message from the second wireless device, which includes one or more parameters indicating time-domain information, wherein the time-domain information is The first wireless device provides a first time-domain sidelink resource for transmitting to the second wireless device, The first wireless device shall not transmit a second time-domain side-link resource to the second wireless device. This indicates that the time domain information includes periodicity and time offset, To transmit an uplink support information message containing one or more of the aforementioned parameters to the base station. The first wireless device is made to perform this action. The second wireless device comprises one or more processors and a memory that stores instructions. When the instruction is executed by one or more processors, Transmitting the at least one sidelink message to the first wireless device. The second wireless device performs this action. The base station comprises one or more processors and memory that stores instructions. When the instruction is executed by one or more processors, To receive the uplink support information message from the first wireless device. A system that causes the aforementioned base station to perform this action.

Images