Cross division duplex signaling

Abstract

The present disclosure relates to cross-partition duplex signaling. Methods, systems, and apparatus, including computer programs encoded on computer storage media, for signaling a cross-partition duplex configuration are disclosed. One of the methods includes identifying, by a first device and for a first link with a second device, a switch for the first link from a first bandwidth part to a second bandwidth part, the first link being associated with a second link having a third bandwidth part; determining, by the first device, whether a bandwidth band between the second bandwidth part and the third bandwidth part satisfies a threshold guard band; and selectively determining, using a result of the determining whether the bandwidth band between the second bandwidth part and the third bandwidth part satisfies the threshold guard band, whether to keep the third bandwidth part for the second link or to switch the third bandwidth part to a fourth bandwidth part for the second link.

Description

Technical Field

[0001] This specification relates to systems and techniques for using cross-division duplexing. Background Technology

[0002] Electronic devices can communicate with each other through one or more cellular networks. For example, a device may communicate with another device across a cellular network using a half-duplex link (e.g., time division duplex (“TDD”), a full-duplex link (e.g., frequency division duplex (“FDD”), or a cross-division duplex link (“xDD”). Communication may include voice data, message data, or other suitable types of data. Summary of the Invention

[0003] Generally, one aspect of the subject matter described in this specification can be embodied in a method comprising the following actions: identifying, by a first device and for a first link with a second device, a switch from a first bandwidth portion to a second bandwidth portion for the first link, the first link being associated with a second link having a third bandwidth portion; determining, by the first device, whether a bandwidth band between the second and third bandwidth portions meets a threshold protection band; and selectively determining, using the result of determining whether the bandwidth band between the second and third bandwidth portions meets the threshold protection band, whether to maintain the third bandwidth portion for the second link or to switch the third bandwidth portion to a fourth bandwidth portion for the second link. Other embodiments of this aspect include corresponding computer systems, apparatuses, computer program products, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. A system of one or more computers may be configured to perform the actions by means of software, firmware, hardware, or combinations thereof installed on the system that cause the system to perform specific operations or actions during operation. One or more computer programs may be configured to perform the actions by means of instructions including instructions that, when executed by a data processing device, cause the device to perform specific operations or actions.

[0004] The foregoing and other embodiments may optionally include one or more of the following features, individually or in combination. The method may include determining, by a first device, that the bandwidth between the second and third bandwidth portions meets a threshold protection band. Selective determination may include selectively determining to maintain the third bandwidth portion for the second link in response to determining that the bandwidth between the second and third bandwidth portions meets the threshold protection band. Determining that the bandwidth between the second and third bandwidth portions meets the threshold protection band may include determining that the bandwidth between the second and third bandwidth portions is greater than, equal to, or greater than or equal to the threshold protection band.

[0005] In some implementations, the method may include determining, by a first device, that the bandwidth between the second and third bandwidth portions does not meet a threshold protection band. Selective determination may include selectively determining, in response to determining that the bandwidth between the second and third bandwidth portions does not meet the threshold protection band, to switch the third bandwidth portion to a fourth bandwidth portion for the second link. Determining that the bandwidth between the second and third bandwidth portions does not meet the threshold protection band may include determining that the bandwidth between the second and third bandwidth portions is less than, equal to, or less than or equal to the threshold protection band.

[0006] In some specific implementations, identifier handover may include switching identifiers from a first partitioned duplex type to a second partitioned duplex type. Switching identifiers from a first partitioned duplex type to a second partitioned duplex type may include switching identifiers from time division duplex to frequency division duplex. Switching identifiers from a first partitioned duplex type to a second partitioned duplex type may include switching identifiers from frequency division duplex to time division duplex.

[0007] In some specific implementations, the first device can be a next-generation node B. The second device can be user equipment. The first link can be a downlink. The second link can be an uplink.

[0008] Generally, one aspect of the subject matter described in this specification can be embodied in a method comprising: determining, by a device and using configuration data specifying a switching of a bandwidth portion for a first link, a switch from a first bandwidth portion to a second bandwidth portion for the first link, the first bandwidth portion of the first link being associated with a third bandwidth portion of the second link; determining whether the third bandwidth portion of the second link is associated with the second bandwidth portion of the first link; and selectively determining, using the result of determining whether the third bandwidth portion of the second link is associated with the second bandwidth portion of the first link, whether to maintain the third bandwidth portion for the second link or to switch the third bandwidth portion to a fourth bandwidth portion for the second link. Other embodiments of this aspect include corresponding computer systems, apparatuses, computer program products, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. A system of one or more computers may be configured to perform the actions by means of software, firmware, hardware, or combinations thereof installed on the system that cause the system to perform specific operations or actions during operation. One or more computer programs may be configured to perform the actions by means of instructions including instructions that, when executed by a data processing device, cause the device to perform specific operations or actions.

[0009] The foregoing and other embodiments may optionally include one or more of the following features, individually or in combination. The method may include determining that a third bandwidth portion of the second link is associated with a second bandwidth portion of the first link. Selective determination may include determining to maintain the third bandwidth portion for the second link in response to determining that the third bandwidth portion of the second link is associated with the second bandwidth portion of the first link.

[0010] In some implementations, the method may include determining that a third bandwidth portion of the second link is not associated with a second bandwidth portion of the first link. Selective determination may include determining, in response to determining that the third bandwidth portion of the second link is not associated with the second bandwidth portion of the first link, to switch the third bandwidth portion to a fourth bandwidth portion for the second link.

[0011] In some implementations, determining whether the third bandwidth portion of the second link is associated with the second bandwidth portion of the first link may include determining that configuration data indicates the device should switch the third bandwidth portion to the fourth bandwidth portion and the first bandwidth portion to the second bandwidth portion.

[0012] In some implementations, the configuration data may include downlink control information. The method may involve receiving downlink control information from a device and from a second device. The device may be user equipment. The second device may be a next-generation node B.

[0013] In some specific implementations, identifier handover may include switching identifiers from a first partitioned duplex type to a second partitioned duplex type. Switching identifiers from a first partitioned duplex type to a second partitioned duplex type may include switching identifiers from time division duplex to frequency division duplex. Switching identifiers from a first partitioned duplex type to a second partitioned duplex type may include switching identifiers from frequency division duplex to time division duplex.

[0014] In some specific implementations, the first link can be a downlink. The second link can be an uplink. The first link can be an uplink. The second link can be a downlink. The first bandwidth portion and the third bandwidth portion can be unpaired spectrum.

[0015] Generally, one aspect of the subject matter described in this specification can be embodied in a method comprising the following actions: a device determining a switch from a first time slot to a second time slot, including i) switching a first link from a first bandwidth portion of the first time slot to a second bandwidth portion of the second time slot, and ii) switching a second link from a third bandwidth portion of the first time slot to a fourth bandwidth portion of the second time slot; determining a corresponding subcarrier interval for each of at least four bandwidth portions, the at least four bandwidth portions including a first bandwidth portion, a second bandwidth portion, a third bandwidth portion, and a fourth bandwidth portion; determining a minimum subcarrier interval from the at least four subcarrier intervals; selecting a handover delay period, the handover delay period indicating the time the device waits after the first time slot before communicating using the minimum subcarrier interval; waiting for the handover delay period after the end of the first time slot; and communicating using the second time slot after waiting for the handover delay period. Other embodiments of this aspect include corresponding computer systems, apparatuses, computer program products, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. A system of one or more computers may be configured to perform said action by means of software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform a specific operation or action during operation. One or more computer programs may be configured to perform said action by means of instructions that, when executed by a data processing device, cause that device to perform a specific operation or action.

[0016] The foregoing and other embodiments may optionally include one or more of the following features, individually or in combination. Selecting the handover delay period may include selecting a handover delay period that includes one of the following: less than two time slots for a new radio time slot length of 0.5 milliseconds, less than three time slots for a new radio time slot length of 0.25 milliseconds, or less than six time slots for a new radio time slot length of 0.125 milliseconds. Selecting the handover delay period may include selecting a handover delay period that includes one of the following: more than one time slot for a new radio time slot length of 1 millisecond, more than two time slots for a new radio time slot length of 0.5 milliseconds, more than three time slots for a new radio time slot length of 0.25 milliseconds, or more than six time slots for a new radio time slot length of 0.125 milliseconds.

[0017] In some implementations, the equipment may be user equipment. Communication using the second time slot may include communication by user equipment and communication with the next-generation node B using the second time slot.

[0018] In some specific implementations, determining the switch from a first time slot to a second time slot may include determining the switch from a first time slot of a first duplex type to a second time slot of a second duplex type. Determining the switch from a first time slot of a first duplex type to a second time slot of a second duplex type may include determining the switch from a time-division duplex time slot to a frequency-division duplex time slot. Determining the switch from a first time slot of a first duplex type to a second time slot of a second duplex type may include determining the switch from a frequency-division duplex time slot to a time-division duplex time slot.

[0019] In some specific implementations, the first link can be a downlink. The second link can be an uplink. The first link can be an uplink. The second link can be a downlink. The first bandwidth portion and the third bandwidth portion can be unpaired spectrum.

[0020] Generally, one aspect of the subject matter described in this specification can be embodied in a method comprising the following actions: a first device, and for symbols in a time slot of a cross-division duplex transmission link between the first and second devices, using cell-specific configuration data to determine that the first device can communicate with the second device at a symbol using a combination of multiple different cross-frequency symbol types, the cell-specific configuration data indicating, for each of a plurality of cross-time symbols including the symbol, various combinations of two or more symbol types for communication across the corresponding symbol; and the first device, and using the cross-division duplex transmission link, communicating with the second device across the symbol in the time slot, using a first symbol type for a first set of bandwidth units and a different second symbol type for different second sets of bandwidth units. Other embodiments of this aspect include corresponding computer systems, apparatuses, computer program products, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. A system of one or more computers may be configured to perform the actions by means of software, firmware, hardware, or combinations thereof installed on the system that cause the system to perform specific operations or actions in operation. One or more computer programs may be configured to perform the action by means of instructions including those that, when executed by a data processing device, cause the device to perform a specific operation or action.

[0021] The foregoing and other embodiments may optionally include one or more of the following features, individually or in combination. The method may include transmitting data to a second device, the data indicating, for the symbol, a first channel bandwidth as a first set of bandwidth units for a first symbol type, and a second channel bandwidth as a different second set of bandwidth units for a different second symbol type.

[0022] In some implementations, the method may include sending data to a second device, the data indicating, for the symbol, a first symbol type for a first bandwidth unit in a first group of bandwidth units, and a different second symbol type for a second bandwidth unit in a different second group of bandwidth units. The first bandwidth unit may include a first physical resource block, and the second bandwidth unit may include a second physical resource block. The data transmission may include a transmission bitmap including bits indicating, for each bandwidth unit, whether the corresponding bandwidth unit has a downlink symbol or an uplink symbol. The data transmission may also include a transmission bitmap including bits indicating, for one or more groups of bandwidth units, whether the bandwidth units in a corresponding group have a downlink symbol or an uplink symbol.

[0023] In some implementations, the method may include sending data to a second device, the data indicating a first number of downlink symbols at a first end of the bandwidth unit range of the symbol, and a second number of uplink symbols adjacent to the first number of downlink symbols within the bandwidth unit range of the symbol. The first end of the bandwidth unit range may be the highest frequency within the bandwidth unit range. The first end of the bandwidth unit range may also be the lowest frequency within the bandwidth unit range.

[0024] In some specific implementations, the method may include sending data to a second device indicating: i) a first start position, a first size, and a first symbol type for a first set of bandwidth units for the symbol; and ii) a second start position, a second size, and a different second symbol type for a different second set of bandwidth units for the symbol. The method may also include sending data to a second device indicating: i) a first start position, a first end position, and a first symbol type for a first set of bandwidth units for the symbol; and ii) a second start position, a second end position, and a different second symbol type for a different second set of bandwidth units for the symbol.

[0025] In some specific implementations, cell-specific configuration data may be tdd-UL-DL-ConfigurationCommon identifying one or more symbols for which a device can use multiple different cross-frequency symbol types and communicate using multiple different cross-time symbol types. Determining that a first device can use a combination of multiple different cross-frequency symbol types to communicate with a second device at a symbol may include the first device determining that the cell-specific configuration data identifies the symbol as a flexible symbol, and the first device can use the flexible symbol to communicate using a first symbol type among the multiple different symbol types or a different second symbol type among the multiple different symbol types, but not both; and in response to determining that the cell-specific configuration data identifies the symbol as a flexible symbol, the first device determines, based on the cross-division duplex transmission link between the first device and the second device, that the first device can use a combination of multiple different cross-frequency symbol types to communicate with the second device at that symbol.

[0026] In some specific implementations, determining that a first device can communicate with a second device at a symbol using a combination of multiple different cross-frequency symbol types may include the first device determining, based on cell-specific configuration data, that the symbol is identified as a cross-segment flexible symbol. The first device can then use this cross-segment flexible symbol to communicate using a combination of a first symbol type and different second symbol types from the multiple different symbol types. Determining that a first device can communicate with a second device at a symbol using a combination of multiple different cross-frequency symbol types may also include determining, based on cell-specific configuration data, that the symbol is identified as a cross-segment flexible symbol and that the second symbol is identified as a flexible symbol. The first device can then use this flexible symbol to communicate using either a first symbol type from the multiple different symbol types or different second symbol types from the multiple different symbol types, but not both. The cell-specific configuration data may sequentially include one or more downlink symbols, one or more flexible symbols, one or more cross-segment flexible symbols, one or more second flexible symbols, and one or more uplink symbols. The cell-specific configuration data may sequentially include one or more downlink symbols, one or more cross-segment flexible symbols, one or more flexible symbols, and one or more uplink symbols.

[0027] In some specific implementations, determining that a first device can communicate with a second device at a symbol using a combination of multiple different cross-frequency symbol types may include the first device using two or more cell-specific configuration datasets, wherein the two or more cell-specific configuration datasets i) are each used for different groups of bandwidth units, and ii) include cell-specific configuration data. The two or more cell-specific configuration datasets may identify the number and size of frequency subbands. The first cell-specific configuration dataset may include a first number of frequency subbands, and the second cell-specific configuration dataset may include a different second number of frequency subbands. The first cell-specific configuration dataset may include a specific number of frequency subbands, and the second cell-specific configuration dataset may include that specific number of frequency subbands. The first cell-specific configuration dataset may include a first subband size, and the second cell-specific configuration dataset may include a different second subband size. The first cell-specific configuration dataset may include a specific subband size, and the second cell-specific configuration dataset may include that specific subband size.

[0028] In some specific implementations, cell-specific configuration data includes: i) a tdd-UL-DL-ConfigurationCommon identifying one or more symbols for which the device can communicate using multiple different cross-time symbol types; and ii) cross-split flexible symbol cell-specific configuration data identifying one or more cross-split flexible symbols for which the device can communicate using multiple different cross-frequency symbol types and multiple different cross-time symbol types. The tdd-UL-DL-ConfigurationCommon may include a flag indicating that the cell-specific configuration data includes cross-split flexible symbol cell-specific configuration data. The method may include a first device using the flag to detect the presence of cross-split flexible symbol cell-specific configuration data; and in response to detecting the presence of cross-split flexible symbol cell-specific configuration data using the flag, determining the one or more cross-split flexible symbols that include the symbol.

[0029] In some specific implementations, the combination of cell-specific configuration data and cross-assignment flexible symbols may, in sequence, include one or more downlink symbols, one or more flexible symbols, one or more cross-assignment flexible symbols, one or more second flexible symbols, and one or more uplink symbols.

[0030] In some specific implementations, determining that a first device can communicate with a second device at a symbol using a combination of multiple different cross-frequency symbol types may include the first device determining cell-specific configuration data for a time slot having multiple symbols including the symbol, indicating that the first device can use a different combination of cross-frequency symbol types for each of the multiple symbols. The cell-specific configuration data may include one or more of the following: a cross-slot field indicating the number of consecutive cross-slot flexible time slots in a pattern for which the device can use the multiple different cross-frequency symbol types and communicate using the multiple different cross-time symbol types; a cross-slot symbol field indicating the number of consecutive cross-slot flexible symbols in the cross-slot flexible time slots; a flexible time slot field indicating the number of consecutive flexible time slots in a pattern for which the device can use the multiple different cross-time symbol types to communicate; a flexible symbol field indicating the number of consecutive flexible symbols in the flexible time slots; or a flexible symbol frequency field indicating the number of downlink symbols, the number of uplink symbols, or both across frequencies.

[0031] In some implementations, the cross-slot field may indicate the number of consecutive cross-slot flexible symbols at the beginning of the cross-slot field following the last complete cross-slot flexible time slot. The cross-slot field may also indicate the number of consecutive cross-slot flexible symbols at the end of the cross-slot field preceding the first complete cross-slot flexible time slot. The flexible symbol field may indicate the number of consecutive flexible symbols at the beginning of a flexible time slot following the last complete flexible time slot. The flexible symbol field may also indicate the number of consecutive flexible symbols at the end of a flexible time slot preceding the first complete flexible time slot.

[0032] In some implementations, the method may include receiving cell-specific configuration data from a first device and a second device. The first device may be user equipment. The second device may be a next-generation node B.

[0033] Generally, one aspect of the subject matter described in this specification can be embodied in a method comprising the following actions: a first device, and for symbols in a time slot of a cross-division duplex transmission link between the first and second devices, using downlink control information to determine that the first device can communicate with the second device at a symbol using a combination of multiple different cross-frequency symbol types; for each of a plurality of cross-time symbols including the symbol, the downlink control information includes a time slot format combination indicating one or more of the multiple different symbol types for communication across the corresponding symbol using bandwidth units among the multiple different bandwidth units. Two or more time slot format combinations may each be used for i) a corresponding time slot format combination, and ii) having bandwidth units different from the multiple different bandwidth units; and the first device, and using a cross-division duplex transmission link, communicating with the second device across the symbol in the time slot, using a first symbol type for a first bandwidth unit among the multiple different bandwidth units and using different second symbol types for different second bandwidth units among the multiple different bandwidth units. Other embodiments of this aspect include corresponding computer systems, apparatuses, computer program products, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. A system of one or more computers may be configured to perform said action by means of software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform a specific operation or action during operation. One or more computer programs may be configured to perform said action by means of instructions that, when executed by a data processing device, cause that device to perform a specific operation or action.

[0034] The foregoing and other embodiments may optionally include one or more of the following features, individually or in combination. Each of the plurality of different bandwidth units may be a frequency range. For a first bandwidth unit among the plurality of different bandwidth units, the downlink control information may include two or more timeslot format combinations, each timeslot format combination indicating a different combination of symbols from the plurality of different symbol types. The method may include selecting a first timeslot format combination by a first device and using data identifying transmitted data with a second device, the first timeslot format combination a) being from the two or more timeslot format combinations; b) including a first symbol type; c) being used for communication during a timeslot, and communicating across symbols in the timeslot using the first symbol type for the first bandwidth unit in response to the selection of the first timeslot format combination.

[0035] In some specific implementations, the method may include receiving downlink control information after receiving cell-specific configuration data and device-specific configuration data. The cell-specific configuration data may include tdd-UL-DL-ConfigurationCommon data. The device-specific configuration data may include tdd-UL-DL-ConfigurationDedicated data. The first timeslot format for the first bandwidth unit may have a first size; and the second timeslot format for the second bandwidth unit may have a different second size.

[0036] The subject matter described in this specification can be implemented in various embodiments and can produce one or more of the following advantages. In some embodiments, using cross-segmentation duplexing can improve data transmission latency, base station coverage area, bandwidth capacity (e.g., for uplink transmission), or a combination of both, compared to a system using only time-division duplexing; it can reduce complexity compared to a system using only frequency-division duplexing; or both. In some embodiments, the base station can use cross-segmentation duplexing, while user equipment connected to the base station does not. This can reduce the complexity of the user equipment, such as configuration complexity and hardware resource complexity, while providing beneficial effects for the base station. In some examples, user equipment that does not support cross-segmentation duplexing does not require new signaling for cross-segmentation duplexing, even if the base station to which the user equipment communicates supports cross-segmentation duplexing.

[0037] In some implementations, configuration data allows the base station to dynamically determine the bandwidth required for specific link types by various user equipment (UEs) and to switch UEs to that link type while maintaining different link types for other UEs. For example, this could provide UEs with more uplink transmission bandwidth for specific time slots identified by downlink control information sent to the UEs, while other UEs use the downlink connection for those specific time slots to communicate with the base station. In some implementations, the systems and methods described in this specification may use a threshold guard band. The parameters of the threshold guard band can be selected to reduce the likelihood of interference between bandwidth portions adjacent to the threshold guard band, such as self-interference between uplink and downlink transmissions.

[0038] Details of one or more specific embodiments of the subject matter described herein are set forth in the following figures and description. Other features, aspects, and advantages of this subject matter will become apparent from the description, figures, and claims. Attached Figure Description

[0039] Figure 1 An example environment is depicted where a base station uses cross-division duplex (“xDD”) to communicate with multiple user equipment devices.

[0040] Figures 2A to 2C An example of cross-segmented duplex signaling data is depicted.

[0041] Figure 3 An example of downlink control information (“DCI”) supporting cross-segmented duplexing is depicted.

[0042] Figures 4A to 4B An example is depicted showing a pattern of base station bandwidth portions used for cross-division duplex transmission.

[0043] Figures 5A to 5D An example of bandwidth switching using two time slot formats is depicted.

[0044] Figure 6 An example of the switching delay for switching between different time slot layouts is depicted.

[0045] Figures 7 to 8 This is a flowchart illustrating an exemplary process for communicating between devices using cross-division duplex configuration data.

[0046] Figure 9 This is a flowchart of an exemplary process using a threshold protection band.

[0047] Figure 10 This is a flowchart of an exemplary process for switching bandwidth portions.

[0048] Figure 11 It is a flowchart used to determine the switching delay period.

[0049] Figure 12 An example of a wireless communication system is shown.

[0050] Figure 13 Examples of infrastructure equipment are shown.

[0051] Figure 14 An example of the platform is shown.

[0052] Figure 15 Exemplary components of the baseband circuitry and radio front-end module (“RFEM”) are shown.

[0053] Similar reference numerals and names in the various figures indicate similar elements. Detailed Implementation

[0054] In 5th generation mobile communication systems (“5GS”) specified by the 3rd Generation Partnership Project (“3GPP”), for example, in Release 18, time slots can be used across time division duplex (“TDD”) or frequency division duplex (“FDD”). Using time slots for FDD within TDD is referred to as cross-division duplex (“xDD”), flexible duplex, or sub-band full-duplex. In xDD, a portion of the frequency band of a time slot (e.g., symbols within the time slot) is allocated to uplink transmission, while another portion of the frequency band is allocated to downlink transmission. Furthermore, different frequency bands can be used for different transmission types in different time slots: uplink or downlink. Compared to systems using only TDD, using xDD can improve data transmission latency, base station coverage area, bandwidth capacity (e.g., for uplink transmission), or a combination of both or more of these. Moreover, xDD can provide one or more of these beneficial effects without requiring full spectrum, full-duplex at the base station (e.g., next-generation Node B (“gNB”), user equipment, or both).

[0055] To support xDD, a base station, user equipment (“UE”), or both require a frame, corresponding signaling, or both for xDD configuration. This can occur for half-duplex UEs, full-duplex UEs, or both. For example, a base station may need a frame and signaling to instruct the UE on xDD configuration. The configuration can be cell-specific, UE-specific, or dynamic.

[0056] As a framework, a system, such as a base station, may use bandwidth portions (“BWP”), sub-band frequencies, or both to communicate using xDD. The system may use the association between bandwidth portions to indicate that when a switch occurs for a first bandwidth portion used for a first link (e.g., a downlink or uplink), a corresponding switch should occur for a second bandwidth portion used for a second link (e.g., an opposite type of second link, such as when the first link is a downlink and the second link is an uplink, or when the first link is an uplink and the second link is a downlink). This can occur when a base station switches from a first bandwidth portion used for the first link having a first frequency range or set of bandwidth units to a third bandwidth portion used for the first link having a different third frequency range or set of bandwidth units. While the examples described in this specification generally refer to bandwidth units, bandwidth units can be frequency ranges, physical resource blocks, or other suitable types of bandwidth units.

[0057] The system (e.g., a base station) can determine whether to switch the second bandwidth portion to the fourth bandwidth portion for the second link. The system can make this determination, for example, based on the frequency band between the third and second bandwidth portions, and whether the frequency band meets a threshold protection condition.

[0058] The system can use identifiers of the bandwidth portions to make this determination. For example, the system may include data, such as mappings, indicating which bandwidth portions are associated. When the system switches from the first bandwidth portion to the third bandwidth portion when the third bandwidth portion is not associated with the second bandwidth portion (e.g., using the corresponding identifiers of these portions), the system switches from the second bandwidth portion to the fourth bandwidth portion. When the system switches from the first bandwidth portion to the third bandwidth portion when the third bandwidth portion is associated with the second bandwidth portion, the system determines to skip the switch from the second bandwidth portion to the fourth bandwidth portion.

[0059] In some examples, the base station may use cross-segmented duplexing (CSD), while user equipment (UE) connected to the base station may not use CSD. This reduces the complexity of UE, such as configuration and hardware resource complexity, while providing beneficial effects for the base station. When the base station determines a specific link type (e.g., uplink or downlink) to use with UE, it can use configuration data to indicate that link type. The configuration data may be downlink control information sent by the base station to the UE, radio resource control, or may include both. Using configuration data allows the base station to dynamically determine that various UEs require more bandwidth for a specific link type and to switch various UEs to that link type while maintaining different link types for other UEs. For example, this could provide more uplink transmission bandwidth for various UEs for a specific time slot identified by downlink control information sent to the various UEs, while other UEs use downlink connections for that time slot to communicate with the base station.

[0060] When switching from a first timeslot with a first configuration to a second timeslot with a second configuration, the system (e.g., user equipment) can determine the handover delay. The system can make this determination using a subcarrier spacing (“SCS”) for the bandwidth portion used for the first and second timeslots. For example, the system can determine a minimum subcarrier spacing and use the minimum subcarrier spacing to select the handover delay.

[0061] In some examples, instead of or appended to the bandwidth usage portion, the system may use sub-band-based cross-segmentation duplexing. For signaling, the base station may generate configuration data for user equipment (UE), indicating the time slots, symbols, or both that the UE can use for cross-segmentation duplexing. The configuration data may include tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-Configuration-Dedicated, xDD-specific configuration data, or a combination of two or more of these. xDD-specific configuration data may include, for example, tdd-UL-DL-ConfigurationCommonXDD or tdd-UL-DL-Configuration-DedicatedXDD. In some examples, the configuration data may include downlink control information. The downlink control information may include time slot format frequency combinations, which may include time slot format indicators identifying valid link type combinations for various frequencies. The link type may be the direction of the link, such as uplink or downlink.

[0062] A base station can provide user equipment with data indicating the specific link type used across frequencies. In some examples, the user equipment can provide the base station with data indicating a specific link type. This data can be a bitmap that identifies across frequencies which are used for a first link type, such as a downlink, and which frequencies are used for a second link type, such as an uplink. The bitmap can identify frequencies based on frequency resources (e.g., physical resource blocks), frequency resource groups (e.g., physical resource block groups), or another suitable mapping. In some examples, the link type can be identified by the frequency start position, frequency end position, frequency block size, or a combination of two or more of these.

[0063] Figure 1 An example of environment 100 is depicted, in which base station 102 communicates with multiple user equipment devices 104a-104b using cross-division duplex (“xDD”). Base station 102 may be a cellular base station that communicates with the multiple user equipment devices 104a-104b as the user equipment moves within the range of base station 102.

[0064] Base station 102 may use a portion of the bandwidth or a sub-band frequency to communicate with user equipment 104a-104b using xDD, as discussed in more detail below. For example, base station 102 may use a first portion of the bandwidth or a first sub-band frequency in a time slot to provide a downlink to user equipment 104a, and use a different second portion of the bandwidth or a different second sub-band frequency to provide an uplink to user equipment 104a.

[0065] To enable user equipment 104a to communicate using xDD, base station 102 can provide configuration data 106 to user equipment 104a. Configuration data 106 may indicate configuration parameters for flexible time slots, cross-slotted flexible time slots (e.g., xFlexible time slots), uplink time slots, downlink time slots, or a combination of both or more of these time slots, such as including xFlexible time slots. Flexible time slots may be time slots used for uplink symbols or downlink symbols, but not for both. Cross-slotted flexible time slots may indicate that base station 102, user equipment 104a, or both may use different bandwidth units within a time slot for uplink and downlink symbols, and enable the corresponding equipment to communicate substantially simultaneously using both uplink and downlink within the time slot.

[0066] For example, configuration data 106 can identify values ​​for multiple time slots (e.g., up to 321 time slots). Figure 1 For simplicity, the example shown includes five time slots: S0, S1, S2, S3, and S4. For the first time slot S0, configuration data 106 indicates that this first time slot is used for downlink transmission. Configuration data 106 indicates that three time slots can be used as flexible cross-slots S1, S2, and S3. Configuration data 106 indicates that the last time slot S4 is used for uplink transmission.

