CN112715038B - Parameter configuration method and device and network equipment - Google Patents

Abstract

Embodiments of the present application provide a parameter configuration method and device, and network equipment. The method includes: the target base station configures the mobility control parameters of the terminal; the target base station sends the terminal mobility control parameters to the anchor base station or to the The terminal, wherein the anchor base station refers to a base station that stores the context of the terminal.

Description

A parameter configuration method and device, and network equipment

technical field

The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a parameter configuration method and device, and network equipment.

Background technique

The radio access network notification area (Radio Access Network Notification Area, RNA) refers to the area used to control the terminal to perform cell selection and reselection in the inactive state, and is also the initial area of the radio access network (Radio Access Network, RAN). The paging range area for paging. Scenarios that trigger the terminal to perform RNA update (RANNotification Area Update, RNAU) include the RNAU timer timeout or the terminal moving to an area outside the RNA.

If the terminal performs an RNAU (or periodic RAN location update), the anchor base station may decide not to migrate the terminal context to the target base station, but the anchor base station generates a Radio Resource Control (RRC) release message and sends The packet data convergence protocol (Packet Data Convergence Protocol, PDCP) packet data unit (Packet Data Unit, PDU) of the RRC release message is sent 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. At present, some terminal-specific information can be configured for the terminal in the RRC release message, 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. When 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, 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.

Contents of the invention

Embodiments of the present application provide a parameter configuration method and device, and network equipment.

The parameter configuration method provided in the embodiment of this application includes:

The target base station configures mobility control parameters of the terminal;

The target base station sends the mobility control parameter of the terminal to an anchor base station or to the terminal, where the anchor base station refers to a base station that stores the context of the terminal.

The parameter configuration method provided in the embodiment of this application includes:

The anchor base station receives a terminal context request message sent by a target base station, where the terminal context request message carries target information, where the anchor base station refers to a base station that stores the context of the terminal;

If the anchor base station decides not to migrate the context of the terminal, send a request for terminal context failure message to the target base station; if the anchor base station decides to migrate the context of the terminal, send a request for terminal context response message to the target base station , the requesting terminal context 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:

a configuration unit, configured to configure mobility control parameters of the terminal;

A sending unit, 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 stores the context of the terminal.

The parameter configuration device provided in the embodiment of the present application is applied to the anchor base station, and the device includes:

The first receiving unit is configured to receive a terminal context request message sent by a target base station, where the terminal context request message carries target information, where the anchor base station refers to a base station that stores the context of the terminal;

The first sending unit is configured to send a request for terminal context failure message to the target base station when the anchor base station decides not to migrate the context of the terminal; when the anchor base station decides to migrate the context of the terminal, send a message to the target base station The base station sends a requesting terminal context response message, where the requesting terminal context response message carries the context of the terminal.

The network device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs 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.

Specifically, 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 for storing a computer program, and the computer program enables the computer to execute the above parameter configuration method.

The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above parameter configuration method.

The computer program provided by the embodiment of the present application, when running on a computer, enables the computer to execute the above parameter configuration method.

Through the above technical solution, in the process of RNAU (or periodic RAN location update), because the target base station is relatively close to the terminal, the target base station configures the mobility control parameters of the terminal, which can assist the anchor base station in configuring the terminal's mobility control parameters The configuration information of the terminal makes the mobility control parameters for the terminal 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.

Description of drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The schematic embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation to the application. In the attached picture:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of RRC state transition provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of the RNA of the UE in the RRC_INACTIVE state provided by the embodiment of the present application;

FIG. 4 is a first schematic flowchart of a parameter configuration method provided by an embodiment of the present application;

Figure 5(a) is a schematic flow chart of RNAU with context migration provided by the embodiment of the present application;

Figure 5(b) is a schematic flow diagram of RNAU without context migration provided by the embodiment of the present application;

FIG. 6 is a schematic flow chart of RNAU with context migration provided in the embodiment of the present application;

FIG. 7 is a first schematic flow diagram of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application;

FIG. 8 is a schematic flow diagram II of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application;

FIG. 9 is a third schematic flow diagram of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application;

FIG. 10 is a schematic flow diagram 4 of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application;

FIG. 11 is a schematic flow diagram 5 of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application;

FIG. 12 is a schematic flowchart II of the parameter configuration method provided by the embodiment of the present application;

FIG. 13 is a schematic diagram of the first structural composition of the parameter configuration device provided by the embodiment of the present application;

FIG. 14 is a second schematic diagram of the structure and composition of the parameter configuration device provided by the embodiment of the present application;

FIG. 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 16 is a schematic structural diagram of a chip according to an embodiment of the present application;

FIG. 17 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The technical scheme of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, Code Division Multiple Access (Code Division Multiple Access, CDMA) system, Wideband Code Division Multiple Access (Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex, TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, a communication system 100 applied in this embodiment of the 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 for communicating with a terminal 120 (or called a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be a base station (Base TransceiverStation, BTS) in a GSM system or a CDMA system, may also be a base station (NodeB, NB) in a WCDMA system, or may be an evolved base station ( Evolutional Node B, eNB or eNodeB), or the wireless controller in the cloud radio access network (Cloud Radio AccessNetwork, CRAN), or the network device can be a mobile switching center, relay station, access point, vehicle equipment, wearable Devices, hubs, switches, bridges, routers, network-side devices in the 5G network or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 . "Terminal" as used herein includes, but is not limited to, a connection via a wire line, such as via a Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM radio A transmitter; and/or another terminal device configured to receive/send communication signals; and/or an Internet of Things (Internet of Things, IoT) device. A terminal arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data communication capabilities; may include radiotelephones, pagers, Internet/Internet PDAs with network access, web browsers, organizers, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic device. A terminal may refer to an access terminal, a user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.

Optionally, direct device to device (Device to Device, D2D) communication may be performed between terminals 120.

Optionally, the 5G system or the 5G network may also be called a New Radio (New Radio, NR) system or an NR network.

Figure 1 exemplarily shows a network device and two terminals. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area of the present application. There is no limit to this.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication The device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below, and any combination of the following related technologies and the technical solutions of the embodiments of the present application belongs to the protection scope of the embodiments of the present application.

In order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services, 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. in,

1) RRC_IDLE state (referred to as idle (idle) state): Mobility is UE-based cell selection and reselection, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no UE context and no RRC connection at the base station side.

2) RRC_CONNECTED state (connected state for short): there is an RRC connection, and UE context exists on the base station side and the UE side. The network side knows the location of the UE at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.

