JP6881722B2 - Truncated buffer status reporting - Google Patents

Description

Cross-reference to related applications This application claims the benefit of US Provisional Application No. 62 / 472,029 filed on March 16, 2017, the patent provisional application, which is hereby incorporated by reference in its entirety. Be incorporated.

Some examples of the various embodiments of the present disclosure are described herein with reference to the drawings.
The present invention provides, for example,:
(Item 1)
It's a method
Receiving the configuration parameters of multiple logical channels grouped into multiple logical channel groups, including the first logical channel group, by the wireless device.
Triggering a padding buffer status report (BSR) and
The truncated BSR,
Triggering the padding BSR and
The number of padding bits is
Larger than the size of the short BSR plus the short BSR subheader, and
Includes being smaller than the size of the long BSR plus the long BSR subheader and sending in response to
The truncated BSR
A first field containing a plurality of existing bits, wherein the existing bits in the plurality of existing bits indicate the existence of a buffer size field for the first logical channel group corresponding to the existing bits, and the buffer size. The first field and the field indicate the amount of data available across the logical channel of the first logical channel group.
A first number of buffer size fields for a logical channel group having logical channels with available data to transmit in ascending order of priority, wherein the first number is based on the number of padding bits. A method comprising a first number of buffer size fields, which has been determined.
(Item 2)
The method according to item 1, wherein the configuration parameter indicates a priority for a logical channel in the plurality of logical channels.
(Item 3)
The method of item 1 or 2, further comprising receiving downlink control information including an uplink grant indicating an uplink resource allocation.
(Item 4)
The method according to any one of items 1 to 3, wherein the number of padding bits is at least based on the size of the uplink grant.
(Item 5)
The truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, and the length field indicates the length of the truncated BSR, according to any of items 1-4. The method described.
(Item 6)
The method of any of items 1-5, wherein the first number of buffer size fields are determined based on the size of the truncated BSR that fits the padding bits.
(Item 7)
The method of any of items 1-6, wherein the size of the truncated BSR depends on the buffer size field of the first number.
(Item 8)
The method according to any one of items 1 to 7, wherein the first position of the first presence bit in the first field identifies a logical channel group identifier.
(Item 9)
A first value, which is 1 for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit exists.
Items 1-8, where the second value, which is zero for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit does not exist. The method described in any of.
(Item 10)
Sending the truncated BSR can
Triggering the padding BSR and
The method of any of items 1-9, further comprising responding further to the number of padding bits equal to the size of the short BSR plus the short BSR subheader.
(Item 11)
It ’s a wireless device,
With one or more processors
A memory for storing instructions that, when executed by the one or more processors, to the wireless device.
Receiving configuration parameters for multiple logical channels grouped into multiple logical channel groups, including the first logical channel group,
Sending a truncated buffer status report (BSR)
The number of padding bits is
Larger than the size of the short BSR plus the short BSR subheader, and
It has a memory, which allows it to send and do in response to being smaller than the size of the long BSR plus the long BSR subheader.
The truncated BSR
A first field containing a plurality of existing bits, wherein the existing bits in the plurality of existing bits indicate the existence of a buffer size field for the first logical channel group corresponding to the existing bits, and the buffer size. The first field and the field indicate the amount of data available across the logical channel of the first logical channel group.
A first number of buffer size fields for a logical channel group having logical channels with available data to transmit in ascending order of priority, wherein the first number is based on the number of padding bits. A wireless device, including a first number of buffer size fields, determined by.
(Item 12)
The wireless device according to item 11, wherein the configuration parameter indicates a priority for a logical channel in the plurality of logical channels.
(Item 13)
The instruction further causes the wireless device to receive downlink control information, including an uplink grant indicating an uplink resource allocation, when executed by the one or more processors, item 11 or 12. The wireless device described in.
(Item 14)
The wireless device according to any one of items 11 to 13, wherein the number of padding bits is at least based on the size of the uplink grant.
(Item 15)
The truncated BSR is associated with a medium access control subheader containing a logical channel identifier and a length field, wherein the length field indicates the length of the truncated BSR, according to any of items 11-14. Wireless device.
(Item 16)
The wireless device according to any one of items 11 to 15, wherein the first number of buffer size fields are determined based on the size of the truncated BSR that fits the padding bits.
(Item 17)
The wireless device according to any one of items 11 to 16, wherein the size of the truncated BSR depends on the buffer size field of the first number.
(Item 18)
The wireless device according to any one of items 11 to 17, wherein the first position of the first presence bit in the first field identifies a logical channel group identifier.
(Item 19)
A first value, which is 1 for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit exists.
Any of items 11-18, a second value that is zero for the first existing bit indicates that the buffer size field for the logical channel group corresponding to the first existing bit does not exist. The wireless device described in.
(Item 20)
Sending the truncated BSR can
Triggering the padding BSR and
The wireless device according to any one of items 11 to 19, wherein the number of padding bits is equal to the size of the short BSR plus the short BSR subheader, and further responds to.
(Item 21)
It ’s a wireless device,
With one or more processors
A memory for storing instructions that, when executed by the one or more processors, to the wireless device.
Receiving configuration parameters for multiple logical channels grouped into multiple logical channel groups, and
Sending a truncated buffer status report (BSR), where the number of padding bits is
Larger than the size of the short BSR plus the short BSR subheader, and
It has a memory, which allows it to send and do in response to being smaller than the size of the long BSR plus the long BSR subheader.
The truncated BSR
A first field containing a series of existing bits, including a first existing bit for a first logical channel group within the plurality of logical channel groups.
The first position of the first presence bit in the first field identifies the identifier of the first logical channel group and
The first field and the value of the first existence bit indicate the existence of the buffer size field for the first logical channel group.
The first number of buffer size fields for the first number of logical channel groups having logical channels having data available for transmission in ascending order of priority, said first number. A wireless device comprising a first number of buffer size fields, which is determined based on the number of padding bits.
(Item 22)
21. The item 21 comprises further causing the wireless device to receive downlink control information, including uplink grants, indicating uplink resource allocation, when the instruction is executed by the one or more processors. Wireless device.
(Item 23)
The wireless device according to item 21 or 22, wherein the number of padding bits is at least based on the size of the uplink grant.
(Item 24)
One of items 21-23, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. Described wireless device.
(Item 25)
The wireless device according to any one of items 21 to 24, wherein the number of the first buffer size fields is determined based on the size of the truncated BSR that fits the padding bits.
(Item 26)
A first value, which is 1 for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit exists.
Any of items 21-25, wherein the second value, which is zero for the first existing bit, indicates that the buffer size field for the logical channel group corresponding to the first existing bit does not exist. The wireless device described in.
(Item 27)
It ’s a base station,
With one or more processors
A memory for storing instructions that, when executed by the one or more processors, tells the base station.
Sending configuration parameters for multiple logical channels grouped into multiple logical channel groups, including the first logical channel group,
Receiving the truncated BSR, the number of padding bits,
Larger than the size of the short BSR plus the short BSR subheader, and
It has a memory, which allows it to receive and receive in response to being smaller than the size of the long BSR plus the long BSR subheader.
The truncated BSR
A first field containing a plurality of existing bits, wherein the existing bits in the plurality of existing bits indicate the existence of a buffer size field for the first logical channel group corresponding to the existing bits, and the buffer size. The first field and the field indicate the amount of data available across the logical channel of the first logical channel group.
The first number of buffer size fields for the first number of logical channel groups having logical channels having data available for transmission in descending order of priority, said first number. A base station that includes a first number of buffer size fields, which is determined based on the number of padding bits.
(Item 28)
27. Item 27, wherein when the instruction is executed by the one or more processors, the base station is further made to transmit downlink control information including an uplink grant indicating an uplink resource allocation. Base station.
(Item 29)
27. The base station of item 27 or 28, wherein the number of padding bits is at least based on the size of the uplink grant.
(Item 30)
One of items 27-29, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. The listed base station.
(Item 31)
27. The base station of any of items 27-30, wherein the first number of buffer size fields are determined based on the size of the truncated BSR that fits the padding bits.
(Item 32)
A first value, which is 1 for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit exists.
Any of items 27-31, wherein the second value, which is zero for the first existing bit, indicates that the buffer size field for the logical channel group corresponding to the first existing bit does not exist. The base station described in.
(Item 33)
It's a method
Receiving the configuration parameters of multiple logical channels grouped by the wireless device into multiple logical channel groups, including the first logical channel group,
Sending a truncated buffer status report (BSR), where the number of padding bits is
Larger than the size of the short BSR plus the short BSR subheader, and
Includes being smaller than the size of the long BSR plus the long BSR subheader and sending in response to
The truncated BSR
A first field containing a plurality of existing bits, wherein the existing bits in the plurality of existing bits indicate the existence of a buffer size field for the first logical channel group corresponding to the existing bits. Field and
A first number of buffer size fields for a logical channel group having logical channels with available data to transmit in ascending order of priority, wherein the first number is based on the number of padding bits. A method comprising a first number of buffer size fields, which has been determined.
(Item 34)
33. The method of item 33, further comprising receiving downlink control information including an uplink grant indicating an uplink resource allocation.
(Item 35)
33 or 34. The method of item 33 or 34, wherein the number of padding bits is at least based on the size of the uplink grant.
(Item 36)
One of items 33-35, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. The method described.
(Item 37)
33. The method of any of items 33-36, wherein the first number of buffer size fields are determined based on the size of the truncated BSR that fits the padding bits.
(Item 38)
A first value, which is 1 for the first existing bit, indicates that the buffer size field for the first logical channel group corresponding to the first existing bit exists.
Any of items 33-37, a second value that is zero for the first existing bit indicates that the buffer size field for the logical channel group corresponding to the first existing bit does not exist. The method described in.
(Item 39)
It's a method
The wireless device receives from the base station the configuration parameters of a plurality of logical channels including the first logical channel having the first logical channel priority, wherein the first logical channel is one or more. To receive and to receive, which is mapped to the transmission duration of
Buffer status report,
The uplink data becomes available to the first logical channel in the first plurality of logical channels having the uplink data.
The first channel priority is higher than one or more of the one or more selected logical channels in the first plurality of logical channels, and the one or more selected. The logical channel is selected in response to being mapped to one or more transmission durations, high, and triggered in response.
A method comprising transmitting the buffer status report to the base station.
(Item 40)
39. The method of item 39, wherein the one or more selected logical channels are fewer than the first plurality of logical channels.
(Item 41)
The availability of the uplink data to the first logical channel responds to the availability of the uplink data in the uplink buffer of the first logical channel. 39 or 40, wherein the uplink buffer is a wireless link control buffer or a packet data convergence protocol buffer.
(Item 42)
The plurality of logical channels are grouped into a first plurality of logical channel groups, and the plurality of logical channels are grouped into a first plurality of logical channel groups.
39. The method of any of items 39-41, wherein the buffer status report shows the buffer status of one or more logical channel groups within the first plurality of logical channel groups.
(Item 43)
The method of any of items 39-42, wherein the buffer status report is one of a short format, a long format, or a truncated format.
(Item 44)
39-43, wherein the configuration parameter indicates whether the second logical channel in the one or more selected logical channels is mapped to the one or more transmission durations. Method.
(Item 45)
39. The method of any of items 39-44, wherein the first logical channel has one logical channel priority during the one or more transmission durations.
(Item 46)
39. The method of any of items 39-45, wherein the plurality of logical channels are grouped based on a logical channel mapping to transmission duration.
(Item 47)
39. The method of any of items 39-46, wherein the configuration parameter comprises a first logical channel identifier for the first logical channel.
(Item 48)
39. The method of any of items 39-47, further comprising receiving an uplink grant in response to sending the buffer status report.
(Item 49)
It ’s a wireless device,
With one or more processors
A memory that stores instructions that, when executed by the one or more processors, to the wireless device.
Receiving configuration parameters for a plurality of logical channels, including a first logical channel having a first logical channel priority, wherein the first logical channel is mapped to one or more transmission durations. Being, receiving and
Buffer status report,
The uplink data becomes available to the first logical channel in the first plurality of logical channels having the uplink data.
The first channel priority is higher than one or more of the one or more selected logical channels in the first plurality of logical channels, and the one or more selected. The logical channel is selected in response to being mapped to one or more transmission durations, high, and triggered in response.
A wireless device comprising a memory for transmitting and performing the buffer status report to the base station.
(Item 50)
49. The wireless device of item 49, wherein the one or more selected logical channels are fewer than the first plurality of logical channels.
(Item 51)
The availability of the uplink data to the first logical channel is in response to the availability of the uplink data in the uplink buffer of the first logical channel. The wireless device according to item 49 or 48, wherein the uplink buffer is a wireless link control buffer or a packet data convergence protocol buffer.
(Item 52)
The plurality of logical channels are grouped into a first plurality of logical channel groups, and the plurality of logical channels are grouped into a first plurality of logical channel groups.
The wireless device according to any one of items 49 to 51, wherein the buffer status report shows the buffer status of one or more logical channel groups in the first plurality of logical channel groups.
(Item 53)
The wireless device according to any one of items 49-52, wherein the buffer status report is one of a short format, a long format, or a truncated format.
(Item 54)
The component according to any one of items 49 to 53, wherein the configuration parameter indicates whether or not the second logical channel in the one or more selected logical channels is mapped to the one or more transmission durations. Wireless device.
(Item 55)
The wireless device according to any one of items 49 to 54, wherein the first logical channel has one logical channel priority during the one or more transmission durations.
(Item 56)
The wireless device of any of items 49-55, wherein the plurality of logical channels are grouped based on a logical channel mapping to transmission duration.
(Item 57)
The method of any of items 49-56, wherein the configuration parameter comprises a first logical channel identifier for the first logical channel.
(Item 58)
Items 49-57 further cause the wireless device to receive an uplink grant in response to transmitting the buffer status report when the instruction is executed by the one or more processors. The wireless device described in any of.
(Item 59)
It's a method
Receiving a configuration parameter by a wireless device, said configuration parameter,
A first parameter of one or more logical channels, each logical channel of the one or more logical channels being mapped to a corresponding first or more transmission duration of a plurality of transmission durations. The first parameter, which indicates that it is
Receiving and receiving, including a second parameter indicating a first value for the buffer status report timer.
To start the buffer status report timer having the first value.
Receiving at least one uplink grant associated with a second transmission duration within the plurality of transmission durations.
Starting in response to at least one logical channel having data among the one or more logical channels mapped to the second transmission duration.
A method comprising sending a buffer status report in response to the expiration of the buffer status report timer.
(Item 60)
To keep executing the buffer status report timer,
Receiving at least one uplink grant associated with the second transmission duration,
Further, in response to the fact that none of the at least one logical channel having data in the one or more logical channels is mapped to the second transmission duration, it continues to execute. Included, the method of item 59.
(Item 61)
59. The method of item 59 or 60, wherein the configuration parameter indicates a time window and the at least one uplink grant is received within the time window.
(Item 62)
The method of any of items 59-61, wherein the buffer status report indicates at least the buffer status of the one or more logical channels.
(Item 63)
The method of any of items 59-62, wherein the wireless device transmits the buffer status report based on at least one of the at least one uplink grant.
(Item 64)
In response to instructing a multiplexing and assembly procedure to generate a buffer status report medium access control (MAC) control element, the first buffer status report timer may be started at the first value. The method of any of items 59-63, further comprising.
(Item 65)
The method of any of items 59-64, wherein the buffer status report has one of a short format, a truncated format, or a long format.
(Item 66)
The method of any of items 59-65, wherein the buffer status report indicates the buffer status of one or more second logical channels of the one or more logical channels.
(Item 67)
The method of any of items 59-66, wherein the first parameter comprises a corresponding logical channel identifier for each of the one or more logical channels.
(Item 68)
The method of any of items 59-67, further comprising receiving an uplink grant in response to sending the buffer status report.
(Item 69)
It ’s a wireless device,
With one or more processors
A memory that stores instructions that, when executed by the one or more processors, to the wireless device.
Receiving a configuration parameter, said configuration parameter
A first parameter of one or more logical channels, each logical channel of the one or more logical channels being mapped to a corresponding first or more transmission duration of a plurality of transmission durations. The first parameter, which indicates that it is
Receiving and receiving, including a second parameter indicating a first value for the buffer status report timer.
To start the buffer status report timer having the first value.
Receiving at least one uplink grant associated with a second transmission duration within the plurality of transmission durations.
In response to the fact that at least one logical channel having data among the one or more logical channels is mapped to the second transmission duration, the operation is started.
A wireless device comprising a memory for sending and performing a buffer status report in response to the expiration of the buffer status report timer.
(Item 70)
The instruction is to cause the wireless device to continue executing the buffer status report timer when executed by the one or more processors.
Receiving at least one uplink grant associated with said transmission duration,
Further including having none of the at least one logical channel having data in the one or more logical channels map to the second transmission duration and having it done in response to. , Item 69.
(Item 71)
The wireless device of item 69 or 70, wherein the configuration parameter indicates a time window and the at least one uplink grant is received within the time window.
(Item 72)
The wireless device according to any one of items 69 to 71, wherein the buffer status report indicates at least the buffer status of the one or more logical channels.
(Item 73)
The wireless device according to any one of items 69 to 72, wherein the wireless device transmits the buffer status report based on at least one of the at least one uplink grant.
(Item 74)
The radio in response to instructing a multiplexing and assembly procedure to generate a buffer status report medium access control (MAC) control element when the instruction is executed by the one or more processors. The wireless device according to any one of items 69 to 73, wherein the device is further allowed to start the first buffer status report timer having the first value.
(Item 75)
The wireless device according to any one of items 69-74, wherein the buffer status report has one of a short format, a truncated format, or a long format.
(Item 76)
The wireless device according to any one of items 69 to 75, wherein the buffer status report indicates the buffer status of one or more second logical channels of the one or more logical channels.
(Item 77)
The wireless device according to any one of items 69 to 77, wherein the first parameter comprises a corresponding logical channel identifier for each of the one or more logical channels.
(Item 78)
When the instruction is executed by the one or more processors, the radio causes the radio device to receive an uplink grant in response to transmitting the buffer status report. The wireless device according to any one of items 69 to 78, which is further caused by the device.

FIG. 6 is a schematic representation of an exemplary RAN architecture based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary user plane protocol stack based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary control user plane protocol stack based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary wireless device and two base stations based on aspects of the embodiments of the present disclosure. It is an exemplary schematic in the case of uplink and downlink signal transmission based on the aspects of the embodiments of the present disclosure. It is an exemplary schematic in the case of uplink and downlink signal transmission based on the aspects of the embodiments of the present disclosure. It is an exemplary schematic in the case of uplink and downlink signal transmission based on the aspects of the embodiments of the present disclosure. It is an exemplary schematic in the case of uplink and downlink signal transmission based on the aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary uplink channel mapping and an exemplary uplink physical signal, based on aspects of the embodiments of the present disclosure. It is a schematic of an exemplary downlink channel mapping and an exemplary downlink physical signal based on aspects of the embodiments of the present disclosure. It is a schematic drawing which depicts the exemplary frame structure based on the aspect of the embodiment of this disclosure. FIG. 5 is a schematic diagram depicting an exemplary OFDM subcarrier set based on aspects of the embodiments of the present disclosure. FIG. 5 is a schematic diagram depicting an exemplary OFDM subcarrier set based on aspects of the embodiments of the present disclosure. FIG. 5 is a schematic diagram depicting an exemplary OFDM radio resource based on aspects of the embodiments of the present disclosure. It is an exemplary schematic of the configured BWP based on the aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary multi-connection based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary multi-connection based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary random access procedure based on aspects of the embodiments of the present disclosure. It is a figure which shows the structure of the exemplary MAC entity based on the aspect of embodiment of this disclosure. FIG. 6 is a schematic representation of an exemplary RAN architecture based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary RRC state based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary scheduling procedure based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary logical channel mapping based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary BSR trigger based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary BSR trigger based on aspects of the embodiments of the present disclosure. It is a schematic diagram of grouping and mapping of exemplary logical channels based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary buffer status report format based on aspects of the embodiments of the present disclosure. It is a schematic of an exemplary buffer status report format and process based on aspects of the embodiments of the present disclosure. It is a schematic of an exemplary buffer status report format and process based on aspects of the embodiments of the present disclosure. It is a schematic of an exemplary buffer status report format and process based on aspects of the embodiments of the present disclosure. FIG. 6 is a schematic representation of an exemplary buffer status report trigger based on aspects of the embodiments of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure. It is an exemplary flow chart based on the aspect of the embodiment of the present disclosure.

An exemplary embodiment of the present disclosure allows for buffer status reporting operations. A plurality of embodiments of the techniques disclosed herein can be used in the technical field of multi-carrier communication systems.

Throughout this disclosure, the following abbreviations are used.

Illustrative embodiments of the present disclosure can be implemented using a variety of physical layer modulation and transmission mechanisms. Exemplary transmission mechanisms include, but are not limited to, code division multiple access (CDMA), orthogonal frequency division multiple access (OFDA), time division multiple access (TDMA), wavelet technology, and / or the like. obtain. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA can also be used. Various modulation schemes can be applied to signal transmission within the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, sign, combinations thereof, and / or the like. An exemplary wireless transmission method is quadrature amplitude modulation (QAM) using two-phase phase modulation (BPSK), four-phase phase modulation (QPSK), 16-QAM, 64-QAM, 256-QAM, and / or similar. Can be carried out. Physical radio transmission can be improved by dynamically or quasi-dynamically varying the modulation and coding scheme, depending on transmission requirements and radio conditions.

FIG. 1 is an exemplary radio access network (RAN) architecture based on aspects of the embodiments of the present disclosure. As illustrated in this example, the RAN node can be the next generation node B (gNB) (eg 120A, 120B) and the new radio (NR) user plane towards the first radio device (eg 110A) and A control plane protocol termination can be provided. In one example, the RAN node may be the next generation evolutionary node B (ng-eNB) (eg 124A, 124B) and evolutionary UMTS terrestrial radio access towards a second radio device (eg 110B). (E-UTRA) User plane and control plane protocol terminations can be provided. The first wireless device can communicate with the gNB via the Uu interface. The second wireless device can communicate with the ng-eNB via the Uu interface. In this disclosure, the wireless devices 110A and 110B are structurally similar to the wireless device 110. The base station 120A and / or 120B can be structurally similar to the base station 120. Base station 120 can include at least one of gNB (eg 122A and / or 122B), ng-eNB (eg 124A and / or 124B), and / or the like.

