CN113260015B - Task processing method and access and mobility management functional entity - Google Patents
Task processing method and access and mobility management functional entity Download PDFInfo
- Publication number
- CN113260015B CN113260015B CN202110512831.7A CN202110512831A CN113260015B CN 113260015 B CN113260015 B CN 113260015B CN 202110512831 A CN202110512831 A CN 202110512831A CN 113260015 B CN113260015 B CN 113260015B
- Authority
- CN
- China
- Prior art keywords
- task
- amf
- context parameter
- category
- processing request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present disclosure provides a task processing method and an access and mobility management function entity, wherein the method comprises the following steps: determining a first task category of a current processing task of an AMF (advanced mobile switching) entity of a first access and mobility management function, and determining a second task category corresponding to a task to be processed and the current processing task of the first AMF, wherein the task to be processed and the current processing task are tasks of terminal UE (user equipment) currently served by the first AMF; determining a first context parameter of UE corresponding to a third task category except the first task category in the second task category; sending the UE first context parameter to a second AMF; and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF. Before the first AMF completes all the in-process task processing, the second AMF receives the UE first context parameter sent by the first AMF, and the second AMF can execute the task processing request sent by the CPNF under the condition that the second AMF does not influence the original task processing.
Description
Technical Field
The disclosure belongs to the technical field of communication, and particularly relates to a task processing method and an access and mobility management functional entity.
Background
In the 5G network, in order to achieve scalability of the network, the original AMF (Access and Mobility Management Function) is allowed to stop or quit the service in a planned manner, and other AMFs replace the network service assumed by the original AMF. And under the condition that the backup AMF is specified in advance, the backup AMF replaces the original AMF which is scheduled to stop to continue providing the service. However, the original AMF scheduled to stop will not hand over the context parameters of the UE (User Equipment) managed by the original AMF to the backup AMF until the tasks that are not completed currently are all completed. At this time, if a certain CPNF (Control Plane Network Function) initiates a task processing request to the backup AMF at this time, since the backup AMF does not obtain the UE context parameter yet, the task processing request of the CPNF can only be rejected, and the original AMF is notified that the original AMF only supports the task processing that is not completed yet. The problem with this is that the original AMF only handles tasks that have not yet been completed, but does not know when all can be completed; before the original AMF completes all the ongoing task processing, the backup AMF can only reject the task requests of all CPNFs because there is no UE context parameter.
Meanwhile, the backup AMF sets a timer, and before the timer is cleared, the backup AMF is not used as the backup AMF to replace the original AMF to undertake any task processing request; and after the timer is cleared, the task processing of the original AMF is started to be taken as the backup AMF. The problems that result from this are: before the timer is cleared, because the original AMF only processes the incomplete task operation and the backup AMF does not accept any task processing request, the CPNF cannot initiate a new task processing request even if the initiated task processing request is unrelated to the ongoing task request of the original AMF.
Disclosure of Invention
In view of the above-mentioned shortcomings in the prior art, the present disclosure provides a task processing method and an access and mobility management functional entity.
As a first aspect of the present disclosure, there is provided a task processing method including:
determining a first task type of a current processing task of an AMF (advanced mobile switching function) entity of a first access and mobility management function, and determining a to-be-processed task of the first AMF and a second task type corresponding to the current processing task, wherein the to-be-processed task and the current processing task are tasks of terminal UE (user equipment) currently served by the first AMF;
determining a first context parameter of UE corresponding to a third task category except the first task category in the second task category;
sending the UE first context parameter to a second AMF;
and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF.
Preferably, there is a correlation between tasks in the same task category.
Preferably, after determining the first task class of the current processing task of the AMF, the method further includes:
determining UE second context parameters of other tasks except the current processing task in the first task category;
and sending the UE second context parameter to a second AMF.
Preferably, the method further comprises:
determining a first application identifier corresponding to other tasks except the current processing task in a first task category;
and sending the first application identification to the second AMF.
Preferably, the method further comprises:
in the event that the current processing task is complete, other tasks in the first task class are processed until all tasks in the first task class are processed.
As a second aspect of the present disclosure, there is provided a task processing method including:
receiving a first context parameter of the UE sent by a first AMF;
responding to a received task processing request sent by a CPNF (Central processing Unit), and determining a UE third context parameter corresponding to the task processing request according to the UE first context parameter, wherein the task processing request is sent by the CPNF according to an identifier of a second AMF in a service stopping message after the CPNF receives the service stopping message sent by a first AMF;
and executing the task processing request according to the UE third context parameter.
Preferably, before the executing the task processing request according to the third context parameter of the UE, the method further includes:
receiving a second context parameter of the UE sent by the first AMF;
the executing the task processing request according to the UE third context parameter includes:
and executing the task processing request according to the third context parameter of the UE under the condition that the task type corresponding to the task processing request is determined not to be the first task type at least according to the third context parameter of the UE and the second context parameter of the UE.
Preferably, the determining that the task category corresponding to the task processing request is not the first task category according to at least the third context parameter of the UE and the second context parameter of the UE includes:
and under the condition that the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task type corresponding to the task processing request is not the first task type.
Preferably, before the executing the task processing request according to the third context parameter of the UE, the method further includes:
receiving a first application identifier sent by a first AMF;
acquiring a second application identifier corresponding to the task processing request through the CPNF;
the determining that the task category corresponding to the task processing request is not the first task category according to at least the third context parameter of the UE and the second context parameter of the UE includes:
and under the condition that the first application identifier is determined to be inconsistent with the second application identifier and the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task category corresponding to the task processing request is not the first task category.
As a third aspect of the present disclosure, there is provided an access and mobility management functional entity, including:
a first determining module, configured to determine a first task category of a current processing task of the first access and mobility management functional entity AMF;
a second determining module, configured to determine a second task category corresponding to a to-be-processed task and a current processing task of the first AMF, where the to-be-processed task and the current processing task are tasks of a terminal UE currently served by the first AMF;
a third determining module, configured to determine a first context parameter of the UE corresponding to a third task category except the first task category in the second task category;
a sending module, configured to send the UE first context parameter to a second AMF; and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF.
As a fourth aspect of the present disclosure, there is provided an access and mobility management functional entity, including:
a receiving module, configured to receive a UE first context parameter sent by a first AMF;
a determining module, configured to determine, in response to receiving a task processing request sent by a CPNF, a third context parameter of the UE corresponding to the task processing request according to the first context parameter of the UE, where the task processing request is sent by the CPNF according to an identifier of a second AMF in a service stopping message after receiving the service stopping message sent by the first AMF;
and the execution module is used for executing the task processing request according to the third context parameter of the UE.
In the embodiment of the present disclosure, before the first AMF completes all ongoing task processing, the second AMF receives the UE first context parameter sent by the first AMF, and the second AMF may execute the task processing request sent by the CPNF without affecting the original task processing.
Drawings
Fig. 1 is a flowchart of a task processing method on a first AMF side according to an embodiment of the present disclosure;
fig. 2 is another flowchart of a task processing method on the first AMF side according to an embodiment of the present disclosure;
fig. 3 is another flowchart of a task processing method on the first AMF side according to an embodiment of the present disclosure;
fig. 4 is a flowchart of a task processing method on the second AMF side according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a first AMF provided by an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a second AMF according to an embodiment of the present disclosure.
Detailed Description
For a better understanding of the technical aspects of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
The method aims to solve the problems that in the prior art, before an original AMF completes all ongoing task processing, the original AMF only processes incomplete task operation and does not accept any task processing request because no UE context parameter exists and before a timer is cleared. The disclosure provides a task processing method and an access and mobility management functional entity. The following detailed description is made with reference to the accompanying drawings which respectively illustrate embodiments provided by the present disclosure.
Fig. 1 shows a flowchart of a task processing method on a first AMF side according to an embodiment of the present disclosure.
As shown in fig. 1, the task processing method provided by the present embodiment includes the following steps.
Step S101, determining a first task class of the current processing task of the first AMF.
And step S102, determining the to-be-processed task of the first AMF and a second task category corresponding to the current processing task.
Step S103, determining a UE first context parameter corresponding to a third task category except the first task category in the second task category.
Step S104, the UE first context parameter is sent to the second AMF.
Step S105, sending a service stop message to the CPNF.
The task to be processed and the current processing task are tasks of the terminal UE currently served by the first AMF. The out-of-service message includes an identification of the second AMF.
The UE CONTEXT parameter, i.e. UE CONTEXT, is the service profile of the user. A process of interacting with the system for an environment in which the current object is located in the program. Such as a chat interface for WeChat and related requests and transmissions.
AMF, is a common control plane function within the core network. One terminal only has one AMF, and the terminal is responsible for authentication, authorization and subscription check of the user so as to ensure that the user is a legal user; user mobility management, including location registration and temporary identity allocation; when a user initiates a PDU (Packet Data Unit) connection establishment request, selecting a suitable SMF (Session Management Function); forwarding Non-Access Stratum (NAS) signaling between the UE and the SMF; and forwarding Access Stratum (AS) signaling between the base station and the SMF.
The CPNF (e.g., SMF, session Management Function) supports an AMF selection Function to select a backup AMF from the AMF set when an original AMF serving the UE is unavailable.
Before step S101, a task of the UE currently served by the first AMF is classified in advance, where the task of the UE is a task currently performed by the UE, and the task of the UE is divided into a plurality of task categories (second task categories), where each task category has a corresponding classification identifier. In some embodiments, there is a correlation between tasks in the same task category. The tasks with relevance are divided into one class, and the relevance refers to the tasks with the operation results possibly influencing each other, namely, no relevance exists among different task classes. Each classification mark corresponds to at least one task mark, and one task mark corresponds to at least one application mark.
It should be noted that the device for classifying the task of the UE may be the first AMF or the UE. When the UE classifies the UE tasks, the first AMF sends task classification requests to the UE served by the UE, the UE classifies the tasks of the UE after receiving the task classification requests, and then the tasks including the task categories, the classification identifiers, the task identifiers and the application identifiers are sent to the first AMF. When the first AMF classifies the tasks of the UE, the first AMF sends a task obtaining request to the UE, the UE sends the tasks of the UE to the first AMF, and the first AMF classifies the tasks of the UE to generate a task category, a classification identifier, a task identifier and an application identifier. It should be noted that the task of the UE includes the current processing task of the first AMF.
In the embodiment of the present disclosure, the first AMF determines a first task category of a task currently processed by the first AMF and a second task category corresponding to a task of the UE, and determines a third task category except the first task category in the second task category, that is, determines all task categories except the first task category in the second task category. The third task class is not associated with the first task class, i.e. is not affected by each other. And determining a first context parameter of the UE corresponding to the third task category, and sending the first context parameter of the UE to the second AMF. At this time, the first AMF sends the out-of-service message carrying the identifier of the second AMF to the CPNF. The CPNF may send a task processing request to a second AMF corresponding to the identifier of the second AMF after receiving the service stop message, and the second AMF may receive the UE first context parameter sent by the first AMF and may execute the task processing request.
In the embodiment of the present disclosure, before the first AMF completes all ongoing task processing, the second AMF receives the UE first context parameter sent by the first AMF, and the second AMF may execute the task processing request sent by the CPNF without affecting the original task processing.
In a preferred embodiment, the first AMF does not send the out-of-service message directly to the CPNF, but sends the out-of-service message to the CPNF through a relay device (e.g., NRF, network functionality Repository Function).
Fig. 2 shows another flowchart of a task processing method on the first AMF side according to an embodiment of the present disclosure.
In some embodiments, as shown in fig. 2, after determining the first task class of the current processing task of the AMF (i.e. step S101), the method further includes:
step S201, determining UE second context parameters of other tasks in the first task category except the current processing task.
Step S202, the UE second context parameter is sent to the second AMF.
In a preferred embodiment, the UE second context parameter may be set to a wildcard value, and the UE second context parameter set to the wildcard value may be sent to the second AMF. Tasks in the first task class other than the current processing task may be affected by the current processing task.
Note that the "wildcard value" refers to a wildcard character similar to "", or the like. For a string, a wildcard "", denotes a string of arbitrary length. For wildcard "? "indicates an arbitrary character, and a null value is indicated for a wildcard"/0 ".
Fig. 3 shows another flowchart of a task processing method on the first AMF side according to an embodiment of the present disclosure.
In some embodiments, as shown in fig. 3, the method further comprises:
step S301, determining first application identifiers corresponding to other tasks except the current processing task in the first task category.
Step S302, sending the first application identifier to the second AMF.
In a preferred embodiment, a first application identity affecting a second context parameter of the UE may also be determined. The method for determining the application identifier influencing a certain context parameter comprises the following two methods:
determining by direct relationship: the same task identifier corresponds to different application identifiers. And establishing the corresponding relation between different application identifications and context parameters according to the corresponding relation between the same task identification and the context parameters of the UE by combining the local task of the first AMF.
Determining, by an indirect relationship: the application identifiers corresponding to the same task category are indirectly associated with the task identifiers corresponding to the same task category; and establishing the indirect corresponding relation between the application identifier and the context parameter by combining the corresponding relation between the same local task category of the first AMF and the context parameter of the UE.
In the embodiment of the present disclosure, the sending of the UE second context parameter and the first application identifier to the second AMF is to determine whether the second AMF can execute a task processing request sent by the CPNF.
In some embodiments, the method further comprises: in the event that the current processing task is complete, other tasks in the first task category are processed until all tasks in the first task category are processed.
In this step, after all tasks in the first task class in the first AMF are processed, the UE first context parameter is updated, and the updated UE first context parameter is sent to the second AMF. And the second AMF executes the task processing request sent by the CPNF according to the updated UE first context parameter.
All the steps are repeatedly executed until all the ongoing tasks on all the AMFs are processed.
Fig. 4 shows a flowchart of a task processing method on the second AMF side according to an embodiment of the present disclosure.
As shown in fig. 4, the task processing method provided by the present embodiment includes the following steps.
Step S401, receives the UE first context parameter sent by the first AMF.
Step S402, responding to the received task processing request sent by the CPNF, and determining a UE third context parameter corresponding to the task processing request according to the UE first context parameter.
Step S403, executing the task processing request according to the UE third context parameter.
The task processing request is sent by the CPNF according to the identifier of the second AMF in the out-of-service message after receiving the out-of-service message sent by the first AMF.
In steps S401 to S403, the UE third context parameter required to be used by the task processing request may be determined, and if the UE first context parameter sent by the first AMF includes the UE third context parameter, the task processing request is executed according to the UE third context parameter.
For example, the task processing request received by the second AMF and sent by the CPNF is a database update task related to the WeChat. And the second AMF receives the first context parameter of the UE sent by the first AMF, and finds out a third context parameter of the UE corresponding to the database updating task related to the WeChat from the first context parameter of the UE, namely finds out a chat interface of the WeChat and related request and transmission data. And the second AMF executes the database updating task related to the WeChat according to the chat interface of the WeChat and the related request and transmission data.
In the embodiment of the present disclosure, before the first AMF completes all ongoing task processing, the second AMF receives the UE first context parameter sent by the first AMF, and the second AMF may execute the task processing request sent by the CPNF without affecting the original task processing.
In some embodiments, before executing the task processing request according to the third context parameter of the UE (i.e. step S403), the method further includes: and receiving the UE second context parameters sent by the first AMF.
The task processing request is executed according to the UE third context parameter (i.e., step S403), including: and executing the task processing request according to the third context parameter of the UE under the condition that the task type corresponding to the task processing request is determined not to be the first task type at least according to the third context parameter of the UE and the second context parameter of the UE.
In steps S401 to S403, the first task class is a task class to which the first AMF currently processes the task. Before executing the task processing request according to the third context parameter of the UE, determining whether a task class corresponding to the task processing request is a task class other than the first task class according to the second context parameter of the UE, if so, determining that the task processing request is not associated with the first task class, the current processing task of the first AMF is not related to the task processing request, and the second AMF may execute the task processing request; if not, the task processing request is determined to belong to the first task class, the current processing task of the first AMF and the task processing request are mutually influenced, and the second AMF does not need to execute the task processing request.
In some embodiments, in step S403, determining that the task category corresponding to the task processing request is not the first task category according to at least the UE third context parameter and the UE second context parameter includes: and under the condition that the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task type corresponding to the task processing request is not the first task type.
In this step, the UE second context parameter corresponds to other tasks in the first task class except the first AMF current processing task, that is, if the UE third context parameter used by the task processing request is not consistent with the UE second context parameter, the task processing request may not be the first AMF current processing task, which indicates that the task class corresponding to the task processing request is not the first task class.
In a preferred embodiment, the UE second context parameter is preset to a wildcard value, and if the task processing request does not use the UE second context parameter set to the wildcard value, it is determined that the task class corresponding to the task processing request is not the first task class.
In some embodiments, before the performing the task processing request according to the UE third context parameter (i.e. step S403), the method further includes: receiving a first application identifier sent by a first AMF; and acquiring a second application identifier corresponding to the task processing request through the CPNF.
In the above steps, the first application identifier corresponds to other tasks except the current processing task in the first task class, and the second AMF obtains the second application identifier corresponding to the task processing request through the CPNF. Of course, the second AMF may also obtain, through another device (for example, the first AMF or a terminal served by the first AMF), the second application identifier corresponding to the task processing request. One task corresponds to at least one application identification.
Correspondingly, in step S403, determining that the task category corresponding to the task processing request is not the first task category according to at least the third context parameter of the UE and the second context parameter of the UE, includes: and under the condition that the first application identifier is determined to be inconsistent with the second application identifier and the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task category corresponding to the task processing request is not the first task category.
In this step, it may be determined whether the task category corresponding to the task processing request is the first task category by determining whether the first application identifier is consistent with the second application identifier. Because one task may correspond to multiple application identifiers, the first application identifier or the second application identifier may not be fully acquired, so that the first application identifier and the second application identifier are inconsistent, and at this time, it cannot be accurately determined whether the task category corresponding to the task processing request is the first task category. Therefore, when it is determined that the first application identifier is inconsistent with the second application identifier, it is further determined whether a third context parameter of the UE used by the task processing request is consistent with the second context parameter of the UE. If the first application identifier is not consistent with the second application identifier, and the third context parameter of the UE is not consistent with the second context parameter of the UE, the task processing request may not be the current processing task of the first AMF, which indicates that the task category corresponding to the task processing request is not the first task category.
In a preferred embodiment, the UE second context parameter is preset to a wildcard value, and if the first application identifier is inconsistent with the second application identifier and the task processing request does not use the UE second context parameter set to the wildcard value, it is determined that the task class corresponding to the task processing request is not the first task class.
Fig. 5 shows a schematic structural diagram of a first AMF provided by an embodiment of the present disclosure. Based on the same technical concept as the embodiment corresponding to fig. 1, as shown in fig. 5, the first AMF provided by the embodiment of the present disclosure includes the following modules.
A first determining module 11, configured to determine a first task class of a current processing task of the first access and mobility management functional entity AMF;
a second determining module 12, configured to determine a second task type corresponding to a to-be-processed task and a current processing task of the first AMF, where the to-be-processed task and the current processing task are tasks of a terminal UE currently served by the first AMF;
a third determining module 13, configured to determine a first context parameter of the UE corresponding to a third task category except the first task category in the second task category;
a sending module 14, configured to send the UE first context parameter to a second AMF; and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF.
In some embodiments, the first AMF further comprises:
and the fourth determining module is used for determining the UE second context parameters of other tasks except the current processing task in the first task category.
The sending module 14 is further configured to send the UE second context parameter to the second AMF.
In a preferred embodiment, the UE second context parameter may be set to a wildcard value, and the UE second context parameter set to the wildcard value may be sent to the second AMF.
In some embodiments, the first AMF further comprises:
and the fifth determining module is used for determining the first application identifier corresponding to other tasks except the current processing task in the first task category.
The sending module 14 is further configured to send the first application identifier to the second AMF.
In some embodiments, the first AMF further comprises:
and the processing module is used for processing other tasks in the first task class under the condition that the current processing task is completed until all the tasks in the first task class are processed and completed.
Fig. 6 shows a schematic structural diagram of a second AMF provided by an embodiment of the present disclosure. Based on the same technical concept as the embodiment corresponding to fig. 4, as shown in fig. 6, the second AMF provided by the embodiment of the present disclosure includes the following modules.
A receiving module 21, configured to receive a UE first context parameter sent by the first AMF;
a determining module 22, configured to determine, in response to receiving a task processing request sent by a CPNF, a third context parameter of the UE corresponding to the task processing request according to the first context parameter of the UE, where the task processing request is sent by the CPNF according to an identifier of a second AMF in a service stopping message after receiving the service stopping message sent by the first AMF;
an executing module 23, configured to execute the task processing request according to the UE third context parameter.
In some embodiments, the receiving module 21 is further configured to receive the UE second context parameter sent by the first AMF;
the execution module 23 is specifically configured to:
and executing the task processing request according to the third context parameter of the UE under the condition that the task type corresponding to the task processing request is determined not to be the first task type at least according to the third context parameter of the UE and the second context parameter of the UE.
In some embodiments, in the execution module 23, it is determined that the task category corresponding to the task processing request is not the first task category at least according to the UE third context parameter and the UE second context parameter, and specifically configured to:
and under the condition that the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task type corresponding to the task processing request is not the first task type.
In some embodiments, the receiving module 21 is further configured to receive the first application identifier sent by the first AMF;
the second AMF further comprises:
the acquisition module is used for acquiring a second application identifier corresponding to the task processing request through the CPNF;
in the executing module 23, it is determined that the task category corresponding to the task processing request is not the first task category at least according to the UE third context parameter and the UE second context parameter, and the determining step is specifically configured to:
and under the condition that the first application identifier is determined to be inconsistent with the second application identifier and the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task category corresponding to the task processing request is not the first task category.
It will be understood that the above embodiments are merely exemplary embodiments employed to illustrate the principles of the present disclosure, and the present disclosure is not limited thereto. It will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the disclosure, and these are to be considered as the scope of the disclosure.
Claims (10)
1. A method for processing a task, comprising:
determining a first task category of a current processing task of an AMF (advanced mobile switching) of a first access and mobility management functional entity, and determining a to-be-processed task of the first AMF and a second task category corresponding to the current processing task, wherein the to-be-processed task and the current processing task are tasks of terminal UE (user equipment) currently served by the first AMF;
determining a first context parameter of UE corresponding to a third task category except the first task category in the second task category;
sending the UE first context parameter to a second AMF;
and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF.
2. The method according to claim 1, wherein there is a correlation between tasks in the same task category.
3. The method according to claim 1, further comprising, after determining the first task class of the current AMF processing task:
determining UE second context parameters of other tasks except the current processing task in the first task category;
and sending the UE second context parameter to the second AMF.
4. The task processing method according to claim 1, further comprising:
determining a first application identifier corresponding to other tasks except the current processing task in a first task category;
and sending the first application identification to the second AMF.
5. The task processing method according to any one of claims 1 to 4, characterized in that the method further comprises:
in the event that the current processing task is complete, other tasks in the first task class are processed until all tasks in the first task class are processed.
6. A task processing method, comprising:
receiving a first context parameter of a terminal UE and a second context parameter of the UE which are sent by a first access and mobility management functional entity AMF;
responding to a received task processing request sent by a control plane network function entity (CPNF), and determining a third context parameter of UE corresponding to the task processing request according to the first context parameter of the UE, wherein the task processing request is sent by the CPNF according to an identifier of a second AMF in a service stopping message after the CPNF receives the service stopping message sent by a first AMF;
and executing the task processing request according to the third context parameter of the UE under the condition that the task type corresponding to the task processing request is determined not to be the first task type at least according to the third context parameter of the UE and the second context parameter of the UE, wherein the first task type is the task type of the current processing task of the first AMF.
7. The task processing method according to claim 6, wherein the determining, according to at least the UE third context parameter and the UE second context parameter, that the task category corresponding to the task processing request is not the first task category comprises:
and under the condition that the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task type corresponding to the task processing request is not the first task type.
8. The task processing method according to claim 6, wherein before the executing the task processing request according to the UE third context parameter, the task processing method further comprises:
receiving a first application identifier sent by a first AMF;
acquiring a second application identifier corresponding to the task processing request through the CPNF;
the determining that the task category corresponding to the task processing request is not the first task category according to at least the third context parameter of the UE and the second context parameter of the UE includes:
and under the condition that the first application identifier is determined to be inconsistent with the second application identifier and the third context parameter of the UE is determined to be inconsistent with the second context parameter of the UE, determining that the task category corresponding to the task processing request is not the first task category.
9. An access and mobility management function entity, comprising:
a first determining module, configured to determine a first task class of a current processing task of the first access and mobility management function entity AMF;
a second determining module, configured to determine a second task category corresponding to a to-be-processed task and a current processing task of the first AMF, where the to-be-processed task and the current processing task are tasks of a terminal UE currently served by the first AMF;
a third determining module, configured to determine a first context parameter of the UE corresponding to a third task category, which is different from the first task category, in the second task category;
a sending module, configured to send the UE first context parameter to a second AMF; and sending a service stopping message to a control plane network function entity (CPNF), wherein the service stopping message comprises the identifier of the second AMF.
10. An access and mobility management function entity, comprising:
a receiving module, configured to receive a first context parameter of the UE and a second context parameter of the UE sent by the first AMF;
a determining module, configured to determine, in response to receiving a task processing request sent by a CPNF, a third context parameter of the UE corresponding to the task processing request according to the first context parameter of the UE, where the task processing request is sent by the CPNF according to an identifier of a second AMF in a service stopping message after receiving the service stopping message sent by the first AMF;
and an execution module, configured to execute the task processing request according to the UE third context parameter when it is determined that the task category corresponding to the task processing request is not the first task category according to at least the UE third context parameter and the UE second context parameter, where the first task category is a task category of the first AMF currently processing task.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110512831.7A CN113260015B (en) | 2021-05-11 | 2021-05-11 | Task processing method and access and mobility management functional entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110512831.7A CN113260015B (en) | 2021-05-11 | 2021-05-11 | Task processing method and access and mobility management functional entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113260015A CN113260015A (en) | 2021-08-13 |
| CN113260015B true CN113260015B (en) | 2022-11-18 |
Family
ID=77222782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110512831.7A Active CN113260015B (en) | 2021-05-11 | 2021-05-11 | Task processing method and access and mobility management functional entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113260015B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101128046A (en) * | 2006-08-16 | 2008-02-20 | 华为技术有限公司 | Method for obtaining access system context |
| CN103430580A (en) * | 2011-01-21 | 2013-12-04 | 黑莓有限公司 | Network apparatus and process to determine connection context for connections used for (local) offloading |
| WO2020070371A1 (en) * | 2018-10-04 | 2020-04-09 | Nokia Technologies Oy | Method and apparatus for security context handling during inter-system change |
| CN112020067A (en) * | 2019-05-31 | 2020-12-01 | 华为技术有限公司 | Method, device and communication system for acquiring security context |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111770539B (en) * | 2019-04-02 | 2021-07-09 | 大唐移动通信设备有限公司 | LMF (local mean function) selection method, terminal positioning service method and device |
-
2021
- 2021-05-11 CN CN202110512831.7A patent/CN113260015B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101128046A (en) * | 2006-08-16 | 2008-02-20 | 华为技术有限公司 | Method for obtaining access system context |
| CN103430580A (en) * | 2011-01-21 | 2013-12-04 | 黑莓有限公司 | Network apparatus and process to determine connection context for connections used for (local) offloading |
| WO2020070371A1 (en) * | 2018-10-04 | 2020-04-09 | Nokia Technologies Oy | Method and apparatus for security context handling during inter-system change |
| CN112020067A (en) * | 2019-05-31 | 2020-12-01 | 华为技术有限公司 | Method, device and communication system for acquiring security context |
Non-Patent Citations (1)
| Title |
|---|
| S2-2103827 "NSAC procedure update because of UE mobility with AMF change";Samsung;《3GPP tsg_sa\wg2_arch》;20210507;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113260015A (en) | 2021-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111083737B (en) | Method and device for shunting data in edge MEC | |
| CN109151906B (en) | Communication method, network equipment, terminal equipment and system | |
| JP6382289B2 (en) | Communication support method and apparatus using non-access layer protocol in mobile communication system | |
| CN106060900A (en) | Method and apparatus for controlling access to network slicing, terminal small cell and SDN controller | |
| CN102316416B (en) | Terminal access method and cordless communication network | |
| CN105722090A (en) | Control method and device for automatically identifying pseudo base station | |
| CN114615023A (en) | Communication method and related device | |
| JP2005168033A (en) | Method and system for automatic setting of device in communications network | |
| CN114567880B (en) | Communication method, system and computer readable storage medium | |
| CN103686718A (en) | D2D (Device-to-Device) device identification label processing method and D2D device identification label processing device | |
| CN111757424B (en) | Sharing method and device of wireless access network | |
| EP2555545A1 (en) | Method and system for selecting mobility management entity of terminal group | |
| JP2022531061A (en) | How to handle communication network components and service requests | |
| CN113453252B (en) | Communication method and device | |
| CN111182542B (en) | Method, system, base station and readable storage medium for establishing proximity service | |
| CN108712743B (en) | Method and system for managing wireless networking of device groups | |
| CN109804706B (en) | Method and radio access network component for setting up a connection of a mobile terminal to a mobile radio communications network | |
| CN113260015B (en) | Task processing method and access and mobility management functional entity | |
| CN117615379A (en) | Connection establishment method, system, terminal and computer readable storage medium | |
| US20220417834A1 (en) | Communication method, system, base station, and terminal | |
| JP2018174404A (en) | Communication control apparatus, communication control method, and program | |
| CN114389943A (en) | Network configuration method, device, equipment and computer storage medium | |
| CN113965976B (en) | Network service method, device, system and storage medium | |
| CN110876148B (en) | Processing method and device for wireless capability matching, core network equipment and base station | |
| CN114071573B (en) | Session control method, apparatus, system and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |