WO2020259435A1 - 信息管理方法、辅节点变更方法、节点及存储介质 - Google Patents

信息管理方法、辅节点变更方法、节点及存储介质 Download PDF

Info

Publication number
WO2020259435A1
WO2020259435A1 PCT/CN2020/097420 CN2020097420W WO2020259435A1 WO 2020259435 A1 WO2020259435 A1 WO 2020259435A1 CN 2020097420 W CN2020097420 W CN 2020097420W WO 2020259435 A1 WO2020259435 A1 WO 2020259435A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
user equipment
historical information
secondary node
information
Prior art date
Application number
PCT/CN2020/097420
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Priority to JP2021577159A priority Critical patent/JP7308305B2/ja
Priority to KR1020217042353A priority patent/KR20220011728A/ko
Priority to EP20830934.4A priority patent/EP3986030A4/en
Priority to US17/622,510 priority patent/US20220248294A1/en
Publication of WO2020259435A1 publication Critical patent/WO2020259435A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H04W36/008375—Determination of triggering parameters for hand-off based on historical data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • This application relates to an information management method, a secondary node change method, a node, and a storage medium.
  • 5G hotspots are deployed on the basis of the Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • LTE network the rapid deployment of 5G systems can be achieved.
  • the dual-connection technology realizes the collaborative work between LTE and 5G systems, which helps to increase the user rate.
  • DC Multi-Radio Dual Connectivity
  • 4G fourth generation mobile communication technology
  • DC also includes dual connectivity in New Radio (NR).
  • MR-DC stands for multi-wireless dual connection. This article specifically refers to 4G and 5G dual connection technologies.
  • the MR-DC protocol defines two architectures.
  • MR-DC with EPC that is, E-UTRA-NR Dual Connectivity (EN-DC) of E-UTRA-NR Dual Connectivity (EN-DC) of the Evolved Universal Mobile Communication System Terrestrial Radio Access and the New Radio, with eNB as the primary node and gNB as the secondary node.
  • E-UTRA-NR Dual Connectivity EN-DC
  • E-UTRA-NR Dual Connectivity EN-DC
  • gNB Evolved Universal Mobile Communication System Terrestrial Radio Access and the New Radio
  • Non-standalone (Non-Standalone, NSA) terminals provide services.
  • MR-DC with 5GC includes next-generation wireless access and E-UTRA-NR dual connectivity (NG-RAN E-UTRA-NR Dual Connectivity, NGEN-DC) and NR-E-UTRA dual connectivity (NR-E- UTRA Dual Connectivity (NE-DC), the main difference is to connect to the fifth generation core network (5G Core, 5GC), which network element serves as the primary node and which network element serves as the secondary node.
  • 5G Core 5G Core
  • the SN Change (SN Change) initiated by the secondary node (Secondary Node, SN) in the dual connectivity scenario is performed by notifying the master node (Master Node, MN) to perform the SN Add (SN Add) operation to the target SN.
  • the SN decision to initiate SN Change is only a reference to related factors such as signal quality, and it is necessary to make improvements.
  • At least one embodiment of the present application provides an information management method, a secondary node change method, a node, and a storage medium.
  • At least one embodiment of the present application provides an information management method, including:
  • the secondary node After the user equipment adds the secondary node, the secondary node records the historical information of the user equipment.
  • At least one embodiment of the present application provides an information management method, including:
  • the master node sends the historical information of the user equipment to the slave node in the process of changing or modifying the slave node.
  • At least one embodiment of the present application provides a method for changing a secondary node, including:
  • the target secondary node is selected according to the historical information of the user equipment.
  • At least one embodiment of the present application provides a node, including a memory and a processor, the memory stores a program, and the program, when read and executed by the processor, implements the information management method described in any embodiment.
  • At least one embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any The information management method described in an embodiment.
  • At least one embodiment of the present application provides a node, including a memory and a processor, the memory stores a program, and when the program is read and executed by the processor, implements the secondary node changing method described in any embodiment .
  • At least one embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any A method for changing a secondary node described in an embodiment.
  • Fig. 1 is a flowchart (SN side) of an information management method provided by an embodiment of the present application
  • FIG. 2 is a flowchart (MN side) of an information management method provided by an embodiment of the present application
  • FIG. 3 is a flowchart of a method for changing a secondary node provided by an embodiment of the present application
  • Figure 4 is a block diagram of a node provided by an embodiment of the present application.
  • Figure 5a is a schematic diagram of a control plane architecture in an EN-DC scenario provided by an embodiment of the present application
  • Figure 5b is a flow chart of SN triggering SN Change in an EN-DC scenario provided by an embodiment of the present application
  • FIG. 6 is a flow chart of SN triggering SN Change in a 5GC-connected MR-DC scenario provided by an embodiment of the present application
  • Fig. 7 is a flowchart of the SN carried in the MN handover in the EN-DC scenario provided by an embodiment of the present application;
  • FIG. 8 is a flowchart of SN carried in MN handover and SN change in an EN-DC scenario provided by an embodiment of the present application
  • FIG. 9 is a block diagram of a node provided by an embodiment of the present application.
  • FIG. 10 is a block diagram of a computer-readable storage medium provided by an embodiment of the present application.
  • FIG. 11 is a block diagram of a node provided by another embodiment of the present application.
  • FIG. 12 is a block diagram of a computer-readable storage medium according to another embodiment of the present application.
  • an information management method that can be used in a dual connectivity system is provided to record and transmit the historical information of the user equipment in the SN side primary and secondary cell (SpCell of a secondary cell group, PScell) to assist the SN Change decision to select a better target SN and enhance the robustness of the system.
  • An embodiment of the present application provides a method for managing historical information of user equipment in a dual-connection system, which includes storing historical information carried from MN by SN, recording historical information under current SN, bringing historical information of SN to MN, The SN refers to the historical information and selects the target SN to trigger the SN Change process.
  • an embodiment of the present application provides an information management method, including:
  • Step 101 After a user equipment (User Equipment, UE) adds an SN, the SN records historical information of the user equipment.
  • UE User Equipment
  • At least one embodiment of the present application provides an information management method, which includes: after a user equipment adds a secondary node, the secondary node records current historical information of the user equipment.
  • the solution provided in this embodiment records the historical information of the user equipment to facilitate subsequent use of the historical information.
  • the SN After the UE successfully adds the SN, the SN records the historical information in the PScell, including the historical information after the PScell change caused by the PScellChange in this process, until the SN is changed or deleted.
  • the SN includes, but is not limited to, Secondary gNodeB (SgNB) and Secondary eNodeB (SeNB).
  • SgNB Secondary gNodeB
  • SeNB Secondary eNodeB
  • the historical information includes content consistent with the current protocol definition, including historical visited cell information, which includes cell system, cell identifier, cell type, current cell residence time, and other information.
  • the current historical information of the user equipment refers to the information of the cell where the user equipment resides under the current SN.
  • the method further includes: when the SN receives historical information of the user equipment under another SN sent by the MN, saving the historical information of the user equipment under another SN.
  • the SN is a target SN, and the MN initiates an SN addition (Add) process. At this time, the MN carries historical information to the target SN through an SN Addition Request (SN Addition Request) message.
  • the method further includes: in the process of changing or modifying the SN, the SN sends historical information of the user equipment to the MN.
  • the source SN carries historical information to the MN.
  • the SN change required (SN change Required) message can carry historical information.
  • the SN Modification Request Acknowledge can be used to carry historical information.
  • the historical information sent by the SN to the MN includes the historical information of the user equipment recorded by the SN itself (including the historical information of the user equipment under the secondary node and the historical information of the user equipment Adding the historical information before the secondary node), or including the historical information of the user equipment under the SN recorded by the SN itself and the historical information of the user equipment under other SNs received by the SN.
  • the historical information transmitted by the source SN includes the historical information carried from other MNs to the source SN and the historical information newly recorded by the source SN itself, which is the accumulation of historical information.
  • the recorded history information exceeds a limited number, part of the records are deleted, for example, the oldest records are eliminated sequentially. Among them, the limited number can be set as needed.
  • an embodiment of the present application provides an information management method, including:
  • step 201 the MN sends historical information of the user equipment to the SN during the SN change or modification process.
  • the history information of the user equipment may be carried in the SNADD request.
  • the MN obtains historical information of the user equipment from a source SN.
  • the MN sending the history information of the user equipment to the SN during the SN change or modification process includes:
  • the MN sends the historical information of the user equipment to the target SN during the SN change or modification process.
  • sending historical information of the user equipment to the secondary node includes:
  • the MN is a source MN, and the source MN sends the history information of the user equipment to the target MN during the SN change or modification process, and the target MN sends the history information of the user equipment to the target SN.
  • an embodiment of the present application provides a method for changing a secondary node, including:
  • step 301 when the SN initiates an SN change, the target SN is selected according to the historical information of the user equipment.
  • the SN When the SN decides to initiate SN Change, it needs to select the target SN. At this time, in addition to referring to the signal quality, historical information can be referred to to select a better SN for change. According to the system implementation, a set of selection algorithms can be provided. For example, in the case of the same signal quality, refer to the residence time of the cell, select the SN with a longer residence time as the target SN, etc.
  • the selection algorithm can be set according to needs. Not limited.
  • the method further includes: the SN obtains historical information of the user equipment from the MN.
  • the historical information of the user equipment in the SN is recorded and transmitted, and the historical information is referred to when the SN initiates the SN Change decision, so as to select the target side of the SN Change and enhance the robustness of the system.
  • An embodiment of the present application provides a node 400, as shown in FIG. 4, which is a schematic diagram and does not limit the implementation of the node.
  • the node 400 includes a recording module 401.
  • the recording module 401 is set to record the historical information of the current SN after the SN is successfully added, including the entire historical track of PScell changes in the SN.
  • the node 400 further includes:
  • the receiving module 402 is configured to receive historical information of the user equipment under the SN sent by the MN. Among them, the historical information can be carried in the SN Add request message.
  • the storage module 403 is configured to store the historical information of the user equipment under the SN.
  • the node 400 further includes a sending module 404, which is configured to send historical information of the UE to the MN when the SN initiates an SN Change; for example, the SN Change request message carries historical information.
  • a sending module 404 which is configured to send historical information of the UE to the MN when the SN initiates an SN Change; for example, the SN Change request message carries historical information.
  • the node 400 further includes a decision-making module 405, which is configured to make a decision based on the historical information of the UE to determine the target SN when the SN Change is initiated.
  • a preset algorithm can be used to select the optimal target SN.
  • An embodiment of the present application provides a method for changing a secondary node.
  • This embodiment relates to an EN-DC scenario.
  • the eNB ie, the MeNB in FIG. 5a
  • the MN only has an S1-C signaling connection with an evolved packet core (Evolved Packet Core, EPC), and the SgNB (the secondary node SN in this embodiment) has no signaling connection with the EPC.
  • EPC evolved Packet Core
  • the eNB and gNB exchange EN-DC related signaling through X2-C.
  • Radio Resource Control Radio Resource Control
  • NAS Non-Access-Stratum
  • step 501 the UE succeeds in accessing the MN, and the MN sends an SgNB Addition Request (SgNB Addition Request) message to the SN (the source SN in this embodiment) to request the addition of the SN, because it is the first time to add the SN and does not carry the history information of the SN.
  • SgNB Addition Request SgNB Addition Request
  • step 502 the source SN replies to the MN with an SgNB Addition Request Acknowledge (SgNB Addition Request Acknowledge) message to confirm the addition of the SN.
  • SgNB Addition Request Acknowledge SgNB Addition Request Acknowledge
  • step 503 the MN side reconfigures the UE successfully, and the MN sends SgNB Reconfiguration Complete to the source SN to notify the source SN that the reconfiguration is successful, and the source SN can start to record historical information in the current PScell.
  • step 504 the source SN initiates the SN Change process, and there is no historical information for reference at this time (at this time, only the historical information recorded by the source SN itself, no historical information from other SNs).
  • the source SN sends an SgNB Change Required (SgNB Change Required) message to the MN to request SN Change, which carries historical information of the PScell in the source SN.
  • SgNB Change Required SgNB Change Required
  • Step 505 The MN sends an SgNB Addition Request (SgNB Addition Request) message to the target SN to request the addition of an SN, which carries historical information of the source SN.
  • SgNB Addition Request SgNB Addition Request
  • Step 506 The target SN replies to the MN with an SgNB Addition Request Acknowledge (SgNB Addition Request Acknowledge) message to confirm the addition of the SN.
  • SgNB Addition Request Acknowledge SgNB Addition Request Acknowledge
  • Step 507 The MN replies to the source SN with an SgNB Change Confirm (SgNB Change Confirm) message to confirm the SN Change.
  • SgNB Change Confirm SgNB Change Confirm
  • the MN side reconfigures the UE successfully, and the MN sends an SgNB Reconfiguration Complete (SgNB Reconfiguration Complete) to the target SN to notify the target SN that the reconfiguration is successful, and the target SN can start recording historical information in the current PScell.
  • the target SN refers to the historical information carried by the source SN in the subsequent SN Change decision to select the next target SN, and carries the historical information of the source SN in the SgNB Change Required message sent by the target SN to the MN in the SN Change process (from The historical information obtained by the source SN) and the historical information of the target SN (the historical information recorded by the target SN).
  • Step 509 The MN sends a UE Context Release to the source SN to notify the SN to release the UE context.
  • an embodiment of the present application provides an implementation solution for SN triggering SN Change in a 5GC-connected MR-DC scenario, including the following steps:
  • step 601 the UE successfully accesses the MN, and the MN sends an SN Addition Request (SN Addition Request) message to the SN (this SN is recorded as the source SN in this embodiment) to request the addition of the SN. Since it is the first time to add the SN, it does not carry the history of the SN. information.
  • SN Addition Request SN Addition Request
  • step 602 the source SN replies to the MN with an SN Addition Request Acknowledge (SN Addition Request Acknowledge) message to confirm adding the SN.
  • SN Addition Request Acknowledge SN Addition Request Acknowledge
  • step 603 the MN side reconfigures the UE successfully, and the MN sends an SN Reconfiguration Complete (SN Reconfiguration Complete) to the source SN to notify the source SN that the reconfiguration is successful, and the source SN can start to record historical information in the current PScell.
  • SN Reconfiguration Complete SN Reconfiguration Complete
  • step 604 the source SN initiates the SN Change process. At this time, no historical information is available for reference (only the historical information recorded by the source SN itself). The source SN sends a SN Change Required (SN Change Required) message to the MN to request SN Change, which carries historical information of the PScell in the source SN.
  • SN Change Required SN Change Required
  • Step 605 The MN sends an SN Addition Request (SN Addition Request) message to the target SN to request the addition of an SN, which carries historical information of the source SN.
  • SN Addition Request SN Addition Request
  • step 606 the target SN replies to the MN with an SN Addition Request Acknowledge (SN Addition Request Acknowledge) message to confirm the addition of the SN.
  • SN Addition Request Acknowledge SN Addition Request Acknowledge
  • step 607 the MN responds to the source SN with a SN Change Confirm (SN Change Confirm) message to confirm the SN Change.
  • SN Change Confirm SN Change Confirm
  • the MN side reconfigures the UE successfully, and the MN sends an SN Reconfiguration Complete (SN Reconfiguration Complete) to the target SN to notify the target SN that the reconfiguration is successful, and the target SN can start to record historical information in the current PScell.
  • the target SN refers to the historical information carried from the source SN in the subsequent SN Change decision to select the next target SN, and carries the history of the source SN and the target SN in the SN Change Required message sent by the target SN to the MN in the SN Change process information.
  • Step 609 The MN sends a UE Context Release to the source SN to notify the SN to release the UE context.
  • step 701 the UE successfully accesses the MN (this MN is the source MN in this embodiment, and will be referred to as the source MN in the following).
  • the source MN sends an SgNB Addition Request message to the SN to request the addition of an SN. Because it is the first time that the SN is added without carrying the SN history information.
  • Step 702 The SN replies a SgNB Addition Request Acknowledge message to the source MN to confirm the addition of the SN.
  • step 703 the source MN successfully reconfigures the UE, and the source MN sends an SgNB Reconfiguration Complete to the SN to notify the SN that the reconfiguration is successful, and the SN can start recording historical information in the current PScell.
  • Step 704 Before the source MN initiates the handover, the SN Modify process needs to be triggered, and the source MN sends an SgNB Modification Request (SgNB Modification Request) message to the SN to request SN configuration information.
  • SgNB Modification Request SgNB Modification Request
  • Step 705 The SN replies to the source MN with an SgNB Modification Request Acknowledge message, which carries historical information of the PScell in the SN.
  • Step 706 The source MN sends a Handover Request (Handover Request) message to the target MN to initiate handover, and the UE context information carries SN history information.
  • Handover Request Handover Request
  • step 707 the target MN initiates an SN addition process, and the target MN sends an SgNB Addition Request (SgNB Addition Request) to the SN, which also carries historical information in the SN.
  • SgNB Addition Request SgNB Addition Request
  • step 708 the SN recognizes that it is the same UE and the PScell remains unchanged, and continues to record the staying time in the current cell. Otherwise, if the PScell changes, re-record the information in the new cell, and the SN replies to the SN Addition Request Acknowledge ) To the target MN.
  • Step 709 The target MN replies to the source MN Handover Request Acknowledge (Handover Request Acknowledge) message.
  • Step 710 The source MN initiates a release preparation process of the SN, and the source MN sends an SgNB Release Request (SgNB Release Request) to the SN.
  • SgNB Release Request SgNB Release Request
  • Step 711 The SN sends an SgNb Release Request Acknowledge (SgNB Release Request Acknowledge) to the source MN.
  • SgNB Release Request Acknowledge SgNB Release Request Acknowledge
  • step 712 the target MN successfully reconfigures the UE, and the target MN sends SN Reconfiguration Complete to the SN to notify the SN that the reconfiguration is successful.
  • Step 713 The target MN sends a UE Context Release to the source MN to notify the source MN to initiate UE context release.
  • Step 714 The source MN initiates the release of the UE context of the SN, and the source MN sends the UE Context Release to the SN.
  • step 801 the UE successfully accesses the MN (referred to as the source MN in this embodiment), and the source MN sends an SgNB Addition Request message to the SN (referred to as the source SN in the subsequent steps) to request the addition of the SN.
  • the source MN sends an SgNB Addition Request message to the SN (referred to as the source SN in the subsequent steps) to request the addition of the SN.
  • step 802 the source SN replies a SgNB Addition Request Acknowledge message to the source MN to confirm the addition of the SN.
  • step 803 the source MN successfully reconfigures the UE, and the source MN sends SgNB Reconfiguration Complete to the source SN to notify the source SN that the reconfiguration is successful, and the source SN can start to record historical information in the current PScell.
  • Step 804 Before the source MN initiates the handover, the SN Modify process needs to be triggered, and the source MN sends a SgNB Modification Request message to the source SN to request SN configuration information.
  • step 805 the source SN replies to the source MN a SgNB Modification Request Acknowledge message, which carries historical information of the PScell in the source SN.
  • Step 806 The source MN sends a Handover Request message to the target MN to initiate handover, and the UE context information carries historical information of the UE in the source SN.
  • Step 807 The target MN initiates an adding process to the target SN, and the target MN sends an SgNB Addition Request (SgNB Addition Request) to the target SN, which also carries historical information in the source SN.
  • SgNB Addition Request SgNB Addition Request
  • Step 808 The target SN sends an SN Addition Request Acknowledge to the target MN, and the target SN records the historical information of the UE in the current SN.
  • Step 809 The target MN replies a Handover Request Acknowledge message to the source MN.
  • step 810 the source MN initiates a release preparation procedure of the source SN, and the source MN sends an SgNb release request (SgNB Release Request) to the source SN.
  • SgNB Release Request SgNB Release Request
  • Step 811 The source SN sends an SgNb Release Request Acknowledge (SgNB Release Request Acknowledge) to the source MN.
  • SgNB Release Request Acknowledge SgNB Release Request Acknowledge
  • step 812 the target MN successfully reconfigures the UE, and the target MN sends an SN Reconfiguration Complete to the target SN to notify the target SN that the reconfiguration is successful.
  • Step 813 The target MN notifies the source MN to initiate a UE context release, and the target MN sends a UE Context Release (UE Context Release) to the source MN.
  • UE Context Release UE Context Release
  • Step 814 The source MN initiates the release of the UE context of the source SN, and the source MN sends UE Context Release to the source SN.
  • an embodiment of the present application provides a node 90, which includes a memory 910 and a processor 920.
  • the memory 910 stores a program.
  • the program is read and executed by the processor 920, any The information management method described in an embodiment.
  • an embodiment of the present application provides a computer-readable storage medium 100.
  • the computer-readable storage medium 100 stores one or more programs 1010.
  • the one or more programs 1010 can be used by one or Multiple processors are executed to implement the information management method described in any embodiment.
  • an embodiment of the present application provides a node 110, which includes a memory 1110 and a processor 1120.
  • the memory 1110 stores a program.
  • the program is read and executed by the processor 1120, any A method for changing a secondary node described in an embodiment.
  • an embodiment of the present application provides a computer-readable storage medium 120.
  • the computer-readable storage medium 120 stores one or more programs 1210, and the one or more programs 1210 can be used by one or A plurality of processors are executed to implement the auxiliary node changing method described in any embodiment.
  • the functional modules/units in the system, and the device can be implemented as software, firmware, hardware, and appropriate combinations thereof.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of multiple The physical components cooperate to execute.
  • Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storing information (such as computer readable instructions, data structures, program modules, or other data) .
  • Computer storage media include Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other memories Technology, portable compact disk read-only memory (Compact Disc Read Only Memory, CD-ROM), digital versatile disk (Digital Video Disk, DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or Any other medium that can be used to store desired information and that can be accessed by a computer.
  • Communication media usually contain computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery media.

Landscapes

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

Abstract

本申请公开了一种信息管理方法、辅节点变更方法、节点及存储介质。所述信息管理方法，包括：在用户设备添加辅节点后，所述辅节点记录所述用户设备的历史信息。

Description

信息管理方法、辅节点变更方法、节点及存储介质
本申请要求在2019年06月24日提交中国专利局、申请号为201910550193.0的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种信息管理方法、辅节点变更方法、节点及存储介质。
背景技术
在第五代移动通信技术(5th Generation，5G)建网初期，在长期演进(Long Term Evolution，LTE)网络基础上部署5G热点，可以只建设5G基站，将5G无线***连接到相关技术中的LTE网络中，可以实现5G***的快速部署。通过双连接技术实现LTE和5G***间协同工作，有助于提升用户速率。标准协议为了区别LTE***内的双连接(Dual Connectivity，DC)，***移动通信技术(4th Generation，4G)和5G的双连接技术称为多无线双连接(Multi-Radio Dual Connectivity，MR-DC)，也包括了新无线(New Radio，NR)内的双连接。MR-DC，即多无线双连接，本文特指4G和5G双连接技术。MR-DC协议定义两种架构。
MR-DC with EPC，即演进的通用移动通信***陆地无线接入和新无线的双连接(E-UTRA-NR Dual Connectivity，EN-DC)，以eNB作为主节点，gNB作为辅节点的方式为非独立组网(Non-Standalone，NSA)终端提供服务。
MR-DC with 5GC，包括了下一代无线接入与E-UTRA-NR双连接(NG-RAN E-UTRA-NR Dual Connectivity，NGEN-DC)和NR-E-UTRA双连接(NR-E-UTRA Dual Connectivity，NE-DC)，主要区别是连接第五代核心网(5G Core，5GC)，哪个网元做主节点，哪个网元做辅节点。
相关技术中，双连接场景下由辅节点(Secondary Node，SN)发起的SN变更(SN Change)，通过通知主节点(Master Node，MN)执行到目标SN的SN添加(SN Add)操作。SN决策发起SN Change仅仅是参考信号质量等相关因素，有必要进行改进。
发明内容
本申请至少一实施例提供了一种信息管理方法、辅节点变更方法、节点及存储介质。
本申请至少一实施例提供一种信息管理方法，包括：
在用户设备添加辅节点后，所述辅节点记录所述用户设备的历史信息。
本申请至少一实施例提供一种信息管理方法，包括：
主节点在辅节点变更或修改过程中，将用户设备的历史信息发送给辅节点。
本申请至少一实施例提供一种辅节点变更方法，包括：
辅节点发起辅节点变更时，根据用户设备的历史信息选择目标辅节点。
本申请至少一实施例提供一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的信息管理方法。
本申请至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的信息管理方法。
本申请至少一实施例提供一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的辅节点变更方法。
本申请至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的辅节点变更方法。
附图说明
图1是本申请一实施例提供的信息管理方法的流程图(SN侧)；
图2是本申请一实施例提供的信息管理方法的流程图(MN侧)；
图3是本申请一实施例提供的辅节点变更方法的流程图；
图4是本申请一实施例提供的节点的框图；
图5a是本申请一实施例提供的EN-DC场景下控制面架构的示意图；
图5b是本申请一实施例提供的EN-DC场景下SN触发SN Change的流程图；
图6是本申请一实施例提供的连接5GC的MR-DC场景下SN触发SN Change的流程图；
图7是本申请一实施例提供的EN-DC场景下MN切换携带SN，SN不变的 流程图；
图8是本申请一实施例提供的EN-DC场景下MN切换携带SN，SN变更的流程图；
图9是本申请一实施例提供的节点的框图；
图10是本申请一实施例提供的计算机可读存储介质的框图；
图11是本申请另一实施例提供的节点的框图；
图12是本申请另一实施例提供的计算机可读存储介质的框图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机***中执行。并且，虽然在流程图中示出了逻辑顺序，但是在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请一实施例中，提供一种可用于双连接***的信息管理方法，用于记录和传递用户设备在SN侧主辅小区(SpCell of a secondary cell group，PScell)的历史信息，来辅助SN Change决策，从而选择更优的目标SN，增强***的鲁棒性。
本申请一实施例提供了一种双连接***的用户设备历史信息的管理方法，其中包括SN保存从MN携带过来的历史信息、记录当前SN下的历史信息、将SN的历史信息带给MN、SN参考历史信息选择目标SN触发SN Change过程。
如图1所示，本申请一实施例提供一种信息管理方法，包括：
步骤101，在用户设备(User Equimpment，UE)添加SN后，所述SN记录所述用户设备的历史信息。
本申请至少一实施例中提供一种信息管理方法，包括：在用户设备添加辅节点后，所述辅节点记录所述用户设备当前的历史信息。本实施例提供的方案，记录用户设备的历史信息，便于后续使用该历史信息。
UE添加SN成功后，由SN记录在PScell的历史信息，包括在此过程中的PScellChange导致的PScell变更后的历史信息，直至SN发生变更或删除。
在一实施例中，所述SN包括但不限于Secondary gNodeB(SgNB)、Secondary  eNodeB(SeNB)。
在一实施例中，所述历史信息包含的内容同当前协议定义一致，包括历史访问小区信息，所述历史访问小区信息包括小区***、小区标识、小区类型和当前小区驻留时间等信息。所述用户设备当前的历史信息是指用户设备在当前SN下驻留小区的信息。
在一实施例中，所述方法还包括：所述SN接收到MN发送的所述用户设备在其他SN下的历史信息时，保存所述用户设备在其他SN下的历史信息。在一实施例中，所述SN为目标SN，所述MN发起SN添加(Add)流程，此时MN通过SN添加请求(SN Addition Request)消息将历史信息携带给目标SN。
在一实施例中，所述方法还包括：在SN变更或修改过程中，所述SN将所述用户设备的历史信息发送给MN。在一实施例中，在SN变更(SN Change)或SN修改(SN Modify)过程中，源SN将历史信息携带给MN。其中，在SN变更过程中，可以通过SN变更请求(SN change Required)消息携带历史信息。其中，在SN修改过程中，可以通过SN修改请求确认(SN Modification Request Acknowledge)携带历史信息。
在一实施例中，所述SN发送给所述MN的历史信息包括所述SN自身记录的用户设备的历史信息(包括所述用户设备在所述辅节点下的历史信息和所述用户设备在添加所述辅节点之前的历史信息)，或者，包括所述SN自身记录的用户设备在所述SN下的历史信息以及所述SN接收到的所述用户设备在其他SN下的历史信息。源SN传递的历史信息包括从其他MN携带到源SN的历史信息以及源SN自身新记录的历史信息，是历史信息的累积。在一实施例中，如果记录的历史信息超出限定个数则删除部分记录，比如依次剔除掉最老的记录。其中，限定个数可以根据需要设置。
如图2所示，本申请一实施例提供一种信息管理方法，包括：
步骤201，MN在SN变更或修改过程中，将用户设备的历史信息发送给SN。
在一实施例中，可以在SN ADD请求中携带用户设备的历史信息。
在一实施例中，所述MN从源SN获取所述用户设备的历史信息。
在一实施例中，所述MN在SN变更或修改过程中，将用户设备的历史信息发送给SN包括：
所述MN在SN变更或修改过程中，将用户设备的历史信息发送给目标SN。
在一实施例中，所述MN在辅节点变更或修改过程中，将用户设备的历史 信息发送给辅节点包括：
所述MN为源MN，所述源MN在SN变更或修改过程中，将用户设备的历史信息发送给目标MN，由所述目标MN将所述用户设备的历史信息发送给目标SN。
如图3所示，本申请一实施例提供一种辅节点变更方法，包括：
步骤301，SN发起SN变更时，根据用户设备的历史信息选择目标SN。
SN决策要发起SN Change时，需要选择目标SN，此时除了参考信号质量外，可以参考历史信息从而选择更优的SN来进行变更。根据***实现可以提供一套选择算法，例如同等信号质量的情况下，参考小区的驻留时长，选择驻留时长较长的SN作为目标SN等，选择算法可以根据需要设定，本申请对此不作限定。
在一实施例中，所述方法还包括：所述SN从MN获取所述用户设备的历史信息。
本实施例提供的方案，通过记录和传递用户设备在SN的历史信息，在SN发起SN Change决策时参考所述历史信息，从而选择出SN Change的目标侧，增强***的鲁棒性。
本申请一实施例提供了一种节点400，如图4所示，此为示意图并不限定节点的实现。当节点作为双连接下的SN侧，所述节点400包括：记录模块401。
记录模块401，设置为SN添加成功后，负责记录在当前SN的历史信息，其中包括在SN内PScell变更等的整个历史轨迹。
在一实施例中，所述节点400还包括：
接收模块402，设置为接收MN发送的用户设备在SN下的历史信息。其中，该历史信息可在SN Add请求消息中携带。
存储模块403，设置为存储所述用户设备在SN下的历史信息。
在一实施例中，所述节点400还包括：发送模块404，设置为SN发起SN Change时，将UE的历史信息发送给MN；比如，在SN Change请求消息中携带历史信息。
在一实施例中，所述节点400还包括：决策模块405，设置为发起SN Change时，根据UE的历史信息进行决策确定目标SN。其中，可以采用预设算法，选择最优的目标SN。
下面通过几个应用实例说明本申请。
本申请一实施例提供一种辅节点变更方法，本实施例涉及EN-DC场景，如图5a所示，EN-DC场景下，仅eNB(即图5a中的MeNB，本实施例中主节点MN)才与演进分组核心网(Evolved Packet Core，EPC)有S1-C信令连接，SgNB(本实施例中辅节点SN)与EPC没有信令连接。eNB与gNB之间通过X2-C交互EN-DC相关信令。UE与LTE之间有信令连接，进行无线资源控制(Radio Resource Control，RRC)信令以及非接入层(Non-Access-Stratum，NAS)信令交互。在SgNB连接建立成功后，也可以进行与SgNB的RRC信令交互。
如图5b所示，包括以下步骤：
步骤501，UE在MN接入成功，MN向SN(本实施例中的源SN)发送SgNB添加请求(SgNB Addition Request)消息请求添加SN，由于是首次添加SN不携带SN的历史信息。
步骤502，源SN向MN回复SgNB添加请求确认(SgNB Addition Request Acknowledge)消息确认添加SN。
步骤503，MN侧重配UE成功，MN向源SN发送SgNB重配置完成(SgNB Reconfiguration Complete)通知源SN重配成功，源SN可以开始记录在当前PScell的历史信息。
步骤504，源SN发起SN Change过程，此时并无历史信息可供参考(此时只有源SN自身记录的历史信息，无来自其他SN的历史信息)。源SN向MN发送SgNB变更请求(SgNB Change Required)消息请求SN Change，携带了在源SN的PScell的历史信息。
步骤505，MN向目标SN发送SgNB添加请求(SgNB Addition Request)消息请求添加SN，携带了源SN的历史信息。
步骤506，目标SN向MN回复SgNB添加请求确认(SgNB Addition Request Acknowledge)消息确认添加SN。
步骤507，MN向源SN回复SgNB变更确认(SgNB Change Confirm)消息确认SN Change。
步骤508，MN侧重配UE成功，MN向目标SN发送SgNB重配置完成(SgNB Reconfiguration Complete)通知目标SN重配成功，目标SN可以开始记录在当前PScell的历史信息。目标SN在后续决策SN Change时参考从源SN携带的历史信息，从而选出下一个目标SN，并在SN Change流程目标SN向MN发送的SgNB Change Required消息中携带包括源SN的历史信息(从源SN获取的历史信息)和目标SN的历史信息(目标SN记录的历史信息)。
步骤509，MN向源SN发送UE上下文释放(UE Context Release)，通知SN 释放UE上下文。
如图6所示，本申请一实施例提供连接5GC的MR-DC场景下SN触发SN Change的实现方案，包括以下步骤：
步骤601，UE在MN接入成功，MN向SN(该SN在本实施例中记为源SN)发送SN添加请求(SN Addition Request)消息请求添加SN，由于是首次添加SN不携带SN的历史信息。
步骤602，源SN向MN回复SN添加请求确认(SN Addition Request Acknowledge)消息确认添加SN。
步骤603，MN侧重配UE成功，MN向源SN发送SN重配置完成(SN Reconfiguration Complete)通知源SN重配成功，源SN可以开始记录在当前PScell的历史信息。
步骤604，源SN发起SN Change过程，此时并无历史信息可供参考(只有源SN自身记录的历史信息)。源SN向MN发送SN变更请求(SN Change Required)消息请求SN Change，携带了在源SN的PScell的历史信息。
步骤605，MN向目标SN发送SN添加请求(SN Addition Request)消息请求添加SN，携带了源SN的历史信息。
步骤606，目标SN向MN回复SN添加请求确认(SN Addition Request Acknowledge)消息确认添加SN。
步骤607，MN向源SN回复SN变更确认(SN Change Confirm)消息确认SN Change。
步骤608，MN侧重配UE成功，MN向目标SN发送SN重配置完成(SN Reconfiguration Complete)通知目标SN重配成功，目标SN可以开始记录在当前PScell的历史信息。目标SN在后续决策SN Change时参考从源SN携带的历史信息，从而选出下一个目标SN，并在SN Change流程目标SN向MN发送的SN Change Required消息中携带包括源SN和目标SN的历史信息。
步骤609，MN向源SN发送UE上下文释放(UE Context Release)，通知SN释放UE上下文。
如图7所示，包括以下步骤：
步骤701，UE在MN(该MN为本实施例中的源MN，后续称为源MN)接入成功，源MN向SN发送SgNB Addition Request消息请求添加SN，由于是首次 添加SN不携带SN的历史信息。
步骤702，SN向源MN回复SgNB Addition Request Acknowledge消息确认添加SN。
步骤703，源MN侧重配UE成功，源MN向SN发送SgNB Reconfiguration Complete通知SN重配成功，SN可以开始记录在当前PScell的历史信息。
步骤704，源MN发起切换前，需要触发SN Modify流程，源MN给SN发送SgNB修改请求(SgNB Modification Request)消息请求SN配置信息。
步骤705，SN给源MN回复SgNB修改请求确认(SgNB Modification Request Acknowledge)消息，携带了在SN的PScell的历史信息。
步骤706，源MN给目标MN发送切换请求(Handover Request)消息发起切换，在UE上下文信息中携带SN的历史信息。
步骤707，目标MN发起SN的添加过程，目标MN发送SgNB添加请求(SgNB Addition Request)给SN，同样携带了在SN的历史信息。
步骤708，SN识别是同一个UE且PScell不变，则继续记录在当前小区的驻留时间，否则如果PScell变化，则重新记录在新小区的信息，SN回复SN添加请求确认(SN Addition Request Acknowledge)给目标MN。
步骤709，目标MN回复源MN切换请求确认(Handover Request Acknowledge)消息。
步骤710，源MN发起SN的释放准备流程，源MN发送SgNB释放请求(SgNB Release Request)给SN。
步骤711，SN发送SgNb释放请求确认(SgNB Release Request Acknowledge)给源MN。
步骤712，目标MN侧重配UE成功，目标MN向SN发送SN Reconfiguration Complete通知SN重配成功。
步骤713，目标MN发送UE上下文释放(UE Context Release)给源MN，通知源MN发起UE上下文释放。
步骤714，源MN发起SN的UE上下文释放，源MN发送UE Context Release给SN。
如图8所示，包括以下步骤：
步骤801，UE在MN(本实施例中，称为源MN)接入成功，源MN向SN (后续步骤中，称为源SN)发送SgNB Addition Request消息请求添加SN，由于是首次添加SN不携带SN的历史信息。
步骤802，源SN向源MN回复SgNB Addition Request Acknowledge消息确认添加SN。
步骤803，源MN侧重配UE成功，源MN向源SN发送SgNB Reconfiguration Complete通知源SN重配成功，源SN可以开始记录在当前PScell的历史信息。
步骤804，源MN发起切换前，需要触发SN Modify流程，源MN给源SN发送SgNB Modification Request消息请求SN配置信息。
步骤805，源SN给源MN回复SgNB Modification Request Acknowledge消息，携带了在源SN的PScell的历史信息。
步骤806，源MN给目标MN发送Handover Request消息发起切换，在UE上下文信息中携带UE在源SN的历史信息。
步骤807，目标MN发起向目标SN的添加过程，目标MN发送SgNB添加请求(SgNB Addition Request)给目标SN，同样携带了在源SN的历史信息。
步骤808，目标SN发送SN添加请求确认(SN Addition Request Acknowledge)给目标MN，目标SN记录UE在当前SN的历史信息。
步骤809，目标MN向源MN回复Handover Request Acknowledge消息。
步骤810，源MN发起源SN的释放准备流程，源MN发送SgNb释放请求(SgNB Release Request)给源SN。
步骤811，源SN发送SgNb释放请求确认(SgNB Release Request Acknowledge)给源MN。
步骤812，目标MN侧重配UE成功，目标MN向目标SN发送SN Reconfiguration Complete通知目标SN重配成功。
步骤813，目标MN通知源MN发起UE上下文释放，目标MN发送UE上下文释放(UE Context Release)给源MN。
步骤814，源MN发起源SN的UE上下文释放，源MN发送UE Context Release给源SN。
如图9所示，本申请一实施例提供一种节点90，包括存储器910和处理器920，所述存储器910存储有程序，所述程序在被所述处理器920读取执行时，实现任一实施例所述的信息管理方法。
如图10所示，本申请一实施例提供一种计算机可读存储介质100，所述计 算机可读存储介质100存储有一个或者多个程序1010，所述一个或者多个程序1010可被一个或者多个处理器执行，以实现任一实施例所述的信息管理方法。
如图11所示，本申请一实施例提供一种节点110，包括存储器1110和处理器1120，所述存储器1110存储有程序，所述程序在被所述处理器1120读取执行时，实现任一实施例所述的辅节点变更方法。
如图12所示，本申请一实施例提供一种计算机可读存储介质120，所述计算机可读存储介质120存储有一个或者多个程序1210，所述一个或者多个程序1210可被一个或者多个处理器执行，以实现任一实施例所述的辅节点变更方法。
上文中所公开方法中的全部或一些步骤、***、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由多种物理组件合作执行。一些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、电可擦只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、闪存或其他存储器技术、便携式紧凑磁盘只读存储器(Compact Disc Read Only Memory，CD-ROM)、数字多功能盘(Digital Video Disk，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (14)

  1. 一种信息管理方法，包括：
    在用户设备添加辅节点后，所述辅节点记录所述用户设备的历史信息。
  2. 根据权利要求1所述的信息管理方法，还包括：在所述辅节点接收到主节点发送的所述用户设备在其他辅节点下的历史信息的情况下，保存所述用户设备在所述其他辅节点下的历史信息。
  3. 根据权利要求1所述的信息管理方法，还包括：在辅节点变更或修改过程中，所述辅节点将所述用户设备的历史信息发送给主节点。
  4. 根据权利要求3所述的信息管理方法，其中，所述辅节点发送给所述主节点的历史信息包括所述辅节点自身记录的所述用户设备的历史信息，或者，包括所述辅节点自身记录的所述用户设备在所述辅节点下的历史信息以及所述辅节点接收到的所述用户设备在其他辅节点下的历史信息。
  5. 一种信息管理方法，包括：
    主节点在辅节点变更或修改过程中，将用户设备的历史信息发送给辅节点。
  6. 根据权利要求5所述的信息管理方法，还包括：所述主节点从源辅节点获取所述用户设备的历史信息。
  7. 根据权利要求5或6所述的信息管理方法，其中，所述主节点在辅节点变更或修改过程中，将用户设备的历史信息发送给辅节点包括：
    所述主节点在辅节点变更或修改过程中，将所述用户设备的历史信息发送给目标辅节点。
  8. 根据权利要求5或6所述的信息管理方法，其中，所述主节点在辅节点变更或修改过程中，将用户设备的历史信息发送给辅节点包括：
    所述主节点为源主节点，所述源主节点在辅节点变更或修改过程中，将所述用户设备的历史信息发送给目标主节点，所述目标主节点将所述用户设备的历史信息发送给目标辅节点。
  9. 一种辅节点变更方法，包括：
    在辅节点发起辅节点变更的情况下，根据用户设备的历史信息选择目标辅节点。
  10. 根据权利要求9所述的辅节点变更方法，还包括：所述辅节点从主节点获取所述用户设备的历史信息。
  11. 一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至8中任一项所述的信息管理方 法。
  12. 一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如权利要求1至8中任一项所述的信息管理方法。
  13. 一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求9或10所述的辅节点变更方法。
  14. 一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如权利要求9或10所述的辅节点变更方法。
PCT/CN2020/097420 2019-06-24 2020-06-22 信息管理方法、辅节点变更方法、节点及存储介质 WO2020259435A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2021577159A JP7308305B2 (ja) 2019-06-24 2020-06-22 情報管理方法、セカンダリノード変更方法、ノード及び記憶媒体
KR1020217042353A KR20220011728A (ko) 2019-06-24 2020-06-22 정보 관리 방법, 세컨더리 노드 변경 방법, 노드 및 저장 매체
EP20830934.4A EP3986030A4 (en) 2019-06-24 2020-06-22 INFORMATION MANAGEMENT METHOD, SECONDARY NODE CHANGING METHOD, NODE, AND STORAGE MEDIA
US17/622,510 US20220248294A1 (en) 2019-06-24 2020-06-22 Information management method, secondary node changing method, node, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910550193.0A CN112135332A (zh) 2019-06-24 2019-06-24 信息管理方法、辅节点变更方法、节点及存储介质
CN201910550193.0 2019-06-24

Publications (1)

Publication Number Publication Date
WO2020259435A1 true WO2020259435A1 (zh) 2020-12-30

Family

ID=73849627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097420 WO2020259435A1 (zh) 2019-06-24 2020-06-22 信息管理方法、辅节点变更方法、节点及存储介质

Country Status (6)

Country Link
US (1) US20220248294A1 (zh)
EP (1) EP3986030A4 (zh)
JP (1) JP7308305B2 (zh)
KR (1) KR20220011728A (zh)
CN (1) CN112135332A (zh)
WO (1) WO2020259435A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023206183A1 (zh) * 2022-04-27 2023-11-02 北京小米移动软件有限公司 成功PScell添加或更换报告的相关信息记录方法、装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115835321A (zh) * 2019-08-15 2023-03-21 华为技术有限公司 历史信息的记录方法、装置及计算机可读存储介质
KR20230115117A (ko) 2022-01-26 2023-08-02 주식회사 엘지에너지솔루션 배터리 soc 추정 장치 및 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104811924A (zh) * 2014-01-24 2015-07-29 上海贝尔股份有限公司 用于双连接***的用户设备历史信息的管理方法
WO2018111158A1 (en) * 2016-12-12 2018-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Network node and method for communicating with a wireless device using channel quality of scell
CN109691169A (zh) * 2016-08-11 2019-04-26 Lg 电子株式会社 在无线通信***中通过终端执行参考信号测量信息的方法和支持该方法的装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3584957B1 (en) * 2009-04-28 2021-03-10 Samsung Electronics Co., Ltd. Method and apparatus for managing user equipment history information in wireless communication network
CN102769877B (zh) * 2011-05-04 2017-08-25 中兴通讯股份有限公司 小区切换方法及基站
JP6314826B2 (ja) * 2012-10-05 2018-04-25 日本電気株式会社 無線通信システム、無線局、無線端末、ネットワーク装置、ベアラ制御方法、及びプログラム
CN104244318A (zh) * 2013-06-08 2014-12-24 株式会社Ntt都科摩 调整触发时间的方法及装置
EP2903386A1 (en) * 2014-01-29 2015-08-05 Alcatel Lucent Methode and device for establishing a dual connectivity between a user equipment and a MeNB and a SeNB, by providing the user equipment history information
JP2015177424A (ja) * 2014-03-17 2015-10-05 株式会社Ｋｄｄｉ研究所 基地局装置、端末装置、通信システムおよび通信方法
JP6765304B2 (ja) * 2014-08-06 2020-10-07 三菱電機株式会社 通信システム
CN106658719B (zh) * 2015-10-30 2019-12-17 中国电信股份有限公司 数据分流方法和装置
CN108282836B (zh) * 2017-01-06 2020-10-30 展讯通信（上海）有限公司 辅基站切换方法、装置及基站
KR102206336B1 (ko) * 2017-06-16 2021-01-25 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) 마스터 기지국 착수형 2차 기지국 해제 및 2차 기지국 착수형 2차 기지국 변경 프로시저들 사이의 경쟁 조건 회피
WO2019074429A1 (en) * 2017-10-09 2019-04-18 Telefonaktiebolaget Lm Ericsson (Publ) MASTER NODE, SECONDARY NODE AND METHODS IMPLEMENTED THEREBY
WO2020151735A1 (en) * 2019-01-25 2020-07-30 Qualcomm Incorporated Secondary cell group configuration in multi-radio access technology-dual connectivity and carrier aggregation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104811924A (zh) * 2014-01-24 2015-07-29 上海贝尔股份有限公司 用于双连接***的用户设备历史信息的管理方法
CN109691169A (zh) * 2016-08-11 2019-04-26 Lg 电子株式会社 在无线通信***中通过终端执行参考信号测量信息的方法和支持该方法的装置
WO2018111158A1 (en) * 2016-12-12 2018-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Network node and method for communicating with a wireless device using channel quality of scell

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3986030A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023206183A1 (zh) * 2022-04-27 2023-11-02 北京小米移动软件有限公司 成功PScell添加或更换报告的相关信息记录方法、装置

Also Published As

Publication number Publication date
JP7308305B2 (ja) 2023-07-13
CN112135332A (zh) 2020-12-25
US20220248294A1 (en) 2022-08-04
KR20220011728A (ko) 2022-01-28
JP2022539745A (ja) 2022-09-13
EP3986030A1 (en) 2022-04-20
EP3986030A4 (en) 2022-08-03

Similar Documents

Publication Publication Date Title
WO2020259435A1 (zh) 信息管理方法、辅节点变更方法、节点及存储介质
WO2018029930A1 (ja) 無線アクセスネットワークノード、無線端末、コアネットワークノード、及びこれらの方法
WO2018029933A1 (ja) 無線アクセスネットワークノード、無線端末、コアネットワークノード、及びこれらの方法
RU2679417C1 (ru) Способ распространения контекста ключа безопасности, объект управления мобильностью и базовая станция
WO2019134506A1 (zh) 一种波束失败恢复方法、装置及设备
US20190274072A1 (en) Communication system, security device, communication terminal, and communication method
US11457393B2 (en) Communication method and apparatus for realizing service continuity
CN108541033B (zh) 处理暂时用户端能力的装置及方法
KR102280393B1 (ko) 다중연결 통신 방법 및 디바이스
KR20210064322A (ko) 정보를 송신하기 위한 방법 및 장치
US20220279403A1 (en) Information transmission method and apparatus, storage medium and electronic apparatus
TW201831002A (zh) 處理新無線能力的裝置及方法
JP6545814B2 (ja) 通信方法、ユーザ機器、及び基地局
US12010570B2 (en) Method and device for establishing aggregated connection
TWI679915B (zh) 處理雙連結中次要節點改變的裝置及方法
US11057807B2 (en) First base station, second base station, and method
CN111083730B (zh) 一种数据处理方法及装置、网络设备
CN109451577B (zh) 一种网络通信方法及设备
CN106060850B (zh) 一种语音调度方法及装置
CN116438845A (zh) 通信方法和通信装置
CN115190640A (zh) 一种通信方法及通信装置
CN115623451A (zh) 条件切换方法和设备
US10123373B1 (en) Transfer of WCD service-context information through the WCD to facilitate transition of the WCD to a new serving base station
KR20170048455A (ko) 무선 단말, 제어 장치, 및 이들의 방법
US20240188152A1 (en) Systems and methods for establishing shared n3 tunnel

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20217042353

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021577159

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020830934

Country of ref document: EP

Effective date: 20220112