WO2018231021A1 - Procédé et appareil de traitement de la mobilité dans un système rrc double - Google Patents

Procédé et appareil de traitement de la mobilité dans un système rrc double Download PDF

Info

Publication number
WO2018231021A1
WO2018231021A1 PCT/KR2018/006809 KR2018006809W WO2018231021A1 WO 2018231021 A1 WO2018231021 A1 WO 2018231021A1 KR 2018006809 W KR2018006809 W KR 2018006809W WO 2018231021 A1 WO2018231021 A1 WO 2018231021A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
message
cell
rrc
scg
Prior art date
Application number
PCT/KR2018/006809
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
Priority claimed from KR1020170125584A external-priority patent/KR102388500B1/ko
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Priority to US16/622,730 priority Critical patent/US11432362B2/en
Priority to CN201880039399.0A priority patent/CN110741721A/zh
Priority to EP18818715.7A priority patent/EP3624547A4/fr
Publication of WO2018231021A1 publication Critical patent/WO2018231021A1/fr

Links

Images

Classifications

    • 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
    • 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

  • This patent relates to a technique for performing dual connectivity using Dual RRC.
  • a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE).
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
  • 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation
  • cloud RAN cloud radio access network
  • D2D Device to Device communication
  • D2D Device to Device communication
  • CoMP Coordinated Multi-Points
  • Hybrid FSK and QAM Modulation FQAM
  • SWSC Slide Window Superposition Coding
  • ACM Advanced Coding Modulation
  • FBMC Fan Bank Multi Carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M machine to machine
  • MTC Machine Type Communication
  • IT intelligent Internet technology services can be provided that collect and analyze data generated from connected objects to create new value in human life.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing information technology (IT) technology and various industries. It can be applied to.
  • the master node (MN) and the secondary node (SN) can operate with the RRC respectively.
  • the master node (MN) and the secondary node (SN) may operate with RRC, respectively, in this case, a method for mobility processing is needed.
  • An object of the present invention is to disclose a method and apparatus for improving mobility-related performance when performing dual connectivity using dual RRC.
  • a control method of a terminal is when a connection with a first master node (MN) is released. Transmitting an RRC connection re-establishment request message including identifier information on a secondary node (SN) to a second master node (MN); When the context information about the terminal is included, the method may include receiving an RRC connection reestablishment message from the second MN.
  • MN master node
  • a terminal when a terminal is disconnected from a transceiver for transmitting and receiving a signal and a first master node (MN), the secondary is disconnected.
  • the controller may control the transceiver to receive the RRC connection reestablishment message from the second MN.
  • a method for controlling a master node may include a secondary node (SN) from a terminal from which a connection with another master node (MN) is released.
  • the master node (MN) is a secondary node (MN) from the terminal that is disconnected from the transceiver for transmitting and receiving signals and other master node (MN) Receiving an RRC connection re-establishment request message including identifier information for the secondary node (SN), and if the context information for the terminal includes, and transmits an RRC connection reestablishment message to the terminal It may include a control unit for controlling the transceiver to.
  • the throughput of the terminal when performing dual connectivity using Dual RRC, the throughput of the terminal can be increased by efficiently performing a procedure related to mobility.
  • FIG. 1 is a diagram illustrating a system to which the present invention is applied.
  • FIG. 2 is a diagram illustrating a sequence diagram describing Embodiment 1.
  • FIG. 2 is a diagram illustrating a sequence diagram describing Embodiment 1.
  • FIG. 3 is a diagram illustrating a sequence for describing Embodiment 2.
  • FIG. 4 is a diagram showing a sequence diagram for explaining a sequence diagram for explaining the third embodiment.
  • FIG. 5 is a diagram for explaining a fourth embodiment.
  • FIG. 6 is a diagram illustrating a sequence diagram illustrating case 1 according to a fourth embodiment.
  • FIG. 7 is a sequence diagram illustrating case 2 according to a fourth embodiment.
  • FIG. 9 is a diagram illustrating a sequence diagram illustrating case 4 according to a fourth embodiment.
  • FIG. 10 is a sequence diagram illustrating an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an SCG SRB and an MR is also transmitted to the SCG SRB.
  • FIG. 11 illustrates a sequence diagram of an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an MCG SRB and an MR to an SCG SRB.
  • FIG. 12 is a sequence diagram illustrating an embodiment in which SN RRCConnectionReconfigurationComplete is transmitted to an SCG SRB and an MR to an MCG SRB.
  • FIG. 13 illustrates a sequence diagram of an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an MCG SRB and an MR is also transmitted to the MCG SRB.
  • FIG. 14 illustrates a sequence diagram of an embodiment in which a UL path is set differently although carried in respective RRCconnectionReconfiguration messages of separate measConfig.
  • 15 is a diagram showing a sequence diagram for describing the sixth embodiment.
  • 16A to 16C illustrate a sequence diagram for an embodiment of a master node (MN) initiated SCG change indication.
  • MN master node
  • 17A to 17C illustrate a sequence diagram of an embodiment in which an SN sends an MN indicating an operation required for an SCG change indication IE in an SN modification required message by an MN.
  • FIG. 18 is a diagram illustrating a structure of a terminal according to an embodiment of the present invention.
  • FIG. 19 is a diagram showing the structure of a base station according to an embodiment of the present invention.
  • each block of the flowchart illustrations and combinations of flowchart illustrations may be performed by computer program instructions. Since these computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, those instructions executed through the processor of the computer or other programmable data processing equipment may be described in flow chart block (s). It creates a means to perform the functions. These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, and thus the computer usable or computer readable memory. It is also possible for the instructions stored in to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block (s).
  • Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions for performing the processing equipment may also provide steps for performing the functions described in the flowchart block (s).
  • each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • logical function e.g., a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • the functions noted in the blocks may occur out of order.
  • the two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the corresponding function.
  • ' ⁇ part' used in the present embodiment refers to software or a hardware component such as an FPGA or an ASIC, and ' ⁇ part' performs certain roles.
  • ' ⁇ ' is not meant to be limited to software or hardware.
  • ' ⁇ Portion' may be configured to be in an addressable storage medium or may be configured to play one or more processors.
  • ' ⁇ ' means components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, and the like. Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.
  • components and the 'parts' may be combined into a smaller number of components and the 'parts' or further separated into additional components and the 'parts'.
  • the components and ' ⁇ ' may be implemented to play one or more CPUs in the device or secure multimedia card.
  • ' ⁇ part' may include one or more processors.
  • This technology assumes that when the RAT is heterogeneous, when two different RATs are attached to the common core system, the master node (MN) and the secondary node (SN) operate with the RRC, respectively.
  • MN master node
  • SN secondary node
  • FIG. 1 is a diagram showing a system to which the present invention is applied according to an embodiment of the present invention.
  • an MN 110 connected to a terminal 100 by an LTE eNB, an SN 120 by an NR gNB, and a core by an EPC 130.
  • the MN 110, the SN 120, and the core 130 are gNB, LTE, and NR cores, respectively, or various core and RAN nodes of heterogeneous systems such as eLTE, gNB, and NR cores. May be used.
  • MN master node
  • RRC radio resource control layer
  • MCG master cell group
  • SCG secondary cell group
  • RRE RRC connection re-establishment
  • PCI physical cell ID
  • RRC may not exist in the SN.
  • the connection through SN is performed when the radio link problem / RRC reconfiguration failure / other types of operations that require reconnection at the RRC level are performed. After executing, it is activated again as needed. For example, even if there is no problem with the link of the SN itself, if the MN link is unstable, the connection utilization of the SN side drops. In addition, interruption may proceed very long in view of data during SN link transmission.
  • FIG. 2 is a diagram showing Example 1.
  • the SRB (eg, SRB3) of the SN side should be set in advance in the UE and the SN, or the operation of setting the SRB3 before the failure of the MN should be entered in advance.
  • FIG. 2 illustrates an embodiment in which the MN 20 connected to the terminal 10 is an LTE eNB and the SN 30 is an NR gNB as described above with reference to FIG. 1.
  • the terminal 10 may receive data from the MN 20 and the SN 30.
  • the terminal 10 when the terminal 10 detects the MN failure, it can first stop the MCG RB.
  • the condition for determining the MN failure by the terminal 10 may include, for example, at least one of MCG radio link failure, MCG integrity failure, MCG reconfiguration failure, and HO failure.
  • the terminal 10 may release the MCG Scell (release).
  • the terminal 10 may maintain the SCG configuration and maintain the DRB and its configuration related to the SCG.
  • the DRB associated with the SCG may refer to the SCG part of the SCG direct or split DRB or SRB or the MCG DRB or SRB.
  • the gNB corresponding to the terminal 10 and the SN 30 may continue to transmit and receive packets through the SCG DRB.
  • the packet may include RRC signaling and data of the UE for the SCG. Packet transmission and reception through the SN gNB 30 may continue until a new MN cell is found and reconnection is successfully completed and SCG reconfiguration is performed through the new MN cell.
  • the terminal 10 may perform cell selection and perform RACH on the appropriate MN cell 40.
  • the UE 10 may transmit a RRE request message to the newly attached MN cell 40.
  • the RRE request message includes the C-rnti and the ID of the source cell (physical cell ID or global ID, etc.) used in the source cell, and the ID of the gNB cell 30 used as the SN (physical cell). ID to distinguish the cell such as ID or global cell ID) and the ID of the gNB.
  • information currently used when the transmission to the SN for example, information of the SN terminated beaerer (EPS bearer ID, ERAB ID, drb ID and QoS information corresponding to the SCG bearer (UE SN AMBR), security key, NCC, NH, security algorithm, etc. can be delivered together.
  • step S225 it may be determined whether the cell has the terminal context. If the new MN cell 40 has a terminal context, the operation after step S225 shown in FIG. 1 may be performed. If not, the RRE reject message is transmitted, so that the UE switches to idle mode.
  • the new MN cell 40 may transmit an RRE message to the terminal 10 to transmit security and NAS related configuration information. Accordingly, the terminal 10 may perform a corresponding setting and transmit a complete message in step S235. From then on, the UE 10 and the new cell 40 of the MN may establish SRB1,2.
  • the new MN cell 40 uses the cell ID and gNB id of the SN used in the RRE request message, and the gNB 30 that is the SN supporting the corresponding cell using the SCG RB information. ) Can send an SN addition request.
  • the SN 30 may negotiate a radio resource and transmit ack or nack to the new MN cell 40 in step S245.
  • the new MN cell 40 may transmit / receive a PDU session path switch request with the core network AMF or UPF 50.
  • the new MN cell 40 may deliver an RLF indication to the old MN cell 20.
  • the forwarding of the SN addition request and the RLF indication message may be reversed.
  • the past MN cell 20 receiving the RLF indication may transmit an SN release command to the gNB 30 which is the SN in step S255.
  • the SN gNB 30 may stop the DL transmission.
  • the gNB can send a message to the new MN that the SN has been released.
  • the new MN 40 may deliver an RRC connection reconfiguration message to the UE, including the SCG configuration information included in the SN addition request ack message received in step S260, in step S260. have.
  • the RRC connection reconfiguration may include a command to perform SCG configuration information and SCB related DRB release used in the past SN 30.
  • the new MN cell 40 may directly command the terminal 10 SCG configuration based on the newly received SCG configuration. Through this, new SCG configuration information can be applied while releasing past SCG configuration information.
  • the SCG configuration information is information obtained by the new MN 40 as a response to the content requested by the SN addition request based on the SCG / DRB information included in the RRE request. Through this, the SN 30 may know the resource request provided by the previous SN gNB 30 as much as possible, and allocate resources based on the resource request provided by the previous SN gNB 30. have.
  • step S265 the UE reconnects to the cell of the corresponding SN through the RACH.
  • step S270 the UE may resume transmission and reception of the SN and data while transmitting an RRCConnection reconfiguration complete message to the SN cell.
  • the new MN cell 40 may transmit / receive data with the core network AMF or UPF 50.
  • step S300 if the terminal 10 detects an MN failure, it may first stop the MCG RB. The terminal 10 may release the MCG Scell. In addition, the terminal 10 may maintain the SCG setting, and maintain the DRB associated with the SCG. Therefore, the operation of allowing the terminal 10 to connect the MN to the new MN cell 40 while maintaining communication with the SN cell 30 will be described.
  • the terminal 10 may transmit the MCG failure information to the SN gNB 30 through the SCG SRB.
  • the SN gNB 30 may deliver the information received from the terminal back to the MN eNB in a re-establishment required message.
  • the MCG failure indication may include serving cell and neighbor cell measurement results (cell ID, measure value) among measurements performed in the MN cell 20.
  • the information is delivered to the MN cell 20 in a re-establishment required message again in step S310, in which case the terminal identifier such as UE ID or C-rnti and security information used in the MN such as shortMAC-I are transmitted. Can be.
  • the MN cell 20 that has received this message may configure information to be included in a handover request (HO) using the measurement result and the terminal identifier.
  • the MN 20 may transmit a Ho request to a new cell 40 of the MN determined to have the best signal state among the measurement results.
  • the HO request may include a target cell ID to be used in the new MN 40. Or it may include multiple cell ID. If the single target cell ID is included, the MN 40 performs HO with the corresponding cell, and given the multiple cell ID, among the given cells, the new MN 40 determines the target cell.
  • the new MN cell 40 may transmit ack if it is able to grant the HO of the terminal as requested in the Ho request in step S320, and nack if not.
  • the new MN 40 may transmit the response to the previous MN 20 including configuration information about a resource that the new MN 40 may give.
  • the previous MN 20 includes the UE configuration information in the corresponding HO response in the handover command message and includes the SN gNB 30.
  • the SN gNB 30 may deliver an RRCconnectionReconfiguration message to the terminal 10 through an SCG SRB (eg, SCG RRC).
  • SCG SRB eg, SCG RRC
  • the previous MN 20 may give an SN release command.
  • the SN release command may be delivered to the RRCconnectionReconfiguration delivered to the UE 10 immediately after the SN release transmission. In this case, there may be no SN release message.
  • the gNB 30 transmits the HO complete message to the gNB 30 and then the SNB self-SN. Release can be performed.
  • the terminal 10 may apply a configuration for accessing the new MN 40 with the target cell ID included in the RRCconnectionReconfiguration and the access information (rach setting, etc.) of the cell.
  • the RRCconnectionReconfigruation may also include SCG configuration information and SN related DRB configuration information. Through this, the SN-related connection maintained after the old MN failure can be disabled.
  • step S335 the terminal 10 may access the target cell of the new MN 40 through the RACH. Thereafter, in step S340, the terminal 10 may transmit the RRCconnectionReconfigurationcomplete information to the target cell.
  • step S350 when the MN 40 of the target cell performs the SN addition procedure and transmits the corresponding configuration information through the MCG SRB of the new MN 40 (step S355), the terminal 10 accesses the SN cell. Can be done.
  • the UE may transmit a connection complete and configuration complete message to the SN cell 30 (step S360).
  • the terminal 10 may later transmit / receive data with the SN cell 30 again.
  • Example 4 is a view showing Example 3;
  • the UE 10 when the UE 10 detects an MN failure in step S400, it may first stop the MCG RB.
  • the terminal 10 may release the MCG Scell.
  • the terminal 10 may maintain the SCG configuration, and maintain the DRB associated with the SCG. Therefore, the operation of allowing the terminal 10 to connect the MN to the new MN cell 40 while maintaining communication with the SN cell 30 will be described.
  • the difference from Embodiment 2 described above is that the SN addition operation is performed during the HO request-HO response with the new MN cell 40, and the SN is added to the RRCConnectionReconfiguration message transmitted from the SN cell 30 to the UE.
  • the release and new SCG config information is included, so that the terminal 10 simultaneously performs SN release and new SN cell access.
  • step S405 in case of an MN failure according to the third embodiment, when the terminal 10 transmits MCG failure information to the SN gNB 30 through the SCG SRB, the SN cell 30 returns the MN again with a re-establishment required message. May be delivered to cell 20.
  • the MCG failure indication may include a neighbor cell measurement result (cell ID, measure value) of neighbor cells among the measurements performed in the MN cell 20.
  • the information is transmitted back to the MN cell 20 in a re-establishment required message, in which case a terminal identifier such as UE ID or C-rnti may be included.
  • the MN cell 20 receiving the message configures information to be included in the HO request through the measurement result and the terminal identifier, and in step S415 to the new cell 40 of the MN determined to have the best signal state among the measurement results.
  • the HO request may include a target cell ID.
  • the HO request includes PCI and SCG info / SCG DRB information of the cell used in the SN cell 30 (for example, EPS bearer ID, ERAB ID, drb ID, and QoS information corresponding to the bearer (UE SN AMBR)). This can be passed along.
  • the new MN cell 40 receiving the HO request can transmit ack if it can approve the HO of the terminal 10 and nack if it cannot approve.
  • the new MN cell 40 together with the previous MN cell 20 through SN PCI (cell ID) information included in the HO request.
  • Information on the used SN cell 30 can be obtained. Therefore, in step S420, the new MN cell 40 may request SN addition from the SN cell 30 used together with the previous MN cell 20 by transmitting an SN addition request message.
  • step S425 when the SN cell 30 receives the new SCG config, the SN cell 30 may be loaded together with the SN addition ack and transferred to the new MN cell 40.
  • the new MN cell 40 may transmit the HO response to the previous MN cell 20 including the SCG config.
  • the new MN cell 40 may include the configuration information on the resources that the new MN cell 40 can give.
  • the previous MN cell 20 loads the UE configuration information in the corresponding HO response in the HO cmd message and the SN gNB 20 currently communicating with the terminal 10. You can also send an SN release command at the same time.
  • the gNB 30, which is an SN cell may transmit an RRCconnectionReconfiguration to the terminal 10 through the SCG SRB.
  • the terminal 10 applies a setting for accessing the new MN cell 40 with the MN target cell ID included in the RRCconnectionReconfiguration and the access information (rach setting, etc.) of the cell, and applies the newly received SN related SCG config.
  • SN radio information can be set by applying.
  • the terminal 10 may apply the configuration information of the newly received SCG config by removing the SN-related DRB configuration information and SCG configuration information received from the previous SN cell 30.
  • the terminal 10 may perform a RACH to access the target cell of the new MN cell 40.
  • the terminal 10 may transmit the RRCconnectionReconfigurationcomplete information to the target cell of the new MN 40.
  • step S455 the new MN cell 40 may complete the PDC session modification with the core network 50.
  • step S460 the terminal 10 may perform a RACH with the SN cell 30 through the access information in the new SCG config.
  • the RACH with the SN cell 30 may be omitted.
  • the terminal 10 may transmit and receive data with the SN cell 30.
  • an SN RRC message in a multi-RAT dual connectivity including EN-DC, may be delivered using SCG SRB in addition to MCG SRB.
  • an RRC message generated in SN RRC if the message is a request type message requesting a response, the UL path of the SN RRC response message corresponding to the corresponding SN RRC request message may be indicated.
  • a method of transmitting an SN RRC message by a terminal is disclosed.
  • 1 bit for the UL path indication may be included in the SN RRC request message. The bit may indicate whether the corresponding SN RRC response message is transmitted to the SCG SRB or the MCG SRB.
  • Embodiment 4 is a diagram showing Embodiment 4 of the present invention.
  • the UE may receive an SN RRC request message.
  • the UE may determine whether the SN RRC request message is received and the UL path indication bit included in the SN RRC request message, and encapsulates the MN RRC message to send to the MCG SRB or the SCG SRB.
  • the UE may check whether the SN RRC request message is delivered by being encapsulated in the MN. Based on the check result, when the SN RRC request message is delivered by being encapsulated in the MN, in step S520, the UE may check whether the SN RRC response UL path indication bit is indicated as SCG SRB. If the SN RRC response UL path indication bit is indicated by the SCG SRB, in step S523, the UE may transmit the MN RRC response message to the MCG SRB and the SN RRC response message to the SCG SRB.
  • the UE transmits the MN RRC response message to the MCG SRB.
  • the SN RRC response message may be delivered as an encapsulate in the MN RRC response message.
  • the UE when the SN RRC request message is not encapsulated in the MN and delivered in step S510, that is, when directly delivered through the SCG SRB, in step S530, the UE is indicated by the SN RRC response UL path indication bit as SCG SRB You can check whether there is. As a result of the check, when the SN RRC response UL path indication bit is indicated by the SCG SRB, in step S533, the UE may transmit the SN RRC response message to the SCG SRB. On the other hand, when the SN RRC response UL path indication bit is not indicated by the SCG SRB, in step S535, the UE may transmit the MN RRC unidirectional message to the MCG SRB. In addition, the UE may transmit the SN RRC response message by encapsulating the MN RRC unidirectional message.
  • the UE delivers the MN RRC response message to the MCG SRB, and a separate SN RRC response message. Can be created and delivered via SCG SRB. In this case, the MN RRC response message may be omitted.
  • the UE creates an MN RRC response message and the SN RRC response to the MN RRC response message.
  • the message may be included and delivered through the MCG SRB.
  • the MN receiving the message may separate only the SN RRC response message and deliver it to the SN as an inter node message.
  • the UE can directly transmit the SN RRC response message to the SN through the SCG SRB.
  • the MN When the MN receives the RRC message from the SN, the UE sends an encapsulation to its MN RRC message, and when the MN receives the MN RRC response message from the UE, the MN checks whether the SN message is encapsulated therein. Delivers SN messages to the Xn interface, if not present.
  • the UE may make an MN RRC unidirectional message and include the SN RRC response message in the MN RRC unidirectional message to transmit it through the MCG SRB.
  • the MN receiving the message may separate only the SN RRC response message and deliver it to the SN as an inter node message.
  • step S600 while the SN cell 30 transmits an SN RRC request message to the MN cell 20, the SN RRC response UL path indication bit may be indicated and transmitted as an SCG SRB.
  • the MN cell 20 may encapsulate and transmit an SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the SN RRC response UL path indication bit as described above. As a result of the check, when the SN RRC response UL path indication bit is indicated as the SCG SRB, the terminal 10 may determine to transmit the SN RRC response message using the SCG SRB in step S620. Specifically, in step S630, the terminal 10 may transmit an MN RRC response message to the MCG SRB, and in step S640, the terminal 10 may transmit an SN RRC response message to the SCG SRB.
  • FIG. 7 is a sequence diagram showing a case 2.
  • the SN cell 30 may transmit an SN RRC request message to the MN cell 20.
  • the SN RRC response UL path indication bit may be indicated by the MCG SRB and transmitted.
  • the MN cell 20 may encapsulate and transmit an SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the SN RRC response UL path indication bit.
  • the UE 10 may determine to transmit an SN RRC response message using the MCG SRB in step S720.
  • the terminal 10 may transmit an MN RRC response message to the MCG SRB.
  • the MN cell 20 may separate only the SN RRC response message and deliver it to the SN as an inter node message.
  • step S800 the terminal 10 may receive an SN RRC request message from the SN cell 30 through an SCG SRB.
  • the UE 10 may determine to use the SCG SRB in step S810.
  • the terminal 10 may directly transmit an SN RRC response message to the SN through the SCG SRB.
  • step S900 the terminal 10 may receive an SN RRC request message from the SN cell 30 through an SCG SRB.
  • the UE 10 may determine to use the MCG SRB in step S9610.
  • step S920 the terminal 10 may make an MN RRC unidirectional message and include the SN RRC response message in the MN RRC unidirectional message to transmit the MCR SRB.
  • the MN cell 20 receiving the message may separate only the SN RRC response message, and may transmit the message to the SN cell 30 as an inter node message in step S930.
  • the SN Measurement report may be set by measConfig included in the SN RRC connection reconfiguration message.
  • measConfig included in the SN RRC connection reconfiguration message.
  • a measurement report message set in measConfig IE is later used when the corresponding event occurs. There may be a 1 bit indication.
  • the UE can transmit the SN RRCConnectionReconfigurationComplete, which is a response message of the SN RRCConnectionReconfiguration message, by viewing UL path indication information and selecting one from SCG / MCG SRB. have.
  • the terminal reports the MR UL path indication bit in the measConfig IE and may transmit the measurement report (MR) to the corresponding UL path when an event occurs.
  • the MR measurement report
  • the terminal may be directly transmitted to the SCG SRB.
  • the terminal may be transmitted to the MN by being included in an MN RRC response or a one-way message. And MN can deliver only the received MR to the SN.
  • FIG. 10 is a sequence diagram illustrating an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an SCG SRB and an MR is also transmitted to the SCG SRB.
  • the SN cell 30 sets both the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE to indicate the SCG SRB to the MN cell 20 to transmit the SN RRC connection reconfiguration message.
  • the MN cell 20 may encapsulate and transmit an SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine to transmit the SN RRCConnectionReconfigurationComplete message and the MR using the SCG SRB in step S1020.
  • the terminal 10 transmits an MN RRC response message to the MN cell 20 in step S1030.
  • the terminal 10 may transmit an SN RRCConnectionReconfigurationComplete message and an MR using the SCG SRB.
  • FIG. 11 is a sequence diagram illustrating an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an MCG SRB and an MR is also transmitted to an SCG SRB.
  • the SN cell 30 sets the UL path indication bit for the RRCConnectionReconfigurationComplete to the MN cell 20 to indicate the MCG SRB and the MR UL path indication bit of the measConfig IE to indicate the SCG SRB.
  • the MN cell 20 may transmit an encapsulated SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine a path to transmit the RRC message.
  • step S1130 the terminal 10 may transmit an MN RRC response message to the MN cell 20.
  • an SN RRCConnectionReconfigurationComplete message may be encapsulated in the MN RRC response message and transmitted together with the MN cell 20.
  • the MN cell 20 may transmit the SN RRCConnectionReconfigurationComplete message to the SN cell 30.
  • the terminal 10 may transmit the MR to the SN cell 30 using the SCG SRB.
  • 12 is a sequence diagram illustrating an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an SCG SRB and an MR to an MCG SRB.
  • the SN cell 30 is configured to indicate to the MN cell 20 the UL path indication bit for the RRCConnectionReconfigurationComplete indicates the SCG SRB, and the MR UL path indication bit of the measConfig IE indicates the MCG SRB.
  • the MN cell 20 may encapsulate and transmit an SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine a path to transmit the RRC message.
  • the terminal 10 may transmit an MN RRC response message to the MN cell 20.
  • the terminal 10 may transmit the SN RRCConnectionReconfigurationComplete message to the SN cell 30 using an SCG SRB.
  • the terminal 10 may transmit an MN RRC response message including the MR to the MN cell 20 using the MCG SRB.
  • the MN cell 20 may separate the MR and transmit the same to the SN cell 30.
  • FIG. 13 is a sequence diagram illustrating an embodiment in which an SN RRCConnectionReconfigurationComplete is transmitted to an MCG SRB and an MR is also transmitted to the MCG SRB.
  • the SN cell 30 sets both the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE to indicate the MCG SRB to the MN cell 20 to transmit the SN RRC connection reconfiguration message.
  • the MN cell 20 may transmit an SN RRC request message to the terminal 10 by encapsulating the MN RRC request message.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine to transmit the SN RRCConnectionReconfigurationComplete message and the MR using the MCG SRB in step S1320.
  • the terminal 10 may transmit an MN RRC response message to the MN cell 20 in step S1330.
  • an SN RRCConnectionReconfigurationComplete message may be encapsulated in the MN RRC response message and transmitted together with the MN cell 20.
  • the MN cell 20 may transmit the SN RRCConnectionReconfigurationComplete message to the SN cell 30.
  • the terminal 10 may transmit an MN RRC response message including the MR to the MN cell 20 using the MCG SRB.
  • the MN cell 20 may separate the MR and transmit the MR to the SN cell 30.
  • FIG. 14 is included in each RRCconnectionReconfiguration message of a plurality of separate measConfig and transmitted.
  • FIG. 11 is a sequence diagram illustrating a case where MR UL paths are set differently. At this time, the MR set in each measConfig can be independently transmitted to each set UL path.
  • the SN cell 30 sets both the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the first measConfig IE to indicate the SCG SRB to the MN cell 20 so as to indicate the SN RRC connection reconfiguration message. Can be transmitted.
  • the MN cell 20 may transmit an SN RRC reconfiguration message to the terminal 10 by encapsulating the MN RRC request message.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine to transmit an SN RRCConnectionReconfigurationComplete message and an MR using the SCG SRB in step S1410.
  • the terminal 10 transmits an MN RRC response message to the MN cell 20 in step S1415.
  • the terminal 10 transmits an SN RRCConnectionReconfigurationComplete message and a first MR using the SCG SRB. Each can be transmitted.
  • the SN cell 30 sets the UL path indication bit for the RRCConnectionReconfigurationComplete to the MN cell 20 to indicate the SCG SRB and the MR UL path indication bit of the measConfig IE to indicate the MCG SRB. You can send a connection reconfiguration message.
  • the MN cell 20 may encapsulate and transmit an SN RRC request message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bit of the measConfig IE.
  • the terminal 10 may determine a path to transmit the RRC message.
  • the terminal 10 may transmit an MN RRC response message to the MN cell 20.
  • the terminal 10 may transmit the SN RRCConnectionReconfigurationComplete message to the SN cell 30 using an SCG SRB.
  • the terminal 10 may transmit an MN RRC response message including the second MR to the MN cell 20 using the MCG SRB.
  • the MN cell 20 may separate and transmit the second MR to the SN cell 30.
  • the UL path of the MR MR for SN may be set per measConfig IE included in the RRCConnectionReconfiguration, but may also be set for each measId in measConfig.
  • 1 bit for UL path selection for SN RRCConnectionReconfigurationComplete and MR UL path indication bits for each measID of measConfig IE may be separately included and transferred in the SN RRCConnectionReconfiguration message.
  • the UE reports the SN RRCConnectionReconfiguration message, reports the MR UL path indication for each measID included in the SN RRCConnectionReconfiguration message, and transmits the corresponding MR to the configured UL path when an event for each measID occurs.
  • step S1500 the SN cell 30 sets the UL path indication bit for the RRCConnectionReconfigurationComplete to the MN cell 20 to indicate the SCG SRB, and in the measConfig IE, the first measID sets the MR UL path indication bit to the SCG SRB, The second measID may set the MR UL path indication bit to the MCG SRB to transmit an SN RRC connection reconfiguration message.
  • the MN cell 20 may encapsulate and transmit an SN RRC reconfiguration message to the MN RRC request message to the terminal 10.
  • the terminal 10 may check the UL path indication bit for the RRCConnectionReconfigurationComplete and the MR UL path indication bits for the first and second measIDs of the measConfig IE. Based on the confirmation result, in step S1520, the terminal 10 may determine to transmit an SN RRCConnectionReconfigurationComplete message and an MR for the first measID using the SCG SRB. The terminal 10 may determine to transmit the MR for the second measID using the MCG SRB.
  • the terminal 10 transmits an MN RRC response message to the MN cell 20 in step S1530.
  • the terminal 10 transmits an SN RRCConnectionReconfigurationComplete message and a first MR using an SCG SRB. Each can be transmitted.
  • the terminal 10 may transmit an MN RRC response message including the second MR to the MN cell 20 using the MCG SRB.
  • the MN cell 20 may separate the second MR and transmit it to the SN cell 30.
  • the SN cell may always set the MR UL path to MCG SRB.
  • MR UL if it is determined that the link quality is very low based on the link status of the SN cell (the average level of RSRP feedback from the terminal or directly measured by the SRS, or the average number of RLC retransmissions or HARQ retransmissions).
  • the path may be set to MCG SRB.
  • the SN RRC request message may be any type of message in which the UE sends a one-time response corresponding to the UE in SN RRC, and the SN RRC response message refers to a response message transmitted by the UE.
  • the following is an example of a request-response message.
  • the SN RRC may be a message sent by the SN RRC one time to the DL or a message sent by the terminal to the UL one time.
  • the one-time message sent to the DL can be directly sent by the SN RRC by selecting the MCG SRB or the SCG SRB, and each UL one-time SN RRC message has a predetermined SRB for the default SN so that the one-time message can be transmitted to the default SRB.
  • the default SRB may be selected from MCG SRB and SCG SRB and transmitted to the UE as system information.
  • an operation required for the SCG change indication or a use case requiring the operation may be displayed and transmitted to the SN or the MN.
  • NR PDCP can be used in the LTE user plane, in relation to PDCP version change, PDCP anchor point change, security key refresh, etc. of bearers used in SCG, existing synchronous reconfiguration (for example, when the UE is MAC, In the case where RLC reset and PDCP re-establishment for SCG and RACH to target SCG) are collectively performed, each layer 2 stack can be partially reset.
  • the partial synchronous reconfiguration operation required for the SCG change IE may be displayed or the use case may be displayed so that the SN may prepare for the operation and reduce latency.
  • 16A to 16C illustrate an embodiment of an MN initiated SCG change.
  • the MN 20 may deliver a SCG change indication in an SN modification request message, while delivering the necessary operation of synchronous reconfiguration to the SN 30.
  • the necessary operation may be as follows. security key refresh, reconfiguration, RACH, RACH and MAC reset, RACH and MAC reset and RLC reset, RACH and MAC reset and RLC reset and PDCP re-establishment.
  • the SN 30 receives the message, the SN 30 performs an operation for the necessary operation. For example, if the general reconfiguration is not a reset of the sub-layer of the L2 stack, the reconfiguration is performed, and if the RACH is displayed in the message, the random access preamble transmission of the corresponding UE is monitored. Can be.
  • the SN 30 may reset the MAC belonging to the corresponding UE.
  • the SN 30 may wait for the RACH operation of the terminal 10.
  • the SN 30 may transmit the SN modification ack message to the MN 20, including the SCG setting for setting the RACH and the MAC reset.
  • the MN 20 may transmit the received setting to the terminal 10. Accordingly, the terminal 10 may reset the MAC in step S1615.
  • the UE 10 may transmit an RACH to the SN 30.
  • the SN 30 may reset all RLC entities belonging to the corresponding UE 10 and may also reset the MAC. .
  • the SN 30 may wait for the RA of the terminal 10.
  • the SN 30 may transmit an SN modification ack message to the MN 20, including an SCG setting for setting RACH, MAC, and RLC reset.
  • the MN 20 may transmit the received setting to the terminal 10. Accordingly, the terminal 10 may reset the MAC and RLC in step S1635.
  • the terminal 10 may transmit a RACH to the SN 30.
  • the SN 30 when the necessary operation of synchronous reconfiguration is RACH and MAC / RLC reset and PDCP re-establishment, the SN 30 re-establishes the PDCP of the terminal 10 and then performs RLC and MAC. You can reset it.
  • the SN 30 may wait for the RA of the terminal 10. Specifically, as shown in FIG. 16C, in step S1645, the SN 30 transmits an SN modification ack message to the MN 20, including an SCG setting for setting RACH and MAC / RLC reset and PDCP re-establishment. Can transmit In operation S1650, the MN 20 may transmit the received setting to the terminal 10. Accordingly, the terminal 10 may reset the MAC and RLC in step S1655. The terminal 10 may perform PDCP re-establishment. In addition, in step S1660, the terminal 10 may transmit a RACH to the SN (30).
  • the SN 30 confirms the displayed operation and confirms the required operation. And it can create a reconfiguration message required by the terminal.
  • the message is delivered to the MN 20 as a container, and when the MN 20 reconfigures the terminal 10, the message may be delivered by the SN 30 to allow the terminal 10 to perform a necessary operation.
  • the terminal 10 shown in FIG. 16A is MAC reset and RACH
  • the terminal 10 shown in FIG. 16B is MAC / RLC reset and RACH
  • the terminal 10 shown in FIG. 16C is MAC / RLC.
  • Refiguration is reconfiguration without MAC reset
  • RACH is RACH
  • RACH and MAC reset is reconfiguration with MAC reset
  • RACH and MAC / RLC reset is traditional handover but without PDCP re-establishment
  • RACH and MAC / RLC / PDCP reset / re -establish can be traditional HO
  • FIGS. 17A to 17C illustrate an embodiment of SN initiated SCG change.
  • the SN 30 may indicate to the MN 20 an operation required for the SCG change indication IE in the SN modification required message.
  • the MN 20 receiving the message may generate an SN modification request and deliver it back to the SN 30, including the necessary operation received from the SN 30 in the SCG change indication IE of the SN modification request. have.
  • the SN 30 recognizes the occurrence of one of the above-described embodiments, it transmits the SCG change indication to the MN 20 in the SN modification required message, and delivers the necessary operation of the synchronous reconfiguration to the MN 20.
  • the necessary operation may be as follows. reconfiguration, RACH, RACH and MAC reset, RACH and MAC reset and RLC reset, RACH and MAC reset and RLC reset and PDCP re-establishment.
  • the MN 20 may generate an SN modification request.
  • the MN 20 may forward back to the SN 30, including the necessary actions received from the SN 30 in the SCG change indication IE of the SN modification request.
  • the SN 30 When the SN 30 receives the SN modification request message, the SN 30 performs an operation performed for the necessary operation. For example, if the general reconfiguration is not a reset of the sub-layer of the L2 stack, the reconfiguration is performed, and if the RACH is displayed in the message, the random access preamble transmission of the corresponding UE can be monitored without performing any other operation. .
  • the SN 30 may reset the MAC belonging to the corresponding terminal.
  • the SN 30 may wait for the RACH operation of the terminal 10.
  • the SN 30 may transmit the SN modification ack message to the MN 20, including the SCG setting for setting the RACH and the MAC reset.
  • the MN 20 may transmit the received setting to the terminal 10. Accordingly, the terminal 10 may reset the MAC in step S1725.
  • the terminal 10 may transmit a RACH to the SN 30.
  • the SN 30 may reset all RLC entities belonging to the corresponding UE 10 and may also reset the MAC. .
  • the SN 30 may wait for the RA of the terminal 10.
  • the SN 30 may transmit an SN modification ack message to the MN 20, including an SCG setting for setting RACH, MAC, and RLC reset.
  • the MN 20 may transmit the received setting to the terminal 10. Accordingly, the terminal 10 may reset the MAC and RLC in step S1745.
  • the terminal 10 may transmit a RACH to the SN 30.
  • the SN 30 when the necessary operation of synchronous reconfiguration is RACH and MAC / RLC reset and PDCP re-establishment, the SN 30 re-establishes the PDCP of the terminal 10 and then performs RLC and MAC. You can reset it.
  • the SN 30 may wait for the RA of the terminal 10.
  • the SN 30 transmits an SN modification ack message to the MN 20, including an SCG setting for setting RACH and MAC / RLC reset and PDCP re-establishment.
  • the MN 20 may transmit the received setting to the terminal 10.
  • the terminal 10 may reset the MAC and RLC in step S1765.
  • the terminal 10 may perform PDCP re-establishment.
  • the terminal 10 may transmit a RACH to the SN (30).
  • the MN 20 receiving the SN modification required message forwards the SN modification request to the SN 30 that has sent the SN modification required, so that the SN 30 performs the operation. Can be ordered.
  • reconfiguration is reconfiguration without MAC reset
  • RACH is RACH
  • RACH and MAC reset is reconfiguration with MAC reset
  • RACH and MAC / RLC reset is traditional handover but without PDCP re-establishment
  • RACH and MAC / RLC / PDCP reset / re -establish can be traditional HO
  • FIG. 18 is a diagram illustrating a structure of a terminal according to an embodiment of the present invention.
  • the terminal may include a transceiver 1810, a controller 1820, and a storage 1830.
  • the controller may be defined as a circuit or application specific integrated circuit or at least one processor.
  • the transceiver 1810 may exchange a signal with another network entity.
  • the transceiver 1810 may receive system information from, for example, a base station, and may receive a synchronization signal or a reference signal.
  • the controller 1820 may control the overall operation of the terminal according to the embodiment proposed by the present invention.
  • the controller 1820 if the connection with the first master node (MN) of the terminal is released, RRC connection reestablishment request (connection) including the identifier information for the secondary node (secondary node, SN) (connection) Send a re-establishment request message to a second master node (MN), and when the second MN includes context information for the terminal, receives an RRC connection reestablishment message from the second MN.
  • the transceiver 1810 may be controlled to control the transmission / reception unit 1810.
  • an SN addition request message may be transmitted to the SN by the second MN based on the identifier information of the SN.
  • the RRC connection reestablishment request message may further include bearer information for the SN.
  • the SN may be characterized by including an RRC layer (radio resource control layer).
  • RRC layer radio resource control layer
  • the storage unit 1830 may store at least one of information transmitted and received through the transceiver 1810 and information generated through the controller 1820.
  • the base station may be an eNB of LTE system (including MeNB, SeNB) or a gNB of NR system.
  • the base station may include a transceiver 1910, a controller 1920, and a storage 1930.
  • the controller 1920 may be defined as a circuit or application specific integrated circuit or at least one processor.
  • the transceiver 1910 may exchange a signal with another network entity.
  • the transceiver 1910 may transmit system information to the terminal, for example, and may transmit a synchronization signal or a reference signal.
  • the controller 1920 may control the overall operation of the base station according to the embodiment proposed by the present invention. For example, when the base station is the second MN, the controller 1920 includes identifier information on the secondary node (SN) from the terminal disconnected from the first master node (MN). When receiving the RRC connection re-establishment request message, and includes the context information for the terminal, the transceiver 1910 can be controlled to transmit the RRC connection reestablishment message to the terminal. have.
  • the controller 1920 may control the transceiver 1910 to transmit an SN addition request message to the SN based on the identifier information of the SN.
  • the RRC connection reestablishment request message may further include bearer information for the SN.
  • the SN may include an RRC layer (radio resource control layer).
  • RRC layer radio resource control layer
  • the storage unit 1930 may store at least one of information transmitted and received through the transceiver 1910 and information generated through the controller 1920.

Landscapes

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

Abstract

L'invention concerne une technique de communication destinée à faire converger une technologie IdO (Internet des objets) et un système de communication 5G pour la prise en charge d'un débit de transfert de données supérieur à celui d'un système 4G, ainsi qu'un système associé. La présente invention peut s'appliquer à des services intelligents (par ex. maisons intelligentes, bâtiments intelligents, villes intelligentes, voitures intelligentes ou voitures connectées, soins de santé, enseignement numérique, commerce de détail, et services liés à la sécurité et la sûreté) sur la base de la technologie de communication 5G et de la technologie associée à l'IdO. L'invention concerne un procédé et un appareil permettant d'améliorer les performances liées à la mobilité lorsqu'une connectivité double est effectuée à l'aide d'une commande RRC double.
PCT/KR2018/006809 2017-06-15 2018-06-15 Procédé et appareil de traitement de la mobilité dans un système rrc double WO2018231021A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/622,730 US11432362B2 (en) 2017-06-15 2018-06-15 Method and apparatus for processing mobility in dual RRC system
CN201880039399.0A CN110741721A (zh) 2017-06-15 2018-06-15 处理双rrc系统中的移动性的方法和装置
EP18818715.7A EP3624547A4 (fr) 2017-06-15 2018-06-15 Procédé et appareil de traitement de la mobilité dans un système rrc double

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2017-0076073 2017-06-15
KR20170076073 2017-06-15
KR1020170125584A KR102388500B1 (ko) 2017-06-15 2017-09-27 듀얼 rrc 시스템에서 이동성을 처리하는 방법 및 장치
KR10-2017-0125584 2017-09-27

