WO2023013954A1 - Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil - Google Patents

Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil Download PDF

Info

Publication number
WO2023013954A1
WO2023013954A1 PCT/KR2022/011007 KR2022011007W WO2023013954A1 WO 2023013954 A1 WO2023013954 A1 WO 2023013954A1 KR 2022011007 W KR2022011007 W KR 2022011007W WO 2023013954 A1 WO2023013954 A1 WO 2023013954A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
gnb
base station
recnf
control
Prior art date
Application number
PCT/KR2022/011007
Other languages
English (en)
Korean (ko)
Inventor
김성훈
Original Assignee
주식회사 블랙핀
김성훈
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 블랙핀, 김성훈 filed Critical 주식회사 블랙핀
Publication of WO2023013954A1 publication Critical patent/WO2023013954A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present disclosure relates to a method and apparatus for changing a secondary node in a wireless communication system.
  • the 5G communication system In order to meet the growing demand for wireless data traffic after the commercialization of 4G communication systems, 5G communication systems are being developed. In order to achieve a high data rate, the 5G communication system has introduced a very high frequency (mmWave) band (eg, such as the 60 GHz band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming and large scale antenna technologies are used. In the 5G communication system, scalability is increased by dividing the base station into a central unit and a distribution unit. In addition, the 5G communication system aims to support very high data rates and very low transmission delays in order to support various services.
  • mmWave very high frequency
  • FD-MIMO Full Dimensional MIMO
  • Disclosed embodiments are intended to provide a method and apparatus for efficiently supporting a secondary base station change in a wireless communication system.
  • the method in a method for controlling switching of a secondary base station, includes a secondary base station central unit receiving a first control message from a primary base station and transmitting a plurality of second control messages to the secondary base station distribution unit. and receiving a plurality of third control messages from the secondary base station distribution unit and transmitting a fourth control message including a first container and a second container to the primary base station, wherein the first container includes a plurality of cell group settings,
  • the second container contains one NR control message.
  • the disclosed embodiments provide a method and apparatus for efficiently supporting a secondary base station change in a wireless communication system.
  • FIG. 1 is a diagram illustrating the structure of an LTE system and an E-UTRAN according to the present disclosure.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system according to the present disclosure.
  • 3A is a diagram illustrating structures of a 5G system and an NG-RAN according to an embodiment of the present disclosure.
  • 3B is a diagram illustrating the structure of a GNB according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating a radio protocol structure in a 5G system according to an embodiment of the present disclosure.
  • FIG. 5 is a diagram illustrating the structure of an EN-DC according to an embodiment of the present disclosure.
  • 6A is a diagram illustrating operations of a terminal and a base station performing an EN-DC operation according to the first embodiment of the present invention.
  • 6B is a diagram illustrating another operation of a terminal and a base station performing an EN-DC operation according to the first embodiment of the present invention.
  • Figure 7a is a diagram showing the structure of the LTE reconfiguration message for the first procedure.
  • Figure 7b is a diagram showing the structure of the LTE reconfiguration message for the second procedure.
  • 7c is a diagram illustrating the structure of an SGNB ADD ACK message for the first procedure.
  • 7d is a diagram illustrating the structure of an SGNB ADD ACK message for the second procedure.
  • FIG. 8 is a flowchart illustrating an operation of the central apparatus of a target secondary base station according to the first embodiment.
  • FIG. 9 is a flowchart for explaining a terminal operation according to the first embodiment.
  • FIG. 10 is a block diagram showing the internal structure of a terminal to which the present invention is applied.
  • FIG. 11 is a block diagram showing the internal structure of a base station to which the present invention is applied.
  • connection node a term referring to network entities, a term referring to messages, a term referring to an interface between network entities, and a term referring to various types of identification information. Etc. are illustrated for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings may be used.
  • the present invention uses terms and names defined in the 3rd Generation Partnership Project (3GPP) standard, which is the most up-to-date among existing communication standards.
  • 3GPP 3rd Generation Partnership Project
  • the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards.
  • Table 1 lists the abbreviations used in the present invention.
  • Table 2 defines terms frequently used in the present invention.
  • Terminology Definition Cell combination of downlink and optionally uplink resources The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources.
  • Global cell identity An identity to uniquely identify an NR cell. It is consisted of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1.
  • gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.
  • Information element A structural element containing single or multiple fields is referred as information element.
  • SCG Cell For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure.
  • Serving Cell For a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells.
  • SpCell primary cell of a master or secondary cell group.
  • Cell Group in dual connectivity a group of serving cells associated with either the MeNB or the SeNB.
  • En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC.
  • Master Cell Group in MR-DC a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells.
  • master node in MR-DC the radio access node that provides the control plane connection to the core network. It may be a Master eNB (in EN-DC), a Master ng-eNB (in NGEN-DC) or a Master gNB (in NR-DC and NE-DC).
  • NG-RAN node either a gNB or an ng-eNB.
  • Secondary Cell Group in MR-DC a group of serving cells associated with the Secondary Node, comprising of the SpCell (PSCell) and optionally one or more SCells.
  • Secondary node in MR-DC the radio access node, with no control plane connection to the core network, providing additional resources to the UE. It may be an en-gNB (in EN-DC), a Secondary ng-eNB (in NE-DC) or a Secondary gNB (in NR-DC and NGEN-DC).
  • Conditional PSCell Change a PSCell change procedure that is executed only when PSCell execution condition(s) are met.
  • gNB Central Unit a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs.
  • the gNB-CU terminates the F1 interface connected with the gNB-DU.
  • gNB Distributed Unit gNB-DU
  • One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU.
  • the gNB-DU terminates the F1 interface connected with the gNB-CU.
  • E-RAB An E-RAB uniquely identifies the concatenation of an S1 Bearer and the corresponding Data Radio Bearer.
  • NAS Non Access Stratum
  • Table 3 is an abbreviation of various messages, IEs, and terms of the present invention.
  • Table 4 is a description of the main technical terms used in the present invention.
  • Terminology Definition PSCell change This means that the current PSCell is changed to a new PSCell, and includes a change of the PSCell within the same SN and a change of the PSCell between SNs.
  • the addition of a PSCell can also be seen as a PSCell change.
  • CG-ConfigInfo IE It is transmitted from the MN to the SN or from the CU to the DU and consists of the following information.
  • l Capability information of the UE l Measurement results of candidate cells that can be added as serving cells (MeasResultList2NR) l MCG's DRX information, etc.
  • CG-Config IE SN delivers to MN or CU to DU and consists of the following information l NR RRCReconfiguration message containing SCG configuration information.
  • the MN transmits the RRCReconfiguration message to the UE as it is without processing it.
  • l Information related to the SCG bearer It includes information specifying a security key to be used in the bearer.
  • l DRX setting information of SCG l ARFCN information indicating the center frequency of PSCell measConfig This is measurement-related information set independently by MN and SN. It is composed of at least one measurement object information (MeasObject), at least one report setting information (ReportConfig), and at least one measurement identifier (MeasId).
  • Measurement target information and report setting information are identified as MeasObjectId and ReportConfigId, respectively, and MeasId consists of one MeasObjectId and one ReportConfigId.
  • MeasId is information instructing to perform a predetermined operation when the measurement result for the related MeasObject meets the condition set in ReportConfigId.
  • TCSPCELL Indicates the target candidate SpCell.
  • the TCSPCELL may be a cell selected by the MN or the S-SN from among cells measured by the UE and reporting the measurement result to the BS. Through the first procedure, one of the TCSPCELLs becomes a PSCell.
  • the E-UTRAN 101 includes an E-UTRA user plane (PDCP/RLC/MAC/PHY) and a control plane. It consists of ENBs 102, 103, and 104 that provide (RRC) to the UE. ENBs are interconnected with each other via the X2 interface.
  • the ENB is connected to a Mobility Management Entity (MME) 105 / Serving-Gateway (S-GW) 106 through an S1 interface.
  • MME 105 and S-GW 106 may be configured as one physical node or separate physical nodes.
  • the eNBs 102, 103, 104 host the functions listed below.
  • radio bearer control radio admission control
  • link mobility control dynamic allocation of resources to UEs in uplink, downlink and sidelink (constant);
  • IP and Ethernet header compression, uplink data decompression and encryption of user data streams are IP and Ethernet header compression, uplink data decompression and encryption of user data streams
  • AMF selection when AMF cannot be selected with information provided by the terminal routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (derived from AMF or O&M), for mobility and scheduling Measurement and measurement reporting configuration, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing, tight interaction between NR and E-UTRA, network slicing support
  • MME 105 hosts functions such as NAS signaling, NAS signaling security, AS security control, S-GW selection, authentication, PWS message transmission support and location management.
  • the S-GW 106 hosts functions such as packet routing and forwarding, uplink and downlink transport level packet marking, and mobility anchoring for handover between eNBs.
  • FIG. 2 is a diagram illustrating a radio protocol structure of an LTE system.
  • the user plane protocol stack is composed of PDCP (201 to 202), RLC (203 to 204), MAC (205 to 206), and PHY (207 to 208).
  • the control clearing protocol stack is composed of NAS (209 to 210), RRC (211 to 212), PDCP, RLC, MAC, PHY.
  • Each protocol sublayer performs functions related to the operations listed in Table 5.
  • Sublayer Functions NAS Authentication, mobility management, security control, etc.
  • RRC System information paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, recovery from radio link failure detection and recovery, NAS message transmission, etc.
  • PDCP Data transmission header compression and decompression, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and out-of-order delivery, etc.
  • PHY Channel coding physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.
  • 3A is a diagram illustrating structures of a 5G system and an NG-RAN according to an embodiment of the present disclosure.
  • the 5G system consists of NG-RAN (301) and 5GC (302).
  • An NG-RAN node is one of the two below.
  • gNB providing NR user plane and control plane towards UE
  • ng-eNB providing E-UTRA user plane and control plane towards UE.
  • the gNBs 305 to 306 and the ng-eNBs 303 to 304 are interconnected through an Xn interface.
  • the gNB and ng-eNB are connected to an Access and Mobility Management Function (AMF) 307 and a User Plane Function (UPF) 308 through an NG interface.
  • AMF 307 and UPF 308 may be configured as one physical node or separate physical nodes.
  • gNBs 305 to 306 and ng-eNBs 303 to 304 host the functions listed below.
  • radio bearer control radio admission control
  • link mobility control dynamic allocation of resources to UEs in uplink, downlink and sidelink (constant);
  • IP and Ethernet header compression, uplink data decompression and encryption of user data streams are IP and Ethernet header compression, uplink data decompression and encryption of user data streams
  • AMF selection when AMF cannot be selected with information provided by the terminal routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (derived from AMF or O&M), for mobility and scheduling Measurement and measurement reporting configuration, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing, tight interaction between NR and E-UTRA, network slicing support
  • AMF 307 hosts functions such as NAS signaling, NAS signal security, AS security control, S-GW selection, authentication, mobility management and location management.
  • UPF 308 hosts functions such as packet routing and forwarding, transport level packet marking on the uplink and downlink, QoS management, and mobility anchoring for mobility.
  • 3B is a diagram illustrating the structure of a GNB according to an embodiment of the present disclosure.
  • the gNBs 311 to 312 may include one gNB-CU 313 and one or more gNB-DUs 314 to 315.
  • the gNB-CU and gNB-DU are connected through the F1 interface.
  • One gNB-DU is connected only to one gNB-CU.
  • the gNB-CU provides RRC, SDAP, and PDCP protocol sublayers, and the gNB-DU provides RLC, MAC, and PHY protocol sublayers.
  • FIG. 4 is a diagram illustrating a radio protocol structure of a 5G system.
  • the user plane protocol stack is composed of SDAP (401 to 402), PDCP (403 to 404), RLC (405 to 406), MAC (407 to 408), and PHY (409 to 410).
  • the control clearing protocol stack is composed of NAS (411 to 412), RRC (413 to 414), PDCP, RLC, MAC, PHY.
  • Each protocol sublayer performs functions related to the operations listed in Table 8.
  • Sublayer Functions NAS Authentication, mobility management, security control, etc.
  • RRC System information paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, recovery from radio link failure detection and recovery, NAS message transmission, etc.
  • RLC Higher layer PDU transmission error correction through ARQ, RLC SDU division and re-division, SDU reassembly, RLC re-establishment, etc.
  • MAC Mapping between logical channels and transport channels multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in a transport block (TB) carried in the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels ranking processing, etc.
  • PHY Channel coding physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.
  • E-UTRAN supports MR-DC through E-UTRA-NR dual connectivity (EN-DC), and the UE It is connected to one eNB (501 to 502) serving as an MN and one en-gNB (503 to 504) serving as an SN.
  • the eNBs 501 to 502 are connected to the EPC 505 through an S1 interface and connected to the en-gNBs 503 to 504 through an X2 interface.
  • the en-gNBs 503 - 504 may be connected to the EPC 505 via the S1-U interface and another en-gNB via the X2-U interface.
  • LTE and NR are expected to coexist for a considerable period of time in the future. It will not be uncommon for one operator to have both LTE and NR. In this case, if the terminal simultaneously transmits and receives data in LTE and NR, the terminal can receive a high transmission rate through NR and stably maintain an RRC connection through LTE. When EN-DC is set, the terminal can transmit and receive data through LTE and NR.
  • the PSCell change procedure generally consists of a process in which the MN or S-SN recognizes the need for change, the T-SN determines configuration information of the new PSCell, and the MN informs the UE of the configuration information of the new PSCell.
  • the PSCell change procedure generally consists of a process in which the MN or S-SN recognizes the need for change, the T-SN determines configuration information of the new PSCell, and the MN informs the UE of the configuration information of the new PSCell.
  • first reconstruction or conditional reconstruction
  • second reconstruction or immediate reconstruction
  • 6A is a diagram for explaining operations of a terminal and a base station performing a second procedure according to the first embodiment of the present invention.
  • the S-SN GNB-CU 603 determines to change the SN of a predetermined terminal through the second procedure. The determination may be made based on a measurement result reported by the terminal, a load of the base station, a radio resource management policy, and the like.
  • the S-SN GNB-CU initiates the procedure by sending an SGNB CHA REQ (606) to the MN (602).
  • SGNB CHA REQ includes the following information.
  • Target node identifier information en-gNB ID of the target node
  • CG-ConfigInfo includes configuration information applied to the UE by the S-SN.
  • the MN In step 608, the MN generates an SGNB ADD REQ based on the information of the SGNB CHA REQ message and transmits it to the T-SN GNB-CU 604 indicated in the target node identifier information.
  • the SGNB ADD REQ includes the following information.
  • MeNB Cell ID PCell's ECGI. With this information, the T-SN considers cells around the MeNB Cell as SpCells.
  • SGNB Addition Trigger Indication IE indicating one of SN change, inter-eNB HO, and intra-eNB HO.
  • Information related to data radio bearer setup Information about the radio bearer to be setup. Can be used for T-SN's call admission control.
  • the T-SN GNB-CU determines whether to accept the SGNB addition request for the UE. If accepted, it is determined which bearer to accept among the bearers of the UE. Then, PDCP configuration information is determined for each accepted bearer.
  • step 611 the T-SN GNB-CU transmits CON SET REQ to the T-SN GNB-DU (605).
  • CON SET REQ includes the following information.
  • SpCell ID Identifier of SpCell determined by T-SN GNB-CU
  • CG-Config PDCP configuration information for each bearer determined by the T-SN GNB-CU, etc.
  • the T-SN GNB-DU Upon receiving the CON SET REQ, the T-SN GNB-DU determines which bearer of the UE to accept the SN change request. If it is decided to accept, RLC configuration information, MAC configuration information, etc. of the accepted bearer are determined. Then, PHY configuration information to be applied to the terminal is determined.
  • the T-SN GNB-DU transmits CON SET RES to the T-SN GNB-CU.
  • CON SET RES includes the following information.
  • CellGroupConfig Various setting information such as RLC setting information and MAC setting information determined in the above step. Although the name is similar, it is information different from CG-config.
  • C-RNTI C-RNTI to be used by the terminal
  • Requested Target Cell ID The SpCell ID that was included in the CON SET REQ. Indicates that CON SET RES is a response message to CON SET REQ.
  • the T-SN GNB-CU Upon receiving the CON SET RES, the T-SN GNB-CU generates NR RECNF using CellGroupConfig and various configuration information determined by itself. Then, CG-Config including the NR RECNF and various information useful to the MN is created.
  • the T-SN GNB-CU transmits an SGNB ADD ACK to the MN.
  • SGNB ADD ACK includes CG-Config. The structure of the SGNB ADD ACK is detailed in FIG. 7-4.
  • LTE RECNF includes NR RECNF, first Transaction id, security key information, and the like.
  • the structure of LTE RECNF for the second procedure is detailed in FIG. 7-2.
  • the MN transmits LTE RECNF to the UE.
  • the terminal Upon receiving the LTE RECNF, the terminal processes the NR RECNF information included in the LTE RECNF to recognize in which cell random access should be performed and which setting should be applied in the new cell.
  • the UE transmits an LTE RECNF CMP to the MN.
  • the LTE RECNF CMP includes a first Transaction id and NR RECNF CMP.
  • the MN Upon receiving the LTE RECNF CMP, the MN sees the first Transaction id and recognizes that the LTE RECNF CMP is a response to the LTE RECNF.
  • MN settings may be adjusted by referring to CG-Config corresponding to the LTE RECNF.
  • the MN transmits the SGNB REC CMP to the T-SN GNB-CU.
  • the T-SN GNB-CU recognizes that the UE has received NR RECNF and will initiate a random access procedure.
  • the MN transmits the SGNB CHA CNF to the S-SN GNB-CU.
  • the S-SN GNB-CU may initiate an SN status transmission procedure and data forwarding.
  • the UE performs a random access process in a specific cell of T-SN GNB-DU and a cell designated as SpCell in NR RECNF.
  • Random access consists of the UE transmitting a preamble in the GNB-DU, the GNB-DU transmitting a random access response to the UE, and the UE transmitting the PUSCH in the GNB-DU.
  • the UE transmits the C-RNTI MAC CE.
  • the C-RNTI MAC CE contains the C-RNTI determined by the T-SN GNB-DU for the cell.
  • the T-SN GNB-DU recognizes which terminal the random access is for by looking at the C-RNTI.
  • the T-SN GNB-DU generates an ACC SUC.
  • the T-SN GNB-DU transmits the ACC SUC to the T-SN GNB-CU.
  • the ACC SUC contains the following information.
  • NR CGI NR CGI of a cell in which the UE completed random access
  • the S-SN GNB-CU transmits the SN STA TRA.
  • the SN STA TRA includes the PDCP SN and HFN of the bearer to which data forwarding is to be applied.
  • the SN STA TRA is transmitted to the T-SN GNB-CU via the MN.
  • the T-SN GNB-CU refers to the PDCP SN and HFN included in the SN STA TRA to determine a PDCP SN to be applied during data transmission.
  • the S-SN GNB-CU starts data forwarding.
  • the S-SN GNB-CU transmits PDCP SDUs that have not yet been transmitted and PDCP SDUs that have been transmitted but have not been confirmed to be transmitted to the MN through the GTP tunnel, and the MN transmits them to the T-SN GNB-CU.
  • the T-SN GNB-CU processes them as PDCP PDUs and delivers them as T-SN GNB-DUs.
  • the T-SN GNB-DU transmits the PDCP PDU to the UE.
  • 6B is a diagram illustrating operations of a terminal and a base station performing a first procedure according to a first embodiment of the present invention.
  • the S-SN GNB-CU determines to change the SN through the first procedure. The determination may be made based on a measurement result reported by the terminal, a load of the base station, a radio resource management policy, and the like.
  • the S-SN GNB-CU initiates the procedure by sending an SGNB CHA REQ to the MN.
  • SGNB CHA REQ includes the following information.
  • Target node identifier information en-gNB ID of the target node
  • CG-ConfigInfo includes setting information applied to the terminal by the S-SN.
  • First information related to the first procedure This may be a list of identifiers of TCSPCELLs related to the first procedure.
  • the S-SN GNB-CU selects k TCSPCELLs based on the measurement results of the UE.
  • Second information related to the first procedure Information representing the nature of the first procedure, indicating whether the first procedure for the TCSPCELLs is a start of a new procedure or a replacement of an existing procedure.
  • the MN In step 643, the MN generates an SGNB ADD REQ based on the information of the SGNB CHA REQ message and transmits it to the T-SN GNB-CU indicated in the target node identifier information.
  • the SGNB ADD REQ includes the following information.
  • MeNB Cell ID PCell's ECGI.
  • the T-SN Upon receiving this information, the T-SN considers cells around the MeNB Cell as SpCells.
  • Information related to data radio bearer setup Information about the radio bearer to be setup. Can be used for T-SN's call admission control.
  • the first procedure does not use SGNB Addition Trigger Indication information. This is because information related to the first procedure can inform that the corresponding procedure is related to the SN change.
  • the T-SN GNB-CU determines which TCSPCELL to accept and which bearer of the UE to accept for each accepted TCSPCELL. Then, PDCP configuration information is determined for each accepted bearer. The T-SN GNB-CU generates CG-Config containing the determined information for each accepted TCSPCELL.
  • the T-SN GNB-CU transmits m CON SET REQs to the T-SN GNB-DU.
  • One CON SET REQ corresponds to one TCSPCELL and includes the following information.
  • SpCell ID Identifier of accepted TCSPCELL
  • CG-Config PDCP setting information determined for the TCSPCELL, etc.
  • the T-SN GNB-DU Upon receiving the CON SET REQ for any TCSPCELL, the T-SN GNB-DU determines whether to accept it. And, if accepted, it decides which bearer to accept. Determines RLC configuration information, MAC configuration information, etc. of the accepted bearer. Then, PHY configuration information to be applied to the terminal is determined.
  • the T-SN GNB-DU transmits n CON SET RES to the T-SN GNB-CU.
  • Each CON SET RES includes the following information.
  • CellGroupConfig Includes various setting information determined for the corresponding TCSPCELL
  • C-RNTI C-RNTI to be used by the terminal
  • Requested Target Cell ID NR CGI of the corresponding TCSPCELL.
  • the T-SN GNB-CU Upon receiving n CON SET RES, the T-SN GNB-CU generates an SGNB ADD ACK.
  • the structure of the SGNB ADD ACK is detailed in FIG. 7-3.
  • the T-SN GNB-CU transmits an SGNB ADD ACK to the MN.
  • MN generates LTE RECNF including NR RECNF received through SGNB ADD ACK.
  • LTE RECNF includes the first Transaction id.
  • the structure of LTE RECNF is detailed in FIG. 7A.
  • step 651 the MN transmits LTE RECNF to the terminal.
  • the terminal Upon receiving the LTE RECNF, the terminal processes the NR RECNF information included therein to recognize the configuration of TCSPCELLs and the execution conditions corresponding to each TCSPCELL.
  • the UE transmits an LTE RECNF CMP to the MN.
  • LTE RECNF CMP includes the first Transaction id.
  • the terminal that has transmitted the LTE RECNF CMP performs a conditional reconfiguration evaluation procedure to determine whether the conditional reconfiguration condition is satisfied.
  • the UE determines whether the measurement result of the cell (TCSPCELL) corresponding to the cell identifier indicated in the third NR reconfiguration message satisfies the execution condition, and if so, the second NR reconfiguration message corresponding to the cell that satisfies the execution condition is applied. to perform conditional reconstruction.
  • the UE performs a random access process in a specific cell of the T-SN GNB-DU, that is, a cell designated as SpCell in the third NR RECNF for which the execution condition is satisfied.
  • Random access consists of the UE transmitting a preamble in the GNB-DU, the GNB-DU transmitting a random access response to the UE, and the UE transmitting the PUSCH in the GNB-DU.
  • the UE transmits the C-RNTI MAC CE.
  • the C-RNTI MAC CE contains the C-RNTI determined by the T-SN GNB-DU for the cell.
  • the T-SN GNB-DU recognizes which terminal the random access is for by looking at the C-RNTI.
  • the T-SN GNB-DU generates an ACC SUC.
  • the T-SN GNB-DU transmits the ACC SUC to the T-SN GNB-CU.
  • the ACC SUC contains the following information.
  • NR CGI NR CGI of a cell in which the UE completed random access
  • the UE transmits the ULIT to the MN.
  • ULIT includes NR RECNF CMP and CRID.
  • the MN identifies the CG-Config corresponding to the CRID and reconfigures the MN's settings according to the CG-Config.
  • the MN transmits the SGNB REC CMP to the T-SN GNB-CU.
  • SGNB REC CMP includes NR RECNF CMP.
  • the NR RECNF CMP includes the Transaction id of the third NR RECNF for which the execution condition is satisfied.
  • the T-SN GNB-CU recognizes that the UE has performed conditional reconfiguration.
  • the MN transmits the SGNB CHA CNF to the S-SN GNB-CU.
  • the S-SN GNB-CU may initiate an SN status transmission procedure and data forwarding.
  • the S-SN GNB-CU transmits the SN STA TRA.
  • the SN STA TRA includes the PDCP SN and HFN of the bearer to which data forwarding is to be applied.
  • the SN STA TRA is transmitted to the T-SN GNB-CU via the MN.
  • the S-SN GNB-CU starts data forwarding.
  • the S-SN GNB-CU transmits PDCP SDUs that have not yet been transmitted and PDCP SDUs that have been transmitted but have not been confirmed to be transmitted to the MN through the GTP tunnel, and the MN transmits them to the T-SN GNB-CU.
  • the T-SN GNB-CU processes them as PDCP PDUs and delivers them as T-SN GNB-DUs.
  • the T-SN GNB-DU transmits the PDCP PDU to the UE.
  • LTE RECNF for setting the first procedure to the UE in EN-DC operation is shown in FIG. 7A.
  • the LTE RECNF includes a 1st Transaction id generated by the MN and a 1NR RECNF 702 generated by the T-SN.
  • the first RECNF may include various information depending on the purpose of the related procedure. If it is for the first procedure (conditional reconstruction), the first NR RECNF includes conditional reconstruction related information 710 .
  • Conditional reconfiguration related information includes at least one CondReconfigToAddMod IE (703 to 720 to 721).
  • Each CondReconfigToAddMod IE includes a configuration identifier 704, an execution condition 705, a 2nd NR RECNF including various setting information 706, and an execution condition cell group IE 722.
  • the second NR RECNF includes radio bearer configuration information 708, a counter for calculating a security key 709, and a third NR RECNF 707.
  • the third NR RECNF includes a secondaryCellGroup IE, and the IE includes TCSPCELL configuration information.
  • one 1st NR reconstruction message for 1st reconstruction includes a plurality of 2nd NR RECNFs, and one 2nd NR RECNF corresponds to one TCSPCELL.
  • One second NR RECNF corresponds to one configuration identifier, one execution condition, and one execution condition cell group.
  • the first NR RECNF includes a second Transaction ID
  • the second NR RECNF includes a third Transaction ID
  • the third NR RECNF includes a fourth Transaction ID.
  • LTE RECNF for setting the second procedure to the UE in EN-DC operation is shown in FIG. 7B.
  • the LTE RECNF includes the first Transaction id generated by the MN and the 1NR RECNF 702 generated by the T-SN GNB-CU.
  • the first RECNF may include various information depending on the purpose of the related procedure.
  • the first NR RECNF includes radio bearer configuration information 728, a counter for calculating a security key 729, and a fourth NR RECNF 727.
  • the fourth NR RECNF includes a secondaryCellGroup IE, and the IE includes SpCell/PSCell configuration information.
  • one 1st NR reconstruction message for the second reconstruction includes one 4th NR RECNF.
  • the 1st NR RECNF includes the 2nd Transaction ID and the 4th NR RECNF includes the 5th Transaction ID, both generated by the T-SN GNB-CU.
  • the structure of the SGNB ADD ACK for the first procedure of the UE in EN-DC operation is shown in FIG. 7c.
  • the SGNB ADD ACK 731 includes at least a first container 732 and a second container 733.
  • the first container stores a number of CG-Configs.
  • CG-config (hereafter, 1st CG-config, 734) stored in the first container includes Assistance Info for MN 735 and CondReconfigurationId (736, hereinafter, CRID).
  • Assistance info for MN includes information that the MN needs to know in order to determine or adjust its configuration, for example, DRX configuration in the SN, band combination information selected in the SN, and the like.
  • the second container contains one NR RECNF 739.
  • the NR RECNF 739 is the first NR RECNF 702 contained in the LTE RECNF.
  • the first NR RECNF may include a plurality of CondReconfigToAddMod IEs, and one CondReconfigToAddMod may include one second NR RECNF 737 and one CRID 738.
  • the CG-Config 735 of the first container and the second NR RECNF 737 of the second container correspond one-to-one and are connected by CRIDs 736 and 738.
  • the number of CG-Configs included in the first container is equal to the number of second NR RECNFs included in the first NR RECNF.
  • the structure of the SGNB ADD ACK for the second procedure of the UE in EN-DC operation is shown in FIG. 7d.
  • the SGNB ADD ACK 741 includes one container 742, hereinafter a third container, and the third container includes one CG-Config 743.
  • CG-Config (hereinafter referred to as second CG-Config) stored in the third container includes Assistance info for MN 744 and NR RECNF 745, which are information necessary for the MN to adjust its own settings.
  • NR RECNF 745 is NR RECNF 722.
  • Assistance info for MN includes information that the MN needs to know in order to determine or adjust its configuration, for example, DRX configuration in the SN, band combination information selected in the SN, and the like.
  • the first CG-Config does not include NR RECNF, but instead includes CRID.
  • the CRID corresponds to one of a plurality of NR RECNFs included in the second container.
  • FIG. 8 is a flowchart for explaining T-SN GNB-CU operation according to the first embodiment.
  • step 801 the T-SN GNB-CU receives a control message requesting preparation of resources for EN-DC operation from the MN.
  • step 811 the T-SN GNB-CU determines whether information related to the first procedure is included in the control message. If included, proceed to step 816, otherwise proceed to step 841.
  • step 816 the T-SN GNB-CU selects m TCSPCELLs among the k TCSPCELLs included in the first information related to the first procedure and generates a CON SET REQ for each TCSPCELL. m number of CON SET REQs are transmitted to the T-SN GNB-DU. One CON SET REQ corresponds to one TCSPCELL. Proceeding to step 816 means that the control message received in step 801 includes one cell group setting information, one execution condition information, and a plurality of cell identifiers.
  • the T-SN GNB-CU receives n CON SET RES from the T-SN GNB-CU.
  • One CON SET RES corresponds to one accepted TCSPCELL.
  • CON SET RES includes information such as CellGroupConfig.
  • the T-SN GNB-CU In step 826, the T-SN GNB-CU generates an SGNB ADD ACK message including the first container and the second container and transmits it to the MN.
  • the first container is composed of a plurality of first CG-Configs, and the first CG-config does not include NR RECNF but includes Assistance Info for MN and CRID.
  • the second container includes the first NR RECNFs and includes the same number of second NR RECNFs as the plurality of CRIDs.
  • the T-SN GNB-CU creates the first container and the second container so that the first CG-Config of the first container and the NR RECNF of the second container are connected by CRID.
  • the T-SN GNB-CU receives the SN STA TRA from the MN, recognizes a PDCP SN to be applied to downlink data, and processes the PDCP SDU transferred from the MN as a PDCP PDU.
  • step 861 the T-SN GNB-CU transmits the PDCP PDU to the T-SN GNB-DU.
  • step 841 the T-SN GNB-CU transmits one CON SET REQ to the T-SN GNB-DU.
  • CON SET REQ contains information such as SpCell ID.
  • the T-SN GNB-CU receives one CON SET RES from the T-SN GNB-CU.
  • CON SET RES includes information such as CellGroupConfig.
  • the T-SN GNB-CU In step 826, the T-SN GNB-CU generates an SGNB ADD ACK message including the third container and transmits it to the MN.
  • the third container is composed of one second CG-Config, and the second CG-config includes NR RECNF and Assistance Info for MN and does not include a CRID.
  • the T-SN GNB-CU receives the SN STA TRA from the MN, recognizes a PDCP SN to be applied to downlink data, and processes the PDCP SDU transferred from the MN as a PDCP PDU.
  • step 861 the T-SN GNB-CU transmits the PDCP PDU to the T-SN GNB-DU.
  • FIG. 9 is a flowchart illustrating an operation of a terminal performing a first procedure according to a first embodiment.
  • step 901 the UE reports the capabilities of the UE related to the EN-DC and the first reconfiguration procedure to the first base station (MN or MeNB).
  • MN the first base station
  • band combination information in which EN-DC is supported (a list of band combinations supporting EN-DC);
  • Second performance information a list of EN-DC band combinations supporting 1 st reconfiguration among band combinations supported by EN-DC;
  • the second capability information indicates which NR band of a band combination among the band combinations reported as the first capability information supports the first reconstruction.
  • the second capability information is information indicating whether intra-band first reconfiguration is supported.
  • the third capability information is a combination of NR bands composed of two NR bands, and indicates that inter-band first reconfiguration is supported in the NR band combination included in the third capability information. For example, if a (N1, N2) band combination is included in the third capability information, it means that the first reconstruction between N1 and N2 is supported. In this case, all NR bands (for example, N1 and N2) belonging to the band combination included in the third capability information are NR bands supported by EN-DC.
  • the terminal receives LTE RECNF.
  • the LTE RECNF includes a first NR RECNF. If the LTE RECNF is a message indicating first reconfiguration, the first NR RECNF includes first information.
  • the first information includes at least one or more pieces of second information, and the second information always includes third information and fourth information and optionally includes fifth information.
  • the third information corresponds to one TCSPCELL.
  • the third information consists of one or two MeasIds, and defines an execution condition for resetting the TCSPCELL.
  • the fourth information is the second NR RECNF, and includes third NR RECNF including radio bearer configuration information, security key related information, and TCSPCELL configuration information.
  • Fifth information is information indicating which of MCG and SCG (or MeNB and SgNB, or MN and S-SN) the execution condition is associated with.
  • the third information and the fifth information define execution conditions of the first reconstruction for each TCSPCELL (or for each second information).
  • third information and fifth information commonly applied to all TCSPCELLs (or second information) included in one first NR message.
  • an operation of the terminal it is also possible to define an operation of the terminal to include common third information and common fifth information as lower IEs of the first information and ignore individual third information included as lower IEs of the second information. In this case, if common third information exists, the terminal applies the common third information to all TCSPCELLs included in one piece of first information, and if common third information does not exist, applies third information indicated for each TCSPCELL. do.
  • One LTE RECNF includes one 1st NR RECNF, one 1st NR RECNF includes multiple 2nd NR RECNFs, and one 2nd NR RECNF includes one 3rd NR RECNF. That is, one LTE RECNF may include a plurality of third NR RECNFs, the same number of third information and the same number of fourth information, and may include another plurality of fifth information.
  • One RECNF includes one Transaction ID.
  • the LTE RECNF includes a first Transaction id
  • the first NR RECNF includes a second Transaction id.
  • the second NR RECNF and the third NR RECNF include a third Transaction id and a fourth Transaction id, respectively.
  • step 911 the terminal transmits the LTE RECNF CMP to the first base station.
  • the LTE RECNF CMP includes a first Transaction id.
  • step 916 the UE initiates a first reconfiguration procedure because the first reconfiguration information is included in the first NR RECNF included in the received LTE RECNF.
  • the terminal determines which cell group (or which node) the MeasId indicated in the third information is associated with based on the third and fifth information set for each TCSPCELL. If there is no fifth information, it is determined that the execution condition for the corresponding TCSPCELL is set by the S-SN, and MeasId is related to the Source SCG (or S-SN). And the meaning of MeasId is interpreted according to MeasConfig of Source SCG (or S-SN). If there is fifth information, it is determined that the execution condition for the corresponding TCSPCELL is set by the MN, and MeasId is related to the MCG (or MN).
  • MeasId is interpreted according to MeasConfig of MCG (or MN).
  • the execution condition for the corresponding TCSPCELL is set by the CG (or node) indicated by the 5th information among MCG and SCG (or between MN and S-SN), and MeasId is the CG (or node ) is judged to be related to And the meaning of MeasId is interpreted according to MeasConfig of the CG (or node).
  • MeasId having a value between 1 and 32 and MeasId-v1250 having a value between 33 and 64.
  • the former is named 5 bit MeasId, and the latter is named 5 bit MeasId-Ext.
  • NR has MeasId having a value between 1 and 64, and is named as 6 bit MeasId in the present invention.
  • the MN may inform the T-SN of MeasId to be used as an execution condition determined by the MN.
  • MN changes 5 bit MeasId or 5 bit MeasId-Ext to 6 bit MeasId, includes it in SGNB ADD REQ, and informs T-SN. If the MN selects 5-bit MeasId as an execution condition, it sets the MSB of 6-bit MeasId to 0 and sets the remaining 5 bits to 5-bit MeasId. If the MN selects 5 bit MeasId-Ext as an execution condition, it sets the MSB of 6 bit MeasId to 1 and sets the remaining 5 bits to 5 bit MeasId.
  • the UE receives 6 bit MeasId as an execution condition through RECNF. If the execution condition is determined by the S-SN, that is, if the execution condition cell group IE is SCG, the terminal determines the execution condition as it is without converting the received 6-bit MeasId. If the execution condition is determined by the MN, that is, if the execution condition cell group IE is MCG, the UE determines the execution condition by converting the received 6-bit MeasId into 5-bit MeasId or 5-bit MeasId-Ext. If the MSB of 6-bit MeasId is 0, the remaining 5 bits are interpreted as 5-bit MeasId and related ReportConfig and MeasObject are selected. If the MSB of 6-bit MeasId is 1, the remaining 5 bits are interpreted as 5-bit MeasId-Ext and the related ReportConfig and MeasObject are selected.
  • the terminal performs a conditional reset evaluation operation. For each second information included in the first information, the terminal considers the serving cell (ie, target candidate cell) indicated in the third NR RECNF of each second information as an 'applicable cell', and the applicable cell Among them, it is determined whether there is a cell that satisfies an event related to an execution condition. In addition, a target candidate cell that satisfies the event is regarded as a triggered cell.
  • step 931 the terminal performs conditional reset.
  • the UE applies the corresponding second NR RECNF to the triggered cell.
  • the terminal transmits the ULIT to the second base station.
  • the ULIT includes the first NR RECNF CMP.
  • the first NR RECNF CMP includes a third Transaction id.
  • the ULIT also includes a CRID corresponding to the triggered cell (or corresponding to the second NR RECNF corresponding to the triggered cell).
  • FIG. 10 is a block diagram showing the internal structure of a terminal to which the present invention is applied.
  • the terminal includes a control unit 1001, a storage unit 1002, a transceiver 1003, a main processor 1004, and an input/output unit 1005.
  • the controller 1001 controls overall operations of the UE related to mobile communication. For example, the controller 1001 transmits and receives signals through the transceiver 1003 . Also, the control unit 1001 writes and reads data in the storage unit 1002 . To this end, the controller 1001 may include at least one processor.
  • the control unit 1001 may include a communication processor (CP) that controls communication and an application processor (AP) that controls upper layers such as application programs.
  • the control unit 1001 controls the storage unit and the transceiver so that the operation of the terminal of FIG. 9 is performed.
  • the storage unit 1002 stores data such as a basic program for operating the terminal, an application program, and setting information.
  • the storage unit 1002 provides stored data according to the request of the control unit 1001 .
  • the transver 1003 includes an RF processing unit, a baseband processing unit, and an antenna.
  • the RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal, transmits the signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal.
  • the RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), and the like.
  • the RF processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation.
  • the baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream.
  • the transceiver is a transceiver.
  • the main processor 1004 controls overall operations except for operations related to mobile communication.
  • the main processor 1004 processes user input transmitted by the input/output unit 1005, stores necessary data in the storage unit 1002, controls the control unit 1001 to perform mobile communication-related operations, and the input/output unit ( 1005) to transmit the output information.
  • the input/output unit 1005 is composed of a device that receives user input, such as a microphone and a screen, and a device that provides information to the user, and performs input and output of user data under the control of a main processor.
  • FIG. 11 is a block diagram showing the configuration of a GNB-CU according to the present invention.
  • the base station includes a control unit 1101, a storage unit 1102, an F1 interface unit 1103, and a backhaul interface unit 1104.
  • the controller 1101 controls overall operations of the base station. For example, the control unit 1101 transmits and receives signals through the transceiver 1103 or the backhaul interface unit 1104 . Also, the control unit 1101 writes and reads data in the storage unit 1102 . To this end, the controller 1101 may include at least one processor. The controller 1101 is an F1 interface unit so that the base station operations shown in FIGS. 6 and 8 are performed. storage. Controls the backhaul interface.
  • the storage unit 1102 stores data such as a basic program for the operation of the main base station, an application program, and setting information.
  • the storage unit 1102 may store information about a bearer allocated to a connected terminal, measurement results reported from the connected terminal, and the like.
  • the storage unit 1102 may store information that is a criterion for determining whether to provide or stop multiple connections to the terminal. And, the storage unit 1102 provides the stored data according to the request of the control unit 1101.
  • the interface unit 1103 provides an interface for communicating with the GNB-DU. That is, the F1 interface unit converts a bit stream transmitted through the GNB-DU into a physical signal and converts a physical signal received from the GNB-DU into a bit stream.
  • the backhaul interface unit 1104 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1104 converts a bit string transmitted from the main base station to another node, for example, a secondary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. convert
  • the interface unit and the backhaul interface unit constitute a transmission/reception unit.