gNB or ng-eNB can be used for radio resource management and scheduling, IP header compression, data encryption and integrity protection, access and mobility management function (AMF) selection in user equipment (UE) attachments, user plane and control plane data. Routing, connection setup and release, scheduling and sending of paging messages (generated from AMF), scheduling and sending of system broadcast information (generated from AMF or quality of service (O & M)), measurement and measurement report configuration, Transport-level packet marking in the uplink, session management, network slicing support, quality of service (QoS) flow management, and mapping to data radio bearers, UE support in the RRC_INACTIVE state, non-access layer (NAS) messages Features such as distributed capabilities for, RAN sharing, and dual connectivity, or close interworking between NR and E-UTRA can be provided as hosts.

In one example, one or more gNBs and / or one or more ng-eNBs can be interconnected with each other by an Xn interface. The gNB or ng-eNB can be connected to a 5G core network (5GC) via an NG interface. In one example, the 5GC may include one or more AMF / User Planning Function (UPF) functions (eg, 130A or 130B). The gNB or ng-eNB may be connected to the UPF by an NG-user plane (NG-U) interface. The NG-U interface can provide delivery (eg, non-guaranteed delivery) of the User Plane Protocol Data Unit (PDU) between the RAN node and the UPF. The gNB or ng-eNB may be connected to the AMF by an NG-control plane (NG-C) interface. The NG-C interface can provide functions such as NG interface management, UE context management, UE mobility management, NAS message transport, paging, PDU session management, configuration transfer, or warning message transmission.

In one example, UPF is an anchor point for intra / inter-radio access technology (RAT) mobility (where applicable), an external PDU session point for interconnecting with a data network, packet routing and forwarding, and policy rule enforcement. Packet inspection and user plane parts, traffic usage reports, uplink classifiers to support routing of traffic flows to the data network, branch points to support multihomed PDU sessions, QoS processing for the user plane, for example. Packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement, uplink traffic validation (eg, service data flow to QoS flow mapping (SDF)), downlink packet buffering, and / or down Functions such as link data notification triggering can be provided as a host.

In one example, AMF is NAS signaling termination, NAS signaling security, access layer (AS) security control, intercore network (CN) node signaling for mobility between third generation partnership project (3GPP) access networks, idle mode. UE reachability (eg, control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming right checking, mobility management control (subscription and policy) , Network slicing support, and / or features such as session management function (SMF) selection can be provided as a host.

FIG. 2A is an exemplary user plane protocol stack, where service data adaptation protocols (SDAP) (eg 211 and 221), packet data convergence protocols (PDCP) (eg 212 and 222), wireless link control (eg, 212 and 222). The RLC) (eg, 213 and 223) and medium access control (MAC) (eg, 214 and 224) sublayers, and the physical (PHY) (eg, 215 and 225) layers are network-side wireless devices (eg, 110). And may be terminated with gNB (eg 120). In one example, the PHY layer provides transport services to higher layers (eg, MAC, RRC, etc.). In one example, the services and functions of the MAC sublayer are the mapping between logical channels and transport channels, to one or a different logical channel from / to the transport block (TB) delivered to / from the PHY layer. Multiplexing / partitioning of the MAC service data unit (SDU) to which it belongs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ) (eg, one HARQ entity per carrier in the case of carrier aggregation (CA)), Priority processing between UEs by dynamic scheduling, priority processing between logical channels of one UE by logical channel prioritization, and / or padding may be included. The MAC entity can support one or more numerology and / or transmission timing. In one example, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing the logical channel can use. In one example, the RLC sublayer can support transparent mode (TM), non-affirmative mode (UM), and positive mode (AM) transmit mode. This RLC configuration can be per logical channel independent of numerology and / or transmission time interval (TTI) duration. In one example, an automatic repeat request (ARQ) can operate for any numerology and / or TTI duration for which a logical channel is configured. In one example, the PDCP layer services and functions for the user plane include sequence numbering, header compression and decompression, user data transfer, reordering and duplicate detection, PDCP PDU routing (eg for split bearers), PDCP SDU. Retransmission, encryption, decryption and integrity protection, PDCP SDU destruction, PDCP reestablishment and data recovery for RLC AM, and / or replication of PDCP PDUs may be included. In one example, SDAP services and functions may include mapping between QoS flows and data radio bearers. In one example, SDAP services and functions may include mapping quality of service indicators (QFIs) on DL and UL packets. In one example, SDAP protocol entities may be configured for individual PDU sessions.

FIG. 2B is an exemplary control plane protocol stack, where PDCP (eg, 233 and 242), RLC (eg, 234 and 243), and MAC (eg, 235 and 244) sublayers, and PHY (eg, eg, PHY). The 236 and 245) layers can be terminated with network-side wireless devices (eg 110) and gNBs (eg 120) to perform the services and functions described above. In one example, the RRC (eg, 232 and 241) may be terminated at the wireless device and the network-side gNB. In one example, RRC services and functions include broadcasting system information about AS and NAS, paging initiated by 5GC or RAN, establishing, maintaining, and releasing RRC connections between UEs and RANs, signaling radio bearers ( Security features including SRB) and data radio bearer (DRB) key management, establishment, configuration, maintenance and release, mobility features, QoS management features, UE measurement reports and control of those reports, detection of radio link failures and from there. Recovery and / or NAS message transfer from / to NAS to / from the UE may be included. In one example, NAS control protocols (eg, 231 and 251) may be terminated with wireless devices, and network-side AMFs (eg, 130), with UEs and AMFs for 3GPP and non-3GPP access. Functions such as mobility management between and session management between the UE and SMFs with 3GPP access and non-3GPP access may be performed.

In one example, a base station may configure multiple logical channels for wireless devices. Logical channels within multiple logical channels can correspond to wireless bearers, which can be associated with QoS requirements. In one example, the base station may constitute a logical channel that is mapped to one or more TTIs / numerologies during multiple TTIs / numerology. The wireless device can receive downlink control information (DCI) via a physical downlink control channel (PDCCH) indicating an uplink grant. In one example, the uplink grant may be for a first TTI / numerology and may indicate an uplink resource for the transmission of transport blocks. The base station can configure each logical channel into a plurality of logical channels having one or more parameters used by the logical channel prioritization procedure in the MAC layer of the wireless device. The one or more parameters can include priority, preferred bit rate, and the like. Each logical channel within a plurality of logical channels may correspond to one or more buffers containing data associated with that logical channel. The logical channel prioritization procedure can allocate uplink resources to multiple logical channels and / or one or more first logical channels within one or more MAC control elements (CEs). This one or more first logical channels can be mapped to a first TTI / numerology. The MAC layer in a wireless device can multiplex one or more MAC CEs and / or one or more MAC SDUs (eg, logical channels) within a MAC PDU (eg, transport block). In one example, the MAC PDU may include a MAC header that includes a plurality of MAC subheaders. MAC subheaders in multiple MAC subheaders may correspond to one or more MAC CEs and / or MAC CEs or MAC SUDs (logical channels) in one or more MAC SDUs. In one example, the MAC CE or logical channel can be configured using a logical channel identifier (LCID). In one example, the LCID for the logical channel or MAC CE may be fixed / preconfigured. In one example, the LCID for a logical channel or MAC CE may be configured for a wireless device by a base station. The MAC subheader corresponding to the MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

In one example, a base station can activate and / or stop and / or influence one or more processes in a wireless device by using one or more MAC commands (eg, one). The setting value of one or more parameters of the above processes starts and / or stops one or more timers of the one or more processes). The one or more MAC commands can include one or more MAC control elements. In one example, one or more processes may include activating and / or stopping PDCP packet replication for one or more radio bearers. The base station can transmit a field value indicating the activation and / or stop of PDCP replication for a MAC CE containing one or more fields and one or more radio bearers. In one example, one or more processes may include channel state information (CSI) transmission on one or more cells. The base station can transmit one or more MAC CEs indicating the activation and / or stop of CSI transmission on one or more cells. In one example, one or more processes may include activating or stopping one or more secondary cells. In one example, the base station may transmit a MACE indicating the activation or shutdown of one or more secondary cells. In one example, the base station may transmit one or more MAC CEs indicating the start and / or stop of one or more intermittent reception (DRX) timers on the wireless device. In one example, the base station may transmit one or more MAC CEs indicating one or more timing advance values for one or more timing advance groups (TAGs).

FIG. 3 is a block diagram of base stations (base stations 1, 120A, and base stations 2, 120B) and wireless device 110. The wireless device is sometimes referred to as the UE. Base stations are sometimes referred to as NB, eNB, gNB, and / or ng-eNB. In one example, the wireless device and / or base station can act as a relay node. Base stations 1, 120A are stored in at least one communication interface 320A (eg, wireless modem, antenna, wired modem, and / or similar), at least one processor 321A, and non-transient memory 322A. And can include at least one set of program code instructions 323A that can be executed by at least one processor 321A. Base stations 2, 120B are at least one of program code instructions 323B stored in at least one communication interface 320B, at least one processor 321B, and non-transient memory 322B and executable by at least one processor 321B. Can contain one set.

A base station can include a large number of sectors, such as 1, 2, 3, 4, or 6 sectors. The base station can include, for example, a large number of cells in the range of 1 to 50 or more. The cells may be categorized as, for example, primary cells or secondary cells. In radio resource control (RRC) connection establishment / reestablishment / handover, one serving cell can provide NAS (non-access layer) mobility information (eg, tracking area identifier (TAI)). In RRC connection reestablishment / handover, one serving cell can provide a security input. This cell is sometimes referred to as the primary cell (PCell). In the downlink, the carrier corresponding to the PCell can be the DL primary component carrier (PCC), whereas in the uplink, the carrier can be the UL PCC. Depending on the wireless device capability, the secondary cell (SCell) may be configured to form a set of serving cells with the PCell. In the downlink, the carrier corresponding to the SCell can be the downlink secondary component carrier (DL SCC), whereas in the uplink, the carrier can be the uplink secondary component carrier (UL SCC). The SCell may or may not have an uplink carrier.

The downlink carrier, and optionally the cell containing the uplink carrier, may be assigned a physical cell ID and cell index. Carriers (downlinks or uplinks) can belong to one cell. The cell ID or cell index can also identify the downlink carrier or uplink carrier of the cell (depending on the situation, it will be used). In the present disclosure, the cell ID can be similarly queried for the carrier ID and the cell index can be queried for the carrier index. In one embodiment, a physical cell ID or cell index can be assigned to a cell. The cell ID can be determined using a sync signal transmitted over the downlink carrier. The cell index can be determined using the RRC message. For example, when the present disclosure refers to a first physical cell ID for a first downlink carrier, the present disclosure states that the first physical cell ID is for a cell that includes a first downlink carrier. Can mean. The same concept may apply, for example, to carrier actuation. If the present disclosure indicates that the first carrier is activated, the specification can similarly mean that the cell containing the first carrier is activated.

The base station can transmit one or more messages (eg, RRC messages) containing a plurality of configuration parameters for one or more cells to the wireless device. One or more cells can include at least one primary cell and at least one secondary cell. In one example, the RRC message can be broadcast or unicast to a wireless device. In one example, the configuration parameters can include common parameters and dedicated parameters.

Services and / or functions of the RRC sublayer include broadcasting system information about AS and NAS, paging initiated by 5GC and / or NG-RAN, establishing and maintaining an RRC connection between the radio device and the NG-RAN, and / Or release, which may include at least one of carrier aggregation addition, modification, and release, or release of dual connections within the NR or between the E-UTRA and NR. Can include at least one of. The services and / or functions of the RRC sublayer are the establishment, configuration, maintenance, and / or release of at least one of the security functions, including key management, the signaling radio bearer (SRB) and / or the data radio bearer (DRB). Mobility features that may include at least one of handover (eg, intra-NR mobility or inter-RAT mobility) and context transfer, or may further include control of radio device cell selection and reselection, as well as cell selection and reselection. it can. The services and / or functions of the RRC sublayer are QoS management functions, wireless device measurement configurations / reports, detection and / or recovery from wireless link failures, or core network entities from / to wireless devices (eg, AMF, etc.). It may further include at least one of NAS message transfers to / from the Mobility Management Entity (MME).

The RRC sublayer can support the RRC_Idle state, the RRC_Inactive state, and / or the RRC_Connected state for the wireless device. In the RRC_Idle state, the wireless device is managed by public land mobile network (PLMN) selection, reception of broadcast system information, cell selection / reselection, monitoring / reception of paging on mobile termination data initiated by 5GC, and 5GC. At least one of paging to the mobile terminal data area or DRX to CN paging configured via NAS can be performed. In the RRC_Inactive state, the radio device receives broadcast system information, cell selection / reselection, monitoring / reception of RAN / CN paging initiated by NG-RAN / 5GC, RAN-based notifications managed by NG-RAN. At least one of the area (RNA) or DRX for RAN / CN paging composed of NG-RAN / NAS can be performed. In the RRC_Idle state of the radio device, the base station (eg, NG-RAN) can maintain a 5GC-NG-RAN connection (both C / U-plane) to the radio device and / or the UE to the radio device. The AS context can be saved. In the RRC_Connected state of the radio device, the base station (eg, NG-RAN) establishes a 5GC-NG-RAN connection (both C / U-plane) to the radio device, stores the UE AS context to the radio device, and the radio device. At least one of the transmission / reception of unicast data to / from or network-controlled mobility based on the measurement results received from the wireless device can be performed. In the RRC_Connected state of the wireless device, the NG-RAN can know the cell to which the wireless device belongs.

System information (SI) can be divided into a minimum SI and other SIs. The minimum SI can be broadcast periodically. The minimum SI can include basic information required for initial access, and information for periodically acquiring any other SI broadcast, or information prepared on demand, i.e. scheduling information. .. Other SIs can be broadcast or prepared in a dedicated way and can be triggered either by the network or based on a request from a wireless device. The minimum SI can be transmitted over two different downlink channels using different messages (eg, master information block and system information block type 1). Another SI may be transmitted via the system information block type 2. For radio devices in the RRC_Connected state, dedicated RRC signaling can be used for the request and delivery of other SIs. For wireless devices in the RRC_Idle state and / or the RRC_Inactive state, the request can trigger a random access procedure.

A wireless device can report its wireless access capability information, which can be static. Base stations can request how much a wireless device is capable of reporting on the basis of bandwidth information. If permitted by the network, temporary capacity limiting requests may be transmitted by the wireless device, transmitting limited use of some capacity (eg, due to hardware sharing, interference, or overheating) to the base station. be able to. The base station can confirm or reject the request. Temporary capacity limits can be transparent to 5GC (eg, static capacity can be preserved at 5GC).

When the CA is configured, the wireless device can have an RRC connection with the network. In the RRC connection reestablishment / reestablishment / handover procedure, one serving cell may provide NAS mobility information, and in the RRC connection reestablishment / handover procedure, one serving cell may provide security input. This cell is sometimes called a PCell. Depending on the capabilities of the wireless device, the SCell may be configured to form a set of serving cells with the PCell. A set of serving cells configured for a wireless device can include one PCell and one or more SCells.

Reconfiguration, addition, and removal of SCells can be performed by the RRC. In an intra-NR handover, the RRC can also add, remove, or reconfigure the SCell for use with the target PCell. When adding a new SCell, dedicated RRC signaling can be used to send all the required system information for the SCell, i.e., while in connection mode, the wireless device will send the broadcasted system information, It may not be necessary to obtain it directly from SCell.

The purpose of the RRC connection reconfiguration procedure is to modify the RRC connection (eg, establish, modify, and / or release the RB, perform a handover, set, modify, and / or release the measurement. , SCell and cell group addition, modification, and / or release). As part of the RRC connection reconfiguration procedure, NAS-only information can be transferred from the network to the wireless device. The RRCConceptionReconnection message can be a command to change the RRC connection. It can convey information for measurement configurations, mobility controls, radio resource configurations (eg, RB, MAC key configurations and physical channel configurations), including any associated dedicated NAS information and security configurations. If the received RRC Connection Reconnection message contains a sCellToReleaseList, the wireless device can perform a SCell release. If the received RRC Connection Reconnection message contains a sCellToAdModList, the wireless device can perform SCell additions or changes.

The RRC connection establishment (or reestablishment, resumption) procedure can be an RRC connection establishment (or reestablishment, resumption), and the RRC connection establishment procedure can include SRB1 establishment. The RRC connection establishment procedure can be used to transfer initial NAS-only information / messages from the wireless device to the E-UTRAN. SRB1 can be reestablished using the RRCConceptionReestival message.

The measurement reporting procedure can be the transfer of measurement results from the radio device to the NG-RAN. The wireless device can initiate the measurement reporting procedure after successful security operation. Measurement report messages can be used to send measurement results.

The wireless device 110 is housed in and at least one communication interface 310 (eg, a wireless modem, antenna, and / or similar), at least one processor 314, and non-transient memory 315. It can include at least one set of program code instructions 316 that can be executed by processor 314. The wireless device 110 includes at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, and at least one Global Positioning System (GPS) chipset 318. , And at least one of the other peripheral devices 319.

The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and / or the processor 321B of the base station 2 120B are general purpose processors, digital signal processors (DSPs), controllers, microcontrollers, application specific integrated circuits (ASICs). , Field Programmable Gate Arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic circuits, discrete hardware components, and the like. Processor 314 of the wireless device 110, processor 321A in base station 1 120A, and / or processor 321B in base station 2 120B are signal coding / processing, data processing, power control, input / output processing, and / or. At least one of the wireless device 110, base station 1 120A, and / or any other functionality capable of operating base station 2 120B in a wireless environment can be performed.

The processor 314 of the wireless device 110 may be connected to a speaker / microphone 311, a keypad 312, and / or a display / touchpad 313. The processor 314 can receive user input data from the user and / or provide user output data to the speaker / microphone 311, keypad 312, and / or display / touchpad 313. The processor 314 in the wireless device 110 can be configured to receive power from the power source 317 and / or distribute that power to other components in the wireless device 110. The power source 317 may include one or more dry batteries, solar cells, fuel cells, and at least one of the same. Processor 314 may be connected to GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information for the wireless device 110.

The processor 314 of the wireless device 110 may be further connected to another peripheral device 319, which peripheral device comprises one or more software and / or hardware modules that provide additional features and / or functionality. be able to. For example, peripheral devices 319 include accelerometers, satellite transmitters and receivers, digital cameras, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, and the like. At least one of them can be included.

The communication interface 320A of the base stations 1 and 120A and / or the communication interface 320B of the base stations 2 and 120B are configured to communicate with the communication interface 310 of the wireless device 110 via the wireless link 330A and / or the wireless link 330B, respectively. Can be done. In one example, the communication interface 320A of base stations 1, 120A may communicate with the communication interface 320B of base station 2, as well as other RANs and core network nodes.

The radio link 330A and / or the radio link 330B can include at least one of a bidirectional link and / or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of base station 1 120A and / or with the communication interface 320B of base station 2 120B. Base station 1 120A and wireless device 110 and / or base station 2 120B and wireless device 110 transmit and receive transport blocks via wireless link 330A and / or wireless link 330B, respectively. Can be configured as The radio link 330A and / or the radio link 330B can use at least one frequency carrier. According to some various aspects of the embodiment, a transmitter / receiver (s) may be used. The transmitter / receiver can be a device that includes both a transmitter and a receiver. Transceivers may be used within devices such as wireless devices, base stations, relay nodes, and / or equivalents. Illustrative embodiments of the wireless technology implemented in the communication interfaces 310, 320A, 320B and the wireless links 330A, 330B are shown in FIGS. 8 and related texts are exemplified.