[0067] Although Figure 1 The example illustrates a specific uplink and downlink combination for the cross-allocation of flexible time slots S1, S2, and S3, but configuration data 106 does not specify a particular combination that base station 102 or user equipment 104a-104b should use. Instead, configuration data 106 indicates any appropriate combination of uplink and downlink transmissions that these time slots S1, S2, and S3 can be used, and the specific format of these time slots can be determined in real time as the device needs to send, receive, or both data. The device can make this determination based on its transmission requirements, for example, the amount of data the device needs to receive, send, or both.

[0068] For example, user equipment 104a may determine to use first and second sub-band frequencies 106a-106b for downlink transmission during second time slot S1 and third time slot S2, while using third sub-band frequency 106c (e.g., a frequency between first and second sub-band frequencies 106a-106b) for uplink transmission. In some examples, user equipment 104a may determine to use fourth sub-band frequency 106d for downlink transmission and fifth sub-band frequency 106e for uplink transmission.

[0069] When using sub-band frequencies for cross-duplexing, equipment can use different cross-frequency symbols to determine the corresponding transmission type for that frequency. For example, from the perspective of a base station (e.g., a gNB), different cross-frequency symbols may exist at a specific time symbol, i.e., a mixture of downlink and uplink. From the perspective of user equipment, different cross-frequency symbols may exist at a specific time symbol, i.e., a mixture of downlink and uplink.

[0070] In some specific implementations, equipment may need to be configured to operate for cross-segmented duplexing. For example, when the environment uses sub-band frequencies for cross-segmented duplexing, both the base station and the user equipment connected to the base station may need to be configured for cross-segmented duplexing. In such environments, if the user equipment is not configured for cross-segmented duplexing, the base station cannot use cross-segmented duplexing to communicate with such user equipment.

[0071] For sub-band frequencies, a base station can configure the bandwidth portion across more than one frequency symbol. For example, a base station can configure the channel bandwidth of the bandwidth portion as uplink, downlink, flexible, or xFlexible. Then, the bandwidth portion including the channel bandwidth can inherit its configuration from the channel bandwidth included in that bandwidth portion.

[0072] The base station can use any appropriate procedure to indicate the time slot configuration for a portion of the bandwidth. For example, the base station can use configuration data such as tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-Configuration-Dedicated, or modifications to downlink control information. The base station can use the configuration data as signaling to indicate the time slot configuration to user equipment (UEs), through which the UEs can communicate with the base station. The base station can, for example, use tdd-UL-DL-ConfigurationCommon or similar configuration data to send the same configuration data to all UEs in the cell. The base station can, for example, use tdd-UL-DL-Configuration-Dedicated or downlink control information to send different configuration data to some UEs in the cell.

[0073] In some examples, the user equipment (UE) can use existing time slot types for cross-segmentation duplexing. For instance, the UE may receive configuration data, such as tdd-UL-DL-ConfigurationCommon, indicating time slots as downlink, uplink, and flexible time slots. The indication of which time slots are flexible time slots can be implicit. For example, the configuration data may indicate, for example, a first number of time slots among multiple time slots are downlink time slots, and, for example, a second number of time slots among multiple time slots are uplink time slots. The UE can then determine, for example, any remaining time slots among the multiple time slots are flexible time slots.

[0074] Table 1 below depicts an example of configuration data that includes implicit indications of flexible time slots. For example, Table 1 indicates the number of downlink time slots, “nrofDownlinkSlots”, and the number of uplink time slots, “nrofUplinkSlots”. Additionally, Table 1 indicates the number of downlink symbols, “nrofDownlinkSymbols”, and the number of uplink symbols, “nrofUplinkSymbols”. Any remaining time slots in the pattern are implicitly flexible time slots. An example of configuration data is tdd-UL-DL-ConfigurationCommon. Configuration data can be data received by all user equipment in the base station cell.

[0075]

[0076] While flexible time slots are typically used to indicate time slots used for uplink or downlink transmissions but not both, in these specific implementations, user equipment supporting cross-segmentation can use flexible time slots for combined cross-frequency downlink and uplink transmissions. User equipment can determine the use of flexible time slots for combined cross-frequency downlink and uplink transmissions when other configuration data, such as flags indicating that the user equipment is supporting cross-segmentation with the base station transmitting data, is used. For example, tdd-UL-DL-ConfigurationCommon may include a new flag indicating that the base station supports cross-segmentation. Since user equipment not supporting cross-segmentation is not programmed for this flag, such user equipment will ignore the flag and operate in a conventional manner, e.g., using flexible time slots for downlink or uplink transmissions but not both. Since user equipment supporting cross-segmentation is programmed for this flag, such user equipment can determine that any flexible time slot can be used for both cross-frequency uplink and downlink transmissions or solely for uplink or downlink transmissions.

[0077] One device can indicate to another how time slots are configured across time and frequency. A cross-segmentation base station can signal to user equipment (UE) across time and frequency how time slots are configured. For example, as described in more detail below, a cross-segmentation base station can use a bitmap indicating bandwidth units for downlink transmission and other bandwidth units for uplink transmission in flexible time slots. UE can receive the bitmap from the base station, process the bitmap, and transmit data with the base station based on the data in the bitmap. In some examples, UE can send time slot configuration data to the base station indicating the time slot configuration across time and frequency.

[0078] Figures 2A to 2C An example of cross-division duplex signaling data is depicted. The signaling data includes configuration data 200a-200c, which indicates the link type available for the corresponding time slot for each of the multiple different cross-time slots in the time slot pattern 202a-202c.

[0079] exist Figure 2A In the diagram, time slot pattern 202a is D, D, F, F, xF, xF, F, U, and U, where D represents a downlink time slot, U represents an uplink time slot, F represents a flexible time slot that can be either a downlink or uplink time slot, and xF represents an xDD flexible time slot that can be used for uplink transmission, downlink transmission, or a combination of both. For example, when a user equipment receives configuration data 200a, which identifies the symbols D, D, F, F, xF, xF, F, U, and U for the time slots used to communicate with the base station from which it receives the configuration data 200a, the user equipment can determine that downlink transmission will be performed using the first and second flexible time slots 204a-204b and uplink transmission will be performed using the third flexible time slot 204c. The user equipment can make this determination using data indicating the predicted transmission volume for each transmission type (e.g., downlink and uplink).

[0080] User equipment (UE) can determine one or more transmission types for each of the cross-division duplex flexible (“xFlexible”) slots 206a-206b. For example, for xFlexible slots 206a-206b, UE can determine to use two bandwidth units 208a, 208c for downlink transmission and another bandwidth unit 208b for uplink transmission. UE can determine to use any appropriate number of bandwidth units for both uplink and downlink transmission, such as one bandwidth unit for downlink transmission and another for uplink transmission. In some examples, UE can determine to use xFlexible slots 206a-206b for a single transmission type (e.g., downlink or uplink).

[0081] User equipment (UE) can use data indicating predicted transmissions, known transmissions, or both, corresponding to the transmission type to determine which bandwidth units 208a-208c are used for the transmission type. For example, when UE determines that twice the uplink transmission is expected after allocating flexible time slots 204a-204c to D, D, and U, UE may select twice the bandwidth units 208a-208c used for uplink transmission for downlink transmission, for xFlexible time slots 206a-206b. The bandwidth unit for downlink transmission may include two bandwidth units 208a and 208c, which, when combined, provide twice the bandwidth of the bandwidth unit 208b used for uplink transmission. In some examples, the downlink transmission bandwidth unit may be a contiguous frequency block providing twice the bandwidth of the uplink transmission bandwidth unit.

[0082] User equipment (UE) can use bitmaps 210a-210b to signal to the base station the bandwidth units used for a specific transmission type. For example, for the first xFlexible slot 206a, UE can determine a first set of bandwidth units 208a. The first set of bandwidth units can be bandwidth units 0 and 1 in bitmap 210a. UE can generate bitmap 210a, which includes values ​​b0 and b1 identifying the corresponding types of bandwidth units 0 and 1. For example, the bitmap may include a value of 1 for downlink symbols and a value of 0 for uplink symbols. Here, the values ​​b0 and b1 of bandwidth units 0 and 1 can be 1 to indicate that the first set of bandwidth units 208a is used for downlink transmission.

[0083] Similarly, for the first xFlexible timeslot 206a, the user equipment may determine a second set of bandwidth units 208b, which includes bandwidth unit 2 for uplink transmission. The user equipment may include the corresponding uplink transmission value 0 for value b2 in the bitmap. For the first xFlexible timeslot 206a, the user equipment may determine a third set of bandwidth units 208c, which includes bandwidth units 3, 4, and 5. Since these bandwidth units are used for downlink transmission, the user equipment may use value 1 for transmission types b3, b4, and b5 in bitmap 210a.

[0084] Configuration data 200a can have any suitable pattern. For example, in Figure 2A In this configuration, the time slot pattern is: D, F, xF, F, U, with each time slot type corresponding to one or more time slots. Specifically, the pattern indicates that one or more time slots are used for downlink transmission; then, one or more flexible time slots are provided for downlink or uplink transmission, but not both; then, one or more xFlexible time slots are provided for downlink transmission, uplink transmission, or both; then, one or more flexible time slots are provided; finally, one or more uplink transmission time slots are provided.

[0085] exist Figure 2B In the second configuration data 200b, the time slot pattern 202b is D, F, xF, U. Compared with the time slot pattern of the first configuration data 200a, the second time slot pattern of the second configuration data includes only one set of flexible time slots 204d-204e, followed by xFlexible time slots 206c-206e, and does not include any flexible time slots after xFlexible time slots 206c-206e.

[0086] As discussed in more detail above, xFlexible time slots 206c-206e can be used for uplink transmission, downlink transmission, or a combination of both. User equipment receiving the second configuration data 200b can use a bitmap (e.g., bitmaps 210a-210b) to indicate the transmission type of xFlexible time slots 206c-206e. For example, the bitmap may indicate that the first bandwidth unit 208d and the third bandwidth unit 208f of xFlexible time slot 206c are used for downlink transmission, while the second bandwidth unit 208e is used for uplink transmission.

[0087] In some implementations, configuration data (e.g., 200a-200c) may include cross-duplex parameters. These parameters may be defined explicitly, implicitly, or in both ways. For example, parameters may define downlink parameters, uplink parameters, and flexible parameters. Cross-duplex parameters may be implicitly defined based on remaining time slots, remaining symbols, or both that are not explicitly defined in configuration data 200a-200c.

[0088] Table 2 below shows some possible configuration parameters for flexible time slots. Configuration parameters can be parameters received by all user equipment (UEs) in the base station cell. In some examples, configuration parameters can be parameters received by a subset of UEs in the base station cell, for example, as part of UE-specific configuration parameters.

[0089] Configuration data 200a-200c may include multiple flexible time slots, “nrofF1slots” or “nrofF2slots”, in each pattern. The first number of flexible time slots, “nrofF1slots”, indicates the number of time slots following the downlink time slots in the pattern. The second number of flexible time slots, “nrofF2slots”, indicates the number of time slots preceding the uplink time slots in the pattern.

[0090] When the pattern indicates the first number of flexible slots, "nrofF1slots," following a downlink slot, the pattern may include "nrofF1symbols," which is the number of consecutive flexible symbols at the beginning of a slot following the last full flexible slot. The remaining symbols in the slot may be xFlexible symbols, including cross-frequency symbols.

[0091] When the pattern indicates a second number of flexible slots, “nrofF2slots”, following the downlink slot, the pattern may include “nrofF2symbols”, which is the number of consecutive flexible symbols at the end of the slot before the first full flexible slot (e.g., before the uplink slot). The remaining symbols in the slot may be xFlexible symbols, including cross-frequency symbols.

[0092] Configuration data may include flexible time slots, flexible symbols, or any suitable combination of both. In some embodiments, the pattern may include only a first number of flexible time slots and a first number of flexible symbols, and exclude a second number of flexible time slots or symbols. In some embodiments, the pattern may include only a second number of flexible time slots and a second number of flexible symbols, and exclude the first number of flexible time slots or symbols.

[0093]

[0094] In some examples, configuration data 200a-200c can explicitly define the cross-split duplex parameter. Configuration data 200a-200c can explicitly define the cross-split duplex (“xFlexible”) parameter in any appropriate configuration data, such as a part of tdd-UL-DL-ConfigurationCommon or as the new cross-split duplex tdd-UL-DL-ConfigurationCommonXDD.

[0095] Table 3 below shows some examples of xFlexible configuration parameters. xFlexible parameters may include a quotation mark indicating the number of consecutive xFlexible slots in a pattern. In some examples, there are two parameters, "nrofX1slots" and "nrofX2slots". The first "nrofX1slots" indicates the number of first xFlexible slots in the pattern following a set of earlier slots (such as downlink slots, flexible slots, or both). The second "nrofX2slots" indicates a second number of xFlexible slots in the pattern preceding a set of later slots. Later slots can be uplink slots, flexible slots, or both.

[0096] “nrofX1symbols” indicates the first number of xFlexible symbols at the beginning of the slot following the last complete xFlexible slot, such as the “nrofX1slots” slot. “nrofX2symbols” indicates the second number of xFlexible symbols at the end of the slot preceding the first complete xFlexible slot, such as the “nrofX2slots” slot.

[0097] The value “XsymbolFreq” indicates the number of cross-frequency symbols in a time slot. For example, when the value of XsymbolFreq is three, there can be three cross-frequency symbols. When the value of XsymbolFreq is sixteen, there can be sixteen cross-frequency symbols. The number of cross-frequency symbols indicates the number of bandwidth units.

[0098] Configuration data may include xFlexible time slots, xFlexible symbols, or any suitable combination of both. Configuration data may be received by all user equipment (UEs) in the base station cell. Configuration data may be received by a subset of UEs in the base station cell, for example, as part of UE-specific configuration parameters. In some embodiments, the pattern may include only a first number of xFlexible time slots and a first number of xFlexible symbols, and exclude a second number of xFlexible time slots or symbols. In some embodiments, the pattern may include only a second number of xFlexible time slots and a second number of xFlexible symbols, and exclude the first number of xFlexible time slots or symbols.

[0099]

[0100] exist Figure 2C In this example, the time slot pattern 202c is D, xF, F, U. The time slot pattern 202c includes a set of xFlexible time slots 206f-206g, followed by a set of flexible time slots 204f-204h.