Publications (1)

Publication Number Publication Date
WO2018231021A1 true WO2018231021A1 (fr) 2018-12-20

Family

ID=64659839

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/006809 WO2018231021A1 (fr) 2017-06-15 2018-06-15 Procédé et appareil de traitement de la mobilité dans un système rrc double

Country Status (1)

Country Link
WO (1) WO2018231021A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836318A (zh) * 2019-08-21 2020-10-27 维沃移动通信有限公司 链路失败处理的方法和通信设备
CN112703770A (zh) * 2019-01-11 2021-04-23 Oppo广东移动通信有限公司 一种rrc连接重建方法及装置、网络设备
KR20210103565A (ko) * 2019-01-18 2021-08-23 비보 모바일 커뮤니케이션 컴퍼니 리미티드 정보 지시 방법, 정보 획득 방법, 단말 및 네트워크 노드
EP4096341A4 (fr) * 2020-02-21 2023-08-02 Huawei Technologies Co., Ltd. Procédé et appareil de communication
EP4108043A4 (fr) * 2020-07-22 2023-08-23 Samsung Electronics Co., Ltd. Procédé et appareil de gestion d'une suspension et d'une reprise de support de protocole d'un groupe de cellules secondaires (scg) dans une technologie de connectivité double supportée par un système de communication mobile de nouvelle génération

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140293769A1 (en) * 2011-12-20 2014-10-02 Huawei Technologies Co., Ltd. Method, apparatus and system for processing device faults

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140293769A1 (en) * 2011-12-20 2014-10-02 Huawei Technologies Co., Ltd. Method, apparatus and system for processing device faults

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: " INACTIVE to CONNECTED state transitions", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1704116, 6 May 2017 (2017-05-06), Hangzhou, China, XP051264277 *
INTEL CORPORATION: "NR RRC state transitions to get CONNECTED", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1704774, 6 May 2017 (2017-05-06), Hangzhou, China, XP051264542 *
INTEL CORPORATION: "RRC Connection Reconfiguration for EN-DC operation", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1704815, 6 May 2017 (2017-05-06), Hangzhou, China, XP051264573 *
INTEL CORPORATION: "Security optimizations when resuming or re-establishing an RRC connection", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1704773, 6 May 2017 (2017-05-06), Hangzhou, China, XP051264541 *
See also references of EP3624547A4 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112703770A (zh) * 2019-01-11 2021-04-23 Oppo广东移动通信有限公司 一种rrc连接重建方法及装置、网络设备
CN112703770B (zh) * 2019-01-11 2023-11-10 Oppo广东移动通信有限公司 一种rrc连接重建方法及装置、网络设备
KR20210103565A (ko) * 2019-01-18 2021-08-23 비보 모바일 커뮤니케이션 컴퍼니 리미티드 정보 지시 방법, 정보 획득 방법, 단말 및 네트워크 노드
KR102613334B1 (ko) 2019-01-18 2023-12-12 비보 모바일 커뮤니케이션 컴퍼니 리미티드 정보 지시 방법, 정보 획득 방법, 단말 및 네트워크 노드
CN111836318A (zh) * 2019-08-21 2020-10-27 维沃移动通信有限公司 链路失败处理的方法和通信设备
CN111836318B (zh) * 2019-08-21 2021-12-03 维沃移动通信有限公司 链路失败处理的方法和通信设备
EP4096341A4 (fr) * 2020-02-21 2023-08-02 Huawei Technologies Co., Ltd. Procédé et appareil de communication
EP4108043A4 (fr) * 2020-07-22 2023-08-23 Samsung Electronics Co., Ltd. Procédé et appareil de gestion d'une suspension et d'une reprise de support de protocole d'un groupe de cellules secondaires (scg) dans une technologie de connectivité double supportée par un système de communication mobile de nouvelle génération
US11856630B2 (en) 2020-07-22 2023-12-26 Samsung Electronics Co., Ltd. Method and apparatus for handling a protocol supporting suspension and resumption of secondary cell group (SCG) in dual connectivity technology supported by next-generation mobile communication system

Similar Documents

Publication Publication Date Title
WO2018231021A1 (fr) Procédé et appareil de traitement de la mobilité dans un système rrc double
EP3624547A1 (fr) Procédé et appareil de traitement de la mobilité dans un système rrc double
WO2015030483A1 (fr) Procédé et système de procédure d'accès aléatoire et de défaillance de liaison radio dans une agrégation de porteuses inter-enb
WO2021029649A1 (fr) Procédé et appareil pour la gestion d'un transfert conditionnel dans un réseau de communication sans fil
WO2018164498A1 (fr) Procédé pour maintenir un équipement d'utilisateur en mode connexion initiée par mobile uniquement dans un mode connecté
WO2018203716A1 (fr) Procédé pour opération d'événement de rapport de mesure et signalisation de réseau dans un transfert autonome d'ue
WO2016133344A1 (fr) Procédé pour déclencher la transmission d'une indication de relais d'un équipement utilisateur (ue) à un réseau
US20210051746A1 (en) Multi-Connectivity Communication Method and Device
WO2014058139A1 (fr) Procédé et appareil pour la gestion de la mobilité
WO2019160310A1 (fr) Procédé et appareil de modification d'une règle de mappage
EP4233418A1 (fr) Procédé et système de gestion de notification et de configuration de services pour un service mbs dans un réseau de communication 5g
WO2021167290A1 (fr) Procedé et appareil pour améliorer la précision de la sélection de réseau dans un système de communication sans fil
WO2020036429A1 (fr) Procédé et appareil de gestion d'une connexion de session de pdu
EP3769561A1 (fr) Procédé et dispositif d'authentification d'ue
WO2011116547A1 (fr) Procédé et dispositif de configuration de ressources au cours d'un transfert intercellulaire
EP3378249A1 (fr) Procédé et appareil permettant de réduire le surdébit de signalisation et la batterie du terminal
AU2020264654A1 (en) Communication method and communications apparatus
WO2016122131A1 (fr) Procédé et appareil permettant de construire un réseau mobile dans un système de communication mobile
JP7013474B2 (ja) コンテキスト解放方法、機器及びシステム
WO2020197277A1 (fr) Procédé et dispositif de traitement de message srb de liaison descendante dans mcg rlf
KR20230107216A (ko) 뉴 라디오에서 통합 액세스 백홀 네트워크를 향상시키기 위한 방법 및 디바이스
WO2021242076A1 (fr) Procédé et dispositif de transmission et de réception de données dans un système de communication sans fil
WO2014012454A1 (fr) Procédé de commutation de porteuse, ainsi que système et dispositif correspondants
WO2021153982A1 (fr) Procédé et appareil pour aviser de changements d'utilisation d'amélioration de couverture dans un réseau
WO2019070106A1 (fr) Procédé et appareil permettant de déclarer une rlf

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: 18818715

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018818715

Country of ref document: EP

Effective date: 20191213