In one example, other nodes in the wireless network (eg, AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and memory for storing instructions.

When a node (eg, wireless device, base station, AMF, SMF, UPF, server, switch, antenna, and / or similar) is executed by one or more processors, and one or more processors. Can include a memory that stores instructions that allow the node to perform specific processes and / or functions. Illustrative embodiments may enable the operation of single-carrier and / or multi-carrier communications. Other exemplary embodiments can include non-transient tangible computer-readable media containing instructions that can be executed by one or more processors that enable the operation of single-carrier and / or multi-carrier communications. Yet another exemplary embodiment can include a product that includes a non-transient tangible computer readable machine accessible medium, which medium has programmable hardware with coded instructions at the top. It can enable nodes that operate single-carrier and / or multi-carrier communication. Nodes can include processors, memory, interfaces, and / or the like.

The interface can include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. Hardware interfaces can include electronic devices such as connectors, wires, drivers, amplifiers, and / or the like. The software interface can include a protocol (s), a protocol layer, a communication driver, a device driver, a combination thereof, and / or code stored in a memory device to implement something similar. A firmware interface contains a combination of embedded hardware and code stored and / or communicating with it in a memory device, including connectivity, electronic device operation, protocol (s), protocol layer, communication driver, device driver. , Hardware operation, combinations thereof, and / or similar can be achieved.

4A, 4B, 4C, and 4D are exemplary schematics for uplink and downlink signal transmission based on aspects of the embodiments of the present disclosure. FIG. 4A shows an exemplary uplink transmitter for at least one physical channel. A baseband signal that represents a physical uplink shared channel can perform one or more functions. One or more features are scrambling, modulation of scrambled bits to generate Magnalis symbols, mapping of Magnal modulation symbols on one or several transmission layers, transformations to generate Magnitude symbols. Precoding, precoding of complex value symbols, mapping of precoded complex value symbols to resource elements, complex value time domain single carrier frequency split multiple connection (SC-FDMA) or CP-OFDM signal to antenna port It can include at least one of generation and / or the like. In one example, if conversion precoding is possible, an SC-FDMA signal for uplink transmission can be generated. In one example, if conversion precoding is not possible, a CP-OFDM signal for uplink transmission may be generated by FIG. 4A. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

An exemplary structure for modulation and up-conversion of complex-valued SC-FDMA or CP-OFDM baseband signals and / or complex-valued physical random access channel (PRACH) baseband signals to carrier frequencies for antenna ports is shown in FIG. 4B. It is shown. Filtering may be used prior to transmission.

An exemplary structure for downlink transmission is shown in FIG. 4C. A baseband signal that represents a downlink physical channel can perform one or more functions. This one or more function is the scrambling of encoded bits in a code word to be transmitted over a physical channel, the modulation of scrambled bits to generate complex-value modulation symbols, the modulation of complex-value modulation symbols. Mapping onto one or several transmission layers, precoding complex-valued modulation symbols on each layer for transmission on the antenna port, mapping of antenna port complex-valued modulation symbols to resource elements, antenna port Each complex value time region OFDM signal generation and / or the like can be included. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

In one example, the gNB can transmit the first and second symbols on the antenna port to the wireless device. The wireless device infers the channel for transmitting the second symbol on the antenna port (eg, fading gain, multipath delay, etc.) from the channel for transmitting the first symbol on the antenna port. Can be done. In one example, the first antenna port and the second antenna port have one or more large-scale characteristics of the channel on which the first symbol is transmitted on the first antenna port, on the second antenna port. If the second symbol can be inferred from the transmitted channel, it can be placed approximately in the same location. One or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial reception (Rx) parameters.

Illustrative modulation and up-conversion of the complex value OFDM baseband signal of the antenna port to the carrier frequency is shown in FIG. 4D. Filtering may be used prior to transmission.

FIG. 5A is a schematic representation of an exemplary uplink channel mapping and an exemplary uplink physical signal. FIG. 5B is a schematic representation of exemplary downlink channel mapping and downlink physical signals. In one example, the physical layer can provide one or more information transfer services to the MAC and / or one or more higher layers. For example, the physical layer can provide one or more information transfer services to the MAC via one or more transport channels. Information transfer services can show how and with what characteristic data is transferred across the wireless interface.

In an exemplary embodiment, the wireless network can include one or more downlink and / or uplink transport channels. For example, the schematic of FIG. 5A shows an exemplary uplink transport channel including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. The schematic of FIG. 5B shows an exemplary downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. The transport channel can be mapped to one or more corresponding physical channels. For example, UL-SCH 501 may be mapped to a physical uplink shared channel (PUSCH) 503. RACH502 can be mapped to PRACH505. DL-SCH511 and PCH512 may be mapped to Physical Downlink Shared Channel (PDSCH) 514. BCH 513 may be mapped to physical broadcast channel (PBCH) 516.

There can be one or more physical channels that do not have a corresponding transport channel. This one or more physical channels can be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, the physical uplink control channel (PUCCH) 504 may carry the UCI 509 from the UE to the base station. For example, the physical downlink control channel (PDCCH) 515 may carry DCI 517 from the base station to the UE. The NR can support UCI 509 multiplexing in PUSCH 503 if the UCI 509 and PUSCH 503 transmissions can at least partially match within the slot. The UCI 509 can include at least one of CSI, acknowledgment (ACK) / negative acknowledgment (NACK), and / or scheduling request. The DCI 517 on the PDCCH 515 can indicate at least one of the following one or more downlink assignments and / or one or more uplink scheduling grants:

On the uplink, the UE can transmit one or more reference signals (RS) to the base station. For example, the one or more RSs may be at least one of Demodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and / or Sounding RS (SRS) 508. .. On the downlink, the base station can send one or more RSs to the UE (eg, unicast, multicast, and / or broadcast). For example, the one or more RSs may be at least one of a primary sync signal (PSS) / secondary sync signal (SSS) 521, CSI-RS522, DM-RS523, and / or PT-RS524.

In one example, the UE attaches one or more uplink DM-RS506 to the base station for channel estimation, eg, for coherent demodulation of one or more uplink physical channels (eg, PUSCH 503 and / or PUCCH 504). Can be sent. For example, the UE may transmit to the base station at least one uplink DM-RS506 having PUSCH 503 and / or PUCCH 504, the at least one uplink DM-RS506 having the same frequency range as the corresponding physical channel. It may extend to. In one example, the base station can configure a UE with one or more uplink DM-RS configurations. At least one DM-RS configuration can support the preceding DM-RS pattern. The preceding DM-RS can be mapped on one or more OFDM symbols (eg, one or two adjacent OFDM symbols). One or more additional uplink DM-RSs may be configured to transmit with one or more symbols of PUSCH and / or PUCCH. The base station can quasi-statistically configure the UE with the maximum number of preceding DM-RS symbols for PUSCH and / or PUCCH. For example, the UE can schedule the single symbol DM-RS and / or the double symbol DM-RS based on the maximum number of preceding DM-RS symbols, and the base station is for PUSCH and / or PUCCH. The UE can be configured with one or more additional uplink DM-RSs. The new wireless network can support a common DM-RS structure for DL and UL, for example, at least in the case of CP-OFDM, where the DM-RS location, DM-RS pattern, and / or scrambling sequence It may be the same or different.

In one example, the presence or absence of the uplink PT-RS507 may depend on the RRC configuration. For example, the presence of the uplink PT-RS can be configured uniquely to the UE. For example, the presence and / or pattern of uplink PT-RS507 in a scheduled resource is for RRC signaling and / or for other purposes that may be indicated by DCI (eg, modulation and coding schemes (MCS)). It can be configured uniquely to the UE by a combination of associations with one or more parameters used in. The dynamic presence of the uplink PT-RS507, when configured, can be associated with one or more DCI parameters, including at least MCS. The wireless network can support multiple uplink PT-RS densities defined in the time / frequency domain. Frequency domain density, if present, can be associated with at least one configuration of scheduled bandwidth. The UE can envision the same precoding for DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resource. For example, the uplink PT-RS507 can be limited within the scheduled time / frequency duration for the UE.

In one example, the UE may transmit SRS508 to the base station for channel state estimation that supports uplink channel dependent scheduling and / or link adaptation. For example, the SRS508 transmitted by the UE can cause the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler can use the uplink channel state to allocate one or more blocks of good quality for uplink PUSCH transmission from the UE. The base station can configure the UE quasi-statistically with one or more SRS resource sets. In the case of the SRS resource set, the base station can configure the UE with one or more SRS resources. The applicability of the SRS resource set can be configured by the parameters of the higher layers (eg RRC). For example, if the upper layer parameter indicates beam management, the SRS resources in each of one or more SRS resource sets may be transmitted at once. The UE can simultaneously transmit one or more SRS resources within different SRS resource sets. The new wireless network can support aperiodic, periodic, and / or semi-permanent SRS transmissions. The UE can send SRS resources based on one or more trigger types, the one or more trigger types being upper layer signaling (eg, RRC) and / or one or more DCI formats (eg, eg). The UE can select at least one of one or more configured SRS resource sets) using at least one DCI format). SRS trigger type 0 may mean an SRS triggered based on higher layer signaling. SRS trigger type 1 can mean SRS triggered based on one or more DCI formats. In one example, if PUSCH 503 and SRS508 are transmitted in the same slot, the UE may be configured to transmit SRS508 after transmission of PUSCH 503 and the corresponding uplink DM-RS506.

In one example, the base station may quasi-statistically configure the UE with one or more SRS configuration parameters indicating at least one of the following, which are the SRS resource configuration identifiers, Number of SRS ports, time-domain operation of SRS resource configuration (eg, periodic, semi-permanent, or aperiodic SRS display), slots for periodic and / or aperiodic SRS resources (mini-slots, and / Or subframe) Level periodicity and / or offset, number of OFDM symbols in the SRS resource, OFDM symbol start of the SRS resource, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

In one example, in a time domain, an SS / PBCH block can contain one or more OFDM symbols (eg, four OFDM symbols numbered from 0 to 3 in increasing order) within the SS / PBCH block. .. The SS / PBCH block can include PSS / SSS521 and PBCH516. In one example, in the frequency domain, the SS / PBCH block has 240 consecutive subcarriers with one or more consecutive subcarriers inside the SS / PBCH block (eg, subcarriers solicited in increasing order from 0 to 239). Carrier) can be included. For example, PSS / SSS521 may occupy one OFDM symbol and 127 subcarriers. For example, PBCH516 can span 3 OFDM symbols and 240 subcarriers. The UE has one or more SS / PBCH blocks transmitted using the same block index placed in pseudo-same position with respect to, for example, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. It can be assumed that it will be obtained. In the case of other SS / PBCH block transmissions, the UE cannot assume a pseudo-same position arrangement. The periodicity of the SS / PBCH block can be configured by a wireless network (eg, by RRC signaling), and one or more time positions where the SS / PBCH block can be transmitted can be determined by the subcarrier interval. In one example, the UE can assume a band-specific subcarrier spacing for SS / PBCH blocks unless the wireless network configures the UE to assume another subcarrier spacing.

In one example, the downlink CSI-RS522 can be used by the UE to acquire channel state information. The wireless network can support periodic, aperiodic, and / or semi-permanent transmission of the downlink CSI-RS522. For example, the base station can quasi-statistically configure and / or reconfigure the UE using the periodic transmission of the downlink CSI-RS522. The configured CSI-RS resource can be up and / or shut down. For semi-persistent transmissions, activation and / or shutdown of CSI-RS resources can be dynamically triggered. In one example, the CSI-RS configuration can include at least one or more parameters indicating the number of antenna ports. For example, a base station can configure a UE with 32 ports. Base stations can quasi-statistically configure UEs with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated to one or more UEs from one or more CSI-RS resource sets. For example, a base station quasi-statistics one or more parameters indicating CSI RS resource mapping, such as the time domain location of one or more CSI-RS resources, the bandwidth of CSI-RS resources, and / or periodicity. Can be configured as a target. In one example, if the downlink CSI-RS522 and the core set are spatially quasi-coordinated, the UE will give the same OFDM symbol to the downlink CSI-RS522 and the control resource set (core set). The resource elements that can be configured to be used and associated with the downlink CSI-RS522 are outside the PRB configured for the core set. In one example, if the downlink CSI-RS522 and SSB / PBCH are spatially located in pseudo-same position, the UE should use the same OFDM symbol for the downlink CSI-RS522 and SSB / PBCH. The resource element that can be configured in and associated with the downlink CSI-RS522 is outside the PRB configured for SSB / PBCH.

In one example, the UE transmits one or more downlink DM-RS523s to the base station for channel estimation, eg, to perform coherent demodulation of one or more downlink physical channels (eg, PDSCH514). be able to. For example, wireless networks can support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration can support the preceding DM-RS pattern. The preceding DM-RS can be mapped on one or more OFDM symbols (eg, one or two adjacent OFDM symbols). The base station can quasi-statistically configure the UE with the maximum number of preceding DM-RS symbols for PDSCH514. For example, a DM-RS configuration can support one or more DM-RS ports. For example, in the case of single-user-MIMO, the DM-RS configuration can support at least eight orthogonal downlink DM-RS ports. For example, in the case of multi-user-MIMO, the DM-RS configuration can support 12 orthogonal downlink DM-RS ports. The wireless network can support a common DM-RS structure for DL and UL, for example at least for CP-OFDM, and the DM-RS location, DM-RS pattern, and / or scrambling sequence are the same. Or may be different.

In one example, the presence or absence of the downlink PT-RS524 may depend on the RRC configuration. For example, the presence of downlink PT-RS524 can be configured uniquely to the UE. For example, the presence and / or pattern of downlink PT-RS524 within a scheduled resource may be used for RRC signaling and / or other purposes that may be indicated by DCI (eg, MCS). It can be configured uniquely to the UE in combination with associations with parameters. The dynamic presence of the downlink PT-RS524, when configured, can be associated with one or more DCI parameters, including at least MCS. The wireless network can support multiple PT-RS densities defined in the time / frequency domain. Frequency domain density, if present, can be associated with at least one configuration of scheduled bandwidth. The UE can envision the same precoding for DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resource. For example, the downlink PT-RS524 can be limited within the scheduled time / frequency duration for the UE.

FIG. 6 is a schematic diagram depicting an exemplary frame structure of a carrier based on aspects of the embodiments of the present disclosure. In a multi-carrier OFDM communication system, one or more carriers can be included, for example, 1 to 32 carriers in the case of carrier aggregation, or 1 to 64 carriers in the case of dual connection. It reaches. Different radio frame structures may be supported (eg, for FDD schemes and for TDD duplex schemes). FIG. 6 shows an exemplary frame structure. The downlink and uplink transmissions may be configured within the radio frame 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10 ms radio frame 601 can be divided into 10 equally sized subframes 602 with a duration of 1 ms. The subframe (s) can include one or more slots (eg, slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz may include 1, 2, 4, 8, 16, and 32 slots, respectively. it can. In FIG. 6, the subframe can be divided into two equally sized slots 603 with a duration of 0.5 ms. For example, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmission at 10 millisecond time intervals. Uplink and downlink transmissions can be separated in the frequency domain. The slot (s) can include a plurality of OFDM symbols 604. The number of OFDM symbols 604 in slot 605 may depend on the cyclic prefix length. For example, one slot can be 14 OFDM symbols with the same subcarrier spacing of up to 480 kHz with normal CP. One slot can be 12 OFDM symbols with the same subcarrier spacing of 60 kHz with extended CP. One slot can include downlinks, uplinks, or downlink and uplink portions, and / or the like.

FIG. 7A is a schematic diagram depicting an exemplary OFDM subcarrier set based on aspects of the embodiments of the present disclosure. In this example, the gNB can communicate with a wireless device having a carrier with an exemplary channel bandwidth of 700. Arrows (s) in the schematic may indicate subcarriers in a multicarrier OFDM system. The OFDM system can use techniques such as OFDM technology, SC-FDMA technology, and / or the like. In one example, arrow 701 indicates a subcarrier that transmits an information symbol. In one example, the subcarrier spacing 702 between two adjacent subcarriers within the carrier can be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz and the like. In one example, different subcarrier intervals may correspond to different transmission numerologies. In one example, the transmitted numerology can include at least the numerology index, the value of the subcarrier interval, the type of cyclic prefix (CP). In one example, the gNB can be transmitted to and received from the UE on a number of subcarriers 703 within the carrier. In one example, the bandwidth (transmission bandwidth) occupied by a large number of subcarriers 703 may be less than the carrier channel bandwidth 700 due to guard bands 704 and 705. In one example, guard bands 704 and 705 can be used to reduce interference to / from one or more neighboring carriers. The number of subcarriers (transmission bandwidth) within a carrier can depend on the channel bandwidth of the carrier and the subcarrier spacing. For example, in the case of a carrier with a 20 MHz channel bandwidth and a 15 KHz subcarrier spacing, the transmission bandwidth can be 1024 subcarriers.

In one example, the gNB and wireless device can communicate with multiple CCs when configured with CA. In one example, different component carriers may have different bandwidths and / or subcarrier spacing if CA is supported. In one example, the gNB can send a first type of service to a UE on a first component carrier. The gNB can send a second type of service to the UE on the second component carrier. Different types of services may have different service requirements (eg, data rate, latency, reliability), which make them suitable for transmission over different component carriers with different subcarrier spacing and / or bandwidth. obtain. FIG. 7B shows an exemplary embodiment. The first component carrier can include a first number of subcarriers 706 with a first subcarrier spacing of 709. The second component carrier can include a second number of subcarriers 707 with a second subcarrier spacing of 710. The third component carrier can include a third number of subcarriers 708 with a third subcarrier spacing of 711. The carriers in the multicarrier OFDM communication system can be continuous carriers, discontinuous carriers, or a combination of both continuous and discontinuous carriers.

FIG. 8 is a schematic diagram depicting an OFDM radio resource based on an embodiment of the present disclosure. In one example, the carrier may have a transmission bandwidth of 801. In one example, the resource grid can be in the structure of frequency domain 802 and time domain 803. In one example, the resource grid can contain a first number of OFDM symbols in a subframe, and a second number of resource blocks, and for transmission numerology and carriers, higher layer signaling (eg, RRC signaling). ) Indicates the common resource block. In one example, in the resource grid, the resource unit identified by the subcarrier index and symbol index can be resource element 805. In one example, the subframe can include a first number of OFDM symbols 807 depending on the numerology associated with the carrier. For example, if the carrier numerology subcarrier spacing is 15 KHz, the subframe can have 14 OFDM symbols for the carrier. If the numerology subcarrier spacing is 30 KHz, the subframe can have 28 OFDM symbols. If the numerology subcarrier spacing is 60 KHz, the subframe can have 56 OFDM symbols. In one example, a second number of resource blocks contained within a carrier's resource grid may depend on carrier bandwidth and numerology.

As shown in FIG. 8, the resource block 806 can include 12 subcarriers. In one example, multiple resource blocks can be grouped into a resource block group (RBG) 804. In one example, the size of the RBG may depend on at least one of the RRC message indicating the RBG size configuration, the size of the carrier bandwidth, or the bandwidth portion of the carrier. In one example, the carrier can include multiple bandwidth portions. The first bandwidth portion of the carrier can have a different frequency position and / or bandwidth than the second bandwidth portion of the carrier.

In one example, the gNB can transmit downlink control information, including downlink or uplink resource block allocation, to the wireless device. The base station is scheduled and transmitted data packets (eg, transport) via one or more resource blocks and one or more slots according to the downlink control information and / or parameters in the RRC message (s) Blocks) can be sent to or received from the wireless device. In one example, a starting symbol for the first slot of one or more slots may be shown on the wireless device. In one example, the gNB can send or receive data packets scheduled for one or more RBGs and one or more slots to or from a wireless device.

In one example, the gNB can transmit downlink control information, including downlink allocation, to wireless devices via one or more PDCCHs. The downlink allocation can include at least parameters indicating modulation and coding formats, resource allocation, and / or HARQ information regarding DL-SCH. In one example, resource allocation can include resource block allocation parameters and / or slot allocation. In one example, the gNB can dynamically allocate resources to wireless devices via the Cell Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device can monitor one or more PDCCHs to find possible allocations when downlink reception of the wireless device is possible. If the wireless device successfully detects one or more PDCCHs, it can receive one or more downlink data packages on one or more PDCCHs scheduled by one or more PDCCHs.

In one example, the gNB can allocate configuration scheduling (CS) resources for downlink transmission to wireless devices. The gNB can send one or more RRC messages indicating the periodicity of the CS grant. The gNB can transmit the DCI via the PDCCH addressed to the configuration scheduling-RNTI (CS-RNTI) that activates the CS resource. The DCI can include a parameter indicating that the downlink grant is a CS grant. CS grants can be implicitly reused until stopped, according to the periodicity defined by one or more RRC messages.

In one example, the gNB can transmit downlink control information, including uplink grants, to wireless devices via one or more PDCCHs. The uplink grant can include at least parameters indicating modulation and coding formats, resource allocation, and / or HARQ information about UL-SCH. In one example, resource allocation can include resource block allocation parameters and / or slot allocation. In one example, the gNB can dynamically allocate resources to wireless devices via C-RNTI on one or more PDCCHs. The wireless device can monitor one or more PDCCHs to find possible resource allocations. If the wireless device successfully detects one or more PDCCHs, it can transmit one or more uplink data packages via one or more PUSCHs scheduled by one or more PDCCHs.

In one example, the gNB can allocate CS resources for transmitting uplink data to wireless devices. The gNB can send one or more RRC messages indicating the periodicity of the CS grant. The gNB can transmit the DCI via the PDCCH addressed to the CS-RNTI that activates the CS resource. The DCI can include a parameter indicating that the uplink grant is a CS grant. CS grants can be implicitly reused until stopped, according to the periodicity defined by one or more RRC messages.

In one example, the base station can transmit DCI / control signaling via PDCCH. The DCI can acquire one of a plurality of formats. The DCI is a downlink and / or uplink scheduling information (eg, resource allocation information, HARQ related parameters, MCS), a CSI request (eg, aperiodic CQI report), an SRS request, up for one or more cells. It can include a link power control command, one or more timing information (eg, TB transmission / reception timing, HARQ feedback timing, etc.) and the like. In one example, DCI can indicate an uplink grant that includes transmit parameters for one or more transport blocks. In one example, DCI can indicate a downlink assignment that indicates a parameter for receiving one or more transport blocks. In one example, DCI can be used by a base station to initiate conflict-free random access in a wireless device. In one example, the base station may transmit a DCI containing a slot format indicator (SFI) notifying the slot format. In one example, the base station may transmit a DCI containing a pre-purchase indication notifying the PRB (s) and / or OFDM symbols (s), where the UE intends to transmit for the UE. It can be assumed that it has not been done. In one example, the base station can transmit DCI for group power control of PUCCH or PUSCH or SRS. In one example, DCI can correspond to RNTI. In one example, the wireless device can acquire the RNTI in response to completing the initial access (eg, C-RNTI). In one example, the base station can configure an RNTI for radio (eg, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In one example, the wireless device can calculate the RNTI (eg, the wireless device can calculate the RA-RNTI based on the resources used to transmit the preamble). In one example, the RNTI can have a preset value (eg, P-RNTI or SI-RNTI). In one example, the wireless device can monitor a group common search space, which space transmits a DCI that is used by a base station and is intended for a group of UEs. In one example, the group common DCI can correspond to an RNTI commonly configured for a group of UEs. In one example, the wireless device can monitor the UE-specific search space. In one example, the UE-specific DCI can correspond to an RNTI configured for a wireless device.

In an exemplary embodiment, the new wireless network can support bandwidth adaptation (BA). In one example, the receive and / or transmit bandwidth configured by the UE with BA does not have to be large. For example, the receive and / or transmit bandwidth does not have to be as large as the bandwidth of the cell. The receive and / or transmit bandwidth may be adjustable. For example, the UE can vary the receive and / or transmit bandwidth to reduce and save power, for example during periods of low activity. For example, the UE can change the position of the receive and / or transmit bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE can vary the subcarrier spacing to enable different services, for example.

In an exemplary embodiment, a subset of the total cell bandwidth of a cell is sometimes referred to as the bandwidth portion (BWP). A base station can configure a UE with one or more BWPs to achieve BA. For example, the base station can indicate to the UE which of the one or more (configured) BWPs is the active BWP.

FIG. 9 comprises BWP1 (1010 and 1050) having a width of 40 MHz and a subcarrier spacing of 15 kHz, BWP2 (1020 and 1040) having a width of 10 MHz and a subcarrier spacing of 15 kHz, and BWP3 1030 having a width of 20 MHz and a subcarrier spacing of 60 kHz. It is an exemplary schematic of the three BWPs made.

In one example, the UE is configured to operate within one or more BWPs in a cell, one or more upper layers per cell (eg, RRC layer), per cell. A set of one or more BWPs (eg, up to four BWPs) for reception by the UE (DL BWP set) within the DL bandwidth with at least one parameter DL-BWP, and at least one per cell. It may consist of one or more sets of BWPs (eg, up to 4 BWPs) for reception by the UE (UL BWP set) within the UL bandwidth with one parameter UL-BWP.

To enable BA in the PCell, the base station can configure the UE with one or more UL and DL BWP pairs. To enable BA in SCell (eg, in the case of CA), the base station can configure the UE with at least one DL BWP (eg, UL may have nothing). is there).

In one example, the initial active DL BWP can be defined by at least one of the position and number of consecutive PRBs, subcarrier spacing, or cyclic prefix for a control resource set for at least one common search space. .. For operation with PCell, one or more upper layer parameters can indicate at least one initial UL BWP for random access procedures. If the UE is configured with a secondary carrier in the primary cell, the UE may be configured with an initial BWP for a random access procedure in the secondary carrier.

In one example, in the case of unpaired spectral operation, the UE can expect that the center frequency in the case of DL BWP can be the same as the center frequency in the case of UL BWP.

For example, for each DL BWP or UL BWP in a set of one or more DL BWPs or one or more UL BWPs, the base station uses one or more parameters indicating at least one of the following: UEs for cells can be configured quasi-statistically, and their parameters are subcarrier spacing, cyclic prefix, number of consecutive PRBs, one or more DL BWP and / or one or more UL. Index within BWP set, link between DL BWP and UL BWP from configured DL BWP and UL BWP set, DCI detection for PDSCH reception timing, PDSCH reception for HARQ-ACK transmission timing value, PUSCH transmission DCI detection for the timing value, the offset of the first PRB of the DL bandwidth or the UL bandwidth with respect to the first PRB of the bandwidth.

