CN112715038A

CN112715038A - Parameter configuration method and device, and network equipment

Info

Publication number: CN112715038A
Application number: CN201980060415.9A
Authority: CN
Inventors: 王淑坤; 杨宁
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-01-28
Filing date: 2019-11-04
Publication date: 2021-04-27
Anticipated expiration: 2039-11-04
Also published as: CN112715038B; WO2020154868A1; WO2020155725A1

Abstract

The embodiment of the application provides a parameter configuration method, a device and network equipment, wherein the method comprises the following steps: the target base station configures the mobility control parameters of the terminal; and the target base station sends the mobility control parameters of the terminal to an anchor base station or the terminal, wherein the anchor base station is a base station for storing the context of the terminal.

Description

Parameter configuration method and device, and network equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a parameter configuration method and device and network equipment.

Background

A Radio Access Network Notification Area (RNA) is an Area for controlling a terminal to perform cell selection and reselection in an inactive (inactive) state, and is also a paging range Area for initial paging of a Radio Access Network (RAN). A scenario in which the terminal is triggered to perform an RNA Update (RNAU) has an RNAU timer timeout or the terminal moves to an Area other than the RNA.

If the terminal executes 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 a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) of the RRC release message to the target base station, and the target base station sends the RRC release message to the terminal, so that the terminal completes the RAN location update process. At present, some terminal-specific information, such as mobility control parameters, may be configured for a terminal in an RRC release message, and these parameters are generally configured by a network according to the topology and deployment of a peripheral network of the network, network load, and other conditions. Under the condition that the context of the terminal does not migrate, the parameters are given by the anchor base station, and at the moment, the terminal may be far away from the anchor base station, and the anchor base station does not know the conditions of network deployment, topology, network load and the like where the UE is located, so that the configuration of the parameters by the anchor base station has no guiding significance.

Disclosure of Invention

The embodiment of the application provides a parameter configuration method and device and network equipment.

The parameter configuration method provided by the embodiment of the application comprises the following steps:

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

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

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

the anchor base station sends a failure message of requesting the context of the terminal to the target base station under the condition that the context of the terminal is not transferred; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited 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 a mobility control parameter of a terminal;

a sending unit, configured to send the mobility control parameter of the terminal to an anchor base station or to the terminal, where the anchor base station is a base station that stores a context of the terminal.

The parameter configuration device provided by the embodiment of the application is applied to an anchor base station, and the device comprises:

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

a first sending unit, configured to send a message of requesting a context failure of a terminal to the target base station when the anchor base station determines not to migrate the context of the terminal; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.

The network equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the parameter configuration method.

The chip provided by the embodiment of the application is used for realizing the parameter configuration method.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the 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 a computer to execute the parameter configuration method.

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

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

Through the technical scheme, in the process of RNAU (or referred to as periodic RAN position updating), because the target base station is closer to the terminal, the target base station configures the mobility control parameters of the terminal, and the anchor base station can be assisted to configure the configuration information of the mobility control parameters of the terminal, so that the mobility control parameters for the terminal are 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.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

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

fig. 2 is a diagram illustrating RRC state transition according to an embodiment of the present application;

fig. 3 is a schematic diagram of an RNA of a UE in an RRC _ INACTIVE state according to an embodiment of the present application;

fig. 4 is a first flowchart illustrating a parameter configuration method according to an embodiment of the present application;

FIG. 5(a) is a flowchart of an RNAU with context migration according to an embodiment of the present application;

FIG. 5(b) is a schematic flow chart of an RNAU without context migration according to an embodiment of the present application;

FIG. 6 is a flowchart of an RNAU with context migration according to an embodiment of the present application;

fig. 7 is a first flowchart illustrating a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a second process for configuring mobility control parameters of a terminal in an RRC recovery procedure according to an embodiment of the present application;

fig. 9 is a third schematic flowchart of a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure according to the embodiment of the present application;

fig. 10 is a fourth flowchart illustrating a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure according to the embodiment of the present application;

fig. 11 is a fifth flowchart illustrating a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure according to an embodiment of the present application;

fig. 12 is a second flowchart illustrating a parameter configuration method according to an embodiment of the present application;

fig. 13 is a first schematic structural diagram of a parameter configuration apparatus according to an embodiment of the present disclosure;

fig. 14 is a schematic structural diagram of a parameter configuration apparatus according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a communication device according to an embodiment of the present application;

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

fig. 17 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

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, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

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

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is 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, a satellite or a cellular phone; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminals 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.

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

It should be understood that a device having a communication function in a network/system in the embodiments 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 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

For the convenience of understanding the technical solutions of the embodiments of the present application, the following description is provided for the related art of the embodiments of the present application, and any combination of the related art and the technical solutions of the embodiments of the present application falls within the scope of the embodiments of the present application.

5G, in order to reduce air interface signaling, quickly recover wireless connection and quickly recover data service, a new RRC state, namely an RRC INACTIVE (RRC _ INACTIVE) state, is defined. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein the content of the first and second substances,

1) RRC _ IDLE state (IDLE state for short): mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no UE context and no RRC connection.

