WO2020154868A1 - 一种参数配置方法及装置、网络设备 - Google Patents

一种参数配置方法及装置、网络设备 Download PDF

Info

Publication number
WO2020154868A1
WO2020154868A1 PCT/CN2019/073525 CN2019073525W WO2020154868A1 WO 2020154868 A1 WO2020154868 A1 WO 2020154868A1 CN 2019073525 W CN2019073525 W CN 2019073525W WO 2020154868 A1 WO2020154868 A1 WO 2020154868A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
base station
context
mobility control
anchor base
Prior art date
Application number
PCT/CN2019/073525
Other languages
English (en)
French (fr)
Inventor
王淑坤
杨宁
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/073525 priority Critical patent/WO2020154868A1/zh
Priority to CN201980060415.9A priority patent/CN112715038B/zh
Priority to PCT/CN2019/115422 priority patent/WO2020155725A1/zh
Publication of WO2020154868A1 publication Critical patent/WO2020154868A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a parameter configuration method and device, and network equipment.
  • RNA refers to the area used to control the terminal to perform cell selection and reselection in the inactive state. It is also the initial radio access network (RAN) The paging range area for paging. Scenarios that trigger the terminal to perform RNA update (RAN Notification Area Update, RNAU) include RNAU timer timeout or the terminal moves to an area outside of RNA.
  • RNAU Radio Access Network Notification Area
  • the anchor base station may decide not to migrate the terminal context to the target base station. Instead, the anchor base station generates a radio resource control (Radio Resource Control, RRC) release message, and Send the Packet Data Convergence Protocol (PDCP) packet data unit (PDU) of the RRC release message to the target base station, and the target base station sends the RRC release message to the terminal, so that the terminal completes the RAN location update process.
  • RRC release message can configure some terminal-specific information for the terminal, such as mobility control parameters. These parameters are generally configured by the network according to the topology and deployment of its surrounding network and network load. In the case that the terminal context does not migrate, these parameters are given by the anchor base station. At this time, the terminal may be far away from the anchor base station.
  • the anchor base station does not know the network deployment and topology and network load of the UE at this time. Therefore, there is no guiding significance for the anchor base station to configure these parameters.
  • the embodiments of the present application provide a parameter configuration method and device, and network equipment.
  • the target base station configures the mobility control parameters of the terminal
  • the target base station sends the mobility control parameters of the terminal to the anchor base station or to the terminal, where the anchor base station refers to a base station that saves the context of the terminal.
  • the anchor base station receives a terminal context request message sent by the target base station, where the terminal context request request message carries target information, where the anchor base station refers to a base station that saves the context of the terminal;
  • the anchor base station decides not to relocate the context of the terminal, send a terminal context requesting failure message to the target base station; if the anchor base station decides to relocate the terminal context, send a requesting terminal context response message to the target base station ,
  • the terminal context request response message carries the context of the terminal.
  • the parameter configuration device provided in the embodiment of the present application is applied to a target base station, and the device includes:
  • the configuration unit is used to configure the mobility control parameters of the terminal
  • the sending unit is configured to send the mobility control parameters of the terminal to an anchor base station or to the terminal, where the anchor base station refers to a base station that saves the context of the terminal.
  • the parameter configuration device provided in the embodiment of the present application is applied to an anchor base station, and the device includes:
  • the first receiving unit is configured to receive a terminal context request request message sent by a target base station, where the terminal context request request message carries target information, wherein the anchor base station refers to a base station that saves the context of the terminal;
  • the first sending unit is configured to send a requesting terminal context failure message to the target base station when the anchor base station decides not to relocate the context of the terminal; when the anchor base station decides to relocate the context of the terminal, to the target base station
  • the base station sends a terminal context request response message, and the terminal context request response message carries the context of the terminal.
  • the network device provided by the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the above parameter configuration method.
  • the chip provided in the embodiment of the present application is used to implement the above parameter configuration method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above parameter configuration method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned parameter configuration method.
  • the computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned parameter configuration method.
  • the computer program provided in the embodiment of the present application when it runs on a computer, causes the computer to execute the above parameter configuration method.
  • the target base station configures the terminal's mobility control parameters, which can assist the anchor base station to configure the terminal's mobility control parameters
  • the configuration information for the terminal makes the mobility control parameters reasonable and effective; or the target base station directly configures the configuration information of the mobility control parameters for the terminal, so that the mobility control parameters for the terminal are reasonable and effective.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of this application.
  • FIG. 2 is a schematic diagram of RRC state transition provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of the RNA in the RRC_INACTIVE state of the UE provided by an embodiment of the application;
  • FIG. 4 is a first schematic flowchart of a parameter configuration method provided by an embodiment of the application.
  • Figure 5(a) is a schematic flow chart of RNAU with context migration provided in an embodiment of the application.
  • Figure 5(b) is a schematic flow chart of RNAU without context migration provided in an embodiment of this application.
  • Fig. 6 is a schematic flow chart of RNAU with context migration provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram 1 of the process of configuring mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application;
  • FIG. 8 is a schematic diagram 2 of the procedure for configuring the mobility control parameters of the terminal during the RRC recovery process provided by an embodiment of this application;
  • FIG. 9 is a third schematic diagram of the flow of configuring mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram 4 of a flow chart for configuring mobility control parameters of a terminal in an RRC recovery process provided by an embodiment of this application;
  • FIG. 11 is a fifth schematic flowchart of configuring mobility control parameters of a terminal in the RRC recovery process provided by an embodiment of this application;
  • FIG. 12 is a second schematic flowchart of a parameter configuration method provided by an embodiment of the application.
  • FIG. 13 is a schematic diagram 1 of the structural composition of a parameter configuration device provided by an embodiment of the application.
  • FIG. 14 is a schematic diagram 2 of the structural composition of a parameter configuration device provided by an embodiment of the application.
  • 15 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of a chip according to an embodiment of the application.
  • FIG. 17 is a schematic block diagram of a communication system provided by an embodiment of this application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or a terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks, or network devices in the future evolution of Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B
  • eNB evolved base station
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridge
  • the communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110.
  • the "terminal” used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN public switched telephone network
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • a terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user Device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 with communication functions.
  • the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • 5G defines a new RRC state, that is, the RRC_INACTIVE state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state. among them,
  • RRC_IDLE state (abbreviated as idle state): mobility is UE-based cell selection and reselection, paging is initiated by the Core Network (CN), and the paging area is configured by the CN. There is no UE context on the base station side, and no RRC connection.
  • RRC_CONNECTED state (referred to as connected state for short): RRC connection exists, and UE context exists on the base station side and the UE side.
  • the network side knows that the location of the UE is of a specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.
  • Mobility is UE-based cell selection and reselection, there is a connection between CN-NR, UE context is stored on a certain base station, and paging is triggered by RAN, based on The paging area of the RAN is managed by the RAN, and the network side knows that the location of the UE is based on the paging area level of the RAN.
  • the network side can control the RRC state transition of the UE, as shown in Figure 2, specifically:
  • the network side can control the UE to switch from the RRC_CONNECTED state to the RRC_INACTIVE state by releasing and suspending the RRC connection;
  • the network side can control the UE to transition from the RRC_INACTIVE state to the RRC_CONNECTED state by restoring the RRC connection.
  • the network side can control the UE to switch from the RRC_CONNECTED state to the RRC_IDLE state by releasing the RRC connection;
  • the network side can control the UE to transition from the RRC_IDLE state to the RRC_CONNECTED state by establishing an RRC connection.
  • the network side can control the UE to transition from the RRC_INACTIVE state to the RRC_IDLE state by releasing the RRC connection.
  • any one of the following events can trigger the UE to return to the RRC_IDLE state autonomously:
  • the timer T319 is started, if the timer T319 expires;
  • Radio Access Technology RAT
  • the UE When the UE is in the RRC_INACTIVE state, it has the following characteristics:
  • the UE is reachable to the RAN side, and the relevant parameters are configured by the RAN;
  • the UE moves within the RNA configured by the RAN, it does not need to notify the network side, but it needs to notify the network side when it moves out of the RNA;
  • the UE moves within the RNA according to the cell selection reselection method.
  • RNA is used to control the area where the UE performs cell selection and reselection in the inactive state, and is also the paging range area for RAN initial paging.
  • the RAN discontinuous reception cycle (RAN DRX cycle) is used to calculate the paging occasion of the RAN initial paging.
  • RNAU period (RNAU periodicity) is used to control the period in which the UE performs periodic RAN location updates.
  • NCC used for the secret key used in the RRC connection recovery process.
  • Figure 3 is a schematic diagram of the RNA when the UE is in the RRC_INACTIVE state.
  • the cell range covered by the base station 1 to the base station 5 is RNA.
  • the network side does not need to be notified, and the mobility behavior in the idle state is followed, that is, cell selection reselection in principle.
  • the UE moves out of the paging area configured by the RAN, the UE will be triggered to resume the RRC connection and reacquire the paging area configured by the RAN.
  • the gNB that maintains the connection between the RAN and the CN for the UE will trigger all cells in the RAN paging area to send paging messages to the UE, so that the UE in the inactive state can resume the RRC connection and receive data.
  • the UE in the inactive state is configured with a RAN paging area. In this area, in order to ensure the reachability of the UE, the UE needs to perform periodic location update according to the period configured by the network. Therefore, the scenarios that trigger the UE to perform RNA update include the timeout of the RNAU timer or the UE moving to an area outside the RNA.
  • the CN initial paging and the RAN initial paging are received at the same time.
  • the UE in the inactive state maintains the connection between the RAN and the CN.
  • the RAN is triggered to initiate an initial paging of the RAN to notify the UE to resume the RRC connection in order to receive downlink data.
  • the initial paging message of the RAN is the same as the initial paging message of the CN, but the DRX used in calculating the paging time is different.
  • FIG. 4 is a schematic flowchart 1 of a parameter configuration method provided by an embodiment of the application. As shown in FIG. 4, the parameter configuration method includes the following steps:
  • Step 401 The target base station configures the mobility control parameters of the terminal.
  • RNAU scenario the scenario where the terminal enters the connected state from the inactive state.
  • RNAU timer timeout or the terminal moves to an area outside of RNA.
  • the flow of RNAU is described below.
  • Figure 5(a) is a schematic flow diagram of RNAU with context migration, as shown in Figure 5(a), including the following processes:
  • the terminal sends an RRC recovery request message to the target base station.
  • the RRC recovery request message may carry a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station sends a terminal context request message to the anchor base station.
  • the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.
  • the anchor base station sends a request for terminal context response message to the target base station.
  • the terminal context request response message carries the context of the terminal.
  • the target base station controls the terminal to be in an inactive state.
  • the target base station sends data forwarding address indication information to the anchor base station.
  • the target base station sends a path switching request message to the Access and Mobility Management Function (AMF).
  • AMF Access and Mobility Management Function
  • the AMF sends a path switching response message to the target base station.
  • the target base station sends an RRC release message to the terminal.
  • the RRC release message carries suspension indication information.
  • the target base station sends a terminal context release message to the anchor base station.
  • Figure 5(b) is a schematic diagram of the RNAU process without context migration, as shown in Figure 5(b), including the following processes:
  • the terminal sends an RRC recovery request message to the target base station.
  • the RRC recovery request message may carry a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station sends a terminal context request message to the anchor base station.
  • the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.
  • the anchor base station sends a failure requesting terminal context message to the target base station.
  • the target base station sends an RRC release message to the terminal.
  • the RRC release message carries suspension indication information.
  • the events that trigger the terminal to enter the connected state from the inactive state include: I) the terminal has downlink data arriving, and the network initiates the initial paging of the RAN to prompt the terminal to enter the connected state; II) the terminal itself initiates RAN location area update, such as periodic RAN Location update or cross-regional location update; III) The terminal has an uplink data transmission request, which prompts the terminal to enter the connected state.
  • the following describes the flow of the terminal from the inactive state to the connected state.
  • Figure 6 is a schematic diagram of the flow of RNAU with context migration, as shown in Figure 6, including the following flow:
  • the terminal sends an RRC recovery request message to the target base station.
  • the target base station sends a terminal context request message to the anchor base station.
  • the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.
  • the anchor base station sends a request for terminal context response message to the target base station.
  • the terminal context request response message carries the context of the terminal.
  • the target base station sends an RRC recovery message to the terminal.
  • the terminal sends an RRC recovery complete message to the target base station.
  • the target base station sends data forwarding address indication information to the anchor base station.
  • the target base station sends a path switching request message to the AMF.
  • the AMF sends a path switching response message to the target base station.
  • the target base station sends a terminal context release message to the anchor base station.
  • the types of the target base station and the anchor base station are not limited.
  • the target base station and the anchor base station belong to the same type of base station, for example, the target base station and the anchor base station are both NR base stations (gNB).
  • the target base station and the anchor base station belong to different types of base stations, for example, the target base station is an NR base station (gNB), and the anchor base station is an LTE base station (eNB).
  • the target base station refers to a new base station that provides services for the terminal during the foregoing RRC recovery process
  • the anchor base station refers to the original base station that provides services for the terminal last time during the foregoing RRC recovery process.
  • the anchor base station needs to decide whether to transfer the context of the terminal to the target base station side . Therefore, the target base station will send the first cause value carried in the RRC recovery request message sent by the terminal to the anchor base station during the terminal context request process, and the anchor base station determines whether the context of the terminal needs to be transferred to the target base station side.
  • the target base station configures the mobility control parameters of the terminal.
  • Step 402 The target base station sends the mobility control parameter of the terminal to the anchor base station or to the terminal, where the anchor base station refers to a base station that saves the context of the terminal.
  • the target base station sends the mobility control parameters of the terminal to the anchor base station, thereby assisting the anchor base station in configuring the mobility control parameters of the terminal; or, the target base station directly configures the terminal mobility control parameters.
  • the mobility control parameter of the terminal is delivered to the terminal through an RRC release message.
  • the mobility control parameter of the terminal specifically refers to the mobility control parameter after the terminal enters an idle state or an inactive state.
  • the mobility control parameter of the terminal includes at least one of the following:
  • a first parameter where the first parameter is used to indicate frequency point information and RAT information to be preferentially selected after the terminal enters an idle state or an inactive state;
  • a second parameter where the second parameter is used to indicate frequency priority information for performing cell selection and reselection after the terminal enters an idle state or an inactive state;
  • the third parameter is used to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state.
  • the first parameter is redirectedCarrierInfo, indicating the frequency information and RAT information that the UE prefers to select after entering the idle state or inactive state
  • the second parameter is cellReselectionPriorities, indicating the frequency at which the UE will perform cell selection and reselection after entering the idle state or inactive state Priority configuration parameter
  • the third parameter is deprioritisationReq, which indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state. Table 1 shows the configuration information of these three parameters.
  • the following describes in detail how to configure the mobility control parameters of the terminal on the network side in conjunction with the specific RRC recovery process.
  • FIG. 7 is a schematic diagram 1 of the procedure for configuring the mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application. As shown in FIG. 7, the procedure includes the following steps:
  • the target base station receives the RRC recovery request message sent by the terminal.
  • the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.
  • RRCResumeRequest RRC recovery request
  • the target base station determines that it is necessary to indicate the configuration information of the mobility control parameter of the terminal to the anchor base station.
  • the RRC recovery request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station determines that it is necessary to control the mobility of the terminal based on the first cause value in the RRC recovery request message (the first cause value indicates that the triggering cause of the RRC connection recovery process is RNAU)
  • the configuration information of the parameters is indicated to the anchor base station.
  • the target base station sends a request for terminal context request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station, where the request for terminal context request message carries configuration information of the mobility control parameters of the terminal.
  • RETRIEVE UE CONTEXT REQUEST request for terminal context request
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • the anchor base station decides not to relocate the context of the terminal, it carries the configuration information of the mobility control parameters of the terminal configured by the target base station in the RRC release message, and generates the RRC release message RRC releases PDCP PDU (RRCRelease PDCP PDU).
  • the target base station receives the RETRIEVE UE CONTEXT FAILURE message sent by the anchor base station.
  • the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control of the terminal. Configuration information of the parameter.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • the target base station After receiving the RRC release PDCP PDU, the target base station sends an RRC release message to the terminal according to the RRC release PDCP PDU, where the RRC release message carries configuration information of mobility control parameters of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • FIG. 8 is a schematic diagram of the second flow of configuring mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application. As shown in FIG. 8, the flow includes the following steps:
  • the target base station receives the RRC recovery request message sent by the terminal.
  • the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.
  • RRCResumeRequest RRC recovery request
  • the target base station determines that it is necessary to indicate the configuration information of the mobility control parameter of the terminal to the anchor base station.
  • the RRC recovery request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station determines that it is necessary to control the mobility of the terminal based on the first cause value in the RRC recovery request message (the first cause value indicates that the triggering cause of the RRC connection recovery process is RNAU)
  • the configuration information of the parameters is indicated to the anchor base station.
  • the target base station sends a request for terminal context request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station, where the request for terminal context request message carries configuration information of the mobility control parameters of the terminal.
  • RETRIEVE UE CONTEXT REQUEST request for terminal context request
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • the anchor base station decides to relocate the context of the terminal, it ignores the configuration information of the mobility control parameter of the terminal configured by the target base station.
  • the target base station receives a terminal context request response (RETRIEVE UE CONTEXT RESPONSE) message sent by the anchor base station, where the terminal context request response message carries the context of the terminal.
  • RETRIEVE UE CONTEXT RESPONSE terminal context request response
  • the target base station sends an RRC release message generated by itself to the terminal.
  • the RRC release message generated by the target base station itself carries configuration information of the mobility control parameters of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • FIG. 9 is a schematic diagram of the third flow of configuring the mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application. As shown in FIG. 9, the flow includes the following steps:
  • the target base station receives the RRC recovery request message sent by the terminal.
  • the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.
  • RRCResumeRequest RRC recovery request
  • the target base station sends a request for terminal context request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station.
  • the request for terminal context request message carries a first reason value, and the first reason value is used to indicate the triggering of the RRC connection recovery process
  • the reason is RNAU.
  • the terminal context request request message further carries first indication information, and the first indication information is used to indicate that the target base station has mobility control parameters that need to be configured for the terminal.
  • the anchor base station decides not to migrate the context of the terminal.
  • the target base station receives the mobility control parameter request message or second indication information sent by the anchor base station, where the second indication information is used to instruct the anchor base station not to relocate the context of the terminal.
  • the anchor base station sends a request for mobility control parameter message or second indication information to the anchor base station according to the first indication information and the decision not to migrate the context of the terminal, or only according to the decision not to migrate the context of the terminal,
  • the second indication information is used to indicate that the anchor base station does not relocate the context of the terminal.
  • the target base station sends the mobility control parameter of the terminal to the anchor base station.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • the target base station receives the RETRIEVE UE CONTEXT FAILURE message sent by the anchor base station.
  • the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control of the terminal. Configuration information of the parameter.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates the low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • the target base station After receiving the RRC release PDCP PDU, the target base station sends an RRC release message to the terminal according to the RRC release PDCP PDU, where the RRC release message carries configuration information of the mobility control parameters of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • Fig. 10 is a schematic diagram 4 of the procedure for configuring the mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application. As shown in Fig. 10, the procedure includes the following steps:
  • the target base station receives the RRC recovery request message sent by the terminal.
  • the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.
  • RRCResumeRequest RRC recovery request
  • the RRC recovery request message further carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station decides that it needs to instruct the anchor base station to perform context migration of the terminal.
  • the target base station decides that it needs to instruct the anchor base station to perform context migration of the terminal.
  • the target base station sends a request for terminal context request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station, where the request for terminal context request message carries a first reason value, and the first reason value is used to indicate the triggering of the RRC connection recovery process
  • the reason is RNAU.
  • the terminal context request request message further carries second indication information, and the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal or is used to indicate that the target base station is configured for the The mobility control parameter of the terminal.
  • the second indication information and the first cause value are used by the anchor base station to decide whether to migrate the context of the terminal.
  • the anchor base station decides whether to relocate the context of the terminal according to the second indication information and the first cause value.
  • the anchor base station jointly decides whether to migrate the context of the terminal according to the second indication information of the target base station and the reason value (such as RNAU) for the terminal to initiate the RRC recovery process.
  • the reason value such as RNAU
  • the target base station receives a request for terminal context response (RETRIEVE UE CONTEXT RESPONSE) message sent by the anchor base station, where the terminal context response message carries the context of the terminal.
  • RETRIEVE UE CONTEXT RESPONSE request for terminal context response
  • the anchor base station decides to migrate the context of the terminal, it sends a terminal context request response message to the target base station, and the terminal context request response message carries the context of the terminal.
  • the target base station sends the RRC release message generated by itself to the terminal.
  • the RRC release message generated by the target base station itself carries configuration information of the mobility control parameters of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • the first parameter (such as redirectedCarrierInfo) indicates the frequency point information and RAT information that the UE prefers to select after entering the idle state or the inactive state;
  • the second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameter for performing cell selection and reselection after the UE enters the idle state or the inactive state;
  • the third parameter (such as deprioritisationReq) indicates low priority frequency information or RAT information after the UE enters the idle state or the inactive state.
  • Table 1 shows the configuration information of these three parameters.
  • FIG. 11 is a schematic diagram 5 of the flow of configuring mobility control parameters of the terminal in the RRC recovery process provided by an embodiment of the application. As shown in FIG. 11, the flow includes the following steps:
  • the target base station receives the RRC recovery request message sent by the terminal.
  • the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.
  • RRCResumeRequest RRC recovery request
  • the RRC recovery request message further carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the target base station sends a request for terminal context request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station.
  • the request for terminal context request message carries a first reason value, and the first reason value is used to indicate the triggering of the RRC connection recovery process
  • the reason is RNAU.
  • the anchor base station decides not to migrate the context of the terminal according to the first cause value.
  • the anchor base station if the anchor base station decides not to relocate the context of the terminal, the anchor base station does not configure the mobility control parameters of the terminal in the RRC release (RRCRelease) message.
  • the target base station receives the request terminal context failure (RETRIEVE UE CONTEXT FAILURE) message sent by the anchor base station, the request terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU does not carry the mobility of the terminal Control parameter configuration information.
  • RETRIEVE UE CONTEXT FAILURE request terminal context failure
  • the target base station After receiving the RRC release PDCP PDU, the target base station sends an RRC release message to the terminal according to the RRC release PDCP PDU, and the RRC release message does not carry configuration information of the mobility control parameters of the terminal.
  • Figure 12 is a schematic diagram of the second flow of the parameter configuration method provided by the embodiment of the application. It should be noted that the solution in this example is applied to the anchor base station side, and the method in this example can be understood in combination with the method on the target base station side, as shown in Figure 12, the parameter configuration method includes the following steps:
  • Step 1201 The anchor base station receives a request for terminal context request message sent by a target base station, where the request for terminal context request message carries target information, where the anchor base station refers to a base station that saves the context of the terminal.
  • the terminal mobility control parameter is configured on the target base station side, and the terminal context request request message carries configuration information of the mobility control parameter of the terminal configured by the target base station.
  • the mobility control parameter of the terminal includes at least one of the following:
  • a first parameter where the first parameter is used to indicate frequency point information and RAT information to be preferentially selected after the terminal enters an idle state or an inactive state;
  • a second parameter where the second parameter is used to indicate frequency priority information for performing cell selection and reselection after the terminal enters an idle state or an inactive state;
  • the third parameter is used to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state.
  • the anchor base station receives the terminal context request message sent by the target base station, and the terminal context request message carries the configuration of the mobility control parameters of the terminal configured by the target base station. information;
  • the terminal context request request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the terminal context request request message further carries first indication information, and the first indication information is used to indicate that the target base station has mobility control parameters that need to be configured for the terminal.
  • the terminal context request request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the terminal context request request message further carries second indication information, and the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal.
  • Step 1202 If the anchor base station decides not to relocate the context of the terminal, send a requesting terminal context failure message to the target base station; if the anchor base station decides to relocate the context of the terminal, send the requesting terminal to the target base station A context response message, where the terminal context request response message carries the context of the terminal.
  • the anchor base station if it decides not to relocate the context of the terminal, it sends a requesting terminal context failure message to the target base station; if the anchor base station decides to relocate the context of the terminal, it sends a message to the target base station. Sending a terminal context request response message, where the terminal context request response message carries the context of the terminal.
  • the request for terminal context failure message can carry the mobility control parameter of the terminal. In this way, the mobility control parameter of the terminal can be delivered to the terminal.
  • the anchor base station decides not to relocate the context of the terminal, it carries the configuration information of the mobility control parameters of the terminal configured by the target base station in the RRC release message RRC release PDCP PDU (RRCRelease PDCP PDU) that generates the RRC release message.
  • RRC release PDCP PDU RRCRelease PDCP PDU
  • the anchor base station sends a request terminal context failure (RETRIEVE UE CONTEXT FAILURE) message to the target base station, and the terminal context request failure message carries the RRC release PDCP PDU, and the RRC releases the PDCP
  • the PDU carries configuration information of the mobility control parameters of the terminal.
  • step 4 in FIG. 8 when the anchor base station decides to relocate the context of the terminal, it ignores the configuration information of the mobility control parameter of the terminal configured by the target base station.
  • the anchor base station sends a request for a terminal context response (RETRIEVE UE CONTEXT RESPONSE) message to the target base station, and the request for a terminal context response message carries the context of the terminal.
  • RETRIEVE UE CONTEXT RESPONSE request for a terminal context response
  • the request for terminal context request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the terminal context request request message further carries first indication information, and the first indication information is used to indicate that the target base station has mobility control parameters that need to be configured for the terminal.
  • the anchor base station decides to relocate the context of the terminal, it sends a request for mobility control parameters or second indication information to the target base station, where the second indication information is used to indicate the The anchor base station does not migrate the context of the terminal.
  • the anchor base station receives the mobility control parameters of the terminal sent by the target base station; carries the configuration information of the mobility control parameters of the terminal configured by the target base station in the RRC In the release message, the RRC release PDCP PDU that generates the RRC release message.
  • the anchor base station sends a request for terminal context failure (RETRIEVE UE CONTEXT FAILURE) message to the target base station, the requesting terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries Configuration information of the mobility control parameters of the terminal.
  • RETRIEVE UE CONTEXT FAILURE request for terminal context failure
  • the terminal context request request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the terminal context request request message further carries second indication information, and the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal.
  • the anchor base station determines whether to relocate the context of the terminal according to the second indication information and the first cause value.
  • step 5 in FIG. 10 when the anchor base station decides to migrate the context of the terminal, it sends a request for terminal context response (RETRIEVE UE CONTEXT RESPONSE) message to the target base station, and the request for terminal context response message carries the terminal The context.
  • RETRIEVE UE CONTEXT RESPONSE request for terminal context response
  • the anchor base station decides not to migrate the context of the terminal according to the first cause value.
  • the anchor base station decides not to relocate the context of the terminal, the anchor base station does not configure the mobility control parameters of the terminal in the RRC release (RRCRelease) message.
  • the anchor base station asks the target base station for a terminal context failure (RETRIEVE UE CONTEXT FAILURE) message, the requesting terminal context failure message
  • the RRC release PDCP PDU is carried, and the RRC release PDCP PDU does not carry the configuration information of the mobility control parameter of the terminal.
  • FIG. 13 is a schematic diagram 1 of the structural composition of a parameter configuration device provided by an embodiment of the application.
  • the device is applied to a target base station. As shown in FIG. 13, the device includes:
  • the configuration unit 1301 is used to configure the mobility control parameters of the terminal
  • the sending unit 1302 is configured to send the mobility control parameters of the terminal to an anchor base station or to the terminal, where the anchor base station refers to a base station that saves the context of the terminal.
  • the device further includes:
  • the first receiving unit 1303 is configured to receive the RRC recovery request message sent by the terminal;
  • the determining unit 1304 is configured to determine that the configuration information of the mobility control parameter of the terminal needs to be indicated to the anchor base station;
  • the sending unit 1302 is configured to send a terminal context request request message to the anchor base station, where the terminal context request request message carries configuration information of the mobility control parameter of the terminal.
  • the RRC recovery request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU;
  • the determining unit 1304 is configured to determine, based on the first cause value in the RRC recovery request message, that it is necessary to indicate the configuration information of the mobility control parameter of the terminal to the anchor base station.
  • the apparatus further includes:
  • the second receiving unit 1305 is configured to receive a terminal context request failure message sent by the anchor base station, where the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control parameters of the terminal Configuration information;
  • the sending unit 1302 is configured to send an RRC release message to the terminal according to the RRC release PDCP PDU, where the RRC release message carries configuration information of mobility control parameters of the terminal.
  • the apparatus when the anchor base station decides to migrate the context of the terminal, the apparatus further includes:
  • the second receiving unit 1305 is configured to receive a terminal context request response message sent by the anchor base station, where the terminal context request response message carries the context of the terminal;
  • the sending unit 1302 is further configured to send an RRC release message generated by itself to the terminal.
  • the RRC release message generated by the target base station itself carries configuration information of the mobility control parameter of the terminal.
  • the device further includes:
  • the first receiving unit 1303 is configured to receive the RRC recovery request message sent by the terminal;
  • the sending unit 1302 is further configured to send a terminal context request request message to the anchor base station, where the terminal context request request message carries a first cause value, and the first cause value is used to indicate the reason for triggering the RRC connection recovery process It is RNAU.
  • the terminal context request request message also carries first indication information, and the first indication information is used to indicate that the target base station has mobility control parameters that need to be configured for the terminal.
  • the apparatus further includes:
  • the third receiving unit 1306 is configured to receive a mobility control parameter request message or second indication information sent by the anchor base station, where the second indication information is used to instruct the anchor base station not to relocate the context of the terminal;
  • the sending unit 1302 is configured to send mobility control parameters of the terminal to the anchor base station;
  • the second receiving unit 1305 is configured to receive a terminal context request failure message sent by the anchor base station, where the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control parameters of the terminal Configuration information;
  • the sending unit 1302 is configured to send an RRC release message to the terminal according to the RRC release PDCP PDU, where the RRC release message carries configuration information of mobility control parameters of the terminal.
  • the terminal context request request message further carries second indication information, and the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal;
  • the second indication information and the first cause value are used by the anchor base station to decide whether to migrate the context of the terminal.
  • the apparatus when the anchor base station decides to migrate the context of the terminal, the apparatus further includes:
  • the second receiving unit 1305 is configured to receive a terminal context request response message sent by the anchor base station, where the terminal context response message carries the context of the terminal;
  • the sending unit is configured to send an RRC release message generated by itself to the terminal.
  • the RRC release message generated by the target base station itself carries configuration information of the mobility control parameter of the terminal.
  • the apparatus further includes:
  • the second receiving unit 1305 is configured to receive a terminal context request failure message sent by the anchor base station, where the terminal context request failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry mobility control parameters of the terminal Configuration information;
  • the sending unit 1302 is configured to send an RRC release message to the terminal according to the RRC release PDCP PDU,
  • the RRC release message does not carry configuration information of the mobility control parameter of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • a first parameter where the first parameter is used to indicate frequency point information and RAT information to be preferentially selected after the terminal enters an idle state or an inactive state;
  • a second parameter where the second parameter is used to indicate frequency priority information for performing cell selection and reselection after the terminal enters an idle state or an inactive state;
  • the third parameter is used to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state.
  • FIG. 14 is a schematic diagram 2 of the structural composition of a parameter configuration device provided by an embodiment of the application.
  • the device is applied to an anchor base station.
  • the device includes:
  • the first receiving unit 1401 is configured to receive a terminal context request request message sent by a target base station, where the terminal context request request message carries target information, where the anchor base station refers to a base station that saves the context of the terminal;
  • the first sending unit 1402 is configured to send a requesting terminal context failure message to the target base station when the anchor base station decides not to relocate the context of the terminal; when the anchor base station decides to relocate the context of the terminal, to the target base station;
  • the target base station sends a terminal context request response message, and the terminal context request response message carries the context of the terminal.
  • the terminal context request request message carries configuration information of the mobility control parameters of the terminal configured by the target base station;
  • the device further includes: a generating unit 1403, configured to carry the configuration information of the mobility control parameters of the terminal configured by the target base station in the RRC when the anchor base station decides not to migrate the context of the terminal In the release message, the RRC release PDCP PDU that generates the RRC release message;
  • the first sending unit 1402 is configured to send a terminal context request failure message to the target base station, where the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility of the terminal Control parameter configuration information.
  • the terminal context request request message carries configuration information of the mobility control parameters of the terminal configured by the target base station;
  • the first sending unit 1402 is configured to ignore the configuration information of the mobility control parameters of the terminal configured by the target base station when the anchor base station decides to migrate the context of the terminal; Sending a terminal context request response message, where the terminal context request response message carries the context of the terminal.
  • the terminal context request request message carries a first cause value, and the first cause value is used to indicate that the triggering cause of the RRC connection recovery process is RNAU.
  • the terminal context request request message also carries first indication information, and the first indication information is used to indicate that the target base station has mobility control parameters that need to be configured for the terminal.
  • the device further includes:
  • the second sending unit 1404 is configured to send a request for mobility control parameter message or second indication information to the target base station when the anchor base station decides to migrate the context of the terminal, where the second indication information is used to indicate The anchor base station does not relocate the context of the terminal;
  • the second receiving unit 1405 is configured to receive the mobility control parameter of the terminal sent by the target base station;
  • the generating unit 1403 is configured to carry the configuration information of the mobility control parameters of the terminal configured by the target base station in an RRC release message, and generate the RRC release PDCP PDU of the RRC release message;
  • the first sending unit 1402 is configured to send a terminal context request failure message to the target base station, where the terminal context request failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility of the terminal Control parameter configuration information.
  • the terminal context request request message further carries second indication information, and the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal; the apparatus further includes:
  • the determining unit 1406 is configured to determine whether to migrate the context of the terminal according to the second indication information and the first cause value
  • the first sending unit 1402 is configured to send a terminal context request response message to the target base station when the anchor base station decides to migrate the context of the terminal, where the terminal context request response message carries the context of the terminal .
  • the first sending unit is configured to request a terminal context failure message from the target base station, and the request terminal context failure message carries The RRC releases the PDCP PDU, and the RRC releases the PDCP PDU does not carry configuration information of the mobility control parameter of the terminal.
  • the mobility control parameter of the terminal includes at least one of the following:
  • a first parameter where the first parameter is used to indicate frequency point information and RAT information to be preferentially selected after the terminal enters an idle state or an inactive state;
  • a second parameter where the second parameter is used to indicate frequency priority information for performing cell selection and reselection after the terminal enters an idle state or an inactive state;
  • the third parameter is used to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state.
  • FIG. 15 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device may be a network device, such as a target base station or an anchor base station.
  • the communication device 600 shown in FIG. 15 includes a processor 610.
  • the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application. .
  • the communication device 600 may further include a memory 620.
  • the processor 610 can call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .
  • the communication device 600 may specifically be a mobile terminal/terminal according to an embodiment of the application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal in each method of the embodiments of the application. For the sake of brevity, This will not be repeated here.
  • FIG. 16 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 700 shown in FIG. 16 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip 700 may further include an input interface 730.
  • the processor 710 can control the input interface 730 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • it will not be omitted here. Repeat.
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • FIG. 17 is a schematic block diagram of a communication system 900 according to an embodiment of the present application. As shown in FIG. 17, the communication system 900 includes a terminal 910 and a network device 920.
  • the terminal 910 may be used to implement the corresponding functions implemented by the terminal in the foregoing method
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the foregoing method.
  • details are not described herein again.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be Read-Only Memory (ROM), Programmable Read-Only Memory (Programmable ROM, PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), and Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application, in order to It's concise, so I won't repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • it is not here. Repeat it again.
  • the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding procedures implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application, for the sake of brevity , I won’t repeat it here.
  • the embodiment of the application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program is run on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application.
  • the computer program runs on the computer, the computer can execute the corresponding methods implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请实施例提供一种参数配置方法及装置、网络设备，该方法包括：目标基站配置终端的移动性控制参数；所述目标基站将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。