In one example, for a DL BWP in a set of one or more DL BWPs in a PCell, the base station is one or more for at least one type of common search space and / or one UE-specific search space. A UE can be configured with a control resource set. For example, a base station cannot configure a UE in an active DL BWP without a common search space on a PCell or on a PSCell.

If there are UL BWPs in one or more sets of UL BWPs, the base station can configure the UE with one or more resource sets for one or more PUCCH transmissions.

In one example, if the DCI includes a BWP indicator field, the BWP indicator field value can indicate an active DL BWP from a DL BWP set configured for one or more DL receptions. If the DCI includes a BWP indicator field, the BWP indicator field value can indicate an active UL BWP from the configured UL BWP set for one or more UL transmissions.

In one example, in the case of PCell, the base station can quasi-statistically configure the UE with the default DL BWP between the configured DL BWPs. If the UE is not provided with a default DL BWP, the default BWP can be the initial active DL BWP.

In one example, the base station can configure the UE using the timer value of the PCell. For example, if the UE detects a DCI that indicates an active DL BWP other than the default DL BWP in the case of paired spectral behavior, or if the UE has unpaired spectral behavior, the default DL. When a DCI indicating an active DL BWP or UL BWP other than BWP or UL BWP is detected, the UE can start a timer called a BWP stop timer. If the UE does not detect DCI during the period of paired or unpaired spectral operation, the UE will perform a period of first value (eg, the first value is 1 millisecond). The timer can be advanced to seconds or 0.5 milliseconds). In one example, a timer may expire when the timer becomes equal to its timer value. The UE can switch from the active DL BWP to the default DL BWP when the timer expires.

In one example, a base station can quasi-statistically configure a UE with one or more BWPs. The UE responds to receiving a DCI indicating the second BWP as an active BWP and / or in response to the expiration of the BWP stop timer (eg, the second BWP can be the default BWP). The active BWP can be switched from the first BWP to the second BWP. For example, FIG. 9 is an exemplary schematic configuration of three BWPs, BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be the default BWP. BWP1 (1010) may be the initial active BWP. In one example, the UE can switch the active BWP from BWP1 1010 to BWP2 1020 in response to the expiration of the BWP stop timer. For example, the UE may switch the active BWP from the BWP2 1020 to the BWP3 1030 in response to receiving a DCI indicating the BWP3 1030 as an active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 responds to receiving a DCI indicating active BWP and / or to the expiration of the BWP stop timer. It may be a thing.

In one example, if the UE is configured for a secondary cell with a default DL BWP between the configured DL BWP and timer value, then the UE procedure in the secondary cell is the timer value in the secondary cell, and the secondary cell. It may be the same as the primary cell using the default DL BWP of.

In one example, if the base station configures the UE with the first active DL BWP and the first active UL BWP on the secondary cell or carrier, the UE will have the displayed DL BWP on the secondary cell, and The displayed UL BWP can be adopted as the first active DL BWP and the first active UL BWP on the secondary cell or carrier, respectively.

10A and 10B show packet flows using multi-connections (eg, dual connections, multi-connections, close interactions, and / or similar). FIG. 10A is an exemplary schematic of the protocol structure of a wireless device 110 (eg, UE) with CA and / or multi-connection, based on aspects of the embodiment. FIG. 10B is an exemplary schematic of the protocol structure of a plurality of base stations using CA and / or multi-connection, based on aspects of the embodiment. Multiple base stations include a master node, MN1130 (eg, master node, master base station, master gNB, master eNB, and / or similar), and a secondary node, SN1150 (eg, secondary node, secondary base station, secondary). gNB, secondary eNB, and / or similar) can be included. The master node 1130 and the secondary node 1150 can cooperate to communicate with the wireless device 110.

When a multi-connection is configured for the wireless device 110, the wireless device 110 may support multiple receive / transmit functions with the RRC connected and is provided by multiple schedulers at multiple base stations. It can be configured to utilize wireless resources. Multiple base stations may be interconnected via non-ideal or ideal backhauls (eg, Xn interface, X2 interface, and / or similar). The base station required for multi-connection to a particular wireless device may perform at least one of two different roles, i.e. the base station either as a master base station or as a secondary base station. Can perform its function. In a multi-connection, the wireless device may be connected to one master base station and one or more secondary base stations. In one example, a master base station (eg, MN1130) provides a wireless device (eg, wireless device 110) with a master cell group (MCG) containing one primary cell and / or one or more secondary cells. Can be. A secondary base station (eg, SN1150) provides a wireless device (eg, wireless device 110) with one primary secondary cell (PSCell) and / or a secondary cell group (SCG) containing one or more secondary cells. Can be provided.

In multi-connection, the radio protocol architecture used by the bearer may depend on how the bearer is configured. In one example, three different types of bearer configuration options, namely MCG bearers, SCG bearers, and / or split bearers may be supported. The wireless device may receive / transmit MCG bearer packets via one or more cells of the MCG and / or receive / transmit SCG bearer packets via one or more cells of the SCG. be able to. Multi-connection can also be described as having at least one bearer configured to use the radio resources provided by the secondary base station. Multi-connection may or may not be configured / realized in some exemplary embodiments.

In one example, the wireless device (eg, wireless device 110) includes a SDAP layer (eg, SDAP1110), a PDCP layer (eg, NR PDCP1111), an RLC layer (eg, MN RLC1114), and a MAC layer (eg, MN MAC1118). Through MCG bearer packets, SDAP layer (eg SDAP1110), PDCP layer (eg NR PDCP1112), master or secondary RLC layer (eg MN RLC1115, SN RLC1116), and master or secondary MAC layer. Packets of split bearers via one of (eg, MN MAC1118, SN MAC1119) and / or SDAP layer (eg, SDAP1110), PDCP layer (eg, NR PDCP1113), RLC layer (eg, SN RLC1117), And SCG bearer packets, which can be transmitted and / or received via the MAC layer (eg, MN MAC1119).

In one example, the master base station (eg, MN1130) and / or the secondary base station (eg, SN1150) is the master or secondary node SDAP layer (eg, SDAP1120, SDAP1140), master or secondary node PDCP layer (eg, NR PDCP1121, etc.). NR PDCP1142), masternode RLC layer (eg, MN RLC1124, MN RLC1125), and MCG bearer packet, master or secondary node SDAP layer (eg, SDAP1120, SDAP1140) via masternode MAC layer (eg, MN MAC1128). SCG bearer packets via the master or secondary node PDCP layer (eg, NR PDCP1122, NR PDCP1143), secondary node RLC layer (eg, SN RLC1146, SN RLC1147), and secondary node MAC layer (eg, SN MAC1148). Master or secondary node SDAP layer (eg SDAP1120, SDAP1140), master or secondary node PDCP layer (eg NR PDCP1123, NR PDCP1141), master or secondary node RLC layer (eg MN RLC1126, SN RLC1144, SN RLC1145, MN RLC1127) ), And the split bearer packets can be transmitted / received via the master or secondary node MAC layer (eg, MN MAC1128, SN MAC1148).

In multi-connection, the wireless device can configure multiple MAC entities, one MAC entity for the master base station (eg, MN MAC1118), and another MAC entity for the secondary base station (eg, SN MAC1119). .. In a multi-connection, a configured set of serving cells for a wireless device can include two subsets, an MCG containing the serving cell of the master base station and an SCG containing the serving cell of the secondary base station. In the case of SCG, one or more of the following configurations may be applied, i.e., at least one cell of SCG has a configured UL CC and the primary secondary cell (PSCell of SCG, At least one cell of the SCG, called a PCell, or possibly a PCell), is configured with PUCCH resources, and if the SCG is configured, there is at least one SCG bearer or one split bearer. Possible, when detecting a physical layer or random access problem on the PSCell, or when detecting the number of NR RLC retransmissions that arrived in association with the SCG, or when detecting an access problem with the PSCell during SCG addition or SCG modification. The RRC connection reestablishment procedure may not be triggered, UL transmissions destined for the SCG cell may be stopped, the master base station may be notified by the radio device regarding the SCG failure type, and the split bearer. In the case of, DL data transfer across the master base station can be maintained, the NR RLC affirmative mode (AM) bearer can be configured for the split bearer, and the PCell and / or PSCell need not be stopped. , PSCell can be modified using SCG modification procedures (eg, using security key modification and RACH procedures) and / or bearer type modification between split bearers and SCG bearers, or simultaneous SCG and split bearers. The configuration may or may not be supported.

For the interaction between the master base station and the secondary base station in the case of multi-connection, one or more of the following may be applied, and the master base station and / or the secondary base station is the RRM measurement of the wireless device. The configuration can be maintained and the master base station can add resources for wireless devices (eg serving cells) to the secondary base station (eg, based on received measurement reports, traffic conditions, and / or bearer type). Upon receiving a request from the master base station, the secondary base station creates / modifies (or modifies) a container that could be the configuration of an additional serving cell for the wireless device. It can be determined that the secondary base station does not have the resources available to do so), and for UE capability coordination, the master base station has AS configuration and (part of) the UE capability as the secondary base. It can be provided to stations, and master and secondary base stations can exchange information about UE configurations by using RRC containers (internode messages) carried via Xn messages. The secondary base station can start reconfiguring the existing serving cell of the secondary base station (eg, PUCCH towards the secondary base station), and the secondary base station determines which cell is the PSCell in the SCG. The master base station may or may not change the contents of the RRC configuration provided by the secondary base station, and in the case of SCG addition and / or SCG SCell addition, the master base station may be the SCG cell ( The latest (or most recent) measurement results for (s) can be provided, and the master and secondary base stations are SFNs and / or subs of each other from the OAM and / or via the Xn interface. Information on frame offsets can be received (eg, for DRX adjustment and / or measurement gap identification). In one example, when adding a new SCG SCell, dedicated RRC signaling can be used to transmit the cell's requested system information about the CA, except for the SFN obtained from the SCG's PSCell MIB.

FIG. 11 is an exemplary schematic of a random access procedure. One or more events can trigger a random access procedure. For example, one or more events can be at least one of the following, that is, during initial access from RRC_IDLE, RRC connection reestablishment procedure, handover, RRC_CONNECTED when UL synchronization status is out of sync. DL or UL data arrival in, transition from RRC_Inactive, and / or request for other system information. For example, a PDCCH instruction, a MAC entity, and / or a beam fault display can initiate a random access procedure.

In an exemplary embodiment, the random access procedure can be at least one of a conflict-based random access procedure and a conflict-free random access procedure. For example, a conflict-based random access procedure can include one or more Msg1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and conflict resolution 1250. For example, a conflict-free random access procedure can include one or more Msg1 1220 transmissions and one or more Msg2 1230 transmissions.

In one example, the base station may transmit (eg, unicast, multicast, or broadcast) RACH configuration 1210 to the UE via one or more beams. The RACH configuration 1210 can include one or more parameters indicating at least one of the following, which are the available set of PRACH resources for the transmission of random access preambles, the initial preamble power (eg, eg). Random access preamble initial receive target power), SS block selection, and RSRP threshold for the corresponding PRACH resource, power ramping factor (eg, random access preamble power ramping step), random access preamble index, maximum number of preamble transmissions, Preamble groups A and B, a threshold for determining a group of random access preambles (eg, message size), one or more random access preambles for system information requests, and a set of corresponding PRACH resources (s), if. One or more random access preambles of the beam fault recovery request, if any, and the corresponding set of PRACH resources (s), time window to monitor the RA response (s), if any, beam fault recovery request A time window for monitoring the response (s) in, and / or a conflict resolution timer.

In one example, the Msg1 1220 can be one or more transmissions of a random access preamble. For conflict-based random access procedures, the UE can select SS blocks with RSRP above the RSRP threshold. If a random access preamble group B is present, the UE can select one or more random access preambles from group A or group B, depending on the possible Msg3 1240 size. If the random access preamble group B does not exist, the UE can select one or more random access preambles from group A. The UE can randomly select a random access preamble index (eg, using equal probabilities or normal distribution) from one or more random access preambles associated with the selected group. If the base station quasi-statistically configures the UE with the association between the random access preamble and the SS block, the UE is one or more associated with the selected SS block and the selected group. Random access preamble indexes can be randomly selected from random access preambles with similar probabilities.

For example, the UE can initiate a conflict-free random access procedure based on the beam failure indication from the lower layers. For example, a base station quasi-statistically configures a UE with one or more conflict-free PRACH resources for beam fault recovery requests associated with at least one of SS blocks and / or CSI-RS. be able to. At least one of the SS blocks having an RSRP above the first RSRP threshold between the associated SS blocks, or a CSI- having an RSRP above the second RSRP threshold between the associated CSI-RSs. If at least one of the RSs is available, the UE selects the random access preamble index corresponding to the selected SS block or CSI-RS from the set of one or more random access preambles for the beam failure recovery request. can do.

For example, the UE can receive a random access preamble index from a base station via PDCCH or RRC for a conflict-free random access procedure. If the base station does not configure the UE with at least one conflict-free PRACH resource associated with the SS block or CSI-RS, the UE can choose a random access preamble index. At least one SS in which the base station configures the UE with one or more non-conflict PRACH resources associated with the SS block and has an RSRP above the first RSRP threshold in the associated SS block. If a block is available, the UE may select at least one SS block and select a random access preamble corresponding to that at least one SS block. At least one base station that configures a UE with one or more non-conflict PRACH resources associated with a CSI-RS and has an RSRP above the second RSSR threshold among the associated CSI-RSs. If one CSI-RS is available, the UE can select at least one CSI-RS and a random access preamble corresponding to at least one CSI-RS.

The UE can perform one or more Msg1 1220 transmissions by transmitting the selected random access preamble. For example, if the UE selects an SS block and is configured with one or more PRACH opportunities and an association between one or more SS blocks, then the UE is one corresponding to the selected SS block. The PRACH opportunity can be determined from the above PRACH opportunities. For example, if the UE selects CSI-RS and is configured with one or more PRACH opportunities and one or more CSI-RS associations, then the UE corresponds to the selected CSI-RS. The PRACH opportunity can be determined from one or more PRACH opportunities. The UE can transmit the selected random access preamble to the base station via the selected PRACH opportunity. The UE can determine the transmit power for transmission of the selected random access preamble, at least based on the initial preamble power and power ramping factor. The UE can determine the RA-RNTI associated with the selected PRACH opportunity to which the selected random access preamble is transmitted. For example, the UE does not have to determine the RA-RNTI for the beam failure recovery request. The UE determines RA-RNTI based on at least the index of the first OFDM symbol, the index of the first slot of the selected PRACH opportunity, and / or the uplink carrier index for transmission of Msg1 1220. be able to.

In one example, the UE can receive a random access response, Msg2 1230, from the base station. The UE can start a time window (eg, ra-ResponseWindow) to monitor the random access response. For beam fault recovery requests, the base station can configure the UE with different time windows (eg, bfr-ResponseWindow) to monitor the response of the beam fault recovery request. For example, the UE can start a time window (eg, ra-ResponseWindow or bfr-ResponseWindow) at the beginning of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the preamble transmission. If the UE transmits multiple preambles, the UE may start a time window from the end of the first preamble transmission at the start of the first PDCCH opportunity after a fixed duration of one or more symbols. .. The UE of the cell responds to at least one random access response identified by RA-RNTI, or at least one response to a beam failure recovery request identified by C-RNTI, while the timer in the time window is running. PDCCH can be monitored.

In one example, the UE may consider reception of a random access response normal if at least one random access response contains a random access preamble identifier corresponding to the random access preamble transmitted by the UE. The UE may consider the conflict-free random access procedure to complete successfully if the random access response is successfully received. If a conflict-free random access procedure is triggered for a beam failure recovery request, the UE may consider the conflict-free random access procedure to complete successfully if the PDCCH transmission is addressed to C-RNTI. .. In one example, if at least one random access response contains a random access preamble identifier, the UE can consider the random access procedure to complete successfully and indicate that it has received an acknowledgment for a system information request to a higher layer. .. If the UE sends multiple preamble transmissions, the UE may stop transmitting the remaining preambles (if any) in response to the successful reception of the corresponding random access response.

In one example, the UE may perform one or more Msg3 1240 transmissions in response to a successful reception of a random access response (eg, in the case of a conflict-based random access procedure). The UE may adjust the uplink send timing based on the timing advanced command indicated by the random access response and send one or more transport blocks based on the uplink grant indicated by the random access response. obtain. The subcarrier spacing for PUSCH transmission of Msg3 1240 can be provided by at least one upper layer (eg, RRC) parameter. The UE can transmit a random access preamble via PRACH and Msg3 1240 via PUSCH on the same cell. The base station can indicate the UL BWP for PUSCH transmission of the Msg3 1240 via the system information block. The UE can use HARQ for retransmission of Msg3 1240.

In one example, multiple UEs may execute Msg1 1220 by transmitting the same preamble to the base station and may receive the same random access response (eg, TC-RNTI) containing the identity from the base station. Conflict resolution 1250 can ensure that a UE does not accidentally use the identity of another UE. For example, conflict resolution 1250 may be based on C-RNTI on PDCCH or UE conflict resolution identity on DL-SCH. For example, if the base station assigns a C-RNTI to a UE, the UE can perform conflict resolution 1250 based on the receipt of a PDCCH transmission addressed to the C-RNTI. In response to the detection of C-RNTI on the PDCCH, the UE may consider the conflict resolution 1250 to be normal and the random access procedure to complete successfully. If the UE does not have the proper C-RNTI, conflict resolution can be addressed by using TC-RNTI. For example, if the MAC PDU is successfully decrypted and the MAC PDU contains a UE conflict resolution identity MAC CE that matches the CCCH SDU sent to the Msg3 1250, the UE may consider the conflict resolution 1250 to be normal. It can be considered that the random access procedure completed successfully.

FIG. 12 is an exemplary structure for a MAC entity, based on aspects of the embodiment. In one example, the wireless device may be configured to operate in multi-connection mode. An RRC_CONNECTED radio device with a plurality of RX / TX may be configured to utilize radio resources provided by a plurality of schedulers installed within the plurality of base stations. The plurality of base stations may be connected via a non-ideal or ideal backhaul via an Xn interface. In one example, each base station in a plurality of base stations can function as a master base station or as a secondary base station. The wireless device may be connected to one master base station and one or more secondary base stations. The wireless device may be configured with multiple MAC entities, eg, one MAC entity for the master base station and one or more other MAC entities for the secondary base station (s). In one example, a set of serving cells configured for a wireless device consists of two subsets, an MCG containing the serving cells of the master base station and one or more SCGs containing the serving cells of the secondary base station (s). Can include. FIG. 13 shows an exemplary structure of a MAC entity when MCGs and SCGs are configured for wireless devices.

In one example, at least one cell in the SCG may have a configured UL CC, and one of the at least one cell may be referred to as the SCG's PSCell or PCell, or in some cases, the SCG. It can be simply called PCell. PSCell can be configured using PUCCH resources. In one example, when an SCG is configured, there may be at least one SCG bearer, or one split bearer. In one example, about detecting a physical layer or random access problem with PSCell, or about reaching the number of RLC retransmissions associated with SCG, or about accessing with PSCell during SCG addition or SCG modification. For detecting problems, the RRC connection reestablishment procedure may not be triggered, UL transmissions destined for the SCG cell may be aborted, and the master base station is notified by the UE regarding the type of SCG failure. DL data transfer via the master base station may be maintained.

In one example, the MAC sublayer can provide services such as data transfer and radio resource allocation to higher layers (eg, 1310 or 1320). This MAC sublayer can include multiple MAC entities (eg 1350 and 1360). This MAC sublayer can provide data transfer services on the logical channel. Multiple types of logical channels can be defined to accommodate different types of data transfer services. Logical channels can support the transfer of certain types of information. The logical channel type can be defined by what type of information (eg, control or data) is transferred. For example, BCCH, PCCH, CCCH, and DCCH can be control channels and DTCH can be traffic channels. In one example, a first MAC entity (eg, 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In one example, a second MAC entity (eg, 1320) may provide services on BCCH, DCCH, DTCH, and MAC control elements.

The MAC sublayer can infer services such as data transfer services, HARQ feedback signaling, scheduling request or measurement signaling (eg CQI) from the physical layer (eg 1330 or 1340). In one example, in a dual connection, two MAC entities can be configured for the wireless device, i.e. they are one for the MCG and one for the SCG. The MAC entity of the wireless device can handle multiple transport channels. In one example, the first MAC entity is the PCCH of the MCG, the first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and the MCG. A first transport channel containing one or more first RACHs can be processed. In one example, the second MAC entity is the second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more of the SCGs. A second transport channel, including a second RACH, can be processed.

In one example, when a MAC entity is configured with one or more SCells, there can be multiple DL-SCHs, multiple UL-SCHs, and multiple RACHs for each MAC entity. In one example, each SpCell may have one DL-SCH and UL-SCH. In one example, there can be one DL-SCH, zero or one UL-SCH, and zero or one RACH for each SCell. The DL-SCH can support reception using a separate numerology and / or TTI duration within the MAC entity. UL-SCH can also support transmission using separate numerology and / or TTI duration within the MAC entity.

In one example, the MAC sublayer can support separate functions and control (eg, 1355 or 1365) elements can be used to control these functions. The function performed by the MAC entity should be delivered to the physical layer on the transport channel (eg, uplink), the mapping between the logical channel and the transport channel (eg, uplink or downlink). Multiplexing the MAC SDU from one or a separate logical channel to the transport block (TB) (eg, 1352 or 1362), the transport delivered from the physical layer on the transport channel (eg, downlink). Partitioning the MAC SDU from a block (TB) into one or a separate logical channel (eg 1352 or 1362), scheduling information reporting (eg on the uplink), error correction through the uplink or HARQ in the downlink (eg,) For example, 1363), and logical channel prioritization on the uplink (eg 1351 or 1361) can be included. The MAC entity can handle a random access process (eg, 1354 or 1364).

FIG. 13 is an exemplary schematic of a RAN architecture that includes one or more base stations. In one example, a protocol stack (eg, RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at the node. The base station (eg, 120A or 120B) is a base station central unit (CU) (eg, gNB-CU1420A or 1420B), and at least one base station distribution unit (eg, gNB-CU1420A or 1420B) when a functional partition is configured. DU) (eg, gNB-DU1430A, 1430B, 1430C, or 1430D) can be included. The upper layer of the base station may be installed in the base station CU, and the lower layer of the base station may be installed in the base station DU. The Fl interface connecting the base station CU and the base station DU (eg, the CU-DU interface) can be an ideal or non-ideal backhaul. Fl-C may provide a control plane connection via the Fl interface, and Fl-U may provide a user plane connection via the Fl interface. In one example, the Xn interface may be configured between base station CUs.

In one example, the base station CU can include an RRC function, a SDAP layer, and a PDCP layer, and a base station DU can include an RLC layer, a MAC layer, and a PHY layer. In one example, the various functional division options between the base station CU and the base station DU are various combinations of upper protocol layers (RAN functions) within the base station CU and lower protocol layers within the base station DU (the lower protocol layer (RAN function)). It may be possible by setting various combinations of RAN functions). Functional partitioning supports flexibility and can move the protocol layer between base station CU and base station DU depending on service requirements and / or network environment.

In one example, functional partitioning options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or with other particle sizes. For each base station CU division, the base station CU may have a fixed division option and the base station DU may be configured to match the division options of the base station CU. For each base station DU division, the base station DU may be configured with different division options, and the base station CU may provide separate division options for different base station DUs. In UE partitioning, the base stations (base station CU, and at least one base station DU) can provide separate partitioning options for separate wireless devices. For each bearer split, separate split options may be available for separate bearers. For each slice splice, separate split options may be applied to separate slices.

FIG. 14 is an exemplary schematic showing the RRC state transition of a wireless device. In one example, the wireless device is in an RRC connected state (eg, RRC connected 1530, RRC_Connected), an RRC idle state (eg, RRC idle 1510, RRC_Idle), and / or an RRC stopped state (eg, RRC stopped 1520, RRC_Inactive). Can be in at least one RRC state. In one example, in the RRC connection state, the wireless device may have at least one RRC connection with at least one base station (eg, gNB and / or eNB), and those base stations are in the UE context of the wireless device. Can have. A UE context (eg, a radio device context) is an access layer context, one or more radio link configuration parameters, a bearer (eg, a data radio bearer (DRB), a signaling radio bearer (SRB), a logical channel, a QoS flow, a PDU session). , And / or similar) Configuration information, security information, PHY / MAC / RLC / PDU / SDAP layer configuration information, and / or similar configuration information for wireless devices. Can be done. In one example, in the RRC idle state, the wireless device may not have an RRC connection with the base station and the UE context of the wireless device may not be stored within the base station. In one example, in the RRC stopped state, the wireless device does not have to have an RRC connection with the base station. The UE context of the wireless device can be stored within a base station, which base station can be referred to as an anchor base station (eg, the final serving base station).

In one example, the wireless device is between the RRC idle state and the RRC connection state in both methods (eg, connection release 1540 or connection establishment 1550, or connection reestablishment) and / or the RRC stop state and RRC connection in both methods. It is possible to transition to the UE RRC state between states (eg, connection stop 1570 or connection resume 1580). In one example, the wireless device can transition its RRC state from the RRC stopped state to the RRC idle state (eg, connection release 1560).

In one example, the anchor base station is the UE context of the radio device at least during a time period during which the radio device remains in the anchor base station's RAN notification area (RNA) and / or the radio device remains in the RRC outage. It can be a base station capable of holding (wireless device context). In one example, the anchor base station may be the base station to which the radio device in the RRC shutdown state was last connected in the most recent RRC connection state, or the radio device was the last base station to internally perform an RNA update procedure. In one example, RNA can include one or more cells operated by one or more base stations. In one example, a base station can belong to one or more RNAs. In one example, the cell may belong to one or more RNAs.

In one example, the wireless device can transition from the RRC connected state to the UE RRC state from the RRC stopped state at the base station. The wireless device can receive RNA information from the base station. RNA information includes at least one of the RNA identifiers, one or more cells of RNA, a base station identifier, a base station IP address, a radio device AS context identifier, a restart identifier, and / or the like. Can be done.

In one example, an anchor base station can broadcast a message (eg, a RAN paging message) to an RNA base station to reach a radio device in an RRC stopped state and / or receive a message from the anchor base station. Base stations send other messages (eg, paging messages) to wireless devices in their base station coverage areas, cell coverage areas, and / or beam coverage areas associated with RNA via air interfaces. Can be broadcast and / or multicast.

In one example, when an RRC-stopped radio device moves into a new RNA, the radio device can perform an RNA update (RNAU) procedure, which procedure is randomized by the radio device and / or the UE context search procedure. You can execute access procedures. The UE context search can include searching for a random access preamble from the radio device by the base station and fetching the UE context of the radio device from the previous anchor base station by the base station. Fetching sends a search UE context request message containing the resume identifier to the previous anchor base station, and receives a search UE context response message containing the UE context of the wireless device from the previous anchor base station. Can include that.

In an exemplary embodiment, the radio device in the RRC stopped state can select camp-on based on at least the measurement results for one or more cells, where the radio device is a base. RNA paging messages from the station and / or core network paging messages can be monitored. In one example, a radio device in the RRC outage state selects a cell to execute a random access procedure to resume the RRC connection and / or sends one or more packets to the base station (eg, to the network). can do. In one example, if the selected cell belongs to a different RNA than the RNA for the radio device in the RRC shutdown state, the radio device can initiate a random access procedure to perform the RNA update procedure. In one example, if the radio device in the RRC outage has one or more packets in the buffer to send to the network, the radio device initiates a random access procedure in the cell of the cell selected by the radio device. One or more packets can be sent to the base station. Random access procedures can be performed between the radio device and the base station with two messages (eg, two stage random access) and / or four messages (eg, four stage random access).

In an exemplary embodiment, the base station that receives one or more uplink packets from the radio device in the RRC shutdown state is from the AS context identifier, RNA identifier, base station identifier, restart identifier, and / or radio device. The UE context of the wireless device can be retrieved by sending a search UE context request message for the wireless device to the anchor base station of the wireless device based on at least one of the received cell identifiers. In response to fetching the UE context, the base station can send rerouting requests for wireless devices to core network entities (eg, AMF, MME, and / or similar). A core network entity is one established for a wireless device between a user plane core network entity (eg, UPF, S-GW, and / or similar) and a RAN node (eg, a base station). The downlink tunnel endpoint identifier for the above bearer can be updated, for example, the downlink tunnel endpoint identifier can be changed from the address of the anchor base station to the address of the base station.

The gNB can communicate with wireless devices over wireless networks that use one or more new wireless technologies. The one or more radio technologies may include at least one of a plurality of technologies relating to the physical layer, a plurality of technologies relating to the medium access control layer, and / or a plurality of technologies relating to the radio resource control layer. An exemplary embodiment that enhances this one or more wireless technologies can improve the performance of the wireless network. An exemplary embodiment can increase system throughput, or transmission data rate. An exemplary embodiment can reduce the battery consumption of the wireless device. An exemplary embodiment can improve the latency of data transmission between the gNB and the wireless device. An exemplary embodiment can improve the network coverage of the wireless network. An exemplary embodiment can improve the transmission efficiency of a wireless network.

In one example, a base station has one or more transmission durations and / or numerology of one or more logical channels (eg, by wireless devices), and / or transmission time intervals (TTIs), such as TTI durations. And / or you can control the mapping to cells. In one example, a base station can configure the maximum transmit duration of each logical channel within multiple logical channels (eg, using RRC). In one example, the maximum transmission duration can correspond to the maximum PUSCH duration. In one example, the maximum transmission duration can match the maximum duration of the transport block. In one example, the transmission duration can be less than or equal to the TTI duration corresponding to the transmission duration. In one example, a configuration parameter for a logical channel can include an information element indicating a maximum transmit duration and / or a maximum PUSCH duration and / or a maximum transport block duration. In one example, the mapping is quasi-static (eg, using RRC configuration), dynamic (eg, using physical layer and / or MAC layer signaling), pre-configuration on wireless devices, hard / soft partitioning, etc. May be. In one example, the wireless device can support multiple TTIs and / or numerology from a single cell. In one example, multiple TTIs and / or numerology, and / or cells can be processed by multiple MAC entities. In one example, multiple TTIs and / or numerology, and / or cells can be grouped (eg, bandwidth, service type / QoS, etc.), and TTI / numerology / cell groups are processed by MAC entities. obtain. In one example, multiple TTIs and / or numerology, and / or cells can be processed by a single MAC entity.

In one example, the network / gNB can constitute one or more numerology and / or TTI durations and / or transmission durations, and / or radio bearers to be mapped to cells. In one example, a MAC entity can support one or more numerology and / or TTI duration and / or transmission duration, and / or cell. In one example, a logical channel can be mapped to one or more numerology, and / or TTI duration and / or transmission duration, and / or cell. In one example, one or more logical channels can be mapped to numerology and / or TTI duration and / or transmission duration, and / or cells. In one example, a HARQ entity can support one or more numerology and / or TTI duration and / or transmission duration, and / or cell.

In one example, a service can be associated with one or more requirements (eg, power consumption, latency, data rate, coverage, etc.). In one example, the base station selects or configures a wireless device to select or configure carriers and / or numerology and / or TTI duration and / or transmission duration so that one or more requirements are met. be able to. For example, high-volume machine-to-machine communication (mMTTC) -based applications may require enhanced network coverage for low mobility UEs and may be deployed in a 6 GHz subband with extended symbol duration. In one example, high speed mobile broadband (eMBB) based applications may require high data rates and can enjoy the wide spectral benefits available in the 6 GHz band described above. In one example, the UE may aggregate multiple carriers and / or PHY numerologies that simultaneously support different service verticals.

In LTE, semi-persistent scheduling (SPS) may be applicable to SpCell (eg, PCell and PSCell). In one example, SpCell does not have to be stopped. In one example, SpCell can manage radio link failure (RLF) procedures and provide stable links for SPS. In one example, scheduling SPS using SpCell can reduce UE complexity through cross-carrier scheduling, DRX, and / or carrier activation / shutdown.

In one example, different services may be considered to support different applications and requirements. In one example, the SPS may be supported by multiple service verticals. In one example, ultra-reliable, low-latency communication (URLLC) -based applications frequently use SPS resources (eg, per symbol, per slot, per subframe, or multiple subframes) to reduce user plane latency. can do. In one example, the eMBB may require SPS support for HD video streaming, VoIP, etc. In one example, mMTC may use SPS for periodic reporting of events. In one example, SPS may be supported for service verticals operating on various carriers. In one example, SPS can be supported on one or more carriers. In one example, the SPS may be supported on the primary carrier.

In LTE, the BSR MAC CE may include the size of the buffer associated with the logical channels of one or more logical channel groups (LCGs). In one example, in LTE, there can be up to four logical channel groups. Logical channel groups can be used to classify various data radio bearers (DRBs) into QoS groups.

In one example, a service vertical can be associated with multiple logical channels. In one example, the LTE BSR mechanism can work for NR if multiple MAC entities consider multiple verticals. In one example, the BSR mechanism may require enhancements for handling multiple service verticals using a single MAC entity. In one example, a service vertical can be associated with one or more QoS groups. The LTE range of the LCG may not be sufficient to indicate the buffer status for various service verticals within the NR.

In one example, the BSR for service verticals can be mapped to a unique resource allocation. In one example, a BSR for a service vertical can be mapped to a HARQ entity. In one example, due to downlink and uplink PDCP protocol data units (PDUs), PDCP replication to more than one logical channel can be used for carrier aggregation, resulting in replicated PDCP PDUs. It can be sent across various carriers.

In one example, numerology may correspond to subcarrier spacing in the frequency domain. In one example, various numerologies may be supported by multiplying the basic subcarrier spacing by an integer N and multiplying. In one example, the TTI duration can correspond to a large number of consecutive symbols in the time domain in one transmit direction.

Different TTI durations can be defined when using different numbers of symbols (eg, corresponding to a minislot, one slot, or several slots in one transmit direction). In one example, a combination of one numerology and one TTI duration can determine how transmission can be done on the physical layer. In one example, which numerology and / or TTI duration the logical channel corresponding to the radio bearer can be mapped to can be configured and reconstructed via RRC signaling. In one example, the mapping is not visible to RLC, for example, the RLC configuration can be per logical channel independent of numerology and / or TTI duration. In one example, the ARQ may operate with a numerology and / or TTI duration in which the logical channel is configured. In one example, a single MAC entity can support one or more numerology and / or TTI durations. In one example, the logical channel prioritization procedure can consider the mapping of one logical channel (LCH) to one or more numerology and / or TTI durations. In one example, HARQ can operate with multiple numerology and TTI durations. In one example, numerological properties that exceed TTI may be visible to the MAC.

In one example, the MAC in the gNB may include a dynamic resource scheduler that allocates physical layer resources for downlinks and uplinks. In one example, given the UE buffer status as well as the QoS requirements for each UE and associated radio bearer, the scheduler can allocate resources between UEs. In one example, the scheduler can allocate resources that take into account radio conditions in the UE, which are performed at the gNB and / or identified through measurements reported by the UE. In one example, the scheduler can allocate radio resources on a TTI basis (eg, one minislot, one slot, or multiple slots). Resource allocation can consist of radio resources (eg, resource blocks). In one example, semi-persistent scheduling (SPS) can be reported. In one example, the UE may skip the UL grant if there is no data in the buffer instead of sending a padding BSR. In one example, the UE may identify a resource by receiving a scheduling (resource allocation) channel. In one example, a measurement report may be required to allow the scheduler to operate both uplink and downlink. These may include transport volumes and measurements in the UE radio environment. In one example, an uplink buffer status report may be needed to provide support for QoS-aware packet scheduling. The uplink buffer status report can refer to the data buffered in the logical channel queue in the UE. The uplink packet scheduler in the eNB can be located at the MAC level. The buffer reporting scheme used in the uplink can be flexible to support different types of data services. Constraints on how often uplink buffer reports are signaled from the UE are specified by the network, and overhead can limit the sending of uplink reports.

In one example, in order to provide the uplink grant to the TTI and / or transmission duration and / or numerology and / or cell, the UE is required to have an uplink grant and TTI and / or numerology and / or It can provide a display of logical channels that are mapped to cells. In one example, a base station may provide an uplink grant corresponding to a default TTI and / or numerology and / or cell after receiving a scheduling request from a wireless device. In one example, the NR scheduling request mechanism can indicate a logical channel or TTI and / or transmission duration and / or numerology in which an uplink grant is required. In one example, the logical channel ID and / or the logical channel group ID, and / or the TTI and / or transmission duration and / or numerology, may be provided by the wireless device, along with a scheduling request. In one example, the scheduling request resource can be for a given TTI and / or transmission duration and / or numerology, or for one or more (eg, group) logical channels. In one example, the NR scheduling request can indicate a TTI and / or transmission duration and / or numerology in which an uplink grant is required.

In one example, wireless link failure can occur with more than one carrier. In one example, the radio link failure can occur on the primary carrier and one or more non-primary carriers unaffected by the RLF can perform one or more primary carrier operations / procedures. In one example, the connection reestablishment procedure can resume connection to one of the secondary carriers, if available.

In one example, various TTIs and / or transmission durations may be configured for NRs (eg, one or more symbols, one or more minislots, one or more slots). In one example, eMBB traffic can be preempted by URLLC transmission. In one example, the gNB MAC can dynamically schedule physical layer resources for downlinks and uplinks. The gNB scheduler can allocate resources, taking into account the traffic volume and QoS requirements of the UE and associated radio bears. In one example, the gNB scheduler can allocate resources taking into account the radio conditions of the UE that are performed on the gNB and / or identified through the measurements reported by the UE.

In one example, radio resource allocation may be appropriate for TTI (eg, one or more symbols, one or more minislots, one or more slots) (or may indicate resources for it). In one example, radio resource allocation can indicate resources for multiple TTIs. This resource allocation can include displaying radio resources (eg, resource blocks). In one example, in the downlink, the gNB can anticipate existing resource allocations to fit latency critical data. In one example, the UE can identify a resource by receiving a scheduling (resource allocation) channel. In one example, measurement reports allow the scheduler to operate on uplinks and downlinks. The measurement can include the amount of transport and the measured value of the UE radio environment.

In one example, the uplink buffer status report can provide support for QoS-aware packet scheduling. In one example, the uplink buffer status report can refer to the data buffered in the UE's logical channel queue. In one example, the uplink packet scheduler in gNB can be located at the MAC level. In one example, the buffer status reporting scheme used in the uplink can be flexible to support different types of data services. In one example, constraints on how often uplink buffer reports are signaled from the UE can be configured in the UE by the network / gNB to limit overhead.

In LTE, scheduling requests (SRs) can be used to request UL-SCH resources for new transmissions if the UE does not have the proper grants. In one example, if the SR resource is not configured for the UE, the UE can invoke a random access procedure to receive the uplink scheduling grant. In LTE, the SR can include 1-bit information, indicating that the UE needs an uplink grant. In one example, for 1-bit SR reception, the gNB has which logical channel (associated with a particular QCI) has the amount of data available for transmission, or data available for transmission on the UE. You don't have to know. In one example, gNB can indicate numerology and / or transmission duration and / or TTI duration in grants. In one example, the UE can indicate the desired numerology and / or transmission duration and / or TTI duration to the gNB.

In one example, the SR and / or BSR reports the UE buffer status of one or more logical channels and / or logical channel groups (priority and / or buffer size) and / or numerology / TTI duration / transmit duration. can do. In one example, the SR can indicate the type of LCG that has the available data and / or the amount of available data associated with the LCG. In one example, by indicating the amount of data available associated with an LCG that requires a grant in the UE, the gNB provides the UE with a suitable grant size for the preferred numerology / TTI duration / transmission duration. can do. In one example, BSR grantless transmission without SR transmission may be supported to avoid delays caused by BSR grant allocation.

In one example, the grantless transmission mechanism can be used for delayed critical use cases such as URLLC. In one example, UE-specific resource allocation can be used in the case of BSR transmission. In one example, if ungrant transmission is supported, the wireless device can transmit BSRs per logical channel and / or per logical channel group and / or per short BSR. In one example, a buffer status report for high priority traffic can be sent using a grantless channel. In one example, the ungranted resource allocated per UE can be used only for the transmission of BSRs. In one example, the ungranted resources allocated per UE can be used only for BSR and data transmission. In one example, a grantless resource can be used to transmit data if there is no BSR waiting to be transmitted.

In LTE, the UE can send a BSR if there is new data available in the buffer that has a higher priority than the existing data, whereas the new data is the same as the existing data. , Or have a lower priority, the UE may not be allowed to send BSRs. This can cause an information mismatch between the UE and the gNB, resulting in a long unwanted scheduling delay before the UE can empty its transmit buffer.

In one example, the UE may send a BSR when new data is no longer relevant to its priority. In one example, the gNB can configure the UE to send a BSR when new data becomes available regardless of its priority.

An exemplary uplink scheduling procedure in LTE is shown in FIG. In one example, a scheduling request (SR) can be used to request a UL-SCH resource for a new transmission. In one example, an SR can be triggered if a normal buffer status report (BSR) is triggered and the UE does not have at least the resources to send to that normal BSR. In one example, a normal BSR can be triggered when data becomes available for transmission over the uplink.

In one example, in LTE, the SR can be transmitted over a physical uplink control channel (PUCCH) and can be configured with one bit to save control channel overhead. SR can be used to notify the eNB that new data exists in one or more buffers associated with the UE's logical channel. The eNB can schedule some resources and, after the SR is received, can show it to the UE in downlink control information (DCI) as an uplink grant. The UE can send a BSR on the uplink grant if the logical channel buffer is not empty, and the eNB can schedule the UE with new resources.

In one example, the NR can support various service requirements such as eMBB, URLLC, etc. Uplink data can have important delay requirements (eg, URLLC). In one example, the gNB may need to know the requirements for such efficient scheduling, because eMBB and URLLC can have various physical layer scheduling procedures and channel structures.

In one example, a multi-bit scheduling request (SR) can be configured for wireless devices. In one example, a UE-specific SR size and / or resource may be configured. In one example, different UEs may have services with different QoS requirements. In one example, a combination of SR and BSR may be used for one or more services (eg, having a high data rate such as eMBB). In one example, a UE with delayed critical services and small packets can be configured with multi-bit SR to indicate the buffer size. The network / gNB can schedule grants of appropriate size so that all data can be transmitted in one round of signaling. In one example, the mapping can be configured between the size of SR and the type of service requested by the UE. In one example, using SR and / or BSR, and / or a combination of SR and BSR, the network / gNB can assign a TTI transmission duration / numerology suitable for the service required by the UE. In one example, depending on the type of service, certain values with different SRs may indicate different buffer sizes for that service.

In one example, the network / gNB can use RRC configuration and / or dynamic signaling (eg, PHY and / or MAC signaling) to enable BSR and / or SR (eg, 1-bit SR or multi-bit SR) / Can be impossible. In one example, the trigger condition for the BSR can be changed depending on whether the network / gNB has enabled SR (eg, multi-bit SR) in the UE. In one example, if a multi-bit SR is configured, the BSR may be disabled or the trigger conditions may change.

In one example, grantless transmission of BSR can be configured. In one example, the network / gNB may preconfigure resources for transmitting grantless BSRs.

In one example, the SR can include multiple bits. In one example, the SR can provide information about one or more logical channels and / or logical channel groups for the UE to need a grant, and / or TTI / transmission duration / numerology. In one example, the multi-bit SR can indicate the type of LCG having available data and / or the amount of available data associated with the LCG. In one example, the periodicity of SR resources can be shorter for URLLC data that supports fast scheduling. In one example, the SR resource can be application type specific and / or the SR transmission (eg SR resource) indicates the type of grant predicted by the UE (eg TTI / numerology). be able to.

In one example, in LTE, a normal BSR can be triggered when new data becomes available, which is the priority of the logical channel that belongs to any LCG and the data is already available for transmission. Either it belongs to a logical channel with a higher priority, or there is no data available for transmission on any logical channel that belongs to LTE. In one example, in LTE, the UE does not have to trigger the BSR if the new data has the same or lower priority than the existing data.

In one example, in LTE, the BSR MAC control element has a short / truncated BSR format with one LCG ID field and one corresponding buffer size field, and a long with four LCG IDs and corresponding buffer size fields. BSR format can be included. In one example, a logical channel can be mapped to a numerology / TTI duration based on one or more criteria (eg, UE capability, service requirements, QoS, ...).

In one example, the ungranted uplink resource can be dedicated for the UE. In one example, if a dedicated non-grant resource is assigned to the UE and the non-grant resource is high enough frequency / density to meet the latency requirement, then the UE requests the resource for the data and BSR from the SR. It doesn't have to be necessary. In one example, the ungranted resources assigned to the UE can be contention-based. In one example, the ungranted resources assigned to the UE may not be dense enough to meet the URLLC's ultra-low latency requirements. In one example, the UE may require an SR procedure to support URLLC. In one example, the SR can provide information about the data wait state on the UE.

In one example, the gNB can group logical channels into one or more logical channel groups (LCGs) in the UE, and the UE can report the buffer status of one or more LCGs. In one example, the UE can report the buffer status for each logical channel. In one example, the gNB can group logical channels into one or more logical channel groups (LCGs) in the UE. The UE can report the buffer status of one or more LCGs and / or one or more logical channels (eg, URLLC logical channels).

In one example, gNB can show a mapping between one or more logical channels and one or more numerology and / or TTI duration and / or transmission duration. In one example, one or more logical channels can be mapped to numerology and / or TTI duration and / or transmission duration. In one example, the UE can report the buffer status by numerology / TTI duration / transmission duration.

In one example, in NR, the UE can multiplex data from a subset of logical channels into a MAC PDU (eg, for better support of QoS). In one example, one MAC PDU can consist of data from one or more logical channels (eg, having the same QoS). In one example, the gNB can include only one logical channel within the LCG. In one example, only logical channels with the same QoS can be grouped into one LCG. In one example, in NR, the BSR can support fine-grained scheduling, such as per-logical channel or per-QoS scheduling.

In one example, the UE can report the amount of PDCP data and the amount of RLC data separately when reporting the buffer status. Having separate PDCP data volumes allows the scheduler, eg, eNB / gNB, to allocate uplink resources without the close coordination of having general principles for scheduling PDCP data. In one example, reporting the amount of PDCP data separately can be advantageous in the case of multi-split bearers. For example, in the case of a multi-split bearer, some eNB / gNB can mainly supply the multi-split bearer in order to avoid wasting resources. In this case, reporting the amount of PDCP data to only a few eNBs / gNBs may reduce coordination efforts.

In one example, a logical channel can be mapped to one or more numerology and / or TTI duration / transmission duration. In one example, the ARQ can be performed with respect to numerology and / or TTI duration to which the logical channel (LCH) can be mapped. In one example, the RLC configuration can be per logical channel, independent of numerology / TTI length. In one example, the mapping of logical channels to numerology / TTI lengths can be reconstructed via RRC reconstruction. In one example, HARQ retransmissions can be performed over various numerology and / or TTI durations. In one example, the HARQ composition can be numerology / TTI duration specific.

In one example, a MAC entity can support one or more numerology / TTI duration / transmission duration. In one example, logical channel prioritization (LCP) considers the mapping of logical channels to one or more numerology / TTI durations. In one example, in NR, the first BSR format may be associated with the URLLC service and the second BSR format may be associated with the eMBB or mMTC service. In one example, the first SR format may be associated with a larger grant size request and the second SR format may be used for a smaller grant size request. In one example, the BSR can support reporting the number of LCG and / or LC selections to the gNB. In one example, the NR can support dynamic scheduling, semi-persistent scheduling, and grantless uplink transmission. In one example, the scheduling function can support dynamic and quasi-static switching between resources corresponding to various numerology of the UE.

In one example, the wireless device is from one or more base stations (eg, one or more NR gNBs and / or one or more LTE eNBs, and / or one or more eLTE eNBs, etc.). One or more messages can be received, including Radio Resource Configuration (RRC) messages. In one example, one or more messages can include configuration parameters for multiple logical channels. In one example, one or more messages can include a logical channel identifier for each of the plurality of logical channels. In one example, the logical channel identifier can be one of a plurality of logical channel identifiers. In one example, multiple logical channel identifiers can be preconfigured. In one example, the logical channel identifier can be one of a plurality of consecutive integers.

In one example, a plurality of logical channels configured for a wireless device may correspond to one or more bearers. In one example, there may be a one-to-one mapping / correspondence relationship between the bearer and the logical channel. In one example, there can be a one-to-many mapping / correspondence between one or more bearers and one or more logical channels. In one example, the bearer can be mapped to multiple logical channels. In one example, data from a packet data convergence protocol (PDCP) entity corresponding to a bearer can be replicated and mapped to multiple radio link control (RLC) entities and / or logical channels. In one example, scheduling of multiple logical channels can be performed by a single medium access control (MAC) entity. In one example, scheduling of multiple logical channels can be performed by more than one MAC entity. In one example, a logical channel can be scheduled by one of a plurality of MAC entities. In one example, one or more bearers can include one or more data radio bearers. In one example, one or more bearers can include one or more signaling radio bearers. In one example, one or more bearers can accommodate one or more applications and / or quality of service (QoS) requirements. In one example, one or more bearers can accommodate ultra-reliable low-latency communication (URLLC) applications and / or high-speed, high-capacity (eMBB) and / or mass-machine communication (mMTTC) applications.

In one example, the first logical channel of the plurality of logical channels can be mapped to one or more of the plurality of transmission time intervals (TTIs) / transmission duration / numerology. In one example, a logical channel may not be mapped to one or more of multiple TTIs / transmission durations / numerology. In one example, the logic channel corresponding to the URLLC bearer can be mapped to one or more first TTIs / transmission durations, and the logic corresponding to the eMBB application can be mapped to one or more second TTIs / transmission durations. It can be mapped and the one or more first TTI / transmission duration can have a shorter duration than the one or more second TTI / transmission duration. In one example, multiple TTIs / transmission duration / numerology can be preconfigured in a wireless device. In one example, one or more messages can include multiple TTI / transmission duration / numerology configuration parameters. In one example, a base station may transmit a grant to a wireless device, which includes a cell and / or TTI / transmission duration / numerology display to which the wireless device can transmit data. In one example, the first field of the grant can indicate a cell and the second field of the grant can indicate TTI / transmission duration / numerology. In one example, a field within a grant can indicate both a cell and TTI / transmission duration / numerology.

In one example, one or more messages can include a logical channel group identifier for one or more of a plurality of logical channels. In one example, one or more of the plurality of logical channels may be assigned the logical channel group identifier n, eg, 0 ≦ n ≦ N (eg, N = 3, or 5, or 7, or 11, or 15, etc.). Is. In one example, one or more of a plurality of logical channels having a logical channel group identifier may be mapped to the same one or more TTI / transmission duration / numerology. In one example, one or more of a plurality of logical channels having a logical channel group identifier can only be mapped to the same one or more TTI / transmission duration / numerology. In one example, one or more of the multiple logical channels may accommodate the same application and / or QoS requirements. In one example, one or more first logical channels may be assigned a logical channel identifier (s) and a logical channel group identifier (s), and one or more second logical channels may be assigned a logical channel identifier (s). Multiple) can be assigned. In one example, a logical channel group may consist of one logical channel.

In one example, one or more messages can include a mapping between multiple logical channels and multiple TTIs / transmission durations / numerology and / or one or more first fields indicating cells. .. In one example, one or more first fields indicate that the logical channel is mapped to one or more first TTI / transmission durations that are shorter or equal to the first value. Can contain values. In one example, one or more first fields indicate that the logical channel is mapped to one or more second TTI / transmission durations that are longer or equal to the second value. Can contain values. In one example, one or more first fields can include and / or indicate one or more TTI / transmission duration / numerology and / or cells to which the logical channel is mapped. In one example, the mapping can be shown using one or more bit mappings. In one example, if the value of the bitmap associated with the logical channel is 1, it can indicate that the logical channel is mapped to the corresponding TTI / transmission duration / numerology and / or cell. In one example, if the value of the bitmap associated with the logical channel is zero, it can indicate that the logical channel is not mapped to the corresponding TTI / transmission duration / numerology and / or cell. In one example, one or more messages can include configuration parameters for multiple logical channels. In one example, a configuration parameter for a logical channel can include a bitmap associated with the logical channel, which is the mapping between the logical channel and multiple TTIs / transmission durations / numerology. , And / or indicates a cell.

In one example, the first logical channel may be assigned at least the first logical channel priority. In one example, the first logical channel may be assigned one or more logical channel priorities for one or more TTI / transmission duration / numerology. In one example, the first logical channel may be assigned a logical channel priority for each of multiple TTIs / transmission durations / numerology. In one example, a logical channel may be assigned a logical channel priority for each of one or more of multiple TTIs / transmission durations / numerology. In one example, a logical channel may be assigned a logical channel priority for each of one or more TTIs / transmission durations / numerology, and the logical channels may be assigned each of one or more TTIs / transmission durations / numerology. Is mapped with respect to. In one example, one or more messages can include one or more second fields that indicate the priority of the logical channel for one or more TTI / transmission duration / numerology. In one example, one or more second fields can include one or more sequences that indicate the priority of the logical channel for one or more TTI / transmission duration / numerology. In one example, one or more second fields can contain multiple sequences for multiple logical channels. The sequence corresponding to the logical channel indicates the priority of the logical channel for one or more of multiple TTIs / transmission duration / numerology / cells or multiple TTIs / transmission duration / numerology / cells. Can be done. In one example, the priority can indicate a mapping between a logical channel and one or more TTIs / transmission durations / numerology. In one example, the priority of a logical channel with a given value for TTI / numerology (eg, zero, or minus infinity or a negative value) indicates that the logical channel is not mapped to TTI / numerology. be able to. In one example, the size of the sequence can be variable. In one example, the size of the sequence associated with the logical channel can be the number of TTIs / transmission duration / numerology to which the logical channel is mapped. In one example, the size of the sequence can be fixed, for example, to TTI / transmission duration / numerology / number of cells.

Wireless device buffer status reports provide base stations with information for efficient scheduling of wireless devices, as well as enhanced air interface throughput, latency, and performance. The wireless device responds to the wireless device having the uplink grant and the buffer status report in the waiting state and sends it to the buffer status report base station. The wireless device triggers a buffer status report in response to one or more events. For example, in LTE, a buffer status report is triggered when data arrives at a logical channel and the logical channel has a higher priority than other logical channels with available data. In one example, in the new radio (NR) radio access technology, a logic channel can be mapped to multiple TTIs / transmission durations / numerologists / cells and can have at least one logic channel priority. In one example, a logical channel can have multiple logical channel priorities (eg, for multiple TTIs / transmission duration / numerology / cells). Existing BSR triggering mechanisms do not have to trigger BSR in some exemplary scenarios when BSR is required, and / or, as a result, send BSR in some other scenarios. Can result in excessive triggering. An efficient buffer status reporting procedure is that the wireless device is scheduled to transmit data in a timely manner and with the appropriate grant (eg, appropriate size, TTI / transmission duration / numerology). Required to ensure. Inefficient BSR procedures cause degradation for wireless devices and network performance, especially for delay-sensitive applications. Methods and systems for triggering buffer status reports in wireless networks need to be enhanced. An exemplary embodiment employs and schedules one or more TTI / transmission duration / logical channel mappings and / or priorities for numerology when triggering a buffer status report for a wireless device. Improve efficiency and wireless device and wireless network performance, such as throughput and latency.

In an exemplary embodiment, the MAC entity can trigger a Buffer Status Report (BSR) when uplink data becomes available in the uplink buffer associated with the first logical channel. One logical channel is one or more TTIs / transmission durations / numerology TTIs / transmissions rather than one or more priorities for TTI / transmission duration / numerology of one or more selected logical channels. Having a higher priority for duration / numerology, the selected one or more logical channels will be assigned if the one or more logical channels are mapped to at least TTI / transmission duration / numerology. It has been selected. In one example, the uplink buffer associated with the first logical channel is the uplink buffer associated with the wireless link control (RLC) entity and / or the packet data convergence protocol associated with the first logical channel ( PDCP) can be an entity. In one example, the wireless device can receive uplink grants from the base station that include transmit parameters (eg, transmit time / resources, MCS, HARQ parameters, power control commands, etc.). In one example, the wireless device can use the resources provided by the grant to transmit the BSR to the base station. In one example, the uplink buffer can be empty when the uplink data becomes available. In one example, the uplink buffer can contain one or more uplink packets when the uplink data becomes available.

In one example, the BSR can include the buffer status of multiple logical channels. In one example, the BSR can include the buffer status of one or more groups of multiple logical channels. In one example, the BSR can include the buffer status of one or more first logical channels and the buffer status of one or more first groups of multiple logical channels. In one example, the BSR is the buffer status of one or more first logical channels corresponding to one or more first application types (eg, URLLC and / or mMTC), and one or more second applications. It can include the buffer status of one or more first groups of multiple logical channels corresponding to the type (eg, eMBB). In one example, a base station can configure a wireless device using one or more of a plurality of BSR formats. In one example, multiple BSR formats may be preconfigured in the wireless device. In one example, the first BSR format can include the buffer status of multiple logical channels. In one example, the second BSR format can include the buffer status of one or more groups of multiple logical channels. In one example, the third BSR format can include the buffer status of one or more first logical channels and the buffer status of one or more first groups of multiple logical channels.

In one example, the BSR can be one of a short format, a long format, and / or other formats. In one example, the BSR can have a variable size. In one example, the size of the BSR may depend on at least one of a first number of logical channels with available data and / or a second number of logical channels with available data. In one example, the variable size BSR format can include a display of logical channels (s) and / or logical channel groups (s) whose buffer status is contained within the BSR. In one example, the display can be one or more bitmaps. In one example, a value of 1 in one or more bitmaps can indicate that the corresponding logical channel and / or logical channel group is included in the BSR. In one example, a value of zero in one or more bitmaps can indicate that the corresponding logical channel and / or logical channel group is not included in the BSR. In one example, the variable size BSR format can accommodate MAC subheaders that do not have a length field (eg, fixed size MAC subheaders that do not have a length (L) field) and display the BSR size on the BSR (for example, For example, it can contain one or more bitmaps and / or other displays). In one example, the variable size BSR format can correspond to a MAC subheader with a length field (eg, a variable size MAC subheader with a length (L) field). In one example, the L field can indicate the number of logical channels and / or logical channel groups whose buffer status is contained within the BSR. In one example, the L field can indicate the number of octets within the BSR. In one example, the BSR comprises one or more logical channel identifiers and / or one or more logical channel group identifiers, and buffer statuses corresponding to one or more logical channels and / or one or more logical channel groups. be able to.

In an exemplary embodiment, the wireless device may receive one or more messages including a logical channel identifier for each of the plurality of logical channels, with the first logical channel of the plurality of logical channels being plural. Maps to one or more of the transmission time intervals (TTI) / transmission duration / numbology of transmission time interval (TTI) / transmission duration / numbology and assigns at least one first logical channel priority. Be done. An example is shown in FIG. In one example, a MAC entity can trigger a buffer status report (BSR) when uplink data becomes available for the uplink buffer associated with the first logical channel, the first logic. The channel is a TTI / transmission duration / numerology of one or more TTIs / transmission durations / numerology rather than one or more priorities of one or more selected logical channels. Having a higher priority over transmit duration / numerology, one or more selected logical channels will have one or more logical channels mapped to at least its TTI / transmit duration / numerology. Be selected. In one example, the uplink buffer associated with the first logical channel is the uplink buffer associated with the wireless link control (RLC) entity and / or the packet data convergence protocol associated with the first logical channel ( PDCP) can be an entity. In one example, the wireless device can receive uplink grants from the base station that include transmit parameters (eg, transmit time / resources, MCS, HARQ parameters, power control commands, etc.). In one example, the wireless device can use the resources provided by the grant to transmit the BSR to the base station. In one example, the uplink buffer can be empty when the uplink data becomes available. In one example, the uplink buffer can contain one or more uplink packets when the uplink data becomes available.

In the case of Example 1 of FIG. 16, logical channels are assigned a priority and mapped to one or more transmission durations. In one example, the data will be available in the buffer associated with LC3. The LC3 can be mapped to one or more first transmission durations and one or more second transmission durations. In one example, the LC3 can have a higher priority than the other logical channels mapped to one or more first transmission durations. In one example, the LC3 can have a higher priority than other logical channels that have available data mapped to one or more first transmission durations. In one example, the LC3 can have a higher priority than other logical channels with available data mapped to one or more first transmission durations, but one or more second transmissions. It cannot have a higher priority than other logical channels mapped to duration. The wireless device responds to the data that becomes available to the LC3 and to the LC3 that has a higher priority than the logical channel having the availability mapped to one or more first transmission durations. The BSR can then be triggered or in response to an LC3 that has a higher priority than a logical channel that has available data mapped to one or more second transmission durations. In the case of Example 2 of FIG. 16, the logical channel can have priority in one or more TTIs / first transmission duration / numerology. In one example, a logical channel priority of zero for TTI transmission duration / numerology can indicate that the logical channel is not mapped to TTI / transmission duration / numerology. The logical channel is each TTI / transmission duration / numerology to which the logical channel is mapped (for example, in FIG. 16, the first TTI (s) / transmission duration (s) / numerology (s). , And the second first TTI (s) / transmission duration (s) / numerology (s)) can be prioritized. If LC2 and LC4 have data available in their associated buffers and the data becomes available for the buffer associated with LC3, it is the first TTI (s) / transmission persistence. Has higher priority for time (s) / numerology (s) (but not higher for second TTI (s) / transmission duration (s) / numerology (s)) Therefore, the wireless device can trigger the BSR.

In an exemplary embodiment, the wireless device comprises one or more fields indicating the priority of one or more transmission time intervals (TTIs) / transmission duration / numerology of one or more logical channels. The above message can be received. In one example, the TTI / transmission duration / numerology logic channel priority can indicate whether the logic channel can be mapped to TTI / transmission duration / numerology. In one example, a zero or minus infinity value or negative value for the logical channel priority can indicate that the logical channel is not mapped to TTI / transmission duration / numerology. In one example, one or more messages can include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. In one example, a MAC entity reports a buffer status when uplink data becomes available for an uplink buffer associated with a logical channel and for at least one TTI / transmission duration / numbology. (BSR) can be triggered and the logical channel has a higher priority than the priority of one or more first logical channels with available data. In one example, the uplink buffer associated with a logical channel can be an uplink buffer associated with a wireless link control (RLC) entity and / or a packet data convergence protocol (PDCP) entity associated with a logical channel. .. In one example, the wireless device can receive uplink grants from the base station that include transmit parameters (eg, transmit time / resources, MCS, HARQ parameters, power control commands, etc.). In one example, the wireless device can use the resources provided by the grant to transmit the BSR to the base station. In one example, the uplink buffer can be empty when the uplink data becomes available. In one example, the uplink buffer can contain one or more uplink packets when the uplink data becomes available.

In an exemplary embodiment, the wireless device comprises one or more fields indicating the priority of one or more transmission time intervals (TTIs) / transmission duration / numerology of one or more logical channels. The above message can be received. In one example, the TTI / transmission duration / numerology logic channel priority can indicate whether the logic channel can be mapped to TTI / transmission duration / numerology. In one example, a zero or minus infinity value or negative value for the logical channel priority can indicate that the logical channel is not mapped to TTI / transmission duration / numerology. In one example, one or more messages can include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. In one example, the MAC entity can trigger a buffer status report (BSR) taking into account the priority of one or more logical channels on the first TTI / transmission duration / numerology. In one example, the first TTI / transmission duration / numerology can be preconfigured in a wireless device and / or can be the default TTI / transmission duration / numerology. In one example, the default TTI / transmission duration / numerology can be LTE TTI / transmission duration / numerology. In one example, one or more messages can include configuration parameters for a first TTI / transmission duration / numerology. In one example, the wireless device can receive uplink grants from the base station that include transmit parameters (eg, transmit time / resources, MCS, HARQ parameters, power control commands, etc.). In one example, the wireless device can use the resources provided by the grant to transmit the BSR to the base station.

In an exemplary embodiment, the wireless device may receive one or more messages containing one or more fields indicating the priority of the one or more logical channels, the priority of which is relative to the wireless device. It is independent of the plurality of transmission time intervals (TTI) / transmission duration / numerology configured in the above, for example, a logical channel can have one priority for multiple TTI / numerology. In one example, a MAC entity can trigger a buffer status report (BSR) that considers priority. The wireless device can receive a grant for transmission on the TTI transmission duration / numerology. The wireless device can transmit a BSR for TTI / transmission duration / numerology.

In an exemplary embodiment, as shown in FIG. 17A, the wireless device can receive configuration parameters for multiple logical channels. The plurality of logical channels can include a first plurality of logical channels including the first logical channel. In one example, the first logical channel can have a first logical channel priority. In one example, the configuration parameter can indicate the logical channel priority for multiple logical channels. In one example, the first logical channel can be mapped to one or more first transmission durations. In one example, uplink data may be available for the first logical channel. In one example, the first plurality of logical channels within the plurality of logical channels may have uplink data in their associated buffers. In one example, the wireless device can trigger a buffer status report in response to the uplink data available to the first logical channel of the first plurality of logical channels having the uplink data. The logical channel priority of is higher than one or more priorities of one or more selected logical channels. In one example, the selected logical channel may be selected in response to being mapped to one or more transmission durations, and the first logical channel is mapped. For example, in FIG. 17A, the logical channels LC1, LC2, LC3, LC4, and LC5 are configured for the wireless device, with priorities 5, 4, 3, 1, and 2, respectively. In one example, the higher the configured priority value, the lower the priority. For example, in this example, the LC4 with the configured priority 1 has the highest logical channel priority and the LC1 with the configured priority 5 has the lowest logical channel priority. In this example, the data will be available for LC3. The LC3 is mapped to one or more first transmission durations and one or more second transmission durations, and the logical channels with uplink data are LC1, LC3, and LC5. The LC3 has a higher logical channel priority among the logical channels having uplink data mapped to one or more first transmission durations. The wireless device triggers a buffer status report, but LC3 does not have the highest priority among the logical channels with available data (eg LC3 has a lower priority than LC2). .. In contrast, if all logical channels are mapped to the same transmit duration (eg, as shown in FIG. 17B), then the LC3 has the uplink data mapped to the transmit duration. The wireless device does not trigger a buffer status report because it does not have the highest priority among them.

In one example, a base station can group a plurality of logical channels into one logical channel group. In an exemplary configuration, the logical channel mapping to at least one TTI / transmission duration / numerology can differ from the various logical channels within the logical channel group. The BSR cannot provide information about resources that request or buffer data that can be mapped to various TTIs / numerologies.

Information about the buffer status of the logical channel group cannot provide the base station with the appropriate information to provide a grant for proper TTI / transmission duration / numerology for the wireless device. In the case of Example 1 of FIG. 18, when the logical channels 1 (LC1) and LC2 are in the logical channel group (LCG1), the base station has a buffer (plurality) in which the data reported by the BSR for the LCG1 is associated with the LC1. I don't know if it's because of (possible) or because of the buffer (s) associated with the LC2. The BS is the appropriate TTI / transmission duration / numerology (eg, first TTI (s) / transmission duration (s) / numerology (s), or second TTI (s) / Grants for transmission duration (s) / numerology (s)) cannot be sent. For example, the LC2 can have data in the buffer associated with LC2, and the LC1 cannot have data in the buffer associated with LC1. The base station can transmit the grant associated with the second TTI (s) / transmission duration (s) / numerology (s), but the grant is effective for LC2 transmission. impossible. Enhanced logical channel grouping by base station and / or radio device operation (eg, in buffer status reporting) may be necessary for efficient scheduling and / or improved user performance. An exemplary embodiment enhances radio device operation in buffer status reporting in response to base station logical channel grouping and / or base station logical channel grouping.

In an exemplary embodiment, the wireless device comprises one or more first fields that indicate a mapping between one or more logical channels and one or more TTIs / transmission durations / numerology. Message can be received. In one example, one or more messages can include one or more RRC messages. In one example, one or more messages can include configuration parameters for one or more logical channels. In one example, one or more messages can include one or more second fields indicating one or more logical channel groups to which one or more logical channels belong, and each logical channel group has one or more. Each of one or more of the first logical channels is only mapped to one or more first TTIs / transmission durations / numerology. The base station can map the logical channels within the group to the same at least one TTI / transmission duration / numerology. In an exemplary embodiment, the BS may not be configurable / feasible to configure Example 1 of FIG. The base station may be configurable / feasible to configure Example 2 of FIG.

In one example, a MAC entity can trigger a buffer status report (BSR) when one or more first conditions occur. In one example, the wireless device can receive grants for transmission regarding TTI / transmission duration / numerology. In one example, the wireless device can transmit a BSR for TTI / transmission duration / numerology. In one example, one or more first conditions can include data that becomes available for logical channels belonging to a logical channel group, and one or more other logical channels belonging to a logical channel group are empty. Has a buffer of. In one example, one or more first conditions are logics having a higher priority (eg, in at least one TTI / transmission duration / numerology) than the priority of other logic channels with available data. It can contain data that will be available for the channel. Other examples of one or more of the first conditions may be provided.

In an exemplary embodiment, the wireless device comprises one or more first fields that indicate a mapping between one or more logical channels and one or more TTIs / transmission durations / numerology. Message can be received. In one example, one or more messages can include one or more RRC messages. In one example, one or more messages can include configuration parameters for one or more logical channels. In one example, one or more messages can include a logical channel identifier for each of the one or more logical channels. In one example, one or more messages can include one or more second fields indicating one or more logical channel groups to which one or more logical channels belong. In one example, one or more messages can include a logical channel group identifier for one or more first logical channels of one or more logical channels. In one example, a MAC entity can trigger a buffer status report (BSR) when one or more first conditions occur. In an exemplary embodiment, a logical channel configuration similar to that of Example 1 in FIG. 18 may be enabled and / or implemented. In one example, at least two first logical channels with the same logical channel group identifier can be mapped to at least one different first TTI / transmission duration numerology. In one example, the wireless device can separately report the buffer status of each of at least two first logical channels in the BSR. In one example, the wireless device can report the buffer status of each logical channel in its group separately in the BSR. In one example, the wireless device can receive grants for transmission regarding TTI / transmission duration / numerology. In one example, the wireless device can transmit a BSR for TTI / transmission duration / numerology. In one example, one or more first conditions can include data that becomes available for logical channels belonging to a logical channel group, and one or more other logical channels belonging to a logical channel group are empty. Has a buffer of. In one example, one or more first conditions are logics having a higher priority (eg, in at least one TTI / transmission duration / numerology) than the priority of other logic channels with available data. It can contain data that will be available for the channel. Other examples of one or more of the first conditions may be provided.

In one example, data for one or more logical channels may be available and the wireless device may continue to receive grants for TTI / transmission duration / numerology where one or more logical channels cannot be mapped. it can. Wireless devices may not receive unique grants (eg, grounds to which one or more logical channels can be mapped) that lead to delayed and inefficient operation for one or more applications. Enhanced BSR triggering is needed to improve the performance of wireless devices. An exemplary embodiment enhances the BSR triggering conditions in the wireless device.

In an exemplary embodiment, the wireless device carries one or more messages that include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. Can be received. In one example, the wireless device can receive grants for transmission regarding TTI / transmission duration / numerology. The wireless device has no data in the buffer (s) associated with the logical channel (s) mapped to TTI / transmission duration / numerology (eg, the buffer is empty, the amount of data is empty). In response to (less than a certain value), the BSR can be transmitted / triggered on the TTI / transmission duration / numerology that employs the grant. At least one of the one or more logical channels can contain data that is not mapped to TTI / transmission duration / numerology.

In an exemplary embodiment, the wireless device carries one or more messages that include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. Can be received. In one example, the wireless device can receive grants for transmission regarding TTI / transmission duration / numerology. In one example, if the wireless device has data on at least one logical channel that cannot be mapped to TTI / transmission duration / numerology, grant reception triggers a BSR.

In an exemplary embodiment, the wireless device carries one or more messages that include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. Can be received. In one example, one or more messages can include configuration parameters for the timer. In one example, the wireless device can start a timer in response to data that becomes available for at least one of one or more first logical channels. The wireless device can abort the timer if the BSR is triggered while the timer is running. The wireless device can trigger the BSR when the timer expires. In one example, one or more messages can include one or more configuration parameters for one or more first logical channels and / or display of one or more first logical channels. In one example, one or more first logical channels can be associated with one or more delay critical bearers (eg, URLLC). The wireless device can receive grants in terms of TTI / transmission duration / numerology. The wireless device can transmit a BSR for TTI / transmission duration / numerology. In one example, if the wireless device receives a TTI / transmission duration / numerological uplink grant to which one or more first logical channels are mapped, the wireless device may abort the timer. .. In one example, if the wireless device receives a TTI / transmission duration / numerological uplink grant in which one or more first logical channels are not mapped to the BSR and can trigger the BSR, then wireless The device can abort the timer. In one example, if the wireless device receives an uplink grant on TTI / transmission duration / numerology in which one or more first logical channels are mapped to the BSR and can trigger the BSR, the wireless device , The timer can be stopped. In one example, if the wireless device receives an uplink grant for TTI / transmission duration / numerology to which at least one of one or more first logical channels is mapped, the wireless device aborts the timer. can do. In one example, the wireless device receives an uplink grant for TTI / transmission duration / numerology in which at least one of the one or more first logical channels is not mapped to the BSR and can trigger the BSR. If so, the wireless device can abort the timer. In one example, the wireless device receives an uplink grant for TTI / transmission duration / numerology in which at least one of one or more first logical channels is mapped to the BSR and can trigger the BSR. If so, the wireless device can abort the timer. At least one of one or more first logical channels and one or more of one or more first logical channels for which data became available while the timer was running. For TTI / transmission duration / numerology to which two logical channels are mapped, if the wireless device receives an uplink grant, the wireless device can abort the timer. At least one of one or more first logical channels and one or more of one or more first logical channels for which data became available while the timer was running. If the wireless device receives an uplink grant for TTI / transmission duration / numerology where the two logical channels are not mapped and can trigger the BSR, the wireless device can abort the timer. At least one of one or more first logical channels and one or more of one or more first logical channels for which data became available while the timer was running. With respect to TTI / transmission duration / numerology where two logical channels can be mapped and trigger BSR, if the wireless device receives an uplink grant, the wireless device can abort the timer. In one example, the wireless device can abort the timer if the wireless device receives an uplink grant. In one example, the wireless device can abort the timer if the wireless device can receive the uplink grant and trigger the BSR.

In an exemplary embodiment, the wireless device carries one or more messages that include one or more fields that indicate the mapping between one or more logical channels and one or more TTI / transmission duration / numerology. Can be received. In one example, one or more messages can include configuration parameters for the counter. In one example, when the wireless device has data available on at least one of one or more first logical channels and the wireless device receives uplink grants on TTI / transmission duration / numerology. , The wireless device can increment the counter and one or more first logical channels are not mapped to TTI / transmission duration / numerology. In one example, the wireless device can trigger the BSR and reset the counter when the counter reaches the first value. In one example, the wireless device can reset the counter when the BSR is triggered. In one example, one or more messages can include one or more configuration parameters for one or more first logical channels and / or display of one or more first logical channels. In one example, one or more first logical channels can be associated with one or more delay critical bearers (eg, URLLC). The wireless device can receive grants in terms of TTI / transmission duration / numerology. The wireless device can transmit a BSR for TTI / transmission duration / numerology. For time / numerology, if the wireless device receives an uplink grant, the wireless device can reset the counter. In one example, if the wireless device receives an uplink grant for TTI / transmission duration / numerology on which one or more first logical channels are mapped and can trigger a BSR, the wireless device is countered. Can be reset. In one example, if the wireless device receives an uplink grant for TTI / transmission duration / numerology to which at least one of one or more first logical channels is mapped, the wireless device resets the counter. can do. In one example, a wireless device may receive an uplink grant for TTI / transmission duration / numerology in which at least one of one or more first logical channels is mapped and can trigger a BSR. If possible, the wireless device can reset the counter. In one example, at least one of one or more first logical channels and one or more first logical channels where data becomes available before the counter reaches the first value. If the wireless device receives an uplink grant for TTI / transmission duration / numerology to which one or more second logical channels of the are mapped, the wireless device can reset the counter. In one example, at least one of one or more first logical channels and one or more first logical channels where data becomes available before the counter reaches the first value. If the wireless device receives an uplink grant for TTI / transmission duration / numerology where one or more of the second logical channels can be mapped and trigger BSR, the wireless device resets the counter. can do.

In one example, the wireless device can trigger / transmit a first type BSR (eg, padded / truncated, BSR) if one or more criteria are met. In one example, the wireless device can transmit a first type BSR without transmitting padding if one or more criteria are met. In one example, the wireless device can take into account the priority of the logical channel / logical channel group when transmitting the first type BSR. A logical channel can have one or more priorities for one or more TTI / transmission duration / numerology. Efficient transmission of BSRs is needed to improve base station scheduling and wireless device performance. The enhancement of the first type BSR format needs to take into account the priority of the logical channel regarding TTI / transmission duration / numerology. An exemplary embodiment enhances the first type BSR format.

In an exemplary embodiment, the wireless device comprises one or more fields indicating the priority of one or more transmission time intervals (TTIs) / transmission duration / numerology of one or more logical channels. The above message can be received. The wireless device can receive a grant for the first TTI / transmission duration / numerology. The wireless device can trigger a first type of buffer status report (BSR) when one or more criteria are met. The wireless device can generate a BSR and can transmit a BSR for the first TTI / transmission duration / numerology. In one example, the BSR comprises the buffer status of the logical channel and / or logical channel group containing the highest logical channel priority with the data available for transmission in the first TTI / transmission duration / numerology. Can be done.

In an exemplary embodiment, the wireless device comprises one or more fields indicating the priority of one or more transmission time intervals (TTIs) / transmission duration / numerology of one or more logical channels. The above message can be received. The wireless device can receive a grant for the first TTI / transmission duration / numerology. The wireless device can trigger a first type of buffer status report (BSR) when one or more criteria are met. The wireless device can generate a BSR and can transmit a BSR for the first TTI / transmission duration / numerology. In one example, the BSR comprises the buffer status of the logical channel and / or logical channel group containing the highest logical channel priority with the data available for transmission in the second TTI / transmission duration / numerology. Can be done. In one example, the second TTI / transmission / numerology can be default / preconfigured TTI / transmission duration / numerology. In one example, a second TTI / transmission / numerology can be configured in a wireless device. In one example, one or more messages can display configuration parameters for a second TTI / transmission duration / numerology and / or include one or more first fields. In one example, the BSR is a logical channel and / or logical channel group containing the highest logical channel priority with data available to transmit in each of one or more third TTIs / transmission durations / numerology. Can include the buffer status of. In one example, a third TTI / transmission duration / numerology can be preconfigured on the radio device and / or is indicated on the radio device.

In one example, one or more first criteria correspond to two or more logical channels and / or logical channel groups with data available for transmission, as well as short BSR MAC control elements (MAC CEs). A number of padding bits equal to or greater than the size with the subheader added, and a long BSR MAC CE can contain a number of padding bits less than the size with the corresponding subheader added. Other examples of one or more first criteria may be provided.

In an NR radio access network, a base station may configure multiple logical channels and / or logical channel groups for wireless devices. The wireless device can send a BSR to the report status of one or more logical channels and / or buffers associated with the logical channel group. BSR formats in LTE include short / truncated formats and long formats. The LTE short / truncated BSR format includes the buffer status of a single logical channel group. The LTE long BSR format includes the buffer status of all logical channel groups (4 logical channel groups in LTE). Flexibility in LTE buffer status reporting is not sufficient. For example, BSR in LTE includes one or four logical channel groups. Further, in the case of truncated BSR reporting, the wireless device will have the buffer status of one logical channel group, even if the number of padding bits is large enough to contain the buffer status of two or more logical channel groups. Report. In NR, the number of logical channels and / or logical channel groups can increase, and additional flexibility in BSR reporting is needed to improve base station scheduling and radio device performance. An exemplary embodiment improves the BSR format for more flexible buffer status reporting by wireless devices.

In one example, the BSR can be one of a short format, a long format, and / or other formats. In one example, the BSR can have a variable size. In one example, the size of the BSR may depend on at least one of the first number of logical channels having available data. In one example, the variable size BSR format may include a display of the logical channels (s) whose buffer status is contained within the BSR. In one example, the display can be one or more bitmaps. In one example, a value of 1 in one or more bitmaps may indicate that the corresponding logical channel is contained within the BSR. In one example, a value of zero in one or more bitmaps may indicate that the corresponding logical channel is not included in the BSR. An exemplary variable size BSR with a bitmap display is illustrated in FIG.

In one example, the BSR can be one of a short format, a long format, and / or other formats. In one example, the BSR can have a variable size. In one example, the size of the BSR may depend on a second number of logical channel groups with available data. In one example, the variable size BSR format may include an indication of the logical channel group (s) whose buffer status is contained within the BSR. In one example, the display can be one or more bitmaps. In one example, a value of 1 in one or more bitmaps may indicate that the corresponding logical channel group is contained within the BSR. In one example, a value of zero in one or more bitmaps may indicate that the corresponding logical channel group is not included in the BSR. An exemplary variable size BSR with a bitmap display is illustrated in FIG.

In one example, the variable size BSR format can accommodate MAC subheaders that do not have a length field (eg, fixed size MAC subheaders that do not have a length (L) field) and display the BSR size on the BSR (for example, For example, it can contain one or more bitmaps and / or other displays). In one example, the variable size BSR format can correspond to a MAC subheader with a length field (eg, a variable size MAC subheader with a length (L) field). In one example, the L field can indicate the number of logical channels and / or logical channel groups whose buffer status is contained within the BSR. In one example, the L field can indicate the number of octets within the BSR. In one example, the BSR comprises one or more logical channel identifiers and / or one or more logical channel group identifiers, and buffer statuses corresponding to one or more logical channels and / or one or more logical channel groups. be able to. In an exemplary embodiment, the BSR length can be indicated within the BSR. In one example, the first field (eg, the first part of the BSR) may indicate the length of the BSR. In one example, the length of the BSR can be in units of the number of octets in the BSR. In one example, the length of the BSR can be in units of the number of logical channels (s) and / or logical channel groups (s) whose buffer status is contained within the BSR. An exemplary variable size BSR format is shown in FIG.

In an exemplary embodiment, the UE may transmit a variable size BSR if the first type BSR (eg, truncated BSR) is triggered. In one example, the wireless device receives one or more messages that include one or more fields indicating the priority of one or more logical channels for one or more transmission time intervals (TTIs) / transmission duration / numerology. Can be. The wireless device can receive a grant for the first TTI / transmission duration / numerology. The wireless device can trigger a first type of buffer status report (BSR) when one or more criteria are met. The wireless device may generate a variable size BSR and may transmit a variable size BSR for the first TTI / transmission duration / numerology. In one example, the variable size BSR is a k logical channel and / or logic containing the k highest logical channel priority with data available for transmission regarding the first TTI / transmission duration / numerology. It may include the buffer status of the channel group, where k may depend on the number of padding bits and / or leftover bits in the grant (eg, k = 1, 2, ...).

In an exemplary embodiment, the wireless device comprises one or more fields indicating the priority of one or more transmission time intervals (TTIs) / transmission duration / numerology of one or more logical channels. The above message can be received. The wireless device can receive a grant for the first TTI / transmission duration / numerology. The wireless device can trigger a buffer status report (BSR) of the first type (eg, truncated BSR) when one or more criteria are met. In one example, one or more criteria add the corresponding subheader to two or more logical channels and / or logical channel groups with data available for transmission, as well as a short BSR MAC control element (MAC CE). It can contain as many padding bits as or greater than the size of the padding bits, and a number of padding bits smaller than the size of the long BSR MAC CE plus the corresponding subheader. The wireless device may generate a variable size BSR and may transmit a variable size BSR for the first TTI / transmission duration / numerology. In one example, the BSR is a k logical channel and / or logical channel group containing the k highest logical channel priority with data available for transmission regarding the second TTI / transmission duration / numerology. Can include the buffer status of, where k can depend on the number of padding bits and / or leftover bits in the grant (eg, k = 1, 2, ...). In one example, the second TTI / transmission duration / numerology can be the default / preconfigured TTI / transmission duration / numerology. In one example, a second TTI / transmission duration / numerology can be configured in a wireless device. In one example, one or more messages can display configuration parameters for a second TTI / transmission duration / numerology and / or include one or more first fields. In one example, a variable size BSR contains k high logic channel priorities with k data available for transmission for each of one or more third TTIs / transmission durations / numerology. It may include the buffer status of the logical channel and / or the logical channel group, where k may depend on the number of padding bits and / or leftover bits in the grant (eg, k = 1, 2, ...). In one example, a third TTI / transmission duration / numerology can be preconfigured on the wireless device and / or displayed on the wireless device.

In an exemplary embodiment, as shown in FIG. 21, the wireless device may receive configuration parameters for multiple logical channels. Multiple logical channels can be grouped into multiple logical channel groups. In one example, a configuration parameter may indicate a logical channel within a plurality of logical channels belonging to a logical channel group within the plurality of logical channel groups. In one example, the wireless device can trigger a padding BSR. In one example, the wireless device can trigger a padding BSR when the wireless device allocates uplink grant resources, and the number of padding bits is the size of the buffer status report MAC CE (eg, short BSR) plus its subheader. Greater than. In one example, a wireless device may transmit a truncated BSR in response to triggering a padding BSR, the number of padding bits being greater than the size of the short BSR plus its subheader, but its subheader to the long BSR. It is smaller than the size including the subheader.

In one example, the truncated BSR includes a first field containing a plurality of existing bits. The first bit may include one octet (eg, eight existing bits). In one example, one existing bit in a plurality of existing bits may correspond to one logical channel group. In one example, the position of an existing bit among a plurality of existing bits may indicate the index of the corresponding logical channel group. In one example, the present bit indicates whether the truncated BSR contains the buffer size for the logical channel group corresponding to the existing bit. In one example, the presence bit indicates whether the buffer size field for the logical channel group corresponding to the presence bit exists in the truncated BSR. The buffer size field can indicate the amount of data available through the logical channel of the logical channel group corresponding to the existing bits.

In one example, there may be a first number of buffer size fields in the truncated BSR. In one example, the first number of buffer size fields is obtained for a logical channel group out of a plurality of logical channel groups having logical channels with available data for transmission in ascending order of priority. In one example, the first number may be based on the number of padding bits.

In the case of the example of FIG. 21, the number of padding bits may allow transmission of three buffer size fields corresponding to three logical channel groups. In this example, the logical channel group LCG _k , the logical channel group LCG _m , and the logical channel group LCG _l are the logical channel having the highest priority, the logical channel having the second highest priority, and the third. Includes the highest logical channel. The truncated BSR may _{include buffer size fields for LCG k} , LCG _m , and LCG _l , and the corresponding existing bits in the first field may represent a value of 1. The wireless device may send a truncated BSR and may receive an uplink grant in response to sending a buffer status report. Uplink grants may be received via downlink control information and may include transmit parameters for the transmission of one or more transport blocks. Transmission parameters may include resource allocation parameters, HARQ related parameters, power control parameters and the like. The wireless device may transmit one or more transport blocks based on the uplink grant.

In an exemplary embodiment, as shown in FIG. 22, the first presence bit (eg, Bi) in the first field containing a series of presence bits may indicate a first position (eg, position i). .. The first position (position i) can identify the first logical channel group within a plurality of logical channel groups (eg, LCGi). In one example, the value of Bi may indicate whether the corresponding buffer size field for LCGi exists in the truncated BSR. In one example, a value of 1 for Bi may indicate that a corresponding buffer size field exists for LCGi. In one example, a value of zero for Bi may indicate that the corresponding buffer size field does not exist for LCGi.

To improve the robustness of the buffer status reporting procedure, the wireless device may be configured with a timer that starts in response to one or more conditions. One or more conditions may include sending a BSR for sending new data or receiving an uplink grant. The wireless device may trigger a buffer status report in response to the timer expiring. This process ensures that the BSR is transmitted frequently enough that the base station has sufficient information about the available data of the wireless device and can schedule the wireless device efficiently. Traditional timer management procedures include restarting a timer in response to receiving an uplink grant to send new data. However, unlike conventional LTE radio access networks, uplink grants in NR radio access networks cannot be effective in transmitting arbitrary data. Uplink grants in NR can be useful for transmitting a subset of data / logical channels in a wireless device. Traditional procedures can result in frequent timer restarts and less frequent BSR transmissions. Traditional procedures result in reduced frequency of BSR transmissions, and therefore base stations may lack sufficient information for efficient scheduling of wireless devices. Traditional timer management procedures cause degradation in wireless device and network performance with respect to throughput, latency, and other performance measurements. An example, an embodiment enhances a traditional buffer status reporting procedure by enhancing the process for managing timers.

In an exemplary embodiment, the base station may configure a radio device (eg, using a quasi-static / RRC configuration and / or dynamic signaling) with a first timer (eg, retxBSR timer). In one example, a wireless device may start or restart a first timer when / when a MAC entity commands the generation of a buffer status report (eg, BSR MAC CE). In one example, the wireless device may start or restart the first timer when / when the MAC entity orders the generation of a buffer status report (eg, BSR MAC CE), except for the padding BSR. In one example, a wireless device starts or restarts a first timer when / when a MAC entity orders the generation of a buffer status report (eg, BSR MAC CE), except for padding BSRs or truncated BSRs. Can be started. In one example, a wireless device may start or restart a first timer when displaying one or more grants, the one or more grants providing resources for transmitting new data (eg, any). The logical channel with the available data (in UL-SCH) can be mapped to the TTI / transmission duration / numerology / cell shown in one or more grants. In one example, one or more grants may be received during the time window. In one example, the time window may be configurable (eg, using an RRC configuration). In one example, one or more grants can be received between n subframes (eg, n = 1, 2, ...). In one example, the value of n can be shown to the wireless device (eg, using RRC and / or dynamic signaling). In one example, a MAC entity can trigger a BSR when the first timer expires.

