Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
  • H04W8/24—Transfer of terminal data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/11—Allocation or use of connection identifiers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/30—Connection release
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/30—Connection release
  • H04W76/34—Selective release of ongoing connections
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections
  • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

• the present disclosure relates to mobile communication systems, and in particular, to a method and an apparatus being capable of substituting reporting of UE capability by use of an identifier of the UE, without reporting the overall UE capabilities in a reporting method of the UE’s own capability.
• the 5G or pre-5G communication system is also called a “Beyond 4G Network” or a “Post LTE System”.
• the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
• mmWave e.g., 60GHz bands
• MIMO massive multiple-input multiple-output
• FD-MIMO full dimensional MIMO
• array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
• RANs cloud radio access networks
• D2D device-to-device
• SWSC sliding window superposition coding
• ACM advanced coding modulation
• FBMC filter bank multi carrier
• NOMA non-orthogonal multiple access
• SCMA sparse code multiple access
• the Internet which is a human-centered connectivity network where humans generate and consume information
• IoT Internet of things
• IoE Internet of everything
• sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “security technology”
• M2M machine-to-machine
• MTC machine type communication
• IoT Internet technology services
• IoT may be applied to a variety of fields including, without limitation, smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing information technology (IT) and various industrial applications.
• IT information technology
• 5G communication systems to IoT networks.
• technologies such as a sensor network, machine type communication (MTC), and machine-to-machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
• Application of a cloud radio access network (RAN) as the above-described big data processing technology may also be considered an example of convergence of the 5G technology with the IoT technology.
• RAN cloud radio access network
• An aspect of the disclosure is to provide examples of methods for substituting reporting of UE capability by use of information of an identifier which is specified for a UE having the same UE capability, in a series of procedures in which the UE receives a request for UE capability from a base station and reports the UE capability to the base station in the NR system.
• the above-described method may employ use of a manufacturer-specific UE identifier and use of a PLMN-specific UE identifier.
• the disclosure provides examples of general operations for methods of delivering UE capability by use of the manufacturer-specific UE identifier.
• Another aspect of the disclosure is, for a specific UE belonging to a base station which supports both a basic uplink and an additional uplink in the NR system, to provide examples of allowing the additional uplink to be released.
• a terminal in a wireless communication system includes receiving, from a base station, information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicating with the base station on the UL or the SUL, based on the information configuring the UL and the SUL for the terminal; receiving, from the base station, information on reconfigurationwithsync; and releasing the SUL, in case that the information on reconfigurationwithsync does not include information associated with a SUL configuration.
• UL uplink
• SUL supplementary uplink
• certain methods performed by a base station in a wireless communication system include transmitting, to a terminal, information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicating with the terminal on the UL or the SUL, based on the information configuring the UL and the SUL for the terminal; and transmitting, to the terminal, information on reconfigurationwithsync, wherein the SUL is released, in case that the information on reconfigurationwithsync does not include information associated with a SUL configuration.
• UL uplink
• SUL supplementary uplink
• a terminal in a wireless communication system comprises a transceiver; and a controller configured to: receive, via the transceiver from a base station, information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicate with the base station on the UL or the SUL, based on the information configuring the UL and the SUL for the terminal; receive, via the transceiver from a base station, information on reconfigurationwithsync; and release the SUL, in case that the information on reconfigurationwithsync does not include information associated with a SUL configuration.
• UL uplink
• SUL supplementary uplink
• a base station in a wireless communication system comprises a transceiver; and a controller configured to: transmit, via the transceiver to a terminal, information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicate with the terminal on the UL or the SUL, based on the information configuring the UL and the SUL for the terminal; and transmit, via the transceiver to a terminal, information on reconfigurationwithsync, wherein the SUL is released, in case that the information on reconfigurationwithsync does not include information associated with a SUL configuration.
• UL uplink
• SUL supplementary uplink
• a NR UE reports its capability
• methods of configuration of a base station as provided by some embodiments of this disclosure support a basic uplink and an additional uplink in a cell.
• the specific UE is allowed to release the additional uplink, the concerned UE can do transmission and reception of data through the basic uplink.
• various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium.
• application and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code.
• computer readable program code includes any type of computer code, including source code, object code, and executable code.
• computer readable medium includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory.
• ROM read only memory
• RAM random access memory
• CD compact disc
• DVD digital video disc
• a “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals.
• a non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
• FIG. 1A illustrates an example of a structure of an LTE system, according to various embodiments of this disclosure
• FIG. 1B illustrates an example of a wireless protocol structure in the LTE system, according to certain embodiments of this disclosure
• FIG. 1C illustrates an example of a structure of a next generation mobile communication system according to certain embodiments of this disclosure
• FIG. 1D illustrates an example of a wireless protocol structure of a next generation mobile communication system according to various embodiments of this disclosure
• FIG. 1E illustrates an example of a message structure for reporting of UE capability in a NR system according to various embodiments of this disclosure
• FIG. 1F illustrates an example of registration and deregistration of a UE with a 5G core network in a NR system according to certain embodiments of this disclosure
• FIG. 1G illustrates an example of an operation to confirm UE capability by use of a manufacturer-specific identifier of UE capability, (referred to herein as a first reference example) according to certain embodiments of this disclosure;
• FIG. 1H illustrates an example of an operation when confirmation of UE capability by use of a manufacturer-specific identifier of UE capability fails, (referred to herein as a second reference example) according to various embodiments of this disclosure;
• FIG. 1I illustrates an example of operations to request a manufacturer-specific identifier of UE capability and report the same, in particular, to generate the manufacturer-specific UE capability, according to certain embodiments of his disclosure
• FIG. 1J illustrates an example of operations by the UE to receive a request for manufacturer-specific UE capability and an identifier thereof and report them, according to certain embodiments of this disclosure
• FIG. 1K illustrates an example of operations by a base station and a core network to request for manufacturer-specific UE capability and an identifier thereof and receive a report therefor, according to certain embodiments of this disclosure
• FIG. 1L illustrates, in block diagram format, an example a configuration of a UE according to various embodiments of this disclosure
• FIG. 1M illustrates, in block diagram format, an example of a configuration of a base station according to various embodiments of this disclosure
• FIG. 2A illustrates an example of a structure of an LTE system, according to certain embodiments of this disclosure
• FIG. 2B illustrates an example of a wireless protocol structure in the LTE system, according to certain embodiments of this disclosure
• FIG. 2C illustrates an example of a structure of the next generation mobile communication system according to some embodiments of this disclosure
• FIG. 2D illustrates an example of a wireless protocol structure of the next generation mobile communication system according to some embodiments of this disclosure
• FIG. 2E illustrates an example of procedures by which a base station transmits cell-based uplink configuration to the UE and thereafter release the specific uplink configuration, according to various embodiments of this disclosure
• FIG. 2F illustrates an example of operations by the UE when release of the UE-based uplink in a specific cell is applied, according to some embodiments of this disclosure
• FIG. 2G illustrates an example of operations by the base station when a method to release the UE-based uplink in a specific cell is applied, according to certain embodiments of this disclosure
• FIG. 2H illustrates, in block diagram format, an example of an internal structure of the UE according to various embodiments of this disclosure.
• FIG. 2I illustrates, in block diagram format, an example of a configuration of the base station according to certain embodiments of this disclosure.
• FIGS. 1A through 2I discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.
• the disclosure uses terms and names defined in 3rd generation partnership project long term evolution (3GPP LTE) standards for the convenience of description.
• 3GPP LTE 3rd generation partnership project long term evolution
• the disclosure is not limited by these terms and names, and may be applied in the same way to systems that conform to other standards.
• FIG. 1A illustrates an example of a structure of an LTE system, according to various embodiments of this disclosure.
• a wireless access network of an LTE system includes a next generation base station (Evolved node B; hereinafter referred to as “eNB”, “Node B” or “base station”) (1a-05, 1a-10, 1a-15, 1a-20), an MME (Mobility Management Entity, 1a-25), and S-GW (Serving-Gateway) (1a-30).
• eNB next generation base station
• MME Mobility Management Entity
• S-GW Serving-Gateway
• eNB (1a-05 to 1a-20) corresponds to an existing node B of the UMTS(Universal Mobile Telecommunication System) system.
• the eNB is connected to the UE (1a-35) via a wireless channel and performs a more complex role than the existing node B.
• a device for collecting and scheduling state information such as buffer state of UEs, available transformation power state, channel state, etc. is required. As such a device, the eNB (1a -05 to 1a-20) is used.
• one eNB usually controls a number of cells.
• the LTE system uses, for example, orthogonal frequency division multiplexing (hereinafter referred to as “OFDM”) in 20 MHz bandwidth as a wireless access technology.
• OFDM orthogonal frequency division multiplexing
• AMC adaptive modulation & coding
• S-GW (1a-30) is a device which provides data bearer, generating or removing the data bearer according to control of an MME (1a-25).
• MME (1a-25) is a device which functions various controls as well as mobility management for a UE and is connected to a number of base stations.
• FIG. 1B illustrates an example of a wireless protocol structure in the LTE system according to various embodiments of this disclosure.
• a wireless protocol of the LTE system includes PDCP (packet data convergence protocol) (1b-05, 1b-40), RLC (radio link control) (1b-10, 1b-35), and MAC (medium access control) (1b-15, 1b-30) at UE and eNB, respectively.
• PDCP packet data convergence protocol
• RLC radio link control
• MAC medium access control
• Radio Link Control (1b-10, 1b-35) reconstructs PDCP PDU (Packet Data Unit) in appropriate sizes and performs ARQ operation, etc.
• PDCP PDU Packet Data Unit
• the functions of RLC comprise:
• MAC (1b-15, 1b-30) is connected to various RLC layer devices provided in a UE and performs operations to multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs.
• the functions of MAC comprise:
• a physical (“PHY”) layer (1b-20, 1b-25) operates channel coding and modulation of upper layer data, makes the data into OFDM symbols and transmits the OFDM symbols via a wireless channel and demodulates the OFDM symbols received via the wireless channel, operates channel-decoding thereof and transmits the decoded data to the upper layer.
• HARQ Hybrid ARQ
• Information on whether or not a receiver has received a packet transmitted from a transmitter is transmitted by using 1 bit. This is HARQ ACK/NACK information.
• Downlink HARQ ACK/NACK information for the uplink transmission is transmitted via a physical channel of PHICH (physical hybrid-ARQ indicator channel), and uplink HARQ ACK/NACK information for the downlink transmission may be transmitted via PUCCH (physical uplink control signal) or PUSCH (physical uplink shared channel).
• PHICH physical hybrid-ARQ indicator channel
• the PHY layer may include one carrier or a plurality of frequencies/carriers.
• a technology to configure and use the plurality of frequencies simultaneously is called carrier aggregation (hereinafter referred to as “CA”).
• CA carrier aggregation
• a carrier is used for communication between a user equipment (UE) and a base station (E-UTRAN Node B, eNB).
• UE user equipment
• E-UTRAN Node B E-UTRAN Node B
• CA technology uses one carrier or a plurality of secondary carriers in addition to a primary carrier, thereby increasing the amount of transmission according to the number of secondary carriers.
• the cell in the base station using the primary carrier is PCell (Primary Cell) and the secondary cell is Scell (Secondary Cell).
• an RRC (radio resource control) layer is present in upper PDCP layers of the UE and the base station respectively, which is not illustrated in the accompanying drawings.
• the RRC layer can make a connection for wireless resource control and exchange configuration control messages associated with measurement.
• FIG. 1C illustrates an example of a structure of a next generation mobile communication system according to certain embodiments of this disclosure.
• a wireless access network of the next generation mobile communication system includes a next generation base station (new radio node B; hereinafter referred to as “NR-NB”) (1c-10) and a new radio core network or a next generation core network (hereinafter referred to as “NG CN” (1c-05).
• NR-NB next generation base station
• NG CN next generation core network
• a new radio user equipment (hereinafter referred to as “NR UE”) (1c-15) connects to an external network via NR NB (1c-10) and NR CN (1c-05).
• the NR NB (1c-10) corresponds to the eNB (evolved node B) of the existing LTE system.
• the NR NB is connected to a NR UE (1c-15) via a wireless channel and can provide more excellent services than the existing node B.
• a device for collecting and scheduling state information including buffer state, available transmission power state, channel state, etc. of the UEs is required.
• a NR NB (1c-10) is used as such a device.
• one NR NB usually controls a plurality of cells.
• the NR NB can have a bandwidth equal to or greater than the existing maximum bandwidth and a beam forming technology can additionally be utilized by using orthogonal frequency division multiplexing (OFDM). Also, adaptive modulation & coding (AMC) to determine a modulation scheme and a channel coding rate adaptive to the channel state of the UE is applied in some embodiments.
• a NR CN (1c-05) functions to support mobility and set up bearer and QoS, etc.
• the NR CN is a device performing a variety of controls as well as mobility management for the UE and is connected to a number of base stations.
• next generation mobile communication system can be associated with the existing LTE system, and the NR CN is connected to MME (1c-25) via a network interface.
• MME is connected to eNB (1c-30), which is an existing base station.
• FIG. 1D illustrates an example a wireless protocol structure of a next generation mobile communication system according to various embodiments of this disclosure.
• a wireless protocol of the next generation mobile communication system includes NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) at UE and NR base station respectively.
• NR SDAP (1d-01, 1d-45)
• a UE may receive, through an RRC message, a configuration as to whether to use a header of the SDAP layer device or to use a function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel.
• the SDAP layer device can instruct the UE to update or reset QoS flows of the uplink and the downlink and mapping information for data bearer by a 1-bit NAS reflective QoS indicator and a 1-bit AS reflective QoS indicator of the SDAP header.
• the SDAP header may include QoS flow ID information representing QoS.
• the QoS information may be used as data processing priority, scheduling information, etc. to assist in the smooth provision of services.
• NR PDCP (1d-05, 1d-40)
• the reordering function of the NR PDCP device is a function to sequentially reorder PDCP PDUs received by the lower layer based on PDCP SN (sequence number).
• This function may include a function to transmit data to the upper layer in the reordered sequence or to directly transmit data without considering the sequence, and a function to record lost PDCP PDUs by reordering the sequence thereof.
• functions to report states of the lost PDCP PDUs to the transmitter, and to request retransmission of the lost PDCM PDUs may be included.
• NR RLC (1d-10, 1d-35)
• in-sequence delivery of the NR RLC device is a function to transmit RLC SDUs received from the lower layer to the upper layer in sequence, originally where one RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, and may include a function to reassemble and transmit the received RLC PDUs may be included.
• a function to reorder the received RLC PDUs based on RLC SN or PDCP SN, a function to reorder the sequence of the received RLC PDUs and record lost RLC PDUs, a function to report the states of the lost RLC PDUs to the transmitter, and a function to request retransmission of the lost RLC PDUs may also be included.
• a function to transmit only the RLC SDUs prior to the lost RLC SDU to the upper layer in sequence may be included.
• a function to transmit all the RLC SDUs received before the timer starts to the upper layer in sequence may be included.
• a function to transmit all the RLC SDUs received up to now to the upper layer in sequence may be included.
• the RLC PDUs may be processed in the order as they are received (in the order as arrived, without regard to the sequence of serial numbers, sequence numbers, etc.) and delivered to the PDCP device without regard to the sequence (out-of sequence delivery).
• segments segments are stored in a buffer or segments to be received later are received, and thereafter they are reconstructed into a complete single RLC PDU, which is then processed and delivered to the PDCP device.
• the NR RLC layer may not include a function of concatenation, or this function may be performed at the NR MAC layer or substituted for a multiplexing function of the NR MAC layer.
• an out-of sequence delivery function of the NR RLC device is a function to deliver the RLC SDUs received from the lower layer directly to the upper layer without regard to the sequence thereof.
• a function to reassemble them may be included.
• a function to store RLC SNs or PDCP SNs of the received RLC PDUs and order them in sequence, and record lost RLC PDUs may also be included.
• NR MAC(1d-15, 1d-30) can be connected to several NR RLC layer devices included in a UE, and main functions of NR MAC may include one or more of the following functions:
• a NR PHY layer (1d-20, 1d-25) can operate channel coding and modulation of upper layer data, makes them into OFDM symbols and transmits the OFDM symbols via a wireless channel, and demodulates the OFDM symbols received via the wireless channel, operates channel-decoding thereof and transmits the decoded data to the upper link.
• FIG. 1E illustrates an example of a message structure for reporting of UE capability in a NR system according to certain embodiments of this disclosure.
• a UE (1e-01) passes through a procedure to report capabilities supported by the UE to a serving base station (1e-02) in a state that the UE is connected to the concerned base station.
• the base station delivers to the UE in a connected state a UE capability enquiry message that requests reporting of the UE capabilities.
• the message may include a request by the base station for UE capability by each RAT type.
• the RAT type based request may include frequency band information as requested according to the priority thereof.
• the UE capability enquiry message may request a plurality of RAT types in one RRC message container, or deliver to the UE the UE capability enquiry message including the RAT type based request several times.
• the UE capability enquiry is repeated several times at 1e-05 and the UE may construct UE capability information messages corresponding thereto, and match a response to the concerned request and then report the response.
• UE capabilities for MR-DC including NR, LTE, EN-DC may be requested.
• the UE capability enquiry message is generally delivered in an initial stage after connection by the UE is made, but it may also be requested in any condition when the base station requires.
• the UE having received the request for reporting UE capability from the base station constructs the UE capability according to RAT type and frequency band information as requested by the base station.
• An example of a method by the UE of constructing UE capability in the NR system according to various embodiments will be described below.
• the UE may receive a request for a part or a whole of RAT types of LTE, EN-DC and NR, as a request for UE capability, from the base station, and may simultaneously receive a list of LTE and NR frequency bands.
• the UE constructs a band combination (BC) for EN-DC and NR stand-alone (SA). That is, based on the frequency bands requested as FreqBandList from the base station, a candidate list of BCs for EN-DC and NR SA is constructed.
• the concerned operation may be defined as an operation of compiling a candidate band combination. Also, the priority of the bands is determined in the sequence as described in the FreqBandList. The concerned operation may be performed one time without regard to the RAT type or operated repeatedly by each RAT type.
• the concerned procedures are performed by each RAT type, and operated according to the priority of NR, MR-DC, and LTE, in order:
• the UE removes fallback BCs from the candidate list of BCs constructed at the above operation.
• the fallback BC is a case where the band corresponding to one SCell at minimum is removed from any super set of BCs. As the superset of BCs can already cover the fallback BC, it is possible to omit the fallback BC. In certain embodiments, this operation is also applied to EN-DC, that is, to LTE bands. The BCs remaining after this operation are the final “candidate list of BCs”.
• the UE selects BCs suitable for the requested RAT types from the final “candidate list of BCs” and selects BCs to be reported therefrom.
• the UE constructs supportedBandCombinationList in the predetermined order. That is, the UE constructs BCs and UE capability to be reported according to the sequence of rat-Types as previously set (nr ⁇ eutra-nr ⁇ eutra).
• featureSetCombination for the constructed spportedBandCombination is constructed, and a list of “candidate feature set combination” from the candidate list of BCs from which a list of the fallback BCs (including capabilities at the same or lower level) is removed is constructed.
• the “candidate feature set combination” includes the feature set combinations both for NR and EUTRA-NR BC and can be obtained from the feature set combination of UE-NR-Capabilities and UE-MRDC-Capabilities containers.
• featureSetCombinations are set adaptively to the concerned rat Type, and all are included in the two containers of UE-MRDC Capabilities and UE-NR Capabilities.
• the feature set of NR includes only UE-NR-Capabilities.
• the UE delivers a UE capability information message including the UE capability to the base station at 1e-10. Based on the UE capability received from the UE, the base station performs proper scheduling and transmission and reception management to the concerned UE thereafter.
• the disclosure considers a method of enabling substitution of UE capability report by means of an identifier (ID) representing the UE capability.
• ID an identifier
• UEs can be set to have the same UE capabilities according to UE serial numbers specified by the manufacturer, or manufacturer-specific models.
• a base station and a core network have capability for the concerned UE, it is possible to store and use the UE capability. If the same UE capability is reported for the same UE models, the base station and the core network would always receive the same UE capability report for the concerned UE model, and therefore, they can perform optimization of the concerned operation.
• the base station and the core network can determine the concerned identifier and retrieve the UE capability.
• an identifier that represents the above UE capability there are two options as described below.
• Manufacturer-specific identifier (ID) of UE capability It is possible to have an identifier for each manufacturer and each UE model (or for the UEs having the same UE capability among UEs of the same manufacturer), which may be an identifier that uniquely represents wireless link UE capability of the UE. Also, the concerned UE identifier may represent the entire capability of the UE.
• PLMN-specific identifier (ID) of UE capability In a situation that the above manufacturer-specific identifier of UE capability is not provided or the concerned base station and the core network cannot discern the identifier, an identifier that can be substituted therefor is required.
• the base station and the core network may provide a specific identifier to the UE according to the UE capability.
• the concerned identifier should be applicable to the serving PLMN and allotted to PLMN specifically.
• certain embodiments according to this disclosure provide operations for requesting and providing a manufacturer-specific identifier of UE capability and confirming the UE capability.
• FIG. 1F illustrates an example of registration and deregistration of a UE with a 5G core network in a NR system according to various embodiments of this disclosure.
• the UE is in a state of registration management (RM)-null with the concerned core network in operation 1f-05. Thereafter, if the concerned UE is activated in N1 mode (a mode that can be connected to a 5G core network) in operation 1f-20, the UE is present in a RM-DEREGISTRATION state with respect to the concerned core network as in the operation 1f-10. That is, this means that the concerned UE is capable of being connected to the 5G core network, but the procedure to connect and register has not yet been completed.
• N1 mode a mode that can be connected to a 5G core network
• the UE in this state will try the procedure to connect and register initially with the 5G core network in operation 1f-30. If this operation is completed, the UE is shifted to the state of RM-REGISTRATION in operation 1f-15. Thereafter, even if the UE performs a procedure to change the serving cell, etc., this is not an operation for initial registration (1f-40), and thus, the UE maintains the state of RM-REGISTRATION. If the UE is deregistered in operation 1f-35, the UE is shifted again to the state of RM-DEREGISTRATION. In certain embodiments, if deactivation of N1 mode is applied at the concerned state, the UE is shifted to an RM-NULL state.
• FIG. 1G illustrates an example of an operation to confirm UE capability by use of a manufacturer-specific identifier of UE capability, (referred to herein as a first reference example), according to various embodiments of this disclosure.
• a UE (1g-01) in a RRC IDLE state can perform the RRC connection procedure with a specific NR base station (gNB) (1g-02) in operation 1g-05.
• gNB NR base station
• an NAS message including a manufacturer-specific identifier of UE capability can be delivered to the core network (CN, 1g-03) to which the concerned base station is connected (1g-10).
• the core network having received the message, discerns the manufacturer-specific identifier of UE capability and checks whether UE capability corresponding to the concerned identifier is stored in operation 1g-15, and can confirm the UE capability mapped with the concerned identifier.
• the manufacturer-specific identifier of UE capability can be present as a table mapped with the UE capability in the core network. Thereafter, the UE and the core network perform a procedure to set up NAS security (authentication) in operation 1g-20, and the core network delivers the UE capability having been known as a result of confirming the manufacturer-specific identifier of UE capability to the base station in operation 1g-25.
• the message may be included in an INTIAL CONTEXT SETUP REQUEST message (NAS message).
• NAS message INTIAL CONTEXT SETUP REQUEST message
• the core network can deliver the manufacturer-specific identifier of UE capability received from the UE together.
• the base station stores the UE capability received from the core network, and thereafter, can reflect the UE capability in configuration of the RRC with the UE. As the concerned base station has been informed of the UE capability through these procedures, the base station may not trigger an operation to request UE for UE capability.
• FIG. 1H illustrates an example of an operation when confirmation of UE capability by use of a manufacturer-specific identifier of UE capability fails, (referred to herein as a second reference example) according to various embodiments of this disclosure.
• a UE (1h-01) in an RRC IDEL state can perform the RRC connection procedure with a specific NR base station (gNB, 1h-02) in operation 1h-05.
• an NAS message including a manufacturer-specific identifier of UE capability (for example, ATTACH/REGISTRATION REQUEST) can be delivered to a core network (CN) (1h-03) to which the concerned base station is connected (1h-10).
• the core network having received the message, discerns the manufacturer-specific identifier of UE capability and confirms whether UE capability corresponding to the concerned identifier is stored in operation 1h-15, but cannot restore UE capability mapped with the concerned identifier.
• the manufacturer-specific identifier of UE capability can be present in the form of a table mapped with the UE capability in the core network. However, in this process, the manufacturer-specific identifier of UE capability provided by the UE may not be stored and the concerned manufacturer-specific identifier of UE capability may not be identified. Thereafter, the UE and the core network perform a procedure to set up NAS security (authentication) in operation 1h-20. According to certain embodiments, at operation 1h-25, the core network informs the base station of having no UE capability for the UE and may deliver an INITIAL CONTEXT SETUP REQUEST message (NAS message) requesting the UE capability to the base station.
• NAS message INITIAL CONTEXT SETUP REQUEST message
• the core network may deliver the manufacturer-specific identifier of UE capability received from the UE together.
• the base station confirms the manufacturer-specific identifier of UE capability received from the core network. If restoration is possible because the base station has UE capability information for the concerned identifier, the base station reports it to the core network and thereafter may omit the UE capability requesting procedure.
• the base station confirms a request for the UE capability received from the core network and can trigger the UE capability request. That is, in operation 1h-35, a UECapabilityEnquiry message, including a RAT type for the UE capability request and filtering information is delivered to the UE.
• the UE reflects the concerned RAT type and filtering information and constructs UE capability in response to the UE capability request message received in operation 1h-35, and delivers UECapabilityInformation message to the base station.
• the UE may include the manufacturer-specific identifier of UE capability in the UECapabilityInfomation message.
• the base station stores the UE capability information received from the UE. If the manufacturer-specific identifier of UE capability is received together from the UE, the concerned information is stored together.
• the base station delivers the UECapabilityInformation message received from the UE to the core network.
• the concerned UE capability may include filtering information in different containers by each RAT type and be delivered as it is (UE-CapabilityRAT-ContainerList together with filter).
• the core network stores the UE capability received in the above operation and updates the UE capability mapping table including the manufacturer-specific identifier of UE capability and UE capability. Thereafter, the stored UE capability can be applied to the UE which provides the concerned manufacturer-specific identifier of UE capability.
• FIG. 1I illustrates an example of operations to request a manufacturer-specific identifier of UE capability and report the same, in particular, to generate the manufacturer-specific UE capability, according to certain embodiments of this disclosure.
• a UE (1i-01) in an RRC IDLE state can perform a RRC connection procedure with a specific NR base station (gNB, 1i-02) in operation 1i-05.
• the UE can deliver an NAS message including a manufacturer-specific identifier of UE capability and a PLMN-specific identifier of UE capability (for example, ATTACH/REGISTRATION REQUEST) to a core network (CN) (1i-03) to which the concerned base station is connected (1i-10).
• CN core network
• the PLMN-specific identifier of UE capability may be optionally included in a case where the UE is in a previous connection state and the PLMN-specific UE capability allotted at the UE capability delivery procedure is present, and it may be delivered in as a list including a plurality of items. Also, the PLMN-specific identifier of UE capability may be selected in consideration of PLMN of the base station currently in a state of being connected to the concerned UE. That is, in some embodiments, only an identifier for a PLMN which is the same as a serving cell can be reported.
• the core network having received the PLMN identifier in operation 1i-15 confirms the concerned manufacturer-specific identifier of UE capability and the PLMN-specific identifier of UE capability so as to confirm whether or not the UE capability for the concerned identifier is stored, but may not restore the UE capability mapped with the concerned identifier.
• the manufacturer-specific identifier of UE capability and the PLMN-specific identifier of UE capability and UE capabilities can be present as a mapping table in the core network.
• the manufacturer-specific identifier of UE capability and the PLMN-specific identifier of UE capability, provided by the UE may not be stored, and the concerned manufacturer-specific identifier of UE capability and the PLMN-specific identifier of UE capability may not be identified.
• the UE and the core network perform a procedure to set up NAS security (authentication) in operation 1i-20, and inform the base station of having no UE capability in operation 1i-25.
• an INITIAL CONTEXT SETUP REQUEST message (NAS message) requesting the UE capability may be delivered to the base station.
• the core network can request the base station for full UE capability, which may be used in obtaining the manufacturer-specific UE capability. Also, the core network may deliver together the manufacturer-specific identifier of UE capability having been received from the UE. In the above operation, the base station confirms the manufacturer-specific identifier of UE capability having been received from the core network. In certain embodiments, if the base station has the UE capability information for the concerned identifier and it is possible to restore the UE capability, this is informed the core network and the UE capability request procedure is omitted thereafter.
• the base station confirms the UE capability request having been received from the core network in operation 1i-30 and can trigger the UE capability request. That is, a UECapabilityEnquiry message including RAT type requesting UE capability and filtering information is delivered to the UE.
• the RRC message may include an option to request full UE capability, that is, manufacturer-specific UE capability in a filter. That is, information for requesting full capability may be included in the filtering information, or the information may be delivered in an unfiltered state by omitting filtering information by each RAT type, and this may be used to mean that the entire UE information should be reported.
• the RRC message may include an indicator to indicate whether or not the UE can provide an identifier of UE capability.
• the UE can deliver a UECapabilityInformation message including only the concerned identifier to the base station in operation 1i-40.
• the UE if the UE does not possess the PLMN-specific identifier of UE capability mapped for the request from the base station, the UE reflects the concerned RAT type and filtering information as in the existing procedure to generate and report UE capability and constructs UE capability in operations 1i-40 and 1i-45 and delivers the UECapabilityInformation message to the base station.
• the below operation addresses a procedure according to which the UE is requested to report the manufacturer-specific UE capability from the base station and reports it.
• the UE generates a UE capability message (UE capability information) for its own UE capability request from the base station. If the concerned message exceeds 9000 Bytes, which is the maximum size of PDCP PDU, segmentation is applied. That is, it can be known that the entire UE capability information message is segmented into segments having the size of 9000 Bytes, and the last segment may be a segment having a remaining size (subtracting the sum of segmented RRC messages from the entire message size).
• 9000 Bytes which is the maximum size of PDCP PDU
• the UE may include the entire UE capability and an indicator to indicate that the UE capability to be reported is manufacturer-specific UE capability or a manufacturer-specific identifier of UE capability.
• the UE capability to be reported is not identical to the manufacturer-specific UE capability (Full UE capability)
• information (indicator) indicating that the UE capability to be reported is not the manufacturer-specific UE capability (full UE capability) is included in the UE capability information message, which is delivered as it is (1i-45).
• each RAT type is included in each container present in UE-CapabilityRAT-ContainerList, and is delivered as it is.
• the base station and the core network store UE capability delivered, by associating it with the manufacturer-specific identifier of UE capability, which may be interpreted and used as UE capability thereafter.
• the below operation addresses a case where the UE does not deliver the manufacturer-specific UE capability in operation 1i-45. That is, where the UE delivers the UE capability together with an indicator indicating that the UE capability is not the manufacturer-specific UE capability, the UE capability information delivered in operation 1i-50 is stored in an internal buffer (memory), together with the RAT type and filtering information requested by the base station in association therewith.
• the UE can store registered PLMN information of the concerned serving cell connected from the system information (SIBI) having been received by the concerned serving cell. It is concluded that the UE stores the PLMN information, RAT type and filtering information, and reported UE capability in one group in the concerned operation.
• SIBI system information
• the base station delivers the UECapabilityInformation message having received from the UE to the core network, and the concerned UE capability includes filtering information in different containers by each RAT type, which is transmitted as it is (UE-CapabilityRAT-ConainterList together with filter). Also, the message may include an indicator indicating that the UE capability is not the manufacturer-specific UE capability delivered from the UE.
• the core network confirms the UE capability having been received at the above operation.
• the concerned identifier is allotted as a PLMN-specific identifier of UE capability.
• the core network may allot a new PLMN-specific identifier of UE capability thereto.
• the core network delivers to the UE the PLMN-specific identifier of UE capability attached adaptive to the UE capability reported by the UE by means of an NAS message (for example, ATTACH/REGISTRATION RESPONSE).
• the message may include index information to indicate whether the identifier is an identifier for any UE capability, or may be provided with the RAT type and the filtering information mapped with the concerned UE capability.
• a reason why the concerned operation is required is because operations 1i-35, 1i-40, and 1i-45 are, in certain embodiments, not finished at one time, but they may be successively completed.
• the base station can deliver an NR-associated UE capability request for RAT type and a filter in operation 1i-35. After having received the concerned UE capability from the UE in operation 1i-45, the base station repeats operation 1i-35 once again and requests EN-DC UE capability, and receives report of the concerned UE capability in operation 1i-45.
• the PLMN-specific identifiers of UE capability for the two UE capabilities having successively been received should be distinguished for allocation. Therefore, index information to distinguish them (for example, the first capability report of UE is set 1 and the second capability report of UE is set 2) may be included, or filing information may be delivered together.
• the method of the core network’s allotting a PLMN-specific identifier of UE capability in operation 1i-60 may be applied differently depending upon network realization.
• the concerned UE capability may be specified only for a case where UE capability reports for a specific UE are received and the number of UE reports to provide the same UE capability as the concerned UE capability is greater than a predetermined critical value (N) and the PLMN-specific identifier of UE capability may be allotted thereto. That is, an algorithm not to allot a specific PLMN-specific identifier of UE capability only with a few UE capability reports is required in certain embodiments.
• the UE maps the PLMN-specific identifier of UE capability having been received from the core network in operation 1i-65 with the UE capability storage group reported and stored by the UE in operation 1i-50 and newly stores the same. That is, the UE groups the PLMN-specific identifier of UE capability, registered PLMN information, RAT type and filtering information, and reported UE capability and stores them in one group at the concerned operation. Thereafter, a PLMN-specific identifier of UE capability allotted to represent the concerned UE capability can be used. Also, in the above operation, the number of PLMN-specific identifiers of UE capability that the UE can store may be limited.
• the PLMN-specific identifier of UE capability and the concerned UE capability group having previously been stored can be erased and updated to new values. Also, in certain embodiments, it is possible to perform an operation to erase information for the other PLMNs, remaining information only for the same PLMN in the above operation.
• the core network can deliver to the base station via an N1 message the PLMN-specific identifier of UE capability having been delivered to the UE, and the base station stores the PLMN-specific identifier of UE capability, registered PLMN information, RAT type and filtering information, and reported UE capability in one group, based on the PLMN-specific identifier of UE capability received in operation 1i-80, the UE capability received in operation 1i-45, and the RAT type and filtering information having been delivered to the UE in operation 1i-35.
• the base station having received the PLMN-specific identifier of UE capability may not trigger the UE capability request.
• FIG. 1J illustrates an example of operations by the UE to receive a request for manufacturer-specific UE capability and an identifier thereof and report same, according to certain embodiments of this disclosure.
• the UE in operation 1j-05, can be camped on a specific serving cell and shifted to an RRC connection state.
• the UE delivers an identifier of UE capability that the UE possesses, via an NAS message (for example, INITIAL ATTACH/REGISTRATION REQUEST message) to the core network connected to the concerned base station in operation 1j-10.
• the concerned identifier may include a manufacturer-specific identifier of UE capability and a PLMN-specific identifier of UE capability.
• the UE in a state that the PLMN-specific identifier of UE capability has not been allotted, only the manufacturer-specific identifier of UE capability can be included.
• the core network or the base station fails to restore the UE capability for the identifier of UE capability having been delivered by the UE, the UE will receive a message that requests report of UE capability through the base station.
• the UE capability request message may include a filter that requests full UE capability. Otherwise, the message may be delivered in an unfiltered state, with omission of all the filtering information by each RAT type, which may be used to mean that the full UE information is to be reported.
• the UE In operation 1j-20, the UE generates UE capability information in response to the above UE capability request message. That is, considering the filtering information having been requested in operation 1j-15, the UE capability message is generated. If the size of the message is in excess of 9000 Bytes, the UE capability information is segmented, generating segmented information. Also, in certain embodiments, in operation 1j-25, it is determined whether the UE capability information generated in operation 1j-20 is the same as the manufacturer-specific full UE capability (1j-30). If the generated UE capability information is same as the manufacturer-specific full UE capability, the full capability information is reported in operation 1j-35. Simultaneously, an indicator indicating that the concerned UE capability is the manufacturer-specific full UE capability, and the manufacturer-specific full UE capability, are included therein and reported to the base station.
• the UE capability information generated in operation 1j-20 is the same as the manufacturer-specific full UE capability (1j-30). Where the generated UE capability information is not the same as the manufacturer-specific full UE capability, the UE includes an indicator indicating that the reported UE capability is not the manufacturer-specific full UE capability and delivers the same in operation 1j-40.
• the UE stores the reported UE capability in a buffer (memory). Thereafter in operation 1j-50, if a PLMN-specific identifier of UE capability is indicated via an NAS message, the stored UE capability is associated with the PLMN-specific identifier of UE capability and then stored and used.
• the UE stores the PLMN-specific identifier of UE capability, registered PLMN information, RAT type and filtering information, reported UE capability in one group. Thereafter, the PLMN-specific identifier of UE capability allotted to represent the concerned UE capability can be used.
• the number of PLMN-specific identifiers of UE capability stored by the UE may be limited. If the UE capability for a new PLMN-specific identifier of UE capability should be stored in a state that the UE has stored the predetermined number of PLMN-specific identifiers of UE capability, the PLMN-specific identifier of UE capability and the concerned UE capability group having previously been stored can be erased and updated to new values. Also, it is possible to perform an operation to erase information for the other PLMNs, remaining information only for the same PLMN in the above operation.
• FIG. 1K illustrates an example of operations by a base station and a core network to request for manufacturer-specific UE capability and an identifier thereof and receive a report therefor, according to various embodiments of this disclosure.
• a base station performs an RRC connection procedure and can shift the UE to a connected state.
• a core network connected to a base station can receive an identifier of UE capability that the UE possesses via an NAS message (for example, ATTACH/REGISTRATION REQUEST message).
• the concerned identifier may include a manufacturer-specific identifier of UE capability and a PLMN-specific identifier of UE capability.
• only the manufacturer-specific identifier of UE capability may be included.
• the core network determines whether the UE has UE capability based on the received identifier. If the concerned UE has no manufacturer-specific UE capability, the core network can instruct the base station to start a procedure to request the required UE capability. The base station can receive an indicator requesting the full UE capability from the core network at the concerned operation, or the core network may allow any necessity for the full UE capability to occur inside the base station.
• the base station can deliver a message to request UE capability to the UE, and the concerned message may include RAT type and filtering information such as frequency, or an indicator indicating that the concerned request is to obtain a manufacturer-specific UE capability of the UE.
• the above UE capability request message may include a filter to request full UE capability, or the message may be delivered in an unfiltered state, omitting the filtering information by each RAT type, which may be used to mean that the full UE capability information should be reported.
• the UE delivers UE capability information in response to the UE capability request message to the base station, and the base station decodes and interprets the concerned received information to thereby obtain the UE capability.
• the base station determines that the reported UE capability is the manufacturer-specific full UE capability and can store the concerned UE capability in the buffer and memory.
• the received UE capability information and the indicator information are delivered to the core network in a NAS message (1k-30).
• the base station determines that the reported UE capability is not the manufacturer-specific full UE capability and can store the concerned UE capability in the buffer and memory.
• the received UE capability information and the indicator information are delivered to the core network in a NAS message (1k-40). Even where the concerned message is delivered, an indicator indicating that the reported UE capability is not the manufacturer-specific full UE capability may be included. In the illustrative example of FIG.
• the base station receives a PLMN-specific identifier of UE capability for the concerned UE capability from an AMF (core network)
• the base station associates the identifier with the stored UE capability, and stores and manages them. Thereafter, they are used for configuration with the UE.
• FIG. 1L illustrates, in block diagram format, an example of a configuration of a UE according various embodiments of this disclosure.
• a UE includes a transceiver (1l-05), a controller (1l-10), a multiplexing and demultiplexing unit (1l-15), a variety of uplink processors (1l-20, 1l-25), and a control message processor (1l-30).
• the transceiver (1l-05) receives data and a predetermined control signal by a forward channel of a serving cell and transmits the data and the predetermined control signal by a backward channel. Where a plurality of serving cells are set, the transceiver (1l-05) performs data transmission and reception and control signal transmission and reception through the plurality of serving cells.
• the multiplexing and demultiplexing unit (1l-15) plays a role of multiplexing data generated in the uplink processors (1l-20, 1l-25) or the control message processor (1l-30) or demultiplexing the data received by the transceiver (1l-05), and delivering the data to the uplink layer processors (1l-20, 1l-25) or the control message processor (1l-30).
• the control signal processor (1l-30) transceives a control message from a base station and conducts a necessary operation therefor.
• the operation includes a function to process the control message such as RRC message and MAC CE, and report of a CBR measurement value, and reception by UE of resource pool and RRC message for an operation.
• the uplink layer processor (1l-20, 1l-25) refers to a DRB device and can be configured by each service. Data generated by user services such as FTP (file transfer protocol) or VoIP (voice over Internet protocol) is processed and delivered to the multiplexing and demultiplexing unit (1l-15), or data delivered from the multiplexing and demultiplexing unit (1l-15) is processed and delivered to a service application of the uplink layer.
• the controller (1l-10) confirms a scheduling instruction received through the transceiver (1l-05), for example, backward grants and controls the transceiver (1l-05) and the multiplexing and demultiplexing unit (1l-15) so that backward transmission to an appropriate transmission resource time can be performed at an appropriate.
• the disclosure has been described with reference to an example of a UE which includes a plurality of blocks and the respective blocks perform different functions, which merely constitutes an exemplary embodiment of the disclosure, and the disclosure is not limited thereto.
• a function that is performed by the multiplexing and demultiplexing unit (1l-15) may be performed by the controller (1l-10) itself.
• FIG. 1M illustrates, in block diagram format, an example a configuration of a base station according to certain embodiments of this disclosure.
• a base station device includes a transceiver (1m-05), a controller (1m-10), a multiplexing and demultiplexing unit (1m-20), a control message processor (1m-35), a variety of uplink processors (1m-25, 1m-30), and a scheduler (1m-15).
• the transceiver (1m-05) transmits data and a predetermined control signal by a forward carrier and receives data and a predetermined control signals by a backward carrier. Where a plurality of carriers are set, the transceiver (1m-05) performs data transmission and reception and control signal transmission and reception through the plurality of carriers.
• the multiplexing and demultiplexing unit (1m-20) plays a role of multiplexing data generated in the uplink processors (1m-25, 1m-30) or the control message processor (1m-35) or demultiplexing data received by the transceiver (1m-05), and delivering the data to the proper uplink layer processors (1m-25, 1m-30), the control message processor (1m-35), or the controller (1m-10).
• the control message processor (1m-35) receives an instruction from the controller and generates a message to be delivered to the UE, and delivers the message to a downlink layer.
• the uplink layer processor (1m-25, 1m-30) may be constructed by each UE and each service, and processes data generated by user services such as FTP or VoIP, etc. and delivers the data to the multiplexing and demultiplexing unit (1m-20), or processes data delivered from the multiplexing and demultiplexing unit (1m-20) and delivers the data to a service application of the uplink layer.
• the scheduler (1m-15) allots any transmission resource to the UE at appropriate time, in consideration of buffer state of the UE, channel state, and active time of the UE, etc., and processes a signal delivered by the UE to the transceiver or processes the signal so as to be delivered to the UE.
• FIG. 2A illustrates an example of a structure of an LTE system, according to various embodiments of this disclosure.
• a wireless access network of the LTE system includes a next generation base station (Evolved node B, “eNB”, “Node B” or “base station”) (2a-05, 2a-10, 2a-15, 2a-20), MME (mobility management entity, 2a-25), and S-GW (serving-gateway, 2a-30).
• UE User equipment
• the eNB (2a-05 to 2a-20) corresponds to an existing node B of the UMTS(Universal Mobile Telecommunication System) system.
• An eNB is connected to UE (2a-35) via a wireless channel, performing a more complex role than the existing node B.
• UE Universal Mobile Telecommunication System
• a device for collecting and scheduling state information such as buffer state, available transformation power state, channel state of UEs, etc. is required.
• the eNB (2a-05 to 2a-20) is used.
• one eNB usually controls a number of cells.
• the LTE system uses, for example, orthogonal frequency division multiplexing (“OFDM”) in 20 MHz bandwidth as a wireless accessing technology.
• OFDM orthogonal frequency division multiplexing
• AMC adaptive modulation & coding
• S-GW (2a-30) is a device which provides data bearer and generates or removes data bearer according to control of MME (2a-25).
• MME (2a-25) is a device which functions various controls as well as mobility management for a UE.
• FIG. 2B illustrates a wireless protocol structure in the LTE system, according to certain embodiments of this disclosure.
• a wireless protocol of the LTE system includes PDCP (packet data convergence protocol) (2b-05, 2b-40), RLC (radio link control) (2b-10, 2b-35), and MAC (medium access control) (2b-15, 2b-30) layers at UE and eNB respectively.
• PDCP packet data convergence protocol
• RLC radio link control
• MAC medium access control
• Radio link control (2b-10, 2b-35) reconstructs PDCP PDU (Packet Data Unit) in appropriate sizes and performs ARQ operation, etc.
• Functions of the RLC layer comprise:
• MAC layer (2b-15, 2b-30) is connected to various RLC layer devices provided in a UE and performs operations to multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs.
• Functions of the MAC layer comprise:
• a physical (“PHY”) layer (2b-20, 2b-25) operates channel coding and modulation of upper layer data, to make the data into OFDM symbols and transmit the OFDM symbols via a wireless channel, and demodulates the OFDM symbols received via the wireless channel, operates channel-decoding thereof and transmits the decoded data to the upper link. Also, even in the physical layer, HARQ (hybrid ARQ) is used to correct any additional error. Information on whether or not a receiver has received a packet transmitted from a transmitter has received is transmitted by using 1 bit. This is HARQ ACK/NACK information.
• Downlink HARQ ACK/NACK information for the uplink transmission is transmitted via a physical channel of PHICH (physical hybrid-ARQ indicator channel), and uplink HARQ ACK/NACK information for the downlink transmission may be transmitted via PUCCH (physical uplink control signal) or PUSCH (physical uplink shared channel).
• PHICH physical hybrid-ARQ indicator channel
• the PHY layer may include one or a plurality of frequencies/carriers.
• a technology to configure and use the plurality of frequencies simultaneously is called carrier aggregation (“CA”).
• CA carrier aggregation
• the CA technology uses one or a plurality of secondary carriers in addition to a primary carrier, thereby being capable of drastically increasing the amount of transmission according to the number of secondary carriers.
• the cell in the base station using the primary carrier is PCell (Primary Cell) and the secondary cell is Scell (Secondary Cell).
• an RRC (radio resource control) layer is present in upper PDCP layers of the UE and the base station respectively, which is not illustrated in the accompanying drawings.
• the RRC layer can make a connection for wireless resource control and exchange configuration control messages associated with measurement.
• FIG. 2C illustrates an example of a structure of the next generation mobile communication system according to various embodiments of this disclosure.
• a wireless access network of the next generation mobile communication system includes a next generation base station (new radio node B, “NR-NB”) (2c-10) and a new radio core network or a next generation core network (“NG CN”) (2c-05).
• NR-NB next generation base station
• NG CN next generation core network
• NR UE new radio user equipment
• the NR NB (2c-10) corresponds to the eNB (evolved node B) of the existing LTE system.
• the NR NB is connected to NR UE (2c-15) via a wireless channel and can provide more excellent services than the existing node B.
• a device for collecting and scheduling state information including buffer state, available transmission power state, channel state, etc. of the UEs is required.
• NR NB (2c-10) is used.
• One NR NB usually controls a plurality of cells.
• the NR NB can have a bandwidth equal to or greater than the existing maximum bandwidth and a beam forming technology can additionally be implemented by using orthogonal frequency division multiplexing (OFDM). Also, adaptive modulation & coding (AMC) to determine a modulation scheme and a channel coding rate adaptive to the channel state of the UE is applied.
• OFDM orthogonal frequency division multiplexing
• AMC adaptive modulation & coding
• a NR CN functions to support mobility and set up bearer and QoS, etc.
• the NR CN is a device providing a variety of controls as well as mobility management for the UE and is connected to a number of base stations.
• the next generation mobile communication system can be associated with the existing LTE system, and the NR CN is connected to MME (2c-25) via a network interface.
• MME is connected to eNB (2c-30) which is an existing base station.
• FIG. 2D illustrates an example of a wireless protocol structure of the next generation mobile communication system according to various embodiments of this disclosure.
• a wireless protocol of the next generation mobile communication system includes NR SDAP(2d-01, 2d-45), NR PDCP (2d-05, 2d-40), NR RLC(2d-10, 2d-35), and NR MAC(2d-15, 2d-30) at UE and NR base station respectively.
• Functions of the NR SDAP (2d-01, 2d-45) comprise one or more of the following:
• a UE can receive setup as to whether to use a header of the SDAP layer device by each PDCP layer device, each bearer, or each logical channel, or to use a function of the SDAP layer device, by means of the RRC message.
• the SDAP layer device can instruct the UE to update or reset QoS flows of the uplink and the downlink and mapping information for data bearer by a 1-bit NAS reflective QoS indicator and a 1-bit AS reflective QoS indicator of the SDAP header.
• the SDAP header may include QoS flow ID information representing QoS.
• the QoS information may be used as data processing priority, scheduling information, etc. to assist in smooth services.
• Functions of NR PDCP (2d-05, 2d-40) can include one or more of the following:
• Reordering function of the NR PDCP device is a function to sequentially reorder PDCP PDUs received by the lower layer based on PDCP SN (sequence number).
• This function may include a function to transmit data to the upper layer in the reordered sequence or to directly transmit data without considering the sequence, and a function to record lost PDCP PDUs by reordering the sequence thereof.
• functions to report states of the lost PDCP PDUs to the transmitter, and to request retransmission of the lost PDCM PDUs may be included.
• Functions of NR RLC (2d-10, 2d-35) include one or more of the following:
• in-sequence delivery of the NR RLC device is a function to transmit RLC SDUs received from the lower layer to the upper layer in sequence, originally where one RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, a function to reassemble and transmit the received RLC PDUs may be included.
• a function to reorder the received RLC PDUs based on RLC SN or PDCP SN, a function to reorder the sequence of the received RLC PDUs and record lost RLC PDUs, a function to report the states of the lost RLC PDUs to the transmitter, and a function to request retransmission of the lost RLC PDUs may also be included.
• a function to transmit only the RLC SDUs prior to the lost RLC SDU to the upper layer in sequence may be included.
• a function to transmit all the RLC SDUs received before the timer starts to the upper layer in sequence may be included.
• a function to transmit all the RLC SDUs received up to now to the upper layer in sequence may be included.
• the RLC PDUs may be processed in the order as they are received (in the order as arrived, without regard to the sequence of serial numbers, sequence numbers, etc.) and delivered to the PDCP device without regard to the sequence (out-of sequence delivery).
• segments segments are stored in a buffer or segments to be received later are received and thereafter they are reconstructed into a complete single RLC PDU, which is then processed and delivered to the PDCP device.
• the NR RLC layer may not include a function of concatenation, or this function may be performed at the NR MAC layer or substituted for a multiplexing function of the NR MAC layer.
• an out-of sequence delivery function of the NR RLC device is a function to deliver the RLC SDUs received from the lower layer directly to the upper layer without regard to the sequence thereof.
• a function to reassemble them may be included.
• a function to store RLC SNs or PDCP SNs of the received RLC PDUs and order them in sequence, and record lost RLC PDUs may also be included.
• NR MAC (2d-15, 2d-30) can be connected to several NR RLC layer devices included in a UE.
• Functions of an NR MAC include one or more of the following:
• an NR PHY layer (2d-20, 2d-25) can operate channel coding and modulation of upper layer data, make them into OFDM symbols and transmit the OFDM symbols via a wireless channel, and demodulate the OFDM symbols received via the wireless channel, operate channel-decoding thereof and transmit the decoded data to the upper link.
• FIG. 2E illustrates an example of procedures by which a base station transmits cell-based uplink configuration to the UE and thereafter releases the specific uplink configuration, according to various embodiments of this disclosure.
• UE (2e-01) in an RRC IDLE state is camped on after passing through a cell selection procedure for a specific base station (2e-02) and can receive system information. Thereafter, the UE performs an RRC connection procedure with the concerned cell in operation 2e-05 and the UE in the RRC connection state is shifted to the concerned cell.
• a base station delivers an RRCReconfiguration message to the UE and provides configuration information applied to the UE in the concerned cell.
• the message may include, in particular, ServingCellConfigCommon, which is the basic information in the concerned serving cell, and ServingCellConfig configuration information which is specific information based on UE in the concerned cell.
• configuration information for a normal uplink hereinafter referred to as “NUL”
• a supplementary uplink hereinafter referred to as “SUL”
• the concerned configuration information is configuration information delivered to all UEs in the cell if the base station supports them on a cell basis.
• this field is optionally present if UplinkConfigcomon is set but is not present in any other cases. Where this field is not present, the UE releases SupplementaryUplinkConfig if set in ServingCellConfig.
• the ServingCellConfigCommon may be included when it is delivered to a target cell from the previous cell at the time of handover.
• the configuration information for SUL may be released. That is, the supplementaryUplinkConfg is discarded from the ServingCellConfigCommon, the UE releases SUL configuration information.
• serving cells support both NUL and SUL, and there is no function to set only one UL for a specific UE. That is, where the UE is isolated from a cell edge (moves to the center of a cell), SUL configuration is not required, and support for more features may be wanted. Also, where SUL is set, as capability limitation (for example, limitation to UL MIMO, etc.) may be applied to the UE, and thus, more UE capability and wireless features can be used if NUL is solely set than in the case of NUL + SUL configuration.
• capability limitation for example, limitation to UL MIMO, etc.
• ASN.1 code shown below indicates that current standards cannot release SUL for a specific UE.
• a SupplementaryUplink field is set to OPTIONAL NEED M in the ASN.1 code. This means that where the concerned filed is discarded and delivered in the next configuration, if there is a value set previously, the previous value is maintained. That is, although NUL and SUL are simultaneously set in the previous RRC configuration, and SUL is discarded and delivered in the next configuration, it does not mean release of SUL.
• the UE can measure serving cells and cells of the serving frequency, and cells of peripheral frequency and other RAT according to the measurement procedure, and includes the measurement results in a measurement reporting message so as to be then delivered to the base station.
• the base station interprets information of the received measurement report of the UE and can know that the current cell is not present in the cell edge but is present near the center of the serving cell. That is, this may be a case where the serving cell measurement value of the UE is good.
• the base station can determine to release SUL having been set for the concerned UE. This is to allow the UE to use more UE capability and provide more wireless resources.
• the base station includes ReconfigurationWithSync and ServingCellConfigCommon including configuration information only for the uplink (NUL) in an RRCReconfiguration message and can deliver the message to the UE.
• the UE is instructed to re-perform synchronous configuration via random access, release SUL configuration from the concerned cell, and apply only the NUL configuration.
• the UE applies the configuration for the set NUL, performs a random access procedure for the concerned cell, and obtains uplink and downlink synchronization.
• the UE performs data transmission and reception with the base station. In this case, the new configuration value received in operation 2e-25 is applied, SUL configuration is released, and communication is conducted by applying only NUL.
• the disclosure features that SUL is not set for a specific UE although the concerned serving sell supports both NUL and SUL.
• cell-based uplink configuration information is continuously provided from ServingCellConfigCommon and ServingCellConfigCommonSIB according to the support thereof by the cell.
• SUL configuration information may be absent for a specific UE, separately from the cell capability. If the base station delivers ServingCellConfigCommon from which SUL configuration is discarded, together from ReconfigurationWithSync, the UE releases the SUL configuration information present in ServingCellConfig, which is a dedicated RRC message.
• the SUL cannot be used again because SUL configuration information included in the dedicated message has been released.
• SIBI that is, both NUL and SUL configurations are included in ServingCellConfigCommonSIB
• the SUL cannot be used again because SUL configuration information included in the dedicated message has been released.
• ReconfigurationWithSync configuration is used in a case of changing PCell (handover), in which the most important system information in the target cell can be included.
• the disclosure features that if the disclosure is applied, a method of using ReconfigurationWithSync is applied for a cell-based UE.
• FIG. 2F illustrates an example of operations by the UE when release of the UE-based uplink in a specific cell is applied, as provided in the disclosure.
• a UE in a RRC IDLE state is camped on after passing through a cell selection procedure for a specific base station, and can receive system information. Thereafter, the UE performs an RRC connection procedure with the concerned cell and is shifted to the concerned cell in the RRC connection state.
• the UE receives an RRCReconfiguration message from the base station and receives configuration information applied to the UE in the concerned cell.
• the message may include ServingCellConfigCommon which is the basic information in the concerned cell and ServingCellConfig configuration information which is specific information based on the UE.
• configuration information for the normal uplink (NUL) and the supplementary uplink (SUL) may be included in ServingCellConfigCommon.
• the concerned configuration information is configuration information delivered to all UEs in the cell if supported by the base station on a cell basis.
• the UE can measure serving cells, cells of serving frequencies, and cells of peripheral frequencies and other RAT cells according to the measurement procedure.
• the UE can receive an RRCReconfiguration message delivered from the base station, and ReconfigurationWithSync and ServingCellConfigCommon having only the uplink configuration information can be included in the concerned message.
• the UE is instructed to re-perform synchronous configuration via random access, release SUL configuration from the concerned cell, and apply only the NUL configuration.
• the UE applies the configuration for the set NUL, performs a random access procedure for the concerned cell, and obtains uplink and downlink synchronization.
• the UE performs data transmission and reception with the base station. In this case, the new configuration value received in operation 2f-15 is applied, SUL configuration is released, and communication is conducted by applying only NUL.
• FIG. 2G illustrates an example of operations by the base station when a method to release the UE-based uplink in a specific cell is applied, according to various embodiments of this disclosure.
• a UE in an RRC IDLE state is camped on after passing through the cell selection procedure for a specific base station and performs an RRC connection procedure with the concerned cell after having received the system information.
• the base station shifts the concerned UE to the RRC connection state.
• the base station delivers an RRCReconfiguration message to the UE and provides configuration information applied to the UE in the concerned cell.
• the message may include, in particular, ServingCellConfigCommon which is the basic information in the concerned serving cell and ServingCellConfig configuration information which is specific information based on UE in the concerned cell.
• configuration information for a normal uplink hereinafter referred to as “NUL” and a supplementary uplink (hereinafter referred to as “SUL”) may be included in the ServingCellConfigCommon.
• the concerned configuration information is configuration information delivered to all UEs in the cell if the base station supports them on a cell basis.
• the base station receives a measurement report delivered by the UE.
• the measurement report may include measurement values of serving cells, cells of serving frequency, and cells of peripheral frequency and other RATs according to the measurement procedure.
• the base station interprets information of the received measurement of the UE and can know that the current UE is not present in the cell edge but is present near the center of the serving cell. That is, this may be a case where the measurement value for the serving cell of the UE is good. In this case, the base station can determine to release SUL set for the concerned UE. This is to allow the UE to use more UE capability and to provide more wireless resources.
• the base station sets an RRCREconfiguration message and delivers the message to the UE for configuring the UE with determination at the above operation.
• the concerned message may include ReconfigurationWithSync and ServingCellConfigCommon having only the uplink (NUL) configuration information.
• NUL uplink
• the UE is instructed to re-perform synchronous configuration via random access, release SUL configuration from the concerned cell, and apply only the NUL configuration.
• the UE applies the configuration for the set NUL and performs a random access procedure for the concerned cell, and the base station performs the concerned random access procedure.
• the base station and the UE perform data transmission and reception.
• FIG. 2H illustrates, in block diagram format, an example of an internal structure of the UE according to certain embodiments of this disclosure.
• a UE includes an RF (radio frequency) processor (2h-10), a baseband processor (2h-20), a storage (2h-30), and a controller (2h-40).
• RF radio frequency
• RF processor (2h-10) performs a function to transceive signals for band conversion of the signal, amplification, etc. via a wireless channel. That is, the RF processor (2h-10) performs upward transformation of a baseband signal provided from the baseband processor (2h-20) into an RF band signal and thereafter transmits the RF band signal through an antenna, and performs downward transformation of the RF band received through the antenna signal into a baseband signal.
• the RF processor (2h-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog convertor), an ADC (analog to digital convertor), etc.
• the UE may be provided with a plurality of antennas.
• the RF processor (2h-10) may include a plurality of RF chains. Further, the RF processor (2h-10) can perform beamforming. For the beamforming, the RF processor (2h-10) can adjust phases and sizes of respective signals transceived through the plurality of antennas or antenna elements. Also, the RF processor can perform MIMO and can receive plural layers when the MIMO operation is performed.
• baseband processor (2h-20) performs transformation between baseband signal and bitstream according to the physical layer specification of the system. For example, when data is transmitted, the baseband processor (2h-20) encodes and modulates the transmitted bitstream, thereby generating complex symbols. Also when data is received, the baseband processor (2h-20) demodulates and decodes the baseband signal provided from the RF processor (2h-10), thereby restoring the received bitstream. For example, according to the OFDM (orthogonal frequency division multiplexing) method, when data is transmitted, the baseband processor (2h-20) encodes and modulates the transmitted bitstream, thereby generating complex symbols.
• OFDM orthogonal frequency division multiplexing
• the baseband processor (2h-20) After mapping the complex symbols with subcarriers, the baseband processor (2h-20) constructs OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. Also when data is received, the baseband processor (2h-20) segments the baseband signal provided from the RF processor (2h-10) in the unit of OFDM symbols. After restoring signals mapped with the subcarriers through FFT (fast Fourier transform) operation, the baseband processor (2h-20) restores the received bitstream through demodulation and decoding.
• IFFT inverse fast Fourier transform
• CP cyclic prefix
• the baseband processor (2h-20) and the RF processor (2h-10) transceive signals. Accordingly, the baseband processor (2h-20) and the RF processor (2h-10) may be referred to as a transmitter, a receiver, a transceiver or a communicator. Further, at least one of the baseband processor (2h-20) and the RF processor (2h-10) may include a plurality of communication modules so as to support a number of different wireless connection technologies. Also, at least one of the baseband processor (2h-20) and the RF processor (2h-10) may include the different communication modules so as to process signals of different frequency bands.
• the different wireless connection technologies may include wireless LAN (e.g., IEEE 802.11), cellular network (e.g., LTE), etc.
• the different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz, NRhz) bands and millimeter (MM) wave (e.g., 60 GHz) bands.
• SHF super high frequency
• MM millimeter
• storage (2h-30) stores basic programs for operation of the UE, application programs and data such as configuration information.
• the storage (2h-30) may store information associated with a second connection node that performs wireless communication by use of a second wireless connection technology. Also, the storage (2h-30) provides the stored data according to request from the controller (2h-40).
• the controller (2h-40) controls general operations of the UE.
• the controller (2h-40) transceives signals through the baseband processor (2h-20) and the RF processor (2h-10).
• the controller (2h-40) records data on the storage (2h-30) and reads the data.
• the controller (2h-40) may include at least one processor.
• the controller (2h-40) may include a CP (communication processor) that performs control for communication and an AP (application processor) that controls upper layers such as application programs.
• FIG. 2I illustrates, in block diagram format, an example of a configuration of the base station according to various embodiments of this disclosure.
• the base station includes an RF processor (2i-10), a baseband processor (2i-20), a backhaul communicator (2i-30), a storage (2i-40), and a controller (2i-50).
• the RF processor (2i-10) functions to transceive signals for band change of signals and amplification, etc. via a wireless channel. That is, the RF processor (2i-10) performs upward transformation of a baseband signal provided from the baseband processor (2i-20) into an RF band signal and transmits the RF band signal through an antenna, and performs downward transformation of an RF band signal received through the antenna into a baseband signal.
• the RF processor (2i-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
• FIG. 2I only one antenna is illustrated, but a first connection node may have a plurality of antennas.
• the RF processor (2i-10) may include a plurality of RF chains. Further, the RF processor (2i-10) can perform beamforming. For the beamforming, the RF processor (2i-10) can adjust phases and sizes of respective signals transceived through the plurality of antennas or antenna elements. Also, the RF processor can perform downward MIMO operating by transmitting one or more layers.
• baseband processor (2i-20) performs a transformation between the baseband signal and bitstream according to the physical layer specification of a first wireless connection technology. For example, when data is transmitted, the baseband processor (2i-20) encodes and modulates the transmitted bitstream, thereby generating complex symbols. Also when data is received, the baseband processor (2i-20) demodulates and decodes the baseband signal provided from the RF processor (2i-10), thereby restoring the received bitstream. For example, according to the OFDM (orthogonal frequency division multiplexing) method, when data is transmitted, the baseband processor (2i-20) encodes and modulates the transmitted bitstream, thereby generating complex symbols.
• OFDM orthogonal frequency division multiplexing
• the baseband processor (2i-20) After mapping the complex symbols with subcarriers, the baseband processor (2i-20) constructs OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. Also when data is received, the baseband processor (2i-20) segments the baseband signal provided from the RF processor (2i-10) in the unit of OFDM symbols. After restoring signals mapped with the subcarriers through a FFT (fast Fourier transform) operation, the baseband processor (2i-20) restores the received bitstream through demodulation and decoding. As described above, the baseband processor (2i-20) and the RF processor (2i-10) transceive signals. Accordingly, the baseband processor (2i-20) and the RF processor (2i-10) may be referred to as a transmitter, a receiver, a transceiver, a communicator or a wireless communicator.
• IFFT inverse fast Fourier transform
• CP cyclic prefix
• backhaul communicator (2i-30) provides an interface for performing communication with other nodes in the network. That is, the backhaul communicator (2i-30) transforms bitstream transmitted from a primary base station to any other node, for example, to a supplementary base station, a core network, etc. into physical signals, and physical signals received from the other node are transformed into bitstream.
• the storage (2i-40) stores basic programs for operation of the primary base station, application programs and data such as configuration information.
• the storage (2i-40) may store information associated with a bearer allotted to the connected UE, measurement results reported from the connected UE, etc.
• the storage (2i-40) may provide multiple connection to the UE or store information that can be a basis to determine interruption of the connection.
• the storage (2i-40) also provides stored data at the request from the controller (2i-50).
• the controller (2i-50) controls general operations of the primary base station.
• the controller (2i-50) transceives signals through the baseband processor (2i-20) and the RF processor (2i-10) or the backhaul communicator (2i-30).
• the controller (2i-50) records data on the storage (2i-40) and reads the data.
• the controller (i-50) may include at least one processor.
• an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments.
• the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Databases & Information Systems (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (1)

Applications Claiming Priority (2)

Related Child Applications (1)

Publications (3)

Family

ID=73017918

Family Applications (2)

Family Applications Before (1)

Country Status (5)

Families Citing this family (9)

Family Cites Families (12)

• 2019
  • 2019-05-02 KR KR1020190051794A patent/KR102711430B1/ko active IP Right Grant
• 2020
  • 2020-04-29 WO PCT/KR2020/005780 patent/WO2020222571A1/en unknown
  • 2020-04-29 EP EP24178524.5A patent/EP4401507A3/de active Pending
  • 2020-04-29 CN CN202080032759.1A patent/CN113785604A/zh active Pending
  • 2020-04-29 EP EP20798521.9A patent/EP3949472B1/de active Active
  • 2020-04-30 US US16/863,822 patent/US11218870B2/en active Active
• 2022
  • 2022-01-03 US US17/567,763 patent/US11812508B2/en active Active
• 2023
  • 2023-11-06 US US18/503,061 patent/US20240073676A1/en active Pending

Also Published As

Similar Documents

Legal Events