Description

一种参数配置方法及装置、网络设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种参数配置方法及装置、网络设备。
背景技术
无线接入网络通知区域(Radio Access Network Notification Area，RNA)是指用于控制终端在非激活(inactive)状态下进行小区选择重选的区域，也是无线接入网络(Radio Access Network，RAN)初始寻呼的寻呼范围区域。触发终端执行RNA更新(RAN Notification Area Update，RNAU)的场景有RNAU定时器超时或者终端移动到RNA之外的区域。
如果终端执行了一个RNAU(或者周期性RAN位置更新)，则锚(anchor)基站可能决定不迁移终端上下文到目标基站，而是anchor基站生成无线资源控制(Radio Resource Control，RRC)释放消息，并将该RRC释放消息的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)分组数据单元(Packet Data Unit，PDU)发送给目标基站，由目标基站将RRC释放消息发送给终端，使得终端完成RAN位置更新过程。目前，RRC释放消息中可以给终端配置一些终端专用的信息，如移动性控制参数，这些参数一般由网络根据自己周边网络的拓扑和部署以及网络负荷等情况来配置。在终端上下文不迁移的情况下，这些参数由anchor基站给出，而此时终端离anchor基站可能距离很远，anchor基站并不了解此时UE所处的网络部署和拓扑以及网络负荷等情况，所以anchor基站配置这些参数没有指导意义。
发明内容
本申请实施例提供一种参数配置方法及装置、网络设备。
本申请实施例提供的参数配置方法，包括：
目标基站配置终端的移动性控制参数；
所述目标基站将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
本申请实施例提供的参数配置方法，包括：
锚基站接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站；
所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
本申请实施例提供的参数配置装置，应用于目标基站，所述装置包括：
配置单元，用于配置终端的移动性控制参数；
发送单元，用于将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
本申请实施例提供的参数配置装置，应用于锚基站，所述装置包括：
第一接收单元，用于接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站；
第一发送单元，用于所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
本申请实施例提供的网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的参数配置方法。
本申请实施例提供的芯片，用于实现上述的参数配置方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的参数配置方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的参数配置方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的参数配置方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的参数配置方法。
通过上述技术方案，在RNAU(或者称为周期性RAN位置更新)过程中，因为目标基站距离终端较近，由目标基站配置终端的移动性控制参数，可以辅助锚基站配置终端的移动性控制参数的配置信息，使得针对终端的移动性控制参数合理且有效；或者，目标基站直接为终端配置移动性控制参数的配置信息，使得针对终端的移动性控制参数合理且有效。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的一种通信系统架构的示意性图；
图2为本申请实施例提供的RRC状态转换的示意图；
图3为本申请实施例提供的UE处于RRC_INACTIVE状态下的RNA的示意；
图4为本申请实施例提供的参数配置方法的流程示意图一；
图5(a)为本申请实施例提供的有上下文迁移的RNAU的流程示意图；
图5(b)为本申请实施例提供的没有上下文迁移的RNAU的流程示意图；
图6为本申请实施例提供的有上下文迁移的RNAU的流程示意图；
图7为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图一；
图8为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图二；
图9为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图三；
图10为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图四；
图11为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图五；
图12为本申请实施例提供的参数配置方法的流程示意图二；
图13为本申请实施例提供的参数配置装置的结构组成示意图一；
图14为本申请实施例提供的参数配置装置的结构组成示意图二；
图15为本申请实施例提供的一种通信设备示意性结构图；
图16为本申请实施例的芯片的示意性结构图；
图17为本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫 星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地，终端120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端120，网络设备110和终端120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技术与本申请实施例的技术方案的任意结合均属于本申请实施例的保护范围。
5G为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定义了一个新的RRC状态，即RRC非激活(RRC_INACTIVE)状态。这种状态有别于RRC空闲(RRC_IDLE)状态和RRC激活(RRC_ACTIVE)状态。其中，
1)RRC_IDLE状态(简称为空闲(idle)状态)：移动性为基于UE的小区选择重选，寻呼由核心网(Core Network，CN)发起，寻呼区域由CN配置。基站侧不存在UE上下文，不存在RRC连接。
2)RRC_CONNECTED状态(简称为连接(connected)状态)：存在RRC连接，基站侧和UE侧存在UE上下文。网络侧知道UE的位置是具体小区级别的。移动性是网络侧控制的移动性。UE和基站之间可以传输单播数据。
3)RRC_INACTIVE状态(简称为非激活(inactive)状态)：移动性为基于UE的小区选择重选，存在CN-NR之间的连接，UE上下文存在某个基站上，寻呼由RAN触发，基于RAN的寻呼区域由RAN管理，网络侧知道UE的位置是基于RAN的寻呼区域级别的。
网络侧可以控制UE的RRC状态转换，如图2所示，具体地：
1)RRC_CONNECTED状态与RRC_INACTIVE状态
一方面，网络侧可以通过释放并悬挂RRC连接控制UE从RRC_CONNECTED状态转换到RRC_INACTIVE状态；
另一方面，网络侧可以通过恢复RRC连接控制UE从RRC_INACTIVE状态转换到RRC_CONNECTED状态。
2)RRC_CONNECTED状态与RRC_IDLE状态
一方面，网络侧可以通过释放RRC连接控制UE从RRC_CONNECTED状态转换到RRC_IDLE状态；
另一方面，网络侧可以通过建立RRC连接控制UE从RRC_IDLE状态转换到RRC_CONNECTED状态。
3)RRC_INACTIVE状态与RRC_IDLE状态
网络侧可以通过释放RRC连接控制UE从RRC_INACTIVE状态转换到RRC_IDLE状态。
UE处于RRC_INACTIVE状态的情况下，可以通过以下事件中的任意一种事件可以触发UE自主回到RRC_IDLE状态：
-接收到CN初始的寻呼消息；
-发起RRC恢复请求时，启动定时器T319，如果定时器T319超时超；
-MSG4完整性保护验证失败；
-小区重选到其他无线接入技术(Radio Access Technology，RAT)；
-进入驻留到任意小区(camp on any cell)的状态。
UE处于RRC_INACTIVE状态的情况下，具有如下特征：
-RAN和CN之间的连接是保持的；
-UE和至少一个基站保存AS上下文；
-UE对于RAN侧来说是可达的，相关参数由RAN配置；
-当UE在RAN配置的RNA内移动时不需要通知网络侧，但当移动出RNA时需要通知网络侧；
-UE在RNA内移动按照小区选择重选方式。
当UE处于RRC_INACTIVE状态，网络侧会通过RRC释放(RRCRelease)专用信令给UE配置RRC_INACTIVE状态的参数，主要参数包括：I-RNTI，用于标识UE在基站侧的inactive状态对应的上下文，I-RNTI在基站内唯一。RNA，用于控制UE在inactive状态下进行小区选择重选的区域，也是RAN初始寻呼的寻呼范围区域。RAN非连续接收周期(RAN DRX cycle)，用于计算RAN初始寻呼的寻呼时机。RNAU周期(RNAU periodicity)，用于控制UE执行周期性RAN位置更新的周期。NCC，用于RRC连接恢复过程中使用的秘钥。
图3为UE处于RRC_INACTIVE状态下的RNA的示意图，基站1至基站5覆盖的小区范围为RNA，当UE在RNA内移动时不用通知网络侧，遵循idle状态下移动性行为，即小区选择重选原则。当UE移动出RAN配置的寻呼区域时，会触发UE恢复RRC连接并重新获取RAN配置的寻呼区域。当UE有下行数据到达时，为UE保持RAN和CN之间连接的gNB会触发RAN寻呼区域内的所有小区发送寻呼消息给UE，使得inactive状态的UE能够恢复RRC连接，进行数据接收。处于inactive状态的UE，配置了RAN寻呼区域，在该区域内为了保证UE的可达性，UE需要按照网络配置的周期进行周期性位置更新。所以触发UE执行RNA更新的场景有RNAU定时器超时或者UE移动到RNA之外的区域。
对于inactive状态的UE，同时接收CN初始的寻呼和RAN初始的寻呼。处于inactive状态的UE，保持RAN和CN之间的连接，当有下行数据达到时则会触发RAN发起RAN初始的寻呼来通知UE恢复RRC连接以便接收下行数据。RAN初始的寻呼消息和CN初始的寻呼消息一样，但在计算寻呼时间采用的DRX不同。
图4为本申请实施例提供的参数配置方法的流程示意图一，如图4所示，所述参数配置方法包括以下步骤：
步骤401：目标基站配置终端的移动性控制参数。
本申请实施例应用于RRC恢复过程，涉及到RRC恢复过程的场景包括但不局限于RNAU场景，终端从非激活状态进入连接状态的场景。
1)RNAU场景
触发终端执行RNAU的事件有RNAU定时器超时或者终端移动到RNA之外的区域。以下对RNAU的流程进行说明。
图5(a)为有上下文迁移的RNAU的流程示意图，如图5(a)所示，包括如下流程：
1、终端向目标基站发送RRC恢复请求消息。
这里，RRC恢复请求消息可以携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
2、目标基站向锚基站发送索要终端上下文请求消息。
这里，锚基站是指最后一个服务终端的基站，该基站保存有终端的上下文。
3、锚基站向目标基站发送索要终端上下文响应消息。
这里，索要终端上下文响应消息携带终端的上下文。
4、目标基站控制终端处于非激活状态。
5、目标基站向锚基站发送数据转发地址指示信息。
6、目标基站向接入和移动性管理实体(Access and Mobility Management Function，AMF)发送路径切换请求消息。
7、AMF向目标基站发送路径切换响应消息。
8、目标基站向终端发送RRC释放消息。
这里，该RRC释放消息携带悬挂指示信息。
9、目标基站向锚基站发送终端上下文释放消息。
图5(b)为没有上下文迁移的RNAU的流程示意图，如图5(b)所示，包括如下流程：
1、终端向目标基站发送RRC恢复请求消息。
这里，RRC恢复请求消息可以携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
2、目标基站向锚基站发送索要终端上下文请求消息。
这里，锚基站是指最后一个服务终端的基站，该基站保存有终端的上下文。
3、锚基站向目标基站发送索要终端上下文失败消息。
4、目标基站向终端发送RRC释放消息。
这里，该RRC释放消息携带悬挂指示信息。
2)终端从非激活状态进入连接状态的场景
触发终端从非激活状态进入连接状态的事件有：I)终端有下行数据到达，网络侧发起RAN初始的寻呼，促使终端进入连接状态；II)终端自身发起RAN位置区域更新，例如周期性RAN位置更新或者跨区域位置更；III)终端有上行数据发送需求，促使终端进入连接状态。以下对终端从非激活状态进入连接状态的流程进行说明。
图6为有上下文迁移的RNAU的流程示意图，如图6所示，包括如下流程：
1、终端向目标基站发送RRC恢复请求消息。
2、目标基站向锚基站发送索要终端上下文请求消息。
这里，锚基站是指最后一个服务终端的基站，该基站保存有终端的上下文。
3、锚基站向目标基站发送索要终端上下文响应消息。
这里，索要终端上下文响应消息携带终端的上下文。
4、目标基站向终端发送RRC恢复消息。
5、终端向目标基站发送RRC恢复完成消息。
6、目标基站向锚基站发送数据转发地址指示信息。
7、目标基站向AMF发送路径切换请求消息。
8、AMF向目标基站发送路径切换响应消息。
9、目标基站向锚基站发送终端上下文释放消息。
本申请实施例中，目标基站和锚基站的类型不做限制，在一个例子中，目标基站和锚基站属于相同类型的基站，例如目标基站和锚基站都是NR基站(gNB)。在另一个例子中，目标基站和锚基站属于不同类型的基站，例如目标基站是NR基站(gNB)，锚基站是LTE基站(eNB)。
本申请实施例中，目标基站是指上述RRC恢复过程中为终端提供服务的新基站，锚基站是指上述RRC恢复过程中上一次为终端提供服务的原基站。
对于RNAU场景下的RRC恢复过程，当终端发起RRC连接恢复过程的目标基站不是锚基站(即目标基站和锚基站是不同的基站)，则锚基站需要判决是否需要转移终端的上下文到目标基站侧。所以目标基站会将终端发送的RRC恢复请求消息中携带的第一原因值在终端上下文索要过程中发送给锚基站，锚基站判决是否需要转移终端的上下文到目标基站侧。
本申请实施例在RRC恢复过程中，由目标基站配置终端的移动性控制参数。
步骤402：所述目标基站将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
在一实施方式中，所述目标基站将所述终端的移动性控制参数发送给锚基站，从而辅助锚基站配置所述终端的移动性控制参数；或者，所述目标基站直接为终端配置所述终端的移动性控制参数。最后，将所述终端的移动性控制参数通过RRC释放消息下发给所述终端。这里，所述终端的移动性控制参数具体是指所述终端进入空闲状态或非激活状态后的移动性控制参数。这里，所述终端的移动性控制参数包括以下至少之一：
第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
举个例子：第一参数为redirectedCarrierInfo，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；第二参数为cellReselectionPriorities，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；第三参数为deprioritisationReq，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
Figure PCTCN2019073525-appb-000001
Figure PCTCN2019073525-appb-000002
表1
以下结合具体的RRC恢复过程对网络侧如何配置终端的移动性控制参数行详细说明。
应用示例一
参照图7，图7为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图一，如图7所示，该流程包括以下步骤：
1、目标基站接收终端发送的RRC恢复请求消息。
这里，终端发送RRC恢复请求(RRCResumeRequest)消息给目标基站，触发RRC连接恢复过程。
2、目标基站确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
可选地，所述RRC恢复请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
基于此，所述目标基站基于所述RRC恢复请求消息中的所述第一原因值(该第一原因值表明RRC连接恢复过程的触发原因是RNAU)，确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
3、目标基站向锚基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，所述索要终端上下文请求消息携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
4、锚基站决定不迁移所述终端的上下文的情况下，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU(RRCRelease PDCP PDU)。
5、目标基站接收所述锚基站发送的索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
6、所述目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
应用示例二
参照图8，图8为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图二，如图8所示，该流程包括以下步骤：
1、目标基站接收终端发送的RRC恢复请求消息。
这里，终端发送RRC恢复请求(RRCResumeRequest)消息给目标基站，触发RRC连接恢复过程。
2、目标基站确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
可选地，所述RRC恢复请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
基于此，所述目标基站基于所述RRC恢复请求消息中的所述第一原因值(该第一原因值表明 RRC连接恢复过程的触发原因是RNAU)，确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
3、目标基站向锚基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，所述索要终端上下文请求消息携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
4、锚基站决定迁移所述终端的上下文的情况下，忽略来自所述目标基站配置的所述终端的移动性控制参数的配置信息。
5、目标基站接收所述锚基站发送的索要终端上下文响应(RETRIEVE UE CONTEXT RESPONSE)消息，所述索要终端上下文响应消息携带所述终端的上下文。
6、所述目标基站向所述终端发送自己生成的RRC释放消息。
可选地，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
应用示例三
参照图9，图9为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图三，如图9所示，该流程包括以下步骤：
1、目标基站接收终端发送的RRC恢复请求消息。
这里，终端发送RRC恢复请求(RRCResumeRequest)消息给目标基站，触发RRC连接恢复过程。
2、目标基站向所述锚基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
可选地，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
3、锚基站决定不迁移所述终端的上下文。
4、目标基站接收所述锚基站发送的索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文。
这里，锚基站根据第一指示信息和不迁移所述终端的上下文的决定，或者仅根据不迁移所述终端的上下文的决定，就向锚基站发送索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文。
5、所述目标基站向所述锚基站发送所述终端的移动性控制参数。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
6、目标基站接收所述锚基站发送的索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信 息或者RAT信息。表1给出了这三个参数的配置信息。
7、目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
应用示例四
参照图10，图10为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图四，如图10所示，该流程包括以下步骤：
1、目标基站接收终端发送的RRC恢复请求消息。
这里，终端发送RRC恢复请求(RRCResumeRequest)消息给目标基站，触发RRC连接恢复过程。
可选地，所述RRC恢复请求消息还携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
2、如果目标基站配置有终端的移动性控制参数，则目标基站决定需要指示锚基站需要进行所述终端的上下文迁移。
进一步，如果目标基站配置有终端的移动性控制参数，且RRC连接恢复过程的触发原因是RNAU，则目标基站决定需要指示锚基站需要进行所述终端的上下文迁移。
3、目标基站向所述锚基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
可选地，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移或者用于指示目标基站有配置给所述终端的移动性控制参数。
这里，所述第二指示信息和所述第一原因值用于所述锚基站决定是否迁移所述终端的上下文。
4、锚基站根据所述第二指示信息和所述第一原因值决定是否迁移所述终端的上下文。
具体地，锚基站根据目标基站的第二指示信息以及终端发起RRC恢复过程的原因值(如RNAU)，共同决定是否迁移终端的上下文。
5、目标基站接收所述锚基站发送的索要终端上下文响应(RETRIEVE UE CONTEXT RESPONSE)消息，所述终端上下文响应消息携带所述终端的上下文。
这里，所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
6、目标基站向所述终端发送自己生成的RRC释放消息。
可选地，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
这里，所述终端的移动性控制参数的包括以下至少之一：
第一参数(如redirectedCarrierInfo)，指示UE进入idle状态或者inactive状态后优先选择的频点信和RAT信息；
第二参数(如cellReselectionPriorities)，指示UE进入idle状态或者inactive状态后执行小区选择重选的频率优先级配置参数；
第三参数(如deprioritisationReq)，指示UE进入idle状态或者inactive状态后低优先级频率信息或者RAT信息。表1给出了这三个参数的配置信息。
应用示例五
参照图11，图11为本申请实施例提供的RRC恢复过程中配置终端的移动性控制参数的流程示意图五，如图11所示，该流程包括以下步骤：
1、目标基站接收终端发送的RRC恢复请求消息。
这里，终端发送RRC恢复请求(RRCResumeRequest)消息给目标基站，触发RRC连接恢复过程。
可选地，所述RRC恢复请求消息还携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
2、目标基站向所述锚基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
锚基站根据所述第一原因值决定不迁移所述终端的上下文。
这里，锚基站决定不迁移所述终端的上下文，则锚基站在RRC释放(RRCRelease)消息中不配置终端的移动性控制参数。
3、目标基站接收所述锚基站发送的索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息。
4、目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息不携带所述终端的移动性控制参数的配置信息。
图12为本申请实施例提供的参数配置方法的流程示意图二，需要说明的是，本示例中的方案应用于锚基站侧，本示例中的方法可以结合前述目标基站侧的方法进行理解，如图12所示，所述参数配置方法包括以下步骤：
步骤1201：锚基站接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站。
本申请实施例中，目标基站侧配置有终端的移动性控制参数，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息。其中，所述终端的移动性控制参数包括以下至少之一：
第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
如图8和图9中的步骤3所示，锚基站接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
如图10中的步骤2所示，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。可选地，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
如图11中的步骤3所示，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。可选地，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移。
步骤1202：所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
本申请实施例中，所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。其中，索要终端上下文失败消息中可以携带终端的移动性控制参数，如此，可以将该终端的移动性控制参数下发给终端。
参照图7，图7中的步骤4中，锚基站决定不迁移所述终端的上下文的情况下，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU(RRCRelease PDCP PDU)。图7中的步骤5中，所述锚基站向所述目标基站发送索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
参照图8，图8中的步骤4中，锚基站决定迁移所述终端的上下文的情况下，忽略来自所述目标基站配置的所述终端的移动性控制参数的配置信息。图8中的步骤5中，锚基站向所述目标基站发送索要终端上下文响应(RETRIEVE UE CONTEXT RESPONSE)消息，所述索要终端上下文响应消息携带所述终端的上下文。
参照图9，图9中的步骤2中，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。可选地，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。图9中的步骤4中，锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文。图9中的步骤5中，所述锚基站接收所述目标基站发送的所述终端的移动性控制参数；将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU。图9中的步骤6中，锚基站向所述目标基站发送索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
参照图10，图10中的步骤2中，所述索要终端上下文请求消息携带第一原因值，所述第一原 因值用于表明RRC连接恢复过程的触发原因是RNAU。可选地，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移。图10中的步骤4中，锚基站根据所述第二指示信息和所述第一原因值决定是否迁移所述终端的上下文。图10中的步骤5中，锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要终端上下文响应(RETRIEVE UE CONTEXT RESPONSE)消息，所述索要终端上下文响应消息携带所述终端的上下文。
参照图11，图11中的步骤3中，锚基站根据所述第一原因值决定不迁移所述终端的上下文。这里，锚基站决定不迁移所述终端的上下文，则锚基站在RRC释放(RRCRelease)消息中不配置终端的移动性控制参数。图11中的步骤4中，锚基站决定不迁移所述终端的上下文的情况下，所述锚基站向所述目标基站索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息。
图13为本申请实施例提供的参数配置装置的结构组成示意图一，该装置应用于目标基站，如图13所示，所述装置包括：
配置单元1301，用于配置终端的移动性控制参数；
发送单元1302，用于将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
在一实施方式中，所述装置还包括：
第一接收单元1303，用于接收终端发送的RRC恢复请求消息；
确定单元1304，用于确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站；
所述发送单元1302，用于向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述RRC恢复请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU；
所述确定单元1304，用于基于所述RRC恢复请求消息中的所述第一原因值，确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
在一实施方式中，所述锚基站决定不迁移所述终端的上下文的情况下，所述装置还包括：
第二接收单元1305，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
所述发送单元1302，用于根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述锚基站决定迁移所述终端的上下文的情况下，所述装置还包括：
第二接收单元1305，用于接收所述锚基站发送的索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文；
所述发送单元1302，还用于向所述终端发送自己生成的RRC释放消息。
在一实施方式中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述装置还包括：
第一接收单元1303，用于接收终端发送的RRC恢复请求消息；
所述发送单元1302，还用于向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
在一实施方式中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
在一实施方式中，所述锚基站决定不迁移所述终端的上下文的情况下，所述装置还包括：
第三接收单元1306，用于接收所述锚基站发送的索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
所述发送单元1302，用于向所述锚基站发送所述终端的移动性控制参数；
第二接收单元1305，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
所述发送单元1302，用于向根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；
所述第二指示信息和所述第一原因值用于所述锚基站决定是否迁移所述终端的上下文。
在一实施方式中，所述锚基站决定迁移所述终端的上下文的情况下，所述装置还包括：
第二接收单元1305，用于接收所述锚基站发送的索要终端上下文响应消息，所述终端上下文 响应消息携带所述终端的上下文；
所述发送单元，用于向所述终端发送自己生成的RRC释放消息。
在一实施方式中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述锚基站决定不迁移所述终端的上下文的情况下，所述装置还包括：
第二接收单元1305，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息；
所述发送单元1302，用于根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，
所述RRC释放消息不携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述终端的移动性控制参数包括以下至少之一：
第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
本领域技术人员应当理解，本申请实施例的上述参数配置装置的相关描述可以参照本申请实施例的参数配置方法的相关描述进行理解。
图14为本申请实施例提供的参数配置装置的结构组成示意图二，该装置应用于锚基站，如图14所示，所述装置包括：
第一接收单元1401，用于接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站；
第一发送单元1402，用于所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
在一实施方式中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
所述装置还包括：生成单元1403，用于所述锚基站决定不迁移所述终端的上下文的情况下，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
所述第一发送单元1402，用于向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
所述第一发送单元1402，用于所述锚基站决定迁移所述终端的上下文的情况下，忽略来自所述目标基站配置的所述终端的移动性控制参数的配置信息；向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
在一实施方式中，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
在一实施方式中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
在一实施方式中，所述装置还包括：
第二发送单元1404，用于所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
第二接收单元1405，用于接收所述目标基站发送的所述终端的移动性控制参数；
生成单元1403，用于将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
所述第一发送单元1402，用于向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；所述装置还包括：
确定单元1406，用于根据所述第二指示信息和所述第一原因值决定是否迁移所述终端的上下文；
所述第一发送单元1402，用于所述锚基站决定迁移所述终端的上下文的情况下，向所述目标 基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
在一实施方式中，所述锚基站决定不迁移所述终端的上下文的情况下，所述第一发送单元，用于向所述目标基站索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息。
在一实施方式中，所述终端的移动性控制参数包括以下至少之一：
第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
本领域技术人员应当理解，本申请实施例的上述参数配置装置的相关描述可以参照本申请实施例的参数配置方法的相关描述进行理解。
图15是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是网络设备，如目标基站或者锚基站，图15所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图15所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图15所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
图16是本申请实施例的芯片的示意性结构图。图16所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图16所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图17是本申请实施例提供的一种通信系统900的示意性框图。如图17所示，该通信系统900包括终端910和网络设备920。
其中，该终端910可以用于实现上述方法中由终端实现的相应的功能，以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性 和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (51)

  1. 一种参数配置方法，所述方法包括：
    目标基站配置终端的移动性控制参数；
    所述目标基站将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述目标基站接收终端发送的无线资源控制RRC恢复请求消息；
    所述目标基站确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站的情况下，向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带所述终端的移动性控制参数的配置信息。
  3. 根据权利要求2所述的方法，其中，所述RRC恢复请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RAN通知区域更新RNAU；所述方法还包括：
    所述目标基站基于所述RRC恢复请求消息中的所述第一原因值，确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
  4. 根据权利要求2或3所述的方法，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述方法还包括：
    所述目标基站接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
    所述目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  5. 根据权利要求2或3所述的方法，其中，所述锚基站决定迁移所述终端的上下文的情况下，所述方法还包括：
    所述目标基站接收所述锚基站发送的索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文；
    所述目标基站向所述终端发送自己生成的RRC释放消息。
  6. 根据权利要求5所述的方法，其中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  7. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述目标基站接收终端发送的RRC恢复请求消息；
    所述目标基站向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
  8. 根据权利要求7所述的方法，其中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
  9. 根据权利要求7或8所述的方法，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述方法还包括：
    所述目标基站接收所述锚基站发送的索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
    所述目标基站向所述锚基站发送所述终端的移动性控制参数；
    所述目标基站接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
    所述目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  10. 根据权利要求7所述的方法，其中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；
    所述第二指示信息和所述第一原因值用于所述锚基站决定是否迁移所述终端的上下文。
  11. 根据权利要求10所述的方法，其中，所述锚基站决定迁移所述终端的上下文的情况下，所述方法还包括：
    所述目标基站接收所述锚基站发送的索要终端上下文响应消息，所述终端上下文响应消息携带所述终端的上下文；
    所述目标基站向所述终端发送自己生成的RRC释放消息。
  12. 根据权利要求11所述的方法，其中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  13. 根据权利要求7所述的方法，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述方法还包括：
    所述目标基站接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息；
    所述目标基站接收到所述RRC释放PDCP PDU后，根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息不携带所述终端的移动性控制参数的配置信息。
  14. 根据权利要求1至13任一项所述的方法，其中，所述终端的移动性控制参数包括以下至少之一：
    第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
    第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
    第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
  15. 一种参数配置方法，所述方法包括：
    锚基站接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站；
    所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  16. 根据权利要求15所述的方法，其中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
    所述锚基站决定不迁移所述终端的上下文的情况下，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
    所述锚基站向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
  17. 根据权利要求15所述的方法，其中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
    所述锚基站决定迁移所述终端的上下文的情况下，忽略来自所述目标基站配置的所述终端的移动性控制参数的配置信息；
    所述锚基站向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  18. 根据权利要求15所述的方法，其中，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
  19. 根据权利要求18所述的方法，其中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
  20. 根据权利要求18或19所述的方法，其中，
    所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
    所述锚基站接收所述目标基站发送的所述终端的移动性控制参数，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
    所述锚基站向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
  21. 根据权利要求18所述的方法，其中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；
    所述锚基站根据所述第二指示信息和所述第一原因值决定是否迁移所述终端的上下文；
    所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  22. 根据权利要求15所述的方法，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述锚基站向所述目标基站索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息。
  23. 根据权利要求16至22任一项所述的方法，其中，所述终端的移动性控制参数包括以下至少之一：
    第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
    第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
    第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
  24. 一种参数配置装置，应用于目标基站，所述装置包括：
    配置单元，用于配置终端的移动性控制参数；
    发送单元，用于将所述终端的移动性控制参数发送给锚基站或者发送给所述终端，其中，所述锚基站是指保存所述终端的上下文的基站。
  25. 根据权利要求24所述的装置，其中，所述装置还包括：
    第一接收单元，用于接收终端发送的RRC恢复请求消息；
    确定单元，用于确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站；
    所述发送单元，用于向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带所述终端的移动性控制参数的配置信息。
  26. 根据权利要求25所述的装置，其中，所述RRC恢复请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU；
    所述确定单元，用于基于所述RRC恢复请求消息中的所述第一原因值，确定需要将所述终端的移动性控制参数的配置信息指示给所述锚基站。
  27. 根据权利要求25或26所述的装置，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述装置还包括：
    第二接收单元，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
    所述发送单元，用于根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  28. 根据权利要求25或26所述的装置，其中，所述锚基站决定迁移所述终端的上下文的情况下，所述装置还包括：
    第二接收单元，用于接收所述锚基站发送的索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文；
    所述发送单元，还用于向所述终端发送自己生成的RRC释放消息。
  29. 根据权利要求28所述的装置，其中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  30. 根据权利要求24所述的装置，其中，所述装置还包括：
    第一接收单元，用于接收终端发送的RRC恢复请求消息；
    所述发送单元，还用于向所述锚基站发送索要终端上下文请求消息，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
  31. 根据权利要求30所述的装置，其中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
  32. 根据权利要求30或31所述的装置，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述装置还包括：
    第三接收单元，用于接收所述锚基站发送的索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
    所述发送单元，用于向所述锚基站发送所述终端的移动性控制参数；
    第二接收单元，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息；
    所述发送单元，用于向根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  33. 根据权利要求30所述的装置，其中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；
    所述第二指示信息和所述第一原因值用于所述锚基站决定是否迁移所述终端的上下文。
  34. 根据权利要求33所述的装置，其中，所述锚基站决定迁移所述终端的上下文的情况下，所述装置还包括：
    第二接收单元，用于接收所述锚基站发送的索要终端上下文响应消息，所述终端上下文响应消息携带所述终端的上下文；
    所述发送单元，用于向所述终端发送自己生成的RRC释放消息。
  35. 根据权利要求34所述的装置，其中，所述目标基站自己生成的所述RRC释放消息携带所述终端的移动性控制参数的配置信息。
  36. 根据权利要求30所述的装置，其中，所述锚基站决定不迁移所述终端的上下文的情况 下，所述装置还包括：
    第二接收单元，用于接收所述锚基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息；
    所述发送单元，用于根据所述RRC释放PDCP PDU向所述终端发送RRC释放消息，所述RRC释放消息不携带所述终端的移动性控制参数的配置信息。
  37. 根据权利要求24至36任一项所述的装置，其中，所述终端的移动性控制参数包括以下至少之一：
    第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
    第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
    第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
  38. 一种参数配置装置，应用于锚基站，所述装置包括：
    第一接收单元，用于接收目标基站发送的索要终端上下文请求消息，所述索要终端上下文请求消息携带目标信息，其中，所述锚基站是指保存所述终端的上下文的基站；
    第一发送单元，用于所述锚基站决定不迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文失败消息；所述锚基站决定迁移终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  39. 根据权利要求38所述的装置，其中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
    所述装置还包括：生成单元，用于所述锚基站决定不迁移所述终端的上下文的情况下，将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
    所述第一发送单元，用于向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
  40. 根据权利要求38所述的装置，其中，所述索要终端上下文请求消息携带所述目标基站配置的所述终端的移动性控制参数的配置信息；
    所述第一发送单元，用于所述锚基站决定迁移所述终端的上下文的情况下，忽略来自所述目标基站配置的所述终端的移动性控制参数的配置信息；向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  41. 根据权利要求38所述的装置，其中，所述索要终端上下文请求消息携带第一原因值，所述第一原因值用于表明RRC连接恢复过程的触发原因是RNAU。
  42. 根据权利要求41所述的装置，其中，所述索要终端上下文请求消息还携带第一指示信息，所述第一指示信息用于指示所述目标基站存在需要配置给所述终端的移动性控制参数。
  43. 根据权利要求41或42所述的装置，其中，所述装置还包括：
    第二发送单元，用于所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要移动性控制参数消息或者第二指示信息，所述第二指示信息用于指示所述锚基站不迁移所述终端的上下文；
    第二接收单元，用于接收所述目标基站发送的所述终端的移动性控制参数；
    生成单元，用于将来自所述目标基站配置的所述终端的移动性控制参数的配置信息携带在RRC释放消息中，并生成所述RRC释放消息的RRC释放PDCP PDU；
    所述第一发送单元，用于向所述目标基站发送索要终端上下文失败消息，所述索要终端上下文失败消息携带所述RRC释放PDCP PDU，所述RRC释放PDCP PDU携带所述终端的移动性控制参数的配置信息。
  44. 根据权利要求41所述的装置，其中，所述索要终端上下文请求消息还携带第二指示信息，所述第二指示信息用于指示所述锚基站需要进行所述终端的上下文迁移；所述装置还包括：
    确定单元，用于根据所述第二指示信息和所述第一原因值决定是否迁移所述终端的上下文；
    所述第一发送单元，用于所述锚基站决定迁移所述终端的上下文的情况下，向所述目标基站发送索要终端上下文响应消息，所述索要终端上下文响应消息携带所述终端的上下文。
  45. 根据权利要求38所述的装置，其中，所述锚基站决定不迁移所述终端的上下文的情况下，所述第一发送单元，用于向所述目标基站索要终端上下文失败消息，所述索要终端上下文失败消息携带RRC释放PDCP PDU，所述RRC释放PDCP PDU不携带所述终端的移动性控制参数的配置信息。
  46. 根据权利要求39至45任一项所述的装置，其中，所述终端的移动性控制参数包括以下至少之一：
    第一参数，所述第一参数用于指示所述终端进入空闲状态或者非激活状态后优先选择的频点信息和RAT信息；
    第二参数，所述第二参数用于指示所述终端进入空闲状态或者非激活状态后执行小区选择重选的频率优先级信息；
    第三参数，所述第三参数用于指示所述终端进入空闲状态或者非激活状态后低优先级的频率信息或者RAT信息。
  47. 一种网络设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至14中任一项所述的方法，或者如权利要求15至23中任一项所述的方法。
  48. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的方法，或者如权利要求15至23中任一项所述的方法。
  49. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法，或者如权利要求15至23中任一项所述的方法。
  50. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至14中任一项所述的方法，或者如权利要求15至23中任一项所述的方法。
  51. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法，或者如权利要求15至23中任一项所述的方法。
