Mobility management method, device and equipment

Abstract

The invention provides a mobility management method, device and equipment, and the method comprises the steps: configuring first parameter information; wherein the first parameter information is used for identifying whether the first network equipment supports RedCap or not; sending the first parameter information; wherein the first parameter information comprises any one of the following items: newly added information in a defined field; the frequency domain position is located in information of a target frequency band; identification information located at a first target time domain position; and a second target time domain position which is not filled. According to the scheme, whether the first network equipment supports the RedCap capability or not can be determined through the first parameter information configuration (including the capability identified through newly added information and the capability indicated through special parameter configuration); therefore, the problem that a ping-pong phenomenon occurs between the 4G network and the 5G network due to the fact that the terminal is switched from the 4G cell or redirected to the 5G cell which does not support RedCap is avoided, and the mobility management performance between systems is optimized.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a mobility management method, device and equipment. Background Art

[0002] In the 3rd generation partnership project (3GPP) release (R) 17 stage, RedCap (Reduced Capability) terminals can only access cells that support RedCap capabilities. When a dual-mode terminal that supports both 4G and 5G RedCap capabilities accesses the LTE (4G) network, mobility may trigger switching from the LTE cell or redirecting to the NR (i.e., 5G) cell; however: at this time, the LTE cell does not know whether the current dual-mode terminal supports RedCap but only knows that the current terminal supports 5G, and the terminal does not know whether the measured 5G cell supports RedCap; when the target NR cell does not support RedCap capabilities, terminal switching or redirection failures (such as voice service interruption, data service interruption, etc.) will occur, and the terminal can only re-establish or re-access the LTE network. The 4G network will initiate switching or redirection again based on the terminal's support for 5G capabilities, and then cause the terminal to ping-pong between the 4G and 5G networks, seriously affecting the user experience.

[0003] From the above, the LTE cell does not know whether the switching or redirection target NR cell measured by the current terminal supports RedCap. When the target NR cell does not support RedCap capability, the terminal will be disconnected from the network after the switching or redirection process is completed (such as voice service interruption, data service interruption, etc.), and the terminal will experience ping-pong between the 4G and 5G networks, reducing the inter-system mobility management performance. Summary of the invention

[0004] The purpose of the present invention is to provide a mobility management method, device and equipment to solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management solution in the prior art.

[0005] In order to solve the above technical problem, an embodiment of the present invention provides a mobility management method, which is applied to a first network device, including:

[0006] Configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0007] Sending the first parameter information;

[0008] The first parameter information includes any one of the following:

[0009] Added information in defined fields;

[0010] Information that the frequency domain position is in the target frequency band;

[0011] Identification information located at the first target time domain position;

[0012] Unfilled second target temporal position.

[0013] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0014] Optionally, the defined field is a master information block (MIB) field;

[0015] The sending the first parameter information includes:

[0016] The first parameter information is sent through broadcasting.

[0017] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0018] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0019] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0020] The embodiment of the present invention further provides a mobility management method, which is applied to a terminal and includes:

[0021] Acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0022] Performing mobility management according to the first parameter information;

[0023] The first parameter information includes any one of the following:

[0024] Added information in defined fields;

[0025] Information that the frequency domain position is in the target frequency band;

[0026] Identification information located at the first target time domain position;

[0027] Unfilled second target temporal position.

[0028] Optionally, performing mobility management according to the first parameter information includes:

[0029] When all the first parameter information obtained indicates that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device;

[0030] When at least one first parameter information indicates that the first network device supports RedCap, first information is sent to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0031] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0032] Optionally, the defined field is a master information block (MIB) field;

[0033] The obtaining of first parameter information sent by at least one first network device includes:

[0034] Acquire first parameter information sent by at least one first network device through broadcasting.

[0035] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0036] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0037] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0038] The embodiment of the present invention further provides a mobility management method, which is applied to a second network device, comprising:

[0039] receiving first information sent by a terminal;

[0040] Determine, according to the first information, a first network device to be accessed by the terminal;

[0041] The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

[0042] The embodiment of the present invention further provides a mobility management device, which is applied to a first network device and includes:

[0043] A first configuration module, configured to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0044] A first sending module, used for sending the first parameter information;

[0045] The first parameter information includes any one of the following:

[0046] Added information in defined fields;

[0047] Information that the frequency domain position is in the target frequency band;

[0048] Identification information located at the first target time domain position;

[0049] Unfilled second target temporal position.

[0050] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0051] Optionally, the defined field is a master information block (MIB) field;

[0052] The sending the first parameter information includes:

[0053] The first parameter information is sent through broadcasting.

[0054] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0055] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0056] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0057] The embodiment of the present invention further provides a mobility management device, applied to a terminal, comprising:

[0058] A first acquisition module, configured to acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0059] A first processing module, configured to perform mobility management according to the first parameter information;

[0060] The first parameter information includes any one of the following:

[0061] Added information in defined fields;

[0062] Information that the frequency domain position is in the target frequency band;

[0063] Identification information located at the first target time domain position;

[0064] Unfilled second target temporal position.

[0065] Optionally, performing mobility management according to the first parameter information includes:

[0066] When all the first parameter information obtained indicates that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device;

[0067] When at least one first parameter information indicates that the first network device supports RedCap, first information is sent to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0068] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0069] Optionally, the defined field is a master information block (MIB) field;

[0070] The obtaining of first parameter information sent by at least one first network device includes:

[0071] Acquire first parameter information sent by at least one first network device through broadcasting.

[0072] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0073] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0074] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0075] The embodiment of the present invention further provides a mobility management device, which is applied to a second network device, including:

[0076] A first receiving module, used for receiving first information sent by a terminal;

[0077] A first determining module, configured to determine a first network device to be accessed by the terminal according to the first information;

[0078] The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

[0079] The embodiment of the present invention further provides a mobility management device, the mobility management device is a first network device, comprising: a processor and a transceiver;

[0080] The processor is used to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0081] Sending the first parameter information through the transceiver;

[0082] The first parameter information includes any one of the following:

[0083] Added information in defined fields;

[0084] Information that the frequency domain position is in the target frequency band;

[0085] Identification information located at the first target time domain position;

[0086] Unfilled second target temporal position.

[0087] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0088] Optionally, the defined field is a master information block (MIB) field;

[0089] The sending the first parameter information includes:

[0090] The first parameter information is sent through broadcasting.

[0091] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0092] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0093] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0094] The embodiment of the present invention further provides a mobility management device, wherein the mobility management device is a terminal, and includes: a processor;

[0095] The processor is used to obtain first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0096] Performing mobility management according to the first parameter information;

[0097] The first parameter information includes any one of the following:

[0098] Added information in defined fields;

[0099] Information that the frequency domain position is in the target frequency band;

[0100] Identification information located at the first target time domain position;

[0101] Unfilled second target temporal position.

[0102] Optionally, performing mobility management according to the first parameter information includes:

[0103] When all the first parameter information obtained indicates that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device;

[0104] When at least one first parameter information indicates that the first network device supports RedCap, first information is sent to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0105] Optionally, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0106] Optionally, the defined field is a master information block (MIB) field;

[0107] The obtaining of first parameter information sent by at least one first network device includes:

[0108] Acquire first parameter information sent by at least one first network device through broadcasting.

[0109] Optionally, the information whose frequency domain position is located in the target frequency band is synchronization signal block SSB information;

[0110] And / or, the identification information is a synchronization signal block identifier SSB ID;

[0111] And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0112] The embodiment of the present invention further provides a mobility management device, which is a second network device and includes: a processor and a transceiver;

[0113] The processor is configured to receive, through the transceiver, first information sent by a terminal;

[0114] Determine, according to the first information, a first network device to be accessed by the terminal;

[0115] The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

[0116] The embodiment of the present invention further provides a mobility management device, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the mobility management method on the first network device side is implemented; or,

[0117] When the processor executes the program, the mobility management method on the second network device side is implemented.

[0118] An embodiment of the present invention further provides a terminal, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the above-mentioned terminal-side mobility management method is implemented.

[0119] An embodiment of the present invention further provides a readable storage medium on which a program is stored. When the program is executed by a processor, the program implements the steps in the mobility management method on the first network device side, the terminal side or the second network device side.

[0120] The beneficial effects of the above technical solution of the present invention are as follows:

[0121] In the above scheme, the mobility management method configures the first parameter information; sends the first parameter information; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; wherein the first parameter information includes any one of the following: new information in the defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; can support the configuration of the first parameter information (including identifying the capability through the new information and indicating the capability through the special parameter configuration) to clarify whether the first network device supports the RedCap capability, and then support avoiding the problem of ping-pong phenomenon between the 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0122] Figure 1The mobility management method according to the embodiment of the present invention is shown in FIG. Figure 1 ;

[0123] Figure 2 The mobility management method according to the embodiment of the present invention is shown in FIG. Figure 2 ;

[0124] Figure 3 The mobility management method according to the embodiment of the present invention is shown in FIG. Figure 3 ;

[0125] Figure 4 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 1 ;

[0126] Figure 5 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 2 ;

[0127] Figure 6 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 3 ;

[0128] Figure 7 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 1 ;

[0129] Figure 8 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 2 ;

[0130] Fig. 9 The structure of the mobility management device of the embodiment of the present invention is shown in FIG. Figure 3 . DETAILED DESCRIPTION

[0131] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0132] The following first introduces the relevant contents of this plan.

[0133] The RedCap (Reduced Capability) technology was introduced in the R (version) 17 stage, and a new terminal type, namely the RedCap terminal, appeared. The network needs to be upgraded to R17 and above.

[0134] At the current stage, the network is based on 4G and 5G, supplemented by 2G networks. Taking the current network as an example, the existing network terminals include 2G only, 2G+4G, and 2G+4G+5G. Among them, when the terminal moves, it will interoperate between 2G and 4G and 4G and 5G networks. Taking the interoperation between 4G and 5G networks as an example, the terminals between 4G and 5G networks have the following behaviors:

[0135] 1.5G->4G reselection (idle state);

[0136] Meet the threshold for starting measurement of different frequencies and systems;

[0137] 2.4G–>5G reselection (idle state);

[0138] Meet the threshold for starting measurement of different frequencies or systems;

[0139] 3.4G–5G redirection;

[0140] Supports coverage-based redirection for different frequencies or systems, including measurement-based redirection and blind redirection after measurement failure:

[0141] 1) Blind redirection: When the UE moves to the edge of the cell coverage, the gNodeB (base station) does not receive the heterogeneous system measurement report message but (the base station) receives the blind A2 (i.e. event A2) report, (the terminal) needs to be redirected to other heterogeneous system cells as soon as possible. Among them, event A2 means: the serving cell is below an absolute threshold.

[0142] 2) Measurement-based redirection: When the UE moves to the edge of the cell coverage, the gNodeB receives a report on poor signal quality of the cell (the cell where the UE is located) triggered by A2, starts hetero-frequency or hetero-system measurement, and after measuring the hetero-frequency or hetero-system neighboring cells, initiates redirection to the target neighboring cell (turns the switch off).

[0143] Specifically, the switching between 4G and 5G includes the following steps:

[0144] Step 1-4 (measurement phase): The UE establishes a connection in the LTE (4G) cell, and the eNodeB configures an A2 measurement event for the UE. After the UE measures and satisfies the A2 (measurement) event, the eNodeB configures the B1 and / or B2 events based on the RAT (radio access technology) to the UE. After the UE measures and satisfies the B1 and / or B2 events, it reports a measurement report of the B1 and / or B2 events; wherein, event B1 means: the neighboring cell of the different system is better than an absolute threshold; event B2 means: the serving cell is lower than an absolute threshold threshold1, and the neighboring cell of the different system is better than an absolute threshold threshold2.

[0145] Step 5-6 (decision stage): gNodeB filters the neighboring cell information in the measurement report and sends an RRC release (radio resource control release) message to the UE;

[0146] Step 7-9 (execution phase): The UE initiates a random access procedure to the target cell and then resides on the target cell.

[0147] Based on the above, the present invention aims at the problem that the ping-pong phenomenon occurs between terminals in different systems (4G and 5G) in the mobility management solution of the existing technology, and provides a mobility management method applied to a first network device, such as Figure 1 As shown, including:

[0148] Step 11: configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0149] Step 12: Send the first parameter information; wherein the first parameter information includes any one of the following: new information in a defined field; information in the frequency domain position located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position.

[0150] Among them, the first network device can be implemented as a 5G cell device, but is not limited to this.

[0151] The mobility management method provided in an embodiment of the present invention configures the first parameter information; sends the first parameter information; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; wherein the first parameter information includes any one of the following: new information in a defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; can support the configuration of the first parameter information (including identifying the capability through the new information and indicating the capability through the special parameter configuration) to clarify whether the first network device supports the RedCap capability, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and well solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art.

[0152] In which, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0153] In this way, the version information of RedCap supported by the first network device can be made clear.

[0154] In the embodiment of the present invention, the defined field is a master information block (MIB) field; and the sending of the first parameter information includes: sending the first parameter information via broadcasting.

[0155] This can support accurate transmission of the first parameter information.

[0156] Among them, the information that the frequency domain position is located in the target frequency band is the synchronization signal block SSB information; and / or the identification information is the synchronization signal block identifier SSB ID; and / or the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0157] In this way, the relevant content of the first parameter information can be clarified.

[0158] The embodiment of the present invention also provides a mobility management method, which is applied to a terminal, such as Figure 2 As shown, including:

[0159] Step 21: Acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0160] Step 22: Perform mobility management according to the first parameter information; wherein the first parameter information includes any one of the following: new information in a defined field; information in the frequency domain position located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position.

[0161] The mobility management method provided in an embodiment of the present invention obtains first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; mobility management is performed according to the first parameter information; wherein the first parameter information includes any one of the following: new information in a defined field; information whose frequency domain position is located in a target frequency band; identification information located at a first target time domain position; an unfilled second target time domain position; and can support the configuration of the first parameter information (including identifying the capability through new information and indicating the capability through special parameter configuration) to clarify whether the first network device supports the RedCap capability, thereby supporting the avoidance of the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from a 4G cell to a 5G cell that does not support RedCap, optimizing the inter-system mobility management performance, and well solving the problem of ping-pong phenomenon between terminals in different systems (4G and 5G) in the mobility management scheme in the prior art.

[0162] Among them, the mobility management based on the first parameter information includes: item (1) when all the first parameter information obtained indicate that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same (network) system as the currently connected network device; item (2) when at least one first parameter information indicates that the first network device supports RedCap, sending first information to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0163] In this way, mobility management can be performed accurately. Item (1) can be specifically implemented as follows: maintaining the same-frequency or different-frequency measurement in the current 4G cell or the 4G cell sending system, and moving to other 4G cells; Item (2) can be specifically implemented as follows: only reporting the 5G cell information and measurement results that support RedCap; the first information can be a measurement report of the 5G cell or carried in the measurement report of the 5G cell, but is not limited to this.

[0164] In the embodiment of the present invention, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0165] In this way, the version information of RedCap supported by the first network device can be made clear.

