Patent Application
20250038837
The present disclosure relates to measurement in non-terrestrial network.
To meet the increasing demand for wireless data traffic since the commercialization of 4th generation (4G) communication systems, the 5th generation (5G) system is being developed. For the sake of high data rate, 5G system introduced millimeter wave (mmW) frequency bands (e. g. 60 GHz bands). In order to increase the propagation distance by mitigating propagation loss in the 5G communication system, various techniques are introduced such as beamforming, massive multiple-input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna. In addition, base station is divided into a central unit and plurality of distribute units for better scalability. In addition, in the 5G communication system, a non-terrestrial network is introduced with the goal of supporting a very high data rate and very low transmission delay in order to support various services.
To increase the coverage of 5G communication system, non-terrestrial network is introduced wherein part of the communication link is established between terminal and satellite. To tackle the long propagation delay in the NTN, various enhancements are required.
Aspects of the present disclosure are to address measurement operation in non-terrestrial network. The method includes receiving a measurement object configuration comprising a first SMTC and a third SMTC list, setting up a first SS/PBCH block timing configuration for said measurement object based on the first SMTC, setting up additional SS/PBCH block timing configurations based on the first SMTC and the third SMTC list for the cells indicated in said pci-List parameter and deriving a measurement result based on the SS/PBCH block.
FIG. IF is a diagram illustrating SS/PBCH.
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, in the description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.
The terms used, in the following description, for indicating access nodes, network entities, messages, interfaces between network entities, and diverse identity information is provided for convenience of explanation. Accordingly, the terms used in the following description are not limited to specific meanings but may be replaced by other terms equivalent in technical meanings.
In the following descriptions, the terms and definitions given in the 3GPP standards are used for convenience of explanation. However, the present disclosure is not limited by use of these terms and definitions and other arbitrary terms and definitions may be employed instead.
Table 1 lists the acronyms used throughout the present disclosure.
Table 2 lists the terminologies and their definition used throughout the present disclosure.
In the present invention, “trigger” or “triggered” and “initiate” or “initiated” can be used interchangeably.
In the present invention, UE and terminal can be used interchangeably. In the present invention, NG-RAN node and base station can be used interchangeably.
The gNBs 1A-05 or 1A-06 and ng-eNBs 1A-03 or 1A-04 are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) and to the UPF (User Plane Function). AMF 1A-07 and UPF 1A-08 may be realized as a physical node or as separate physical nodes.
A gNB 1A-05 or 1A-06 or an ng-eNBs 1A-03 or 1A-04 hosts the functions listed below.
Functions for Radio Resource Management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling); and
IP and Ethernet header compression, uplink data decompression and encryption of user data stream; and
Selection of an AMF at UE attachment when no routing to an MME can be determined from the information provided by the UE; and
Routing of User Plane data towards UPF; and
Scheduling and transmission of paging messages; and
Scheduling and transmission of broadcast information (originated from the AMF or O&M); and
Measurement and measurement reporting configuration for mobility and scheduling; and
Session Management; and
QoS Flow management and mapping to data radio bearers; and
Support of UEs in RRC_INACTIVE state; and
Radio access network sharing; and
Tight interworking between NR and E-UTRA; and
Support of Network Slicing.
The AMF 1A-07 hosts the functions such as NAS signaling, NAS signaling security, AS security control, SMF selection, Authentication, Mobility management and positioning management.
The UPF 1A-08 hosts the functions such as packet routing and forwarding, transport level packet marking in the uplink, QoS handling and the downlink, mobility anchoring for mobility etc.
User plane protocol stack consists of SDAP 1B-01 or 1B-02, PDCP 1B-03 or 1B-04, RLC 1B-05 or 1B-06, MAC 1B-07 or 1B-08 and PHY 1B-09 or 1B-10. Control plane protocol stack consists of NAS 1B-11 or 1B-12, RRC 1B-13 or 1B-14, PDCP, RLC, MAC and PHY.
Each protocol sublayer performs functions related to the operations listed in the table 3.
The terminal supports three RRC states. Table 4 lists the characteristics of cach state.
Between RRC_CONNECTED 1C-11 and RRC_INACTIVE 1C-13, a state transition occurs due to the exchange of the Resume message and the Release message containing the Suspend IE.
A state transition occurs between RRC_CONNECTED 1C-11 and RRC_IDLE 1C-15 through RRC connection establishment and RRC connection release.
SuspendConfig IE includes the following information.
<SuspendConfig>
1. The first terminal identifier: an identifier of a terminal that may be included in the ResumeRequest when a state transition to RRC_CONNECTED is made. It has a 40-bit length.
2. The second terminal identifier: an identifier of a terminal that may be included in the Resume Request when a state transition to RRC_CONNECTED is made. It has a 24-bit length.
3. ran-Paging Cycle: Paging cycle to be applied in RRC_INACTIVE state.
4. ran-Notification AreaInfo: Configuration information of a ran-Notification Area consisting of a list of cells and the like. The terminal initiates a resume procedure when the ran_Notification Area is changed.
5. t380: Timer related to the periodic resumption procedure.
6. NextHopChangingCount (NCC): Counter used to derive new security keys after performing the resume procedure.
7. Extended-ran-Paging-Cycle: Paging cycle to be applied in RRC_INACTIVE when extended DRX is configured. It indicates one of predefined values: rf256, rf512,rf1024 and a reserved value.
FIG.1D is a diagram illustrating architecture of NTN.
A non-terrestrial network refers to a network, or segment of networks using RF resources on board a satellite (or UAS platform).
The typical scenario of a non-terrestrial network providing access to user equipment is depicted in FIG.1D.
Non-Terrestrial Network typically consists of the following elements:
One or several sat-gateways 1D-19 that connect the Non-Terrestrial Network to a public data network 1D-21. A Feeder link 1D-17 or radio link between a sat-gateway and the satellite. A service link 1D-13 or radio link between the user equipment and the satellite. A satellite 1D-15 providing RF resource. User Equipment 1D-11 served by the satellite within the targeted service area.
FIG.1E is a diagram illustrating protocol architecture of NTN.
Satellite 1E-11 or 1E-21 and NTN gateway 1E-13 and 1E-23 are equipped with RF processing & Frequency Switching to relay the signal between gNB and UE. Other protocols such as SDAP, PDCP, RLC, MAC, PHY, RRC, NAS are same as used in normal terrestrial network.
FIG.1F is a diagram illustrating SS/PBCH.
The Synchronization Signal and PBCH block (SSB) consists of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols 1F-05 and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS as show in Figure IF. The possible time locations of SSBs within a half-frame are determined by sub-carrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell).
The length of a half-frame is 5 ms. The periodicity of a half-frame is 5 ms or 10 ms or 20 ms or 40 ms or 80 ms or 160 ms. UE tries to measure SSBs during the half-frame. Base station can configure UE with SMTC for SSB measurement. SMTC can be configured in accordance with the half-frame.
In general, half-frames of cells in a same frequency are synchronized. Hence only one SMTC is required. However, in NTN, due to long propagation delay half-frames between neighbour cells can be received in different point of time depending on UE location. It requires plurality of SMTCs if UE needs to measure plurality of neighbor cells.
FIG.2A is a diagram illustrating the operation of UE and GNB according to the embodiment of the invention.
In 2A-11, GNB 2A-07 determines measurement configuration for UE 2A-01. GNB transmits, to UE via NTN gateway 2A-05 and Satellite 2A-03, RRCReconfiguration message. RRCReconfiguration message includes measConfig IE based on determined measurment configuration. measConfig IE includes plurality of measObject IEs and plurality of ReportConfig IEs and plurality of MeasIdToAddMod IEs. a MeasObject IE specifies information applicable for SSBs intra/inter-frequency measurements. a MeasObject IE includes following IEs; ssbFrequency IE, ssbSubcarrierSpacing IE, smtcl IE, smtc2 IE, smtc3list IE, ssb-ToMeasure IE, etc. smtcl is primary measurement timing configuration for SS Synchronization Signal). smtc2 is secondary measurement timing configuration for SS. smtc3list is measurement timing configuration list for SS corresponding to neighbor cells having different SSB time patterns. ssbFrequency IE indicates the frequency of the SS associated to this MeasObjectNR. ssbSubcarrierSpacing is subcarrier spacing of SSB. ssb-ToMeasure is the set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value O in the bitmap indicates that the corresponding SS/PBCH block is not to be measured while value 1 indicates that the corresponding SS/PBCH block is to be measured. ReportConfig IE specifies criteria for triggering of an NR measurement reporting event or of a CHO (Conditional Handover) event. A ReportConfig IE comprises a reportType IE. A reportType IE may include one of eventTriggered IE and condTriggerConfig IE. A eventTriggered IE specifies criteria for triggering of a measurement reporting event. A condTriggerConfig IE specifies criteria for triggering of a CHO event.
A MeasIdToAddMod includes a measId and a measObjectId and a reportConfigId. The measId is associated with the measObject indicated by the measObjectId and the reportConfig indicated by the reportConfigId.
GNB can determine to configure UE with conditional reconfiguration. GNB includes plurality of CondReconfigToAddMod IEs in the RRCReconfiguration messsage, if determined so. A CondReconfigToAddMod IE includes following IEs; a condReconfigId IE, a condExecutionCond IE and a condRRCReconfig IE.
A condExecutionCond IE is the execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for a candidate cell. When configuring 2 triggering events (Meas Ids) for a candidate cell, if both events are related to reference signal measurement, network ensures that both refer to the same measObject.
A condRRCReconfig IE is the RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message includes the configuration information of a candidate target cell.
In 2A-13, UE configure measurement timing configuration based on received measConfig IE. For each measObject IE included in the measConfig IE. UE setup SMTC (SS/PBCH block measurement timing configuration) for each measObject based on smtc1, smtc 2 and smtc3 list. smtcl comprises a SSB-MTC (Measurement Timing Configuration) IE. A SSB-MTC IE includes a periodicity AndOffset IE and a duration IE. It is a primary measurement timing configuration.
smtc2 comprises a SSB-MTC2 IE. A SSB-MTC2 IE includes pci-List IE and periodicity IE. It is a secondary measurement timing configuration applied to the cells listed in pci-List. The secondary measurement timing configuration has a different periodicity and a same offset comparing to the primary measurement timing configuration. smtc2 is an optional IE.
smtc3List IE comprises plurality of SSB-MTC3 IEs. a SSB-MTC3 IE includes a pci-List IE and a offset IE. smtc3List is used for the case where neighbor cell's offset is different, due to significantly different propagation delay, from what is indicated by the primary measurement timing. It is mainly used in NTN network. smtc3List is an optional IE. If smtc3List IE is present and smtel IE is not present in a measObject IE, UE is unable to comply with RRCReconfiguration and initiates the connection re-establishment procedure.
UE setup the first SMTC in accordance with the received periodicity AndOffset parameter in the smtcl configuration.
The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the following condition:
periodicity and offset are derived from periodicityAndOffset IE. A periodicityAndOffset IE is an integer chosen from a integer set. Six integer sets are defined for periodicityAndOffset. The lowest integer is 0 for all six integer sets. The highest value of six integer sets are 4, 9, 19, 39, 79 and 159 respectively. If the integer is chosen from the integer set with highest value of n, periodicity is sf_n+1 and the offset is the chosen integer. For example, if integer 15 is chosen from the integer set with highest value of 159,periodicity is sf160 and the offset is 15.
sf5 is five subframes, sf10 is ten subframes and so on.
If smtc2 is present, for cells indicated in the pci-List parameter in smtc2 in the same
MeasObject, the UE shall setup an additional SMTC in accordance with the received periodicity parameter in the smtc2 configuration and use the Offset and duration parameter from the smtc 1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition.
If smtc3list is present, for cells indicated in the pci-List parameter in each SSB-MTC3element of the list in the same MeasObject IE, the UE shall setup an additional SS block measurement timing configuration in accordance with the received offset parameter from each SSB-MTC3 configuration and use the periodicity and duration parameters from the smtcl configuration. The first subframe of each SMTC occasion of each SSB-MTC3configuration occurs at an SFN and subframe of the NR SpCell meeting the above condition.
The offset IE of each SSB-MTC3 is an integer selected (or determined) from the same integer set as used in the smtcl for the periodicity determination.
If smtc3list is present, UE setup an additional SS block measurement timing configuration for each SSB-MTC3 element in accordance with the received offset parameter from each SSB-MTC3 element and in accordance with the periodicity and the duration from smtc1 IE. In other words, offset parameter of a SSB-MTC3 clement is valid for (and applied to setup) SS block measurement timing configuration of the SSB-MTC3 element. duration parameter of smtcl IE is valid for (and applied to setup) SS block measurement timing configuration of the smtcl IE and SS block measurement timing configurations of the plurality of SSB-MTC3 elements in the same measObject IE. periodicity determined based on periodicity AndOffset IE of a smtcl IE is valid for (and applied to) SS block measurement timing configuration of the smtel IE and SS block measurement timing configurations of the plurality of SSB-MTC3 elements in the same measObject IE.
In 2A-15, UE performs measurement for SS/PBCH block during the SMTC occasions established in step 2A-13. UE derives cell measurement results based on measurements on SS/PBCH blocks during the SMTC occasions.
In 2A-17, UE determines for each measId if the event corresponding with the eventId of the corresponding reportConfig is fulfilled. UE initiate the measurement reporting procedure for the measId if the event is fulfilled.
A reportConfig IE can include an eventTriggered IE. An eventTriggered IE includes an eventId IE and a rsType IE. A rsType IE indicates one of ssb and csi-rs. UE performs measurement on the indicated reference signal. An eventId IE is defined for each of following event types.
Event A1: Serving becomes better than absolute threshold;
Event A2: Serving becomes worse than absolute threshold;
Event A3: Neighbour becomes amount of offset better than PCell/PSCell;
Event A4: Neighbour becomes better than absolute threshold;
Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2;
Event A6: Neighbour becomes amount of offset better than SCell;
Event D1: Distance between UE and a reference location referenceLocation1 becomes larger than configured threshold Thresh 1 and distance between UE and a reference location referenceLocation2 becomes shorter than configured threshold Thresh2
For event DI, An eventId IE includes distanceThresFromReferencel IE, distance ThresFromReference2 IE, referenceLocation1 IE, referenceLocation2 IE and HysteresisLocation IE.
distanceThresFromReference1 indicates a first distance threshold in meter. distanceThresFromReference2 indicates a second distance threshold in meter. referenceLocation1 is a GNSS coordinates and indicates the location of the first reference.
referenceLocation2 is a GNSS coordinates and indicates the location of the second reference. HysteresisLocation is the hysteresis in meter.
The UE consider the entering condition for event D1 to be satisfied when both conditions are fulfilled.
Alternatively, the conditions can be defined by applying the hysteresis only to one condition as below.
measured location 1>distanceThresFromReference1; AND
measured location 2 is the UE location represented by the distance between UE and a reference location parameter for this event (i.e., referenceLocation2 as defined within reportConfigNR this event).
UE determines for each measId included in the condExecutionCond IE associated to conReconfigId if the event corresponding with the condEventId of the corresponding condTriggerConfig is fulfilled. UE initiate the conditional reconfiguration execution for a target canddidate cell if the events associated to all measIds within condTriggerConfig for the target candidate cell are fulfilled.
A reportConfig IE associated with the measId within the condExecutionCond IE includes a condTriggerConfig IE. A condTriggerConfig IE includes a condEventId IE and a rsType IE. A rsType IE indicates one of ssb and csi-rs. UE performs measurement on the indicated reference signal. A condEventId IE is defined for each of the following conditional event types.
CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell;
CondEvent A4: Conditional reconfiguration candidate becomes better than absolute threshold;
CondEvent A5: PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2;
CondEvent D1: Distance between UE and a reference location referenceLocation1becomes larger than configured threshold Thresh 1 and distance between UE and a reference location referenceLocation2 of conditional reconfiguration candidate becomes shorter than configured threshold Thresh2;
CondEvent T1: Time measured at UE becomes more than configured threshold
Thresh 1but is less than Thresh2;
For CondEevent D1, a condEventId IE includes distanceThresFromReferencel IE, distanceThresFromReference2 IE, referenceLocation1 IE, referenceLocation2 IE and HysteresisLocation IE.
The UE consider the entering condition for CondEvent DI to be satisfied when two conditions for Event D1 are fulfilled.
For CondEvent A5, condEventId includes following IEs; a5-Threshold1, a5-Threshold2and hysteresis.
The UE consider the entering condition for CondEvent A5 to be satisfied when both conditions are fulfilled.
Measurement result of the NR SpCell+Hysteresis<a5-Threshold1; AND
Measurement result of the neighbouring cell+measurement object specific offset of the neighbouring cell+cell specific offset of the neighbouring cell−Hysteresis>a5-Threshold2measurement object specific offset and cell specific offset of the neighbouring cell are included in the corresponding measObject IE.
The UE variable VarMeasConfig includes the accumulated configuration of the measurements to be performed by the UE, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements. VarMeasConfig includes a list of measIds, a list of measObjects, a list of reportConfig, etc.
The UE variable VarConditionalReconfig includes the accumulated configuration of the conditional handover or conditional PSCell change configurations including the pointers to conditional handover or conditional PSCell change execution condition (associated measld(s)) and the stored target candidate SpCell RRCReconfiguration.
VarConditionalReconfig includes a list of CondReconfigToAddModList.
For each condReconfigId within the VarConditionalReconfig, UE consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync in the received condRRCReconfig to be applicable cell.
For each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond associated to condReconfigId, UE consider the event associated to that measId to be fulfilled if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig (or condExecutionCond) within VarConditionalReconfig, is fulfilled for the applicable cells.
If event(s) associated to all measId(s) within condTriggerConfig (or condExecutionCond) for a target candidate cell within the stored condRRCReconfig are fulfilled, UE consider the target candidate cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell;
If more than one triggered cell exists, UE selects one of the triggered cells as the selected cell for conditional reconfiguration execution.
If two measIds are included in condExecutionCond associated with a condReconfigId and if one measId is associated with CondEvent A5 and the other measId is associated with the CondEvent DI, UE considers the target canddidate cell associated with the condReconfigId as a triggered cell when four conditions (two associated with the first MeasId and two associated with the second MeasId) are fulfilled.
If two events are specified for a conditional reconfiguration (or conditional handover), and if the first event is CondEvent A5 and the second event is CondEventDI, the conditional reconfiguration is executed when four conditions are fulfilled simultaneously.
Both events can refer to a different measObject if one of the events is CondEventD1 or CondEventT1.
In 2A-19, UE generates a MeasurementReport message based on the measurement result on the measurement object. This step is skipped if conditional reconfiguration is executed.
UE sets a measId field of the MeasurementReport message to the measurement identity that triggered the measurement reporting.
UE sets a measurement result serving cell field of the Measurement Report message to include RSRP and RSRQ and the available SINR of PCell based on the rsType indicated in the associated ReportConfig.
UE sets a location field of the MeasuremntReport message to include the distance between UE and the first reference location and the distance between UE and the second reference location if the measId is associated with event D1.
In 2A-21, UE transmits the MeasurementReport message to the GNB via Satellite 2A-03 and NTN gateway 2A-05, if measurement reporting proceudre is initiated.
UE appliies the condRRCReconfig of the selected (target candidate) cell if conditional reconfiguration is executed. FIG.3A illustrates the operation of the terminal. In step 3A-11, the terminal receives a measurement object configuration from the base station.
In step 3A-13, the terminal sets up a first SS/PBCH block timing configuration for said measurement object according to a duration parameter in the first SMTC and a first offset and first period determined based on joint parameters.
In step 3A-15, if a third SMTC list is included in said measurement object configuration, the terminal sets up additional SS/PBCH block timing configurations for the cells indicated in said pci-List parameter included in each SSB-MTC3 element of said third SMTC settings list based on said first period and said first duration and second offset. In steps 3A-17, the terminal derives a measurement result based on the SS/PBCH block.
Said measurement object configuration includes said first SMTC and said third SMTC list. Said first SMTC comprises said joint parameter and said duration parameter. Said third SMTC list comprises at least one of said SSB-MTC3 elements. Said at least one SSB-MTC3 element comprises one said pci-List and one offset parameter.
Said second offset is determined based on said offset parameter included in said respective SSB-MTC3 element.
If a second SMTC is included in said measurement object configuration, additional SS/PBCH block timing setting is established based on said first offset and said first duration and second period, said second period being determined based on a period parameter included in said second SMTC.
Said third smtc list comprises a plurality of SSB-MTC3 elements, each of said SSB-MTC3 elements comprising one pci-List and one offset parameter.
Said offset parameter of said SSB-MTC3 is an integer between 0 and a certain value, wherein said certain value is equal to the value of the first period minus 1.
Said offset parameter of said SSB-MTC3 is an integer between 0 and a certain value, wherein said certain value is equal to the highest value of the set of integers having the most highest value minus one.
Wherein said set of integers is one of a plurality of integer sets, and wherein the first cycle is determined based on said plurality of integer sets.
If the list of the third SMTC and the first SMTC are included in one measurement object setting, but the first SMTC is not, a connection re-establishment procedure is initiated.
Referring to the diagram, the UE includes a controller 4A-01, a storage unit 4A-02, a transceiver 4A-03, a main processor 4A-04 and I/O unit 4A-05.
The controller 4A-01 controls the overall operations of the UE in terms of mobile communication. For example, the controller 4A-01 receives/transmits signals through the transceiver 4A-03. In addition, the controller 4A-01 records and reads data in the storage unit 4A-02. To this end, the controller 4A-01 includes at least one processor. For example, the controller 4A-01 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls the upper layer, such as an application program. The controller controls storage unit and transceiver such that UE operations illustrated in
The storage unit 4A-02 stores data for operation of the UE, such as a basic program, an application program, and configuration information. The storage unit 4A-02 provides stored data at a request of the controller 4A-01.
The transceiver 4A-03 consists of a RF processor, a baseband processor and one or more antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up-converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a milOr, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. The RF processor may perform MIMO and may receive multiple layers when performing the MIMO operation. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.
The main processor 4A-04 controls the overall operations other than mobile operation. The main processor 4A-04 process user input received from I/O unit 4A-05, stores data in the storage unit 4A-02, controls the controller 4A-01 for required mobile communication operations and forward user data to I/O unit 4A-05.
I/O unit 4A-05 consists of equipment for inputting user data and for outputting user data such as a microphone and a screen. I/O unit 4A-05 performs inputting and outputting user data based on the main processor's instruction.
As illustrated in the diagram, the base station includes a controller 4B-01, a storage unit 4B-02, a transceiver 4B-03 and a backhaul interface unit 4B-04.
The controller 4B-01 controls the overall operations of the main base station. For example, the controller 4B-01 receives/transmits signals through the transceiver 4B-03, or through the backhaul interface unit 4B-04. In addition, the controller 4B-01 records and reads data in the storage unit 4B-02. To this end, the controller 4B-01 may include at least one processor. The controller controls transceiver, storage unit and backhaul interface such that base station operation illustrated in
The storage unit 4B-02 stores data for operation of the main base station, such as a basic program, an application program, and configuration information. Particularly, the storage unit 4B-02 may store information regarding a bearer allocated to an accessed UE, a measurement result reported from the accessed UE, and the like. In addition, the storage unit 4B-02 may store information serving as a criterion to determine whether to provide the UE with multi-connection or to discontinue the same. In addition, the storage unit 4B-02 provides stored data at a request of the controller 4B-01.
The transceiver 4B-03 consists of a RF processor, a baseband processor and one or more antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up-converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down—converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a milOr, an oscillator, a DAC, an ADC, and the like. The RF processor may perform a down link MIMO operation by transmitting at least one layer. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.
The backhaul interface unit 4B-04 provides an interface for communicating with other nodes inside the network. The backhaul interface unit 4B-04 converts a bit string transmitted from the base station to another node, for example, another base station or a core network, into a physical signal, and converts a physical signal received from the other node into a bit string.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0173208 | Dec 2021 | KR | national |
This application is a continuation of U.S. application Ser. No. 18/597,968, filed on March. 7, 2024, which is a continuation of International Application No. PCT/KR2022/018853, filed on Nov. 25, 2022, which claims priority to and the benefit of Korean Patent Application No. 10-2021-0173208, filed on Dec. 6, 2021. The entire content of each of these applications is incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18597968 | Mar 2024 | US |
| Child | 18918255 | US | |
| Parent | PCT/KR2022/018853 | Nov 2022 | WO |
| Child | 18597968 | US |