[0101] User equipment receiving time slot pattern 202c can use one of the time slots in xFlexible time slot 206g for combined downlink and uplink transmission. For example, the user equipment can use the first bandwidth unit 208g for downlink transmission and the second and third bandwidth units for uplink transmission.

[0102] In this example, the user equipment may use bitmap 210c, which includes bits for blocks of bandwidth units, for example, to reduce the size of bitmap 210c compared to bitmap 210a. The user equipment may generate bitmap 210c to indicate, using the first bit b0, that the first bandwidth unit 0 and the second bandwidth unit 1 are used for a first transmission type, such as downlink. The user equipment may generate bitmap 210c to indicate, using the second bit b1, that the third bandwidth unit 2 and the fourth bandwidth unit 3 are used for a second transmission type, such as uplink. The user equipment may generate bitmap 210c to indicate, using the third bit b2, that the fifth bandwidth unit 4 and the sixth bandwidth unit 5 are used for a third transmission type, such as uplink.

[0103] For example, bandwidth unit 208g can represent two bandwidth units 0 and 1. Bandwidth unit 208h can represent two bandwidth units 2 and 3. Bandwidth unit 208i can represent two bandwidth units 4 and 5.

[0104] User equipment (UE) can use other appropriate signaling to indicate the configuration of the slot pattern. For example, UE may include a signal comprising: [nrofswitches]nrofDLsymbols0, nrofULSymbols0, nrofDLSymbols1, nrofULSymbols2, ..., nrofULSymbol{nrofswitches-1}. The signal may include individual parameters for each xFlexible slot, use the same set of parameters for each xFlexible slot, or use the same set of parameters for multiple xFlexible slots, where the number of slots can be identified using parameters such as nrofXFlexibleslots. For example, the “nrofswitches” parameter may indicate a new set of symbols for the xFlexible slots.

[0105] Here, "nrofswitches" indicates the number of transmission type switches within an xFlexible timeslot. "nrofDLsymbols" indicates the number of consecutive downlink symbols. For example, "nrofDLsymbols0" can indicate the number of consecutive downlink symbols at a predetermined end within an xFlexible timeslot, while "nrofDLsymbols1" can indicate the number of consecutive downlink symbols following a set of consecutive uplink symbols. The end can be either the highest bandwidth unit or the lowest bandwidth unit.

[0106] “nrofULSymbols” indicates the number of consecutive uplink symbols. “nrofULSymbols0” can indicate the number of consecutive uplink symbols after the first group of consecutive downlink symbols, “nrofDLsymbols0”, or the number of consecutive uplink symbols at a predetermined end within an xFlexible time slot.

[0107] In some implementations, the user equipment can use a start position and size to send a signal to notify the time slot configuration. The base station receiving the signal can use the start position and size to determine the corresponding bandwidth unit and transmission type for those bandwidth units. For example, the user equipment can use the format: [start1,size1], [start2,size2], ... . This format may optionally include bits indicating the corresponding transmission type. In some examples, the user equipment may always use a predetermined transmission type for a first start position and alternate between transmission types for each parameter pair. For example, "start1" may indicate a bandwidth unit used for downlink transmission, such as bandwidth unit 208g. Here, given that one bandwidth unit is used for downlink transmission, "size1" may have a value of one. "start2" may indicate the position of the second bandwidth unit 208h, while "size2" may have a value of two to indicate that both the second and third bandwidth units 208h-i are used for uplink transmission.

[0108] In some implementations, the user equipment can use start and end positions to send signals to notify the time slot configuration. The base station receiving the signal can use the start and end positions to determine the corresponding bandwidth units and transmission types for those bandwidth units. For example, the user equipment can use the format: [start1,end1], [start2,end2], ... . This format may optionally include bits indicating the corresponding transmission type. In some examples, the user equipment may always use a predetermined transmission type for a first start position and alternate between transmission types for each parameter pair. For example, "start1" may indicate the bandwidth unit used for downlink transmission, such as bandwidth unit 208g. Here, "end1" may also identify the position of the first bandwidth unit 208g to indicate that only a single bandwidth unit is used for downlink transmission in that xFlexible time slot 206g. "start2" may indicate the position of the second bandwidth unit 208h, while "end2" may identify the position of the third bandwidth unit 208i to indicate that the second and third bandwidth units 208h-208i are used for uplink transmission.

[0109] In some implementations, the base station can send configuration parameters to specific user equipment (UE). Table 4 below includes examples of configuration parameters for cross-duplex configuration. While the base station can send the same or similar configuration parameters to every UE in its cell, it can also send separate messages to each UE or a subset of UEs. For example, the base station can send configuration parameters in tdd-UL-DL-configurationDedicated.

[0110] The base station can transmit configuration parameters in the Radio Resource Control (“RRC”) signal. The RRC signal can be a semi-static user equipment-specific configuration.

[0111] As shown in Table 4 below, configuration parameters may include a type field, such as a flag, which indicates the type of symbol that is neither downlink nor uplink. For example, when the type field has a first value (e.g., zero), the configuration parameter may indicate that any undefined time slot is a flexible time slot, such as in a legacy system. When the type field has a second value (e.g., one), the configuration parameter may indicate that any undefined time slot is an xFlexible time slot used for cross-division duplexing (“xDD”).

[0112]

[0113]

[0114] When a device that does not support xDD receives configuration parameters, it cannot detect the type field. Therefore, devices that do not support xDD will default to using an undefined timeslot as the flexible timeslot. This means that devices that do not support xDD will use all timeslots for downlink or uplink, but not both, for a specific period of time, which is compatible with cross-segmentation duplexing.

[0115] When a base station does not receive a signal indicating that different bandwidth units represent different transmission types, the base station can determine that the signal was sent by a device that does not support xDD. Therefore, the base station can use TDD to transmit data with devices that do not support xDD.

[0116] When an xDD-enabled device receives the configuration parameters described in Table 4, the xDD device can, for example, use "nrofDownlinkSymbols" to determine which symbols are downlink, or use "nrofUplinkSymbols" to determine which symbols are uplink, or both. The xDD-enabled device can then analyze the type field to determine whether the remaining symbols are flexible or xFlexible. The xDD-enabled device can then transmit data with the base station from which it received the configuration parameters, based on the type field.

[0117] In some implementations, when configuration parameters, such as "allDownlink" or "allUplink," indicate that all symbols are either uplinks or downlinks, xDD-enabled devices can determine to skip the analysis of the type field. For example, an xDD-enabled device can determine that all symbols belong to a predefined type and that no flexible or xFlexible slots exist, thus eliminating the need to analyze the type field.

[0118] Figure 3 Examples of downlink control information (“DCI”) 300 supporting cross-segmentation duplexing are depicted. In some examples, DCI 300 can be used to dynamically configure flexible symbols, xFlexible symbols, or both. For example, after defining an RRC semi-static cell-specific configuration, a user equipment-specific configuration, or both, a base station can use DCI 300 to dynamically configure any remaining flexible symbols, xFlexible symbols, or both.

[0119] The DCI 300 includes configuration parameters for both frequency and time. For example, for flexible symbols or xFlexible symbols, the DCI includes configuration parameters for bandwidth units, such as frequency range, bandwidth portion, or channel bandwidth. In some examples, the DCI 300 may include a slot format indicator (“SFI”)—a radio network temporary identifier (“RNTI”)—for each of several different bandwidth units. The DCI 300 may include combinations of slot formats, i.e., a set of SFIs valid across multiple slots.

[0120] like Figure 3 As shown, DCI 300 includes four time slot format combinations 302a-302d within the same duration. Each time slot format combination 302a-302d is used for a different bandwidth unit. For example, the first time slot format combination 302a is used for the first bandwidth unit, the second time slot format combination 302b is used for the second bandwidth unit, the third time slot format combination 302c is used for the third bandwidth unit, and the fourth time slot format combination is used for the fourth bandwidth unit.

[0121] The first time slot format combination 302a and the fourth time slot format combination 302d can indicate that the corresponding bandwidth unit is applied to a first larger number of downlink time slots or symbols. The first time slot format combination 302a and the fourth time slot format combination 302d can indicate that the downlink time slots are followed by a second smaller number of uplink time slots or symbols. The first larger number is greater than the second smaller number.

[0122] The second and third timeslot format combinations 302b-302c indicate that the corresponding bandwidth unit is applied to a third, smaller number of downlink timeslots or symbols. The second and third timeslot format combinations 302b-302c indicate that a fourth, larger number of uplink timeslots or symbols follows the downlink timeslots. The third smaller number is less than the fourth larger number.

[0123] The bandwidth units of time slot format combinations 302a-302d can be of any suitable size. For example, the sizes of the bandwidth units can be equal, unequal, or a combination of both. In some examples, the first and second time slot format combinations 302a-302b can have a first size for their corresponding bandwidth units. The third and fourth time slot format combinations 302c-d can have a different second size for their corresponding bandwidth units, i.e., a size different from the first size.

[0124] In some examples, bandwidth units can be pre-configured. For instance, the base station can indicate parameters for the bandwidth units used for time slot format combinations 302a-302d in the DCI 300. For each time slot format combination 302a-302d, the parameters can indicate a frequency range, bandwidth portion, per-channel bandwidth, or a combination thereof.

[0125] In some examples, bandwidth units can be defined implicitly. For instance, DCI 300 can indicate the number of slot format indicators over a specific duration, and user equipment receiving DCI 300 can determine parameters of the bandwidth portion based on the number of slot format indicators. For example, when the total bandwidth is x and DCI 300 includes y slot format indicators, the user equipment can determine the size of each bandwidth portion to be x / y.

[0126] In some examples, the DCI 300 may use a bitmap to indicate the bandwidth portion of time slot format combinations 302a-302d. For example, bitmap [1 1 0 0] may indicate the existence of four time slot format combinations, with the first two allocated for downlink transmission, e.g., when DL=1, and the latter two allocated for uplink transmission, e.g., when UL=0. When the DCI 300 includes bitmap [1 1 0 0 1 1], the DCI 300 identifies six time slot format combinations, where the first two are used for downlink transmission, the middle two for uplink transmission, and the latter two for downlink transmission.

[0127] In the example with four timeslot format combinations, the bandwidth unit for each combination can be based on the total number of bandwidth units divided by four. In the example with six timeslot format combinations, the bandwidth unit for each combination can be based on the total number of bandwidth units divided by six.

[0128] In some implementations, multiple user equipment (UE) devices can receive the same DCI 300. UE devices can use the RNTI to determine their specific timeslot format combinations. For example, a UE can determine which timeslot format combinations have the same RNTI as the UE and use these combinations to transmit with the base station from which the UE receives the DCI 300.

[0129] The base station can generate DCI 300 to include multiple timeslot format combinations 302a-302d, each for different bandwidth units. For example, the base station can indicate the existence of four bandwidth units, each with a specific size. In some examples, the base station can signal the presence of four SFIs, and the user equipment (“UE”) will implicitly divide the transmission bandwidth (“BW”) into four equal parts. In some examples, the base station can explicitly signal the number of physical resource blocks (“PRBs”) associated with each SFI. In some examples, the base station can signal the number of bandwidth units associated with each SFI.

[0130] Figures 4A to 4B An example of a base station bandwidth portion pattern 400 for cross-division duplex transmission is depicted. The bandwidth portion pattern 400 is shown from two perspectives: Figure 4A The perspective of the medium base station and Figure 4B From the perspective of the user equipment (UE). When some devices (e.g., base stations) can use cross-segmented duplexing (CSD) while others (e.g., UEs) cannot, different devices can have different perspectives. For example, a base station may support CSD while UEs do not. Enabling some devices to support CSD while others do not reduces overall system complexity, for example, because only some devices need to be configured for CSD. For example, UEs that do not support CSD do not require new signaling for CSD.

[0131] like Figure 4A As shown, from the base station's perspective, the bandwidth portion pattern 400 includes multiple time slots T0 to T4. The base station can use time division duplexing to configure some of the time slots, such as T0 and T4. For example, the base station can configure the first time slot T0 for downlink transmission across the first bandwidth portion BWP1 and the fifth time slot T4 for uplink transmission across the fifth bandwidth portion BWP5.

[0132] The base station uses cross-division duplexing to configure three intermediate time slots T1, T2, and T3. For these time slots, the base station can configure a second bandwidth portion (BWP2) for downlink transmission across all three time slots T1, T2, and T3. The base station can configure a third bandwidth portion (BWP3) for uplink transmission across all three time slots T1, T2, and T3. The base station can configure a fourth bandwidth portion (BWP4) for downlink transmission across all three time slots T1, T2, and T3.

[0133] The base station can configure the transmission type of time slots T0 to T4, such as downlink, uplink, flexible, or xFlexible, based on known or predicted transmissions of the multiple user equipment (UE1 to UE3) with which the base station communicates. While the example here describes five time slots T0 to T4 and three user equipment (UE1 to UE3), other combinations of time slot numbers and user equipment can be used in a similar manner. For example, the base station could use fourteen time slots to communicate with sixty-eight user equipment devices.

[0134] like Figure 4B As shown, the bandwidth portion pattern 400 may include multiple different bandwidth elements, each allocated to one of the user equipments UE1 through UE3. This allows a base station (e.g., a gNB) to have multiple different cross-frequency symbols at a specific time symbol, while the user equipment has only a single cross-frequency symbol at a specific time symbol, such as a downlink, uplink, or flexible symbol. For example, the user equipment may communicate with the base station based on the bandwidth portion pattern 400 in a time-division duplex configuration.

[0135] The first user equipment UE1 can use the corresponding portion of bandwidth portion pattern 400 to transmit data with the base station. During the first four time slots T0 to T3, the first user equipment UE1 will have downlink transmission with the base station. During the fifth time slot T4, the first user equipment UE1 will have uplink transmission with the base station. Similarly, based on bandwidth portion pattern 400, the third user equipment UE3 will have four time slots T0 to T3 for downlink transmission and one time slot T4 for uplink transmission.

[0136] The second user equipment (UE2) can use the corresponding portion of the bandwidth pattern 400 to transmit data with the base station. During the first time slot T0, the second user equipment (UE2) can have downlink transmission with the base station. During the last four time slots T1 to T4, the second user equipment (UE2) can have uplink transmission with the base station.

[0137] As described above, for User Equipment UE1, UE2, and UE3, the base station can select the configuration of the bandwidth portion pattern 400 using the transmission type (whether known or predicted). When the base station will have more uplink transmissions with User Equipment UE1 and UE3, such as sending video content to the User Equipment, compared to when the base station will have more uplink transmissions with other User Equipment UE2 (e.g., receiving real-time video charges), the base station can include more downlink transmission slots in the bandwidth portion pattern 400 for the respective User Equipment.

[0138] As shown in bandwidth portion pattern 400, the base station can configure the bandwidth portion for each user equipment (UE) to have a cross-frequency symbol, for example, for transmission type. The base station can use bandwidth portion switching, described in more detail below, to signal the slot configuration to the corresponding UE. In some examples, the base station can use bandwidth portion switching for UEs supporting half-duplex operation. The base station can use or not use bandwidth portion switching for UEs supporting full-duplex operation. When the base station communicates with UEs supporting full-duplex operation, the base station does not need to use bandwidth portion switching that could cause removal delays, which would otherwise be caused by the bandwidth portion switching.

[0139] Figures 5A to 5D An example of bandwidth partial handover using two time slot formats 500a-500b is depicted. The base station can use bandwidth partial handover to instruct user equipment to switch to time slot format 500a-500b. The time slot format 500a-500b handover can be from using a first set of bandwidth units for a first transmission type to using a different second set of bandwidth units for the first transmission type.

[0140] exist Figure 5A In this system, the base station has two time slot formats 500a-500b, which it can use to communicate with user equipment. In some examples, the base station may use some, but not all, of the bandwidth portions 502-504 from the first time slot format 500a and the bandwidth portions 506-508 from the second time slot format 500b. In some specific implementations, the base station may use only the bandwidth portions from the respective time slot formats 500a-500b.

[0141] For example, a base station can simultaneously use different bandwidth segments with the same identifier. When the base station switches from a bandwidth segment with a first identifier to a bandwidth segment with a different second identifier, the base station instructs the user equipment (UE) to which it is transmitting data to switch to any other bandwidth segment with the same identifier as the bandwidth segment to which the base station has switched.

[0142] exist Figure 5AIn this configuration, the first bandwidth portion 502a has the identifier BWP-ID = 1, and the second bandwidth portion 504a has the same identifier BWP-ID = 1. Both the first bandwidth portion 502a and the second bandwidth portion 504a are part of the first timeslot format 500a. The third bandwidth portion 506a and the fourth bandwidth portion 508a both have the identifier BWP-ID = 2 and are part of the second timeslot format 500b.

[0143] When the base station switches downlink transmission from the first bandwidth section 502b to the third bandwidth section 506b (this switch is in...) Figure 5B When (as shown in the diagram), the downlink transmission identifier changes from BWP-ID=1 to BWP-ID=2. The base station can use this identifier change to indicate a switch from the first timeslot format 500a to the second timeslot format 500b.

[0144] User equipment (UE) transmitting data with a base station and receiving an instruction to switch to downlink transmission can detect a handover from a first bandwidth portion 502b to a third bandwidth portion 506b. In response to the detected handover, UE can determine whether the identifier of the bandwidth portion has changed. If so, UE can determine whether another bandwidth portion should be switched. If not, UE can determine, based on the detected handover, to skip switching to another bandwidth portion. This can occur when UE uses, for example, all bandwidth portions within or between time slots for a single transmission type.

[0145] The user equipment can use data indicating the identifier of the bandwidth section to determine whether the identifier of the bandwidth section has changed. The user equipment can access this data based on the signal received during the change from the first bandwidth section 502b to the third bandwidth section 506b. The user equipment can access this data in a database, such as in memory stored on the user equipment.

[0146] When the user equipment determines that another bandwidth segment should be switched, the user equipment can determine which or which other bandwidth segments should be switched. The user equipment can make this determination by analyzing the bandwidth segment identifiers it has for any other transmissions. For example, the user equipment can determine that the second bandwidth segment 504b used for uplink transmissions has the identifier BWP = 1. The user equipment can use any appropriate procedure to compare this identifier with the identifier for the bandwidth segment being switched (e.g., the third bandwidth segment 506b). When the identifiers are the same, the user equipment can determine to skip switching the other bandwidth segment. Based on this comparison, when the user equipment determines that the identifiers are different, the user equipment can determine that another bandwidth segment, such as the second bandwidth segment 504b, should be switched.

[0147] The user equipment can determine which bandwidth portion to switch to. The user equipment can make this determination using the identifiers of various bandwidth portions 502b, 504b, 506b, and 508b, using the corresponding timeslot formats 500a-500b, or another suitable procedure. For example, the user equipment can determine that a fourth bandwidth portion 508b used for uplink transmission has the same identifier BWP-ID=2 as the third bandwidth portion 506b, and determine that both bandwidth portions are part of the second timeslot format 500b, or both.

[0148] like Figure 5C As shown, the user equipment can switch from the second bandwidth section 504c to the fourth bandwidth section 508c for uplink transmission. The user equipment can use any appropriate procedure to perform this switch.

[0149] In some examples, bandwidth portions 502-508 may be associated with other bandwidth portions, such as those in a database. A bandwidth portion may be associated with one other bandwidth portion; for example, a third bandwidth portion 506 may be associated with only a fourth bandwidth portion 508. A bandwidth portion may be associated with two or more other bandwidth portions; for example, a first bandwidth portion 502 may be associated with both a second bandwidth portion 504 and a fourth bandwidth portion 508. These associations may be identified in memory, such as in a database stored on the user equipment.

[0150] like Figure 5A As shown, the user equipment has both an active first bandwidth portion 502a and a second bandwidth portion 504a. For example, the user equipment is using bandwidth portions 502a and 504a to transmit data with the device. When the user equipment detects that the bandwidth portion used for uplink transmission has changed from the second bandwidth portion 504d to the fourth bandwidth portion 508d, as... Figure 5D As shown, the user equipment can determine whether to change the bandwidth portion used for downlink transmission. Because the first bandwidth portion 502d is associated with both the second bandwidth portion 504d and the fourth bandwidth portion 508d, the user equipment can determine to skip switching the other bandwidth portion.

[0151] User equipment can use a threshold guard band 510 to determine whether to switch to another bandwidth section. For example, the user equipment can maintain at least a threshold guard band between bandwidth sections. Parameters of the threshold guard band can be selected to reduce the possibility of interference between bandwidth sections adjacent to the threshold guard band, such as self-interference between uplink and downlink transmissions. The user equipment can use the threshold guard band to perform sub-band full-duplex communication using cross-division duplexing.

[0152] When a user equipment (UE) is communicating using different transmission types across different bandwidth portions, and detects a change in the bandwidth portion used for one of the transmission types, the UE can determine whether the threshold protection band 510 is still satisfied. For example, when the UE detects a change from... Figure 5A The first bandwidth portion 502a shown is changed to Figure 5B When the third bandwidth portion 506b is shown, the user equipment can determine whether the bandwidth band between the currently active bandwidth portions 504b and 506b meets the threshold protection band 510.

[0153] In some examples, the bandwidth satisfies the threshold protection band when the bandwidth size is greater than the threshold protection band size. The bandwidth satisfies the threshold protection band size when it is equal to or greater than the threshold protection band size.

[0154] When the user equipment determines that the bandwidth does not meet the threshold protection band, the user equipment determines to switch to another bandwidth section. Figure 5B In the case where the second bandwidth portion 504b and the third bandwidth portion 506b are active, if the second bandwidth portion 504b is included in the same time slot as the third bandwidth portion 506b, then the second bandwidth portion 504b will be adjacent to the cross-frequency third bandwidth portion 506b. Therefore, the bandwidth between the second bandwidth portion 504b and the third bandwidth portion 506b will be zero and the threshold guard band 510 will not be satisfied. In this example, the user equipment can switch uplink transmission from the second bandwidth portion 504c to the fourth bandwidth portion 508c, as... Figure 5C As shown.

[0155] When the user equipment determines that the bandwidth meets the threshold protection band, the user equipment can determine to skip switching to another bandwidth portion based on the bandwidth portion switching. For example, the user equipment can use the first bandwidth portion 502a and the second bandwidth portion 504a to communicate with the base station, such as... Figure 5A As shown. The user equipment can receive signals from the base station to switch uplink transmission from the second bandwidth section 504d to the fourth bandwidth section 508d, as... Figure 5D As shown. The user equipment can determine the bandwidth band between the active first bandwidth portion 502d and the fourth bandwidth portion 508d. The user equipment can use the distance between the two active bandwidth portions (e.g., the distance in frequency) to determine the bandwidth band. Since the bandwidth band has a size greater than the threshold guard band, the user equipment can determine to skip switching to another bandwidth portion. For example, the user equipment can determine that it is not necessary to switch the first bandwidth portion 502d used for downlink transmission to another bandwidth portion, such as the third bandwidth portion 506d.

[0156] In some implementations, the equipment may determine whether to switch to another bandwidth portion based on the previous bandwidth portion switching configuration. For example, the base station may send a signal to the user equipment indicating a change from a first bandwidth portion 502a to a third bandwidth portion 506a. This signal may also indicate whether the user equipment should change any other active bandwidth portion, such as a second bandwidth portion 504a, to a fourth bandwidth portion 508a.

[0157] In some specific implementations, for unpaired spectrum, the uplink and downlink bandwidth portions (e.g., 502a and 504a) may have the same bandwidth portion identifier, the same parameters, the same frequency, or a combination of two or more of these. The uplink and downlink bandwidth portions may have the same or different sizes. The uplink and downlink bandwidth portions may have different center frequencies. For example, the bandwidth portions may have a frequency division duplex (FDM) layout as part of cross-division duplex transmission.

[0158] The device can use partial bandwidth switching to switch between Time Division Duplex (“TDD”) layouts, Frequency Division Duplex (“FDD”) layouts, or both within a cross-division duplex transmission. For example, the device can use partial bandwidth switching to switch from a TDD layout to an FDD layout. The device can also use partial bandwidth switching to switch from an FDD layout to a TDD layout. In some examples, the device can use partial bandwidth switching in xDD transmissions to switch between different FDD layouts.

[0159] In some implementations, the device may have more than two active bandwidth segments. While the example above describes switching from one bandwidth segment to another when two bandwidth segments are active, a similar process can be applied when the device uses three or more bandwidth segments to transmit data. For example, when a device (e.g., user equipment) transmits data with a base station using three bandwidth segments (two for downlink transmission and a third for uplink transmission), the device can determine whether switching one of those bandwidth segments indicates that the device should switch one or both of the other bandwidth segments. The device can use any appropriate process to make this determination, such as using bandwidth segment identifiers, threshold guard bands, or both.

[0160] In these specific implementations, the device may determine to switch one of two other bandwidth portions, but not both. For example, when the device uses a threshold protection band, it may determine that the bandwidth portion to be switched has a first bandwidth band and a second bandwidth band of the two other bandwidth portions, for example, the bandwidth portion to be switched is between the two other bandwidth portions. The device may determine that the first bandwidth band satisfies the threshold protection band 510, and the device may skip switching the corresponding bandwidth portion. The device may determine that the second bandwidth band does not satisfy the threshold protection band 510, and the device should switch the corresponding bandwidth portion.

[0161] In some implementations, the equipment can use downlink control information to determine when to switch bandwidth portions. For example, the user equipment can receive downlink control information scheduling data that instructs the user equipment to switch the active downlink bandwidth portion to a target downlink bandwidth portion. If the target downlink bandwidth portion is not associated with the active uplink bandwidth portion, the user equipment can switch the active uplink bandwidth portion.

[0162] In some examples, downlink control information may indicate multiple or all bandwidth portions that should be switched. For instance, user equipment may receive downlink control information scheduling data that instructs the user equipment to switch both the active uplink bandwidth portion and the active downlink bandwidth portion to the corresponding target bandwidth portion. When the user equipment is transmitting data using only two bandwidth portions, the downlink control information indicates all bandwidth portions that should be changed.

[0163] When a user equipment (UE) has three bandwidth sections and receives downlink control information indicating that two of the bandwidth sections should be switched, the UE may not change all three bandwidth sections. For example, the downlink control information may indicate that only the two identified bandwidth sections should be switched. In some examples, the UE may determine whether a third bandwidth section should also be switched.

[0164] In some examples, the user equipment (UE) may switch from a first number of bandwidth portions to a different second number of bandwidth portions, from a first number of transmissions to a different second number of transmissions, or both. For example, the UE may have uplink and downlink transmissions with the base station during a first time slot. The UE may determine to switch the bandwidth portions used for uplink and downlink transmissions to different bandwidth portions supporting both first and second downlink transmissions, as well as uplink transmissions. Therefore, the number of transmissions with the base station that the UE has changes.

[0165] Figure 6An example of a switching delay of 600 is depicted for switching between different time slot layouts. The device can use a switching delay of 600 when switching between TDD layouts, FDD layouts, or a combination of both.

[0166] For example, a device such as a user equipment may have multiple time slots spanning multiple time intervals, such as time slot n 602, time slot n+1 604, and time slot n+2 606. Time slot n 602 may have a first layout, such as a TDD layout having multiple downlink bandwidth portions 608 and multiple uplink bandwidth portions 612 separated across multiple time intervals by a guard band 610.

[0167] To switch from time slot n 602 with a first layout to time slot n+2 with a different second layout, the device can use a switching delay 600. Time slot n+2 may have an FDD layout having multiple second uplink bandwidth portions 618 and multiple second downlink bandwidth portions 614 separated by a second guard band 616.

[0168] To determine the attributes of the handover delay 600, the device can use subcarrier spacing (“SCS”) data. For example, the device can determine the minimum subcarrier spacing across the downlink bandwidth portion 608, the uplink bandwidth portion 612, the second downlink bandwidth portion 614, and the second uplink bandwidth portion 618. The device can use any suitable procedure to determine the minimum subcarrier spacing, for example, by comparing the attributes of the four subcarrier spacings.

[0169] In some implementations, the device may determine the minimum subcarrier spacing from more than four subcarrier spacings or from three subcarrier spacings. For example, based on the amount of bandwidth in time slot n 602 and time slot n+2 606, the device may use three subcarrier spacings or five subcarrier spacings.

[0170] The device can then use the minimum subcarrier spacing to determine the subcarrier spacing and time slot n+1604 for a handover delay of 600. For example, the device can access a table indicating the subcarrier spacing and time period, the number of time slots, or both. For example, the device can use fewer than two time slots for a new radio time slot length of 0.5 milliseconds, fewer than three time slots for a new radio time slot length of 0.25 milliseconds, or fewer than six time slots for a new radio time slot length of 0.125 milliseconds.

[0171] The device can use any suitable switching delay of 600. In some examples, the device can use one time slot for a new radio time slot length of 1 millisecond, two time slots for a new radio time slot length of 0.5 milliseconds, three time slots for a new radio time slot length of 0.25 milliseconds, or six time slots for a new radio time slot length of 0.125 milliseconds. In some examples, the device can use more than one time slot for a new radio time slot length of 1 millisecond, more than two time slots for a new radio time slot length of 0.5 milliseconds, more than three time slots for a new radio time slot length of 0.25 milliseconds, or more than six time slots for a new radio time slot length of 0.125 milliseconds.

[0172] although Figure 6 The switching delay of 600 is described in time slot n+1 604, but the switching delay may include more than one time slot. The size (e.g., time period) of the switching delay time slot n+1 604 may differ from the sizes of the other time slots n 602 and n+1 606.

[0173] In some examples, the device can determine a handover delay of 600 for unpaired spectrum. For example, when handing over between TDD slot n 602 and FDD slot n+2 606, the device can determine a handover delay of 600. The value of the handover delay for a bandwidth unit within unpaired spectrum can be less than the value defined in Table 8.6.2-1 of 3GPP TS 38.133. For example, for SCS = 30 kHz, the device can use a single slot instead of two slots for a handover delay of 600.

[0174] Figure 7 This is a flowchart of an exemplary process 700 for communicating between devices using cross-division duplex configuration data. For example, process 700 may be used by base station 102 or user equipment 104a-104b from environment 100.

[0175] The first device determines the symbol in the time slot of the cross-division duplex transmission link between the first device and the second device. The first device may use a combination of multiple different cross-frequency symbol types to communicate with the second device at that symbol (702). The first device may use cell-specific configuration data, device-specific configuration data, or both to make this determination. The configuration data indicates, for each of the multiple cross-time symbols including the symbol, various combinations of two or more symbol types from the multiple different symbol types for communication across the corresponding symbol. Cell-specific configuration data may include tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationCommonXDD, or both. Device-specific configuration data may include tdd-UL-DL-Configuration-Dedicated. Although the various examples described in this specification refer to cell-specific configuration data, device-specific configuration data may be used instead of or appended to cell-specific configuration data where appropriate.

[0176] Configuration data may include data stored in memory such as a database. For example, when the first device is a base station, the base station can access configuration data in memory to determine that the base station can communicate with user equipment using a combination of multiple different cross-frequency symbols.

[0177] The first device uses a cross-division duplex transmission link, spanning symbols across time slots, using a first symbol type for a first set of bandwidth units and a different second symbol type for different second sets of bandwidth units to communicate with the second device (704). For example, the first device can use downlink symbols for the first symbol type and can use uplink symbols for different second symbol types. The first set of bandwidth units can be used for downlink transmission. The second set of bandwidth units can be used for uplink transmission.

[0178] In some examples, the first device can use uplink symbols for a first symbol type and downlink symbols for a different second symbol type. The first set of bandwidth units can be used for uplink transmission. The second set of bandwidth units can be used for downlink transmission.

[0179] In some implementations, process 700 may include additional steps, fewer steps, or some of these steps may be divided into multiple steps. For example, the first device may send data to the second device indicating, for the symbol, a first bandwidth portion as a first group of bandwidth units for a first symbol type, and a second bandwidth portion as a second group of bandwidth units for a different second symbol type. Process 700 may include sending data, such as a bitmap, which includes bits indicating for each bandwidth unit whether the bandwidth unit in the corresponding group has a downlink symbol or an uplink symbol.

[0180] Figure 8 This is a flowchart of another exemplary process 800 for communicating between devices using cross-division duplex configuration data. For example, process 800 may be used by base station 102 or user equipment 104a-104b from environment 100.

[0181] For a symbol in a time slot of a cross-division duplex transmission link between the first device and the second device, the first device uses downlink control information to determine that the first device can communicate with the second device at that symbol using a combination of multiple different cross-frequency symbol types (802). For each of the multiple cross-time symbols including that symbol, the downlink control information (“DCI”) may include a time slot format combination that indicates one or more of the multiple different symbol types for communication across the corresponding symbol using bandwidth units among the multiple different bandwidth units. The two or more time slot format combinations may each be used for i) a corresponding time slot format combination, and ii) having a bandwidth unit different from the multiple different bandwidth units.

[0182] The first device uses a cross-division duplex transmission link, communicating with the second device across time slots, using a first symbol type for the first bandwidth unit among the multiple different bandwidth units and using different second symbol types for different second bandwidth units among the multiple different bandwidth units (804). For example, the first device can use a downlink symbol for the first symbol type and can use an uplink symbol for a different second symbol type. The first bandwidth unit can be used for downlink transmission. The second bandwidth unit can be used for uplink transmission.

[0183] In some examples, the first device can use uplink symbols for a first symbol type and downlink symbols for a different second symbol type. A first bandwidth unit can be used for uplink transmission. A second bandwidth unit can be used for downlink transmission.

[0184] In some implementations, process 800 may include additional steps, fewer steps, or some of these steps may be divided into multiple steps. For example, the first device may receive downlink control information after receiving cell-specific configuration data and device-specific configuration data.

[0185] Figure 9 This is a flowchart of an exemplary process 900 using a threshold protection band. For example, process 900 may be used by base station 102 or user equipment 104a-104b from environment 100.

[0186] The first device identifies a switch (902) for a first link with the second device, from a first bandwidth portion to a second bandwidth portion of the first link. The first link may be associated with a second link having a third bandwidth portion. For example, the first device may initiate a switch from a first transmission layout to a second transmission layout. The transmission layouts may be of the same type (e.g., FDD) or different types (e.g., TDD and FDD).

[0187] The first device determines whether the bandwidth between the second and third bandwidth portions meets the threshold protection band (904). For example, the first device determines the boundary between the second and third bandwidth portions. The first device may use the inner boundary toward the other bandwidth portion to determine the bandwidth between the two bandwidth portions.

[0188] In some examples, when two bandwidth portions overlap, for example, in frequency, the first device can determine that there is no bandwidth band between the two bandwidth portions. This can occur when the first device is switching from FDD to TDD, from TDD to FDD, or switching between different bandwidth portions of different sizes in FDD.

[0189] Using the result of determining whether the bandwidth between the second and third bandwidth portions meets the threshold protection band, the first device selectively determines whether to maintain the third bandwidth portion for the second link or switch the third bandwidth portion to the fourth bandwidth portion for the second link (906). For example, the first device may determine whether the bandwidth portion meets the threshold protection band. In response to determining that the bandwidth meets the threshold protection band, the first device may determine to maintain the third bandwidth portion for the second link. In response to determining that the bandwidth portion does not meet the threshold protection band, the first device may determine to switch the third bandwidth portion to the fourth bandwidth portion.

[0190] In some implementations, process 900 may include additional steps, fewer steps, or some of these steps may be divided into multiple steps. For example, the first device may perform the process at least partially for three or more different bandwidth portions used for transmission at a single symbol or time slot. When the first device has three bandwidth portions and receives data indicating a switch for one of the bandwidth portions, the first device may perform process 900 twice. When the first device has four bandwidth portions and receives data indicating a switch for one of the bandwidth portions, the first device may perform process 900 three times. When the first device has four bandwidth portions and receives data indicating a switch for two of the bandwidth portions, the first device may perform process 900 two, three, or four times depending on the relative positions of the bandwidth portions to each other.

[0191] Figure 10This is a flowchart of an exemplary process 1000 for switching bandwidth portions. For example, process 1000 may be used by base station 102 or user equipment 104a-104b from environment 100.

[0192] The device uses configuration data specifying the switching of a bandwidth portion for the first link to determine the switching from a first bandwidth portion to a second bandwidth portion for the first link (1002). The first bandwidth portion is available for the first link, which is associated with a third bandwidth portion of the second link.

[0193] A device (e.g., user equipment) may receive configuration data from another device (e.g., a base station). For example, the device may have multiple transmission links with another device and receive configuration data through one of these transmission links.

[0194] The device determines whether a third bandwidth portion of the second link is associated with a second bandwidth portion of the first link (1004). The device may use a bandwidth portion identifier, data that associates the second bandwidth portion with other bandwidth portions (e.g., data stored in a database), or other appropriate data to make this determination.

[0195] Using the result of determining whether a third bandwidth portion of the second link is associated with a second bandwidth portion of the first link, the device selectively determines whether to maintain the third bandwidth portion for the second link or to switch the third bandwidth portion to a fourth bandwidth portion for the second link (1006). For example, in response to determining that the third bandwidth portion is associated with the second bandwidth portion, the device may determine to maintain the third bandwidth portion. In response to determining that the third bandwidth portion is not associated with the second bandwidth portion, the device may determine to switch the third bandwidth portion to the fourth bandwidth portion.

[0196] In some implementations, process 1000 may include additional steps, fewer steps, or some of these steps may be divided into multiple steps. For example, the device may receive configuration data, such as downlink control information, from another device.

[0197] Figure 11 This is a flowchart of a process 1100 for determining a handover delay period. For example, process 1100 may be used by base station 102 or user equipment 104a-104b from environment 100.

[0198] The device determines to switch from a first timeslot to a second timeslot, including i) switching the first link from a first bandwidth portion of the first timeslot to a second bandwidth portion of the second timeslot, and ii) switching the second link from a third bandwidth portion of the first timeslot to a fourth bandwidth portion of the second timeslot (1102). In some examples, the bandwidth portions of one, but not both, links may be the same. For example, either the first link or the second link, but not both, may include only one bandwidth portion.

[0199] The device determines the corresponding subcarrier spacing (1104) for each of at least four bandwidth portions. The device may use any appropriate procedure to determine the subcarrier spacing of the bandwidth portions.

[0200] The device determines the minimum subcarrier spacing from the four subcarrier spacings (1106). For example, the device can compare the first subcarrier spacing with the second subcarrier spacing and use the result of the comparison to determine which subcarrier spacing is smaller. The device can continue this process until it determines the minimum subcarrier spacing from the four subcarrier spacings.

[0201] In some examples, one or both of the links may have more than one pair of bandwidth portions. For example, the first link may have two pairs of bandwidth portions. In these examples, the device may determine the minimum subcarrier spacing from more than four subcarrier spacings (e.g., from six subcarrier spacings).

[0202] The device selects a handover delay period, which indicates the time the device waits after the first time slot before communicating using the minimum subcarrier interval (1108). For example, the device may access a table identifying handover delay periods for corresponding subcarrier intervals. The device may use the minimum subcarrier interval as the key value of the table to determine the handover delay period. The handover delay period may be the number of time slots, the duration, or another suitable delay period.

[0203] The device waits for a switching delay period (1110). For example, after the end of the first time slot, the device may wait for a switching delay period.

[0204] The device uses a second timeslot for communication (1112). For example, after waiting for a handover delay period, the device can use the second timeslot to communicate with another device. The device can be user equipment. The other device can be a base station, such as a next-generation node B (“gNB”).

[0205] The device can communicate using both downlink and uplink transmissions. For example, the first link can be a downlink and the second link can be an uplink. In some examples, the first link can be an uplink and the second link can be a downlink.

[0206] In some implementations, process 1100 may include additional steps, fewer steps, or some of these steps may be divided into multiple steps. For example, the device may perform steps 1102, 1104, 1106, and 1108 without performing steps 1110 or 1112.

[0207] This specification may use the phrases "in one embodiment," "in an embodiment," or "in some embodiments," each of which may refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," etc., used in conjunction with embodiments of this disclosure are synonymous.

[0208] The various operations can be described in the most helpful way to understand the claimed subject matter as a series of discrete operations. However, the order of description should not be interpreted as implying that these operations necessarily depend on the order.

[0209] Several specific implementations have been described. However, it should be understood that various modifications may be made without departing from the spirit and scope of this disclosure. For example, various forms of processes shown above may be used, in which steps are rearranged, added, or removed.

[0210] Figure 12 An example of a wireless communication system 1200 is illustrated. For convenience and not limitation, the exemplary system 1200 is described in the context of Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. More specifically, the wireless communication system 1200 is described in the context of a non-standalone (NSA) network combining both LTE and NR, such as an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network and a NE-DC network. However, the wireless communication system 1200 could also be a standalone (SA) network combining only NR. Furthermore, other types of communication standards are also possible, including future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0211] like Figure 12As shown, system 1200 includes UE 1201a and UE 1201b (collectively referred to as "UE 1201"). In this example, multiple UEs 1201 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine electronic control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0212] In some implementations, any of UEs in UE 1201 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0213] UE 1201 can be configured to connect to RAN 1210, for example, for communications coupling. In implementations, RAN 1210 can be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 1210 operating in NR or 5G system 1200, while the term "E-UTRAN," etc., can refer to RAN 1210 operating in LTE or 4G system 1200. UE 1201 utilizes connections (or channels) 1203 and 1204, each connection including a physical communication interface or layer (discussed in further detail below).

[0214] In this example, connections 1203 and 1204 are shown as air interfaces for communication coupling and are compatible with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, LTE-A (LTE-Advanced Long Term Evolution), LTE-U (LTE-U), 5G, NR, NR-U (NR-U), and / or any other communication protocols discussed herein. In an implementation, UE 1201 may directly exchange communication data via ProSe interface 1205. ProSe interface 1205 may also be referred to as SL interface 1205 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0215] UE 1201b is shown configured to access AP 1206 (also referred to as "WLAN node 1206", "WLAN 1206", "WLAN terminal 1206", "WT 1206", etc.) via connection 1207. Connection 1207 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 1206 will include Wireless Fibre. Router. In this example, AP 1206 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 1201b, RAN 1210, and AP 1206 can be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1201b in an RRC_CONNECTED state, configured by RAN nodes 1211a-1211b to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 1201b using WLAN radio resources (e.g., connection 1207) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 1207. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0216] RAN 1210 includes one or more AN nodes or RAN nodes 1211a and 1211b (collectively referred to as "RAN node 1211") that enable connectivity between 1203 and 1204. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 1211 (e.g., gNB) operating in NR or 5G system 1200, while the terms "E-UT RAN node," etc., can refer to RAN node 1211 (e.g., eNB) operating in LTE or 4G system 1200. According to various implementation schemes, RAN node 1211 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity or higher bandwidth compared to macro cells.

[0217] In some implementations, all or part of RAN node 1211 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 1211; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 1211; or "lower PHY" partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes 1211. This virtualization framework allows idle processor cores of RAN node 1211 to execute other virtualized applications. In some specific implementations, a single RAN node 1211 may represent a virtual network via a single F1 interface (…). Figure 12 (Not shown) A separate gNB-DU connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio head units or RFEMs (see, for example...). Figure 13Furthermore, the gNB-CU can be operated by a server (not shown) located in RAN 1210 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more RAN nodes in RAN 1211 can be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminals to UE 1201 and are connected to 5GC via the ng interface (discussed below).

[0218] In a V2X scenario, one or more RAN nodes in RAN node 1211 can be RSUs or act as RSUs. The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside, which provides connectivity support to a passing vehicle UE 1201 (vUE 1201). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0219] Any node in RAN 1211 can terminate the air interface protocol and can be the first point of contact for UE 1201. In some implementations, any node in RAN 1211 can perform various logical functions of RAN 1210, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0220] In the implementation, UE 1201 may be configured to communicate with each other or with any of the RAN nodes 1211 on a multi-carrier communication channel using OFDM communication signals according to various communication technologies, such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0221] In some implementations, the downlink resource grid can be used for downlink transmissions from any node in RAN node 1211 to UE 1201, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0222] According to various implementations, UE 1201 and RAN node 1211 transmit data (e.g., send and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band. NR in the unlicensed spectrum may be referred to as NR-U, and LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0223] To operate in unlicensed spectrum, UE 1201 and RAN node 1211 may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 1201 and RAN node 1211 may perform one or more known medium sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0224] LBT is a mechanism that equipment (e.g., UE 1201, RAN node 1211, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when that medium is sensed to be idle (or when a specific channel in that medium is sensed to be unoccupied). Medium sensing operations may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0225] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1201, AP 1206, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between the X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0226] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0227] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides the PCC for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, and changing the PCC may require UE 1201 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (called "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0228] The PDSCH carries user data and higher-layer signaling to UE 1201. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 1201 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1201b within the cell) can be performed at any of the RAN nodes 1211 based on channel quality information fed back from any of the UEs 1201. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UE 1201.

[0229] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L = 1, 2, 4, or 8) can exist.

[0230] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0231] RAN nodes 1211 can be configured to communicate with each other via interface 1212. In an implementation where system 1200 is LTE system 12, interface 1212 can be an X2 interface 1212. The X2 interface can be defined between two or more RAN nodes 1211 connected to EPC 1220 (e.g., two or more eNBs, etc.), and / or between two eNBs connected to EPC 1220. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U can provide flow control mechanisms for user packets transmitted via the X2 interface and can be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from MeNB to SeNB; information about the successful in-order delivery of PDCP PDUs from SeNB to UE 1201 for user data; information about PDC PDUs not delivered to UE 1201; information about the current minimum expected buffer size at SeNB for transmitting user data to UE; and so on. The X2-C provides LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0232] In an implementation where system 1200 is a 5G or NR system 12, interface 1212 may be an Xn interface 1212. The Xn interface is defined between two or more RAN nodes 1211 (e.g., two or more gNBs, etc.) connected to 5GC 1220, between a RAN node 1211 (e.g., a gNB) connected to 5GC 1220 and an eNB, and / or between two eNBs connected to 5GC 1220. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 1201 in connected modes (e.g., CM connection) includes functions for managing UE mobility in connected modes between one or more RAN nodes 1211. Mobility support may include context transfer from the old (source) serving RAN node 1211 to the new (destination) serving RAN node 1211; and control of the user plane tunnel between the old (source) serving RAN node 1211 and the new (destination) serving RAN node 1211. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0233] RAN 1210 is shown as communication-coupled to the core network—in this embodiment, communication-coupled to the core network (CN) 1220. CN 1220 may include multiple network elements 1222 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 1201) connected to CN 1220 via RAN 1210. Components of CN 1220 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1220 may be referred to as a network slice, and a logical instance of a portion of CN 1220 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0234] Generally, application server 1230 can be a component that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 1230 can also be configured to support one or more communication services for UE 1201 via EPC 1220 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0235] In the implementation, CN 1220 may be a 5GC (referred to as "5GC 1220", etc.), and RAN 1210 may be connected to CN 1220 via NG interface 1213. In the implementation, NG interface 1213 may be divided into two parts: NG User Plane (NG-U) interface 1214, which carries traffic data between RAN node 1211 and UPF; and S1 Control Plane (NG-C) interface 1215, which is the signaling interface between RAN node 1211 and AMF 1212.

[0236] In one implementation, CN 1220 may be a 5G CN (referred to as "5GC 1220", etc.), while in other implementations, CN 1220 may be an EPC. When CN 1220 is an EPC (referred to as "EPC 1220", etc.), RAN 1210 may be connected to CN 1220 via S1 interface 1213. In another implementation, S1 interface 1213 may be divided into two parts: an S1 user plane (S1-U) interface 1214, which carries traffic data between RAN node 1211 and S-GW; and an S1-MME interface 1215, which is the signaling interface between RAN node 1211 and MME.

[0237] Figure 13 Examples of infrastructure equipment 1300 according to various embodiments are shown. Infrastructure equipment 1300 (or "system 1300") may be implemented as a base station, a radio head unit, a RAN node (such as RAN node 1211 and / or AP 1206 previously shown and described), an application server 1230, and / or any other element / device discussed herein. In other examples, system 1300 may be implemented in or by a UE.

[0238] System 1300 includes: application circuitry 1305, baseband circuitry 1310, one or more radio front-end modules (RFEMs) 1315, memory circuitry 1320, power management integrated circuit (PMIC) 1325, power tee circuitry 1330, network controller circuitry 1335, network interface connector 1340, satellite positioning circuitry 1345, and user interface circuitry 1350. In some embodiments, system 1300 may include additional components, such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be individually included in more than one device for CRAN, vBBU, or other similar implementations.

[0239] Application circuitry 1305 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low-dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a universal programmable serial interface module, a real-time clock (RTC), timers (including interval timers and watchdog timers), general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of application circuitry 1305 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1300. In some specific implementations, the memory / storage element may be an on-chip memory circuit, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0240] The processor of application circuit 1305 may include, for example, one or more processor cores (CPU), one or more application processors, one or more graphics processing units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuit 1305 may include or may be a dedicated processor / controller for operation according to the various embodiments described herein. As an example, the processor of application circuit 1305 may include one or more Apple A-series processors, or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, system 1300 may not utilize application circuitry 1305 and may instead include a dedicated processor / controller to process, for example, IP data received from an EPC or 5GC.

[0241] In some embodiments, application circuitry 1305 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. These hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, programmable processing devices may be one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 1305 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such implementations, the circuitry of application circuit 1305 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in lookup tables (LUTs).

[0242] The baseband circuit 1310 can be implemented, for example, as a soldered substrate, comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. See below for reference. Figure 15 This paper discusses the various hardware electronic components of the 1310 baseband circuit.

[0243] User interface circuitry 1350 may include one or more user interfaces designed to enable a user to interact with system 1300 or peripheral component interfaces, wherein the peripheral component interfaces are designed to enable peripheral components to interact with system 1300. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power interfaces, etc.

[0244] The radio front-end module (RFEM) 1315 may include a millimeter-wave (mmWave) RFEM and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some specific implementations, the one or more sub-millimeter-wave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example, below). Figure 15 The antenna array 1511 is used, and the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 1315 that combines both millimeter-wave and sub-millimeter-wave antennas.

[0245] The memory circuitry 1320 may include one or more of the following: volatile memory, including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as "flash memory"), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may be combined with... and A three-dimensional (3D) XPOINT memory. The memory circuit 1320 can be implemented as one or more of the following: a solder-in packaged integrated circuit, a socket memory module, and an insert memory card.

[0246] The PMIC 1325 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 1330 can provide electrical power drawn from the network cable to provide power and data connectivity to the infrastructure equipment 1300 using a single cable.

[0247] Network controller circuitry 1335 may provide connectivity to a network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol. Network connectivity may be provided to / from infrastructure equipment 1300 via a physical connection via network interface connector 1340; this physical connection may be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuitry 1335 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, network controller circuitry 1335 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0248] Positioning circuit 1345 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the U.S. Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler orbit charts and satellite integrated radio positioning (DORIS), etc.). Positioning circuit 1345 includes various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) for facilitating OTA communication to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, positioning circuit 1345 may include a micro-technology (micro PNT) IC for positioning, navigation, and timing, which performs position tracking / estimation using a master timing clock in the absence of GNSS assistance. The positioning circuit 1345 may also be part of or interact with the baseband circuit 1310 and / or RFEM 1315 to communicate with nodes and components of the positioning network. The positioning circuit 1345 may also provide location data and / or time data to the application circuit 1305, which may use the data to synchronize operations with various infrastructures, such as RAN node 1211.

[0249] Figure 13 The components shown can communicate with each other using interface circuitry, which may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI Express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0250] Figure 14 Examples of platform 1400 (or “device 1400”) according to various embodiments are shown. In embodiments, computer platform 1400 may be adapted to function as UE 1201, application server 1230, and / or any other element / device discussed herein. Platform 1400 may include any combination of the components shown in the examples. Components of platform 1400 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 1400, or may be implemented as components otherwise integrated within the chassis of a larger system. Figure 14The block diagram is intended to show a high-level view of the components of the computer platform 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific embodiments.

[0251] Application circuitry 1405 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: LDO, interrupt controller, serial interface (such as SPI), I2C or general programmable serial interface module, RTC, timers (including interval timers and watchdog timers), general-purpose I / O, memory card controller (such as SD MMC or similar controllers), USB interface, MIPI interface, and JTAG test access port. The processor (or core) of application circuitry 1405 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1400. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0252] The processor of application circuit 1305 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, application circuit 1305 may include or may be a dedicated processor / controller for operation according to various embodiments herein.

[0253] As an example, the processor of application circuit 1405 may include an Apple A-series processor. The processor of application circuit 1405 may also be one or more of the following: based on... Architecture Core TM processors, such as Quark TM Atom TM i3, i5, i7 or MCU-level processors, or available from Santa Clara, California. company( Another processor of this type from [Company Name], Santa Clara, CA; and Advanced Micro Devices (AMD). Processor or Accelerated Processing Unit (APU); from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments Open Multimedia ApplicationsPlatform(OMAP) TM Processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some specific implementations, the application circuit 1405 may be part of a system-on-a-chip (SoC), where the application circuit 1405 and other components are formed as a single integrated circuit.

[0254] In addition to or alternatively, application circuitry 1405 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 1405 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such embodiments, the circuitry of application circuitry 1405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuses, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs), etc.

[0255] The baseband circuit 1410 can be implemented, for example, as a soldered substrate, comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. (Refer to below) Figure 15 This paper discusses the various hardware electronic components of the baseband circuit 1410.

[0256] RFEM 1415 may include a millimeter-wave (mmWave) RFEM and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some specific implementations, the one or more sub-millimeter-wave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example, below). Figure 15 The antenna array 1511 is used, and the RFEM can be connected to multiple antennas. In an alternative embodiment, the radio functions of both millimeter wave and sub-millimeter wave can be implemented in the same physical RFEM 1415 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0257] Memory circuitry 1420 may include any number and type of memory devices for providing a fixed amount of system memory. For example, memory circuitry 1420 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. Memory circuitry 1420 may be developed according to designs based on Low Power Double Data Rate (LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc., as per the Joint Electronic Equipment Committee (JEDEC) design guidelines. The memory circuit 1420 may be implemented as one or more of the following: solder-in packaged integrated circuit, single-die package (SDP), dual-die package (DDP), or quad-die package (Q17P), socket memory module, dual in-line memory module (DIMM) including micro DIMM or mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 1420 may be an on-chip memory or register associated with the application circuit 1405. To provide persistent storage for information such as data, applications, operating systems, etc., the memory circuit 1420 may include one or more mass storage devices, which may include, in particular, solid-state drives (SSDDs), hard disk drives (HDDs), miniature HDDs, resistance-changing memories, phase-change memories, holographic memories, or chemical memories. For example, the computer platform 1400 may be integrated with... and 3D XPOINT memory.

[0258] The removable memory circuitry 1423 may include devices, circuitry, enclosures / housings, ports, or sockets for coupling portable data storage devices to the platform 1400. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, MicroSD cards, xD picture cards, etc.), as well as USB flash drives, optical discs, external HDDs, etc.

[0259] Platform 1400 may also include interface circuitry (not shown) for connecting external devices to platform 1400. External devices connected to platform 1400 via this interface circuitry include sensor circuitry 1421 and electromechanical components (EMC) 1422, as well as a removable memory device coupled to removable memory circuitry 1423.

[0260] Sensor circuit 1421 includes devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, and / or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0261] EMC 1422 includes devices, modules, or subsystems intended to enable platform 1400 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, EMC 1422 can be configured to generate messages / signaling and send messages / signaling to other components of platform 1400 to indicate the current state of EMC 1422. Examples of EMC 1422 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, propellers, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In embodiments, platform 1400 is configured to operate one or more EMC 1422s based on one or more captured events and / or commands or control signals received from a service provider and / or various clients.

[0262] In some implementations, the interface circuitry can connect platform 1400 to positioning circuitry 1445. Positioning circuitry 1445 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) may include the US GPS, Russia's GLONASS, the EU's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.). Positioning circuitry 1445 may include various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) for facilitating OTA communication to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some implementations, positioning circuitry 1445 may include a miniature PNT IC that performs position tracking / estimation using a master timing clock without GNSS assistance. Positioning circuitry 1445 may also be part of or interact with baseband circuitry 1310 and / or RFEM 1415 to communicate with nodes and components of the positioning network. The positioning circuit 1445 can also provide location data and / or time data to the application circuit 1405, which can use the data to synchronize operations with various infrastructures (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0263] In some implementations, this interface circuitry can connect platform 1400 to near-field communication (NFC) circuitry 1440. NFC circuitry 1440 is configured to provide contactless short-range communication based on radio frequency identification (RFID) standards, where magnetic field sensing is used to enable communication between NFC circuitry 1440 and NFC-enabled devices (e.g., “NFC contacts”) external to platform 1400. NFC circuitry 1440 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to NFC circuitry 1440 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals may power passive NFC tags (e.g., microchips embedded in stickers or wristbands) to transmit stored data to NFC circuitry 1440, or initiate data transfer between NFC circuitry 1440 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) located near platform 1400.

[0264] The driving circuitry 1446 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1400. The driving circuitry 1446 may include various drivers that allow other components of the platform 1400 to interact with or control various input / output (I / O) devices that may exist within or be connected to the platform. For example, the driving circuitry 1446 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 1400; a sensor driver for acquiring sensor readings of sensor circuitry 1421 and controlling and allowing access to sensor circuitry 1421; an EMC driver for acquiring actuator position of EMC 1422 and / or controlling and allowing access to EMC 1422; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0265] The power management integrated circuit (PMIC) 1425 (also referred to as "power management circuit 1425") manages the power supplied to various components of the platform 1400. Specifically, relative to the baseband circuit 1410, the PMIC 1425 controls power selection, voltage scaling, battery charging, or DC-DC conversion. The PMIC 1425 is typically included when the platform 1400 can be powered by the battery 1430, for example, when the device is included in the UE 1201.

[0266] In some implementations, the PMIC 1425 can be controlled or otherwise integrated into various power-saving mechanisms of the platform 1400. For example, if the platform 1400 is in an RRC connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive (DRX) after a period of inactivity. During this state, the platform 1400 can power down for short intervals to save power. If there is no data traffic activity for an extended period, the platform 1400 can transition to the RRC_Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 1400 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network and then power down again. The platform 1400 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0267] Battery 1430 can power platform 1400, but in some examples, platform 1400 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 1430 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, battery 1430 may be a typical lead-acid automotive battery.

[0268] In some implementations, battery 1430 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in platform 1400 to track the state of charge (SoCh) of battery 1430. The BMS can be used to monitor other parameters of battery 1430, such as the state of health (SoH) and state of function (SoF) of battery 1430, to provide fault prediction. The BMS can transmit information about battery 1430 to application circuitry 1405 or other components of platform 1400. The BMS may also include an analog-to-digital converter (ADC) that allows application circuitry 1405 to directly monitor the voltage of battery 1430 or the current from battery 1430. Battery parameters can be used to determine actions that platform 1400 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0269] A power block coupled to the grid or other power source can be coupled to the BMS to charge the battery 1430. In some examples, a wireless power receiver can replace the power block XS30 to wirelessly obtain power, for example, via a loop antenna in the computer platform 1400. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuitry chosen may depend on the size of the battery 1430 and therefore on the required current. Charging can be performed using the aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Radio Power Alliance, or the Rezence charging standard published by the Radio Power Alliance.

[0270] User interface circuitry 1450 includes various input / output (I / O) devices present within or connected to platform 1400, and includes one or more user interfaces designed to enable user interaction with platform 1400 and / or peripheral component interfaces designed to enable interaction with peripheral components of platform 1400. User interface circuitry 1450 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual device for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number and / or combination of audio or visual displays, particularly one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of platform 1400. Output device circuitry may also include speakers or other audio transmitting devices, printers, etc. In some embodiments, sensor circuitry 1421 may be used as input device circuitry (e.g., image capture devices, motion capture devices, etc.) and one or more EMCs may be used as output device circuitry (e.g., actuators for providing haptic feedback, etc.). In another example, NFC circuitry may be included for reading electronic tags and / or connecting to another NFC-enabled device, the NFC circuitry including an NFC controller and processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0271] Although not shown, components of Platform 1400 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be a proprietary bus / IX, for example, used in SoC-based systems. Other bus / IX systems may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0272] Figure 15 Exemplary components of a baseband circuit 1510 and a radio front-end module (RFEM) 1515 according to various embodiments are illustrated. The baseband circuit 1510 corresponds to... Figure 13 and Figure 14 The baseband circuits 1310 and 1410. RFEM 1515 corresponds to... Figure 13 and Figure 14 RFEMs 1315 and 1415. As shown, RFEM 1515 may include at least radio frequency (RF) circuitry 1506, front-end module (FEM) circuitry 1508, and antenna array 1511 coupled together as shown.

[0273] Baseband circuitry 1510 includes circuitry and / or control logic components configured to perform various radio / network protocols and radio control functions that enable communication with one or more radio networks via RF circuitry 1506. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1510 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1510 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments. Baseband circuitry 1510 is configured to process baseband signals received from the receive signal path of RF circuitry 1506 and to generate baseband signals for the transmit signal path of RF circuitry 1506. Baseband circuit 1510 is configured to work with application circuits 1305 / 1405 (see...) Figure 13 and Figure 14 The baseband circuit 1510 is connected to generate and process baseband signals and control the operation of the RF circuit 1506. The baseband circuit 1510 can handle various radio control functions.

[0274] The aforementioned circuitry and / or control logic components of the baseband circuitry 1510 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 1504A, a 4G / LTE baseband processor 1504B, a 5G / NR baseband processor 1504C, or other baseband processors 1504D for other existing, developing, or future generations (e.g., sixth generation (6G)). In other embodiments, some or all of the functions of the baseband processors 1504A-1504D may be included in modules stored in memory 1504G and executed via a central processing unit (CPU) 1504E. In other embodiments, some or all of the functions of the baseband processors 1504A-1504D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various implementations, memory 1504G may store program code for a real-time operating system (RTOS), which, when executed by CPU 1504E (or other baseband processor), will enable CPU 1504E (or other baseband processor) to manage resources of baseband circuitry 1510, schedule tasks, etc. Examples of RTOS may include those developed by... The provided Operating System Embedded (OSE) TM By Mentor Nucleus RTOS provided TM By Mentor The provided Versatile Real-Time Executive (VRTX) is by Express. ThreadX provided TM ,Depend on The provided FreeRTOS and REX OS are based on the Open Kernel (OK). The provided OKL4, or any other suitable RTOS, such as those discussed herein. Furthermore, the baseband circuitry 1510 includes one or more audio digital signal processors (DSPs) 1504F. The audio DSP 1504F includes elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements.

[0275] In some implementations, each processor in processors 1504A-1504E includes a corresponding memory interface for sending data to / receiving data from memory 1504G. Baseband circuitry 1510 may also include one or more interfaces for communicatively coupling to other circuitry / devices, such as interfaces for sending data to / receiving data from memory external to baseband circuitry 1510; and interfaces for sending data to / receiving data from memory external to baseband circuitry 1510. Figures 13 to 14 Application circuit interface for sending / receiving data from application circuit 1305 / 1405; used for sending data to / receiving data from application circuit 1305 / 1405. Figure 15 RF circuit 1506 is an RF circuit interface for transmitting / receiving data from / from one or more wireless hardware components (e.g., near field communication (NFC) components). Low power components A wireless hardware connection interface for transmitting data to / receiving data from these wireless hardware components; and a power management interface for transmitting power or control signals to / receiving power or control signals from the PMIC 1425.

[0276] In an alternative embodiment (which may be combined with the embodiments described above), baseband circuitry 1510 includes one or more digital baseband systems coupled to each other and to a CPU subsystem, an audio subsystem, and an interface subsystem via interconnect subsystems. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, a network-on-chip (NOC) architecture, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital converter circuitry and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and / or other similar components. In one aspect of this disclosure, baseband circuitry 1510 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and / or radio frequency circuitry (e.g., radio front-end module 1515).

[0277] although Figure 15Not shown, but in some embodiments, baseband circuitry 1510 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when baseband circuitry 1510 and / or RF circuitry 1506 are part of millimeter-wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry can operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when baseband circuitry 1510 and / or RF circuitry 1506 are part of a Wi-Fi communication system, the protocol processing circuitry can operate one or more IEEE-based protocols. In the second example, the protocol processing circuitry will operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 1504G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using the data. The baseband circuitry 1510 may also support radio communication using more than one wireless protocol.

[0278] The various hardware components of the baseband circuit 1510 discussed herein can be implemented, for example, as a solderable substrate comprising one or more integrated circuits (ICs), a single-packaged IC soldered to a main board, or a multi-chip module containing two or more ICs. In one example, components of the baseband circuit 1510 may be suitably combined in a single chip or a single chipset, or disposed on the same board. In another example, some or all of the components of the baseband circuit 1510 and the RF circuit 1506 may be implemented together, such as, for example, a system-on-a-chip (SoC) or a system-in-package (SiP). In yet another example, some or all of the components of the baseband circuit 1510 may be implemented as a separate SoC communicatively coupled to the RF circuit 1506 (or multiple instances of the RF circuit 1506). In yet another example, some or all of the components of the baseband circuit 1510 and the application circuits 1305 / 1405 may be implemented together as a separate SoC mounted to the same board (e.g., a “multi-chip package”).

[0279] In some implementations, baseband circuit 1510 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1510 can support communication with E-UTRAN or other WMAN, WLAN, WPAN. Implementations in which baseband circuit 1510 is configured to support radio communication with more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0280] RF circuit 1506 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1506 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1506 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 1508 and providing a baseband signal to baseband circuit 1510. RF circuit 1506 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1510 and providing an RF output signal for transmission to FEM circuit 1508.

[0281] In some embodiments, the receive signal path of RF circuit 1506 may include mixer circuit 1506a, amplifier circuit 1506b, and filter circuit 1506c. In some embodiments, the transmit signal path of RF circuit 1506 may include filter circuit 1506c and mixer circuit 1506a. RF circuit 1506 may also include synthesizer circuit 1506d for synthesizing the frequency used by mixer circuit 1506a in both the receive and transmit signal paths. In some embodiments, mixer circuit 1506a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1508 based on the synthesized frequency provided by synthesizer circuit 1506d. Amplifier circuit 1506b may be configured to amplify the down-converted signal, and filter circuit 1506c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1510 for further processing. In some implementations, although not required, the output baseband signal may be a zero-frequency baseband signal. In some implementations, the mixer circuit 1506a in the receiving signal path may include a passive mixer, but the scope of the implementations is not limited in this respect.

[0282] In some implementations, the mixer circuit 1506a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1506d to generate an RF output signal for the FEM circuit 1508. The baseband signal can be provided by the baseband circuit 1510 and can be filtered by the filter circuit 1506c.

[0283] In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and quadrature upconversion, respectively. In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may be configured for superheterodyne operation.

[0284] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1510 may include a digital baseband interface for communicating with the RF circuit 1506.

[0285] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0286] In some implementations, synthesizer circuit 1506d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1506d may be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0287] Synthesizer circuit 1506d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1506a of RF circuit 1506. In some embodiments, synthesizer circuit 1506d can be a fractional N / N+1 synthesizer.

[0288] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1510 or the application circuit 1305 / 1405 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1305 / 1405.

[0289] The synthesizer circuit 1506d of the RF circuit 1506 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0290] In some embodiments, the synthesizer circuit 1506d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 1506 may include an IQ / polarity converter.

[0291] FEM circuit 1508 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 1511, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1506 for further processing. FEM circuit 1508 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1506 for transmission by one or more antenna elements in antenna array 1511. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1506, only in FEM circuit 1508, or in both RF circuit 1506 and FEM circuit 1508.

[0292] In some embodiments, FEM circuit 1508 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 1508 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 1508 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 1506). The transmit signal path of FEM circuit 1508 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 1506), and one or more filters for generating the RF signal for subsequent transmission by one or more antenna elements of antenna array 1511.

[0293] Antenna array 1511 includes one or more antenna elements, each configured to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. For example, a digital baseband signal provided by baseband circuit 1510 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 1511, which includes one or more antenna elements (not shown). Antenna elements can be omnidirectional, directional, or a combination thereof. Antenna elements can be arranged in various configurations as known and / or discussed herein. Antenna array 1511 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. Antenna array 1511 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to RF circuit 1506 and / or FEM circuit 1508 using metal transmission lines, etc.

[0294] The processors of application circuitry 1305 / 1405 and baseband circuitry 1510 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuitry 1510 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 1305 / 1405 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include the MAC layer, RLC layer, and PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which will be described in further detail below.

[0295] While this specification contains numerous specific implementation details, these details should not be construed as limiting the scope of the claims, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of different embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, while some features may be described above as functioning in certain combinations and even initially claimed in this manner, one or more features of a claimed combination may be removed from that combination in certain circumstances, and the claimed combination may involve sub-combinations or variations thereof.

[0296] Similarly, although operations are shown in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in a sequential order or the specific order shown, or requiring all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the division of various system modules and components in the above embodiments should not be construed as requiring such division in all embodiments, and it should be understood that the program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0297] Specific embodiments of the invention have been described. Other embodiments are also within the scope of the following claims. For example, the steps set forth in the claims, described in the specification, or depicted in the drawings may be performed in a different order and still achieve the desired result. In some cases, multitasking and parallel processing may be advantageous.

Claims

1. A method comprising: The first device identifies the switching of a first link between the first device and the second device from a first bandwidth portion to a second bandwidth portion, the first link being associated with a second link having a third bandwidth portion; The first device determines whether the bandwidth between the second bandwidth portion and the third bandwidth portion meets the threshold protection band. as well as Using the result of determining whether the bandwidth band between the second bandwidth portion and the third bandwidth portion meets the threshold protection band, it is selectively determined whether to maintain the third bandwidth portion for the second link or to switch the third bandwidth portion to the fourth bandwidth portion for the second link.

2. The method according to claim 1, comprising: The first device determines that the bandwidth band between the second bandwidth portion and the third bandwidth portion satisfies the threshold protection band, wherein selective determination includes, in response to determining that the bandwidth band between the second bandwidth portion and the third bandwidth portion satisfies the threshold protection band, selectively determining to maintain the third bandwidth portion for the second link.

3. The method of claim 2, wherein determining that the bandwidth between the second bandwidth portion and the third bandwidth portion satisfies the threshold protection band includes determining that the bandwidth between the second bandwidth portion and the third bandwidth portion is greater than, equal to, or greater than or equal to the threshold protection band.

4. The method according to claim 1, comprising: The first device determines that the bandwidth band between the second bandwidth portion and the third bandwidth portion does not meet the threshold protection band, wherein selective determination includes, in response to determining that the bandwidth band between the second bandwidth portion and the third bandwidth portion does not meet the threshold protection band, selectively determining to switch the third bandwidth portion to the fourth bandwidth portion for the second link.

5. The method of claim 4, wherein determining that the bandwidth between the second bandwidth portion and the third bandwidth portion does not satisfy the threshold protection band includes determining that the bandwidth between the second bandwidth portion and the third bandwidth portion is less than, equal to, or less than or equal to the threshold protection band.

6. The method of claim 1, wherein identifying the switching includes identifying a switching from a first partition duplex type to a second partition duplex type.

7. The method of claim 6, wherein identifying the handover from the first partition duplex type to the second partition duplex type includes identifying the handover from time division duplex to frequency division duplex.

8. The method of claim 6, wherein identifying the handover from the first partition duplex type to the second partition duplex type includes identifying the handover from frequency division duplex to time division duplex.

9. The method of claim 1, wherein the first device comprises a next-generation node B, and the second device comprises user equipment.

10. The method of claim 1, wherein the first link comprises a downlink and the second link comprises an uplink.

11. The method of claim 1, wherein the first link includes an uplink and the second link includes a downlink.

12. A non-transitory computer storage medium encoded with instructions that, when executed by one or more baseband processors, cause the one or more baseband processors to perform the method according to any of the preceding claims.

13. A system comprising one or more baseband processors and one or more storage devices, the one or more storage devices storing operable instructions that, when executed by the one or more baseband processors, cause the one or more baseband processors to perform the method according to any one of claims 1 to 11.

Images