PCT/CN2019/073525 2019-01-28 2019-01-28 一种参数配置方法及装置、网络设备 WO2020154868A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2019/073525 WO2020154868A1 (zh) 2019-01-28 2019-01-28 一种参数配置方法及装置、网络设备
CN201980060415.9A CN112715038B (zh) 2019-01-28 2019-11-04 一种参数配置方法及装置、网络设备
PCT/CN2019/115422 WO2020155725A1 (zh) 2019-01-28 2019-11-04 一种参数配置方法及装置、网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/073525 WO2020154868A1 (zh) 2019-01-28 2019-01-28 一种参数配置方法及装置、网络设备

Publications (1)

Publication Number Publication Date
WO2020154868A1 true WO2020154868A1 (zh) 2020-08-06

Family

ID=71839897

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2019/073525 WO2020154868A1 (zh) 2019-01-28 2019-01-28 一种参数配置方法及装置、网络设备
PCT/CN2019/115422 WO2020155725A1 (zh) 2019-01-28 2019-11-04 一种参数配置方法及装置、网络设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/115422 WO2020155725A1 (zh) 2019-01-28 2019-11-04 一种参数配置方法及装置、网络设备

Country Status (2)

Country Link
CN (1) CN112715038B (zh)
WO (2) WO2020154868A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024020966A1 (zh) * 2022-07-28 2024-02-01 北京小米移动软件有限公司 移动性配置方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378802A (zh) * 2013-08-12 2015-02-25 中兴通讯股份有限公司 驻留小区处理方法、装置、终端及基站
CN105814967A (zh) * 2014-10-28 2016-07-27 联发科技股份有限公司 用户设备及其电路域回落的方法
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备
CN108366389A (zh) * 2018-05-24 2018-08-03 南京邮电大学 Lte网络中基于有效带宽和信号质量的自适应切换方法
CN108696910A (zh) * 2017-04-11 2018-10-23 华为技术有限公司 一种选择目标基站的方法、装置和存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7693517B2 (en) * 2004-08-10 2010-04-06 Nextel Communications Inc. System and method for handoff between base stations
CN102056260B (zh) * 2009-10-28 2014-12-10 中兴通讯股份有限公司 一种移动性参数的查询及协商方法/系统
JP6561376B2 (ja) * 2015-09-02 2019-08-21 パナソニックＩｐマネジメント株式会社 基地局装置および通信方法
WO2018014154A1 (zh) * 2016-07-18 2018-01-25 华为技术有限公司 一种rrc连接重建方法和装置
CN113163459B (zh) * 2017-04-04 2024-04-09 华为技术有限公司 通信方法及通信设备
CN108541032B (zh) * 2017-09-22 2022-04-29 中兴通讯股份有限公司 无线基站分离架构下的通信方法、功能实体及无线基站

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378802A (zh) * 2013-08-12 2015-02-25 中兴通讯股份有限公司 驻留小区处理方法、装置、终端及基站
CN105814967A (zh) * 2014-10-28 2016-07-27 联发科技股份有限公司 用户设备及其电路域回落的方法
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备
CN108696910A (zh) * 2017-04-11 2018-10-23 华为技术有限公司 一种选择目标基站的方法、装置和存储介质
CN108366389A (zh) * 2018-05-24 2018-08-03 南京邮电大学 Lte网络中基于有效带宽和信号质量的自适应切换方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.300, vol. RAN WG2, no. V15.4.0, 30 December 2018 (2018-12-30), pages 1 - 97, XP051591684 *
HUAWEI ET AL.: "CR on resumeMAC-I calculation for RNA update without context relocation", R2-1814134; 3GPP TSG-RAN WG2 MEETING #103BIS, vol. RAN WG2, no. Chengdu, China; 20181008 - 20181012, 8 October 2018 (2018-10-08) - 12 October 2018 (2018-10-12), pages 1 - 9, XP051523593 *
INTEL CORP.: "Open issues on RRC connection release message", 3GPP DRAFT; R2-1809795-RRC-RELEASE, vol. RAN WG2, no. Montreal, Canada; 20180702 - 20180706, 6 July 2018 (2018-07-06), pages 1 - 8, XP051525634 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024020966A1 (zh) * 2022-07-28 2024-02-01 北京小米移动软件有限公司 移动性配置方法及装置

Also Published As

Publication number Publication date
CN112715038B (zh) 2023-05-09
CN112715038A (zh) 2021-04-27
WO2020155725A1 (zh) 2020-08-06

Similar Documents

Publication Publication Date Title
US20200351977A1 (en) Information transmission method and apparatus, and communication device
WO2021203310A1 (zh) 一种数据传输方法及装置、终端设备
WO2020154869A1 (zh) 无线通信方法、终端设备和网络设备
WO2021000331A1 (zh) 一种数据传输方法及装置、通信设备
WO2021003612A1 (zh) 一种移动性管理方法及装置、终端
WO2020223978A1 (zh) 无线通信方法、网络设备和终端设备
TW202025696A (zh) 一種控制數據傳輸方法、網路設備和儲存媒介
WO2021189235A1 (zh) 一种数据传输方法及装置、通信设备
WO2020258191A1 (zh) 一种接入控制方法及装置、终端
US20220061075A1 (en) Information transmission method and apparatus, and network device
WO2021031010A1 (zh) 通信方法、终端设备和网络设备
US11805563B2 (en) Wireless communication method and base station
WO2022061872A1 (zh) 一种小数据传输方法及装置、终端设备
WO2021000320A1 (zh) 一种数据传输方法及装置、网络设备、终端
WO2020155725A1 (zh) 一种参数配置方法及装置、网络设备
WO2020258192A1 (zh) 一种数据传输方法及装置、终端
WO2021088007A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021022428A1 (zh) 无线通信的方法、终端设备和网络设备
TW202007199A (zh) 一種核心網選擇方法及裝置、終端設備、網路設備
US11653407B2 (en) Information transmission method and apparatus, and terminal and network device
WO2022021413A1 (zh) 一种密钥生成方法及装置、终端设备、网络设备
WO2021026842A1 (zh) 无线通信方法、网络设备和终端设备
WO2020252659A1 (zh) 一种数据发送方法、网络设备、终端设备
WO2020034125A1 (zh) 一种恢复rrc连接的方法及装置、终端
US20210243833A1 (en) Radio communication method, terminal device and network device

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19912461

Country of ref document: EP

Kind code of ref document: A1