3) RRC_INACTIVE state (referred to as inactive (inactive) state): Mobility is UE-based cell selection and reselection, there is a connection between CN-NR, UE context exists on a certain base station, paging is triggered by RAN, based on The paging area of the RAN is managed by the RAN, and the network side knows the location of the UE 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:

1) RRC_CONNECTED state and RRC_INACTIVE state

On the one hand, the network side can control the UE to transition from the RRC_CONNECTED state to the RRC_INACTIVE state by releasing and suspending the RRC connection;

On the other hand, the network side can control the UE to transition from the RRC_INACTIVE state to the RRC_CONNECTED state by restoring the RRC connection.

2) RRC_CONNECTED state and RRC_IDLE state

On the one hand, the network side can control the UE to transition from the RRC_CONNECTED state to the RRC_IDLE state by releasing the RRC connection;

On the other hand, the network side can control the UE to transition from the RRC_IDLE state to the RRC_CONNECTED state by establishing an RRC connection.

3) RRC_INACTIVE state and RRC_IDLE state

The network side can control the UE to transition from the RRC_INACTIVE state to the RRC_IDLE state by releasing the RRC connection.

When the UE is in the RRC_INACTIVE state, any of the following events can trigger the UE to autonomously return to the RRC_IDLE state:

- Receive the initial paging message from CN;

- When the RRC recovery request is initiated, start the timer T319, if the timer T319 times out;

- MSG4 integrity protection verification failed;

- Cell reselection to other radio access technologies (Radio Access Technology, RAT);

-Enter the state of camping on any cell.

When the UE is in the RRC_INACTIVE state, it has the following characteristics:

- the connection between RAN and CN is maintained;

- UE and at least one base station save the AS context;

- The UE is reachable to the RAN side, and the relevant parameters are configured by the RAN;

- The network side does not need to be notified when the UE moves within the RNA configured by the RAN, but needs to be notified when the UE moves out of the RNA;

- The UE moves within the RNA according to the cell selection reselection mode.

When the UE is in the RRC_INACTIVE state, the network side will configure the parameters of the RRC_INACTIVE state for the UE through RRC Release (RRCRelease) dedicated signaling. The main parameters include: I-RNTI, used to identify the context corresponding to the inactive state of the UE on the base station side, I- The RNTI is unique within the base station. 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 of the RAN's initial paging. RAN discontinuous reception cycle (RAN DRX cycle), used to calculate the paging opportunity of RAN initial paging. The 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 UE in the RRC_INACTIVE state of RNA. The cell range covered by base station 1 to base station 5 is RNA. When the UE moves within the RNA, it does not need to notify the network side, and follows the mobility behavior in the idle state, that is, cell selection and reselection in principle. When the UE moves out of the paging area configured by the RAN, it will trigger the UE to restore the RRC connection and reacquire the paging area configured by the RAN. When the UE has downlink data arriving, 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 a paging message to the UE, so that the UE in the inactive state can restore 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 updates according to the period configured by the network. Therefore, 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.

For the UE in the inactive state, the paging initiated by the CN and the paging initiated by the RAN are received at the same time. The UE in the inactive state maintains the connection between the RAN and the CN, and when downlink data arrives, it will trigger the RAN to initiate RAN initial paging to notify the UE to restore the RRC connection in order to receive downlink data. The RAN initial paging message is the same as the CN initial paging message, but the DRX used to calculate the paging time is different.

Fig. 4 is a schematic flow diagram 1 of the parameter configuration method provided by the embodiment of the present application. As shown in Fig. 4, the parameter configuration method includes the following steps:

Step 401: the target base station configures mobility control parameters of the terminal.

The embodiment of the present application is applied to the RRC recovery process, and scenarios related to the RRC recovery process include but are not limited to RNAU scenarios, and scenarios in which a terminal enters a connected state from an inactive state.

1) RNAU scene

The event that triggers the terminal to perform RNAU is that the RNAU timer expires or the terminal moves to an area outside the RNA. The flow of RNAU will be described below.

Figure 5(a) is a schematic flow chart of RNAU with context migration, as shown in Figure 5(a), including the following process:

1. The terminal sends an RRC recovery request message to the target base station.

Here, 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.

2. The target base station sends a request message for requesting the terminal context to the anchor base station.

Here, the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.

3. The anchor base station sends a requesting terminal context response message to the target base station.

Here, the requesting terminal context response message carries the terminal context.

4. The target base station controls the terminal to be in an inactive state.

5. The target base station sends data forwarding address indication information to the anchor base station.

6. The target base station sends a path switching request message to an Access and Mobility Management Function (AMF).

7. The AMF sends a path switching response message to the target base station.

8. The target base station sends an RRC release message to the terminal.

Here, the RRC release message carries suspension indication information.

9. The target base station sends a terminal context release message to the anchor base station.

Figure 5(b) is a schematic diagram of the process of RNAU without context migration, as shown in Figure 5(b), including the following process:

1. The terminal sends an RRC recovery request message to the target base station.

Here, 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.

2. The target base station sends a request message for requesting the terminal context to the anchor base station.

Here, the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.

3. The anchor base station sends a message of failure to request the terminal context to the target base station.

4. The target base station sends an RRC release message to the terminal.

Here, the RRC release message carries suspension indication information.