[0166] In the embodiment of the present invention, the defined field is a master information block (MIB) field; the obtaining of first parameter information sent by at least one first network device includes: obtaining first parameter information sent by at least one first network device via broadcast.

[0167] This can support accurate transmission of the first parameter information.

[0168] Among them, the information that the frequency domain position is located in the target frequency band is the synchronization signal block SSB information; and / or the identification information is the synchronization signal block identifier SSB ID; and / or the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0169] In this way, the relevant content of the first parameter information can be clarified.

[0170] The embodiment of the present invention also provides a mobility management method, which is applied to a second network device, such as Figure 3 As shown, including:

[0171] Step 31: receiving first information sent by a terminal;

[0172] Step 32: Determine the first network device to be accessed by the terminal according to the first information; wherein the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0173] The first network device may be implemented as a 4G cell device, but is not limited thereto. Step 32 may be exemplified as follows: the 4G cell determines which 5G cell the terminal moves to based on MR (measurement report) information.

[0174] The mobility management method provided in an embodiment of the present invention receives the first information sent by the terminal; determines the first network device to be accessed by the terminal according to the first information; wherein the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap; can support the implementation of clearly supporting the first network device supporting RedCap through the first information, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal being switched or redirected from the 4G cell (second network device) to the 5G cell (first network device) that does not support RedCap, optimizes the inter-system mobility management performance, and well solves the problem of ping-pong phenomenon between terminals in different systems (4G and 5G) in the mobility management scheme in the prior art.

[0175] The mobility management method provided in an embodiment of the present invention is illustrated below by taking a 5G network device (5G cell) as an example of the first network device and a 4G network device (4G cell) as an example of the second network device.

[0176] In response to the above technical problems, an embodiment of the present invention provides a mobility management method, which can be specifically implemented as a cell feature identification solution, involving: a method for the network to identify its own unique capabilities (corresponding to the above-mentioned first parameter information including newly added information in a defined field) or a method for solving inter-system mobility management through special parameter configuration (corresponding to the above-mentioned first parameter information including: information that the frequency domain position is located in the target frequency band, identification information located at the first target time domain position, and / or an unfilled second target time domain position) to ensure the continuity and reliability of the terminal during the inter-system movement process.

[0177] The specific scheme of the embodiment of the present invention is introduced below.

[0178] Solution 1:

[0179] A dedicated identifier (corresponding to the above-mentioned newly added information) is added to the broadcast information of the higher protocol version (R17 and above) to ensure that the terminal can accurately evaluate whether the measured cell supports or matches the terminal's proprietary or special technical capabilities when measuring in a different system.

[0180] Embodiment 1:

[0181] 1. Negotiate with the terminal, use the reserved field or the idle field in the MIB of the 5G cell and define whether RedCap is supported (corresponding to the above-mentioned first parameter information, such as: 1bit information, 0 means RedCap is not supported, 1 means RedCap is supported), and the RedCap version (corresponding to the above-mentioned version information, such as: 1bit information, 0 means R17 RedCap, 1 means R18 RedCap); the terminal can confirm whether the current 5G cell supports RedCap and the protocol version information of RedCap (i.e. version information) according to the information in the MIB; the network can send the field (i.e. the field carrying the first parameter information) in the MIB in all SSB (synchronization signal block) beams or send the field in the MIB in one or several SSB beams;

[0182] 2. After the dual-mode or multi-mode terminal (specifically RedCap terminal) accesses the 4G cell, due to mobility or service requirements, 4G (cell) sends out inter-system measurements, and the terminal measures the 5G cell (parses the MIB; that is, measures and parses the MIB sent by the 5G cell), and obtains several 5G cells:

[0183] a. The MIB indications of all 5G cells are that RedCap is not supported. At this time, the terminal does not report MEASUREMENTREPORT, maintains the same-frequency or different-frequency measurement in the current 4G cell or the 4G cell sending system, and moves to other 4G cells (corresponding to the above-mentioned situation where all the first parameter information obtained indicates that the first network device does not support RedCap, maintains the network device currently accessed by the terminal or moves to another network device in the same system as the currently accessed network device);

[0184] b. The MIB of some cells indicates that RedCap is supported, while the MIB of some cells indicates that RedCap is not supported. At this time, the terminal MEASUREMENT REPORT (measurement report) only reports the 5G cell information and measurement results that support RedCap (corresponding to the above-mentioned sending of the first information to the second network device when at least one first parameter information indicates that the first network device supports RedCap; the first information includes: information of the first network device that supports RedCap, and measurement results for the first network device that supports RedCap), and the 4G cell determines which 5G cell the terminal moves to according to the MR (measurement report) information (corresponding to the above-mentioned determination of the first network device to be accessed by the terminal according to the first information);

[0185] From the above, this solution involves: the 5G cell configures the first parameter information, the first parameter information is used to identify (or indicate) whether the 5G cell supports the RedCap capability; the first parameter information is sent; the terminal identifies the 5G cell that supports RedCap and reports it to the 4G cell; the 4G cell determines the target 5G cell.

[0186] Option 2:

[0187] By configuring special parameter information in the cell of a high protocol version (R17 and above) (corresponding to the information that the above-mentioned frequency domain position is located in the target frequency band, the identification information located in the first target time domain position; and / or, the unfilled second target time domain position), the technical capability differences caused by different protocol versions can be distinguished to ensure that the terminal can accurately evaluate whether the measured or accessed cell supports or matches the terminal's proprietary or special technical capabilities. The parameter configuration method adopted by the network in this solution also needs to be negotiated with the terminal in advance (for example, "the information that the frequency domain position is located in the target frequency band" is used to identify whether the first network device supports RedCap).

[0188] Embodiment 1:

[0189] a. Before upgrading the 5G R15 or R16 cell to the R17 version, configure the frequency domain position of the SSB of the 5G R15 or R16 cell to a low frequency (2515-2535MHz of n (i.e. 5G) 41), and configure the frequency domain position of the SSB of the 5G R17 cell to a high frequency (2595-2615MHz of n41). The terminal determines whether the current cell supports RedCap based on the measured SSB frequency domain position;

[0190] b. Before the 5G R17 cell is upgraded to the R18 version, the frequency domain position of the SSB of the 5G R17 cell is configured at a high frequency (2595-2615MHz of n41), and the frequency domain position of the SSB of the 5G R18 cell is configured at a low frequency (2515-2535MHz of n41). The terminal determines whether the current cell supports RedCap based on the measured SSB frequency domain position;

[0191] The above a and b correspond to the above first parameter information including: information that the frequency domain position is located in the target frequency band. The setting conditions of a and b (such as before the 5G R15 or R16 cell is upgraded to the R17 version) can be expressed as: before the first version cell switches to the second version cell, where the second version cell has stronger protocol capabilities; there is a generation gap between the protocol versions;

[0192] c. After the dual-mode or multi-mode terminal (specifically, the RedCap terminal) accesses the 4G cell, due to mobility or business requirements, the 4G (cell) sends an inter-system measurement, and the terminal measures the 5G cell (specifically measures the SSB configuration sent by the 5G cell), and obtains several 5G cells by measurement; the terminal identifies the protocol capability of the measured cell (including whether it supports RedCap) through the SSB configuration, and at this time the terminal MEASUREMENT REPORT only reports the 5G cell information and measurement results that support RedCap (corresponding to the above-mentioned sending of the first information to the second network device when at least one first parameter information indicates that the first network device supports RedCap; the first information includes: information of the first network device that supports RedCap, and the measurement result of the first network device that supports RedCap), and the 4G cell determines which 5G cell the terminal moves to based on the MR information (corresponding to the above-mentioned determination of the first network device to be accessed by the terminal based on the first information).

[0193] Embodiment 2:

[0194] a. Before the 5G R15 or R16 cell is upgraded to the R17 version, the SSB ID of the 5G R17 cell and the transmitted time domain position (fixed downlink time slot DL slot) are jointly bound, and the special SSB ID at a specific time domain position (corresponding to the identification information at the first target time domain position) is used to indicate that the current cell supports the R17 RedCap capability;

[0195] b. Before the 5G R17 cell is upgraded to the R18 version, the SSB ID of the 5G R18 cell and the transmitted time domain position (fixed DL slot) are jointly bound, and the special SSB ID of the specific time domain position (corresponding to the identification information located at the first target time domain position) is used to indicate that the current cell supports the R18 RedCap capability; or, maintain step a, and the special marking of the R17 cell (that is, the special SSB ID of the specific time domain position is used to indicate that the current cell supports the R17 RedCap capability), and the cell without special marking is the R18 RedCap cell (corresponding to the above-mentioned unfilled second target time domain position);

[0196] The setting conditions of a and b above (such as before the 5G R15 or R16 cell is upgraded to R17) can be expressed as: before the first version cell is switched to the second version cell, where the second version cell has stronger protocol capability; there is a generation gap between the protocol versions;

[0197] c. After the dual-mode or multi-mode terminal (specifically, the RedCap terminal) accesses the 4G cell, due to mobility or service requirements, the 4G (cell) sends an inter-system measurement, and the terminal measures the 5G cell (specifically measures the SSB configuration sent by the 5G cell - the special SSB ID at a specific time domain position), and obtains several 5G cells by measurement; the terminal identifies the protocol capability of the measured cell (including whether it supports RedCap) through the SSB configuration, and at this time, the terminal MEASUREMENT REPORT only reports the 5G cell information and measurement results that support RedCap (corresponding to the above-mentioned sending of the first information to the second network device when at least one first parameter information indicates that the first network device supports RedCap; the first information includes: information of the first network device that supports RedCap, and the measurement result for the first network device that supports RedCap), and the 4G cell determines which 5G cell the terminal moves to based on the MR information (corresponding to the above-mentioned determination of the first network device to be accessed by the terminal based on the first information).

[0198] Based on the above, the solution provided by the embodiment of the present invention involves the following contents:

[0199] 1. The method of adding key fields to the broadcast information to identify the network's own exclusive capabilities: add an exclusive identifier in the broadcast information of the high-protocol version to identify whether the network itself supports RedCap, and can also identify the RedCap version. After the RedCap terminal measures in a different system, it can only report the 5G cell information and measurement results that support RedCap in the measurement report.

[0200] 2. Method of identifying the network's own exclusive capabilities through special parameter configuration: by configuring special SSB parameter information (including special time domain positions and special frequency domain positions) in high-protocol version cells, to distinguish the technical capability differences caused by different protocol versions: whether RedCap is supported, this information can also indicate the RedCap version. After the RedCap terminal is measured in a different system, it can only report the 5G cell information and measurement results that support RedCap in the measurement report. This method improves the inter-system mobility defects of the RedCap terminal by clearly distinguishing the key capability differences in different version stages within the network, ensuring that the terminal does not go offline, and to a certain extent ensuring business continuity.

[0201] In summary, compared with the prior art, this solution has the following advantages:

[0202] 1. Clearly distinguish the key capabilities of different versions of network internal factors;

[0203] 2. Clarified the network version stage;

[0204] 3. Improved the inter-system mobility defects of RedCap terminals, ensuring that the terminals will not be disconnected from the network, and to a certain extent, ensuring business continuity.

[0205] The embodiment of the present application also provides a mobility management device, which is applied to a first network device, such as Figure 4 As shown, including:

[0206] A first configuration module 41 is used to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0207] A first sending module 42, configured to send the first parameter information;

[0208] The first parameter information includes any one of the following:

[0209] Added information in defined fields;

[0210] Information that the frequency domain position is in the target frequency band;

[0211] Identification information located at the first target time domain position;

[0212] Unfilled second target temporal position.

[0213] The mobility management device provided in an embodiment of the present invention configures the first parameter information; sends the first parameter information; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; wherein the first parameter information includes any one of the following: new information in a defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; can support the configuration of the first parameter information (including identifying the capability through the new information and indicating the capability through the special parameter configuration) to clarify whether the first network device supports the RedCap capability, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and well solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art.

[0214] In which, when the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

[0215] In the embodiment of the present application, the defined field is a master information block MIB field; the sending of the first parameter information includes: sending the first parameter information via broadcasting.

[0216] In an embodiment of the present application, the information that the frequency domain position is located in the target frequency band is synchronization signal block SSB information; and / or, the identification information is a synchronization signal block identifier SSB ID; and / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0217] Among them, the implementation embodiments of the mobility management method on the first network device side are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0218] The present application also provides a mobility management device, which is applied to a terminal, such as Figure 5 As shown, including:

[0219] A first acquisition module 51 is used to acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0220] A first processing module 52, configured to perform mobility management according to the first parameter information;

[0221] The first parameter information includes any one of the following:

[0222] Added information in defined fields;

[0223] Information that the frequency domain position is in the target frequency band;

[0224] Identification information located at the first target time domain position;

[0225] Unfilled second target temporal position.

[0226] The mobility management device provided in an embodiment of the present invention obtains the first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; mobility management is performed according to the first parameter information; wherein the first parameter information includes any one of the following items: new information in a defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; it can support the configuration of the first parameter information (including identifying the capability through new information and indicating the capability through special parameter configuration) to clarify whether the first network device supports the RedCap capability, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and well solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art.

[0227] Among them, the mobility management based on the first parameter information includes: (1) when all the first parameter information obtained indicate that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device; (2) when at least one first parameter information indicates that the first network device supports RedCap, sending first information to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0228] In the embodiment of the present application, when the first parameter information indicates that the first network device supports RedCap, the first parameter information is also used to identify the version information of the RedCap.

[0229] The defined field is a master information block (MIB) field; and obtaining the first parameter information sent by at least one first network device includes: obtaining the first parameter information sent by at least one first network device via broadcast.

[0230] In an embodiment of the present application, the information that the frequency domain position is located in the target frequency band is synchronization signal block SSB information; and / or, the identification information is a synchronization signal block identifier SSB ID; and / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0231] Among them, the implementation embodiments of the above-mentioned terminal-side mobility management method are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0232] The present application also provides a mobility management device, which is applied to a second network device, such as Figure 6 As shown, including:

[0233] A first receiving module 61, configured to receive first information sent by a terminal;

[0234] A first determining module 62, configured to determine a first network device to be accessed by the terminal according to the first information;

[0235] The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

[0236] The mobility management device provided in an embodiment of the present invention receives the first information sent by the terminal; determines the first network device to be accessed by the terminal according to the first information; wherein the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap; can support the implementation of clearly supporting the first network device supporting RedCap through the first information, and then support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal being switched or redirected from the 4G cell (second network device) to the 5G cell (first network device) that does not support RedCap, optimizes the mobility management performance between systems, and well solves the problem of ping-pong phenomenon between terminals in different systems (4G and 5G) in the mobility management scheme in the prior art.

[0237] Among them, the implementation embodiments of the mobility management method on the second network device side are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0238] The embodiment of the present application further provides a mobility management device, wherein the mobility management device is a first network device, such as Figure 7 As shown, it includes: a processor 71 and a transceiver 72;

[0239] The processor 71 is used to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0240] Sending the first parameter information via the transceiver 72;

[0241] The first parameter information includes any one of the following:

[0242] Added information in defined fields;

[0243] Information that the frequency domain position is in the target frequency band;

[0244] Identification information located at the first target time domain position;

[0245] Unfilled second target temporal position.

[0246] The mobility management device provided in an embodiment of the present invention configures the first parameter information; sends the first parameter information; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; wherein the first parameter information includes any one of the following: new information in a defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; can support the configuration of the first parameter information (including identifying the capability through the new information and indicating the capability through the special parameter configuration) to clarify whether the first network device supports the RedCap capability, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and well solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art.

[0247] In the embodiment of the present application, when the first parameter information indicates that the first network device supports RedCap, the first parameter information is also used to identify the version information of the RedCap.

[0248] The defined field is a master information block (MIB) field; and sending the first parameter information includes: sending the first parameter information via broadcasting.

[0249] In an embodiment of the present application, the information that the frequency domain position is located in the target frequency band is synchronization signal block SSB information; and / or, the identification information is a synchronization signal block identifier SSB ID; and / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0250] Among them, the implementation embodiments of the mobility management method on the first network device side are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0251] The embodiment of the present application also provides a mobility management device, wherein the mobility management device is a terminal, such as Figure 8 As shown, it includes: a processor 81;

[0252] The processor 81 is configured to obtain first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap;

[0253] Performing mobility management according to the first parameter information;

[0254] The first parameter information includes any one of the following:

[0255] Added information in defined fields;

[0256] Information that the frequency domain position is in the target frequency band;

[0257] Identification information located at the first target time domain position;

[0258] Unfilled second target temporal position.

[0259] Among them, in the embodiment of the present invention, of course, it can also include: a transceiver 82 capable of communicating with the processor 81, but it is not limited to this.

[0260] The mobility management device provided in an embodiment of the present invention obtains the first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports the reduced capability RedCap; mobility management is performed according to the first parameter information; wherein the first parameter information includes any one of the following items: new information in a defined field; information whose frequency domain position is located in the target frequency band; identification information located at the first target time domain position; unfilled second target time domain position; it can support the configuration of the first parameter information (including identifying the capability through new information and indicating the capability through special parameter configuration) to clarify whether the first network device supports the RedCap capability, and further support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal switching or redirecting from the 4G cell to the 5G cell that does not support RedCap, optimize the inter-system mobility management performance, and well solve the problem of ping-pong phenomenon between terminals of different systems (4G and 5G) in the mobility management scheme in the prior art.

[0261] Among them, the mobility management based on the first parameter information includes: (1) when all the first parameter information obtained indicate that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device; (2) when at least one first parameter information indicates that the first network device supports RedCap, sending first information to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

[0262] In the embodiment of the present application, when the first parameter information indicates that the first network device supports RedCap, the first parameter information is also used to identify the version information of the RedCap.

[0263] The defined field is a master information block (MIB) field; and obtaining the first parameter information sent by at least one first network device includes: obtaining the first parameter information sent by at least one first network device via broadcast.

[0264] In an embodiment of the present application, the information that the frequency domain position is located in the target frequency band is synchronization signal block SSB information; and / or, the identification information is a synchronization signal block identifier SSB ID; and / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

[0265] Among them, the implementation embodiments of the above-mentioned terminal-side mobility management method are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0266] The embodiment of the present application also provides a mobility management device, wherein the mobility management device is a second network device, such as Fig. 9 As shown, it includes: a processor 91 and a transceiver 92;

[0267] The processor 91 is configured to receive first information sent by a terminal through the transceiver 92;

[0268] Determine, according to the first information, a first network device to be accessed by the terminal;

[0269] The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

[0270] The mobility management device provided in an embodiment of the present invention receives the first information sent by the terminal; determines the first network device to be accessed by the terminal according to the first information; wherein the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap; can support the implementation of clearly supporting the first network device supporting RedCap through the first information, and then support avoiding the problem of ping-pong phenomenon between 4G and 5G networks caused by the terminal being switched or redirected from the 4G cell (second network device) to the 5G cell (first network device) that does not support RedCap, optimizes the inter-system mobility management performance, and well solves the problem of ping-pong phenomenon between terminals in different systems (4G and 5G) in the mobility management solution in the prior art.

[0271] Among them, the implementation embodiments of the mobility management method on the second network device side are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0272] An embodiment of the present invention also provides a mobility management device, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the mobility management method on the first network device side is implemented; or, when the processor executes the program, the mobility management method on the second network device side is implemented.

[0273] Among them, the implementation embodiments of the mobility management method on the first network device side or the second network device side are all applicable to the embodiments of the mobility management device and can achieve the same technical effect.

[0274] An embodiment of the present invention further provides a terminal, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the above-mentioned terminal-side mobility management method is implemented.

[0275] Among them, the implementation embodiments of the above-mentioned terminal-side mobility management method are all applicable to the embodiments of the terminal and can achieve the same technical effect.

[0276] An embodiment of the present invention further provides a readable storage medium on which a program is stored. When the program is executed by a processor, the program implements the steps in the mobility management method on the first network device side, the terminal side or the second network device side.

[0277] Among them, the implementation embodiments of the mobility management method on the first network device side, the terminal side or the second network device side are all applicable to the embodiments of the readable storage medium and can achieve the same technical effect.

[0278] It should be noted that many functional components described in this specification are referred to as modules in order to more particularly emphasize the independence of their implementation methods.

[0279] In the embodiment of the present invention, module can be implemented with software so that it can be executed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of the module.

[0280] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0281] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0282] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary personnel in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A mobility management method, applied to a first network device, characterized in that: include: Configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; Sending the first parameter information; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

2. The mobility management method according to claim 1, characterized in that: In the case where the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

3. The mobility management method according to claim 1, characterized in that: The defined field is a main information block MIB field; The sending the first parameter information includes: The first parameter information is sent through broadcasting.

4. The mobility management method according to claim 1, characterized in that: The information where the frequency domain position is located in the target frequency band is synchronization signal block SSB information; And / or, the identification information is a synchronization signal block identifier SSBID; And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

5. A mobility management method, applied to a terminal, characterized in that: include: Acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; Performing mobility management according to the first parameter information; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

6. The mobility management method according to claim 5, characterized in that: The performing mobility management according to the first parameter information includes: When all the first parameter information obtained indicates that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device; When at least one first parameter information indicates that the first network device supports RedCap, first information is sent to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

7. The mobility management method according to claim 5, characterized in that: In the case where the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

8. The mobility management method according to claim 5, characterized in that: The defined field is a main information block MIB field; The obtaining of first parameter information sent by at least one first network device includes: Acquire first parameter information sent by at least one first network device through broadcasting.

9. The mobility management method according to claim 5, characterized in that: The information where the frequency domain position is located in the target frequency band is synchronization signal block SSB information; And / or, the identification information is a synchronization signal block identifier SSBID; And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

10. A mobility management method, applied to a second network device, characterized in that: include: receiving first information sent by a terminal; Determine, according to the first information, a first network device to be accessed by the terminal; The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

11. A mobility management device, applied to a first network device, characterized in that: include: A first configuration module, configured to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; A first sending module, used for sending the first parameter information; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

12. The mobility management device according to claim 11, characterized in that: In the case where the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

13. The mobility management device according to claim 11, characterized in that: The defined field is a main information block MIB field; The sending the first parameter information includes: The first parameter information is sent through broadcasting.

14. The mobility management device according to claim 11, characterized in that: The information where the frequency domain position is located in the target frequency band is synchronization signal block SSB information; And / or, the identification information is a synchronization signal block identifier SSBID; And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

15. A mobility management device, applied to a terminal, characterized in that: include: A first acquisition module, configured to acquire first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; A first processing module, configured to perform mobility management according to the first parameter information; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

16. The mobility management device according to claim 15, characterized in that: The performing mobility management according to the first parameter information includes: When all the first parameter information obtained indicates that the first network device does not support RedCap, maintaining the network device currently connected by the terminal or moving to another network device in the same system as the currently connected network device; When at least one first parameter information indicates that the first network device supports RedCap, first information is sent to the second network device; the first information includes: information of the first network device supporting RedCap, and measurement results for the first network device supporting RedCap.

17. The mobility management device according to claim 15, characterized in that: In the case where the first parameter information identifies that the first network device supports RedCap, the first parameter information is also used to identify version information of the RedCap.

18. The mobility management device according to claim 15, characterized in that: The defined field is a main information block MIB field; The obtaining of first parameter information sent by at least one first network device includes: Acquire first parameter information sent by at least one first network device through broadcasting.

19. The mobility management device according to claim 15, characterized in that: The information where the frequency domain position is located in the target frequency band is synchronization signal block SSB information; And / or, the identification information is a synchronization signal block identifier SSBID; And / or, the second target time domain position belongs to the time domain position corresponding to the SSB information.

20. A mobility management device, applied to a second network device, characterized in that: include: A first receiving module, used for receiving first information sent by a terminal; A first determining module, configured to determine a first network device to be accessed by the terminal according to the first information; The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

21. A mobility management device, the mobility management device being a first network device, characterized in that: include: processor and transceiver; The processor is used to configure first parameter information; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; Sending the first parameter information through the transceiver; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

22. A mobility management device, the mobility management device being a terminal, characterized in that: include: processor; The processor is used to obtain first parameter information sent by at least one first network device; wherein the first parameter information is used to identify whether the first network device supports reduced capability RedCap; Performing mobility management according to the first parameter information; The first parameter information includes any one of the following: Added information in defined fields; Information that the frequency domain position is in the target frequency band; Identification information located at the first target time domain position; Unfilled second target temporal position.

23. A mobility management device, the mobility management device being a second network device, characterized in that: include: processor and transceiver; The processor is configured to receive, through the transceiver, first information sent by a terminal; Determine, according to the first information, a first network device to be accessed by the terminal; The first information includes: information of a first network device supporting RedCap, and a measurement result of the first network device supporting RedCap.

24. A mobility management device, comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, the mobility management method according to any one of claims 1 to 4 is implemented; or, When the processor executes the program, the mobility management method according to claim 10 is implemented.

25. A terminal comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, the mobility management method according to any one of claims 5 to 9 is implemented.

26. A readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the steps of the mobility management method according to any one of claims 1 to 10 are implemented.

Images