In an exemplary embodiment, a base station may configure a radio device with one or more first timers (eg, using a quasi-static / RRC configuration and / or dynamic signaling). In one example, a base station may configure one or more first timers for multiple logical channels and / or logical channel groups. In one example, the base station may configure a timer for each logical channel and / or logical channel group. In one example, a base station may configure one or more first timers for one or more first logic channels and one or more second logic channel groups. The wireless device may start or restart one or more first timers when / when the MAC entity commands the generation of a buffer status report (eg, BSR MAC CE). In one example, when a wireless device commands the generation of a buffer status report (eg, BSR MAC CE) that includes one or more logical channels and / or logical channel groups corresponding to one or more timers / Occasionally, one or more first timers may be started or restarted. In one example, a wireless device has one or more first timers when / when a MAC entity commands the generation of a buffer status report (eg, BSR MAC CE), except for padding BSRs or truncated BSRs. Can be started or restarted. In one example, the wireless device generates a buffer status report in which the MAC entity contains one or more logical channels and / or logical channel groups corresponding to one or more timers, except for padding BSRs or truncated BSRs. For example, when instructing / sometimes BSR MAC CE), one or more timers of one or more first timers may be started or restarted. In one example, when a wireless device receives a grant associated with a logical channel and / or logical channel group, the timer associated with the logical channel and / or logical channel group can be started or restarted. In one example, a BSR for at least one logical channel and / or logical channel group can be triggered when the timer associated with at least one logical channel and / or logical channel group expires. In one example, the BSR for all logical channels and / or logical channel groups can be triggered when the timer associated with at least one logical channel and / or logical channel group expires.

In an exemplary embodiment, as shown in FIG. 23, the wireless device may receive one or more messages containing configuration parameters. In one example, this configuration parameter can be a logical channel configuration parameter for multiple logical channels. In one example, the configuration parameters may include a first parameter of one or more logical channels indicating that the logical channels of the one or more logical channels are mapped to at least one first transmission duration. In one example, the configuration parameters may include a second parameter that indicates a first value for the buffer status report timer. In one example, the buffer status report timer can be a retxBSR timer.

In one example, the wireless device may initiate a buffer status report timer with a first value in response to receiving at least one uplink grant associated with a second transmit duration, one or more. The at least one logical channel having the data of the logical channel of is mapped to a second transmission duration with which at least one uplink grant is associated. In one example, the wireless device may initiate a buffer status report timer with a first value in response to receiving at least one uplink grant associated with a second transmit duration, one or more. The logical channel with the data of the logical channel of is mapped to a second transmission duration with which at least one uplink grant is associated.

The wireless device can send a buffer status report in response to the buffer status report timer expiring. In one example, the wireless device receives at least one uplink grant associated with a second transmission duration, and any of the logical channels having data from one or more logical channels is at least one uplink. The buffer status report timer can continue to run in response to not being mapped to the grant's associated second transmit duration (eg, do not start the buffer status report timer).

According to various embodiments, devices such as, for example, wireless devices, off-network wireless devices, base stations, and / or the like may include one or more processors and memory. The memory, when executed by one or more processors, can store instructions that cause the device to perform a series of operations. Embodiments of exemplary operation are shown in the accompanying drawings and specification. Features from various embodiments can be combined to create yet another embodiment.

FIG. 24 is an exemplary flow diagram according to one aspect of the embodiment of the present disclosure. At 2410, the wireless device may receive configuration parameters for multiple logical channels. Multiple logical channels can be grouped into multiple logical channel groups. The plurality of logical channel groups may include a first logical channel group. At 2420, the padding buffer status report (BSR) can be triggered. At 2430, the truncated BSR may be transmitted in response to triggering the padding BSR and responding that the number of padding bits meets one or more criteria. One or more criteria are, for example, a combination of these that is greater than the size of the short BSR plus the short BSR subheader, smaller than the size of the long BSR plus the long BSR subheader, and / or the same. It may include the number of padding bits. The truncated BSR may include a first field that constitutes a plurality of existing bits. One existence bit in a plurality of existence bits may indicate the existence of a buffer size field for the first logical channel group corresponding to the existence bit. The buffer size field may indicate the amount of data available across the logical channels of the first logical channel group. The truncated BSR may include a first number of buffer size fields for a logical channel group among a plurality of logical channel groups having logical channels with available data to transmit in ascending order of priority. The first number can be determined based on the number of padding bits.

According to embodiments, the configuration parameters may indicate the priority for one logical channel within the plurality of logical channels. According to the embodiment, the downlink control information constituting the uplink grant indicating the uplink resource allocation can be received. According to embodiments, the number of padding bits can be at least based on the size of the uplink grant. According to embodiments, the truncated BSR can be associated with a medium access control subheader that includes a logical channel identifier and a length field. The length field may indicate the length of the truncated BSR. According to embodiments, the first number of buffer size fields can be determined based on the size of the truncated BSR that fits the padding bits. According to embodiments, the size of the truncated BSR may depend on the first number of buffer size fields. According to embodiments, the first position of the first presence bit in the first field can identify the logical channel identifier. According to an embodiment, the first value of 1 for the first existing bit may indicate that there is a buffer size field for the first logical channel group corresponding to the first existing bit, and the first existence. A second value of zero for a bit may indicate that there is no buffer size field for the first logical channel group corresponding to the first existing bit. According to embodiments, transmitting the truncated BSR further responds to triggering the padding BSR and for the number of padding bits equal to the size of the short BSR plus the short BSR subheader. be able to.

FIG. 25 is an exemplary flow diagram based on aspects of the embodiments of the present disclosure. At 2510, the wireless device may receive configuration parameters for multiple logical channels in which multiple logical channels can be grouped into multiple logical channel groups. The plurality of logical channel groups may include a first logical channel group. At 2520, the truncated buffer status report (BSR) states that the number of padding bits is greater than the size of the short BSR plus the short BSR subheader and smaller than the size of the long BSR plus the long BSR subheader. Can be sent in response to. The truncated BSR may include a first field that constitutes a plurality of existing bits. One existence bit in a plurality of existence bits may indicate the existence of a buffer size field for the first logical channel group corresponding to the existence bit. The buffer size field may indicate the amount of data available across the logical channels of the first logical channel group. The first number of buffer size fields for a logical channel group among a plurality of logical channel groups having a logical channel with available data for transmission may follow a decreasing order of priority. The first number can be determined based on the number of padding bits.

According to embodiments, the configuration parameters may indicate the priority for one logical channel within the plurality of logical channels. According to embodiments, the wireless device may further receive downlink control information, including uplink grants indicating uplink resource allocation. According to embodiments, the number of padding bits can be at least based on the size of the uplink grant. According to embodiments, the truncated BSR can be associated with a medium access control subheader that includes a logical channel identifier and a length field. The length field may indicate the length of the truncated BSR. According to embodiments, the first number of buffer size fields can be determined based on the size of the truncated BSR that fits the padding bits. According to embodiments, the size of the truncated BSR may depend on the first number of buffer size fields. According to embodiments, the first position of the first presence bit in the first field can identify the logical channel identifier. According to an embodiment, the first value of 1 for the first existing bit may indicate that there is a buffer size field for the first logical channel group corresponding to the first existing bit, and the first existence. A second value of zero for a bit may indicate that there is no buffer size field for the logical channel group corresponding to the first existing bit. According to embodiments, the wireless device may further receive uplink grants in response to transmitting the truncated BSR. According to the embodiment, the wireless device transmits the truncated BSR in response to triggering the padding BSR and further responding that the number of padding bits is equal to the short BSR plus the short BSR subheader. obtain.

FIG. 26 is an exemplary flow diagram based on aspects of the embodiments of the present disclosure. At 2610, the wireless device may receive configuration parameters for multiple logical channels grouped into multiple logical channel groups. At 2620, the truncated buffer status report (BSR) responds to a number of padding bits that is greater than the size of the short BSR plus the short BSR subheader and smaller than the size of the long BSR plus the long BSR subheader. Can be sent. The truncated BSR may include a first field that constitutes a series of existing bits, including a first existing bit for the first logical channel group within the plurality of logical channel groups. The first position of the first presence bit in the first field can identify the identifier of the first logical channel group. The value of the first presence bit may indicate the presence of a buffer size field for the first logical channel group. The first number of buffer size fields for the first number of logical channel groups having logical channels may have available data for transmission in ascending order of priority. The first number can be determined based on the number of padding bits.

FIG. 27 is an exemplary flow diagram based on aspects of the embodiments of the present disclosure. At 2710, the base station may transmit configuration parameters for a plurality of logic channels grouped into a plurality of logic channel groups, including a first logic channel group. At 2720, the truncated BSR may be received in response to a number of padding bits that is greater than the size of the short BSR plus the short BSR subheader and smaller than the size of the long BSR plus the long BSR subheader. The truncated BSR may include a first field containing a plurality of existing bits. One existence bit in a plurality of existence bits may indicate the existence of a buffer size field for the first logical channel group corresponding to the existence bit. The buffer size field may indicate the amount of data available across the logical channels of the first logical channel group. The first number of buffer size fields for the first number of logical channel groups in a plurality of logical channel groups having logical channels may have available data for transmission in ascending order of priority. The first number can be determined based on the number of padding bits.

According to embodiments, the wireless device may receive configuration parameters for a plurality of logical channels in which the plurality of logical channels are grouped into a plurality of logical channel groups. The plurality of logical channel groups may include a first logical channel group. The wireless device has a truncated buffer status report in response that the padding bits are larger than the short BSR plus the short BSR subheader and smaller than the long BSR plus the long BSR subheader. (BSR) can be transmitted. The truncated BSR may include a first field that constitutes a plurality of existing bits. One existence bit in a plurality of existence bits may indicate the existence of a buffer size field for the first logical channel group corresponding to the existence bit. The truncated BSR may include a first number of buffer size fields for a logical channel group among a plurality of logical channel groups having logical channels with available data to transmit in ascending order of priority. The first number can be determined based on the number of padding bits.

FIG. 28 is an exemplary flow diagram based on aspects of the embodiments of the present disclosure. At 2810, the wireless device may receive configuration parameters for multiple logical channels from the base station. The plurality of logical channels may include a first logical channel having a first logical channel priority. The first logical channel can be mapped to one or more transmission durations. At 2820, the buffer status report states that the uplink data is available to the first logical channel within the first plurality of logical channels that have the uplink data, and that the first logical channel priority. Can be triggered in response to being greater than one or more priorities of one or more selected logical channels within the first plurality of logical channels. One or more selected logical channels may be selected in response to being mapped to one or more transmission durations. At 2830, the buffer status report may be sent to the base station.

According to the embodiment, the number of selected logical channels may be less than that of the first plurality of logical channels. According to embodiments, the uplink data may become available to the first logical channel in response to the uplink data becoming available in the uplink buffer of the first logical channel. .. The uplink buffer may be a wireless link control buffer or a packet data convergence protocol buffer. According to an embodiment, a plurality of logical channels can be grouped into a first plurality of logical channel groups, and a buffer status report is a buffer of one or more logical channel groups in the first plurality of logical channel groups. Can indicate status. According to embodiments, the buffer status report may be one of a short format, a long format, or a truncated format. According to embodiments, configuration parameters may indicate whether a second logical channel within one or more selected logical channels is mapped to one or more transmission durations. According to embodiments, the first logical channel may have one logical channel priority for one or more transmission durations. According to embodiments, multiple logical channels can be grouped based on a logical channel mapping to transmission duration. According to embodiments, the configuration parameters may include a first logical channel identifier for the first logical channel. According to embodiments, the wireless device may receive additional uplink grants in response to sending a buffer status report.

FIG. 29 is an exemplary flow diagram based on aspects of the embodiments of the present disclosure. At 2910, the wireless device is one or more logics indicating that each logic channel of one or more logic channels is mapped to one or more first transmission durations corresponding to the plurality of transmission durations. A configuration parameter may be received that includes a first parameter of the channel and a second parameter indicating a first value for the buffer status report timer. At 2920, the buffer status report timer receives at least one uplink grant associated with the second transmit duration and of one or more logical channels mapped to the second transmit duration. It can be started with a first value in response to at least one logical channel that has data of it. At 2930, the buffer status report may be sent in response to the buffer status report timer expiring.

According to embodiments, the wireless device receives at least one uplink grant associated with a second transmit duration and one or more logical channels mapped to a second transmit duration. The buffer status report timer can continue to run in response to not receiving any of the at least one logical channels that have data in it. According to embodiments, the configuration parameters may indicate a time window and at least one uplink grant is received within the time window. According to embodiments, the buffer status report may indicate at least one buffer status for one or more logical channels. According to embodiments, the wireless device may send a buffer status report based on at least one of at least one uplink grant. According to an embodiment, the wireless device responds to instructing a multiplexing and assembly procedure to generate a buffer status reporting medium access control (MAC) control element with a first buffer status with a first value. The report timer can be started. According to embodiments, the buffer status report may have one of a short format, a truncated format, or a long format. According to embodiments, the buffer status report may indicate the buffer status of one or more second logical channels of one or more logical channels. According to embodiments, the first parameter may include a corresponding logical channel identifier for each of the one or more logical channels. According to embodiments, the wireless device may receive an uplink grant in response to sending a buffer status report.

Embodiments may be configured to work, if desired. The disclosed mechanisms may be implemented, for example, in wireless devices, base stations, wireless environments, networks, the above combinations thereof, and / or similar, when certain criteria are met. The exemplary criteria may be at least partially based on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, combinations thereof, and / or the like. Various exemplary embodiments may be implemented if one or more of these criteria are met. Therefore, it may be possible to implement exemplary embodiments that selectively execute the protocols of the present disclosure.

The base station may communicate with a combination of multiple wireless devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. The wireless device may have some specific capabilities (s), depending on the category and / or capability (s) of the wireless device. The base station may include multiple sectors. Where the disclosure is intended for base stations communicating with multiple wireless devices, the disclosure may be intended for a subset of all wireless devices within the coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release having a given capability and within a given sector of a base station. A plurality of radio devices in the present disclosure refers to a plurality of selected radio devices and / or a subset of all radio devices in a coverage area and / or equivalents that function according to the disclosed method. May be good. There may be multiple base stations or multiple radio devices within a coverage area that is not compatible with the methods of the present disclosure, eg, those radio devices or base stations are based on older releases of LTE or 5G technology. This is because it has been realized.

In the present disclosure, "a" and "an" and similar phrases should be construed as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" should be construed as "at least one" and "one or more". In the present disclosure, the term "may" should be construed as "sometimes, for example." In other words, the term "may" is a number of preferred possibilities that the phrase following the term "may" may or may not be used in one or more of the various embodiments. It implies that it is an example of sex.

If A and B are sets and each element of A is also an element of B, then A is called a subset of B. Only non-empty sets and subsets are considered herein. 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 similarly "based on at least") may be used in one or more of various embodiments, with the phrase following the term "based on". Or, it implies that it is one example of a number of favorable possibilities that may not be. The phrase "in response to" (or "at least in response to") is the phrase that follows the term "in response to" and is used in one or more of the various embodiments. It implies that it is one example of a number of favorable possibilities that may or may not be. The phrase "according to" (or similarly "at least according to") may be used in one or more of various embodiments with the phrase following the term "according to". , Or implying that it is one of a number of favorable possibilities that may not be. The phrase "adopt / use" (or similarly "at least adopt / use") has the phrase "adopt / use" followed by one or more of the various embodiments. It implies that it is one example of a number of favorable possibilities that may or may not be used.

The term "configured" can relate to the potential of a device, whether the device is in a working state or in a non-working state. The term "configured" can also refer to a particular setting within a device that affects the operating characteristics of the device, whether the device is in an operating state or in a non-operating state. In other words, hardware, software, firmware, registers, memory values, and / or similar things are "configured" inside the device, whether the device is operational or non-operational. , Provide devices with specific characteristics. Terms such as "control messages that occur within a device" can be used to configure a particular characteristic of a device, whether the device is in an operating state or in a non-operating state, or a device. It may mean having parameters that can be used within to achieve a particular operation.

In this disclosure, various embodiments are disclosed. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure.

In the present disclosure, a parameter (or similarly, a field, or information element: referred to as IE) may include one or more information objects, and one information object may include 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, for example, N Includes K and N contains J. In an exemplary embodiment, when one or more messages contain a plurality of parameters, one of the plurality of parameters is contained in at least one of the one or more messages. This means that it does not have to be included in each of one or more messages.

In addition, many of the features presented above have been described as optional through the use of "may" or the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly list all possible permutation combinations that can be obtained by choosing from a set of optional features. However, this disclosure should be construed as explicitly disclosing all such permutation combinations. For example, a system described as having three arbitrary features can be described in seven different ways: only one of the three possible features, any two of the three possible features, or It can be embodied in all three of the three possible features.

Many of the elements described in the disclosed embodiments may be embodied as modules. A module is defined herein as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be embodied in hardware, software in combination with hardware, firmware, wetware (ie, hardware with biological elements), or a combination thereof, all of which operate. Equivalent. For example, a program may be a software routine written in a computer language (C, C ++, Fortran, Java®, Basic, MATLAB, etc.) configured to be run by a hardware machine, or Simulink, Stateflow, GNU. It can be embodied as a modeling / simulation program such as Octave, or LabVIEWMathScript. In addition, it may be possible to embody the module using physical hardware that incorporates individual 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 a hardware description language (VHDL) such as VHSIC hardware description language (VHDL) or Verilog, and between internal hardware modules with less programmable device functionality. Configure the connection. The above techniques are often used in combination to achieve functional module results.

The disclosure of this patent document incorporates material subject to copyright protection. The copyright owner does not object to any reproduction of a patent document or disclosure by anyone for the limited purposes required by law, as described in the Patent and Trademark Office's patent files or records. Otherwise, all copyrights are reserved.

Although various embodiments have been described above, it should be understood that they are presented as examples rather than limitations. It will be apparent to those skilled in the art that various changes in form and detail can be made without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to those skilled in the art how to embody alternative embodiments. Therefore, this embodiment should not be limited by any of the exemplary embodiments described above.

In addition, it should be understood that the figures emphasizing functionality and benefits are all presented for illustrative purposes only. The disclosed architecture is sufficient so that it can be utilized in ways other than those shown. Is flexible and configurable. For example, in some embodiments, the actions listed in any flowchart may be rearranged or simply used in an arbitrary choice.

In addition, the purpose of the abstract of the disclosure is to glance at the US Patent and Trademark Office and the general public, especially scientists, engineers and practitioners in the field who are not familiar with patents or legal terms or expressions. To be able to quickly determine the nature and nature of the disclosure. The abstract of the disclosure is not intended to be scoped in any way.

Finally, only claims containing the explicit term "means" or "step" are 35 U.S.A. S. C. It is the applicant's intention to be construed under 112. Claims that do not explicitly include the phrase "means" or "step" are 35 U.S.A. S. C. It should not be interpreted on the basis of 112.

Claims (15)

It's a method
Upon receiving the configuration parameters of the logical channels grouped into the logical channel group including the first logical channel group by the wireless device (406),
Sending a truncated buffer status report (BSR) based on the number of padding bits,
Including
The truncated BSR
Existence bits, indicating the existence of a buffer size field for the first logical channel group, and
For a logical channel group including the logical channel having the transmission data for the signal, the buffer size field of the first number,
The first number of the data for the transmission of the logical channel is determined based on the number of padding bits according to the order of decreasing priority of the logical channel. The method of claim 1, further comprising receiving downlink control information including an uplink grant indicating an uplink resource allocation, wherein the number of padding bits is at least based on the size of the uplink grant. Either claim 1 or 2, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. The method described in. It said first number of bus Tsu file size field, wherein is determined based on the truncated BSR size that fits in the padding bits in number, The method according to any one of claims 1 to 3. It is a wireless device (406)
With one or more processors (403)
A memory (404) for storing an instruction (405) and
When the instruction is executed by the one or more processors (403), the wireless device (406).
Receiving the configuration parameters of the logical channels grouped into the logical channel group, including the first logical channel group,
Sending a truncated buffer status report (BSR) based on the number of padding bits,
And the truncated BSR
Existence bits, indicating the existence of a buffer size field for the first logical channel group, and
For a logical channel group including the logical channel having the transmission data for the signal, the buffer size field of the first number,
The first number of the data for the transmission of the logical channel is determined based on the number of padding bits according to the order of decreasing priority of the logical channel (406). When the instruction (405) is executed, the wireless device (406) is further made to receive downlink control information including an uplink grant indicating an uplink resource allocation.
The wireless device (406) according to claim 5, wherein the number of padding bits is at least based on the size of the uplink grant. Either of claims 5 or 6, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. The wireless device (406) described in. The wireless device (406) according to any one of claims 5 to 7, wherein the first number of the buffer size fields is determined based on the size of the truncated BSR that fits within the number of padding bits. It's a method
The base station (401) transmits the configuration parameters of the logical channels grouped into the logical channel group including the first logical channel group, and
Receiving a truncated buffer status report (BSR) based on the number of padding bits
The truncated BSR contains
Wherein indicates the presence of a buffer size field for the first logical channel group, the logical channel group including the logical channel having the presence bits, and the data for transmission, the buffer size field of the first number,
The first number of the data for the transmission of the logical channel is determined based on the number of padding bits according to the order of decreasing priority of the logical channel. The method of claim 9, further comprising transmitting downlink control information including uplink grants indicating uplink resource allocation, wherein the number of padding bits is at least based on the size of the uplink grant. Either claim 9 or 10, wherein the truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR. The method described in. It said first number of bus Tsu file size field, wherein is determined based on the truncated BSR size that fits in the padding bits in number, The method of any of claims 9-11. It is a base station (401)
With one or more processors (403)
A memory (404) for storing an instruction (405) and
When the instruction is executed by the one or more processors (403), the base station (401).
Sending the configuration parameters of the grouped logical channels to the logical channel group, including the first logical channel group,
Receiving a truncated buffer status report (BSR) based on the number of padding bits
And the truncated BSR
Existence bits, indicating the existence of a buffer size field for the first logical channel group, and
For a logical channel group including the logical channel having the transmission data for the signal, the buffer size field of the first number,
The base station (401), wherein the first number of the data for the transmission of the logical channel is determined based on the number of padding bits according to the order of decreasing the priority of the logical channel. When the instruction (405) is executed, the base station (401) is further made to transmit downlink control information including an uplink grant indicating an uplink resource allocation.
13. The base station (401), wherein the number of padding bits is at least based on the size of the uplink grant. The truncated BSR is associated with a medium access control subheader that includes a logical channel identifier and a length field, the length field indicating the length of the truncated BSR.
The bar Tsu first number of file size field, wherein is determined based on the truncated BSR size that fits in the padding in the bit, the base station according to any one of claims 13 or 14 (401).

Images