2) The scenario where the terminal enters the connected state from the inactive state

The events that trigger the terminal to enter the connected state from the inactive state are: I) the terminal has downlink data arrival, and the network side initiates RAN initial paging 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 a demand for uplink data transmission, prompting the terminal to enter the connection state. The following describes the process of the terminal entering the connected state from the inactive state.

Figure 6 is a schematic flow diagram of RNAU with context migration, as shown in Figure 6, including the following flow:

1. The terminal sends an RRC recovery request message to the target base station.

2. The target base station sends a request message for requesting the terminal context to the anchor base station.

Here, the anchor base station refers to the last base station serving the terminal, and the base station stores the context of the terminal.

3. The anchor base station sends a requesting terminal context response message to the target base station.

Here, the requesting terminal context response message carries the terminal context.

4. The target base station sends an RRC recovery message to the terminal.

5. The terminal sends an RRC recovery complete message to the target base station.

6. The target base station sends data forwarding address indication information to the anchor base station.

7. The target base station sends a path switching request message to the AMF.

8. The AMF sends a path switching response message to the target base station.

9. The target base station sends a terminal context release message to the anchor base station.

In this embodiment of the present application, the types of the target base station and the anchor base station are not limited. In one example, the target base station and the anchor base station belong to the same type of base station, for example, both the target base station and the anchor base station are NR base stations (gNB). In another example, 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).

In this embodiment of the present application, the target base station refers to the new base station that provides services for the terminal during the above RRC recovery process, and the anchor base station refers to the original base station that provided services for the terminal last time during the above RRC recovery process.

For the RRC recovery process in the RNAU scenario, when the target base station that the terminal initiates the RRC connection recovery process is not the anchor base station (that is, the target base station and the anchor base station are different base stations), 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 will decide whether to transfer the context of the terminal to the target base station.

In the embodiment of the present application, during the RRC restoration process, the target base station configures the mobility control parameters of the terminal.

Step 402: The target base station sends 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 stores the context of the terminal.

In an embodiment, the target base station sends the mobility control parameters of the terminal to the anchor base station, so as to assist the anchor base station in configuring the mobility control parameters of the terminal; or, the target base station directly configures the mobility control parameters for the terminal. Mobility control parameters of the terminal. Finally, the mobility control parameters of the terminal are delivered to the terminal through an RRC release message. Here, the mobility control parameters of the terminal specifically refer to mobility control parameters after the terminal enters an idle state or an inactive state. Here, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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.

For example: the first parameter is redirectedCarrierInfo, which indicates the preferred frequency point and RAT information after the UE enters the idle state or inactive state; the second parameter is cellReselectionPriorities, which indicates the frequency of performing cell selection and reselection after the UE enters the idle state or inactive state Priority configuration parameters; the third parameter is deprioritisationReq, which indicates low-priority frequency information or RAT information after the UE enters the idle state or inactive state. Table 1 shows the configuration information of these three parameters.

Table 1

The following describes in detail how the network side configures the mobility control parameters of the terminal in combination with a specific RRC recovery process.

Application example one

Referring to FIG. 7, FIG. 7 is a schematic flow diagram of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application. As shown in FIG. 7, the flow includes the following steps:

1. The target base station receives the RRC recovery request message sent by the terminal.

Here, the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.

2. The target base station determines that it needs to indicate configuration information of the mobility control parameters of the terminal to the anchor base station.

Optionally, 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.

Based on this, the target base station, 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), determines that the mobility control The parameter configuration information is indicated to the anchor base station.

3. The target base station sends a RETRIEVE UE CONTEXT REQUEST message to the anchor base station, and the UE CONTEXT REQUEST message carries the configuration information of the mobility control parameters of the terminal.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

4. When the anchor base station decides not to transfer 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).

5. The target base station receives the RETRIEVE UE CONTEXTFAILURE message sent by the anchor base station, the request UE context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control parameters of the terminal configuration information.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

6. After the target base station receives the RRC release PDCP PDU, it sends an RRC release message to the terminal according to the RRC release PDCP PDU, and the RRC release message carries configuration information of mobility control parameters of the terminal.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

Application example two

Referring to FIG. 8, FIG. 8 is a schematic flow diagram II of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application. As shown in FIG. 8, the flow includes the following steps:

1. The target base station receives the RRC recovery request message sent by the terminal.

Here, the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.

2. The target base station determines that it needs to indicate configuration information of the mobility control parameters of the terminal to the anchor base station.

Optionally, 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.

Based on this, the target base station, 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), determines that the mobility control The parameter configuration information is indicated to the anchor base station.

3. The target base station sends a RETRIEVE UE CONTEXT REQUEST message to the anchor base station, and the UE CONTEXT REQUEST message carries the configuration information of the mobility control parameters of the terminal.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

4. When the anchor base station decides to migrate the context of the terminal, ignore the configuration information of the mobility control parameters of the terminal configured by the target base station.

5. The target base station receives the UE CONTEXTRESPONSE message sent by the anchor base station, and the UE CONTEXTRESPONSE message carries the context of the terminal.

6. The target base station sends an RRC release message generated by itself to the terminal.

Optionally, the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal. Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

Application example three

Referring to FIG. 9, FIG. 9 is a schematic flow diagram of the third configuration of the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application. As shown in FIG. 9, the flow includes the following steps:

1. The target base station receives the RRC recovery request message sent by the terminal.

Here, the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.

2. The target base station sends a RETRIEVE UE CONTEXTREQUEST message to the anchor base station, and the request message carries a first cause value, and the first cause value is used to indicate the triggering cause of the RRC connection recovery process is RNAU.

Optionally, the requesting terminal context request message further carries first indication information, where 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.

3. The anchor base station decides not to migrate the context of the terminal.

4. The target base station receives the requesting mobility control parameter message or the second indication information sent by the anchor base station, where the second indication information is used to instruct the anchor base station not to transfer the context of the terminal.

