Mobility management method, apparatus, network node and terminal

Abstract

The application discloses a mobility management method, device, network node and terminal, and belongs to the technical field of communication. The mobility management method comprises the following steps: a first network node sends protocol stack indication information to a second network node, wherein the protocol stack indication information is used for indicating a protocol stack configuration mode of a target service adopted by the first network node, or is used for indicating a protocol stack configuration mode of the target service expected by the first network node to be adopted by the second network node; and the first network node receives feedback information from the second network node, wherein the feedback information is used for indicating a protocol stack configuration mode of the target service used by the second network node.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a mobility management method, apparatus, network node, and terminal. Background Technology

[0002] In existing mobility management, when a user equipment (UE) switches its service data channel from a source node to a target node, the source node provides the target node with the configuration used by the corresponding service at the source node. If a service's data bearer uses a simplified protocol stack configuration, such as a one-byte Packet Data Convergence Protocol (PDCP) header, the target base station will consider it a configuration error and refuse to accept the corresponding service session, resulting in poor service continuity. Summary of the Invention

[0003] This application provides a mobility management method, apparatus, network node, and terminal, which can improve service continuity during the mobility management process.

[0004] Firstly, a mobility management method is provided, applied to a first network node, the method comprising:

[0005] The first network node sends protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0006] The first network node receives feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service on the second network node.

[0007] Secondly, a mobility management device is provided, the device comprising:

[0008] The first sending module is used to send protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0009] The first receiving module is configured to receive feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service in the second network node.

[0010] Thirdly, a mobility management method is provided for application to a second network node, the method comprising:

[0011] The second network node receives protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0012] The second network node sends feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service on the second network node.

[0013] Fourthly, a mobility management device is provided, the device comprising:

[0014] The second receiving module is used to receive protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0015] The second sending module is used to send feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service in the second network node.

[0016] Fifthly, a mobility management method is provided, applied to a terminal, the method comprising:

[0017] The terminal receives first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node;

[0018] The terminal configures the protocol stack of the target service according to the first protocol stack configuration information.

[0019] Sixthly, a mobility management device is provided, the device comprising:

[0020] The third receiving module is used to receive first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node;

[0021] The configuration module is used to configure the protocol stack of the target service according to the first protocol stack configuration information.

[0022] In a seventh aspect, a first network node is provided, the first network node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0023] Eighthly, a first network node is provided, including a processor and a communication interface, wherein the communication interface is used to send protocol stack indication information to a second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by a target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node; and to receive feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service in the second network node.

[0024] In a ninth aspect, a second network node is provided, the second network node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0025] In a tenth aspect, a second network node is provided, including a processor and a communication interface, wherein the communication interface is configured to receive protocol stack indication information from a first network node, wherein the protocol stack indication information is configured to indicate the protocol stack configuration method adopted by a target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node; and to send feedback information to the first network node, wherein the feedback information is configured to indicate the protocol stack configuration method adopted by the target service in the second network node.

[0026] Eleventhly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the fifth aspect.

[0027] In a twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive first protocol stack configuration information from a first network node, wherein the first protocol stack configuration information is protocol stack configuration information adopted by a target service in a second network node; the processor is used to configure the protocol stack of the target service according to the first protocol stack configuration information.

[0028] In a thirteenth aspect, a mobility management system is provided, comprising: a first network node, a second network node, and a terminal, wherein the first network node is configured to perform the steps of the mobility management method as described in the first aspect, the second network node is configured to perform the steps of the mobility management method as described in the third aspect, and the terminal is configured to perform the steps of the mobility management method as described in the fifth aspect.

[0029] In a fourteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect.

[0030] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect.

[0031] In a sixteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fifth aspect.

[0032] In this embodiment, a first network node sends protocol stack indication information to a second network node. The protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service on the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt on the second network node. Thus, the second network node can know the protocol stack configuration method of the target service transmitting service data packets through the first network node or the protocol stack configuration method that the first network node expects the target service to adopt on the second network node based on the protocol stack indication information. This is beneficial for the second network node to accept services using simplified protocol stack configuration methods, thereby improving service continuity. Attached Figure Description

[0033] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0034] Figure 2 This is a schematic diagram of an NR UP protocol architecture provided in an embodiment of this application;

[0035] Figure 3This is a schematic diagram of an SDAP data packet format provided in an embodiment of this application;

[0036] Figure 4 This is a schematic diagram of another SDAP data packet format provided in an embodiment of this application;

[0037] Figure 5 This is a schematic diagram of a PDCP data packet format provided in an embodiment of this application;

[0038] Figure 6 This is a schematic diagram of another PDCP data packet format provided in an embodiment of this application;

[0039] Figure 7 This is a schematic diagram of an RLC data packet format provided in an embodiment of this application;

[0040] Figure 8 This is a schematic diagram of another RLC data packet format provided in an embodiment of this application;

[0041] Figure 9 This is a schematic diagram of a MAC data packet format provided in an embodiment of this application;

[0042] Figure 10 This is a schematic diagram of another MAC data packet format provided in an embodiment of this application;

[0043] Figure 11 This is a schematic diagram of another MAC data packet format provided in an embodiment of this application;

[0044] Figure 12 This is a schematic diagram of another MAC data packet format provided in an embodiment of this application;

[0045] Figure 13 This is a schematic diagram of another MAC data packet format provided in an embodiment of this application;

[0046] Figure 14 This is a schematic diagram of another MAC data packet format provided in an embodiment of this application;

[0047] Figure 15 This is a flowchart of a mobility management method provided in an embodiment of this application;

[0048] Figure 16 This is a flowchart of another mobility management method provided in the embodiments of this application;

[0049] Figure 17 This is a flowchart of another mobility management method provided in the embodiments of this application;

[0050] Figure 18 This is a structural diagram of a mobility management device provided in an embodiment of this application;

[0051] Figure 19 This is a structural diagram of another mobility management device provided in an embodiment of this application;

[0052] Figure 20 This is a structural diagram of another mobility management device provided in an embodiment of this application;

[0053] Figure 21 This is a structural diagram of the communication device provided in the embodiments of this application;

[0054] Figure 22 This is a structural diagram of the first network node provided in the embodiments of this application;

[0055] Figure 23 This is a structural diagram of the second network node provided in the embodiments of this application;

[0056] Figure 24 This is a structural diagram of the terminal provided in the embodiments of this application. Detailed Implementation

[0057] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0058] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0059] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0060] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11, a first network node 12, and a second network node 13. Terminal 11 can be a mobile phone, tablet computer, laptop computer (also known as a notebook computer), personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Both the first network node 12 and the second network node 13 can include access network equipment or core network equipment. Access network equipment can also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment can include base stations, WLAN access points, or WiFi nodes, etc. Base stations can be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.

[0061] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0062] I. Traditional protocol stack configuration method, also known as the existing protocol stack configuration method:

[0063] Regarding the NR user plane (UP) protocol stack:

[0064] NR UP protocol architecture diagram as follows Figure 2 As shown, it consists of the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and Physical Layer (PHY).

[0065] For SDAP:

[0066] SDAP is primarily responsible for the mapping and management of Quality of Service (QoS) flow and Data Radio Bearer (DRB);

[0067] The SDAP header for both uplink (UL) and downlink (DL) data packets occupies one byte. The SDAP layer data packet format can be as follows: Figure 3 and Figure 4 As shown, it is mainly used to carry the QoS flow identifier (QFI). Data is the data area.

[0068] For PDCP:

[0069] PDCP is mainly responsible for header compression and / or decompression, encryption and / or decryption, integrity protection and / or integrity verification, data copying and / or duplicate detection, reordering, PDCP retransmission and other processing.

[0070] PDCP data packets (i.e., PDCP data PDUs) carry a PDCP header. The PDCP header primarily carries the PDCP sequence number (SN). For service data, a 12-bit or 18-bit PDCP SN can be used, depending on the network configuration, occupying 2 or 3 bytes respectively. The PDCP layer data packet format is as follows: Figure 5 and Figure 6 As shown. Figure 5 This is the PDCP layer packet format using a 12-bit PDCP SN. Figure 6 This is the PDCP layer packet format using an 18-bit PDCP SN. Optional indicates optional, and cont indicates the content.

[0071] For RLC:

[0072] RLC is primarily responsible for data segmentation and / or reassembly, Automatic Repeat Request (ARQ) and / or duplicate detection and / or resegmentation (applicable to acknowledgment mode), and other functions.

[0073] RLC has three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). Each mode has a different data packet format. TM does not require an RLC header and is commonly used for system messages, paging messages, and signaling carried by SRB0; it is not used for transmitting service data. AM carries an RLC header, which must include an RLC SN (Relative Serial Number), which can be 12-bit or 18-bit. UM carries a one-byte RLC header when the data packet is complete (i.e., the packet has not been fragmented). This RLC header does not need to include an RLC SN; otherwise, it must include an RLC SN, which can be 6-bit or 12-bit. Because AM and UM support packet fragmentation and / or reassembly, their data packet formats are relatively complex. The RLC header needs to carry fragmentation information, such as SI and SO fields, to facilitate packet reassembly at the receiving end. Some RLC layer data packet formats are shown below. Figure 7 and Figure 8 As shown. Figure 7 This is the format of a UDM PDU data packet carrying a 12-bit RLC SN and SO field. Figure 8 This is the format for AMD PDU packets carrying an 18-bit RLC SN and SO field.

[0074] For MAC:

[0075] The MAC layer is mainly responsible for data multiplexing and / or demultiplexing, Hybrid Automatic Repeat Request (HARQ), resource scheduling, and other functions.

[0076] The MAC layer can transmit data packets transparently, meaning it doesn't carry a MAC header, but this is primarily suitable for paging messages and system message transmission. In other cases, a MAC header is required. Because the MAC layer has data multiplexing and / or demultiplexing functions, each MAC subPDU has a corresponding MAC subheader to carry the Logical Channel Identity (LCID), which identifies the data source. Additionally, it carries an L field to indicate the length of the MAC subPDU. Figures 9 to 11 The MAC layer packet format that carries an 8-bit L field in the MAC subheader. Figures 12 to 14 The MAC layer packet format carries a 16-bit L field in the MAC subheader.

[0077] II. Mobile Management Process:

[0078] For connected UEs, the base station configures the UE to measure neighboring cells and can decide to perform handover operations on the UE based on the measurement results reported by the UE. Taking Xn handover as an example, after determining the target cell, the source base station will initiate a handover request to the target base station to which the target cell belongs. In this handover request, the source base station will inform the target base station of the service resource configuration information such as the UE's service session (i.e., Protocol Data Unit (PDU) session) at the source base station. If the target base station agrees to establish a service session, it will inform the source base station of the acceptance of the corresponding service session. For service sessions that it does not accept, it will inform the source base station of the reason for not accepting them. After the UE successfully hands over to the target base station, the target base station will initiate a path switch request to the core network node to request that the UE's service session channel at the source node be switched from the source base station to the target base station.

[0079] The mobility management method and its application scenarios provided in this application will be described in detail below with reference to the accompanying drawings.

[0080] Please see Figure 15 , Figure 15 This is a flowchart of a mobility management method provided in an embodiment of this application. This method can be executed by a first network node, such as... Figure 15 As shown, it includes the following steps:

[0081] Step 201: The first network node sends protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0082] The first network node mentioned above can be a source node in mobility management, and the second network node mentioned above can be a target node in mobility management. The second network node can be any network node; for example, it may or may not support a simplified protocol stack configuration method; or it may only support a simplified protocol stack configuration method. The protocol stack configuration method may include, but is not limited to, the traditional protocol stack configuration method or the simplified protocol stack configuration method. The target service mentioned above can be any service, and this embodiment does not limit it.

[0083] In one embodiment, the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service at the first network node. The protocol stack configuration method adopted by the target service at the first network node can be understood as the protocol stack configuration method used by the target service when transmitting service data packets through the first network node. For example, if the target service uses a simplified protocol stack configuration method to transmit service data packets at the first network node, the protocol stack indication information indicates the simplified protocol stack configuration method; if the target service uses a traditional protocol stack configuration method to transmit service data packets at the first network node, the protocol stack indication information indicates the traditional protocol stack configuration method.

[0084] In another embodiment, the protocol stack indication information is used to indicate the protocol stack configuration method that the first network node expects the target service to adopt at the second network node. Here, the protocol stack configuration method that the first network node expects the target service to adopt at the second network node can be understood as the protocol stack configuration method that the first network node expects the target service to adopt when transmitting service data packets through the second network node. For example, if the first network node expects the target service to transmit service data packets at the second network node using a simplified protocol stack configuration method, the above-mentioned protocol stack indication information indicates the simplified protocol stack configuration method; if the first network node expects the target service to transmit service data packets at the second network node using a conventional protocol stack configuration method, the above-mentioned protocol stack indication information indicates the conventional protocol stack configuration method.

[0085] It should be noted that the protocol stack configuration method that the first network node expects the target service to adopt in the second network node can be the same as or different from the protocol stack configuration method adopted in the first network node. In an optional embodiment, the first network node can determine the protocol stack configuration method that it expects the target service to adopt in the second network node based on the protocol stack configuration method adopted by the target service in the first network node. For example, the first network node can expect the protocol stack configuration method adopted by the target service in the second network node to be the same as the protocol stack configuration method adopted by the target service in the first network node.

[0086] In this embodiment, the first network node sends protocol stack indication information to the second network node. In this way, the second network node can learn, based on the protocol stack indication information, the protocol stack configuration method of the target service transmitting service data packets through the first network node, or the protocol stack configuration method that the first network node expects the target service to adopt in the second network node. Then, the second network node can configure the protocol stack of the target service in the second network node based on the protocol stack indication information.

[0087] Step 202: The first network node receives feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service in the second network node.

[0088] For example, when the target service adopts a simplified protocol stack configuration in the second network node, the feedback information is used to indicate the simplified protocol stack configuration. When the target service adopts a traditional protocol stack configuration in the second network node, the feedback information is used to indicate the traditional protocol stack configuration.

[0089] The mobility management method provided in this application embodiment involves a first network node sending protocol stack indication information to a second network node. This protocol stack indication information indicates the protocol stack configuration method used by a target service on the first network node, or indicates the protocol stack configuration method that the first network node expects the target service to use on the second network node. Based on this information, the second network node can determine the protocol stack configuration method used by the target service to transmit service data packets through the first network node, or the protocol stack configuration method that the first network node expects the target service to use on the second network node. This facilitates the second network node's acceptance of services using simplified protocol stack configuration methods, thereby improving service continuity.

[0090] Optionally, the protocol stack indication information may include at least one of the following:

[0091] The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal;

[0092] The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

[0093] The aforementioned first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal, which can be understood as an indication of the protocol stack configuration method based on the terminal's granularity (i.e., per UE). The protocol stack configuration method indicated by the first protocol stack indication information can be applied to all services of the terminal.

[0094] The aforementioned second protocol stack indication information is used to indicate the protocol stack configuration method of the target service, and can also be understood as an indication of the protocol stack configuration method based on the granularity of the service. The protocol stack configuration method indicated by the second protocol stack indication information can be specifically used for the target service; that is, the protocol stack configuration method indicated by the second protocol stack indication information is only applicable to the target service.

[0095] For example, the above protocol stack indication information can be represented by an enumerated type information field, the value of which can include traditional protocol stack and simplified protocol stack; or, the above protocol stack indication information can be represented by a selected type information field, where the simplified protocol stack is represented when the above protocol stack indication information exists, and the traditional protocol stack is represented when the above protocol stack indication information is omitted.

[0096] Optionally, the target service can be identified by at least one of the following: service session identification information; radio bearer identification information; service flow identification information.

[0097] The aforementioned service session identification information, such as PDU session ID. The aforementioned radio bearer identification information, such as Data Radio Bearer (DRB) ID. The aforementioned service flow identification information, such as Quality of Service (QoS) flow ID.

[0098] In an optional embodiment, when the second protocol stack indication information is used to indicate the protocol stack configuration method of the target service session, the second protocol stack indication information can be carried through a PDU session resource to be setup list. For example, the PDU session resources to be setup list can be as shown in Table 1. It is understood that in this embodiment, the target service can be identified by service session identification information, and the target service session is the service session of the target service.

[0099] Table 1

[0100]

[0101] In another optional embodiment, when the second protocol stack indication information is used to indicate the protocol stack configuration method of the target radio bearer or the target service flow, the second protocol stack indication information can be carried through a DRB to QoS Flow Mapping List. For example, the aforementioned DRB to QoS Flow Mapping List can be as shown in Table 2. It is understood that in this embodiment, the target service can be identified by radio bearer identification information or service flow identification information, where the target radio bearer is the radio bearer of the target service, and the target service flow is the service flow of the target service.

[0102] Table 2

[0103]

[0104] In Tables 1 and 2 above, "M" in the second column indicates that the corresponding information field is mandatory, and "O" indicates that the corresponding information field is optional. The "maxnoof PDU sessions" in the third column of Table 1 represents the maximum number of PDU sessions, and the "maxnoof DRBs" in the third column of Table 2 represents the maximum number of radio bearers. "maxnoof QoSFlows" represents the maximum number of QoS flows. It should be noted that the content in Tables 1 and 2, except for the row on protocol stack type, can be found in the relevant sections of the DRB to QoS Flow Mapping List and DRB to QoS Flow Mapping List in related technologies.

[0105] Optionally, the protocol stack configuration method includes one of the following:

[0106] Traditional protocol stack configuration method;

[0107] Simplify protocol stack configuration.

[0108] The aforementioned traditional protocol stack configuration method refers to the packet configuration method in existing protocols. For details, please refer to the relevant explanations of the traditional protocol stack configuration method described above. It is understood that the aforementioned traditional protocol stack configuration method may include, but is not limited to: flexible configuration to enable reverse mapping function; configuration of long sequence numbers for the Packet Data Convergence Protocol (PDCP); configuration of unacknowledged mode (UM) or acknowledged mode (AM) radio link control protocol (RLC); and support for Media Access Control (MAC) multiplexing. The aforementioned long sequence number may include a 12-bit or 18-bit serial number (SN).

[0109] Optionally, the simplified protocol stack configuration method may include at least one of the following:

[0110] Disable the anti-mapping function at the Service Data Adaptation Protocol (SDAP) layer;

[0111] PDCP enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits;

[0112] The RLC layer uses a transparent transmission mode;

[0113] Disable MAC multiplexing at the MAC layer.

[0114] The aforementioned SDAP layer disables the anti-mapping function, which can also be referred to as not enabling the anti-mapping function. This can include not enabling the anti-mapping function at the RAN level and not enabling the anti-mapping function at the CN level.

[0115] The length of the aforementioned short sequence number is less than or equal to 8 bits; for example, the aforementioned short sequence number is a 6-bit PDCP SN. It should be noted that the aforementioned short sequence number can be agreed upon by the protocol or configured on the network side.

[0116] The MAC layer above disables MAC multiplexing. For example, when the sending end transmits data for a target service, it does not reuse the data of the target service with other service data and transmit it through the same resource.

[0117] Optionally, the first network node sends protocol stack indication information to the second network node, including:

[0118] The first network node sends protocol stack indication information to the second network node through a first interface, wherein the first interface is the interface between the second network node and the first network node;

[0119] or

[0120] The first network node sends protocol stack instruction information to the second network node via the core network node.

[0121] In one implementation, the first network node can directly send protocol stack indication information to the second network node through the interface between the second network node and the first network node. For example, during the Xn handover process, the source node (i.e., the first network node) can send the protocol stack indication information to the target node (i.e., the second network node) through a handover request message.

[0122] In another implementation, the first network node can send protocol stack indication information to the second network node via the core network node; that is, the first network node sends protocol stack indication information to the core network node, and the core network node sends the received protocol stack indication information to the second network node. For example, during the N2 handover process, the source node (i.e., the first network node) can carry the protocol stack indication information through the source-to-target transparent container in the handover request message.

[0123] Optionally, before the first network node sends protocol stack indication information to the second network node, the method further includes:

[0124] The first network node selects the second network node, wherein the second network node supports the transmission of service data through a simplified protocol stack;

[0125] or

[0126] The first network node selects a first cell, wherein the first cell supports the transmission of service data through a simplified protocol stack, and the first cell is a cell of the second network node.

[0127] In one embodiment, the first network node selects a second network node that supports the transmission of service data via a simplified protocol stack. That is, during mobility management, the first network node selects a network node that supports the transmission of service data via a simplified protocol stack for handover. This ensures that the target service can be transmitted via a simplified protocol stack configuration on the second network node. It should be noted that the second network node supporting the transmission of service data via a simplified protocol stack may include all cells managed by the second network node supporting this transmission, or at least a portion of the cells managed by the second network node supporting this transmission.

[0128] In another implementation, the first network node selects a first cell that supports the transmission of service data via a simplified protocol stack. This first cell can be the target cell for the handover of the target service to the second network node; that is, after the handover, the target service transmits service data through the first cell of the second network node. In other words, during mobility management, the first network node selects a cell that supports the transmission of service data via a simplified protocol stack for handover, thus ensuring that the target service can transmit service data using a simplified protocol stack configuration in the first cell of the second network node.

[0129] Optionally, the first network node learns that the second network node or the first cell supports the transmission of service data via a simplified protocol stack based on at least one of the following:

[0130] Information exchanged between network nodes regarding their capabilities;

[0131] Operations, Administration and Maintenance (OAM) configuration information.

[0132] The first network node learns from the capability interaction information between network nodes that the second network node supports the transmission of service data via a simplified protocol stack. In one example, network node #1 can send capability interaction information to network node #2, indicating whether network node #1 supports or does not support the transmission of service data via the simplified protocol stack. Network node #2 can also send capability interaction information to network node #1, indicating whether network node #2 supports or does not support the transmission of service data via the simplified protocol stack. In another example, network node #1 can send a capability interaction request message to network node #2. After receiving the capability interaction request message, network node #2 can send a capability interaction response message to network node #1, indicating whether it requests network node #2 to support or not support the transmission of service data via the simplified protocol stack. Furthermore, network nodes can also interact to determine whether the cells they manage support the transmission of service data via the simplified protocol stack.

[0133] The first network node learns from the capability interaction information between network nodes that the first cell supports the transmission of service data via a simplified protocol stack. In one example, network node #1 can send capability interaction information to network node #2. This capability interaction information indicates whether the cells managed by network node #1 support or do not support the transmission of service data via a simplified protocol stack. For example, cell 1 managed by network node #1 supports the transmission of service data via a simplified protocol stack, while cell 2 does not. Network node #2 can also send capability interaction information to network node #1. This capability interaction information indicates whether the cells managed by network node #2 support or do not support the transmission of service data via a simplified protocol stack. For example, cell 1 managed by network node #2 supports the transmission of service data via a simplified protocol stack, while cell 2 does not. In another example, network node #1 can send a capability interaction request message to network node #2. After receiving the capability interaction request message, network node #2 can send a capability interaction response message to network node #1. This capability interaction response message indicates whether the cells managed by network node #2 support or do not support the transmission of service data via a simplified protocol stack.

[0134] For example, if the first network node learns from the OAM configuration information that the second network node supports the transmission of service data through a simplified protocol stack, the OAM system can provide OAM configuration information to network node #1. The OAM configuration information is used to indicate whether each network node supports or does not support the transmission of service data through a simplified protocol stack. For example, network node #2 supports the transmission of service data through a simplified protocol stack, while network node #3 does not support the transmission of service data through a simplified protocol stack.

[0135] The first network node learns from the OAM configuration information that the first cell supports the transmission of service data via a simplified protocol stack. The OAM system can provide OAM configuration information to network node #1, which indicates whether the cells managed by each network node support or do not support the transmission of service data via a simplified protocol stack. For example, cell 1 managed by network node #2 supports the transmission of service data via a simplified protocol stack, cell 2 does not support the transmission of service data via a simplified protocol stack, and cell 1 managed by network node #3 does not support the transmission of service data via a simplified protocol stack.

[0136] It should be noted that, regarding the knowledge that the second network node supports the transmission of service data through a simplified protocol stack, the capability interaction information between the aforementioned network nodes can include capability exchange information at the network node level, and the aforementioned OAM configuration information can include OAM configuration information at the network node level. In other words, the capability interaction information between the aforementioned network nodes can include capability interaction information between each network node, and the aforementioned OAM configuration information can include only the OAM configuration information of the network nodes.

[0137] Upon learning that the first cell supports the transmission of service data via a simplified protocol stack, the capability exchange information between the aforementioned network nodes can include cell-level capability exchange information, and the OAM configuration information can include cell-level OAM configuration information. In other words, the capability exchange information between the aforementioned network nodes can include inter-cell capability exchange information within each network node, and the OAM configuration information can include the OAM configuration information of cells within each network node.

[0138] Optionally, if the second network node changes the protocol stack configuration of the target service, the feedback information includes first protocol stack configuration information, which is the protocol stack configuration information used by the target service in the second network node.

[0139] In this embodiment, when the second network node changes the protocol stack configuration method of the target service, for example, the target service uses a simplified protocol stack configuration method on the first network node while the second network node uses a traditional protocol stack configuration method, or the target service uses a traditional protocol stack configuration method on the first network node while the second network node uses a simplified protocol stack configuration method, the second network node can feed back the protocol stack configuration information used by the target service on the second network node to the first network node, so that the first network node can notify the terminal to reconfigure the protocol stack of the target service.

[0140] Optionally, after the first network node receives feedback information from the second network node, the method further includes:

[0141] The first network node sends the first protocol stack configuration information to the terminal.

[0142] In this embodiment, the first network node sends the first protocol stack configuration information to the terminal, which makes it easy for the terminal to directly reconfigure the protocol stack of the target service based on the first protocol stack configuration information.

[0143] Please see Figure 16 , Figure 16 This is a flowchart of a mobility management method provided in an embodiment of this application. This method can be executed by a second network node, such as... Figure 16 As shown, it includes the following steps:

[0144] Step 301: The second network node receives protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0145] The first network node mentioned above can be a source node in mobility management, and the second network node mentioned above can be a target node in mobility management. The second network node can be any network node; for example, it may or may not support a simplified protocol stack configuration method; or it may only support a simplified protocol stack configuration method. The protocol stack configuration method may include, but is not limited to, the traditional protocol stack configuration method or the simplified protocol stack configuration method. The target service mentioned above can be any service, and this embodiment does not limit it.

[0146] In one embodiment, the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service at the first network node. The protocol stack configuration method adopted by the target service at the first network node can be understood as the protocol stack configuration method used by the target service when transmitting service data packets through the first network node. For example, if the target service uses a simplified protocol stack configuration method to transmit service data packets at the first network node, the protocol stack indication information indicates the simplified protocol stack configuration method; if the target service uses a traditional protocol stack configuration method to transmit service data packets at the first network node, the protocol stack indication information indicates the traditional protocol stack configuration method.

[0147] In another embodiment, the protocol stack indication information is used to indicate the protocol stack configuration method that the first network node expects the target service to adopt at the second network node. Here, the protocol stack configuration method that the first network node expects the target service to adopt at the second network node can be understood as the protocol stack configuration method that the first network node expects the target service to adopt when transmitting service data packets through the second network node. For example, if the first network node expects the target service to transmit service data packets at the second network node using a simplified protocol stack configuration method, the above-mentioned protocol stack indication information indicates the simplified protocol stack configuration method; if the first network node expects the target service to transmit service data packets at the second network node using a conventional protocol stack configuration method, the above-mentioned protocol stack indication information indicates the conventional protocol stack configuration method.

[0148] It should be noted that the protocol stack configuration method that the target service expects to use in the second network node can be the same as or different from the protocol stack configuration method used in the first network node.

[0149] In this embodiment, the second network node receives protocol stack indication information from the first network node. Based on this information, the second network node can determine the protocol stack configuration method for transmitting service data packets through the first network node, or the protocol stack configuration method the first network node expects the target service to use on the second network node. Consequently, the second network node can configure the protocol stack of the target service on the second network node based on the protocol stack indication information. For example, if the protocol stack indication information indicates a simplified protocol stack configuration method, the second network node can preferentially choose the simplified method to configure the target service's protocol stack. Conversely, if the information indicates a traditional protocol stack configuration method, the second network node can preferentially choose the traditional method.

[0150] Step 302: The second network node sends feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service in the second network node.

[0151] For example, when the target service adopts a simplified protocol stack configuration in the second network node, the feedback information is used to indicate the simplified protocol stack configuration. When the target service adopts a traditional protocol stack configuration in the second network node, the feedback information is used to indicate the traditional protocol stack configuration.

[0152] The mobility management method provided in this application embodiment involves a second network node receiving protocol stack indication information from a first network node. This information indicates the protocol stack configuration method used by the target service on the first network node, or the protocol stack configuration method that the first network node expects the target service to use on the second network node. Based on this information, the second network node can determine the protocol stack configuration method used by the target service to transmit service data packets through the first network node, or the protocol stack configuration method that the first network node expects the target service to use on the second network node. This facilitates the second network node's acceptance of services using simplified protocol stack configuration methods, thereby improving service continuity.

[0153] Optionally, after the second network node receives protocol stack indication information from the first network node, the method further includes:

[0154] The second network node configures the protocol stack configuration method adopted by the target service on the second network node according to the protocol stack indication information.

[0155] The protocol stack configuration method used by the target service in the second network node can be understood as the protocol stack configuration method used when configuring the target service to transmit service data through the cell of the second network node.

[0156] In this embodiment, the second network node configures the protocol stack configuration method adopted by the target service in the second network node according to the protocol stack indication information. For example, if the protocol stack indication information indicates a simplified protocol stack configuration method, the second network node can preferentially select the simplified protocol stack configuration method to configure the protocol stack for the target service to transmit service data through the second network node. If the protocol stack indication information indicates a traditional protocol stack configuration method, the second network node can preferentially select the traditional protocol stack configuration method to configure the protocol stack for the target service to transmit service data through the second network node.

[0157] Optionally, the second network node configures the protocol stack configuration method adopted by the target service on the second network node according to the protocol stack indication information, including at least one of the following:

[0158] When the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node does not support the transmission of service data through the simplified protocol stack, the second network node adopts the traditional protocol stack configuration method for the target service.

[0159] When the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node supports the transmission of service data through the simplified protocol stack, the second network node decides to adopt the simplified protocol stack configuration method for the target service, or the second network node decides to adopt the traditional protocol stack configuration method for the target service.

[0160] In this embodiment, when the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node does not support the transmission of service data through the simplified protocol stack, the second network node adopts the traditional protocol stack configuration method for the target service. That is, the second network node uses the traditional protocol stack configuration information to configure the data channel for the target service to transmit service data through the second network node.

[0161] When the protocol stack indication information indicates a simplified protocol stack configuration and the second network node supports transmitting service data via the simplified protocol stack, the second network node decides whether to adopt the simplified protocol stack configuration for the target service, or decides to adopt the traditional protocol stack configuration for the target service. In other words, the second network node decides which protocol stack configuration to use. Specifically, if the second network node decides to adopt the simplified protocol stack configuration for the target service, it can use the simplified protocol stack configuration information to configure the data channel for transmitting service data through the second network node. If the second network node decides to adopt the traditional protocol stack configuration for the target service, it can use the traditional protocol stack configuration information to configure the data channel for transmitting service data through the second network node.

[0162] It should be noted that when the second network node decides to adopt a simplified protocol stack configuration method for the target service, the second network node can configure the data channel for the target service to transmit service data through the second network node based on the simplified protocol stack configuration information provided by the first network node (e.g., the simplified protocol stack configuration information of the target service in the first network node), or it can configure the data channel for the target service to transmit service data through the second network node based on newly generated simplified protocol stack configuration information (e.g., different from the simplified protocol stack configuration information of the target service in the first network node).

[0163] Optionally, if the protocol stack indication information indicates a traditional protocol stack configuration and the second network node does not support transmitting service data via a simplified protocol stack, the second network node may adopt a traditional protocol stack configuration for the target service; if the protocol stack indication information indicates a traditional protocol stack configuration and the second network node supports transmitting service data via a simplified protocol stack, the second network node may decide to adopt a simplified protocol stack configuration for the target service, or the second network node may decide to adopt a traditional protocol stack configuration for the target service.

[0164] Optionally, the protocol stack indication information includes at least one of the following:

[0165] The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal;

[0166] The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

[0167] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0168] Optionally, the protocol stack configuration method includes one of the following:

[0169] Traditional protocol stack configuration method;

[0170] Simplify protocol stack configuration.

[0171] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0172] Optionally, the simplified protocol stack configuration method includes at least one of the following:

[0173] The SDAP layer disables the anti-mapping function;

[0174] PDCP enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits;

[0175] The RLC layer uses a transparent transmission mode;

[0176] Disable MAC multiplexing at the MAC layer.

[0177] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0178] Optionally, the target service is identified by at least one of the following information:

[0179] Business session identification information;

[0180] Wireless bearer identification information;

[0181] Business flow identification information.

[0182] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0183] Optionally, the first network node sends protocol stack indication information to the second network node, including:

[0184] The second network node receives protocol stack indication information from the first network node through a first interface, wherein the first interface is the interface between the second network node and the first network node;

[0185] or

[0186] The second network node receives protocol stack instruction information from the first network node via the core network node.

[0187] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0188] Optionally, if the second network node changes the protocol stack configuration of the target service, the feedback information includes the protocol stack configuration information used by the target service in the second network node.

[0189] It should be noted that the implementation method of this method can be found in [reference needed]. Figure 15 The relevant descriptions of the embodiments shown are not repeated here.

[0190] Please see Figure 17 , Figure 17 This is a flowchart of a mobility management method provided in an embodiment of this application. This method can be executed by a terminal, such as... Figure 17 As shown, it includes the following steps:

[0191] Step 401: The terminal receives first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node.

[0192] Step 402: The terminal configures the protocol stack of the target service according to the first protocol stack configuration information.

[0193] For example, if the first protocol stack configuration information and the protocol stack configuration information of the target service on the first network node are different, the terminal can configure the protocol stack of the target service according to the first protocol stack configuration information; otherwise, the protocol stack of the target service does not need to be reconfigured.

[0194] The mobility management method provided in this application embodiment involves a terminal receiving first protocol stack configuration information from a first network node. The first protocol stack configuration information is the protocol stack configuration information used by the target service in the second network node. The terminal configures the protocol stack of the target service according to the first protocol stack configuration information, which facilitates the smooth switching of the target service to the second network node and improves service continuity.

[0195] Optionally, the terminal configures the protocol stack of the target service according to the first protocol stack configuration information, including:

[0196] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal releases the first protocol stack entity of the target service and establishes a new protocol stack entity for the target service based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the change in protocol stack configuration method; or,

[0197] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal initializes the first protocol stack entity of the target service and reconfigures the first protocol stack entity based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the protocol stack configuration method is changed.

[0198] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal releases the first protocol stack entity of the target service and establishes the protocol stack entity of the target service based on the first protocol stack configuration information. For example, if the target service uses a simplified protocol stack configuration method in the first network node and a traditional protocol stack configuration method in the second network node, the terminal releases the simplified protocol stack entity of the target service (i.e., the protocol stack entity corresponding to the simplified protocol stack configuration method) and establishes the protocol stack entity of the target service based on the traditional protocol stack configuration information (i.e., the protocol stack configuration information used by the target service in the second network node); if the target service uses a traditional protocol stack configuration method in the first network node and a simplified protocol stack configuration method in the second network node, the terminal releases the traditional protocol stack entity of the target service (i.e., the protocol stack entity corresponding to the traditional protocol stack configuration method) and establishes the protocol stack entity of the target service based on the simplified protocol stack configuration information (i.e., the protocol stack configuration information used by the target service in the second network node).

[0199] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal initializes the first protocol stack entity of the target service and reconfigures the first protocol stack entity based on the first protocol stack configuration information. For example, if the target service uses a simplified protocol stack configuration method on the first network node and a traditional protocol stack configuration method on the second network node, the terminal initializes the simplified protocol stack entity of the target service (i.e., the protocol stack entity corresponding to the simplified protocol stack configuration method) and reconfigures the simplified protocol stack entity based on the traditional protocol stack configuration information (i.e., the protocol stack configuration information used by the target service on the second network node). If the target service uses a traditional protocol stack configuration method on the first network node and a simplified protocol stack configuration method on the second network node, the terminal initializes the traditional protocol stack entity of the target service (i.e., the protocol stack entity corresponding to the traditional protocol stack configuration method) and reconfigures the traditional protocol stack entity based on the simplified protocol stack configuration information (i.e., the protocol stack configuration information used by the target service on the second network node). It can be understood that when the terminal initializes the first protocol stack entity of the target service, it initializes the parameter configuration of the first protocol stack entity.

[0200] In summary, the mobility management method provided in this application can realize information on whether the target service uses a simplified protocol stack at the source node during the mobility management process, so as to assist the data channel corresponding to the target service in switching to the target node.

[0201] It should be noted that the mobility management method provided in this application embodiment can be executed by a mobility management device, or by a control module within the mobility management device for executing the mobility management method. This application embodiment uses the execution of the mobility management method by a mobility management device as an example to illustrate the mobility management device provided in this application embodiment.

[0202] Please see Figure 18 , Figure 18 This is a structural diagram of a mobility management device provided in an embodiment of this application, as shown below. Figure 18 As shown, the mobility management device 500 includes:

[0203] The first sending module 501 is used to send protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0204] The first receiving module 502 is used to receive feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service in the second network node.

[0205] Optionally, the protocol stack indication information includes at least one of the following:

[0206] The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal;

[0207] The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

[0208] Optionally, the protocol stack configuration method includes one of the following:

[0209] Traditional protocol stack configuration method;

[0210] Simplify protocol stack configuration.

[0211] Optionally, the simplified protocol stack configuration method includes at least one of the following:

[0212] Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer;

[0213] The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits.

[0214] The Radio Link Control (RLC) layer uses a transparent transmission mode;

[0215] The Media Access Control (MAC) layer disables the MAC multiplexing function.

[0216] Optionally, the target service is identified by at least one of the following information:

[0217] Business session identification information;

[0218] Wireless bearer identification information;

[0219] Business flow identification information.

[0220] Optionally, the first sending module is specifically used for:

[0221] The protocol stack instruction information is sent to the second network node through the first interface, wherein the first interface is the interface between the second network node and the first network node;

[0222] or

[0223] The protocol stack instruction information is sent from the core network node to the second network node.

[0224] Optionally, the device further includes:

[0225] The selection module is used to select the second network node before sending protocol stack indication information to the second network node, wherein the second network node supports the transmission of service data through a simplified protocol stack; or to select a first cell, wherein the first cell supports the transmission of service data through a simplified protocol stack, and the first cell is a cell of the second network node.

[0226] Optionally, the first network node learns that the second network node or the first cell supports the transmission of service data via a simplified protocol stack based on at least one of the following:

[0227] Information exchanged between network nodes regarding their capabilities;

[0228] Operation, management, and maintenance of OAM configuration information.

[0229] Optionally, if the second network node changes the protocol stack configuration of the target service, the feedback information includes first protocol stack configuration information, which is the protocol stack configuration information used by the target service in the second network node.

[0230] Optionally, the first sending module is further configured to:

[0231] After receiving feedback information from the second network node, the first protocol stack configuration information is sent to the terminal.

[0232] The mobility management device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a first network node, or other devices besides a first network node. For example, the first network node can be, but is not limited to, the type of first network node 12 listed above. Other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the scope of the device.

[0233] The mobility management device provided in this application embodiment can achieve Figure 15 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0234] Please see Figure 19 , Figure 19 This is a structural diagram of a mobility management device provided in an embodiment of this application, as shown below. Figure 19 As shown, the mobility management device 600 includes:

[0235] The second receiving module 601 is used to receive protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service in the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt in the second network node.

[0236] The second sending module 602 is used to send feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service in the second network node.

[0237] Optionally, the device further includes:

[0238] The configuration module is used to configure the protocol stack configuration method adopted by the target service in the second network node according to the protocol stack indication information after receiving the protocol stack indication information from the first network node.

[0239] Optionally, the configuration module is specifically used for at least one of the following:

[0240] When the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node does not support the transmission of service data through the simplified protocol stack, the traditional protocol stack configuration method shall be adopted for the target service.

[0241] If the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node supports the transmission of service data through the simplified protocol stack, a decision is made to adopt the simplified protocol stack configuration method for the target service, or to adopt the traditional protocol stack configuration method for the target service.

[0242] Optionally, the protocol stack indication information includes at least one of the following:

[0243] The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal;

[0244] The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

[0245] Optionally, the protocol stack configuration method includes one of the following:

[0246] Traditional protocol stack configuration method;

[0247] Simplify protocol stack configuration.

[0248] Optionally, the simplified protocol stack configuration method includes at least one of the following:

[0249] Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer;

[0250] The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits.

[0251] The Radio Link Control (RLC) layer uses a transparent transmission mode;

[0252] The Media Access Control (MAC) layer disables the MAC multiplexing function.

[0253] Optionally, the target service is identified by at least one of the following information:

[0254] Business session identification information;

[0255] Wireless bearer identification information;

[0256] Business flow identification information.

[0257] Optionally, the second sending module is specifically used for:

[0258] Protocol stack indication information is received from the first network node through a first interface, wherein the first interface is the interface between the second network node and the first network node;

[0259] or

[0260] The protocol stack instruction information is received from the first network node via the core network node.

[0261] Optionally, if the second network node changes the protocol stack configuration of the target service, the feedback information includes the protocol stack configuration information used by the target service in the second network node.

[0262] The mobility management device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a second network node, or other devices besides a second network node. For example, the second network node can be, but is not limited to, the type of second network node 13 listed above. Other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the scope of the device.

[0263] The mobility management device provided in this application embodiment can achieve Figure 16 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0264] Please see Figure 20 , Figure 20 This is a structural diagram of a mobility management device provided in an embodiment of this application, as shown below. Figure 20 As shown, the mobility management device 700 includes:

[0265] The third receiving module 701 is used to receive first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node;

[0266] The configuration module 702 is used to configure the protocol stack of the target service according to the first protocol stack configuration information.

[0267] Optionally, the configuration module is specifically used for:

[0268] When the first protocol stack configuration information indicates a change in the protocol stack configuration of the target service, the first protocol stack entity of the target service is released, and a new protocol stack entity of the target service is established based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration of the target service before the protocol stack configuration method is changed; or,

[0269] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the first protocol stack entity of the target service is initialized, and the first protocol stack entity is reconfigured based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the protocol stack configuration method is changed.

[0270] The mobility management device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, a terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0271] The mobility management device provided in this application embodiment can achieve Figure 17 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0272] Optional, such as Figure 21 As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described mobility management method embodiment and achieve the same technical effect. When the communication device 800 is a first network node, the program or instructions executed by the processor 801 implement the various steps of the above-described mobility management method embodiment and achieve the same technical effect. When the communication device 800 is a second network node, the program or instructions executed by the processor 801 implement the various steps of the above-described mobility management method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0273] This application embodiment also provides a first network node, including a processor and a communication interface. The communication interface is used to send protocol stack indication information to a second network node, wherein the protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service on the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt on the second network node; and to receive feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service on the second network node. This first network node embodiment corresponds to the above-described first network node-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this first network device embodiment and can achieve the same technical effects.

[0274] Specifically, embodiments of this application also provide a first network node. For example... Figure 22 As shown, the first network node 900 includes: an antenna 901, a radio frequency (RF) device 902, a baseband device 903, a processor 904, and a memory 905. The antenna 901 is connected to the RF device 902. In the uplink direction, the RF device 902 receives information through the antenna 901 and transmits the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be transmitted and sends it to the RF device 902. The RF device 902 processes the received information and transmits it through the antenna 901.

[0275] The method executed by the first network node in the above embodiments can be implemented in the baseband device 903, which includes a baseband processor.

[0276] The baseband device 903 may, for example, include at least one baseband board on which multiple chips are disposed, such as... Figure 22 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 905 via a bus interface to call the program in the memory 905 and execute the network device operations shown in the above method embodiment.

[0277] The first network node may also include a network interface 906, such as a common public radio interface (CPRI).

[0278] Specifically, the first network node 900 in this embodiment of the invention further includes: instructions or programs stored in memory 905 and executable on processor 904, wherein processor 904 calls the instructions or programs in memory 905 to execute. Figure 18 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0279] This application embodiment also provides a second network node, including a processor and a communication interface. The communication interface is used to receive protocol stack indication information from a first network node, wherein the protocol stack indication information indicates the protocol stack configuration method adopted by the target service on the first network node, or indicates the protocol stack configuration method that the first network node expects the target service to adopt on the second network node; and to send feedback information to the first network node, wherein the feedback information indicates the protocol stack configuration method adopted by the target service on the second network node. This second network node embodiment corresponds to the above-described second network node-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this second network node embodiment and achieve the same technical effects.

[0280] Specifically, embodiments of this application also provide a second network node. For example... Figure 23 As shown, the second network node 1000 includes: an antenna 1001, a radio frequency (RF) device 1002, a baseband device 1003, a processor 1004, and a memory 1005. The antenna 1001 is connected to the RF device 1002. In the uplink direction, the RF device 1002 receives information through the antenna 1001 and sends the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be transmitted and sends it to the RF device 1002. The RF device 1002 processes the received information and then transmits it through the antenna 1001.

[0281] The method executed by the second network node in the above embodiments can be implemented in the baseband device 1003, which includes a baseband processor.

[0282] The baseband device 1003 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 23 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1005 via a bus interface to call the program in the memory 1005 and execute the network device operation shown in the above method embodiment.

[0283] The second network node may also include a network interface 1006, such as a common public radio interface (CPRI).

[0284] Specifically, the second network node 1000 in this embodiment of the invention further includes: instructions or programs stored in memory 1005 and executable on processor 1004, wherein processor 1004 calls the instructions or programs in memory 1005 to execute. Figure 19The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0285] This application embodiment also provides a terminal, including a processor and a communication interface. The communication interface is used to receive first protocol stack configuration information from a first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by a target service in a second network node; the processor is used to configure the protocol stack of the target service according to the first protocol stack configuration information. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 24 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0286] The terminal 1100 includes, but is not limited to, at least some of the following components: radio frequency unit 1101, network module 1102, audio output unit 1103, input unit 1104, sensor 1105, display unit 1106, user input unit 1107, interface unit 1108, memory 1109, and processor 1110.

[0287] Those skilled in the art will understand that the terminal 1100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 24 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0288] It should be understood that, in this embodiment, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042. The GPU 11041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0289] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1101 can transmit it to the processor 1110 for processing; in addition, the radio frequency unit 1101 can send uplink data to the network-side device. Typically, the radio frequency unit 1101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0290] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback function, image playback function, etc.). Furthermore, the memory 1109 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1109 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0291] Processor 1110 may include one or more processing units; optionally, processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1110.

[0292] The radio frequency unit 1101 is used to receive first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node.

[0293] Processor 1110 is used to configure the protocol stack of the target service according to the first protocol stack configuration information.

[0294] In this embodiment, a first network node sends protocol stack indication information to a second network node. The protocol stack indication information is used to indicate the protocol stack configuration method adopted by the target service at the first network node, or to indicate the protocol stack configuration method that the first network node expects the target service to adopt at the second network node. Thus, the second network node can know the protocol stack configuration method for the target service to transmit service data packets through the first network node or the protocol stack configuration method that the first network node expects the target service to adopt at the second network node based on the protocol stack indication information. This is beneficial for the second network node to accept services using simplified protocol stack configuration methods, thereby improving service continuity.

[0295] Optionally, the processor 1110 is further configured to, when the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, release the first protocol stack entity of the target service and establish a protocol stack entity of the target service based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the change in the protocol stack configuration method; or,

[0296] When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal initializes the first protocol stack entity of the target service and reconfigures the first protocol stack entity based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the protocol stack configuration method is changed.

[0297] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described mobility management method embodiments, or implement the various processes of the above-described mobility management method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0298] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0299] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described mobility management method embodiments, or to implement the various processes of the above-described mobility management method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0301] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described mobility management method embodiments, or to implement the various processes of the above-described mobility management method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0302] This application also provides a mobility management system, including: a first network node, a second network node, and a terminal, wherein the first network node is used to perform, for example... Figure 15 And the various processes of the above method embodiments, the second network node is used to execute such as Figure 16 And the various processes of the above method embodiments, the terminal is used to execute such as Figure 17 The processes of the above-described method embodiments are all the same and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0303] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0304] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0305] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A mobility management method, characterized in that, include: The first network node sends protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service in the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt in the second network node. The first network node receives feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service on the second network node; The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

2. The method according to claim 1, characterized in that, The protocol stack indication information includes at least one of the following: The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal; The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

3. The method according to claim 1, characterized in that, The protocol stack configuration method includes the following: Traditional protocol stack configuration method; Simplify protocol stack configuration.

4. The method according to claim 1, characterized in that, The target service is identified by at least one of the following information: Business session identification information; Wireless bearer identification information; Business flow identification information.

5. The method according to claim 1, characterized in that, The first network node sends protocol stack indication information to the second network node, including: The first network node sends protocol stack indication information to the second network node through a first interface, wherein the first interface is the interface between the second network node and the first network node; or The first network node sends protocol stack instruction information to the second network node via the core network node.

6. The method according to claim 1, characterized in that, Before the first network node sends protocol stack indication information to the second network node, the method further includes: The first network node selects the second network node, wherein the second network node supports the transmission of service data through a simplified protocol stack; or The first network node selects a first cell, wherein the first cell supports the transmission of service data through a simplified protocol stack, and the first cell is a cell of the second network node.

7. The method according to claim 6, characterized in that, The first network node learns that the second network node or the first cell supports the transmission of service data via a simplified protocol stack based on at least one of the following: Information exchanged between network nodes regarding their capabilities; Operation, management, and maintenance of OAM configuration information.

8. The method according to claim 1, characterized in that, If the second network node changes the protocol stack configuration of the target service, the feedback information includes first protocol stack configuration information, which is the protocol stack configuration information used by the target service in the second network node.

9. The method according to claim 8, characterized in that, After the first network node receives feedback information from the second network node, the method further includes: The first network node sends the first protocol stack configuration information to the terminal.

10. The method according to any one of claims 1-9, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

11. A mobility management method, characterized in that, include: The second network node receives protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service in the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt in the second network node. The second network node sends feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service on the second network node; The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

12. The method according to claim 11, characterized in that, After the second network node receives protocol stack indication information from the first network node, the method further includes: The second network node configures the protocol stack configuration method adopted by the target service on the second network node according to the protocol stack indication information.

13. The method according to claim 12, characterized in that, The second network node configures the protocol stack configuration method adopted by the target service on the second network node according to the protocol stack indication information, including at least one of the following: When the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node does not support the transmission of service data through the simplified protocol stack, the second network node adopts the traditional protocol stack configuration method for the target service. When the protocol stack indication information indicates a simplified protocol stack configuration method and the second network node supports the transmission of service data through the simplified protocol stack, the second network node decides to adopt the simplified protocol stack configuration method for the target service, or the second network node decides to adopt the traditional protocol stack configuration method for the target service.

14. The method according to claim 11, characterized in that, The protocol stack indication information includes at least one of the following: The first protocol stack indication information is used to indicate the protocol stack configuration method of the terminal; The second protocol stack indication information is used to indicate the protocol stack configuration method of the target service.

15. The method according to claim 11, characterized in that, The protocol stack configuration method includes the following: Traditional protocol stack configuration method; Simplify protocol stack configuration.

16. The method according to claim 11, characterized in that, The target service is identified by at least one of the following information: Business session identification information; Wireless bearer identification information; Business flow identification information.

17. The method according to claim 11, characterized in that, The first network node sends protocol stack indication information to the second network node, including: The second network node receives protocol stack indication information from the first network node through a first interface, wherein the first interface is the interface between the second network node and the first network node; or The second network node receives protocol stack instruction information from the first network node via the core network node.

18. The method according to claim 11, characterized in that, If the second network node changes the protocol stack configuration of the target service, the feedback information includes the protocol stack configuration information used by the target service in the second network node.

19. The method according to any one of claims 11-18, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

20. A mobility management method, characterized in that, include: The terminal receives first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node; The terminal configures the protocol stack of the target service according to the first protocol stack configuration information; The first protocol stack configuration information is the information included in the feedback information sent by the second network node to the first network node; The feedback information is feedback on the protocol stack indication information sent by the first network node to the second network node. The protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service at the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt at the second network node. The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

21. The method according to claim 20, characterized in that, The terminal configures the protocol stack of the target service according to the first protocol stack configuration information, including: When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal releases the first protocol stack entity of the target service and establishes a new protocol stack entity for the target service based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the change in protocol stack configuration method; or, When the first protocol stack configuration information indicates a change in the protocol stack configuration method of the target service, the terminal initializes the first protocol stack entity of the target service and reconfigures the first protocol stack entity based on the first protocol stack configuration information, wherein the first protocol stack entity is the protocol stack entity corresponding to the protocol stack configuration method of the target service before the protocol stack configuration method is changed.

22. The method according to any one of claims 20-21, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

23. A mobility management device, characterized in that, include: The first sending module is used to send protocol stack indication information to the second network node, wherein the protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service in the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt in the second network node. The first receiving module is configured to receive feedback information from the second network node, wherein the feedback information is used to indicate the protocol stack configuration method used by the target service in the second network node; The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

24. The apparatus according to claim 23, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

25. A mobility management device, characterized in that, include: The second receiving module is used to receive protocol stack indication information from the first network node, wherein the protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service in the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt in the second network node. The second sending module is used to send feedback information to the first network node, wherein the feedback information is used to indicate the protocol stack configuration method adopted by the target service in the second network node; The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

26. The apparatus according to claim 25, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

27. A mobility management device, characterized in that, include: The third receiving module is used to receive first protocol stack configuration information from the first network node, wherein the first protocol stack configuration information is the protocol stack configuration information adopted by the target service in the second network node; The configuration module is used to configure the protocol stack of the target service according to the first protocol stack configuration information; The first protocol stack configuration information is the information included in the feedback information sent by the second network node to the first network node; The feedback information is feedback on the protocol stack indication information sent by the first network node to the second network node. The protocol stack indication information is used to indicate the simplified protocol stack configuration method adopted by the target service in the first network node, or to indicate the simplified protocol stack configuration method that the first network node expects the target service to adopt in the second network node. The simplified protocol stack configuration method includes at least one of the following: Disable the reverse mapping function at the Service Data Adaptation Protocol (SDAP) layer; The Packet Data Convergence Protocol (PDCP) enables the function of short sequence numbers, wherein the length of the short sequence number is less than or equal to 8 bits. The Media Access Control (MAC) layer disables the MAC multiplexing function.

28. The apparatus according to claim 27, characterized in that, The simplified protocol stack configuration method also includes: the Radio Link Control (RLC) layer adopts a transparent transmission mode.

29. A network node, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the mobility management method as described in any one of claims 1 to 10.

30. A network node, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the mobility management method as described in any one of claims 11 to 19.

31. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the mobility management method as described in any one of claims 20 to 22.

32. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the mobility management method as described in any one of claims 1 to 10, or the steps of the mobility management method as described in any one of claims 11 to 19, or the steps of the mobility management method as described in any one of claims 20 to 22.

Images