Access network information management method and device and storage medium

Abstract

The invention provides an access network information management method and device and a storage medium, and relates to the technical field of communication, any access network element creates or updates network context information and transmits the network context information to a network function entity, the network function entity identifies the network context information according to a terminal identifier, and the terminal identifier identifies the network context information according to the terminal identifier. And storing and / or managing the network context based on the terminal identification. The network context information is stored and managed in a unified mode through the network function entity, interface messages and basic processes between network elements of an access network are simplified, time delay and complexity are reduced, reliability is improved, separation of data of the network context information and messages between the network elements of the access network can be achieved, and user experience is improved. Subsequent change and expansion of network elements and interfaces are facilitated, and scenes such as artificial intelligence and network cloudization are better supported.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an access network information management method, device and storage medium. Background Art

[0002] In network systems such as 5G or 6G, access network elements usually need to maintain some status information of the terminal, including the network context information of the terminal.

[0003] In the prior art, network context information may interact between different network elements, which is usually transmitted through the interfaces between network elements in the form of messages. As the network architecture evolves, more network elements and interfaces appear, making the transmission and management of network context information more complicated. The content of network context information that needs to be transmitted may also increase. In addition, under the trend of dense and ultra-dense networking, terminals move and switch frequently, and network context information interacts frequently, which increases latency and complexity. Summary of the invention

[0004] The present application provides an access network information management method, device and storage medium to uniformly store and manage network context information through a network function entity.

[0005] In a first aspect, the present application provides an access network information management method, which is applied to a network function entity, and the method includes:

[0006] Obtaining network context information created or updated by any access network element;

[0007] Identifying the network context information according to the terminal identifier, and storing and / or managing the network context information based on the terminal identifier;

[0008] The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

[0009] Optionally, the storing and / or managing the network context information based on the terminal identifier includes:

[0010] Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or

[0011] An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

[0012] Optionally, the obtaining of network context information created or updated by any access network element includes:

[0013] Receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; acquiring the network context information according to the context information creation request; or

[0014] Receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; acquiring the updated network context information according to the context information update request; or

[0015] If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, a context information synchronization request sent by other network function entities deployed in other access network elements is received, and the context information synchronization request includes the network context information; and the network context information is obtained according to the context information synchronization request.

[0016] Optionally, the performing the data service on the network context information based on the terminal identifier includes at least one of the following:

[0017] storing, according to the context information creation request, the network context information included in the context information creation request; or

[0018] updating the currently stored network context information according to the context information update request and according to the updated network context information included in the context information update request; or

[0019] According to the context information synchronization request, synchronizing currently stored network context information with the network context information included in the context information synchronization request; or

[0020] Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or

[0021] A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

[0022] Optionally, the executing the event service on the network context information based on the terminal identifier includes at least one of the following:

[0023] If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or

[0024] Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or

[0025] If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

[0026] Optionally, the network function entity is connected to multiple access network centralized units CU; accordingly, obtaining network context information created or updated by any access network element includes:

[0027] After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or

[0028] After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or

[0029] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

[0030] Optionally, the performing the data service on the network context information based on the terminal identifier includes at least one of the following:

[0031] According to the context information creation request, storing the network context information included in the context information creation request; or

[0032] According to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request; or

[0033] After the terminal moves and a switch occurs from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or

[0034] When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or

[0035] When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

[0036] Optionally, the network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, the executing the event service about the network context information based on the terminal identifier includes:

[0037] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or

[0038] After the terminal moves, the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0039] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

[0040] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the acquiring of network context information created or updated by any access network network element includes:

[0041] The first network function entity receives a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or

[0042] The first network function entity receives a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, where the context information update request includes the updated network context information; or

[0043] The first network function entity receives a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, wherein the context information synchronization request includes the updated network context information.

[0044] Optionally, the performing the data service on the network context information based on the terminal identifier includes at least one of the following:

[0045] The first network function entity stores the network context information included in the context information creation request according to the terminal identifier, and sends a context information synchronization request to the second network function entity; or

[0046] The first network function entity updates currently stored network context information with updated network context information included in the context information update request according to the terminal identifier, and sends a context information synchronization request to the second network function entity; or

[0047] The first network function entity synchronizes the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

[0048] Optionally, the executing the event service regarding the network context information based on the terminal identifier further includes:

[0049] The second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, and sends a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or

[0050] The first network function entity receives a notification event triggered by the second network function entity after updating context information, and sends a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

[0051] Optionally, the performing the data service on the network context information based on the terminal identifier further includes at least one of the following:

[0052] The second network function entity receives the context information query request sent by the first DU according to the notification, and sends the network context information to the first DU; or

[0053] The second network function entity receives a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; stores the updated network context information according to the terminal identifier, and sends a context information synchronization request to the first network function entity.

[0054] Optionally, the network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

[0055] In a second aspect, the present application provides an access network information management method, which is applied to an access network element, and the method includes:

[0056] Create or update network context information;

[0057] Sending the network context information to the network function entity;

[0058] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0059] Optionally, sending the network context information to the network function entity includes:

[0060] After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or

[0061] After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or

[0062] If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

[0063] Optionally, the method further includes:

[0064] Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or

[0065] Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

[0066] Optionally, requesting a data service about the network context information from the network function entity based on the terminal identifier includes at least one of the following:

[0067] Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or

[0068] After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

[0069] Optionally, the controlling the network function entity to perform an event service regarding the network context information includes:

[0070] If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to subscribe to each other, so that the first access network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or

[0071] If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the first access network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

[0072] Optionally, the access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0073] After the terminal accesses the first CU and registers, the first CU establishes the network context information according to a request of the core network, and sends a context information creation request to the network function entity, where the context information creation request includes the network context information; or

[0074] After the terminal establishes a protocol data unit (PDU) session, the first CU updates the network context information and sends a context information update request to the network function entity, where the context information update request includes the updated network context information; or

[0075] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the second CU updates the network context information while keeping the terminal in an inactive state, and sends a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

[0076] Optionally, the requesting, from the network function entity, a data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0077] After the terminal moves and a switch occurs from the first CU to the second CU, the second CU sends a context information query request to the network function entity, where the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or

[0078] When the terminal is converted from an inactive state to a connected state, the first CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the first CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or

[0079] When the terminal is converted from an inactive state to a connected state, the second CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier.

[0080] Optionally, the access network network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service about the network context information includes:

[0081] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the first CU or the first DU determines that the first CU and the first DU cooperate to serve the terminal, and controls mutual subscription between a first network function entity in the first CU and a second network function entity in the first DU; or

[0082] After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the first CU, the first DU or the second DU determines that the first CU, the first DU and the second DU cooperate to serve the terminal, and controls the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0083] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the first CU determines that the first CU and the second DU cooperate to serve the terminal, controls the mutual subscription between the first network function entity and the third network function entity in the second DU, and controls the cancellation of the mutual subscription between the first network function entity and the second network function entity.

[0084] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0085] After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the first CU sends a context information creation request to the first network function entity, where the context information creation request includes the network context information; or

[0086] After the terminal establishes a PDU session and updates the network context information, the first CU sends a context information update request to the first network function entity, where the context information update request includes the updated network context information; or

[0087] The first CU controls the first network function entity to send a context information synchronization request to the second network function entity.

[0088] Optionally, the method further includes:

[0089] After the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the first DU receives a notification sent by the second network function entity, and sends a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or

[0090] After the first network function entity receives a notification event triggered by the second network function entity after updating context information, the first CU receives the notification sent by the first network function entity, and sends a context information query request to the first network function entity according to the notification to obtain the network context information for subsequent processing.

[0091] In a third aspect, the present application provides a network function entity, wherein the network function entity is connected to multiple access network elements and / or is distributedly deployed in multiple access network elements, and the network function entity includes a memory, a transceiver, and a processor:

[0092] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0093] Obtaining network context information created or updated by any access network element;

[0094] Identifying the network context information according to the terminal identifier, and storing and / or managing the network context information based on the terminal identifier;

[0095] The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

[0096] Optionally, when the processor stores and / or manages the network context information based on the terminal identifier, is configured to:

[0097] Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or

[0098] An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

[0099] Optionally, when acquiring network context information created or updated by any access network element, the processor is configured to:

[0100] Receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; acquiring the network context information according to the context information creation request; or

[0101] Receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; acquiring the updated network context information according to the context information update request; or

[0102] If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, a context information synchronization request sent by other network function entities deployed in other access network elements is received, and the context information synchronization request includes the network context information; and the network context information is obtained according to the context information synchronization request.

[0103] Optionally, the processor executes the data service regarding the network context information based on the terminal identifier, and is configured to perform at least one of the following:

[0104] storing, according to the context information creation request, the network context information included in the context information creation request; or

[0105] updating the currently stored network context information according to the context information update request and according to the updated network context information included in the context information update request; or

[0106] According to the context information synchronization request, synchronizing currently stored network context information with the network context information included in the context information synchronization request; or

[0107] Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or

[0108] A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

[0109] Optionally, when executing the event service regarding the network context information based on the terminal identifier, the processor is configured to perform at least one of the following:

[0110] If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or

[0111] Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or

[0112] If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

[0113] Optionally, the network function entity is connected to multiple access network centralized units CU; accordingly, when the processor obtains network context information created or updated by any access network network element, it is used to:

[0114] After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or

[0115] After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or

[0116] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

[0117] Optionally, when executing the data service regarding the network context information based on the terminal identifier, the processor is configured to perform at least one of the following:

[0118] According to the context information creation request, storing the network context information included in the context information creation request; or

[0119] According to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request; or

[0120] After the terminal moves and a switch occurs from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or

[0121] When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or

[0122] When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

[0123] Optionally, the network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, when the processor executes the event service about the network context information based on the terminal identifier, it is used to:

[0124] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or

[0125] After the terminal moves, the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0126] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

[0127] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the acquiring of network context information created or updated by any access network network element includes:

[0128] The processor of the first network function entity is used to receive a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to the request of the core network, wherein the context information creation request includes the network context information; or

[0129] The processor of the first network function entity is used to receive a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, wherein the context information update request includes the updated network context information; or

[0130] The processor of the first network function entity is used to receive a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, and the context information synchronization request includes the updated network context information.

[0131] Optionally, the performing of the data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0132] The processor of the first network function entity is used to store the network context information included in the context information creation request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0133] The processor of the first network function entity is used to update the currently stored network context information with the updated network context information included in the context information update request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0134] The processor of the first network function entity is used to synchronize the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

[0135] Optionally, the executing the event service regarding the network context information based on the terminal identifier further includes:

[0136] The processor of the second network function entity is used to receive a notification event triggered by the first network function entity after creating or updating the network context information, and send a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or

[0137] The processor of the first network function entity is used to receive a notification event triggered by the second network function entity after updating the context information, and send a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

[0138] Optionally, the performing the data service on the network context information based on the terminal identifier further includes at least one of the following:

[0139] The processor of the second network function entity is used to receive a context information query request sent by the first DU according to the notification, and send the network context information to the first DU; or

[0140] The processor of the second network function entity is used to receive a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; store the updated network context information according to the terminal identifier, and send a context information synchronization request to the first network function entity.

[0141] Optionally, the network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

[0142] In a fourth aspect, the present application provides an access network element, wherein the access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element, and the access network element includes a memory, a transceiver, and a processor:

[0143] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0144] Create or update network context information;

[0145] Sending the network context information to the network function entity;

[0146] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0147] Optionally, when sending the network context information to the network function entity, the processor is configured to:

[0148] After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or

[0149] After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or