Here, the anchor base station sends a request for mobility control parameter message or the 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 instruct the anchor base station not to transfer the context of the terminal.

5. The target base station sends the mobility control parameters of the terminal to the anchor base station.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

6. The target base station receives the RETRIEVE UE CONTEXTFAILURE message sent by the anchor base station, the request UE context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control parameters of the terminal configuration information.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

7. 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 carries configuration information of mobility control parameters of the terminal.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

Application example four

Referring to FIG. 10 , FIG. 10 is a schematic flow diagram IV of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application. As shown in FIG. 10 , the flow includes the following steps:

1. The target base station receives the RRC recovery request message sent by the terminal.

Here, the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.

Optionally, the RRC recovery request message also 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.

2. If the target base station is configured with the mobility control parameters of the terminal, the target base station decides to instruct the anchor base station to perform the context transfer of the terminal.

Further, if the target base station is configured with mobility control parameters of the terminal, and the RRC connection recovery process is triggered by RNAU, the target base station decides to instruct the anchor base station to perform context migration of the terminal.

3. The target base station sends a RETRIEVE UE CONTEXTREQUEST message to the anchor base station, and the request message carries a first cause value, and the first cause value is used to indicate the triggering cause of the RRC connection recovery process is RNAU.

Optionally, the requesting terminal context request message also 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 has configuration for the Mobility control parameters of the terminal.

Here, 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.

4. The anchor base station decides whether to migrate the context of the terminal according to the second indication information and the first cause value.

Specifically, 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 cause value (for example, RNAU) of the terminal initiating the RRC recovery process.

5. The target base station receives the UE CONTEXTRESPONSE message sent by the anchor base station, where the UE context response message carries the context of the terminal.

Here, when 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, where the terminal context request response message carries the terminal context.

6. The target base station sends an RRC release message generated by itself to the terminal.

Optionally, the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.

Here, the mobility control parameters of the terminal include at least one of the following:

The first parameter (such as redirectedCarrierInfo) indicates the preferred frequency point signal and RAT information after the UE enters the idle state or the inactive state;

The second parameter (such as cellReselectionPriorities) indicates the frequency priority configuration parameters for performing cell selection 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.

Application example five

Referring to FIG. 11 , FIG. 11 is a schematic diagram of the fifth flow diagram of configuring the mobility control parameters of the terminal during the RRC recovery process provided by the embodiment of the present application. As shown in FIG. 11 , the flow includes the following steps:

1. The target base station receives the RRC recovery request message sent by the terminal.

Here, the terminal sends an RRC recovery request (RRCResumeRequest) message to the target base station to trigger the RRC connection recovery process.

Optionally, the RRC recovery request message also 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.

2. The target base station sends a RETRIEVE UE CONTEXTREQUEST message to the anchor base station, and the request message carries a first cause value, and the first cause value is used to indicate the triggering cause of the RRC connection recovery process is RNAU.

The anchor base station decides not to migrate the context of the terminal according to the first cause value.

Here, the anchor base station decides not to migrate the context of the terminal, and the anchor base station does not configure the mobility control parameters of the terminal in the RRC Release (RRCRelease) message.

3. The target base station receives the RETRIEVE UE CONTEXTFAILURE message sent by the anchor base station, the UE CONTEXTFAILURE request message carries the RRC release PDCP PDU, and the RRC release PDCP PDU does not carry the mobility control parameters of the terminal configuration information.

4. 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 the configuration information of the mobility control parameters of the terminal.

Figure 12 is a schematic flow diagram of the second parameter configuration method provided by the embodiment of the present 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 aforementioned method on the target base station side, as shown in As shown in Figure 12, the parameter configuration method includes the following steps:

Step 1201: An anchor base station receives a terminal context request message sent by a target base station, and the request terminal context request message carries target information, wherein the anchor base station refers to a base station that stores the context of the terminal.

In this embodiment of the present application, the target base station is configured with the terminal's mobility control parameters, and the request for terminal context request message carries the configuration information of the terminal's mobility control parameters configured by the target base station. Wherein, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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.

As shown in step 3 in FIG. 8 and FIG. 9, 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;

As shown in step 2 in FIG. 10 , the requesting 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 restoration process is RNAU. Optionally, the requesting terminal context request message further carries first indication information, where 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.

As shown in step 3 in FIG. 11 , the requesting 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 restoration process is RNAU. Optionally, the requesting terminal context request message further carries second indication information, where 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 migrate the context of the terminal, send a request for terminal context failure message to the target base station; A context response message, where the requesting terminal context response message carries the context of the terminal.

In this embodiment of the present application, if the anchor base station decides not to migrate the context of the terminal, it sends a request for the context of the target base station to the target base station; when the anchor base station decides to migrate the context of the terminal, it sends a message to the target base station Sending a requesting terminal context response message, where the requesting terminal context response message carries the context of the terminal. Wherein, the terminal's mobility control parameter may be carried in the requesting terminal context failure message, so that the terminal's mobility control parameter may be delivered to the terminal.

Referring to FIG. 7, in step 4 in FIG. 7, when the anchor base station decides not to migrate the context of the terminal, the configuration information of the mobility control parameters of the terminal configured by the target base station is carried in the RRC release message , and generate the RRC release PDCP PDU (RRCRelease PDCP PDU) of the RRC release message. In step 5 in FIG. 7, the anchor base station sends a RETRIEVE UE CONTEXT FAILURE message to the target base station, and the request for UE CONTEXT FAILURE message carries the RRC release PDCP PDU, and the RRC release PDCP The PDU carries configuration information of mobility control parameters of the terminal.

Referring to FIG. 8 , in step 4 in FIG. 8 , when the anchor base station decides to migrate the context of the terminal, it ignores the configuration information of the mobility control parameters of the terminal configured by the target base station. In step 5 in FIG. 8 , the anchor base station sends a RETRIEVE UE CONTEXT RESPONSE message to the target base station, and the UE CONTEXT RESPONSE message carries the context of the terminal.

Referring to FIG. 9, in step 2 in FIG. 9, the requesting 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. Optionally, the requesting terminal context request message further carries first indication information, where 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. In step 4 in FIG. 9 , when the anchor base station decides to migrate the context of the terminal, it sends a request for mobility control parameter message or second indication information to the target base station, and the second indication information is used to indicate the The anchor base station does not transfer the context of the terminal. In step 5 in FIG. 9, the anchor base station receives the mobility control parameters of the terminal sent by the target base station; and 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, and generate the RRC release PDCP PDU of the RRC release message. In step 6 in FIG. 9 , the anchor base station sends a RETRIEVE UE CONTEXTFAILURE message to the target base station, the requesting the UE context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the The configuration information of the mobility control parameters of the terminal.

Referring to FIG. 10 , in step 2 in FIG. 10 , the requesting 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. Optionally, the requesting terminal context request message further carries second indication information, where the second indication information is used to indicate that the anchor base station needs to perform context migration of the terminal. In step 4 in FIG. 10 , the anchor base station decides whether to migrate the context of the terminal according to the second indication information and the first cause value. In step 5 in FIG. 10, when the anchor base station decides to migrate the context of the terminal, it sends a RETRIEVE UE CONTEXT RESPONSE message to the target base station, and the request UE CONTEXT RESPONSE message carries the terminal context.

Referring to FIG. 11 , in step 3 in FIG. 11 , the anchor base station decides not to transfer the context of the terminal according to the first cause value. Here, the anchor base station decides not to migrate the context of the terminal, and the anchor base station does not configure the mobility control parameters of the terminal in the RRC Release (RRCRelease) message. In step 4 in FIG. 11 , when the anchor base station decides not to migrate the context of the terminal, the anchor base station requests a RETRIEVE UE CONTEXTFAILURE message from the target base station, and the requesting the terminal context failure message carries The RRC releases the PDCP PDU, and the RRC releases the PDCP PDU without carrying the configuration information of the mobility control parameters of the terminal.

On the other hand, the network side configures measurement configuration information through an RRC release message (also called an RRC connection release message) and/or a system broadcast message (such as SIB), and the measurement configuration information is called an early measurement configuration (early measurement configuration). The terminal performs measurements in the idle state or inactive state, and reports the measurement results to the network side when the terminal enters the connected state, so as to assist the network side in quickly configuring CA or MR-DC for the terminal. For terminals in the inactive state, the network side may update the UE RAN location without context migration. At this time, if the current serving base station wants to configure early measurement configuration, there is no way to configure it. Therefore, in order that the current serving base station can configure the early measurement configuration, it is necessary to carry a fourth parameter in the mobility control parameters of the terminal in the above solution, and the fourth parameter is an early measurement configuration parameter.

Based on this, optionally, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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 fourth parameter, the fourth parameter is an early measurement configuration parameter (ie early measurement configuration).

Fig. 13 is a schematic diagram of the first structural composition of the parameter configuration device provided by the embodiment of the present application. The device is applied to the target base station. As shown in Fig. 13, the device includes:

Configuration unit 1301, configured to configure 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 stores the context of the terminal.

In one embodiment, the device also includes:

The first receiving unit 1303 is configured to receive the RRC recovery request message sent by the terminal;

A determining unit 1304, configured to determine that configuration information of mobility control parameters of the terminal needs to be indicated to the anchor base station;

The sending unit 1302 is configured to send a requesting terminal context request message to the anchor base station, where the requesting terminal context request message carries configuration information of mobility control parameters of the terminal.

In an embodiment, the RRC recovery request message carries a first cause value, and the first cause value is used to indicate that the trigger 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 configuration information of mobility control parameters of the terminal needs to be indicated to the anchor base station.

In an embodiment, when the anchor base station decides not to transfer the context of the terminal, the device 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 carries the mobility control parameter 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.

In an embodiment, when the anchor base station decides to migrate the context of the terminal, the device further includes:

The second receiving unit 1305 is configured to receive a requesting terminal context response message sent by the anchor base station, where the requesting terminal context response message carries the context of the terminal;

The sending unit 1302 is further configured to send the RRC release message generated by itself to the terminal.

In an embodiment, the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.

In one embodiment, the device also 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 requesting terminal context request message to the anchor base station, where the requesting terminal context request message carries a first cause value, and the first cause value is used to indicate the triggering cause of the RRC connection recovery process is RNAU.

In an embodiment, the requesting terminal context 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.

In an embodiment, when the anchor base station decides not to transfer the context of the terminal, the device further includes:

The third receiving unit 1306 is configured to receive a requesting mobility control parameter 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 migrate the context of the terminal;

The sending unit 1302 is configured to send the 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 an RRC release PDCP PDU, and the RRC release PDCP PDU carries the mobility control parameter 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.

In an embodiment, the requesting terminal context 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.

In an embodiment, when the anchor base station decides to migrate the context of the terminal, the device further includes:

The second receiving unit 1305 is configured to receive a requesting terminal context response message sent by the anchor base station, where the terminal context response message carries the context of the terminal;

The sending unit 1302 is configured to send the RRC release message generated by itself to the terminal.

In an embodiment, the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.

In an embodiment, when the anchor base station decides not to transfer the context of the terminal, the device 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 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, and the RRC release message does not carry configuration information of mobility control parameters of the terminal.

In an embodiment, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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.

In an embodiment, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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;

A fourth parameter, the fourth parameter is an early measurement configuration parameter.

Those skilled in the art should understand that the relevant description of the above parameter configuration apparatus in the embodiment of the present application can be understood with reference to the relevant description of the parameter configuration method in the embodiment of the present application.

FIG. 14 is a schematic diagram of the second structure of the parameter configuration device provided by the embodiment of the present application. The device is applied to the anchor base station, as shown in FIG. 14 , the device includes:

The first receiving unit 1401 is configured to receive a terminal context request message sent by a target base station, where the terminal context request message carries target information, where the anchor base station refers to a base station that stores the context of the terminal;

The first sending unit 1402 is configured to send a request for terminal context failure message to the target base station when the anchor base station decides not to migrate the context of the terminal; when the anchor base station decides to migrate the context of the terminal, send the The target base station sends a requesting terminal context response message, where the requesting terminal context response message carries the context of the terminal.

In an embodiment, the requesting terminal context request message carries configuration information of mobility control parameters of the terminal configured by the target base station;

The apparatus 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, 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 Configuration information for control parameters.

In an embodiment, the requesting terminal context request message carries configuration information of 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 requesting terminal context response message, where the requesting terminal context response message carries the context of the terminal.

In an implementation manner, the requesting 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 restoration process is RNAU.

In an embodiment, the requesting terminal context 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.

In one embodiment, the device also 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, and the second indication information is used to indicate The anchor base station does not migrate the context of the terminal;

The second receiving unit 1405 is configured to receive the mobility control parameters of the terminal sent by the target base station;

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 an RRC release message, and generate an 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 Configuration information for control parameters.

In an embodiment, the requesting terminal context request message also 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 device further includes:

A determining unit 1406, 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 requesting terminal context response message to the target base station when the anchor base station decides to transfer the context of the terminal, and the requesting terminal context response message carries the context of the terminal .

In an embodiment, when the anchor base station decides not to migrate the context of the terminal, the first sending unit 1402 is configured to request a terminal context failure message from the target base station, and the request terminal context failure message Carry the RRC release PDCP PDU, and the RRC release PDCP PDU does not carry the configuration information of the mobility control parameters of the terminal.

In an embodiment, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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.

In an embodiment, the mobility control parameters of the terminal include at least one of the following:

A first parameter, where the first parameter is used to indicate frequency point information and RAT information that are 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;

A third parameter, where 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;

A fourth parameter, the fourth parameter is an early measurement configuration parameter.

Those skilled in the art should understand that the relevant description of the above parameter configuration apparatus in the embodiment of the present application can be understood with reference to the relevant description of the parameter configuration method in the embodiment of the present application.

FIG. 15 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device can 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, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application .

Optionally, as shown in FIG. 15 , the communication device 600 may further include a memory 620 . Wherein, the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.

Wherein, the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, as shown in FIG. 15 , 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, to send information or data to other devices, or receive other Information or data sent by the device.

Wherein, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be the network device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .

Optionally, the communication device 600 may specifically be the mobile terminal/terminal of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal in each method of the embodiment of the present application. For brevity, in This will not be repeated here.

FIG. 16 is a schematic structural diagram of a chip according to 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 a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 16 , the chip 700 may further include a memory 720 . Wherein, the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.

Wherein, the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may also include an input interface 730 . Wherein, the processor 710 may control the input interface 730 to communicate with other devices or chips, specifically, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may also include an output interface 740 . Wherein, the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application. For the sake of brevity, details are not repeated here.

Optionally, the chip can be applied to the mobile terminal/terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, no more repeat.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

FIG. 17 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 17 , the communication system 900 includes a terminal 910 and a network device 920 .

Wherein, the terminal 910 can be used to realize the corresponding functions realized by the terminal in the above method, and the network device 920 can be used to realize the corresponding functions realized by the network device in the above method. For the sake of brevity, details are not repeated here.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable Logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented 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, register. 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.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. The volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available, such as 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 (Synchlink DRAM, SLDRAM) And direct memory bus random access memory (DirectRambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a 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), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the methods of the embodiments of the present application, for It is concise and will not be repeated here.

The embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product may 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. For the sake of brevity, the Let me repeat.

Optionally, 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 processes implemented by the mobile terminal/terminal in the methods of the embodiments of the present application. For the sake of brevity , which will not be repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program is run on the computer, the computer executes the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , which will not be repeated here.

Optionally, the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application. When the computer program is run on the computer, the computer executes the corresponding functions implemented by the mobile terminal/terminal in the methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art 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 methods described in the various embodiments 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 disc, etc., which can store program codes. .

Claims (39)

1. A method of parameter configuration, the method comprising:

the target base station configures mobility control parameters of the terminal;

the target base station sends mobility control parameters of the terminal to an anchor base station or to the terminal, wherein the anchor base station refers to a base station for storing the context of the terminal;

the target base station sends mobility control parameters of the terminal to an anchor base station or to the terminal, which comprises:

the target base station receives a request terminal context failure message sent by the anchor base station under the condition that the anchor base station decides not to migrate the context of the terminal, wherein the request terminal context failure message carries an RRC release PDCP PDU, the RRC release PDCP PDU carries configuration information of mobility control parameters of the terminal, and the mobility control parameters of the terminal are provided for the anchor base station by 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, wherein the RRC release message carries configuration information of mobility control parameters of the terminal;

the target base station receives a request terminal context response message sent by the anchor base station under the condition that the anchor base station decides to migrate the context of the terminal, wherein the request terminal context response message carries the context of the terminal; the target base station sends an RRC release message generated by the target base station to the terminal; the RRC release message generated by the target base station carries the configuration information of the mobility control parameters of the terminal.

2. The method of claim 1, wherein the method further comprises:

the target base station receives a Radio Resource Control (RRC) recovery request message sent by a terminal;

and under the condition that the target base station determines that the configuration information of the mobility control parameters of the terminal needs to be indicated to the anchor base station, sending a request terminal context request message to the anchor base station, wherein the request terminal context request message carries the configuration information of the mobility control parameters of the terminal.

3. The method of claim 2, wherein the RRC restoration request message carries a first cause value, the first cause value being used to indicate that a trigger cause of an RRC connection restoration procedure is a RAN notification area update, RNAU; the method further comprises the steps of:

the target base station determines that configuration information of mobility control parameters of the terminal needs to be indicated to the anchor base station based on the first cause value in the RRC restoration request message.

4. The method of claim 1, wherein the method further comprises:

the target base station receives an RRC recovery request message sent by a terminal;

and the target base station sends a request terminal context request message to the anchor base station, wherein the request terminal context request message carries a first cause value, and the first cause value is used for indicating that the triggering cause of the RRC connection recovery process is RNAU.

5. The method of claim 4, wherein the request for terminal context message further carries first indication information indicating that the target base station has mobility control parameters that need to be configured to the terminal.

6. The method of claim 5, wherein the anchor base station decides not to migrate the context of the terminal, the method further comprising:

the target base station receives a message of a mobility control parameter or second indication information sent by the anchor base station, wherein the second indication information is used for indicating that the anchor base station does not migrate the context of the terminal;

and the target base station sends the mobility control parameters of the terminal to the anchor base station.

7. The method of claim 4, wherein the request for terminal context message further carries second indication information indicating that the anchor base station needs to perform a context migration of the terminal;

the second indication information and the first cause value are used for the anchor base station to decide whether to migrate the context of the terminal.

8. The method according to any of claims 1 to 7, wherein the mobility control parameters of the terminal comprise at least one of:

The first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

and the third parameter is used for indicating the low-priority frequency information or the RAT information after the terminal enters the idle state or the inactive state.

9. The method according to any of claims 1 to 7, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

a third parameter, where 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;

and a fourth parameter, which is an early measurement early measurement configuration parameter.

10. A method of parameter configuration, the method comprising:

the anchor base station receives a request terminal context request message sent by a target base station, wherein the request terminal context request message carries target information, and the anchor base station refers to a base station for storing the context of a terminal;

the anchor base station sends a request terminal context failure message to the target base station under the condition that the anchor base station decides not to migrate the context of the terminal, wherein the request terminal context failure message carries RRC release PDCP PDU which carries configuration information of mobility control parameters of the terminal, and the mobility control parameters of the terminal are provided to the anchor base station by the target base station; the RRC release PDCP PDU is used for triggering the target base station to send an RRC release message to the terminal, wherein the RRC release message carries configuration information of mobility control parameters of the terminal; the anchor base station sends a request terminal context response message to the target base station under the condition that the anchor base station decides to migrate the context of the terminal, wherein the request terminal context response message carries the context of the terminal, and the request terminal context response message is used for triggering the target base station to send an RRC release message generated by the anchor base station to the terminal; the RRC release message generated by the target base station carries the configuration information of the mobility control parameters of the terminal.

11. The method of claim 10, wherein the solicited terminal context request message carries configuration information of mobility control parameters of the terminal configured by the target base station;

the anchor base station decides not to migrate the context of the terminal, carries configuration information of mobility control parameters of the terminal configured by the target base station in an RRC release message, and generates an RRC release PDCP PDU of the RRC release message;

the anchor base station sends a request terminal context failure message to the target base station, wherein the request terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the configuration information of the mobility control parameters of the terminal.

12. The method of claim 10, wherein the solicited terminal context request message carries configuration information of 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, ignoring configuration information of mobility control parameters of the terminal configured by the target base station;

and the anchor base station sends a request terminal context response message to the target base station, wherein the request terminal context response message carries the context of the terminal.

13. The method of claim 10, wherein the solicited terminal context request message carries a first cause value indicating that a trigger cause of an RRC connection recovery procedure is an RNAU.

14. The method of claim 13, wherein the request for terminal context message further carries first indication information indicating that the target base station has mobility control parameters that need to be configured to the terminal.

15. The method of claim 14, wherein,

the anchor base station sends a message requiring mobility control parameters or second indication information to the target base station under the condition that the anchor base station decides to migrate the context of the terminal, wherein the second indication information is used for indicating the anchor base station not to 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 configuration information of the mobility control parameters of the terminal configured by the target base station in an RRC release message, and generates an RRC release PDCP PDU of the RRC release message;

the anchor base station sends a request terminal context failure message to the target base station, wherein the request terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the configuration information of the mobility control parameters of the terminal.

16. The method of claim 13, wherein the request for terminal context message further carries second indication information indicating that the anchor base station needs to perform a context migration of the terminal;

the anchor base station decides whether to migrate the context of the terminal according to the second indication information and the first cause value;

and under the condition that the anchor base station decides to migrate the context of the terminal, sending a request terminal context response message to the target base station, wherein the request terminal context response message carries the context of the terminal.

17. The method according to any of claims 10 to 16, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

and the third parameter is used for indicating the low-priority frequency information or the RAT information after the terminal enters the idle state or the inactive state.

18. The method according to any of claims 10 to 16, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

a third parameter, where 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;

and a fourth parameter, which is an early measurement early measurement configuration parameter.

19. A parameter configuration apparatus for application to a target base station, the apparatus comprising:

a configuration unit, configured to configure mobility control parameters of a terminal;

a sending unit, configured to send 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 stores a context of the terminal;

a second receiving unit;

the second receiving unit is configured to receive a request terminal context failure message sent by the anchor base station, where the request terminal context failure message carries an RRC release PDCP PDU, where the RRC release PDCP PDU carries configuration information of mobility control parameters of the terminal, and the mobility control parameters of the terminal are provided to the anchor base station by the target base station; the sending unit is further 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 second receiving unit is configured to receive a request terminal context response message sent by the anchor base station, where the request terminal context response message carries the context of the terminal, where the anchor base station decides to migrate the context of the terminal; the sending unit is further configured to send an RRC release message generated by the sending unit to the terminal; the RRC release message generated by the target base station carries the configuration information of the mobility control parameters of the terminal.

20. The apparatus of claim 19, wherein the apparatus further comprises:

a first receiving unit, configured to receive an RRC restoration request message sent by a terminal;

a determining unit configured to determine that configuration information of mobility control parameters of the terminal needs to be indicated to the anchor base station;

the sending unit is configured to send a request message for requesting a context of a terminal to the anchor base station, where the request message for requesting the context of the terminal carries configuration information of mobility control parameters of the terminal.

21. The apparatus of claim 20, wherein the RRC restoration request message carries a first cause value indicating that a trigger cause of an RRC connection restoration procedure is an RNAU;

The determining unit is configured to determine that configuration information of mobility control parameters of the terminal needs to be indicated to the anchor base station based on the first cause value in the RRC restoration request message.

22. The apparatus of claim 19, wherein the apparatus further comprises:

a first receiving unit, configured to receive an RRC restoration request message sent by a terminal;

the sending unit is further configured to send a request message for a context of the requiring terminal to the anchor base station, where the request message for the context of the requiring terminal carries a first cause value, and the first cause value is used to indicate that a trigger cause of the RRC connection recovery procedure is an RNAU.

23. The apparatus of claim 22, wherein the request for terminal context message further carries first indication information indicating that the target base station has mobility control parameters that need to be configured for the terminal.

24. The apparatus of claim 23, wherein the apparatus further comprises, in the event that the anchor base station decides not to migrate the context of the terminal:

a third receiving unit, 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 indicate that the anchor base station does not migrate a context of the terminal;

And the sending unit is used for sending the mobility control parameters of the terminal to the anchor base station.

25. The apparatus of claim 22, wherein the request for terminal context message further carries second indication information indicating that the anchor base station needs to perform a context migration of the terminal;

the second indication information and the first cause value are used for the anchor base station to decide whether to migrate the context of the terminal.

26. The apparatus of any of claims 19 to 25, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

and the third parameter is used for indicating the low-priority frequency information or the RAT information after the terminal enters the idle state or the inactive state.

27. The apparatus of any of claims 19 to 25, wherein the mobility control parameters of the terminal comprise at least one of:

The first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

a third parameter, where 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;

and a fourth parameter, which is an early measurement early measurement configuration parameter.

28. A parameter configuration apparatus for use in an anchor base station, the apparatus comprising:

the first receiving unit is used for receiving a request terminal context request message sent by a target base station, wherein the request terminal context request message carries target information, and the anchor base station is a base station for storing the context of the terminal;

a first sending unit, configured to send a request terminal context failure message to the target base station when the anchor base station decides not to migrate the context of the terminal, where the request terminal context failure message carries an RRC release PDCP PDU, where the RRC release PDCP PDU carries configuration information of mobility control parameters of the terminal, and mobility control parameters of the terminal are provided to the anchor base station by the target base station; the RRC release PDCP PDU is used for triggering the target base station to send an RRC release message to the terminal, wherein the RRC release message carries configuration information of mobility control parameters of the terminal; the anchor base station sends a request terminal context response message to the target base station under the condition that the anchor base station decides to migrate the context of the terminal, wherein the request terminal context response message carries the context of the terminal, and the request terminal context response message is used for triggering the target base station to send an RRC release message generated by the anchor base station to the terminal; the RRC release message generated by the target base station carries the configuration information of the mobility control parameters of the terminal.

29. The apparatus of claim 28, wherein the request for terminal context message carries configuration information of mobility control parameters of the terminal configured by the target base station;

the apparatus further comprises: a generating unit, configured to, when the anchor base station decides not to migrate the context of the terminal, carry configuration information of mobility control parameters of the terminal configured by the target base station in an RRC release message, and generate an RRC release PDCP PDU of the RRC release message.

30. The apparatus of claim 28, wherein the request for terminal context message carries configuration information of mobility control parameters of the terminal configured by the target base station;

the first sending unit is configured to ignore configuration information of mobility control parameters of the terminal configured by the target base station, where the anchor base station decides to migrate a context of the terminal.

31. The apparatus of claim 28, wherein the solicited terminal context request message carries a first cause value indicating that a trigger cause of an RRC connection recovery procedure is an RNAU.

32. The apparatus of claim 31, wherein the request for terminal context message further carries first indication information indicating that mobility control parameters to be configured for the terminal exist for the target base station.

33. The apparatus of claim 32, wherein the apparatus further comprises:

a second sending unit, configured to send a mobility control parameter request message or second indication information to the target base station, where the anchor base station decides to migrate the context of the terminal, where the second indication information is used to indicate that the anchor base station does not migrate the context of the terminal;

a second receiving unit, configured to receive a mobility control parameter of the terminal sent by the target base station;

and the generating unit is used for carrying configuration information of the mobility control parameters of the terminal configured by the target base station in an RRC release message and generating an RRC release PDCP PDU of the RRC release message.

34. The apparatus of claim 31, wherein the request for terminal context message further carries second indication information indicating that the anchor base station needs to perform a context migration of the terminal; the apparatus further comprises:

A determining unit, configured to determine whether to migrate a context of the terminal according to the second indication information and the first cause value;

the first sending unit is configured to send a request terminal context response message to the target base station when the anchor base station decides to migrate the context of the terminal, where the request terminal context response message carries the context of the terminal.

35. The apparatus of any of claims 28-34, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

and the third parameter is used for indicating the low-priority frequency information or the RAT information after the terminal enters the idle state or the inactive state.

36. The apparatus of any of claims 28-34, wherein the mobility control parameters of the terminal comprise at least one of:

The first parameter is used for indicating frequency point information and RAT information which are preferably selected after the terminal enters an idle state or an inactive state;

the second parameter is used for indicating the frequency priority information for executing cell selection reselection after the terminal enters an idle state or an inactive state;

a third parameter, where 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;

and a fourth parameter, which is an early measurement early measurement configuration parameter.

37. A network device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 9 or the method according to any of claims 10 to 18.

38. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 9 or the method of any one of claims 10 to 18.

39. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 9 or the method of any one of claims 10 to 18.

Images