2) RRC _ CONNECTED state (CONNECTED state for short): there is an RRC connection and there is a UE context on the base station side and the UE side. The network side knows that the location of the UE is at a specific cell level. Mobility is network side controlled mobility. Unicast data may be transmitted between the UE and the base station.

3) RRC _ INACTIVE state (INACTIVE state for short): mobility is UE-based cell selection reselection, there is a connection between CN-NRs, UE context exists on a certain base station, paging is triggered by RAN, RAN-based paging area is managed by RAN, and network side knows that UE location is based on RAN's paging area level.

The network side may control RRC state transition of the UE, as shown in fig. 2, specifically:

1) RRC _ CONNECTED state and RRC _ INACTIVE state

On one hand, the network side can control the UE to be converted into the RRC _ INACTIVE state from the RRC _ CONNECTED state by releasing and suspending the RRC connection;

on the other hand, the network side may 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 be converted into the RRC _ IDLE state from the RRC _ CONNECTED state by releasing the RRC connection;

on the other hand, the network side may 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.

In the case that the UE is in the RRC _ INACTIVE state, the UE may be triggered to autonomously return to the RRC _ IDLE state by any one of the following events:

-receiving a CN initial paging message;

-upon initiation of an RRC recovery request, starting a timer T319, if the timer T319 times out;

MSG4 integrity protection verification failure;

-cell reselection to other Radio Access Technology (RAT);

entering a camped on any cell (camp on any cell).

When the UE is in the RRC _ INACTIVE state, the following features are provided:

-the connection between RAN and CN is maintained;

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

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

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

-UE movement within RNA according to cell selection reselection mode.

When the UE is in the RRC _ INACTIVE state, the network side configures parameters of the RRC _ INACTIVE state to the UE through RRC release (rrcreelease) dedicated signaling, where the main parameters include: and the I-RNTI is used for identifying the context corresponding to the inactive state of the UE at the base station side, and the I-RNTI is unique in the base station. RNA is used for controlling the area of the UE for cell selection reselection in an inactive state, and is also the paging range area of RAN initial paging. A RAN discontinuous reception cycle (RAN DRX cycle) for calculating a paging occasion for RAN initial paging. An RNAU period (RNAU periodicity) for controlling a period for the UE to perform periodic RAN location updates. And the NCC is used for a secret key used in the RRC connection recovery process.

Fig. 3 is a schematic diagram of RNA when the UE is in the RRC _ INACTIVE state, where the cell range covered by the base stations 1 to 5 is RNA, and when the UE moves in the RNA, the UE does not notify the network side, and follows mobility behavior in idle state, i.e. cell selection and reselection principle. When the UE moves out of the paging area configured by the RAN, the UE is triggered to recover RRC connection and reacquire the paging area configured by the RAN. When downlink data arrives at the UE, the gNB maintaining the connection between the RAN and the CN for the UE triggers all cells in the RAN paging area to send paging messages to the UE, so that the UE in an inactive state can recover RRC connection and receive data. The UE in the inactive state configures a RAN paging area, and in order to ensure the accessibility of the UE in the area, the UE needs to perform periodic location update according to a period configured by the network. The scenario that triggers the UE to perform an RNA update has the RNAU timer timeout or the UE moves to an area outside the RNA.

For inactive UEs, CN-initiated paging and RAN-initiated paging are received simultaneously. The UE in inactive state keeps the connection between RAN and CN, when the downlink data arrives, the RAN is triggered to initiate RAN initial paging to inform the UE to recover RRC connection so as to receive the downlink data. The RAN-initiated paging message is the same as the CN-initiated paging message, but the DRX used in calculating the paging time is different.

Fig. 4 is a first schematic flow chart of a parameter configuration method provided in an embodiment of the present application, and as shown in fig. 4, the parameter configuration method includes the following steps:

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

The embodiment of the application is applied to the RRC recovery process, and scenes related to the RRC recovery process include but are not limited to an RNAU scene and a scene that a terminal enters a connection state from an inactive state.

1) RNAU scene

The event triggering the terminal to execute RNAU is the expiration of the RNAU timer or the terminal moving to an area outside the RNA. The following describes the flow of RNAU.

Fig. 5(a) is a schematic flow chart of RNAU with context migration, and as shown in fig. 5(a), the flow chart includes the following steps:

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 indicating that the trigger cause of the RRC connection recovery procedure is RNAU.

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

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

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

Here, the solicitation terminal context response message carries the context of the terminal.

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

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

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

7. And 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. And the target base station sends a terminal context release message to the anchor base station.

Fig. 5(b) is a schematic flow chart of RNAU without context migration, and as shown in fig. 5(b), the following flows are included:

3. The anchor base station sends a message of requesting the context failure of the terminal 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) Scenario for terminal to enter connected state from inactive state

The events that trigger the terminal to enter the connected state from the inactive state are: I) when downlink data arrives at the terminal, a network side initiates RAN initial paging to promote the terminal to enter a connection state; II) the terminal itself initiates a RAN location area update, e.g. a periodic RAN location update or a cross-area location update; and III) the terminal has an uplink data sending requirement, so that the terminal is promoted to enter a connection state. The following describes a procedure of entering a connected state from an inactive state by a terminal.

Fig. 6 is a flowchart of RNAU with context migration, and as shown in fig. 6, the following steps are included:

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