[0150] If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

[0151] Optionally, the processor is further configured to:

[0152] Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or

[0153] Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

[0154] Optionally, when the processor requests a data service about the network context information from the network function entity based on the terminal identifier, the processor is configured to perform at least one of the following:

[0155] Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or

[0156] After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

[0157] Optionally, when controlling the network function entity to perform an event service regarding the network context information, the processor is configured to:

[0158] If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to subscribe to each other, so that the first access network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or

[0159] If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the processor of the first access network element is used to control the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

[0160] Optionally, the access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0161] After the terminal accesses the first CU and registers, the processor of the first CU is used to establish the network context information according to the request of the core network, and send a context information creation request to the network function entity, where the context information creation request includes the network context information; or

[0162] After the terminal establishes a protocol data unit PDU session, the processor of the first CU is used to update the network context information and send a context information update request to the network function entity, where the context information update request includes the updated network context information; or

[0163] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the processor of the second CU is used to update the network context information while keeping the terminal in an inactive state, and send a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

[0164] Optionally, the requesting, from the network function entity, a data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0165] After the terminal moves and a switch occurs from the first CU to the second CU, the processor of the second CU is used to send a context information query request to the network function entity, where the context information query request includes a terminal identifier; the processor of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0166] When the terminal is converted from an inactive state to a connected state, the processor of the first CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor of the first CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0167] When the terminal is converted from an inactive state to a connected state, the processor of the second CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier.

[0168] Optionally, the access network network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service about the network context information includes:

[0169] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the processor of the first CU or the processor of the first DU is used to determine that the first CU and the first DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity in the first CU and the second network function entity in the first DU; or

[0170] After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the processor of the first CU, the processor of the first DU or the processor of the second DU is used to determine that the first CU, the first DU and the second DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0171] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the processor of the first CU is used to determine that the first CU and the second DU cooperate to serve the terminal, control the mutual subscription between the first network function entity and the third network function entity in the second DU, and control the cancellation of the mutual subscription between the first network function entity and the second network function entity.

[0172] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0173] After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the processor of the first CU is used to send a context information creation request to the first network function entity, where the context information creation request includes the network context information; or

[0174] After the terminal establishes a PDU session and updates the network context information, the processor of the first CU is used to send a context information update request to the first network function entity, where the context information update request includes the updated network context information; or

[0175] The processor of the first CU is used to control the first network function entity to send a context information synchronization request to the second network function entity.

[0176] Optionally, after the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the processor of the first DU is used to receive a notification sent by the second network function entity, and send a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or

[0177] When the first network function entity receives a notification event triggered by the second network function entity after updating context information, the processor of the first CU is used to receive the notification sent by the first network function entity, and send a context information query request to the first network function entity according to the notification, so as to obtain the network context information for subsequent processing.

[0178] In a fifth aspect, the present application provides an access network information management device, which is applied to a network function entity, and the device includes:

[0179] A receiving unit, configured to obtain network context information created or updated by any access network element;

[0180] a processing unit, configured to identify the network context information according to the terminal identifier, and store and / or manage the network context information based on the terminal identifier;

[0181] The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

[0182] In a sixth aspect, the present application provides an access network information management device, applied to an access network element, the device comprising:

[0183] A processing unit, configured to create or update network context information;

[0184] A sending unit, configured to send the network context information to the network function entity;

[0185] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0186] In a seventh aspect, the present application provides an access network information management system, including the network function entity as described in the third aspect and the access network network element as described in the fourth aspect;

[0187] The network function entity is connected to a plurality of access network elements, and / or the network function entity is distributedly deployed in a plurality of access network elements.

[0188] In an eighth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method described in the first aspect or the second aspect.

[0189] The access network information management method, device and storage medium provided in the present application create or update network context information through any access network element and transmit it to the network function entity, which identifies the network context information according to the terminal identifier and stores and / or manages the network context based on the terminal identifier. The unified storage and management of network context information by the network function entity simplifies the interface messages and basic processes between access network elements, reduces latency and complexity, improves reliability, and can achieve the separation of network context information data and messages between access network elements, facilitates subsequent changes and expansions of network elements and interfaces, and better supports scenarios such as artificial intelligence and network cloudification.

[0190] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0191] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0192] Figure 1 A schematic diagram of a scenario of an access network information management method provided in an embodiment of the present application;

[0193] Figure 2 A flowchart of an access network information management method provided in an embodiment of the present application;

[0194] Figure 3a A schematic diagram of a centralized deployment of network function entities provided in an embodiment of the present application;

[0195] Figure 3b A schematic diagram of distributed deployment of network function entities provided in an embodiment of the present application;

[0196] Figure 3c A schematic diagram of a centralized and distributed combined deployment of a network function entity provided in an embodiment of the present application;

[0197] Figure 4a A schematic diagram of a network function entity providing data services according to an embodiment of the present application;

[0198] Figure 4b A schematic diagram of a network function entity providing data services and event services according to an embodiment of the present application;

[0199] Figure 5 A flowchart of an access network information management method provided by another embodiment of the present application;

[0200] Figure 6 A schematic diagram of centralized deployment of network function entities provided by another embodiment of the present application;

[0201] Figure 7 A signaling diagram of an access network information management method provided in an embodiment of the present application;

[0202] Figure 8 A schematic diagram of distributed deployment of network function entities provided in another embodiment of the present application;

[0203] Fig. 9 A schematic diagram of a centralized and distributed combined deployment of a network function entity provided in another embodiment of the present application;

[0204] Fig.10 A structural diagram of a network function entity provided in an embodiment of the present application;

[0205] Fig.11 A structural diagram of an access network element provided in an embodiment of the present application;

[0206] Fig.12 A structural diagram of an access network information management device provided in an embodiment of the present application;

[0207] Fig.13 A structural diagram of an access network information management device provided in another embodiment of the present application. DETAILED DESCRIPTION

[0208] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0209] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0210] In network systems such as 5G or 6G, access network elements usually need to maintain some status information of the terminal, including network context information of the terminal, such as the terminal-related NG-RAN node terminal context (UE Context) and bearer context (Bearer Context), where the terminal context contains the necessary information required to maintain NG-RAN services for RRC connected (RRC_CONNECTED) and RRC inactive (RRC_INACTIVE) terminals, which should at least include terminal status information, security information, terminal capability information and information about logical connections related to the terminal; the bearer context maintains the necessary information required for user plane services for the terminal, which may include information about data radio bearers, PDU (Protocol Data Unit) sessions and QoS (Quality of Service) flows associated with the terminal; in addition, when the terminal enters the inactive state, it is also necessary to save some state-related parameters (UE Inactive AS Context, such as the current KgNB and KRRCint keys, the ROHC state, the UDC state, the stored QoS flow to DRB mapping rules, etc.) to facilitate rapid recovery of the connection state.

[0211] In the prior art, network context information may interact between different network elements. For example, the evolution of 5G network architecture has brought more and more network elements and interfaces. The basic NG-RAN logical nodes (network elements) may include gNB, gNB-CU (gNB-CU-CP and gNB-CU-UP) and gNB-DU. The related interfaces include Xn, F1, E1 and other interfaces. The above-mentioned network context information containing a large amount of content needs to interact frequently between network elements through messages, and the content included in these network contexts has become more and more with the introduction of new features.

[0212] Facing B5G and 6G, evolution trends such as cloud networks and user-centric networks have gradually emerged. Network elements can be deployed in a variety of ways, such as cloud deployment, centralized deployment, and distributed deployment. Cloud network elements can also improve transmission efficiency and resource utilization by co-deployment with data centers. However, although the current network has undergone a certain degree of architectural separation design, network data such as network context information is still closely bound to messages and network elements, which brings difficulties to the application of new technologies and new architectures.

[0213] Therefore, with the evolution of network architecture, more network elements and interfaces appear, making the transmission and management of network context information more complicated; with the continuous introduction of new features, the content of network context information that needs to be transmitted may also increase; under the trend of dense and ultra-dense networking, terminals move and switch frequently, and network context information interacts frequently, which increases latency and complexity; and it is impossible to fully utilize the advantages of network element cloud deployment (such as CU).

[0214] In order to solve the above technical problems, the present application provides an access network information management method, which uniformly stores and manages network context information through network function entities, simplifies interface messages and basic processes between access network network elements, reduces latency and complexity, and improves reliability. It can realize the separation of network context information data and messages between access network network elements, facilitates subsequent changes and expansions of network elements and interfaces, and better supports scenarios such as artificial intelligence and network cloudification.

[0215] The access network information management method provided in this application can be applied to Figure 1 The application scenario shown includes an access network element and a network function entity, wherein the network function entity is connected to multiple access network elements and / or distributedly deployed in multiple access network elements, and network context information is created or updated by any access network element and transmitted to the network function entity, which identifies the network context information according to the terminal identifier and stores and / or manages the network context based on the terminal identifier.

[0216] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G system or 6G system. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0217] The terminal involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0218] The network device (access network element) involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base TransceiverStation, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0219] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0220] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0221] Figure 2 Flow chart of an access network information management method provided in this embodiment. Figure 2 As shown, this embodiment provides an access network information management method, and the execution subject is a network function entity.

[0222] The network function entity is used to persist and synchronize the context information in the network, and provide management services such as creation, update, query and deletion of network context information to the access network element. The network function entity can be named as the state maintenance and management service network function entity (State Network Function, SNF), and the network function entities in the following embodiments can all be this type of network function entity. The network context information includes but is not limited to the state information required for any access network element to maintain the terminal connection state and provide services to the terminal. The state information includes but is not limited to one or more of the following: state information reported by the terminal, state information configured, generated, or saved by any access network element, for example, it may include but is not limited to the state information of the terminal, the security information of the terminal, the capability information of the terminal, the information of the logical connection related to the terminal, the radio bearer information, the PDU session information, the quality of service QoS flow information, etc.

[0223] Among them, the network function entity can be deployed in a centralized manner, such as Figure 3a As shown, the network function entity is connected to multiple access network elements, for example, connected to the NG-RAN network element through a unified message bus; or the network function entity can also be distributedly deployed, and the network function entity is distributedly deployed in multiple access network elements, such as Figure 3b As shown, that is, each of the multiple access network elements is deployed with a network function entity, for example, the network function entity is deployed in multiple NG-RAN network elements in the form of a function module, and the network function entity provides data services and / or event services for other function modules in the network element by providing an API (Application Programming Interface), a message bus, or other implementation methods such as a function call configured by the network element. The network function entities are interconnected, for example, through a message bus connection, to achieve event services and data synchronization between network function entities; or the network function entity can be deployed in a combination of centralized and distributed modes, wherein the centralized network function entity is connected to some access network elements, and the distributed network function entity is deployed in other access network elements, such as Figure 3c As shown, each network function entity is connected to each other. The access network elements include but are not limited to the centralized unit CU, the distributed unit DU, etc.

[0224] The specific steps of the access network information management method are as follows:

[0225] S201. Obtain network context information created or updated by any access network element.

[0226] In this embodiment, after any access network element creates network context information for the UE, the network context information can be transmitted to the network function entity; or any access network element may update the network context in the process of providing services to the UE. After the network context is updated, the updated network context information can be transmitted to the network function entity. Optionally, the updated full network context information can be transmitted to the network function entity, or only part of the updated network context information can be transmitted to the network function entity. The updated part of the network context information is the updated content, so that the network function entity only performs incremental synchronization on the updated network context information.

[0227] Optionally, after any access network element creates or updates network context information, the created or updated network context information can be transmitted to the network function entity in real time, or can be transmitted to the network function entity after a predetermined time interval or at a preset period, or can be transmitted to the network function entity after being triggered by a specified message or command.

[0228] For a centralized network function entity, any access network element may transmit the created or updated network context information to a centralized network function entity connected to the access network element through a message bus or other means; for a scenario in which network function entities are deployed in a distributed manner, any access network element may transmit the created or updated network context information to a network function entity deployed in the access network element through an API interface, a message bus, or a function call or other means, wherein the network context information may be created or updated by a functional module of any access network element, and then the functional module may transmit the created or updated network context information to the network function entity deployed in the access network element.

[0229] S202: Identify the network context information according to the terminal identifier, and store and / or manage the network context information based on the terminal identifier.

[0230] In this embodiment, the unique terminal identifier of the terminal related to the network context information is used to identify the associated network context information. The terminal identifier includes but is not limited to 5G-GUTI, AMF UE NGAP ID, RAN UE NGAP ID or other IDs assigned to the terminal by the network, etc., and the network context can be stored and / or managed based on the terminal identifier.

[0231] Optionally, the storing and / or managing the network context information based on the terminal identifier may provide a data service and / or an event service regarding the network context information, which may specifically include:

[0232] Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or

[0233] An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

[0234] In this embodiment, the data service includes but is not limited to the storage, query, update, deletion and data synchronization of the network context information based on the terminal identification, wherein the data synchronization is the synchronization of the network context information between the distributed network function entities; Figure 4a In the network function entity centralized deployment scenario, the access network element sends a data service request to the network function entity, and the network function entity returns a data service response after executing the corresponding data service; Figure 4b In the distributed deployment scenario of network function entities, the functional module in the access network element sends a data service request to the network function entity in the access network element. The network function entity performs the corresponding data service and returns a data service response. The network function entities in different access network elements can synchronize data.

[0235] The event service takes into account that since different access network elements no longer use messages to transmit network context information through interfaces, frequent transmission of network context information between access network elements is avoided. Therefore, when a certain access network element creates or updates network context information, other related network elements may not be aware of it and thus do not perform subsequent processing. Therefore, the event service is used to notify other related access network elements that the context information is created or updated when a certain access network element creates or updates network context information, so as to trigger other related access network elements to obtain the created or updated network context information from the network function entity and perform subsequent processing, especially for scenarios where network function entities are distributedly deployed, such as Figure 4bAs shown, different network function entities can be subscribed to and notified of each other, the subscription service is used to determine which network function entity is triggered to notify the access network element when the network context information is created or updated, and the notification service is used to trigger the notification of the subscribed network function entity after the network context information is created or updated on any network function entity, so that the subscribed network function entity notifies the access network element. The subscription and unsubscription between network function entities are subscription and unsubscription for the network context information corresponding to the terminal identifier.

[0236] Optionally, a centralized network function entity may not provide event services. When an access network element creates or updates network context information, the created or updated network context information is transmitted to the network function entity, and the access network element sends a notification message of the creation or update of the network context information to other related access network elements, so that other related access network elements obtain the created or updated network context information from the network function entity and perform subsequent processing.

[0237] The access network information management method provided in this embodiment creates or updates network context information through any access network element and transmits it to the network function entity, which identifies the network context information according to the terminal identifier and stores and / or manages the network context based on the terminal identifier. The network function entity uniformly stores and manages the network context information, simplifies the interface messages and basic processes between access network elements, reduces latency and complexity, improves reliability, and can separate the data of the network context information from the messages between the access network elements, facilitates subsequent changes and expansions of network elements and interfaces, and better supports scenarios such as artificial intelligence and network cloudification.

[0238] On the basis of any of the above embodiments, the acquisition of network context information created or updated by any access network element in S201 may specifically include but is not limited to the following methods:

[0239] Method 1: The network function entity receives a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; and obtains the network context information according to the context information creation request.

[0240] In this manner, after any access network element creates network context information, it may send a context information creation request to a network function entity, carry the created network context information in the context information creation request, and transmit it to the network function entity, so that the network function entity can obtain the network context information from the context information creation request. Wherein, any access network element network context information refers to the process of the access network element forming / obtaining context information, including but not limited to querying the core network, and / or querying the UE, and / or the access network element itself configuring the network context information for the terminal.

[0241] Method 2: The network function entity receives a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; and obtains the updated network context information according to the context information update request.

[0242] In this manner, after any access network element updates the network context information, it may send a context information update request to the network function entity, carry the updated network context information in the context information update request, and transmit it to the network function entity, so that the network function entity can obtain the updated network context information from the context information update request. The updated network context information may be the updated full network context information, or may only include the updated content.

[0243] The above-mentioned method 1 and method 2 are applicable to the scenario where the network function entity is centrally deployed; they are also applicable to the scenario where the network function entity is distributedly deployed, and any access network element can send a context information creation request or a context information update request to the network function entity deployed in the access network element.

[0244] Method three: If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, receive a context information synchronization request sent by other network function entities deployed in other access network elements, and the context information synchronization request includes the network context information; obtain the network context information according to the context information synchronization request.

[0245] In this method, in the scenario where network function entities are deployed in a distributed manner, if network context information is created or updated in a network function entity in any access network element, a context information synchronization request may be sent to network function entities in other access network elements. The context information synchronization request includes the created network context information or the updated network context information. The network function entities in other access network elements may obtain the network context information included in the context information synchronization request for subsequent synchronization, so that the network function entities in each access network element maintain consistency.

[0246] Based on any of the foregoing embodiments, the network function entity performs a data service on the network context information based on the terminal identifier, including at least one of the following:

[0247] According to the context information creation request, the network context information included in the context information creation request is stored; wherein the context information creation request is actually a request for storing the network context information for the first time, and when storing the network context information, the network context information is stored in association with the corresponding terminal identifier, so as to facilitate other query, update, deletion and other services based on the terminal identifier;

[0248] Alternatively, according to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request; wherein when updating, the network function entity may first search for the current network context information according to the terminal identifier, and then update based on the updated network context information;

[0249] Alternatively, according to the context information synchronization request, the currently stored network context information is synchronized with the network context information included in the context information synchronization request; wherein in a scenario where network function entities are distributedly deployed, if it is determined based on the terminal terminal identifier that the network context information corresponding to the terminal identifier does not currently exist in the network function entity, the network context information included in the context information synchronization request is stored; if the network context information corresponding to the terminal identifier currently exists in the network function entity, it is updated according to the network context information included in the context information synchronization request, thereby ensuring that the network context information corresponding to the same terminal identifier between the network function entities remains consistent;

[0250] Alternatively, receiving a context information query request sent by any access network network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network network element, thereby enabling any access network network element to obtain the network context information from the network function entity without the need to transmit the network context information between access network network elements;

[0251] Alternatively, a context information deletion request is received from any access network element after detecting that the terminal has left the network or is shut down and offline, and the network context information corresponding to the terminal is deleted according to the context information deletion request to avoid invalid network context information occupying the storage space of the network function entity.

[0252] Based on any of the foregoing embodiments, the network function entity performs an event service on the network context information based on the terminal identifier, including at least one of the following:

[0253] If it is determined that the access network element where the user is located collaborates with other access network elements to serve the terminal, mutual subscription is performed with other network function entities in other access network elements; wherein, when multiple access network elements collaborate to serve the terminal, when any access network element creates or updates the network context information of the terminal, the created or updated network context information will be synchronized to the network function entities in all access network elements (including the network function entities in the multiple access network elements that collaborate to serve the terminal, and the network function entities in other access network elements); if the network function entities in the multiple access network elements that collaborate to serve the terminal subscribe to each other, when the network context information in any of the mutually subscribed network function entities is created or updated, a notification event is triggered to the other mutually subscribed network function entities, so that the subscribed network function entity notifies the access network element where the user is located, so that the access network element where the user is located perceives that the network context information is created or updated, and then performs subsequent processing; that is, the subscription service is used to determine which network function entity is triggered to notify when the network context information is created or updated;

[0254] Alternatively, receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; wherein the notification event is used to notify the subscribed network function entity, so that the subscribed network function entity notifies the access network element where the entity is located that the network context information is created or updated;

[0255] Alternatively, if it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, then the mutual subscription with other network function entities in other access network elements is cancelled, that is, there is no need to trigger the notification event.

[0256] On the basis of any of the above embodiments, in a specific application scenario, the access network element may be a CU, and in a scenario where the network function entity is centrally deployed, the network function entity is connected to multiple access network centralized units CU; accordingly, S201 obtains network context information created or updated by any access network element, which may specifically include but is not limited to the following situations:

[0257] After the terminal accesses the first CU and registers, a context information creation request sent by the first CU after the network context information is established according to the request of the core network is received, and the context information creation request includes the network context information; wherein the terminal accesses the first CU and registers, and the first CU establishes initial network context information after receiving the network context information establishment request of the core network, wherein the network context information may include querying the core network, querying the terminal (for example, querying UE capability information in the figure), and the network context information configured by the first CU itself for the UE, and then the first CU may send a context information creation request to the network function entity, and the context information creation request includes the network context information, so as to transmit the network context information to the network function entity;

[0258] Alternatively, after the terminal establishes a protocol data unit PDU session, a context information update request sent by the first CU after updating the network context information is received, wherein the context information update request includes the updated network context information; wherein after the terminal establishes the PDU session, the first CU may use the PDU session and other information as the updated network context information, and send a context information update request to the network function entity, so as to update the PDU session and other information to the network function entity;

[0259] Alternatively, when the terminal is in an inactive state and the movement occurs when switching from the first CU to the second CU, a context information update request is received, which is sent by the second CU after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information; wherein when the terminal is in an inactive state and the movement switches from the first CU to the second CU, the terminal does not need to restore the connection state at this time and can continue to remain in the active state, the second CU can directly update the network context information and send a context information update request to the network function entity, and the context information update request includes the updated network context information; the network function entity updates the network context information according to the updated network context information included in the context information update request.

[0260] Further, the network function entity performs a data service on the network context information based on the terminal identifier, including at least one of the following:

[0261] According to the context information creation request, storing the network context information included in the context information creation request;

[0262] Alternatively, according to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request;

[0263] Alternatively, after the terminal moves and switches from the first CU to the second CU, a context information query request sent by the second CU is received, where the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU; wherein when the CU switching occurs, the switched second CU does not need to obtain the network context information from the first CU or the terminal, but can directly query the network context information corresponding to the terminal from the network function entity;

[0264] Alternatively, when the terminal is converted from an inactive state to a connected state, a context information query request sent by the first CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the first CU; wherein if the terminal is converted from an inactive state to a connected state first CU under the first CU, the first CU may also directly query the network context information corresponding to the terminal from the network function entity;

[0265] Alternatively, when the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU; wherein if the terminal is in an inactive state and moves from the first CU to the second CU, the second CU updates the network context information and sends a context information update request to the network function entity, the context information update request includes the updated network context information, after the network function entity updates the network context information according to the updated network context information included in the context information update request, if the terminal is converted from an inactive state to a connected state, the second CU may also directly query the network context information corresponding to the terminal from the network function entity.

[0266] On the basis of any of the foregoing embodiments, in a specific application scenario, the access network element may be a CU and a DU. In a scenario where the network function entity is distributedly deployed, the network function entity is distributedly deployed in at least one CU and multiple DUs in the access network; accordingly, the network function entity performs an event service on the network context information based on the terminal identifier, which may specifically include at least one of the following:

[0267] After the terminal accesses the first CU through the first transmission and receiving point TRP (Transmission and Receiving Point) under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and the first network function entity in the first CU and the second network function entity in the first DU are mutually subscribed; wherein the terminal enters the first transmission and receiving point TRP under the first DU, then the first CU and the first DU cooperate to serve the terminal, so the first network function entity in the first CU and the second network function entity in the first DU can be mutually subscribed, and after the mutual subscription, when the first network function entity or the second network function entity creates or updates the network context information, a notification event can be triggered;

[0268] Alternatively, after the terminal moves, the first sending and receiving point TRP under the first DU is switched to the second sending and receiving point TRP shared by the first DU and the second DU, it is determined that the first CU, the first DU and the second DU cooperate to serve the terminal, and the first network function entity, the second network function entity, and the third network function entity in the second DU are mutually subscribed; wherein the terminal enters the second sending and receiving point TRP, at which time the first CU, the first DU and the second DU cooperate to serve the terminal, and the network function entities in the first CU, the first DU and the second DU are mutually subscribed, and a notification event can be triggered when any network function entity in the first CU, the first DU and the second DU creates or updates network context information;

[0269] Alternatively, after the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the first network function entity and the second network function entity are mutually subscribed; if it is determined that the first DU no longer cooperates with the first CU to serve the terminal, the mutual subscription between the first network function entity in the first DU and the second network function entity in the first CU can be canceled, that is, the notification event is no longer triggered when creating or updating the network context information.

[0270] Further, in the case where the first network function entity in the first CU and the second network function entity in the first DU subscribe to each other, S201 obtains network context information created or updated by any access network element, which may specifically include but is not limited to the following situations:

[0271] The first network function entity receives a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to the request of the core network, wherein the context information creation request includes the network context information; wherein the first CU establishes the network context information as in the above embodiment, and the first CU sends the context information creation request to the first network function entity included in the first CU, which may be transmitted to the first network function entity through an API interface, a message bus, or a function call, etc.;

[0272] Alternatively, the first network function entity receives a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, and the context information update request includes the updated network context information; wherein, the first CU updates the network context information as in the above embodiment, and the first CU sends the context information update request to the first network function entity included in the first CU, and the context information update request may also be transmitted to the first network function entity through an API interface, a message bus, or a function call, etc.;

[0273] Alternatively, the first network function entity receives a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, and the context information synchronization request includes the updated network context information; wherein, if the network context is created or updated in the first network function entity, the created network context information or the updated network context information can be synchronized to other network function entities through the context information synchronization request; similarly, if other network function entities create or update the network context, the created network context information or the updated network context information can be synchronized to the first network function entity through the context information synchronization request, and the first network function entity can perform synchronization based on the received context information synchronization request.

[0274] Further, the network function entity performs a data service on the network context information based on the terminal identifier, including at least one of the following:

[0275] The first network function entity stores the network context information included in the context information creation request according to the terminal identifier, and sends a context information synchronization request to the second network function entity;

[0276] Alternatively, the first network function entity updates the currently stored network context information with the updated network context information included in the context information update request according to the terminal identifier, and sends a context information synchronization request to the second network function entity;

[0277] Alternatively, the first network function entity synchronizes the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

[0278] On the basis of any of the foregoing embodiments, the network function entity performs an event service on the network context information based on the terminal identifier, and may further include:

[0279] The second network function entity receives a notification event triggered by the first network function entity after creating or updating the network context information, and sends a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; wherein, since the first network function entity and the second network function entity subscribe to each other, the first network function entity triggers a notification event to the second network function entity after creating or updating the network context information, and the second network function entity sends a notification to the first DU where it is located based on the notification event, so that the first DU perceives the creation or update of the network context information, and then the first DU can query the second network function entity for the network context information, and then perform subsequent processing based on the network context information;

[0280] Alternatively, the first network function entity receives a notification event triggered by the second network function entity after updating the context information, and sends a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information; wherein the first DU may update the network context information when performing subsequent processing based on the network context information. Similarly, the first DU sends a context update request to the second network function entity, where the context update request includes the updated network context information. The second network function entity updates the network context information and synchronizes it to the first network function entity. Since the first network function entity and the second network function entity are subscribed to each other, the second network function entity triggers a notification event to the first network function entity after updating the network context information. Based on the notification event, the first network function entity sends a notification to the first CU where it is located, so that the first CU can perceive the update of the network context information, and then the first CU can query the first network function entity for the network context information, and then perform subsequent processing based on the network context information.

[0281] Further, the network function entity performs a data service on the network context information based on the terminal identifier, further comprising at least one of the following:

[0282] The second network function entity receives the context information query request sent by the first DU according to the notification, and sends the network context information to the first DU; or

[0283] The second network function entity receives a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; stores the updated network context information according to the terminal identifier, and sends a context information synchronization request to the first network function entity.

[0284] Figure 5 Flow chart of an access network information management method provided in this embodiment. Figure 5 As shown, this embodiment provides an access network information management method, the execution subject is an access network element, the access network element is connected to a network function entity, and / or the access network element is deployed with the network function entity. The access network information management method provided in this embodiment is a method embodiment of the access network element side in the above embodiment, and the specific steps of the method are as follows:

[0285] S301, creating or updating network context information;

[0286] S302, sending the network context information to the network function entity;

[0287] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0288] Optionally, sending the network context information to the network function entity includes:

[0289] After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or

[0290] After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or

[0291] If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

[0292] Optionally, the method further includes:

[0293] Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or

[0294] Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

[0295] Optionally, requesting a data service about the network context information from the network function entity based on the terminal identifier includes at least one of the following:

[0296] Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or

[0297] After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

[0298] Optionally, the controlling the network function entity to perform an event service regarding the network context information includes:

[0299] If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to subscribe to each other, so that the first access network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or

[0300] If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the first access network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

[0301] Optionally, the access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0302] After the terminal accesses the first CU and registers, the first CU establishes the network context information according to a request of the core network, and sends a context information creation request to the network function entity, where the context information creation request includes the network context information; or

[0303] After the terminal establishes a protocol data unit (PDU) session, the first CU updates the network context information and sends a context information update request to the network function entity, where the context information update request includes the updated network context information; or

[0304] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the second CU updates the network context information while keeping the terminal in an inactive state, and sends a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

[0305] Optionally, the requesting, from the network function entity, a data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0306] After the terminal moves and a switch occurs from the first CU to the second CU, the second CU sends a context information query request to the network function entity, where the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or

[0307] When the terminal is converted from an inactive state to a connected state, the first CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the first CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or

[0308] When the terminal is converted from an inactive state to a connected state, the second CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier.

[0309] Optionally, the access network network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service about the network context information includes:

[0310] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the first CU or the first DU determines that the first CU and the first DU cooperate to serve the terminal, and controls mutual subscription between a first network function entity in the first CU and a second network function entity in the first DU; or

[0311] After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the first CU, the first DU or the second DU determines that the first CU, the first DU and the second DU cooperate to serve the terminal, and controls the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0312] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the first CU determines that the first CU and the second DU cooperate to serve the terminal, controls the mutual subscription between the first network function entity and the third network function entity in the second DU, and controls the cancellation of the mutual subscription between the first network function entity and the second network function entity.

[0313] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0314] After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the first CU sends a context information creation request to the first network function entity, where the context information creation request includes the network context information; or

[0315] After the terminal establishes a PDU session and updates the network context information, the first CU sends a context information update request to the first network function entity, where the context information update request includes the updated network context information; or

[0316] The first CU controls the first network function entity to send a context information synchronization request to the second network function entity.

[0317] Optionally, the method further includes:

[0318] After the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the first DU receives a notification sent by the second network function entity, and sends a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or

[0319] After the first network function entity receives a notification event triggered by the second network function entity after updating context information, the first CU receives the notification sent by the first network function entity, and sends a context information query request to the first network function entity according to the notification to obtain the network context information for subsequent processing.

[0320] The access network information management method provided in this embodiment is an embodiment of the method on the access network element side in the above embodiments. Its principles and technical effects can be found in the above embodiments and will not be described in detail here.

[0321] The above process of the embodiment of the present application will be described in detail below with reference to specific examples.

[0322] Example 1

[0323] This example provides an access network information management method, the network function entity is centralized, such as Figure 6 As shown, the network function entity is connected to multiple CUs (centralized units), where for ease of description, it is assumed that the multiple CUs include a first CU (denoted as CU1), a second CU (denoted as CU2), etc. The centralized network function entity can provide data service functions as shown in the table.

[0324] Table 1 List of centralized network function entity services

[0325]

[0326] The signaling diagram of the access network information management method of this example is as follows Figure 7 As shown, the method includes:

[0327] 1) After network initialization is completed, the terminal (UE) accesses CU1 and registers to obtain the network's unique terminal identifier ueid, which can be, for example, the AMF UE NGAP ID.

[0328] 2) After receiving the network context information establishment request from the core network (CN), CU1 establishes the initial network context information (UE context), including querying the core network and the terminal (for example Figure 7Query UE capability information), CU1 itself configures network context information for UE, and sends a context information creation request to the network function entity, where the context information creation request includes the network context information;

[0329] The network function entity stores the network context information included in the context information creation request based on the terminal identifier ueid according to the context information creation request; the network function entity may also return a context information creation response to CU1;

[0330] 3) When the terminal wants to perform a service, it sends a PDU session establishment request to CU1. CU1 forwards the PDU session establishment request to the core network and receives the PDU session establishment acceptance message sent by the core network. CU1 uses the PDU session and other information as the updated network context information and sends a context information update request to the network function entity to update the PDU session and other information to the network function entity;

[0331] The network function entity updates the network context information corresponding to the terminal identifier ueid currently stored in the network function entity according to the updated network context information included in the context information update request; the network function entity may also return a context information update response.

[0332] 4) When the terminal moves, CU1 determines to switch according to the reported measurement results, that is, the terminal switches from CU1 to CU2. After CU2 receives the switching request through the NG interface (the interface between the CU and the core network) or the Xn interface (the interface between the wireless network nodes), CU2 can send a context information query request to the network function entity, and the context information query request includes the terminal identifier ueid; the network function entity queries the network context information according to the terminal identifier ueid, and sends the network context information to CU2, for example, returns a context information query response to CU2, and the context information query response includes the network context information. CU2 can perform subsequent processing based on the network context information;

[0333] 5) When the terminal service is terminated and enters the inactive state, if the terminal does not move, or moves but does not switch CU, if the terminal is in CU2 at this time, when the terminal is converted from the inactive state to the connected state (triggering RRC Resume), CU2 may send a context information query request to the network function entity, and the context information query request includes the terminal identifier ueid; the network function entity queries the network context information according to the terminal identifier ueid, and sends the network context information to CU2, and CU2 may perform subsequent processing based on the network context information to restore the terminal to the connected state;

[0334] 6) After the terminal service is terminated and enters the inactive state, if the terminal moves and triggers RNA Update when it is in the inactive state, when switching from CU2 to CU1 occurs, while the terminal continues to be in the inactive state (without switching to the connected state first and then returning to the inactive state), CU1 updates the network context information and sends a context information update request to the network function entity, and the context information update request includes the updated network context information; the network function entity updates the network context information corresponding to the terminal identifier ueid currently stored in the network function entity according to the updated network context information included in the context information update request;

[0335] When the terminal is converted from an inactive state to a connected state (triggering RRC Resume), CU1 may send a context information query request to the network function entity, where the context information query request includes the terminal identifier ueid; the network function entity queries the network context information according to the terminal identifier ueid, and sends the network context information to CU1, and CU1 may perform subsequent processing based on the network context information to restore the terminal to a connected state;

[0336] 7) After CU1 detects that the terminal has left the network or is turned off offline, CU1 may send a context information deletion request to the network function entity, and the context information deletion request includes the terminal identifier ueid; the network function entity deletes the network context information corresponding to the terminal identifier ueid according to the context information deletion request. The network function entity may also return a context information deletion response to CU1.

[0337] Example 2

[0338] This example provides an access network information management method, where the network function entity is distributedly deployed, such as Figure 8 As shown, the network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network. For the convenience of description, it is assumed that at least one CU includes a first CU (denoted as CU1), and multiple DUs include a first DU (denoted as DU1), a second DU (denoted as DU2), etc. The first network function entity ( Figure 8 The second network function entity ( Figure 8 The third network function entity ( Figure 8 In the table, it is marked as network function entity 3), and the distributed network function entity can provide data service functions as shown in the table.

[0339] Table 2 List of distributed network function entity services

[0340]

[0341] The access network information management method of this example specifically includes:

[0342] 1) After network initialization is completed, the terminal (UE) accesses the network through the first transmission and reception point TRP1 under DU1, and obtains the network unique terminal identifier ueid, which can be, for example, RAN NGAP UE ID. CU1 and DU1 cooperate to serve the terminal, and the first network function entity in CU1 and the second network function entity in DU1 call the subscription service, and subscribe to each other between the first network function entity in CU1 and the second network function entity in DU1;

[0343] 2) The terminal initiates and completes CN registration. After CU1 receives the network context information establishment request from the core network (CN), it establishes the initial network context information (UE context), which includes querying the core network, querying the terminal, querying DU1, and the network context information configured by CU1 for the UE; then executes:

[0344] a) CU1 sends a context information creation request to the first network function entity in CU1, where the context information creation request includes network context information; the first network function entity in CU1 stores the network context information included in the context information creation request based on the terminal identifier ueid according to the context information creation request; the first network function entity in CU1 may also return a context information creation response to CU1;

[0345] b) The first network function entity in CU1 sends a context information synchronization request to the second network function entity in DU1 and the third network function entity in DU2, where the context information synchronization request includes network context information, so that the second network function entity in DU1, the third network function entity in DU2 and the first network function entity in CU1 can synchronize network context information; in addition, the first network function entity in CU1 triggers a notification event to the second network function entity in DU1 after creating the network context information, where the notification event carries at least an event triggered by creating or updating the network context information, such as F1_UE CONTEXT SETUP REQUEST, so that the second network function entity sends a notification to DU1, where the notification is used to instruct DU1 to perform subsequent processing according to the network context information;

[0346] 3) After receiving the notification event triggered by the first network function entity in CU1, the second network function entity in DU1 sends a notification to DU1. DU1 sends a context information query request to the second network function entity in DU1 according to the notification, and the context information query request includes the terminal identifier ueid; the second network function entity in DU1 queries the network context information according to the terminal identifier ueid, and sends the network context information to DU1. DU1 performs subsequent processing according to the network context information, updates the network context information, and then executes:

[0347] a) DU1 sends a context information update request to the second network function entity in DU1, where the context information update request includes updated network context information; the second network function entity in DU1 updates the updated network context information included in the context information update request to the network context information corresponding to the terminal identifier ueid according to the context information update request; the second network function entity in DU1 may also return a context information update response to DU1;

[0348] b) The second network function entity in DU1 sends a context information synchronization request to the first network function entity in CU1 and the third network function entity in DU2, wherein the context information synchronization request includes network context information, so that the second network function entity in DU1, the third network function entity in DU2 and the first network function entity in CU1 can synchronize network context information; in addition, the second network function entity in DU1 triggers a notification event to the first network function entity in CU1 after updating the network context information, so that the first network function entity sends a notification to CU1, wherein the notification is used to instruct CU1 to perform subsequent processing according to the network context information;

[0349] 4) After receiving the notification event triggered by the second network function entity in DU1, the first network function entity in CU1 sends a notification to CU1, and CU1 sends a context information query request to the first network function entity in CU1 according to the notification, and the context information query request includes the terminal identifier ueid; the first network function entity in CU1 queries the network context information according to the terminal identifier ueid, and sends the network context information to CU1, and CU1 performs subsequent processing according to the network context information, such as completing RRC reconfiguration and other message processes to complete the terminal access to the network;

[0350] 5) When the terminal wants to conduct business, it sends a PDU session establishment request to CU1. CU1 forwards the PDU session establishment request to the core network and receives the PDU session establishment acceptance message sent by the core network. CU1 uses the PDU session and other information as the updated network context information, and then performs context update and synchronization of the network functional entity, which is similar to the process in steps 2) and 3) above and will not be repeated here.

[0351] 6) When the terminal moves, after TRP1 under DU1 switches to TRP2 shared by DU1 and DU2, the network serves the terminal according to the measurement scheduling TRPG1. At this time, CU1, DU1 and DU2 cooperate to serve the terminal. The subscription service is called between the first network function entity in CU1, the second network function entity in DU1 and the third network function entity in DU2, and the first network function entity in CU1, the second network function entity in DU1 and the third network function entity in DU2 are mutually subscribed;

[0352] When DU2 transmits terminal data independently or collaboratively with DU1 according to the configuration, DU2 may send a context information query request to the third network function entity in DU2, and the context information query request includes the terminal identifier ueid; the third network function entity in DU2 queries the network context information according to the terminal identifier ueid, and sends the network context information to DU2, and DU2 may perform subsequent processing based on the network context information; the terminal continues the service after accessing TRPG1;

[0353] 7) When the terminal continues to move, when TRP2 shared by DU1 and DU2 switches to TRP3 under DU2, the network serves the terminal according to the measurement scheduling TRPG2, DU1 no longer serves the terminal, CU1 and DU2 cooperate to serve the terminal, and the first network function entity in CU1 and the second network function entity in DU1 call the unsubscription service to cancel the mutual subscription between the first network function entity in CU1 and the second network function entity in DU1;

[0354] At the same time, CU1 configuration switches to DU2, updates the network context information, and CU1 executes and then executes the context update and synchronization of the network function entity, that is, repeats the process in the above step 2), which will not be repeated here; DU2 and the third network function entity in DU2 repeat step 3), and DU2 performs subsequent processing according to the network context information, and the terminal continues the service after accessing TRPG2.

[0355] 8) When the terminal moves, and TRP1 under DU1 directly switches to TRP3 under DU2, the network serves the terminal according to the measurement scheduling TRPG2, DU1 no longer serves the terminal, CU1 and DU2 cooperate to serve the terminal, and the first network function entity in CU1 and the second network function entity in DU1 call the unsubscription service to cancel the mutual subscription between the first network function entity in CU1 and the second network function entity in DU1; the first network function entity in CU1 and the third network function entity in DU2 call the subscription service to subscribe the first network function entity in CU1 and the third network function entity in DU2;

[0356] At the same time, CU1 configuration switches to DU2, updates the network context information, and CU1 executes and then executes the context update and synchronization of the network function entity, that is, repeats the process in the above step 2), which will not be repeated here; DU2 and the third network function entity in DU2 repeat step 3), and DU2 performs subsequent processing according to the network context information, and the terminal continues the service after accessing TRPG2.

[0357] 9) After each access network element confirms that the terminal has left the network or is shut down and offline, each access network element may send a context information deletion request to its respective network function entity, where the context information deletion request includes the terminal identifier ueid, so that the respective network function entity deletes the network context information corresponding to the terminal identifier ueid according to the context information deletion request; or after the network function entity in any access network element deletes the network context information corresponding to the terminal identifier ueid, it sends a context information synchronization request to the network function entities in other access network elements, so that the network function entities in other access network elements also delete the network context information corresponding to the terminal identifier ueid.

[0358] Example 3

[0359] This example provides an access network information management method, in which the network function entity combines centralized deployment and distributed deployment, such as Fig. 9 As shown, a centralized network function entity is connected to multiple CUs, and multiple distributed network function entities are deployed in multiple DUs respectively, and the network function entities are connected to each other.

[0360] On this basis, the access network information management method of this example may be similar to the above-mentioned Example 2, except that, in this example, the first network function entity in CU1 in Example 2 is replaced with a centralized network function entity connected to CU1; in addition, when the terminal moves and switches between CUs, the corresponding steps in Example 1 may be executed, and when the network context information in the centralized network function entity is updated, the corresponding steps in Example 2 may be referred to for synchronization between the network function entities, which will not be repeated here.

[0361] It should be noted that some steps in the above examples may not be executed, and steps in different examples may be combined with each other without conflict.

[0362] Fig.10 The network function entity provided in this embodiment is connected to multiple access network elements and / or distributedly deployed in multiple access network elements. The network function entity can execute the processing flow provided by the method embodiment on the network function entity side, such as Fig.10 As shown, the network function entity 400 includes a memory 401 , a transceiver 402 , and a processor 403 .

[0363] Among them, Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 403 and various circuits of memory represented by memory 401 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 402 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 403 is responsible for managing the bus architecture and general processing, and the memory 401 may store data used by the processor 403 when performing operations.

[0364] The processor 403 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0365] The memory 401 is used to store computer programs; the transceiver 402 is used to send and receive data under the control of the processor 403; the processor 403 is used to read the computer program in the memory 401 and perform the following operations:

[0366] Obtaining network context information created or updated by any access network element;

[0367] Identifying the network context information according to the terminal identifier, and storing and / or managing the network context information based on the terminal identifier;

[0368] The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

[0369] Optionally, when storing and / or managing the network context information based on the terminal identifier, the processor 403 is configured to:

[0370] Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or

[0371] An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

[0372] Optionally, when acquiring network context information created or updated by any access network element, the processor 403 is configured to:

[0373] Receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; acquiring the network context information according to the context information creation request; or

[0374] Receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; acquiring the updated network context information according to the context information update request; or

[0375] If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, a context information synchronization request sent by other network function entities deployed in other access network elements is received, and the context information synchronization request includes the network context information; and the network context information is obtained according to the context information synchronization request.

[0376] Optionally, the processor 403 executes the data service about the network context information based on the terminal identifier, and is configured to perform at least one of the following:

[0377] storing, according to the context information creation request, the network context information included in the context information creation request; or

[0378] updating the currently stored network context information according to the context information update request and according to the updated network context information included in the context information update request; or

[0379] According to the context information synchronization request, synchronizing currently stored network context information with the network context information included in the context information synchronization request; or

[0380] Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or

[0381] A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

[0382] Optionally, when executing the event service regarding the network context information based on the terminal identifier, the processor 403 is configured to perform at least one of the following:

[0383] If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or

[0384] Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or

[0385] If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

[0386] Optionally, the network function entity is connected to multiple access network centralized units CU; accordingly, when the processor 403 obtains the network context information created or updated by any access network network element, it is used to:

[0387] After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or

[0388] After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or

[0389] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

[0390] Optionally, when executing the data service about the network context information based on the terminal identifier, the processor 403 is configured to perform at least one of the following:

[0391] According to the context information creation request, storing the network context information included in the context information creation request; or

[0392] According to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request; or

[0393] After the terminal moves and a switch occurs from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or

[0394] When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or

[0395] When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

[0396] Optionally, the network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, when the processor 403 executes the event service about the network context information based on the terminal identifier, it is used to:

[0397] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or

[0398] After the terminal moves, the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0399] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

[0400] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the acquiring of network context information created or updated by any access network network element includes:

[0401] The processor 403 of the first network function entity is used to receive a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to the request of the core network, wherein the context information creation request includes the network context information; or

[0402] The processor 403 of the first network function entity is used to receive a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, where the context information update request includes the updated network context information; or

[0403] The processor 403 of the first network function entity is used to receive a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, and the context information synchronization request includes the updated network context information.

[0404] Optionally, the performing of the data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0405] The processor 403 of the first network function entity is configured to store the network context information included in the context information creation request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0406] The processor 403 of the first network function entity is used to update the currently stored network context information with the updated network context information included in the context information update request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0407] The processor 403 of the first network function entity is configured to synchronize the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

[0408] Optionally, the executing the event service regarding the network context information based on the terminal identifier further includes:

[0409] The processor 403 of the second network function entity is used to receive a notification event triggered by the first network function entity after creating or updating the network context information, and send a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or

[0410] The processor 403 of the first network function entity is used to receive a notification event triggered by the second network function entity after updating the context information, and send a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

[0411] Optionally, the performing the data service on the network context information based on the terminal identifier further includes at least one of the following:

[0412] The processor 403 of the second network function entity is configured to receive a context information query request sent by the first DU according to the notification, and send the network context information to the first DU; or

[0413] The processor 403 of the second network function entity is used to receive a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; store the updated network context information according to the terminal identifier, and send a context information synchronization request to the first network function entity.

[0414] Optionally, the network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

[0415] The network function entity provided in the embodiment of the present application can be specifically used to execute the method embodiment on the above-mentioned network function entity side, and the specific functions are not repeated here.

[0416] Fig.11 The present application embodiment is a structural diagram of an access network element. The access network element provided in this embodiment is connected to a network function entity, and / or the access network element is deployed with the network function entity. The access network element can execute the processing flow provided by the method embodiment on the access network element side, such as Fig.11 As shown, the access network element 500 includes a memory 501 , a transceiver 502 , and a processor 503 .

[0417] Among them, Fig.11 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 503 and various circuits of memory represented by memory 501 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 502 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 503 is responsible for managing the bus architecture and general processing, and the memory 501 may store data used by the processor 503 when performing operations.

[0418] The processor 503 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0419] The memory 501 is used to store computer programs; the transceiver 502 is used to send and receive data under the control of the processor 503; the processor 503 is used to read the computer program in the memory 501 and perform the following operations:

[0420] Create or update network context information;

[0421] Sending the network context information to the network function entity;

[0422] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0423] Optionally, when sending the network context information to the network function entity, the processor 503 is configured to:

[0424] After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or

[0425] After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or

[0426] If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

[0427] Optionally, the processor 503 is further configured to:

[0428] Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or

[0429] Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

[0430] Optionally, when the processor 503 requests the network function entity for a data service regarding the network context information based on the terminal identifier, it is configured to perform at least one of the following:

[0431] Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or

[0432] After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

[0433] Optionally, when controlling the network function entity to perform an event service regarding the network context information, the processor 503 is configured to:

[0434] If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to subscribe to each other, so that the first access network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or

[0435] If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the processor 503 of the first access network element is used to control the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

[0436] Optionally, the access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0437] After the terminal accesses the first CU and registers, the processor 503 of the first CU is used to establish the network context information according to the request of the core network, and send a context information creation request to the network function entity, where the context information creation request includes the network context information; or

[0438] After the terminal establishes a protocol data unit PDU session, the processor 503 of the first CU is used to update the network context information and send a context information update request to the network function entity, where the context information update request includes the updated network context information; or

[0439] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the processor 503 of the second CU is used to update the network context information while keeping the terminal in an inactive state, and send a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

[0440] Optionally, the requesting, from the network function entity, a data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0441] After the terminal moves and switches from the first CU to the second CU, the processor 503 of the second CU is used to send a context information query request to the network function entity, where the context information query request includes a terminal identifier; the processor 503 of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0442] When the terminal is converted from an inactive state to a connected state, the processor 503 of the first CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor 503 of the first CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0443] When the terminal is converted from an inactive state to a connected state, the processor 503 of the second CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor 503 of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier.

[0444] Optionally, the access network network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service about the network context information includes:

[0445] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the processor 503 of the first CU or the processor 503 of the first DU is used to determine that the first CU and the first DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity in the first CU and the second network function entity in the first DU; or

[0446] After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the processor 503 of the first CU, the processor 503 of the first DU or the processor 503 of the second DU is used to determine that the first CU, the first DU and the second DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0447] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the processor 503 of the first CU is used to determine that the first CU and the second DU cooperate to serve the terminal, control the mutual subscription between the first network function entity and the third network function entity in the second DU, and control the cancellation of the mutual subscription between the first network function entity and the second network function entity.

[0448] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0449] After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the processor 503 of the first CU is used to send a context information creation request to the first network function entity, where the context information creation request includes the network context information; or

[0450] After the terminal establishes a PDU session and updates the network context information, the processor 503 of the first CU is used to send a context information update request to the first network function entity, where the context information update request includes the updated network context information; or

[0451] The processor 503 of the first CU is used to control the first network function entity to send a context information synchronization request to the second network function entity.

[0452] Optionally, after the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the processor 503 of the first DU is used to receive a notification sent by the second network function entity, and send a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or

[0453] When the first network function entity receives a notification event triggered by the second network function entity after updating context information, the processor 503 of the first CU is used to receive the notification sent by the first network function entity, and send a context information query request to the first network function entity according to the notification, so as to obtain the network context information for subsequent processing.

[0454] The access network element provided in the embodiment of the present application can be specifically used to execute the method embodiment on the access network element side, and the specific functions will not be repeated here.

[0455] Fig.12 The access network information management device provided in this embodiment can execute the processing flow provided in the method embodiment of the network function entity side, such as Fig. 9 As shown, the access network information management device 600 includes: a receiving unit 601 and a processing unit 602.

[0456] A receiving unit 601 is used to obtain network context information created or updated by any access network element;

[0457] The processing unit 602 is configured to identify the network context information according to the terminal identifier, and store and / or manage the network context information based on the terminal identifier;

[0458] The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

[0459] Optionally, when storing and / or managing the network context information based on the terminal identifier, the processing unit 602 is configured to:

[0460] Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or

[0461] An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

[0462] Optionally, when acquiring the network context information created or updated by any access network element, the receiving unit 601 is configured to:

[0463] Receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; acquiring the network context information according to the context information creation request; or

[0464] Receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; acquiring the updated network context information according to the context information update request; or

[0465] If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, a context information synchronization request sent by other network function entities deployed in other access network elements is received, and the context information synchronization request includes the network context information; and the network context information is obtained according to the context information synchronization request.

[0466] Optionally, when executing the data service regarding the network context information based on the terminal identifier, the processing unit 602 is configured to perform at least one of the following:

[0467] storing, according to the context information creation request, the network context information included in the context information creation request; or

[0468] updating the currently stored network context information according to the context information update request and according to the updated network context information included in the context information update request; or

[0469] According to the context information synchronization request, synchronizing currently stored network context information with the network context information included in the context information synchronization request; or

[0470] Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or

[0471] A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

[0472] Optionally, when executing the event service regarding the network context information based on the terminal identifier, the processing unit 602 is configured to perform at least one of the following:

[0473] If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or

[0474] Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or

[0475] If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

[0476] Optionally, the network function entity is connected to multiple access network centralized units CU; accordingly, the receiving unit 601 acquires the network context information created or updated by any access network element, including:

[0477] After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or

[0478] After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or

[0479] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

[0480] Optionally, when executing the data service regarding the network context information based on the terminal identifier, the processing unit 602 is configured to perform at least one of the following:

[0481] According to the context information creation request, storing the network context information included in the context information creation request; or

[0482] According to the context information update request, the currently stored network context information is updated according to the updated network context information included in the context information update request; or

[0483] After the terminal moves and a switch occurs from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or

[0484] When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or

[0485] When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

[0486] Optionally, the network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, when the processing unit 602 performs an event service on the network context information based on the terminal identifier, it is used to:

[0487] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or

[0488] After the terminal moves, the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0489] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

[0490] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the receiving unit 601 acquires network context information created or updated by any access network network element, including:

[0491] The receiving unit 601 of the first network function entity is used to receive a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to the request of the core network, wherein the context information creation request includes the network context information; or

[0492] The receiving unit 601 of the first network function entity is used to receive a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, wherein the context information update request includes the updated network context information; or

[0493] The receiving unit 601 of the first network function entity is used to receive a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, and the context information synchronization request includes the updated network context information.

[0494] Optionally, the performing the data service on the network context information based on the terminal identifier includes at least one of the following:

[0495] The processing unit 602 of the first network function entity is used to store the network context information included in the context information creation request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0496] The processing unit 602 of the first network function entity is used to update the currently stored network context information with the updated network context information included in the context information update request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or

[0497] The processing unit 602 of the first network function entity is configured to synchronize the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

[0498] Optionally, the executing the event service regarding the network context information based on the terminal identifier further includes:

[0499] The processing unit 602 of the second network function entity is used to receive a notification event triggered by the first network function entity after creating or updating the network context information, and send a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or

[0500] The processing unit 602 of the first network function entity is used to receive a notification event triggered by the second network function entity after updating the context information, and send a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

[0501] Optionally, the performing the data service on the network context information based on the terminal identifier further includes at least one of the following:

[0502] The processing unit 602 of the second network function entity is configured to receive a context information query request sent by the first DU according to the notification, and send the network context information to the first DU; or

[0503] The processing unit 602 of the second network function entity is used to receive a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; store the updated network context information according to the terminal identifier, and send a context information synchronization request to the first network function entity.

[0504] Optionally, the network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

[0505] The access network information management device provided in the embodiment of the present application can be specifically used to execute the method embodiment on the above-mentioned network function entity side, and the specific functions will not be repeated here.

[0506] Fig.13The access network information management device provided in this embodiment can execute the processing flow provided in the method embodiment of the access network element side, such as Fig.13 As shown, the access network information management device 700 includes: a processing unit 701 and a sending unit 702.

[0507] The processing unit 701 is used to create or update network context information;

[0508] A sending unit 702, configured to send the network context information to the network function entity;

[0509] The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

[0510] Optionally, when sending the network context information to the network function entity, the sending unit 702 is configured to:

[0511] After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or

[0512] After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or

[0513] If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

[0514] Optionally, the processing unit 701 is further configured to:

[0515] Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or

[0516] Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

[0517] Optionally, when the processing unit 701 requests the network function entity for a data service regarding the network context information based on the terminal identifier, it is configured to perform at least one of the following:

[0518] Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or

[0519] After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

[0520] Optionally, the controlling the network function entity to perform an event service regarding the network context information includes:

[0521] If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the processing unit 701 of the first access network network element is used to control the first network function entity in the first access network network element and the second network function entity in the second access network network element to subscribe to each other, so that the first access network network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or

[0522] If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the processing unit 701 of the first access network element is used to control the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

[0523] Optionally, the access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0524] After the terminal accesses the first CU and registers, the sending unit 702 of the first CU is used to establish the network context information according to the request of the core network, and send a context information creation request to the network function entity, where the context information creation request includes the network context information; or

[0525] After the terminal establishes a protocol data unit PDU session, the sending unit 702 of the first CU is used to update the network context information and send a context information update request to the network function entity, where the context information update request includes the updated network context information; or

[0526] When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the sending unit 702 of the second CU is used to update the network context information while keeping the terminal in an inactive state, and send a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

[0527] Optionally, the requesting, from the network function entity, a data service regarding the network context information based on the terminal identifier includes at least one of the following:

[0528] After the terminal moves and switches from the first CU to the second CU, the processing unit 701 of the second CU is used to send a context information query request to the network function entity, where the context information query request includes a terminal identifier; the processing unit 701 of the second CU is used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0529] When the terminal is converted from an inactive state to a connected state, the processing unit 701 of the first CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processing unit 701 of the first CU is used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or

[0530] When the terminal is converted from an inactive state to a connected state, the processing unit 701 of the second CU is used to send a context information query request to the network function entity, and the context information query request includes a terminal identifier; the processing unit 701 of the second CU is used to receive the network context information sent by the network function entity after querying according to the terminal identifier.

[0531] Optionally, the access network network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service about the network context information includes:

[0532] After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the processing unit 701 of the first CU or the processing unit 701 of the first DU is used to determine that the first CU and the first DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity in the first CU and the second network function entity in the first DU; or

[0533] After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the processing unit 701 of the first CU, the processing unit 701 of the first DU or the processing unit 701 of the second DU is used to determine that the first CU, the first DU and the second DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or

[0534] After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the processing unit 701 of the first CU is used to determine that the first CU and the second DU cooperate to serve the terminal, control the mutual subscription between the first network function entity and the third network function entity in the second DU, and control the cancellation of the mutual subscription between the first network function entity and the second network function entity.

[0535] Optionally, when a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating the network context information and sending the network context information to the network function entity includes:

[0536] After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the processing unit 701 of the first CU is used to send a context information creation request to the first network function entity, where the context information creation request includes the network context information; or

[0537] After the terminal establishes a PDU session and updates the network context information, the processing unit 701 of the first CU is used to send a context information update request to the first network function entity, where the context information update request includes the updated network context information; or

[0538] The first CU controls the first network function entity to send a context information synchronization request to the second network function entity.

[0539] Optionally, after the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the processing unit 701 of the first DU is also used to receive a notification sent by the second network function entity, and send a context information query request to the second network function entity according to the notification to obtain the network context information for subsequent processing and update the network context information; or

[0540] When the first network function entity receives a notification event triggered by the second network function entity after updating the context information, the processing unit 701 of the first CU is also used to receive the notification sent by the first network function entity, and send a context information query request to the first network function entity according to the notification, so as to obtain the network context information for subsequent processing.

[0541] The access network information management device provided in the embodiment of the present application can be specifically used to execute the method embodiment on the access network element side, and the specific functions will not be repeated here.

[0542] It should be noted that the division of units in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated in a processing unit 701, or each unit may exist physically separately, or two or more units may be integrated in one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0543] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0544] An embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program is used to enable a processor to execute the above method embodiment.

[0545] Among them, the computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0546] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0547] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0548] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0549] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0550] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for managing access network information, characterized in that: Applied to a network function entity, the method comprises: Obtaining network context information created or updated by any access network element; Identifying the network context information according to the terminal identifier, and storing and / or managing the network context information based on the terminal identifier; The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

2. The method according to claim 1, characterized in that The storing and / or managing the network context information based on the terminal identifier includes: Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

3. The method according to claim 2, characterized in that The obtaining of network context information created or updated by any access network element includes: Receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; acquiring the network context information according to the context information creation request; or Receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; acquiring the updated network context information according to the context information update request; or If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, a context information synchronization request sent by other network function entities deployed in other access network elements is received, and the context information synchronization request includes the network context information; and the network context information is obtained according to the context information synchronization request.

4. The method according to claim 3, characterized in that The performing of the data service on the network context information based on the terminal identifier includes at least one of the following: storing, according to the context information creation request, the network context information included in the context information creation request; or According to the context information update request, updating the currently stored network context information according to the updated network context information included in the context information update request; or According to the context information synchronization request, synchronizing the currently stored network context information with the network context information included in the context information synchronization request; or Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

5. The method according to claim 3, characterized in that: The performing of the event service on the network context information based on the terminal identifier includes at least one of the following: If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

6. The method according to any one of claims 2 to 5, characterized in that: The network function entity is connected to a plurality of access network centralized units CU; accordingly, the obtaining of network context information created or updated by any access network element includes: After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

7. The method according to claim 6, characterized in that The performing of the data service on the network context information based on the terminal identifier includes at least one of the following: According to the context information creation request, storing the network context information included in the context information creation request; or According to the context information update request, updating the currently stored network context information according to the updated network context information included in the context information update request; or After the terminal moves and switches from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

8. The method according to claim 5, characterized in that The network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, the event service about the network context information is executed based on the terminal identifier, including: After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or After the terminal moves, the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

9. The method according to claim 8, characterized in that In a case where a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the acquiring network context information created or updated by any access network element includes: The first network function entity receives a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or The first network function entity receives a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, where the context information update request includes the updated network context information; or The first network function entity receives a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, wherein the context information synchronization request includes the updated network context information.

10. The method according to claim 9, characterized in that The performing of the data service on the network context information based on the terminal identifier includes at least one of the following: The first network function entity stores the network context information included in the context information creation request according to the terminal identifier, and sends a context information synchronization request to the second network function entity; or The first network function entity updates currently stored network context information with updated network context information included in the context information update request according to the terminal identifier, and sends a context information synchronization request to the second network function entity; or The first network function entity synchronizes the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

11. The method according to claim 10, characterized in that The performing of the event service on the network context information based on the terminal identification further includes: The second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, and sends a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or The first network function entity receives a notification event triggered by the second network function entity after updating context information, and sends a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

12. The method according to claim 11, characterized in that The performing of the data service on the network context information based on the terminal identification further includes at least one of the following: The second network function entity receives the context information query request sent by the first DU according to the notification, and sends the network context information to the first DU; or The second network function entity receives a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; The updated network context information is stored according to the terminal identifier, and a context information synchronization request is sent to the first network function entity.

13. The method according to claim 1, characterized in that The network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

14. A method for managing access network information, characterized in that: Applied to an access network element, the method comprises: Create or update network context information; Sending the network context information to the network function entity; The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

15. The method according to claim 14, characterized in that The sending the network context information to the network function entity includes: After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

16. The method according to claim 15, characterized in that The method further comprises: Requesting a data service about the network context information from the network function entity based on the terminal identification, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

17. The method according to claim 16, characterized in that Requesting a data service about the network context information from the network function entity based on the terminal identifier includes at least one of the following: Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

18. The method according to claim 16, characterized in that The controlling the network function entity to perform an event service on the network context information includes: If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to subscribe to each other, so that the first access network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the first access network element controls the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

19. The method according to any one of claims 14 to 18, characterized in that: The access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes: After the terminal accesses the first CU and registers, the first CU establishes the network context information according to a request of the core network, and sends a context information creation request to the network function entity, where the context information creation request includes the network context information; or After the terminal establishes a protocol data unit (PDU) session, the first CU updates the network context information and sends a context information update request to the network function entity, where the context information update request includes the updated network context information; or When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the second CU updates the network context information while keeping the terminal in an inactive state, and sends a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

20. The method according to any one of claims 14 to 18, characterized in that: The requesting the network function entity for a data service regarding the network context information based on the terminal identifier includes at least one of the following: After the terminal moves and a switch occurs from the first CU to the second CU, the second CU sends a context information query request to the network function entity, where the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or When the terminal is converted from an inactive state to a connected state, the first CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the first CU receives the network context information sent by the network function entity after querying according to the terminal identifier; or When the terminal is converted from an inactive state to a connected state, the second CU sends a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the second CU receives the network context information sent by the network function entity after querying according to the terminal identifier.

21. The method according to any one of claims 14 to 18, characterized in that: The access network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service on the network context information includes: After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the first CU or the first DU determines that the first CU and the first DU cooperate to serve the terminal, and controls mutual subscription between a first network function entity in the first CU and a second network function entity in the first DU; or After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the first CU, the first DU or the second DU determines that the first CU, the first DU and the second DU cooperate to serve the terminal, and controls the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the first CU determines that the first CU and the second DU cooperate to serve the terminal, controls the mutual subscription between the first network function entity and the third network function entity in the second DU, and controls the cancellation of the mutual subscription between the first network function entity and the second network function entity.

22. The method according to claim 21, characterized in that In a case where a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating network context information and sending the network context information to the network function entity includes: After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the first CU sends a context information creation request to the first network function entity, where the context information creation request includes the network context information; or After the terminal establishes a PDU session and updates the network context information, the first CU sends a context information update request to the first network function entity, where the context information update request includes the updated network context information; or The first CU controls the first network function entity to send a context information synchronization request to the second network function entity.

23. The method according to claim 22, characterized in that The method further comprises: After the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the first DU receives a notification sent by the second network function entity, and sends a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or After the first network function entity receives a notification event triggered by the second network function entity after updating context information, the first CU receives the notification sent by the first network function entity, and sends a context information query request to the first network function entity according to the notification to obtain the network context information for subsequent processing.

24. A network function entity, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Obtaining network context information created or updated by any access network element; Identifying the network context information according to the terminal identifier, and storing and / or managing the network context information based on the terminal identifier; The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

25. The network function entity according to claim 24, characterized in that: When the processor stores and / or manages the network context information based on the terminal identifier, the processor is configured to: Execute a data service on the network context information based on the terminal identification, the data service comprising at least one of the following: storage, query, update, deletion and data synchronization of the network context information; and / or An event service on the network context information is executed based on the terminal identifier, and the event service includes at least one of the following: subscription, notification and unsubscription between network function entities deployed in other access network elements.

26. The network function entity according to claim 25, characterized in that: When acquiring network context information created or updated by any access network element, the processor is used to: receiving a context information creation request sent by any access network element after establishing the network context information, wherein the context information creation request includes the network context information; Acquiring the network context information according to the context information creation request; or receiving a context information update request sent by any access network element after updating the network context information, wherein the context information update request includes the updated network context information; Acquire updated network context information according to the context information update request; or If the network function entity is distributedly deployed in multiple access network elements, then for the network function entity deployed in any access network element, receiving a context information synchronization request sent by other network function entities deployed in other access network elements, wherein the context information synchronization request includes the network context information; The network context information is acquired according to the context information synchronization request.

27. The network function entity according to claim 26, characterized in that: The processor performs a data service on the network context information based on the terminal identifier, and is configured to perform at least one of the following: storing, according to the context information creation request, the network context information included in the context information creation request; or According to the context information update request, updating the currently stored network context information according to the updated network context information included in the context information update request; or According to the context information synchronization request, synchronizing the currently stored network context information with the network context information included in the context information synchronization request; or Receiving a context information query request sent by any access network element, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the access network element; or A context information deletion request is received from any access network element after detecting that the terminal has left the network or is powered off and offline, and network context information corresponding to the terminal is deleted according to the context information deletion request.

28. The network function entity according to claim 26, characterized in that: When the processor executes the event service regarding the network context information based on the terminal identifier, the processor is configured to execute at least one of the following: If it is determined that the access network element where the terminal is located cooperates with other access network elements to serve the terminal, subscribing to each other with other network function entities in the other access network elements; or Receiving a notification event triggered by other network function entities deployed in other access network elements after creating or updating network context information, and sending a notification to the access network element where the entity is located, wherein the notification is used to instruct the access network element where the entity is located to perform subsequent processing according to the network context information; or If it is determined that the access network element where the user is located stops cooperating with other access network elements to serve the terminal, the mutual subscription with other network function entities in the other access network elements is cancelled.

29. The network function entity according to any one of claims 25 to 28, characterized in that: The network function entity is connected to a plurality of access network centralized units CU; accordingly, when the processor obtains network context information created or updated by any access network element, it is used to: After the terminal accesses the first CU and registers, receiving a context information creation request sent by the first CU after establishing the network context information according to a request of the core network, wherein the context information creation request includes the network context information; or After the terminal establishes a protocol data unit (PDU) session, receiving a context information update request sent by the first CU after updating the network context information, wherein the context information update request includes the updated network context information; or When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, a context information update request is received after the second CU updates the network context information while keeping the terminal in an inactive state, and the context information update request includes the updated network context information.

30. The network function entity according to claim 29, characterized in that: When executing the data service related to the network context information based on the terminal identifier, the processor is configured to perform at least one of the following: According to the context information creation request, storing the network context information included in the context information creation request; or According to the context information update request, updating the currently stored network context information according to the updated network context information included in the context information update request; or After the terminal moves and switches from the first CU to the second CU, receiving a context information query request sent by the second CU, wherein the context information query request includes a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the second CU; or When the terminal is converted from an inactive state to a connected state, receiving a context information query request sent by the first CU, the context information query request including a terminal identifier; querying the network context information according to the terminal identifier, and sending the network context information to the first CU; or When the terminal is converted from an inactive state to a connected state, a context information query request sent by the second CU is received, wherein the context information query request includes a terminal identifier; the network context information is queried according to the terminal identifier, and the network context information is sent to the second CU.

31. The network function entity according to claim 28, characterized in that: The network function entity is distributedly deployed in at least one centralized unit CU and multiple distributed units DU of the access network; accordingly, when the processor executes the event service about the network context information based on the terminal identifier, it is used to: After the terminal accesses the first CU through the first transmission and reception point TRP under the first DU and registers, it is determined that the first CU and the first DU cooperate to serve the terminal, and a first network function entity in the first CU and a second network function entity in the first DU are mutually subscribed; or After the terminal moves, the first transmission and reception point TRP under the first DU is switched to the second transmission and reception point TRP shared by the first DU and the second DU, determining that the first CU, the first DU, and the second DU cooperate to serve the terminal, and mutually subscribing to the first network function entity, the second network function entity, and the third network function entity in the second DU; or After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, it is determined that the first CU and the second DU cooperate to serve the terminal, the first network function entity and the third network function entity in the second DU are mutually subscribed, and the mutual subscription between the first network function entity and the second network function entity is canceled.

32. The network function entity according to claim 31, characterized in that: In a case where a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the acquiring of network context information created or updated by any access network element includes: The processor of the first network function entity is used to receive a context information creation request sent by the first CU after the terminal accesses the first CU and establishes the network context information according to the request of the core network, wherein the context information creation request includes the network context information; or The processor of the first network function entity is used to receive a context information update request sent by the first CU after the terminal establishes a PDU session and updates the network context information, wherein the context information update request includes the updated network context information; or The processor of the first network function entity is used to receive a context information synchronization request sent by the second network function entity after the second DU updates the network context information in the second network function entity, and the context information synchronization request includes the updated network context information.

33. The network function entity according to claim 32, characterized in that: The performing of the data service on the network context information based on the terminal identifier includes at least one of the following: The processor of the first network function entity is used to store the network context information included in the context information creation request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or The processor of the first network function entity is used to update the currently stored network context information with the updated network context information included in the context information update request according to the terminal identifier, and send a context information synchronization request to the second network function entity; or The processor of the first network function entity is used to synchronize the currently stored network context information with the updated network context information included in the context information synchronization request according to the terminal identifier.

34. The network function entity according to claim 33, characterized in that: The performing of the event service on the network context information based on the terminal identification further includes: The processor of the second network function entity is used to receive a notification event triggered by the first network function entity after creating or updating the network context information, and send a notification to the first DU, where the notification is used to instruct the first DU to perform subsequent processing according to the network context information; or The processor of the first network function entity is used to receive a notification event triggered by the second network function entity after updating the context information, and send a notification to the first CU, where the notification is used to instruct the first CU to perform subsequent processing according to the network context information.

35. The network function entity according to claim 34, characterized in that: The performing of the data service on the network context information based on the terminal identification further includes at least one of the following: The processor of the second network function entity is used to receive a context information query request sent by the first DU according to the notification, and send the network context information to the first DU; or The processor of the second network function entity is used to receive a context information update request sent by the first DU after performing subsequent processing according to the network context information and updating the network context information, wherein the context information update request includes the updated network context information; The updated network context information is stored according to the terminal identifier, and a context information synchronization request is sent to the first network function entity.

36. The network function entity according to claim 24, characterized in that: The network context information includes status information required by any access network element to maintain the terminal connection status and provide services for the terminal, and the status information includes one or more of the following: status information reported by the terminal, status information configured, generated, or saved by any access network element.

37. An access network element, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Create or update network context information; Sending the network context information to the network function entity; The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

38. The access network element according to claim 37, characterized in that: When sending the network context information to the network function entity, the processor is configured to: After establishing the network context information, sending a context information creation request to the network function entity, wherein the context information creation request includes the network context information; or After updating the network context information, sending a context information update request to the network function entity, wherein the context information update request includes the updated network context information; or If the network function entity is distributedly deployed in multiple access network elements, then for any first access network element, the first network function entity in the first access network element is controlled to send a context information synchronization request to the second network function entity deployed in the second access network element, and the context information synchronization request includes the network context information.

39. The access network element according to claim 38, characterized in that: The processor is further configured to: Requesting a data service about the network context information from the network function entity based on the terminal identifier, the data service comprising at least one of the following: storage, query, update and deletion of the network context information; and / or Control the network function entity to perform an event service on the network context information, wherein the event service includes at least one of the following: subscription and unsubscription with network function entities deployed in other access network elements.

40. The access network element according to claim 39, characterized in that: When the processor requests the data service about the network context information from the network function entity based on the terminal identifier, the processor is configured to perform at least one of the following: Sending a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; receiving the network context information sent by the network function entity after querying according to the terminal identifier; or After detecting that the terminal leaves the network or is shut down and offline, a context information deletion request is sent to the network function entity, so that the network function entity deletes the network context information corresponding to the terminal according to the context information deletion request.

41. The access network element according to claim 39, characterized in that: When controlling the network function entity to perform an event service on the network context information, the processor is configured to: If it is determined that the first access network network element and the second access network network element collaborate to serve the terminal, the first access network network element controls the first network function entity in the first access network network element and the second network function entity in the second access network network element to subscribe to each other, so that the first access network network element receives the notification sent by the first network function entity after the second network function entity creates or updates network context information and triggers a notification event; or If it is determined that the first access network element and the second access network element stop collaborating to serve the terminal, the processor of the first access network element is used to control the first network function entity in the first access network element and the second network function entity in the second access network element to cancel mutual subscription.

42. The access network element according to any one of claims 37 to 41, characterized in that: The access network element is a CU in the access network, and the network function entity is connected to multiple CUs; ​​accordingly, the creating or updating the network context information and sending the network context information to the network function entity includes: After the terminal accesses the first CU and registers, the processor of the first CU is used to establish the network context information according to the request of the core network, and send a context information creation request to the network function entity, where the context information creation request includes the network context information; or After the terminal establishes a protocol data unit PDU session, the processor of the first CU is used to update the network context information and send a context information update request to the network function entity, where the context information update request includes the updated network context information; or When the terminal is in an inactive state and a switch occurs from the first CU to the second CU, the processor of the second CU is used to update the network context information while keeping the terminal in an inactive state, and send a context information update request to the network function entity, wherein the context information update request includes the updated network context information.

43. The access network element according to any one of claims 37 to 41, characterized in that: The requesting the network function entity for a data service regarding the network context information based on the terminal identifier includes at least one of the following: After the terminal moves and switches from the first CU to the second CU, the processor of the second CU is used to send a context information query request to the network function entity, where the context information query request includes a terminal identifier; the processor of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or When the terminal is converted from an inactive state to a connected state, the processor of the first CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor of the first CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier; or When the terminal is converted from an inactive state to a connected state, the processor of the second CU is used to send a context information query request to the network function entity, wherein the context information query request includes a terminal identifier; the processor of the second CU is also used to receive the network context information sent by the network function entity after querying according to the terminal identifier.

44. The access network element according to any one of claims 37 to 41, characterized in that: The access network element is a CU or a DU, and the network function entity is distributedly deployed in at least one CU and multiple DUs of the access network; accordingly, controlling the network function entity to perform an event service on the network context information includes: After the terminal accesses the first CU through the first transmitting and receiving point TRP under the first DU and registers, the processor of the first CU or the processor of the first DU is used to determine that the first CU and the first DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity in the first CU and the second network function entity in the first DU; or After the terminal moves and the first transmitting and receiving point TRP under the first DU is switched to the second transmitting and receiving point TRP shared by the first DU and the second DU, the processor of the first CU, the processor of the first DU or the processor of the second DU is used to determine that the first CU, the first DU and the second DU cooperate to serve the terminal, and control the mutual subscription of the first network function entity, the second network function entity, and the third network function entity in the second DU; or After the terminal moves and the first sending and receiving point TRP under the first DU switches to the third sending and receiving point TRP under the second DU, the processor of the first CU is used to determine that the first CU and the second DU cooperate to serve the terminal, control the mutual subscription between the first network function entity and the third network function entity in the second DU, and control the cancellation of the mutual subscription between the first network function entity and the second network function entity.

45. The access network element according to claim 44, characterized in that: In a case where a first network function entity in the first CU and a second network function entity in the first DU subscribe to each other, the creating or updating network context information and sending the network context information to the network function entity includes: After the terminal accesses the first CU and establishes the network context information according to the request of the core network, the processor of the first CU is used to send a context information creation request to the first network function entity, where the context information creation request includes the network context information; or After the terminal establishes a PDU session and updates the network context information, the processor of the first CU is used to send a context information update request to the first network function entity, where the context information update request includes the updated network context information; or The processor of the first CU is used to control the first network function entity to send a context information synchronization request to the second network function entity.

46. ​​The access network element according to claim 45, characterized in that: After the second network function entity receives a notification event triggered by the first network function entity after creating or updating network context information, the processor of the first DU is used to receive a notification sent by the second network function entity, and send a context information query request to the second network function entity according to the notification, so as to obtain the network context information for subsequent processing and update the network context information; or When the first network function entity receives a notification event triggered by the second network function entity after updating context information, the processor of the first CU is used to receive the notification sent by the first network function entity, and send a context information query request to the first network function entity according to the notification, so as to obtain the network context information for subsequent processing.

47. An access network information management device, characterized in that: Applied to a network function entity, the device comprises: A receiving unit, configured to obtain network context information created or updated by any access network element; a processing unit, configured to identify the network context information according to the terminal identifier, and store and / or manage the network context information based on the terminal identifier; The network function entity is connected to a plurality of access network elements and / or is distributedly deployed in a plurality of access network elements.

48. An access network information management device, characterized in that: Applied to access network elements, the device includes: A processing unit, configured to create or update network context information; A sending unit, configured to send the network context information to the network function entity; The access network element is connected to a network function entity, and / or the network function entity is deployed in the access network element.

49. An access network information management system, characterized in that: comprising a network function entity as described in any one of claims 24 to 36 and an access network element as described in any one of claims 37 to 46; The network function entity is connected to a plurality of access network elements, and / or the network function entity is distributedly deployed in a plurality of access network elements.

50. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method according to any one of claims 1 to 23.

Images