Access network equipment, wireless side data processing method and readable storage medium

Abstract

The present application discloses an access network device, a wireless-side data processing method, and a readable storage medium, relating to the field of communications. The access network device includes a data management function (DMF) entity, the DMF entity comprising a data management function (Control Plane) (DMF-CP) entity and a data management function (User Plane) (DMF-UP) entity. The DMF-CP entity is configured to provide storage and management services for terminal (UE) contexts, and the DMF-UP entity is configured to provide storage and management services for user-plane data. In the access network device of an embodiment of the present application, by providing a DMF entity comprising a DMF-CP entity and a DMF-UP entity, wireless network-side status data can be separated from the processing process, thereby enhancing network scalability and improving network reliability.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an access network device, a wireless side data processing method, and a readable storage medium. Background Art

[0002] Services are generally divided into stateful services and stateless services. The difference between the two is whether the service needs to be associated with a context when running on the server after a request is initiated. The Third Generation Mobile Communications (3GPP) introduced a stateless architecture in the core network of the fifth-generation mobile communication technology (5th-Generation, 5G) to achieve network optimization and better reliability and elasticity. 3GPP defined an unstructured data storage function (UDSF) to uniformly store the state data of network function entities (NF) (also known as unstructured data, such as mobile data, etc.). Business logic applications (Application, App) can perform elasticity, expansion, destruction, rebirth, and migration operations at any time to achieve separation of computing and storage. The stateless design not only achieves architectural reliability, but also ensures data reliability.

[0003] Existing radio access networks are stateful. Each layer of the protocol stack on the Radio Access Network (RAN) side receives specific services from the layer below it and is responsible for providing specific services to the layer above it. A stateful network function / element must retain user information or contextual information associated with the transport layer, and the implementation of each layer of the protocol stack is linked to the protocols of the upper and lower layers. From a service perspective, due to the strong correlation between successive requests for stateful services, the data processing flow is serial and relatively fixed, which often makes horizontal expansion difficult and has poor scalability. Summary of the Invention

[0004] The embodiments of the present application provide an access network device, a wireless side data processing method and a readable storage medium, which solve the problems that the current stateful service requests have a strong correlation between each other, the data processing flow is serial and relatively fixed, it is difficult to expand horizontally, and the scalability is poor.

[0005] In a first aspect, to achieve the above-mentioned object, an embodiment of the present application provides an access network device, including: a data management function DMF entity, wherein the DMF entity includes a data management function control plane DMF-CP entity and a data management function user plane DMF-UP entity;

[0006] The DMF-CP entity is used to provide storage and management services for the terminal UE context; the DMF-UP entity is used to provide storage and management services for user plane data.

[0007] Optionally, the access network device further includes: at least one first centralized unit CU entity within a first range, the first CU entity including a first centralized unit control plane CU-CP entity and a first centralized unit user plane CU-UP entity; the first range is related to the DMF-CP entity;

[0008] The DMF-CP entity is connected in communication with the first CU-CP entity for transmitting the UE context, and the DMF-UP entity is connected in communication with the first CU-UP entity for transmitting the user plane data.

[0009] Optionally, the UE context storage and management service includes at least one of the following:

[0010] subscribing to and storing a UE context of a terminal accessing a CU entity within the first range or a distributed unit DU entity associated with the CU entity;

[0011] Sending a UE context required by the first target CU-CP entity to a first target CU-CP entity, where the first target CU-CP entity is located within the first range;

[0012] Sending a UE context required by a second target CU-CP entity to a DMF-CP entity associated with the second target CU-CP entity, where the second target CU-CP entity is located outside the first range.

[0013] Optionally, the DMF-UP entity is used to manage user plane data, including at least one of the following:

[0014] Buffering the received user plane data in a data queue, and inserting the positioning identification data into the data queue;

[0015] Sending the data queue to a first target CU-UP entity, where the first target CU-UP entity is located within the first range;

[0016] The data queue is sent to a DMF-CP entity associated with a second target CU-UP entity, and the second target CU-UP entity is located outside the first range.

[0017] In a second aspect, to achieve the above-mentioned objectives, an embodiment of the present application provides a wireless side data processing method, which is applied to a first DMF-CP entity, including:

[0018] Sending a UE context subscription message to a first CU-CP entity within a first scope; wherein the first scope is related to the DMF-CP entity;

[0019] receiving a UE context notification message sent by the first CU-CP entity, where the UE context notification message includes a real-time UE context of a UE accessing the first CU-CP entity;

[0020] The cached UE context is updated according to the received real-time UE context.

[0021] Optionally, the method further includes:

[0022] receiving a termination message sent by the first CU-CP entity;

[0023] In response to the termination message, a currently cached UE context related to the termination message is released.

[0024] Optionally, the method further includes:

[0025] receiving a UE context request message sent by the first CU-CP entity;

[0026] In response to the UE context request message, a UE context of a first target UE group is sent to the first CU-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

[0027] Optionally, the method further includes:

[0028] receiving a UE context forwarding request message sent by the first CU-CP entity, where the UE context forwarding request message includes a target CU ID;

[0029] In response to the UE context forwarding request message, the UE context of the second target UE group is sent to the second CU-CP entity corresponding to the target CU ID, where the second target UE group includes at least one UE that is switched from accessing the first CU-CP entity to accessing the second CU-CP entity.

[0030] Optionally, sending the UE context of the second target UE group to the second CU-CP entity includes:

[0031] In a case where the second CU-CP entity is located outside the first range, the UE context of the second target UE group is sent to the second CU-CP entity via a second DMF-CP entity, wherein the second DMF-CP is associated with the second CU-CP entity.

[0032] In a third aspect, to achieve the above-mentioned objectives, an embodiment of the present application provides a wireless side data processing method, which is applied to a second DMF-CP entity, including:

[0033] receiving a UE context of a second target UE group sent by the first DMF-CP entity;

[0034] Send the UE context of the second target UE group to the second CU-CP entity; wherein the second DMF-CP is associated with the second CU-CP entity, the second target UE group includes at least one UE that is switched from accessing the first CU-CP entity to accessing the second CU-CP entity, and the first CU-CP entity is associated with the first DMF-CP entity.

[0035] Optionally, the method further includes:

[0036] During the process of a UE in the second target UE group randomly accessing a cell corresponding to the second CU-CP entity, sending a path switching request to a core network device;

[0037] Receive a path switching response sent by the core network device.

[0038] In a fourth aspect, to achieve the above-mentioned objectives, an embodiment of the present application provides a wireless side data processing method, applied to a first DMF-UP entity, comprising:

[0039] Receive user plane data sent by the user plane function UPF entity;

[0040] caching the received user plane data into a data queue according to the order of the received user plane data;

[0041] According to the data queue, the user plane data is sent to a first target CU-UP entity, wherein the first target CU-UP entity is located within a first range, the first range is associated with the first DMF-UP, and the UE corresponding to the user plane data is a UE accessing the first target CU-UP entity.

[0042] Optionally, the method further includes:

[0043] According to preconfigured rules, the positioning identification data is inserted into the cached data queue.

[0044] Optionally, the method further includes:

[0045] receiving a user plane data forwarding request sent by the first target CU-UP entity, where the user plane data forwarding request includes at least one of a target CU ID, a hyperframe number HFN, a sequence number SN corresponding to the HFN, and a DMF identifier;

[0046] In response to the user plane data forwarding request, perform at least one of the following:

[0047] Stop sending user plane data to the first target CU-UP entity;

[0048] Buffering user plane data received from the UPF entity;

[0049] According to the HFN, the SN and the positioning identification data, user plane data of the third target UE group is sent to the second target CU-UP entity corresponding to the target CU ID, wherein the third target UE group is at least one UE that switches from accessing the first target CU-UP entity to accessing the second target CU-UP entity.

[0050] Optionally, sending user plane data of the third target UE group to the second target CU-UP entity includes any one of the following:

[0051] When a second target CU-UP entity corresponding to the target CU ID is located within the first range, sending user plane data of a third target UE group to the second target CU-UP entity;

[0052] In a case where the second target CU-UP entity corresponding to the target CU ID is outside the first range, the user plane data of the third target UE group is sent to the second target CU-UP entity through the second DMF-UP entity corresponding to the DMF identifier.

[0053] Optionally, sending user plane data of a third target UE group to the second target CU-UP entity according to the HFN, the SN, and the positioning identifier data includes:

[0054] determining, according to the HFN, the SN, and the positioning identifier data, user plane data not processed by the first target CU-UP entity;

[0055] Send the unprocessed user plane data to the second target CU-UP entity in sequence.

[0056] In a fifth aspect, to achieve the above-mentioned objectives, embodiments of the present application provide a radio-side data processing method, applied to a first CU-CP entity, comprising:

[0057] Receiving a UE context subscription message sent by the first DMF-CP entity;

[0058] In response to the UE context subscription message, a UE context notification message is sent to the first DMF-CP entity, where the UE context notification message includes a real-time UE context of the UE accessing the first CU-CP entity.

[0059] Optionally, sending a UE context notification message to the first DMF-CP entity includes:

[0060] When the UE context of the terminal accessing the first CU-CP entity changes, the UE context notification message is sent to the first DMF-CP entity.

[0061] Optionally, the method further includes:

[0062] Send a termination message to the first DMF-CP entity.

[0063] Optionally, the method further includes:

[0064] Sending a UE context request message to the first DMF-CP entity;

[0065] Receive a UE context of a first target UE group sent by the first DMF-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

[0066] Optionally, the method further includes:

[0067] A UE context forwarding request message is sent to the first DMF-CP entity, where the UE context forwarding request message includes a target CU ID.

[0068] In a sixth aspect, to achieve the above-mentioned objectives, embodiments of the present application provide a radio-side data processing method, applied to a first CU-UP entity, comprising:

[0069] Receive user plane data sent by the first DMF-UP entity, where the UE corresponding to the user plane data is the UE accessing the first CU-UP entity.

[0070] Optionally, the method further includes:

[0071] A user plane data forwarding request is sent to the first DMF-UP entity, where the user plane data forwarding request includes at least one of a target CU ID, a hyperframe number HFN, a sequence number SN corresponding to the HFN, and a DMF identifier.

[0072] In the seventh aspect, in order to achieve the above-mentioned purpose, an embodiment of the present application provides an access network device, including a transceiver, a processor, a memory, and a program stored on the memory and runnable on the processor; when the processor executes the program, it implements the wireless side data processing method as described in the second aspect, or implements the wireless side data processing method as described in the third aspect, or implements the wireless side data processing method as described in the fourth aspect, or implements the wireless side data processing method as described in the fifth aspect, or implements the wireless side data processing method as described in the sixth aspect.

[0073] In the eighth aspect, in order to achieve the above-mentioned purpose, an embodiment of the present application provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by the processor, it implements the wireless side data processing method as described in the second aspect, or implements the wireless side data processing method as described in the third aspect, or implements the wireless side data processing method as described in the fourth aspect, or implements the wireless side data processing method as described in the fifth aspect, or implements the wireless side data processing method as described in the sixth aspect.

[0074] The beneficial effects of the above technical solution of this application are as follows:

[0075] The access network equipment of an embodiment of the present application includes: a data management function (DMF) entity, wherein the DMF entity includes a data management function control plane (DMF-CP) entity and a data management function user plane (DMF-UP) entity; wherein the DMF-CP entity is used to provide storage and management services for terminal (UE) context; and the DMF-UP entity is used to provide storage and management services for user plane data. By adding DMF entities including the DMF-CP entity and the DMF-UP entity to the access network equipment, it is possible to separate wireless network status data from the processing process, thereby enhancing network scalability and improving network reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Figure 1 This is one of the structural diagrams of the access network device according to an embodiment of the present application;

[0077] Figure 2 This is a flowchart of a wireless side data processing method according to an embodiment of the present application;

[0078] Figure 3 This is a second flow chart of the wireless side data processing method according to an embodiment of the present application;

[0079] Figure 4 This is a third flow chart of the wireless side data processing method according to an embodiment of the present application;

[0080] Figure 5This is a fourth flow chart of the wireless side data processing method according to an embodiment of the present application;

[0081] Figure 6 This is a fifth flowchart of the wireless side data processing method according to an embodiment of the present application;

[0082] Figure 7 Schematic diagram of the UE context subscription and notification process in an embodiment of the present application;

[0083] Figure 8 This is a schematic diagram of the UE context request process in an embodiment of the present application;

[0084] Figure 9 This is a schematic diagram of the UE context forwarding process in an embodiment of the present application;

[0085] Figure 10 This is a schematic diagram of the user plane data link forwarding process in an embodiment of the present application;

[0086] Figure 11 This is one of the switching process diagrams based on stateless service in an embodiment of the present application;

[0087] Figure 12 This is the second schematic diagram of the switching process based on the stateless service in the embodiment of the present application;

[0088] Figure 13 This is the second structural diagram of the access network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0089] In order to make the technical problems, technical solutions and advantages to be solved by this application clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0090] It should be understood that references throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0091] In the various embodiments of the present application, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0092] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0093] In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0094] like Figure 1 As shown, an embodiment of the present application provides an access network device, including: a data management function DMF (Data Management Function, DMF) entity, the DMF entity including a data management function control plane (Data Management Function Control Plane, DMF-CP) entity and a data management function user plane (Data Management Function User Plane, DMF-UP) entity;

[0095] The DMF-CP entity is used to provide storage and management services for the terminal (User Equipment, UE) context; the DMF-UP entity is used to provide storage and management services for user plane data.

[0096] An access network device according to an embodiment of the present application includes a DMF entity, which includes a DMF-CP entity and a DMF-UP entity. The DMF-CP entity is configured to provide storage and management services for UE context, and the DMF-UP entity is configured to provide storage and management services for user plane data. By adding a DMF entity including the DMF-CP entity and the DMF-UP entity to the access network device, wireless network status data can be separated from the processing process, thereby enhancing network scalability and improving network reliability.

[0097] Furthermore, if Figure 1 As shown, the access network device further includes: at least one first centralized unit (CU) entity within a first range, the first CU entity including a first centralized unit control plane (CU-CP) entity and a first centralized unit user plane (CU-UP) entity; the first range is related to the DMF-CP entity;

[0098] The DMF-CP entity is connected in communication with the first CU-CP entity for transmitting UE context, and the DMF-UP entity is connected in communication with the first CU-UP entity for transmitting user plane data.

[0099] Here, the first range may be a pre-configured range, for example, a range centered or starting at the DMF entity, and each first CU entity within the first range is associated with the DMF entity, i.e., the two can communicate with each other. In other words, the first range is a management range pre-configured for the DMF entity, i.e., the DMF entity can manage the CU entities within the range.

[0100] Also like Figure 1 As shown, the access network equipment also includes a distributed unit (DU) entity, which can communicate with the CU entity. Specifically, the 5G New Radio (NR) base station can be reconstructed into a CU entity and a DU entity, which can be deployed in one or separately depending on the scenario and needs.

[0101] As a specific implementation, the UE context storage and management service includes at least one of the following:

[0102] Subscribe to and store a UE context of a terminal accessing a CU entity or a DU entity associated with the CU entity within a first range;

[0103] Sending a UE context required by the first target CU-CP entity to a first target CU-CP entity, where the first target CU-CP entity is located within a first range;

[0104] Sending a UE context required by the second target CU-CP entity to a DMF-CP entity associated with the second target CU-CP entity, where the second target CU-CP entity is located outside the first range. In this step, by sending the UE context required by the second target CU-CP entity to the DMF-CP entity associated with the second target CU-CP entity, the DMF-CP entity associated with the second target CU-CP entity sends the received UE context required by the second target CU-CP entity to the second target CU-CP entity.

[0105] Here, the first target CU-CP entity and the second target CU-CP entity can be CU-CP entities within the target CU entity to which the UE switches from the source CU entity, that is, when the UE switches the service cell, the DMF entity will send the UE context of the UE to the CU corresponding to the target cell. Among them, the first target CU-CP entity and the source CU-CP entity are associated with the same DMF-CP entity, that is, both are located in the management scope of the same DMF-CP entity, and the second target CU-CP entity and the source CU-CP entity are associated with different DMF-CP entities, that is, both are located in the management scope of different DMF-CP entities.

[0106] As another specific implementation, the DMF-UP entity is used to manage user plane data, including at least one of the following:

[0107] The received user plane data is cached in the form of a data queue, and the positioning identification data is inserted into the data queue; here, first, the received user plane data is the data sent by the User Plane Function (UPF) entity; second, caching in the form of a data queue means caching in the order of the received user plane data; third, by introducing the positioning identification data, the CU can use the positioning identification data to correspond the Packet Data Convergence Protocol (PDCP) sequence number (SN) with the data cached in the DMF-UP, so as to locate the user plane data that the CU has processed and realize user plane data forwarding synchronization.

[0108] Sending a data queue to a first target CU-UP entity, the first target CU-UP entity being located within a first range;

[0109] Sending a data queue to a DMF-CP entity associated with a second target CU-UP entity, where the second target CU-UP entity is located outside the first range. In this step, by sending the data queue to the DMF-CP entity associated with the second target CU-UP entity, the DMF-UP entity associated with the second target CU-UP entity sends the received transmit data queue to the second target CU-CP entity.

[0110] Here, the first target CU-UP entity and the second target CU-UP entity can be CU-UP entities within the target CU entity to which the UE switches from the source CU entity. That is, when the UE switches the service cell, the DMF-UP entity will send the user plane data of the UE to the CU-UP corresponding to the target cell. Among them, the first target CU-UP entity and the source CU-UP entity are associated with the same DMF-UP entity, that is, both are located in the management scope of the same DMF-UP entity; the second target CU-CP entity and the source CU-UP entity are associated with different DMF entities, that is, both are located in the management scope of different DMF-UP entities. In addition, the above-mentioned sending data queue refers to sending data in the data queue sequentially.

[0111] In the access network equipment of the embodiment of the present application, by adding a DMF entity, firstly, the DMF-CP entity provides storage and management services for UE context, and the DMF-UP entity provides storage and management services for user plane data. In this way, the UE context and user plane data are cached and managed separately, thereby achieving independent interaction and synchronization between the control plane data and the user plane data of each base station, thereby improving data transmission efficiency. Secondly, a stateless service design is introduced on the wireless access network side, separating the wireless side state data from the processing process. Therefore, when a node or a DMF module fails, it will not cause the loss of UE context and user data, and other nodes / DMF modules can be immediately enabled, thereby enhancing network scalability and improving network reliability.

[0112] like Figure 2 As shown, the embodiment of the present application also provides a wireless side data processing method, which is applied to the first DMF-CP entity, including:

[0113] Step 201, sending a UE context subscription message to the first CU-CP entity within the first scope; wherein the first scope is related to the DMF-CP entity; here, the first scope is a range pre-configured for the DMF-CP entity, and each first CU-CP entity within the first scope can communicate with the first DMF-CP entity, that is, the first DMF-CP entity can provide services for each first CU-CP entity within the first scope.

[0114] Step 202: Receive a UE context notification message sent by the first CU-CP entity, where the UE context notification message includes the real-time UE context of the UE accessing the first CU-CP entity. For example, when the UE context accessing the first CU-CP entity changes (such as initial context establishment, UE context modification, etc.), the first CU-CP entity sends a UE context notification message to the first DMF-CP entity.

[0115] Step 203: Update the cached UE context according to the received real-time UE context.

[0116] That is to say, the first DMF-CP entity, as a service provider, will subscribe to the UE context to each first CU-CP entity within its first range, so that when a UE accesses the first CU-CP entity, or the UE context of the terminal accessing the first CU-CP entity changes, the first CU-CP entity will carry the real-time UE context in the UE context notification message and send it to the first DMF-CP entity. The first DMF-CP entity will cache the real-time UE context so as to subsequently send the UE context to the required CU-CP entity.

[0117] In the wireless side data processing method of the embodiment of the present application, first, the first DMF-CP entity sends a UE context subscription message to the first CU-CP entity within the first range; wherein the first range is related to the DMF-CP entity; secondly, the first DMF-CP entity receives the UE context notification message sent by the first CU-CP entity, and the UE context notification message includes the real-time UE context of the UE connected to the first CU-CP entity; finally, the first DMF-CP entity updates the cached UE context based on the received real-time UE context. In this way, the UE context is cached separately, and the processing and storage are separated. When a node or a DMF module fails, the UE context will not be lost, and other nodes / DMF modules can be immediately enabled, thereby improving the reliability and scalability of the RAN.

[0118] Furthermore, as an optional implementation, the method further includes:

[0119] receiving a termination message sent by the first CU-CP entity; specifically, when the first CU-CP entity determines that the UE context needs to be released, sending the termination message to the first DMF-CP entity;

[0120] In response to the termination message, the currently cached UE context related to the termination message is released.

[0121] Furthermore, as another optional implementation, the method further includes:

[0122] receiving a UE context request message sent by the first CU-CP entity;

[0123] In response to the UE context request message, a UE context of a first target UE group is sent to the first CU-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

[0124] Furthermore, as another optional implementation, the method further includes:

[0125] Receive a UE context forwarding request message sent by the first CU-CP entity, where the UE context forwarding request message includes a target CU ID; here, the first CU-CP entity can be understood as a source CU-CP entity, and the second CU-CP entity corresponding to the target CU ID can be understood as a target CU-CP entity; that is, when the UE switches the service cell from the first CU-CP entity to the second CU-CP entity corresponding to the target CU ID, the first CU-CP entity sends the UE context forwarding request to the first DMF-CP entity to request the first DMF-CP entity to forward the relevant UE context to the second CU-CP entity corresponding to the target CU-ID.

[0126] In response to the UE context forwarding request message, the UE context of the second target UE group is sent to the second CU-CP entity corresponding to the target CU ID, where the second target UE group includes at least one UE that is switched from accessing the first CU-CP entity to accessing the second CU-CP entity.

[0127] That is to say, in mobility management, after determining the target base station (including the second CU-CP entity), by enabling the UE context forwarding process of DMF-CP (the first CU-CP entity sends a UE context forwarding request to the first DMF-CP entity), the UE can immediately release the connection with the source base station (including the first CU-CP entity) without losing the context, thereby enhancing the robustness of the control plane switching.

[0128] As a specific implementation manner, sending the UE context of the second target UE group to the second CU-CP entity includes:

[0129] In a case where the second CU-CP entity is outside the first range, the UE context of the second target UE group is sent to the second CU-CP entity via the second DMF-CP entity, wherein the second DMF-CP is associated with the second CU-CP entity.

[0130] That is to say, when the first CU-CP entity and the second CU-CP entity are associated with different DMF-CPs, when the UE is switched from the first CU-CP entity to the second CU-CP entity, the first DMF-CP entity needs to send the relevant UE context to the second DMF-CP entity associated with the second CU-CP entity, so that the second DMF-CP entity can send the UE context to the second CU-CP entity.

[0131] When the first CU-CP entity and the second CU-CP entity are associated with the same DMF-CP entity (the first DMF-CP entity), when the UE is switched from the first CU-CP entity to the second CU-CP entity, the first DMF-CP entity can send the relevant UE context directly to the second CU-CP entity. In this way, there is no need for the access network device and the core network device to perform path switching, thereby reducing unnecessary communication between the access network device and the core network device.

[0132] like Figure 3 As shown, an embodiment of the present application also provides a radio side data processing method, which is applied to a second DMF-CP entity, where the second DMF-CP entity is a DMF-CP entity corresponding to a target cell when the UE performs cell handover, the method comprising:

[0133] Step 301, receiving the UE context of the second target UE group sent by the first DMF-CP entity; here, the UE in the second target UE group is the UE switched from the service cell corresponding to the first DMF-CP entity to the service cell corresponding to the second DMF-CP entity.

[0134] Step 302: Send a UE context for a second target UE group to a second CU-CP entity; wherein the second DMF-CP is associated with the second CU-CP entity, the second target UE group includes at least one UE that switches from accessing the first CU-CP entity to accessing the second CU-CP entity, and the first CU-CP entity is associated with the first DMF-CP entity. Here, the association of the second DMF-CP entity with the second CU-CP entity means that the second CU-CP entity is located within a second range covered by the second DMF-CP entity, or in other words, the second CU-CP entity is able to communicate with the second DMF-CP entity.

[0135] In the wireless side data processing method of an embodiment of the present application, when a UE in the second target UE group is switched from a source service cell corresponding to a first CU-CP entity to a target service cell corresponding to a second CU-CP entity, first, the second DMF-CP entity receives the UE context of the second target UE group sent by the first DMF-CP entity, and secondly, the second DMF-CP entity sends the UE context of the second target UE group to the second CU-CP entity associated with the second DMF-CP entity. In this way, in mobility management, after determining the target base station, by enabling the UE context forwarding process of the DMF-CP, the UE can immediately release the connection with the source base station without losing the context, thereby enhancing the robustness of the control plane switching.

[0136] Furthermore, as an optional implementation, the method further includes:

[0137] During the process of a UE in the second target UE group randomly accessing a cell corresponding to the second CU-CP entity, sending a path switching request to the core network device;

[0138] Receive the path conversion response sent by the core network device.

[0139] That is to say, when the UE performs cell handover, the user plane data path switching can be executed synchronously with the UE random access process, converting the original serial process into a parallel process, thereby realizing fast mobility management.

[0140] like Figure 4 As shown, the embodiment of the present application also provides a wireless side data processing method, which is applied to the first DMF-UP entity, including:

[0141] Step 401: Receive user plane data sent by the UPF entity;

[0142] Step 402: Cache the received user plane data as a data queue according to the order in which the user plane data are received; that is, this step caches the user plane data as a data queue according to the order in which the user plane data are received, that is, for each user plane data received, the user plane data is cached after the last data in the data queue.

[0143] Step 403: User plane data is sent to the first target CU-UP entity according to the data queue. The first target CU-UP entity is located within a first range, the first range is associated with the first DMF-UP, and the UE corresponding to the user plane data is the UE accessing the first target CU-UP entity. In other words, the first range can be understood as the range that can be covered by the first DMF-UP entity.

[0144] In the wireless side data management method of the embodiment of the present application, the first DMF-UP entity in the access network device first receives the user plane data sent by the UPF entity, and secondly, according to the order of the received user plane data, caches the received user plane data as a data queue, and finally, according to the data queue, sends the user plane data to the first target CU-UP entity, wherein the first target CU-UP entity is located within the first range, the first range is associated with the first DMF-UP, and the UE corresponding to the user plane data is the UE accessing the first target CU-UP entity. In this way, the caching and sending of user plane data are realized. Combined with the aforementioned wireless side data management method applied to the first DMF-CP entity, in the DMF entity of the access network device, the first DMF-CP entity provides UE context storage and management services, and the first DMF-UP entity provides user plane data storage and management services. In this way, the data synchronization of the control plane and the user plane can be realized independently, thereby improving the data transmission efficiency.

[0145] Furthermore, as an optional implementation, the method further includes:

[0146] According to the pre-configured rules, the location identification data is inserted into the cached data queue. For example, a location identification data is added after every N user plane data. In this way, the first DMF-UP entity will send a location identification data after sending every N data packets, so that the CU-UP entity can use this location identification data to match the downlink PDCP SN with the data cached in the first DMF-UP entity. For example: PDCP SN corresponds to DMF data identification i ud , then PDCP (SN+1) corresponds to DMF data identifier i ud In this way, in a cell handover scenario, the user plane data that has been processed by the source CU entity can be located based on the data identifier, thereby achieving user plane data forwarding synchronization.

[0147] Furthermore, as an optional implementation, the method further includes:

[0148] Receive a user plane data forwarding request sent by the first target CU-UP entity, where the user plane data forwarding request includes at least one of a target CU ID, a hyper frame number (HFN), a sequence number SN corresponding to the HFN, and a DMF identifier; wherein the HFN and the SN are related to the user data that has been processed by the first target CU-UP, for example, the SN is the SN of the data that the first target CU-UP entity has received feedback confirmation from the UE.

[0149] Here, the first target CU-UP entity is the first CU-UP entity within the first range covered by the first DMF-UP entity; for example, when the first target CU-UP entity and the second target CU-UP entity corresponding to the target CU ID are associated with different DMF-UP entities, the user plane data forwarding request carries the DMF identifier, wherein the second DMF-UP entity corresponding to the DMF identifier is associated with the second CU-UP entity; that is, the user plane data forwarding request includes the target CU ID, HFN and the SN corresponding to the HFN; or, the user plane data forwarding request includes the target CU ID, HFN and the SN corresponding to the HFN, and the DMF identifier.

[0150] In response to the user plane data forwarding request, perform at least one of the following:

[0151] Stop sending user plane data to the first target CU-UP entity;

[0152] Cache user plane data received from the UPF entity;

[0153] According to the HFN, SN and positioning identification data, the user plane data of the third target UE group is sent to the second target CU-UP entity corresponding to the target CU ID, wherein the third target UE group is at least one UE that switches from accessing the first target CU-UP entity to accessing the second target CU-UP entity.

[0154] That is to say, after the first DMF-UP entity receives the user plane data forwarding request sent by the first target CU-UP entity, the first DMF-UP entity stops sending user plane data to the first target CU-UP entity, continues to receive and cache the user plane data sent by the UPF entity, and sends the required user plane data to the second target CU-UP entity corresponding to the target CU ID based on the HFN and SN in the user plane data forwarding request, as well as the positioning identification data. In this way, in the cell switching scenario, the UE can resume the transmission of user plane data immediately after accessing the target cell.

[0155] As a specific implementation manner, sending user plane data of the third target UE group to the second target CU-UP entity includes any of the following:

[0156] When the second target CU-UP entity corresponding to the target CU ID is located within the first range, the user plane data of the third target UE group is sent to the second target CU-UP entity; that is, when the first target CU-UP entity and the second target CU-UP entity are both located in the first range covered by the first DMF-UP entity, that is, when the first target CU-UP entity and the second target CU-UP entity are both associated with the first DMF-UP entity, the first DMF-UP entity can directly forward the user plane data to the second target CU-UP entity without the need for the second CU-UP entity to interact with the core network device for path conversion. In this way, unnecessary interaction between the access network device and the core network can be reduced, and the switching process can be simplified.

[0157] When the second target CU-UP entity corresponding to the target CU ID is located outside the first range, user plane data of the third target UE group is sent to the second target CU-UP entity through the second DMF-UP entity. That is, when the first target CU-UP entity is located in the first range covered by the first DMF-UP entity and the second target CU-UP entity is located outside the first range, for example, the second target CU-UP entity is located in the second range covered by the second DMF-UP entity, that is, when the first target CU-UP entity is associated with the first DMF-UP entity and the second target CU-UP entity is associated with the second DMF-UP entity, in a cell handover scenario, after the first DMF-UP entity receives the user plane data forwarding request sent by the first CU-UP entity, the first DMF-UP entity stops sending user plane data to the first target CU-UP entity, continues to receive and buffer the user plane data sent by the UPF entity, and sends the user plane data not processed by the first target CU-UP entity to the second DMF-UP entity corresponding to the DMF identifier based on the HFN and SN in the user plane data forwarding request and the positioning identifier data, so that the second DMF-UP entity sends the received user data to the second target CU-UP entity.

[0158] As a specific implementation manner, sending user plane data of the third target UE group to the second target CU-UP entity according to the HFN, SN and positioning identifier data includes:

[0159] According to the HFN, SN and positioning identification data, the user plane data that has not been processed by the first target CU-UP entity is determined; as mentioned above, the SN is the SN for which the user has received terminal feedback confirmation. Therefore, the first DMF-UP entity corresponds to the positioning identification data according to the HFN and SN to locate the user data that has not been processed by the first CU-UP entity.

[0160] Send unprocessed user plane data to the second target CU-UP entity in sequence.

[0161] like Figure 5 As shown, the embodiment of the present application further provides a wireless side data processing method, which is applied to a first CU-CP entity, including:

[0162] Step 501: receiving a UE context subscription message sent by a first DMF-CP entity;

[0163] Step 502: In response to the UE context subscription message, a UE context notification message is sent to the first DMF-CP entity, where the UE context notification message includes the real-time UE context of the UE accessing the first CU-CP entity.

[0164] In the wireless side data processing method of an embodiment of the present application, when the first CU-CP entity receives the UE context subscription message sent by the first DMF-CP entity, the first CU-CP entity sends a UE context notification message to the first DMF-CP entity, thereby realizing the subscription and caching service of the first DMF-CP entity to the UE context. When a node or a DMF module fails, the UE context will not be lost, and other nodes / DMF modules can be immediately enabled, thereby enhancing network scalability and improving network reliability.

[0165] As a specific implementation manner, sending a UE context notification message to the first DMF-CP entity includes:

[0166] When the UE context of the terminal accessing the first CU-CP entity changes, a UE context notification message is sent to the first DMF-CP entity. That is, when the UE context of the terminal accessing the first CU-CP entity changes, such as initial context establishment or UE context modification, the first CU-CP entity sends the latest UE group context to the first DMF-CP entity in a notification message, and updates the cache in the first DMF-CP entity.

[0167] Furthermore, as an optional implementation, the method further includes:

[0168] Sending a termination message to the first DMF-CP entity. For example, when the UE context is released, the first CU-CP entity may send the termination message to the first DMF-CP entity to instruct the first DMF-CP entity to release the current UE context cache.

[0169] like Figure 7 As shown in FIG, a schematic diagram of the UE context subscription and notification process in an embodiment of the present application is shown, and the specific process includes:

[0170] First, the DMF-CP (specifically, for example, the first DMF-CP entity) sends a UE context subscription message to each CU-CP (specifically, for example, the first CU-CP entity); wherein each CU-CP is a CU-CP within the coverage of the DMF-CP.

[0171] Secondly, the CU-CP sends a UE context notification message to the DMF-CP, which includes the latest UE context or a termination message. As mentioned above, when the UE context accessing the CU-CP changes, for example, when an initial context is established or a UE context is modified, the CU-CP sends the latest UE group context to the DMF-CP in the notification message, so that the DMF-CP updates the cached UE context; or,

[0172] When the UE context is released, the CU-CP sends a termination message to the DMF-CP, so that the DMF-CP releases the current UE context buffer.

[0173] Furthermore, as an optional implementation, the method further includes:

[0174] Sending a UE context request message to the first DMF-CP entity;

[0175] Receive a UE context of a first target UE group sent by a first DMF-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

[0176] like Figure 8 As shown, the UE context request process includes: first, the CU-CP sends a UE context request message to the corresponding DMF-CP; second, the DMF-CP feeds back a UE context response message to the CU-CP, wherein the UE context response message includes the UE context of the corresponding UE group.

[0177] Furthermore, as an optional implementation, the method further includes:

[0178] Send a UE context forwarding request message to the first DMF-CP entity, where the UE context forwarding request message includes the target CU ID. For example, in mobility management, after determining the target base station / target cell, the first CU-CP entity sends a UE context forwarding request message to the first DMF-CP entity to instruct the first DMF-CP entity to forward the corresponding UE context to the second target CU-CP entity corresponding to the target CUID.

[0179] like Figure 9 As shown, the UE context forwarding process includes: first, the source CU-CP sends a UE context forwarding request message to the corresponding DMF-CP, and the UE context forwarding request message includes the target CU ID; secondly, the DMF-CP feeds back a UE context forwarding response message to the source CU-CP, for example, the response message includes a confirmation, etc.; thirdly, the DMF-CP forwards the UE context to the target CU-CP.

[0180] like Figure 6 As shown, the embodiment of the present application further provides a radio side data processing method, which is applied to a first CU-UP entity, including:

[0181] Receive user plane data sent by the first DMF-UP entity, where the UE corresponding to the user plane data is the UE accessing the first CU-UP entity.

[0182] In the wireless side data processing method of an embodiment of the present application, the first CU-UP entity receives the user plane data sent by the first DMF-UP entity to send the received user plane data to the corresponding UE. In this way, the synchronization of the UE context and the user plane data on the wireless side is achieved independently, thereby improving data transmission efficiency.

[0183] Furthermore, as an optional implementation, the method further includes:

[0184] A user plane data forwarding request is sent to the first DMF-UP entity, where the user plane data forwarding request includes at least one of the target CU ID, the hyperframe number HFN, the sequence number SN corresponding to the HFN, and the DMF identifier. This instructs the first DMF-UP entity to forward the user plane data to the second CU-UP entity corresponding to the target CU ID. The second CU-UP entity is the CU-UP entity corresponding to the serving cell newly accessed by the UE. For example, the user plane data forwarding request includes the target CU ID, the HFN, and the SN corresponding to the HFN; or, the user plane data forwarding request includes the target CU ID, the HFN, the SN corresponding to the HFN, and the DMF identifier.

[0185] like Figure 10As shown, the user plane data forwarding process includes two steps: the source CU-UP sends a user plane data forwarding request to the corresponding DMF-UP, and the DMF-UP forwards the user plane data to the target CU-UP.

[0186] Next, combine Figure 11 , describes the switching process based on stateless services, specifically, Figure 11 This applies to scenarios where the target cell and the source cell are managed by the same DMF.

[0187] After a UE accesses the source gNB, it transmits uplink and downlink user data to the DMF and UPF through the source gNB. Furthermore, the source and target gNBs interact with the DMF to implement DMF subscription caching. This means that before and during the handover process, the DMF subscribes to and caches data for the base stations within its control area.

[0188] When a UE is handed over from a source gNB to a target gNB, the following steps are performed:

[0189] 1. The source base station sends a handover request message to the target base station. This step is specifically that the CU-CP of the source base station sends the handover request message to the CU-CP of the target base station.

[0190] 2. The target base station performs admission control.

[0191] 3. The target base station (CU-CP of the target base station) sends a handover request confirmation message to the source base station (CU-CP of the source base station). The confirmation message includes the handover command sent to the UE, including parameters such as the target cell identifier. Specifically, the target base station sends a handover request confirmation to the source base station after preparing for the handover.

[0192] 4. The source base station CU sends a context change request to the source base station DU, instructing the source base station DU and the source base station CU to stop data transmission.

[0193] 5. The source base station sends a handover command to the terminal. For example, the handover command is an RRC reconfiguration message.

[0194] 6. The source base station DU feeds back a UE context change response to the source base station CU.

[0195] 7. The source base station CU sends a UE context and user data forwarding request to the DMF, which includes the target cell identifier and the HFN and corresponding SN number processed by the source CU.

[0196] 8. DMF forwards the current cache data to the target base station (CU of the target base station). DMF-CP communicates directly with the target base station CU-CP to transmit the UE context. DMF-UP establishes a data transmission link with the target base station CU-UP. DMF-UP uses the received HFN and the corresponding SN number to communicate with the positioning identifier i ud Correspondingly, the user data that has not been processed by the source CU is located and the downlink user data transmission is started from this location.

[0197] 9. The UE initiates random access to the target cell (DU of the target base station) and successfully accesses the target cell.

[0198] 10. The UE sends an RRC reconfiguration complete message to the DU of the target base station to confirm to the target base station that the handover process is complete.

[0199] 11. The UE of the target base station sends an uplink RRC message to the CU of the target base station.

[0200] Afterwards, after successful random access, the UE exchanges uplink and downlink user data with the target base station.

[0201] 12. The target base station (CU of the target base station) sends a UE context release message to the source base station (CU of the source base station), notifying the source base station of the successful handover and triggering the source base station to release the terminal context.

[0202] Next, combine Figure 12 , describes the switching process based on stateless services, specifically, Figure 12 This is for scenarios where the target cell and the source cell are managed by different DMFs.

[0203] After a UE accesses the source gNB, it transmits uplink and downlink user data to the DMF and UPF via the source gNB. Furthermore, the source gNB interacts with the source DMF, and the target gNB interacts with the target DMF to implement DMF subscription caching. In other words, before and during the handover process, the DMFs of the source and target gNBs subscribe to, request, and cache data. The specific process is as described above and will not be repeated here.

[0204] When a UE is handed over from a source gNB to a target gNB, the following steps are performed:

[0205] 1. The source base station sends a handover request message to the target base station. This step is specifically that the CU-CP of the source base station sends the handover request message to the CU-CP of the target base station.

[0206] 2. The target base station performs admission control.

[0207] 3. The target base station (CU-CP of the target base station) sends a handover request confirmation message to the source base station (CU-CP of the source base station). The confirmation message includes the handover command sent to the UE, including parameters such as the target cell identifier and the target cell DMF identifier. Specifically, the target base station sends a handover request confirmation to the source base station after preparing for the handover.

[0208] 4. The source base station CU sends a context change request to the source base station DU, instructing the source base station DU and the source base station CU to stop data transmission.

[0209] 5. The source base station sends a handover command to the terminal. For example, the handover command is an RRC reconfiguration message.

[0210] 6. The source base station DU feeds back a UE context change response to the source base station CU.

[0211] 7. The source base station CU sends a UE context and user data forwarding request to the corresponding DMF, which includes the target cell identifier, the HFN processed by the source CU and the corresponding SN number and the target DMF identifier.

[0212] 8. The source DMF forwards the current cached UE context and user data that has not been processed by the source CU to the target DMF ( Figure 12 The dotted arrows between the source DMF and the target DMF in the middle correspond to the cached downlink user data), where the DMF-CP communicates directly to transmit the UE context; the DMF-UP communicates directly to transmit user data.

[0213] 9. The target DMF synchronizes the UE context forwarded by the source DMF to the target CU.

[0214] 10a. The target DMF sends a path switching request to the core network (CN) to inform the core network that the UE has changed cells, triggering the core network to switch the downlink data path to the target DMF.

[0215] 11a. The CN sends a path switching response to the target DMF.

[0216] 10b. The UE initiates random access to the target cell and successfully accesses the target cell.

[0217] 11b. The UE sends an RRC reconfiguration complete message to the DU of the target base station, confirming to the target base station that the handover process is complete.

[0218] 12. The UE of the target base station sends an uplink RRC message to the CU of the target base station.

[0219] Afterwards, after successful random access, the UE exchanges uplink and downlink user data with the target base station.

[0220] 13. The target base station (CU of the target base station) sends a UE context release message to the source base station (CU of the source base station), notifying the source base station of the successful handover and triggering the source base station to release the terminal context.

[0221] In the access network equipment of the embodiment of the present application, a DMF functional entity is added, and the DMF functional entity is subdivided into a DMF-CP entity and a DMF-UP entity to provide cache and management services for the control plane UE context data and the user plane data, respectively, and the services provided by the function and the related parameters introduced are defined in detail. The stateless service design is introduced in the wireless access network, and the wireless side state data is separated from the processing process. Specifically, when the DMF entity acts as a service consumer, the DMF-CP entity provides UE context subscription and cache services, and the DMF-UP entity provides user plane downlink data cache and location identifier addition services; when the DMF entity acts as a service provider, the DMF-CP entity provides UE context response and forwarding, and the DMF-UP entity provides user plane downlink data link establishment and downlink data forwarding synchronization services. In this way, when a node or a DMF module fails, it will not cause the loss of UE context and user data, thereby enhancing network scalability and improving network reliability. By separating the DMF control plane and the user plane, independent interaction and synchronization of the control plane data and the user plane data of each base station are achieved, thereby improving data transmission efficiency.

[0222] In the access network device with the added DMF entity, based on the further decoupling of the control plane and the user plane, the wireless side data processing method provided by the embodiment of the present application, in the cell switching scenario, first, during the data synchronization process between the source base station and the target base station, the data of the control plane and the data plane can be synchronized and independently carried out to improve the data transmission efficiency; second, when the source base station and the target base station are associated with the same DMF entity, the CU entity corresponding to the target base station does not need to interact with the core network to perform path switching, reducing unnecessary communication between the access network device and the core network device, simplifying the switching process, and ensuring the stability of the L3 message; third, when the source base station and the target base station are associated with different DMF entities, the user plane data path conversion can be executed synchronously with the UE random access process, and converted from a serial process to a parallel process. Fourth, by introducing the DMF entity, the UE can immediately resume the transmission of user data after accessing the target base station, shortening the service interruption delay caused by the switching; fifth, the DMF-CP entity caches and forwards the UE context, so that after determining the target cell / base station, the UE can immediately release the connection with the source base station without losing the context, and can also enhance the robustness of the control plane switching.

[0223] like Figure 13As shown, an embodiment of the present application also provides an access network device, including a transceiver 1310, a processor 1300, a memory 1320, and a program or instruction stored on the memory 1320 and runnable on the processor 1300; when the processor 1300 executes the program or instruction, it implements the above-mentioned wireless side processing method applied to the first DMF-CP entity, or implements the above-mentioned wireless side processing method applied to the second DMF-CP entity, or implements the above-mentioned wireless side processing method applied to the first DMF-UP entity, or implements the above-mentioned wireless side processing method applied to the first CU-CP entity, or implements the above-mentioned wireless side processing method applied to the first CU-UP entity.

[0224] The transceiver 1310 is configured to receive and send data under the control of the processor 1300 .

[0225] Among them, Figure 13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1300 and memory represented by memory 1320. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1310 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1300 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1300 when performing operations.

[0226] It should be noted here that the above-mentioned access network equipment provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned wireless side data processing method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0227] A readable storage medium in an embodiment of the present application stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the wireless side data processing method described above are implemented and the same technical effect can be achieved. To avoid repetition, they will not be described here.

[0228] The processor is the processor in the communication device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0229] It should be further explained that the electronic devices described in this specification include but are not limited to smartphones, tablet computers, etc., and many of the functional components described are referred to as modules in order to more particularly emphasize the independence of their implementation methods.

[0230] In embodiments of the present application, modules can be implemented in software so that they can be executed by various types of processors. For example, an identified executable code module can include one or more physical or logical blocks of computer instructions, for example, which can be constructed as objects, processes, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the specified purpose of the module.

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

[0232] When a module can be implemented using software, given the current state of hardware technology, those skilled in the art can build corresponding hardware circuits to implement the corresponding functions of the module, regardless of cost. The hardware circuits may include conventional very large scale integration (VLSI) circuits or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules may also be implemented using programmable hardware devices, such as field programmable gate arrays, programmable array logic, or programmable logic devices.

[0233] The above exemplary embodiments are described with reference to the accompanying drawings. Many different forms and embodiments are possible without departing from the spirit and teachings of this application. Therefore, this application should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this application will be complete and impartial and will convey the scope of this application to those skilled in the art. In the drawings, component sizes and relative sizes may be exaggerated for clarity. The terminology used herein is for purposes of describing specific exemplary embodiments only and is not intended to be limiting. As used herein, unless the context clearly indicates otherwise, the singular forms "a," "an," and "the" are intended to encompass such plural forms. It will be further understood that the terms "comprising" and / or "including," when used in this specification, indicate the presence of the stated features, integers, steps, operations, components, and / or elements, but do not preclude the presence or addition of one or more other features, integers, steps, operations, components, elements, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

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

Claims

1. A wireless side data processing method, characterized in that: Applied to the first DMF-CP entity, including: Sending a UE context subscription message to a first CU-CP entity within a first scope; wherein the first scope is related to the DMF-CP entity; receiving a UE context notification message sent by the first CU-CP entity, where the UE context notification message includes a real-time UE context of a UE accessing the first CU-CP entity; Updating a cached UE context according to the received real-time UE context; receiving a UE context forwarding request message sent by the first CU-CP entity, where the UE context forwarding request message includes a target CU ID; In response to the UE context forwarding request message, the UE context of the second target UE group is sent to the second CU-CP entity corresponding to the target CU ID, where the second target UE group includes at least one UE that is switched from accessing the first CU-CP entity to accessing the second CU-CP entity.

2. The method according to claim 1, characterized in that The method further comprises: receiving a termination message sent by the first CU-CP entity; In response to the termination message, a currently cached UE context related to the termination message is released.

3. The method according to claim 1, characterized in that The method further comprises: receiving a UE context request message sent by the first CU-CP entity; In response to the UE context request message, a UE context of a first target UE group is sent to the first CU-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

4. The method according to claim 1, wherein Sending the UE context of the second target UE group to the second CU-CP entity includes: In a case where the second CU-CP entity is located outside the first range, the UE context of the second target UE group is sent to the second CU-CP entity via a second DMF-CP entity, wherein the second DMF-CP is associated with the second CU-CP entity.

5. A wireless side data processing method, characterized in that: Applicable to the second DMF-CP entity, including: receiving a UE context of a second target UE group sent by the first DMF-CP entity; Send the UE context of the second target UE group to the second CU-CP entity; wherein the second DMF-CP is associated with the second CU-CP entity, the second target UE group includes at least one UE that is switched from accessing the first CU-CP entity to accessing the second CU-CP entity, and the first CU-CP entity is associated with the first DMF-CP entity.

6. The method according to claim 5, characterized in that The method further comprises: During the process of a UE in the second target UE group randomly accessing a cell corresponding to the second CU-CP entity, sending a path switching request to a core network device; Receive a path switching response sent by the core network device.

7. A wireless side data processing method, characterized in that: Applied to the first DMF-UP entity, including: Receive user plane data sent by the user plane function UPF entity; caching the received user plane data into a data queue according to the order of the received user plane data; Sending the user plane data to a first target CU-UP entity according to the data queue, wherein the first target CU-UP entity is within a first range, the first range is associated with the first DMF-UP, and a UE corresponding to the user plane data is a UE accessing the first target CU-UP entity; Inserting positioning identification data into the cached data queue according to preconfigured rules; receiving a user plane data forwarding request sent by the first target CU-UP entity, where the user plane data forwarding request includes a target CU ID, a hyperframe number HFN, and a sequence number SN corresponding to the HFN, or the user plane data forwarding request includes a target CU ID, a HFN, a SN corresponding to the HFN, and a DMF identifier; In response to the user plane data forwarding request, perform at least one of the following: Stop sending user plane data to the first target CU-UP entity; Buffering user plane data received from the UPF entity; According to the HFN, the SN and the positioning identification data, user plane data of the third target UE group is sent to the second target CU-UP entity corresponding to the target CU ID, wherein the third target UE group is at least one UE that switches from accessing the first target CU-UP entity to accessing the second target CU-UP entity.

8. The method according to claim 7, characterized in that Sending user plane data of the third target UE group to the second target CU-UP entity includes any of the following: When a second target CU-UP entity corresponding to the target CUID is located within the first range, sending user plane data of a third target UE group to the second target CU-UP entity; In a case where the second target CU-UP entity corresponding to the target CUID is outside the first range, the user plane data of the third target UE group is sent to the second target CU-UP entity through the second DMF-UP entity corresponding to the DMF identifier.

9. The method according to claim 7, characterized in that Sending user plane data of a third target UE group to the second target CU-UP entity according to the HFN, the SN, and the positioning identifier data, including: determining, according to the HFN, the SN, and the positioning identifier data, user plane data not processed by the first target CU-UP entity; Send the unprocessed user plane data to the second target CU-UP entity in sequence.

10. A wireless side data processing method, characterized in that: Applied to the first CU-CP entity, including: Receiving a UE context subscription message sent by the first DMF-CP entity; In response to the UE context subscription message, send a UE context notification message to the first DMF-CP entity, where the UE context notification message includes a real-time UE context of the UE accessing the first CU-CP entity; A UE context forwarding request message is sent to the first DMF-CP entity, where the UE context forwarding request message includes a target CUID, and the UE context forwarding request message is used to instruct the first DMF-CP entity to forward the corresponding UE context to a second target CU-CP entity corresponding to the target CU ID.

11. The method according to claim 10, characterized in that Sending a UE context notification message to the first DMF-CP entity includes: When the UE context of the terminal accessing the first CU-CP entity changes, the UE context notification message is sent to the first DMF-CP entity.

12. The method according to claim 10, characterized in that The method further comprises: Send a termination message to the first DMF-CP entity.

13. The method according to claim 10, characterized in that The method further comprises: Sending a UE context request message to the first DMF-CP entity; Receive a UE context of a first target UE group sent by the first DMF-CP entity, where the first target UE group includes at least one UE accessing the first CU-CP entity.

14. A wireless side data processing method, characterized in that: Applied to the first CU-UP entity, including: receiving user plane data sent by a first DMF-UP entity, wherein the UE corresponding to the user plane data is a UE accessing the first CU-UP entity; A user plane data forwarding request is sent to the first DMF-UP entity, where the user plane data forwarding request includes a target CUID, a hyperframe number HFN, and a sequence number SN corresponding to the HFN, or the user plane data forwarding request includes a target CUID, a HFN, a SN corresponding to the HFN, and a DMF identifier; the user plane data forwarding request is used to instruct the first DMF-UP entity to forward user plane data to the second CU-UP entity corresponding to the target CU ID.

15. An access network device comprising a transceiver, a processor, a memory, and a program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, it implements the wireless side data processing method according to any one of claims 1 to 4, or implements the wireless side data processing method according to any one of claims 5 to 6, or implements the wireless side data processing method according to any one of claims 7 to 9, or implements the wireless side data processing method according to any one of claims 10 to 13, or implements the wireless side data processing method according to claim 14.

16. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by the processor, it implements the wireless side data processing method according to any one of claims 1 to 4, or implements the wireless side data processing method according to any one of claims 5 to 6, or implements the wireless side data processing method according to any one of claims 7 to 9, or implements the wireless side data processing method according to any one of claims 10 to 13, or implements the wireless side data processing method according to claim 14.

Images