5. And the terminal sends an RRC recovery completion message to the target base station.

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

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

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

In the embodiment of the present application, the types of the target base station and the anchor base station are not limited, and in one example, the target base station and the anchor base station belong to the same type of base station, for example, the target base station and the anchor base station are both NR base stations (gnbs). In another example, the target base station and the anchor base station belong to different types of base stations, e.g., the target base station is an NR base station (gNB) and the anchor base station is an LTE base station (eNB).

In this embodiment, the target base station refers to a new base station providing service for the terminal in the RRC recovery process, and the anchor base station refers to an original base station providing service for the terminal last time in the RRC recovery process.

For the RRC recovery process in the RNAU scenario, when the target base station where the terminal initiates the RRC connection recovery process is not the anchor base station (i.e., the target base station and the anchor base station are different base stations), the anchor base station needs to determine whether to transfer the context of the terminal to the target base station side. Therefore, the target base station sends the first cause value carried in the RRC recovery request message sent by the terminal to the anchor base station in the context requisition process of the terminal, and the anchor base station determines whether the context of the terminal needs to be transferred to the target base station side.

In the embodiment of the application, the target base station configures the mobility control parameters of the terminal in the RRC recovery process.

Step 402: and the target base station sends the mobility control parameters of the terminal to an anchor base station or the terminal, wherein the anchor base station is a base station for storing the context of the terminal.

In one embodiment, the target base station sends the mobility control parameters of the terminal to an anchor base station, so as to assist the anchor base station to configure the mobility control parameters of the terminal; or, the target base station directly configures the mobility control parameters of the terminal for the terminal. And finally, the mobility control parameters of the terminal are sent to the terminal through an RRC release message. Here, the mobility control parameter of the terminal specifically refers to a mobility control parameter after the terminal enters an idle state or an inactive state. Here, the mobility control parameter of the terminal includes at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

and 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 a redirectedCarrier Info, and indicates the frequency point information and RAT information which are preferentially selected after the UE enters an idle state or an inactive state; the second parameter is cellreselection priorities, and is a frequency priority configuration parameter for indicating the UE to execute cell selection reselection after entering an idle state or an inactive state; the third parameter is priority req, which indicates low priority frequency information or RAT information after the UE enters idle state or inactive state. Table 1 gives the configuration information for these three parameters.

TABLE 1

How the network side configures the mobility control parameters of the terminal is described in detail below with reference to a specific RRC recovery procedure.

Application example 1

Referring to fig. 7, fig. 7 is a first schematic flowchart illustrating a procedure for configuring a mobility control parameter of a terminal in an RRC recovery process according to an embodiment of the present application, and as shown in fig. 7, the procedure includes the following steps:

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

Here, the terminal transmits an RRC recovery request (RRCResumeRequest) message to the target base station, triggering an RRC connection recovery procedure.

2. And 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.

Optionally, the RRC connection recovery request message carries a first cause value, where the first cause value is used to indicate that a trigger cause of the RRC connection recovery procedure is RNAU.

Based on this, the target base station determines that the configuration information of the mobility control parameter of the terminal needs to be indicated to the anchor base station based on the first cause value in the RRC recovery request message, which indicates that the triggering cause of the RRC connection recovery procedure is RNAU.

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

Here, the mobility control parameter of the terminal includes at least one of:

a first parameter (e.g., a redirectedCarrierInfo) indicating frequency point information and RAT information which are preferentially selected after the UE enters an idle state or an inactive state;

a second parameter (e.g., cellreselection priorities), which indicates a frequency priority configuration parameter for performing cell reselection after the UE enters an idle state or an inactive state;

a third parameter (e.g., priority req), indicating low priority frequency information or RAT information after the UE enters idle state or inactive state. Table 1 gives the configuration information for these three parameters.

4. And under the condition that the anchor base station determines not to migrate the context of the terminal, carrying the 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 (RRCRelease PDCP PDU) of the RRC release message.

5. And the target base station receives a request terminal CONTEXT FAILURE (RETRIEVE UE CONTEXT FAILURE) message sent by the anchor base station, wherein the request terminal CONTEXT FAILURE message carries RRC release PDCP PDU which carries the configuration information of the mobility control parameters of the terminal.

Here, the mobility control parameter of the terminal includes at least one of:

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

Here, the mobility control parameter of the terminal includes at least one of:

Application example two

Referring to fig. 8, fig. 8 is a second flowchart illustrating a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure according to the embodiment of the present application, and as shown in fig. 8, the process includes the following steps:

Here, the mobility control parameter of the terminal includes at least one of:

4. And under the condition that the anchor base station decides to migrate the context of the terminal, ignoring the configuration information of the mobility control parameters of the terminal configured by the target base station.

5. And the target base station receives a solicited terminal CONTEXT RESPONSE (RETRIEVE UE CONTEXT RESPONSE) message sent by the anchor base station, wherein the solicited terminal CONTEXT RESPONSE message carries the CONTEXT of the terminal.

6. And the target base station sends the RRC release message generated by the target base station to the terminal.

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

Application example three

Referring to fig. 9, fig. 9 is a third schematic view of a flow chart illustrating configuring a mobility control parameter of a terminal in an RRC recovery process according to the embodiment of the present application, and as shown in fig. 9, the flow chart includes the following steps:

2. The target base station sends a solicited terminal CONTEXT REQUEST (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station, wherein the solicited terminal CONTEXT REQUEST message carries a first cause value, and the first cause value is used for indicating that the trigger cause of the RRC connection recovery process is RNAU.

Optionally, the solicitation terminal context request message further carries first indication information, where the first indication information is used to indicate that the target base station has a mobility control parameter that needs to be configured to the terminal.

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

4. And the target base station receives the message of requesting the mobility control parameter or second indication information sent by the anchor base station, wherein the second indication information is used for indicating the anchor base station not to migrate the context of the terminal.

Here, the anchor base station transmits a message requesting mobility control parameters or second indication information to the anchor base station according to the first indication information and the decision not to migrate the context of the terminal, or only according to the decision not to migrate the context of the terminal, the second indication information indicating that the anchor base station does not migrate the context of the terminal.

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

Here, the mobility control parameter of the terminal includes at least one of:

6. And the target base station receives a request terminal CONTEXT FAILURE (RETRIEVE UE CONTEXT FAILURE) message sent by the anchor base station, wherein the request terminal CONTEXT FAILURE message carries RRC release PDCP PDU which carries the configuration information of the mobility control parameters of the terminal.

Here, the mobility control parameter of the terminal includes at least one of:

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

Here, the mobility control parameter of the terminal includes at least one of:

Application example four

Referring to fig. 10, fig. 10 is a fourth schematic view of a process of configuring a mobility control parameter of a terminal in an RRC recovery procedure provided in the embodiment of the present application, as shown in fig. 10, the process includes the following steps:

Optionally, the RRC recovery request message further carries a first cause value, where the first cause value is used to indicate that the trigger cause of the RRC connection recovery procedure is RNAU.

2. And if the target base station is configured with the mobility control parameters of the terminal, the target base station determines that the anchor base station needs to be indicated to perform context migration of the terminal.

Further, if the target base station is configured with the mobility control parameter of the terminal and the trigger reason of the RRC connection recovery procedure is RNAU, the target base station decides that it needs to indicate that the anchor base station needs to perform context migration of the terminal.

3. The target base station sends a solicited terminal CONTEXT REQUEST (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station, wherein the solicited terminal CONTEXT REQUEST message carries a first cause value, and the first cause value is used for indicating that the trigger cause of the RRC connection recovery process is RNAU.

Optionally, the solicitation for 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 or to indicate that the target base station has a mobility control parameter configured for the terminal.

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

4. And the anchor base station determines whether to migrate the context of the terminal according to the second indication information and the first reason value.

Specifically, the anchor base station jointly determines whether to migrate the context of the terminal according to the second indication information of the target base station and a cause value (such as RNAU) of the RRC recovery procedure initiated by the terminal.

5. And the target base station receives a request terminal CONTEXT RESPONSE (RETRIEVE UE CONTEXT RESPONSE) message sent by the anchor base station, wherein the terminal CONTEXT RESPONSE message carries the CONTEXT of the terminal.

Here, when the anchor base station determines to migrate the context of the terminal, the anchor base station sends a solicited terminal context response message to the target base station, where the solicited terminal context response message carries the context of the terminal.

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

Here, the mobility control parameter of the terminal includes at least one of:

Application example five

Referring to fig. 11, fig. 11 is a fifth schematic view of a process of configuring a mobility control parameter of a terminal in an RRC recovery process according to the embodiment of the present application, and as shown in fig. 11, the process includes the following steps:

And the anchor base station determines not to migrate the context of the terminal according to the first reason 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 parameter of the terminal in an RRC release (rrcreelease) message.

3. And the target base station receives a request terminal CONTEXT FAILURE (RETRIEVE UE CONTEXT FAILURE) message sent by the anchor base station, wherein the request terminal CONTEXT FAILURE message carries RRC release PDCP PDU which does not carry the configuration information of the mobility control parameters of the terminal.

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

Fig. 12 is a second flowchart of a parameter configuration method provided in the embodiment of the present application, and it should be noted that, when the scheme in this example is applied to the anchor base station side, the method in this example can be understood by combining the foregoing method on the target base station side, as shown in fig. 12, the parameter configuration method includes the following steps:

step 1201: an anchor base station receives a request message of requesting the context of a terminal sent by a target base station, wherein the request message of requesting the context of the terminal carries target information, and the anchor base station is a base station for storing the context of the terminal.

In the embodiment of the present application, a target base station side is configured with a mobility control parameter of a terminal, and the solicitation terminal context request message carries configuration information of the mobility control parameter of the terminal configured by the target base station. Wherein the mobility control parameter of the terminal comprises at least one of:

As shown in step 3 in fig. 8 and fig. 9, an anchor base station receives a solicited terminal context request message sent by a target base station, where the solicited terminal context request message carries configuration information of a mobility control parameter of the terminal configured by the target base station;

as shown in step 2 in fig. 10, the solicited terminal context request message carries a first cause value indicating that the trigger cause of the RRC connection recovery procedure is RNAU. Optionally, the solicitation terminal context request message further carries first indication information, where the first indication information is used to indicate that the target base station has a mobility control parameter that needs to be configured to the terminal.

As shown in step 3 in fig. 11, the solicited terminal context request message carries a first cause value, which is used to indicate that the trigger cause of the RRC connection recovery procedure is RNAU. Optionally, the request message for requesting the context of the terminal 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: the anchor base station sends a failure message of requesting the context of the terminal to the target base station under the condition that the context of the terminal is not transferred; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.

In the embodiment of the application, the anchor base station sends a failure message of requesting the context of the terminal to the target base station under the condition that the context of the terminal is not migrated; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal. The message of requesting the terminal context failure may carry the mobility control parameter of the terminal, and thus, the mobility control parameter of the terminal may be issued to the terminal.

Referring to fig. 7, in step 4 in fig. 7, when the anchor base station determines not to migrate the context of the terminal, the anchor base station carries configuration information of the mobility control parameter of the terminal configured by the target base station in an RRC release message, and generates an RRC release PDCP PDU (rrcleease PDCP PDU) of the RRC release message. In step 5 in fig. 7, the anchor base station sends a request for terminal CONTEXT FAILURE (retry UE CONTEXT FAILURE) message to the target base station, where the request for terminal CONTEXT FAILURE message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of the mobility control parameter of the terminal.

Referring to fig. 8, in step 4 in fig. 8, when the anchor base station determines to migrate the context of the terminal, the anchor base station ignores configuration information of the mobility control parameter of the terminal configured from the target base station. In step 5 in fig. 8, the anchor base station sends a solicited terminal CONTEXT RESPONSE (RETRIEVE UE CONTEXT RESPONSE) message to the target base station, where the solicited terminal CONTEXT RESPONSE message carries the CONTEXT of the terminal.

Referring to fig. 9, in step 2 in fig. 9, the solicited terminal context request message carries a first cause value indicating that a trigger cause of the RRC connection recovery procedure is RNAU. Optionally, the solicitation terminal context request message further carries first indication information, where the first indication information is used to indicate that the target base station has a mobility control parameter that needs to be configured to the terminal. In step 4 in fig. 9, when the anchor base station determines to migrate the context of the terminal, the anchor base station sends a message requesting mobility control parameters or second indication information to the target base station, where the second indication information is used to indicate that the anchor base station does not migrate the context of the terminal. In step 5 in fig. 9, the anchor base station receives the mobility control parameter of the terminal sent by the target base station; and carrying the 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. In step 6 in fig. 9, the anchor base station sends a request for terminal CONTEXT FAILURE (retry UE CONTEXT FAILURE) message to the target base station, where the request for terminal CONTEXT FAILURE message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries the configuration information of the mobility control parameter of the terminal.

Referring to fig. 10, in step 2 in fig. 10, the solicited terminal context request message carries a first cause value, where the first cause value is used to indicate that a trigger cause of the RRC connection recovery procedure is RNAU. Optionally, the request message for requesting the context of the terminal 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 determines 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 determines to migrate the CONTEXT of the terminal, the anchor base station sends a solicited terminal CONTEXT RESPONSE (RETRIEVE UE CONTEXT RESPONSE) message to the target base station, where the solicited terminal CONTEXT RESPONSE message carries the CONTEXT of the terminal.

Referring to fig. 11, in step 3 in fig. 11, 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 parameter of the terminal in an RRC release (rrcreelease) message. In step 4 in fig. 11, in a case that the anchor base station determines not to migrate the CONTEXT of the terminal, the anchor base station asks the target base station for a terminal CONTEXT FAILURE (retry UE CONTEXT FAILURE) message, where the solicited terminal CONTEXT FAILURE message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of a mobility control parameter of the terminal.

On the other hand, the network side configures measurement configuration information through an RRC release message (which may also be referred to as an RRC connection release message) and/or a system broadcast message (such as an SIB), where the measurement configuration information is referred to as early measurement configuration (early measurement configuration) and is used for the terminal to perform measurement in an idle state or an inactive state, and report a measurement result to the network side when the terminal enters a connected state, so as to assist the network side in quickly configuring a CA or an MR-DC for the terminal. For the terminal in the inactive state, the network side may perform UE RAN location update without context migration, and at this time, if the current serving base station wants to configure early measurement configuration, there is no way to configure the UE RAN location update. Therefore, in order that the current serving base station may configure the early measurement configuration, a fourth parameter needs to be carried in the mobility control parameter of the terminal in the above scheme, where the fourth parameter is the early measurement configuration parameter.

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

a third parameter, configured to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state;

a fourth parameter, where the fourth parameter is an early measurement configuration parameter (that is, early measurement configuration).

Fig. 13 is a schematic structural diagram of a parameter configuration apparatus according to an embodiment of the present application, where the apparatus is applied to a target base station, and as shown in fig. 13, the apparatus includes:

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

a sending unit 1302, configured to send the mobility control parameter of the terminal to an anchor base station or to the terminal, where the anchor base station is a base station that stores a context of the terminal.

In one embodiment, the apparatus further comprises:

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

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

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

In an embodiment, the RRC connection recovery request message carries a first cause value, where the first cause value is used to indicate that a trigger cause of the RRC connection recovery procedure is RNAU;

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

In one embodiment, in a case where the anchor base station determines not to migrate the context of the terminal, the apparatus further includes:

a second receiving unit 1305, configured to receive a solicited terminal context failure message sent by the anchor base station, where the solicited terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal;

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 a mobility control parameter of the terminal.

In one embodiment, in a case where the anchor base station determines to migrate the context of the terminal, the apparatus further includes:

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

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

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

In one embodiment, the apparatus further comprises:

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

In an embodiment, the solicitation terminal context request message further carries first indication information, where the first indication information is used to indicate that the target base station has a mobility control parameter that needs to be configured to the terminal.

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

the sending unit 1302 is configured to send the mobility control parameter of the terminal to the anchor base station;

In an embodiment, the request message for requesting the context of the terminal 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;

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.

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

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

a second receiving unit 1305, configured to receive a solicited terminal context failure message sent by the anchor base station, where the solicited terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of a mobility control parameter of the terminal;

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 does not carry configuration information of a mobility control parameter of the terminal.

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

and a fourth parameter, wherein the fourth parameter is an early measurement configuration parameter.

Those skilled in the art should understand that the related description of the above parameter configuration apparatus in the embodiment of the present application can be understood by referring to the related description of the parameter configuration method in the embodiment of the present application.

Fig. 14 is a schematic structural diagram of a parameter configuration apparatus according to an embodiment of the present application, where the apparatus is applied to an anchor base station, and as shown in fig. 14, the apparatus includes:

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

a first sending unit 1402, configured to send a message of requesting a context failure of a terminal to the target base station when the anchor base station determines not to migrate the context of the terminal; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.

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

the device further comprises: a generating unit 1403, configured to, when the anchor base station determines not to migrate the context of the terminal, carry configuration information of a mobility control parameter 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 solicited terminal context failure message to the target base station, where the solicited terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal.

the first sending unit 1402, configured to ignore configuration information of the mobility control parameter of the terminal configured by the target base station when the anchor base station determines to migrate the context of the terminal; and 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.

In an embodiment, the solicited terminal context request message carries a first cause value indicating that the trigger cause of the RRC connection recovery procedure is an RNAU.

In one embodiment, the apparatus further comprises:

a second sending unit 1404, configured to send a message requesting mobility control parameters or second indication information to the target base station when the anchor base station determines 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 1405, configured to receive the mobility control parameter of the terminal sent by the target base station;

a generating unit 1403, configured to carry the configuration information of the mobility control parameter 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;

In an embodiment, the request message for requesting the context of the terminal 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; the device further comprises:

a determining unit 1406, configured to decide 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 solicited terminal context response message to the target base station under the condition that the anchor base station determines to migrate the context of the terminal, where the solicited terminal context response message carries the context of the terminal.

In an embodiment, in a case that the anchor base station determines not to migrate the context of the terminal, the first sending unit is configured to ask the target base station for a terminal context failure message, where the ask for terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of a mobility control parameter of the terminal.

Fig. 15 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device may be a network device, such as a target base station or an anchor base station, and the communication device 600 shown in fig. 15 includes a processor 610, and the processor 610 may call and execute 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. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into 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, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.

Optionally, the communication device 600 may specifically be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 600 may specifically be a mobile terminal/terminal according to this embodiment, and the communication device 600 may implement a corresponding process implemented by the mobile terminal/terminal in each method according to this embodiment, which is not described herein again for brevity.

Fig. 16 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 16 includes a processor 710, and the processor 710 can call and run a computer program from a memory 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. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal in the embodiment of the present application, and the chip may implement a corresponding process implemented by the mobile terminal/terminal in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 17 is a schematic block diagram of a communication system 900 according to an embodiment of the present application. As shown in fig. 17, the communication system 900 includes a terminal 910 and a network device 920.

The terminal 910 may be configured to implement the corresponding function implemented by the terminal in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, which is not described herein again for brevity.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. 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 may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising 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 enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims

A method of parameter configuration, the method comprising:

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

and the target base station sends the mobility control parameters of the terminal to an anchor base station or the terminal, wherein the anchor base station is a base station for storing the context of the terminal.
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 the target base station sends a request message for the context of the terminal to the anchor base station under the condition that the configuration information of the mobility control parameters of the terminal needs to be indicated to the anchor base station, wherein the request message for the context of the terminal carries the configuration information of the mobility control parameters of the terminal.
The method of claim 2, wherein the RRC recovery request message carries a first cause value indicating that a trigger cause of the RRC connection recovery procedure is a RAN notification area update, RNAU; the method further comprises the following steps:

and 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 based on the first cause value in the RRC recovery request message.
The method of claim 2 or 3, wherein, in the case that the anchor base station decides not to migrate the context of the terminal, the method further comprises:

the target base station receives a request terminal context failure message sent by the anchor base station, wherein the request terminal context failure message carries RRC release PDCP PDU which carries configuration information of a mobility control parameter of the terminal;

and 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 the configuration information of the mobility control parameters of the terminal.
The method of claim 2 or 3, wherein, in case the anchor base station decides to migrate the context of the terminal, the method further comprises:

the target base station receives a solicited terminal context response message sent by the anchor base station, wherein the solicited terminal context response message carries the context of the terminal;

and the target base station sends the RRC release message generated by the target base station to the terminal.
The method of claim 5, wherein the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.
The method of claim 1, wherein the method further comprises:

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

the target base station sends a solicited terminal context request message to the anchor base station, wherein the solicited terminal context request message carries a first cause value, and the first cause value is used for indicating that the trigger cause of the RRC connection recovery process is an RNAU.
The method according to claim 7, wherein the solicited terminal context request message further carries first indication information, and the first indication information is used for indicating that the target base station has mobility control parameters that need to be configured to the terminal.
The method of claim 7 or 8, wherein, in case the anchor base station decides not to migrate the context of the terminal, the method further comprises:

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

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

the target base station receives a request terminal context failure message sent by the anchor base station, wherein the request terminal context failure message carries RRC release PDCP PDU which carries configuration information of a mobility control parameter of the terminal;

and 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 the configuration information of the mobility control parameters of the terminal.
The method according to claim 7, wherein the solicited terminal context request message further carries second indication information, and the second indication information is used for indicating that the anchor base station needs to perform 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.
The method of claim 10, wherein in the case that the anchor base station decides to migrate the context of the terminal, the method further comprises:

the target base station receives a request terminal context response message sent by the anchor base station, wherein the terminal context response message carries the context of the terminal;

and the target base station sends the RRC release message generated by the target base station to the terminal.
The method of claim 11, wherein the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.
The method of claim 7, wherein, in the case that the anchor base station decides not to migrate the context of the terminal, the method further comprises:

the target base station receives a request terminal context failure message sent by the anchor base station, wherein the request terminal context failure message carries RRC release PDCP PDU which does not carry configuration information of a mobility control parameter of the terminal;

and 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 does not carry the configuration information of the mobility control parameters of the terminal.
The method according to any of claims 1 to 13, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

and 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 method according to any of claims 1 to 13, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

a third parameter, configured to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state;

and a fourth parameter, wherein the fourth parameter is an early measurement configuration parameter.
A method of parameter configuration, the method comprising:

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

the anchor base station sends a failure message of requesting the context of the terminal to the target base station under the condition that the context of the terminal is not transferred; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.
The method of claim 16, wherein the solicited terminal context request message carries configuration information of mobility control parameters of the terminal configured by the target base station;

under the condition that the anchor base station determines not to migrate the context of the terminal, 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;

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

ignoring configuration information of a mobility control parameter of the terminal configured from the target base station under the condition that the anchor base station decides to migrate the context of the terminal;

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.
The method of claim 16, wherein the solicited terminal context request message carries a first cause value indicating that a triggering cause of an RRC connection recovery procedure is an RNAU.
The method of claim 19, wherein the solicited 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 to the terminal.
The method of claim 19 or 20,

sending, by the anchor base station, a message requesting mobility control parameters or second indication information to the target base station when the anchor base station decides to migrate the context of the terminal, where the second indication information is used to indicate that the anchor base station does not migrate the context of the terminal;

the anchor base station receives the mobility control parameters of the terminal sent by the target base station, carries the configuration information of the mobility control parameters of the terminal configured by the target base station in 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.
The method of claim 19, wherein the solicitation for terminal context request message further carries second indication information, and the second indication information is used for indicating that the anchor base station needs to perform context migration of the terminal;

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

and under the condition that the anchor base station decides to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.
The method of claim 16, wherein the anchor base station asks the target base station for a terminal context failure message in case that the anchor base station decides not to migrate the context of the terminal, the ask for terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of mobility control parameters of the terminal.
The method according to any of claims 17 to 23, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

and 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 method according to any of claims 17 to 23, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

a third parameter, configured to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state;

and a fourth parameter, wherein the fourth parameter is an early measurement configuration parameter.
An apparatus for parameter configuration, applied to a target base station, the apparatus comprising:

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

a sending unit, configured to send the mobility control parameter of the terminal to an anchor base station or to the terminal, where the anchor base station is a base station that stores a context of the terminal.
The apparatus of claim 26, wherein the apparatus further comprises:

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

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

the sending unit is configured to send a solicited terminal context request message to the anchor base station, where the solicited terminal context request message carries configuration information of a mobility control parameter of the terminal.
The apparatus of claim 27, wherein the RRC recovery request message carries a first cause value indicating that a triggering cause of an RRC connection recovery procedure is an RNAU;

the determining unit is configured to determine that the configuration information of the mobility control parameter of the terminal needs to be indicated to the anchor base station based on the first cause value in the RRC recovery request message.
The apparatus of claim 27 or 28, wherein, in the case that the anchor base station decides not to migrate the context of the terminal, the apparatus further comprises:

a second receiving unit, configured to receive a solicited terminal context failure message sent by the anchor base station, where the solicited terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal;

the sending unit 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 a mobility control parameter of the terminal.
The apparatus according to claim 27 or 28, wherein, in case that the anchor base station decides to migrate the context of the terminal, the apparatus further comprises:

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

the sending unit is further configured to send the RRC release message generated by the sending unit to the terminal.
The apparatus of claim 30, wherein the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.
The apparatus of claim 26, wherein the apparatus further comprises:

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

the sending unit is further configured to send a solicited terminal context request message to the anchor base station, where the solicited terminal context request message carries a first cause value, and the first cause value is used to indicate that a trigger cause of an RRC connection recovery procedure is an RNAU.
The apparatus of claim 32, wherein the solicited 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 to the terminal.
The apparatus of claim 32 or 33, wherein, in the case that the anchor base station decides not to migrate the context of the terminal, the apparatus further comprises:

a third receiving unit, configured to receive a message requesting mobility control parameters 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 the context of the terminal;

the sending unit is configured to send the mobility control parameter of the terminal to the anchor base station;

a second receiving unit, configured to receive a solicited terminal context failure message sent by the anchor base station, where the solicited terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal;

the sending unit 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 a mobility control parameter of the terminal.
The apparatus of claim 32, wherein the solicitation for terminal context request message further carries second indication information, the second indication information indicating that the anchor base station needs to perform 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.
The apparatus of claim 35, wherein in a case where the anchor base station decides to migrate the context of the terminal, the apparatus further comprises:

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

the sending unit is configured to send the RRC release message generated by the sending unit to the terminal.
The apparatus of claim 36, wherein the RRC release message generated by the target base station itself carries configuration information of mobility control parameters of the terminal.
The apparatus of claim 32, wherein, in the case that the anchor base station decides not to migrate the context of the terminal, the apparatus further comprises:

a second receiving unit, configured to receive a solicited terminal context failure message sent by the anchor base station, where the solicited terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of a mobility control parameter of the terminal;

the sending unit is configured to send an RRC release message to the terminal according to the RRC release PDCP PDU, where the RRC release message does not carry configuration information of a mobility control parameter of the terminal.
The apparatus of any of claims 26 to 38, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

and 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 apparatus of any of claims 26 to 38, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

a third parameter, configured to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state;

and a fourth parameter, wherein the fourth parameter is an early measurement configuration parameter.
An apparatus for parameter configuration, applied to an anchor base station, the apparatus comprising:

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

a first sending unit, configured to send a message of requesting a context failure of a terminal to the target base station when the anchor base station determines not to migrate the context of the terminal; and under the condition that the anchor base station determines to migrate the context of the terminal, sending a solicited terminal context response message to the target base station, wherein the solicited terminal context response message carries the context of the terminal.
The apparatus of claim 41, wherein the solicited terminal context request message carries configuration information for mobility control parameters of the terminal configured by the target base station;

the device further comprises: a generating unit, configured to, under a condition that the anchor base station determines not to migrate the context of the terminal, carry configuration information of a mobility control parameter 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 is configured to send a solicited terminal context failure message to the target base station, where the solicited terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal.
The apparatus of claim 41, wherein the solicited terminal context request message carries configuration information for mobility control parameters of the terminal configured by the target base station;

the first sending unit is configured to ignore configuration information of a mobility control parameter of the terminal, which is configured by the target base station, when the anchor base station determines to migrate the context of the terminal; and 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.
The apparatus of claim 41, wherein the solicitation terminal context request message carries a first cause value indicating that a triggering cause of an RRC connection recovery procedure is an RNAU.
The apparatus of claim 44, wherein the solicited 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 to the terminal.
The apparatus of claim 44 or 45, wherein the apparatus further comprises:

a second sending unit, configured to send a message requesting mobility control parameters or second indication information to the target base station when the anchor base station determines 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;

a generating unit, configured to carry configuration information of the mobility control parameter 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 is configured to send a solicited terminal context failure message to the target base station, where the solicited terminal context failure message carries the RRC release PDCP PDU, and the RRC release PDCP PDU carries configuration information of a mobility control parameter of the terminal.
The apparatus of claim 44, wherein the solicitation for terminal context request message further carries second indication information indicating that the anchor base station needs to perform context migration for the terminal; the device further comprises:

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

the first sending unit is configured to send a solicited terminal context response message to the target base station under the condition that the anchor base station determines to migrate the context of the terminal, where the solicited terminal context response message carries the context of the terminal.
The apparatus of claim 41, wherein in a case that the anchor base station decides not to migrate the context of the terminal, the first sending unit is configured to ask the target base station for a terminal context failure message, where the ask for terminal context failure message carries an RRC release PDCP PDU, and the RRC release PDCP PDU does not carry configuration information of a mobility control parameter of the terminal.
The apparatus of any of claims 42 to 48, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

and 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 apparatus of any of claims 42 to 48, wherein the mobility control parameters of the terminal comprise at least one of:

the first parameter is used for indicating the frequency point information and RAT information which are preferentially selected after the terminal enters an idle state or a non-activated state;

the second parameter is used for indicating the frequency priority information for executing cell selection and reselection after the terminal enters an idle state or a non-activated state;

a third parameter, configured to indicate low-priority frequency information or RAT information after the terminal enters an idle state or an inactive state;

and a fourth parameter, wherein the fourth parameter is an early measurement configuration parameter.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory, to perform the method of any of claims 1 to 15, or to perform the method of any of claims 16 to 25.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1 to 15, or the method of any of claims 16 to 25.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any of claims 1 to 15 or the method of any of claims 16 to 25.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 1 to 15 or the method of any of claims 16 to 25.
A computer program for causing a computer to perform the method of any one of claims 1 to 15 or the method of any one of claims 16 to 25.