Landscapes

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

Abstract

Selon un mode de réalisation, la présente invention concerne un procédé de commande d'un changement de station de base secondaire, comprenant une étape dans laquelle une unité centrale de station de base secondaire reçoit un premier message de commande en provenance d'une station de base principale, transmet une pluralité de deuxièmes messages de commande à des unités de distribution de station de base secondaire, reçoit une pluralité de troisièmes messages de commande en provenance des unités de distribution de station de base secondaire, et transmet, à la station de base principale, un quatrième message de commande comprenant un premier récipient et un second récipient, le premier récipient comprenant une pluralité de configurations de groupe de cellules et le second récipient comprenant un message de commande NR.
PCT/KR2022/011007 2021-08-05 2022-07-27 Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil WO2023013954A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2021-0103224 2021-08-05
KR20210103224 2021-08-05

Publications (1)

Publication Number Publication Date
WO2023013954A1 true WO2023013954A1 (fr) 2023-02-09

Family

ID=85156187

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/011007 WO2023013954A1 (fr) 2021-08-05 2022-07-27 Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil

Country Status (1)

Country Link
WO (1) WO2023013954A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210092725A1 (en) * 2019-03-27 2021-03-25 Ofinno, Llc Cell Information for Access Management

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210092725A1 (en) * 2019-03-27 2021-03-25 Ofinno, Llc Cell Information for Access Management

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.401, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V16.6.0, 13 August 2021 (2021-08-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 79, XP052056341 *
GOOGLE: "Clarification of the default configuration behaviour in SN change", 3GPP DRAFT; R3-182983 DEFAULT CONFIG OPTION IN R15.1.0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Busan, South Korea; 20180521 - 20180525, 11 May 2018 (2018-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051527159 *
INTEL CORPORATION, CATT, ZTE, HUAWEI: "Baseline CR for introducing Rel-16 NR mobility enhancement", 3GPP DRAFT; R3-201587, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Electronic Meeting; 20200420 - 20200430, 5 April 2020 (2020-04-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051868726 *
ZTE: "Discussion on SgNB Change in Option 3 with CU-DU split", 3GPP DRAFT; R3-172924 DISCUSSION ON SGNB CHANGE IN OPTION 3 WITH CU-DU SPLIT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Berlin, Germany; 20170821 - 20170825, 21 August 2017 (2017-08-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051319764 *

Similar Documents

Publication Publication Date Title
WO2018174627A1 (fr) Procédé et dispositif pour indiquer le type de support utilisé pour le prochain message dans un système de communication sans fil
WO2019160327A1 (fr) Procédé et dispositif permettant d'effectuer une resélection de cellule dans un système de communication mobile
WO2012060608A2 (fr) Procédé de coordination de brouillage entre cellules et station de base
WO2019160281A1 (fr) Procédé et appareil pour réaliser un transfert basé sur dc
WO2014142487A1 (fr) Procédé de gestion d'informations concernant des petites cellules actives/inactives dans un système d'accès radio, et appareil destiné à le prendre en charge
WO2019022480A1 (fr) Procédé et appareil permettant d'attribuer des ressources basées sur une porteuse d'ancrage dans un système de communication sans fil
WO2023080470A1 (fr) Procédé et dispositif pour mettre en oeuvre et rapporter une mesure de couche d'application dans un système de communication mobile sans fil
WO2023113340A1 (fr) Procédé et dispositif permettant de libérer une connexion rrc sur la base d'un message de commande rrc dans un réseau non terrestre
WO2023013954A1 (fr) Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil
WO2023013976A1 (fr) Procédé et dispositif de changement de station de base secondaire dans un système de communication mobile sans fil
WO2023013958A1 (fr) Procédé et dispositif de changement de station de base secondaire dans un système de communication mobile sans fil
WO2023013975A1 (fr) Procédé et appareil de modification d'une station de base secondaire dans un système de communication mobile sans fil
WO2023013977A1 (fr) Procédé et appareil de reprise d'une connexion rrc dans un système de communication mobile sans fil
WO2023106716A1 (fr) Procédé et appareil d'exécution de reconfiguration conditionnelle lorsque de multiples conditions associées à de multiples événements sont satisfaites dans un réseau non terrestre
WO2023106708A1 (fr) Procédé et appareil permettant de mesurer une cellule voisine par l'intermédiaire d'une pluralité de configurations de synchronisation de mesure dans un réseau non terrestre
WO2023106709A1 (fr) Procédé et dispositif de déclenchement d'un rapport de résultat de mesure dans un réseau non terrestre sur la base d'une position
WO2023013960A1 (fr) Procédé et dispositif pour changer une station de base secondaire dans un système de communication mobile sans fil
WO2023096377A1 (fr) Procédé et dispositif de traitement de message de radiomessagerie par un terminal dans un système de communication mobile sans fil
WO2023096316A1 (fr) Procédé et appareil de traitement, par une unité distribuée, d'un message de radiomessagerie dans un système de communication mobile sans fil
WO2023096317A1 (fr) Procédé et dispositif permettant de traiter un message de radiorecherche au moyen d'une station de base dans un système de communication mobile sans fil
WO2023022401A1 (fr) Procédé de transmission/réception, par un terminal dans un état rrc_inactif, de données dans un système de communication mobile sans fil, et dispositif
WO2023080471A1 (fr) Procédé et dispositif de mesure de couche d'application et de rapport de cette dernière dans un système de communication mobile sans fil
WO2023022403A1 (fr) Procédé et dispositif de transmission et de réception, par un terminal dans un état rrc_inactif, de données dans un système de communication mobile sans fil
WO2023022408A1 (fr) Procédé et dispositif de transmission d'un rapport d'état de tampon et d'un rapport de marge de puissance par un terminal dans un état rrc_inactive dans un système de communication mobile sans fil
WO2023080472A1 (fr) Procédé et appareil pour effectuer et rapporter une mesure de couche d'application dans un système de communication mobile sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22853332

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE