CN113163472B - AMF selection method and device - Google Patents
AMF selection method and device Download PDFInfo
- Publication number
- CN113163472B CN113163472B CN202110511796.7A CN202110511796A CN113163472B CN 113163472 B CN113163472 B CN 113163472B CN 202110511796 A CN202110511796 A CN 202110511796A CN 113163472 B CN113163472 B CN 113163472B
- Authority
- CN
- China
- Prior art keywords
- entity
- identifier
- access
- control plane
- mobility management
- 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
- 238000010187 selection method Methods 0.000 title claims abstract description 40
- 238000013479 data entry Methods 0.000 claims abstract description 109
- 230000011664 signaling Effects 0.000 abstract description 18
- 206010048669 Terminal state Diseases 0.000 abstract description 10
- 238000004891 communication Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 104
- 238000000034 method Methods 0.000 description 19
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
Abstract
The invention discloses an AMF selection method and device, and relates to the technical field of communication. The scheme comprises the following steps: receiving an entity query request sent by a first control plane network functional entity, judging whether to store data items meeting matching conditions, in the case where it is determined that the data entry satisfying the matching condition is stored, acquiring a second entity identification from the data entry satisfying the matching condition, generating an entity query result based on the second entity identification, and sending the entity query result to a first control plane network function entity, the first control plane network function entity establishing a connection with a second access and mobility management function entity based on the second entity identity, under the condition that the backup AMF is not appointed in advance, different control plane network functional entities corresponding to the same terminal are accessed to the same AMF, thereby avoiding the state confusion of the terminal, and further, the control plane network function entity is prevented from interacting with the access network to achieve the signaling overhead caused by the same AMF for providing service for solving the terminal state confusion.
Description
Technical Field
The invention relates to the technical field of communication, in particular to an AMF selection method and device.
Background
In the 5G network, in order to achieve the scalability of the network, Access and Mobility Management Function (AMF) entities are allowed to stop or exit the service in a planned way, and other AMFs are used to replace the stopped or exited AMF to take on the corresponding network service. However, if the backup AMF is not pre-designated, different network functional entities corresponding to the same terminal may select different alternative AMFs, thereby causing additional signaling overhead or confusion of the terminal state, which affects the user experience.
Disclosure of Invention
Therefore, the invention provides an AMF selection method and device, so as to solve the problem that different network function entities corresponding to the same terminal may select different alternative AMFs under the condition that a backup AMF is not specified in advance, thereby requiring extra signaling overhead or causing terminal state confusion.
In order to achieve the above object, a first aspect of the present invention provides an AMF selection method, which can be applied to a specified storage function entity. The method comprises the following steps:
receiving an entity query request sent by a first control plane network functional entity, wherein the first control plane network functional entity is a functional entity providing a control plane service for a terminal, the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing an access service for the terminal and does not designate a backup functional entity;
judging whether a data item meeting the matching condition is stored or not, wherein the data item is a data record which is generated by a storage functional entity according to the received message and is used for storage;
under the condition that the data items meeting the matching conditions are determined to be stored, acquiring a second entity identifier from the data items meeting the matching conditions, wherein the second entity identifier is the identifier of a second access and mobility management functional entity which replaces the first access and mobility management functional entity to provide access service for the terminal;
and generating an entity query result based on the second entity identifier, and sending the entity query result to the first control plane network functional entity so that the first control plane network functional entity establishes connection with the second access and mobility management functional entity based on the second entity identifier.
Further, the matching condition is that an entity identification part of a global identification in the data entry is matched with the first entity identification, a terminal identification part of the global identification in the data entry is matched with the terminal short identification, the service state identification of the data entry is an effective service identification, and the update time of the data entry is closest to the current time.
Further, before the determining whether to store the data entry satisfying the matching condition, the AMF selection method further includes:
receiving a first update message sent by a network function repository function entity, wherein the first update message is a message sent when the network function repository function entity allocates the second access and mobility management function entity for a second control plane network function entity, the second control plane network function entity is a function entity that provides a control plane service for the terminal except for the first control plane network function entity, and the first update message includes the second entity identifier, the global identifier, and the valid service identifier;
generating and storing the data entry corresponding to the first update message based on the first update message.
Further, after determining whether to store the data entry satisfying the matching condition, the AMF selection method further includes:
sending a no match function entity feedback message to the first control plane network function entity if it is determined that no data entry satisfying the match condition is stored.
Further, after sending a no-match function entity feedback message to the first control plane network function entity in the case that it is determined that the data entry satisfying the match condition is not stored, the AMF selection method further includes:
receiving a second update message sent by a network function repository function entity, wherein the second update message is a message sent when the network function repository function entity allocates a third access and mobility management function entity for the first control plane network function entity, the second update message includes a third entity identifier, the global identifier, and the valid service identifier, and the third entity identifier is an identifier of the third access and mobility management function entity;
generating and storing the data entry corresponding to the second update message based on the second update message.
Further, after the generating the data entry corresponding to the second update message based on the second update message, the AMF selection method further includes:
receiving a third update message sent by the third access and mobility management functional entity, where the third update message is a message that is generated and sent when the terminal leaves a service range of the third access and mobility management functional entity, and the third update message includes the first entity identifier, the global identifier, and an invalid service identifier;
generating and storing the data entry corresponding to the third update message based on the third update message.
In order to achieve the above object, a second aspect of the present invention provides an AMF selection method, which can be applied to a control plane network function entity. The method comprises the following steps:
sending an entity query request to a designated storage functional entity, wherein the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing access service for a terminal and does not designate a backup functional entity;
receiving an entity query result returned by the storage function entity, wherein the entity query result is a result returned when the storage function entity stores a data entry meeting a matching condition, the data entry is a data record for storage generated by the storage function entity according to a received message, the entity query result comprises a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity which replaces the first access and mobility management function entity to provide an access service for a terminal;
and establishing connection with the second access and mobility management functional entity according to the second entity identifier.
Further, after sending the entity query request to the specified storage function entity, the AMF selection method further includes:
and receiving a non-matching functional entity feedback message returned by the storage functional entity, wherein the non-matching functional entity feedback message is a message generated and sent under the condition that the storage functional entity does not store the data item meeting the matching condition.
Further, after receiving the feedback message of the non-matching functional entity returned by the storage functional entity, the AMF selection method further includes:
sending an entity allocation request to a network function repository function entity;
receiving an entity allocation result returned by the network function repository function entity, wherein the entity allocation result comprises a third entity identifier, and the third entity identifier is an identifier of a third access and mobility management function entity allocated to the current control plane function entity;
and establishing connection with the third access and mobility management functional entity based on the third entity identification.
In order to achieve the above object, a third aspect of the present invention provides an AMF selection apparatus, which is applicable to a specified storage function entity. The device includes:
a first receiving module, configured to receive an entity query request sent by a first control plane network functional entity, where the first control plane network functional entity is a functional entity that provides a control plane service for a terminal, the entity query request includes a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity that stops providing an access service for the terminal and does not specify a backup functional entity;
the judging module is configured to judge whether to store a data item meeting a matching condition, wherein the data item is a data record which is generated by the storage functional entity according to the received message and is used for storage;
an obtaining module, configured to, in a case that it is determined that the data entry satisfying the matching condition is stored, obtain a second entity identifier from the data entry satisfying the matching condition, where the second entity identifier is an identifier of a second access and mobility management function entity that provides an access service for the terminal in place of the first access and mobility management function entity;
a generation module configured to generate an entity query result based on the second entity identification;
a first sending module configured to send the entity query result to the first control plane network function entity, so that the first control plane network function entity establishes a connection with the second access and mobility management function entity based on the second entity identifier.
In order to achieve the above object, a fourth aspect of the present invention provides an AMF selection apparatus, which is applicable to a control plane network function entity. The device includes:
a second sending module, configured to send an entity query request to a designated storage function entity, where the entity query request includes a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management function entity that stops providing an access service for a terminal and does not designate a backup function entity;
a second receiving module, configured to receive an entity query result returned by the storage function entity, where the entity query result is a result returned when the storage function entity stores a data entry that satisfies a matching condition, the data entry is a data record for storage generated by the storage function entity according to a received message, the entity query result includes a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity that replaces the first access and mobility management function entity to provide an access service for a terminal;
and the connection module is configured to establish connection with the second access and mobility management function entity according to the second entity identifier.
The invention has the following advantages:
the AMF selection method provided by the invention receives an entity query request sent by a first control plane network functional entity, judges whether to store data items meeting matching conditions, acquires a second entity identifier from the data items meeting the matching conditions under the condition of determining to store the data items meeting the matching conditions, generates an entity query result based on the second entity identifier, and sends the entity query result to the first control plane network functional entity, the first control plane network functional entity establishes connection with a second access and mobility management functional entity based on the second entity identifier, and realizes that different control plane network functional entities corresponding to the same terminal access the same AMF under the condition of not appointing backup AMF in advance, thereby avoiding the terminal state confusion caused by the different control plane network functional entities corresponding to the same terminal accessing different AMFs, and further, the control plane network function entity is prevented from interacting with the access network for multiple times to solve the problem of disordered terminal states so as to achieve the signaling overhead caused by the service provided by the same AMF.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention.
Fig. 1 is a flowchart of an AMF selection method according to an embodiment of the present invention;
fig. 2 is a flowchart of an AMF selection method according to a second embodiment of the present invention;
fig. 3 is a flowchart of an AMF selection method according to a third embodiment of the present invention;
fig. 4 is a flowchart of an AMF selection method according to a fourth embodiment of the present invention;
fig. 5 is a flowchart of an AMF selection method according to a fifth embodiment of the present invention;
fig. 6 is a block diagram illustrating an AMF selection apparatus according to a sixth embodiment of the present invention;
fig. 7 is a block diagram illustrating an AMF selection apparatus according to a seventh embodiment of the present invention;
fig. 8 is a block diagram illustrating an AMF selection system according to an eighth embodiment of the present invention;
fig. 9 is a schematic signaling interaction diagram of an AMF selection method according to a ninth embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.
In the 5G network, in order to achieve scalability of the network, a specific network function service entity or network function service instance is allowed to stop or exit service in a planned manner, the network function service entity or network function service instance with the same function replaces the network function service entity or network function service instance with the stopped or exited service to undertake the corresponding network service, and the replacement process is transparent to User Equipment (UE) and does not affect the service experience of the User.
For example, in 3GPP TS23.501, if an Access and Mobility Management Function (AMF) plans to stop service without specifying a backup AMF in advance, a Control Plane Network Function (CPNF) with which a signaling interaction is present will look for a substitute AMF through a Network Function Repository Function (NRF). However, each CPNF corresponding to the same terminal may independently initiate a request for allocating an alternative AMF to the NRF, and the NRF does not guarantee that the CPNFs are allocated the same alternative AMF, so that the same terminal may be served by multiple AMFs at the same time.
In the prior art, if the access network receives the CPNF transaction signaling forwarded by a plurality of different AMFs at the same time, the state of the terminal will be confused. In order to avoid confusion of the terminal state, when the same terminal is served by multiple AMFs at the same time, the access network may reject the transaction signaling of a certain CPNF, and notify the same CPNF to resend the transaction signaling to another AMF (the AMF is a functional entity accepted by the access network), and finally achieve the state that the same AMF serves the terminal. In this process, if a plurality of CPNFs are assigned with different alternative AMFs, the signaling interaction process is complicated, resulting in a large signaling overhead.
A first aspect of the present application provides an AMF selection method, which is applicable to a specified storage function entity. Fig. 1 is a flowchart of an AMF selection method according to an embodiment of the present application. As shown in fig. 1, the method comprises the steps of:
step S101, receiving an entity query request sent by a first control plane network function entity.
The first control plane network functional entity is a functional entity for providing a control plane service for the terminal, the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing an access service for the terminal and does not designate a backup functional entity.
In some embodiments, the first entity Identifier may adopt a Globally Unique AMF Identifier (GUAMI) of the first access and mobility management function entity, and the terminal short Identifier may adopt 5G-TMSI. The 5G-TMSI is a shortened form of the 5G-GUTI, the 5G-GUTI (5G Global Unique temporal Identifier) is a Globally Unique Temporary UE Identifier, and the 5G-TMSI is used for replacing the 5G-GUTI, so that an air interface signaling message can be smaller, and the air interface efficiency is improved.
In some implementations, when a first access and mobility management Function entity providing services to a first control plane Network Function entity stops serving, the first control plane Network Function entity sends an entity query request to a specified storage Function entity (Network Function, NF). The designated Storage Function entity is a pre-designated Function entity with a Storage Function, for example, the designated Storage Function entity includes, but is not limited to, a Unified Data Repository Function entity (UDR) and/or an Unstructured Data Storage Function entity (UDSF) and/or a Network Function registration Function entity (NRF). When the number of the storage functional entities is multiple, the storage functional entities form a storage functional entity Set (NF Set), where each NF may be a specific functional entity or an NF Instance (NF Service Instance). When the NF is an NF instance, each NF instance may contain one or more NF services, thereby constituting an NF Service Set (NF Service Set). Correspondingly, the AMF is similar to the NF, and may be an AMF service function entity or an AMF service instance, which is not limited in this application.
It should be noted that, in the prior art, when the control plane network functional entity cannot connect the access and mobility management function service entity, the control plane network functional entity directly initiates a request for searching for the alternative AMF to the network functional repository functional entity, and does not send an entity query request to a predetermined storage functional entity. Moreover, when the control plane network function entity initiates a request for finding a substitute AMF to the network function repository function entity, only the entity identifier of the AMF which stops service is generally provided, but not the identifier of the terminal, the network function repository function entity allocates the substitute AMF to the control plane network function entity according to the entity identifier of the AMF which stops service, and then the substitute AMF finds the context information of the terminal according to the terminal identifier, thereby providing service for the terminal. Since the network function repository function entity does not refer to the terminal identifier when allocating the alternative AMF for the control plane network function entity, the AMF allocation result of the network function repository function entity has no necessary association with the terminal, thereby possibly causing a situation that one terminal is served by a plurality of AMFs.
Step S102, judging whether the data items meeting the matching conditions are stored.
The data entry is a data record which is generated by the storage function entity according to the received message and is used for storage.
In some embodiments, the matching condition is that the entity identifier portion of the global identifier in the data entry matches the first entity identifier, the terminal identifier portion of the global identifier in the data entry matches the terminal short identifier, the service status identifier of the data entry is a valid service identifier, and the update time of the data entry is closest to the current time. The global identifier may adopt 5G-GUTI, and the service state identifier is used to reflect whether the functional entity corresponding to the data entry is in an effective service state.
Specifically, the storage functional entity judges whether the global identifier 5G-GUTI exists in the stored data entry according to the first entity identifier GU AMI and the terminal short identifier 5G-TMSI in the entity query request, where the global identifier 5G-GUTI satisfies 5G-GUTI > <5G-TMSI >. In the case where it is determined that there is a data entry satisfying 5G-GUTI ═ GUAMI > <5G-TMSI >, it is further determined whether the service state identifier of the data entry is a valid service identifier, so that it is possible to obtain data entries for which one or more service state identifiers are valid service identifiers. When only one data entry with the service state identifier as the effective service identifier exists, directly taking the data entry as the data entry meeting the matching condition; when a plurality of data entries with service status identifications as valid service identifications exist, the data entry with the update time closest to the current time is further selected from the data entries as the data entry meeting the matching condition.
And step S103, acquiring a second entity identifier from the data item meeting the matching condition under the condition that the data item meeting the matching condition is determined to be stored.
The second entity identifier is an identifier of a second access and mobility management functional entity which replaces the first access and mobility management functional entity to provide the terminal with the access service.
The essence of the matched data entry is that after the network function repository functional entity allocates the alternative AMF for the other control plane network functional entity corresponding to the terminal (the other control plane network functional entity refers to any control plane network functional entity corresponding to the terminal except the first control plane network functional entity), the data entry generated by the storage functional entity based on the update message sent by the network function repository functional entity is stored, and the update message includes the entity identifier replacing the AMF, that is, the second entity identifier. Thus, in the event that it is determined that a data entry satisfying the matching condition is stored, the storage function entity may obtain the second entity identification from the data entry satisfying the matching condition.
And step S104, generating an entity query result based on the second entity identifier, and sending the entity query result to the first control plane network functional entity so that the first control plane network functional entity establishes connection with the second access and mobility management functional entity based on the second entity identifier.
In some embodiments, the storage function entity generates an entity query result based on the second entity identification and sends the entity query result to the first control plane network function entity. And the first control plane network functional entity receives the entity query result, acquires a second entity identifier from the entity query result, and establishes connection with the second access and mobility management functional entity based on the second entity identifier.
At this time, the first control plane network function entity and the control plane network function entity corresponding to the data entry satisfying the matching condition (i.e. the control plane network function entity corresponding to the terminal, except the first control plane network function entity, and allocated with the second access and mobility management function entity as the control plane network function entity replacing the AMF) are both accessed to the second access and mobility management function entity. When any control plane network functional entity corresponding to the terminal except the two control plane network functional entities cannot be connected with the first access and mobility management functional entity, the second entity identification is obtained through the storage functional entity, so that the second access and mobility management functional entity is accessed, and the terminal only uses the service of the second access and mobility management functional entity.
In the AMF selection method disclosed in this embodiment, an assigned storage function entity receives an entity query request sent by a first control plane network function entity, determines whether to store a data entry satisfying a matching condition, acquires a second entity identifier from the data entry satisfying the matching condition under the condition that the data entry satisfying the matching condition is determined to be stored, generates an entity query result based on the second entity identifier, and sends the entity query result to the first control plane network function entity, the first control plane network function entity establishes a connection with a second access and mobility management function entity based on the second entity identifier, and realizes that different control plane network function entities corresponding to the same terminal access the same AMF under the condition that a backup AMF is not pre-assigned, thereby avoiding terminal state confusion caused by the access of different control plane network function entities corresponding to the same terminal to different AMFs, and further, the control plane network function entity is prevented from interacting with the access network for multiple times to solve the problem of disordered terminal states so as to achieve the signaling overhead caused by the service provided by the same AMF.
Fig. 2 is a flowchart of an AMF selection method provided in the second embodiment of the present application, where the method is applicable to a specified storage function entity. As shown in fig. 2, the method comprises the steps of:
step S201, receiving a first update message sent by a network function repository function entity.
The first update message is a message sent when the network function repository function entity allocates a second access and mobility management function entity for a second control plane network function entity, the second control plane network function entity is a function entity which provides a control plane service for the terminal except the first control plane network function entity, and the first update message includes a second entity identifier, a global identifier and an effective service identifier.
In some embodiments, a terminal corresponds to multiple control plane network function entities, and in a normal case, these control plane network function entities interact with the same access and mobility management function entity to provide services for the terminal. However, if the access and mobility management functional entities interacting with these control plane network functional entities stop service and do not specify a backup AMF, after the functional entity that sent the entity allocation request to the network function repository functional entity earliest among these control plane network functional entities is allocated with a replacement AMF (in this embodiment, specifically, the second access and mobility management functional entity), the network function repository functional entity generates a first update message according to the second entity identifier, the global identifier, and the valid service identifier, and sends the first update message to the current storage functional entity. The current storage function entity receives a first update message sent by the network function repository function entity.
Step S202, generating and storing a data entry corresponding to the first update message based on the first update message.
In some embodiments, the first update message includes the second entity identification, the global identification, and the valid service identification. The second entity mark represents the mark of the access and mobility management functional entity which successfully establishes connection with the second control plane network functional entity; the global identity may be used to identify the terminal; the valid service identification is used to characterize that the second access and mobility management functional entity is providing an alternative access service for the second control plane network functional entity.
After generating a data entry corresponding to the first update message based on the first update message and storing the data entry, the storage function entity obtains the updated data entry. If an entity query request sent by any control plane network functional entity is received, the storage functional entity judges whether a data item meeting the matching condition exists or not based on the updated data item, so that an accurate entity query result is obtained.
Specifically, when the storage function entity receives an entity query request sent by another control plane network function entity corresponding to the same terminal (i.e., any control plane network function entity corresponding to the terminal except the second control plane network function entity), the data entry corresponding to the first update message stored in the storage function entity is the data entry satisfying the matching condition, and the storage function entity returns the entity query result generated based on the second entity identifier to the control plane network function entities, so that the control plane network function entities are all connected with the second access and mobility management function entity, thereby avoiding that the terminal accesses different AMFs at the same time, and avoiding that the state of the terminal is disordered.
Step S203, receiving an entity query request sent by the first control plane network function entity.
Step S204, judging whether the data items meeting the matching conditions are stored.
In step S205, in the case that it is determined that the data entry satisfying the matching condition is stored, the second entity identifier is acquired from the data entry satisfying the matching condition.
Step S206, generating an entity query result based on the second entity identifier, and sending the entity query result to the first control plane network functional entity, so that the first control plane network functional entity establishes a connection with the second access and mobility management functional entity based on the second entity identifier.
Steps S203 to S206 in this embodiment are the same as steps S101 to S104 in the first embodiment of the present application, and are not described herein again.
Fig. 3 is a flowchart of an AMF selection method provided in the third embodiment of the present application, where the method is applicable to a specified storage function entity. As shown in fig. 3, the method comprises the steps of:
step S301, receiving an entity query request sent by a first control plane network function entity.
Step S302, determining whether to store the data entry satisfying the matching condition.
Steps S301 to S302 in this embodiment are the same as steps S101 to S102 in the first embodiment of the present application, and are not described again here.
Step S303, sending a non-matching functional entity feedback message to the first control plane network functional entity when it is determined that the data entry satisfying the matching condition is not stored.
In some embodiments, the storage function entity returns a no match function entity feedback message to the first control plane network function entity in the event that it is determined that no data entry satisfying the match condition is stored. After receiving the feedback message of the non-matching functional entity, the first control plane network functional entity learns the non-matching access and mobility management functional entity, and therefore, the first control plane network functional entity initiates a process of searching for the replacement AMF.
Step S304, receiving a second update message sent by the network function repository function entity.
The second update message is a message sent when the network function repository function entity allocates a third access and mobility management function entity to the first control plane network function entity, the second update message includes a third entity identifier, a global identifier and an effective service identifier, and the third entity identifier is an identifier of the third access and mobility management function entity.
In some embodiments, the first control plane network function entity sends an entity allocation request to the network function repository function entity after receiving the no match function entity feedback message. After receiving the entity allocation request, the network function repository function entity allocates a third access and mobility management function entity as a substitute AMF for the first control plane network function entity, generates an entity allocation result based on a third entity identifier corresponding to the third access and mobility management function entity, and sends the entity allocation result to the first control plane network function entity. And the first control plane network functional entity receives an entity distribution result returned by the network functional repository functional entity and establishes connection with the third access and mobility management functional entity based on the third entity identification.
And the network function repository function entity also generates a second updating message according to the third entity identifier, the global identifier and the effective service identifier, and sends the second updating message to the current storage function entity. The storage function entity receives a second update message sent by the network function repository function entity.
Step S305 generates and stores a data entry corresponding to the second update message based on the second update message.
In some embodiments, the second update message comprises a third entity identification, a global identification, and a valid service identification. The third entity identification represents the identification of the access and mobility management functional entity distributed by the first control plane network functional entity; the global identity may be used to identify the terminal; the valid service identity is used to characterize that the third access and mobility management functional entity is providing an alternative access service for the first control plane network functional entity.
After generating a data entry corresponding to the second update message based on the second update message and storing the data entry, the storage function entity obtains the updated data entry. If an entity query request sent by any control plane network functional entity is received, the storage functional entity judges whether a data item meeting the matching condition exists or not based on the updated data item, so that an accurate entity query result is obtained.
It should be noted that, if the terminal leaves the service range of the third access and mobility management functional entity, the third access and mobility management functional entity generates a third update message based on the first entity identifier, the global identifier and the invalid service identifier, and sends the third update message to the current storage functional entity. And the current storage functional entity receives the third updating message and generates and stores a data entry corresponding to the third updating message based on the third updating message. After the storage function entity receives the entity query request of other control plane network function entities corresponding to the same terminal again, the third access and mobility management function entity is not allocated to the control plane network function entity any more, so that the terminal is prevented from using the services of multiple AMFs simultaneously.
A second aspect of the present application provides an AMF selection method, which is applicable to a control plane network function entity. Fig. 4 is a flowchart of an AMF selection method according to the fourth embodiment of the present application. As shown in fig. 4, the method includes the steps of:
step S401, sending an entity query request to the designated storage function entity.
The entity query request comprises a first entity identifier and a terminal short identifier, wherein the first entity identifier is the identifier of a first access and mobility management functional entity which stops providing access service for the terminal and does not designate a backup functional entity.
In some embodiments, the first entity identifier may adopt a GUAMI of the first access and mobility management function entity, and the terminal short identifier may adopt 5G-TMSI. The 5G-S-TMSI is a shortened form of the 5G-GUTI, the 5G-GUTI is a globally unique temporary UE identifier, and the 5G-S-TMSI is used for replacing the 5G-GUTI, so that an air interface signaling message can be smaller, and the air interface efficiency is improved.
In some implementations, when a first access and mobility management functional entity providing services to a first control plane network functional entity stops serving, the first control plane network functional entity sends an entity query request to a designated storage functional entity. Wherein the specified storage functional entity is a pre-specified functional entity with a storage function, for example, the specified storage functional entity includes, but is not limited to, UDR and/or UDSF and/or NRF.
Step S402, receiving the entity query result returned by the storage function entity.
The entity query result is a result returned when the storage function entity stores a data entry meeting the matching condition, the data entry is a data record which is generated by the storage function entity according to the received message and is used for storage, the entity query result comprises a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity which replaces the first access and mobility management function entity to provide the access service for the terminal.
In some embodiments, the matching condition is that the entity identifier portion of the global identifier in the data entry matches the first entity identifier, the terminal identifier portion of the global identifier in the data entry matches the terminal short identifier, the service status identifier of the data entry is a valid service identifier, and the update time of the data entry is closest to the current time. The global identifier may adopt 5G-GUTI, and the service state identifier is used to reflect whether the functional entity corresponding to the data entry is in an effective service state.
Step S403, establishing a connection with the second access and mobility management function entity according to the second entity identifier.
The second entity identifier is an identifier of a second access and mobility management functional entity which replaces the first access and mobility management functional entity to provide the terminal with the access service.
The essence of the matched data entry is that after the network function repository functional entity allocates the alternative AMF for the other control plane network functional entity corresponding to the terminal (the other control plane network functional entity refers to any control plane network functional entity corresponding to the terminal except the first control plane network functional entity), the data entry generated by the storage functional entity based on the update message sent by the network function repository functional entity is stored, and the update message includes the entity identifier replacing the AMF, that is, the second entity identifier. Thus, in the event that it is determined that a data entry satisfying the matching condition is stored, the storage function entity may obtain the second entity identification from the data entry satisfying the matching condition.
In some embodiments, the storage function entity generates an entity query result based on the second entity identification and sends the entity query result to the first control plane network function entity. And the first control plane network functional entity receives the entity query result, acquires a second entity identifier from the entity query result, and establishes connection with the second access and mobility management functional entity based on the second entity identifier.
In the AMF selection method provided by this embodiment, the control plane network functional entity sends an entity query request to a designated storage functional entity, receives an entity query result returned by the storage functional entity, and establishes a connection with the second access and mobility management functional entity according to a second entity identifier in the entity query request, and under the condition that a backup AMF is not pre-designated, different control plane network functional entities corresponding to the same terminal access the same AMF, thereby avoiding a terminal state confusion caused by accessing different AMFs by different control plane network functional entities corresponding to the same terminal, and further avoiding a situation that the control plane network functional entity interacts with an access network for multiple times to achieve a signaling overhead caused by providing a service by the same AMF in order to solve the terminal state confusion.
Fig. 5 is a flowchart of an AMF selection method according to a fifth embodiment of the present application. As shown in fig. 5, the method includes the steps of:
step S501, sending an entity query request to a specified storage function entity.
Step S501 in this embodiment is the same as step S401 in the fourth embodiment of the present application, and is not described herein again.
Step S502, receiving feedback information of the non-matching functional entity returned by the storage functional entity.
Wherein the no-match functional entity feedback message is a message generated and transmitted in case that the storage functional entity does not store a data entry satisfying the match condition.
In some embodiments, the storage function entity returns a no match function entity feedback message to the first control plane network function entity in the event that it is determined that no data entry satisfying the match condition is stored. After receiving the feedback message of the non-matching functional entity, the first control plane network functional entity learns the non-matching access and mobility management functional entity, and therefore, the first control plane network functional entity initiates a process of searching for the replacement AMF.
Step S503, sending an entity allocation request to the network function repository function entity.
In some embodiments, the first control plane network function entity sends an entity allocation request to the network function repository function entity after receiving the no match function entity feedback message.
Step S504, receiving the entity distribution result returned by the network function repository function entity.
The entity allocation result comprises a third entity identifier, and the third entity identifier is an identifier of a third access and mobility management functional entity allocated to the current control plane functional entity.
In some embodiments, after receiving the entity allocation request sent by the first control plane network functional entity, the network function repository functional entity allocates a third access and mobility management functional entity to the first control plane network functional entity as a substitute AMF, generates an entity allocation result based on a third entity identifier corresponding to the third access and mobility management functional entity, and sends the entity allocation result to the first control plane network functional entity.
Step S505, based on the third entity identifier, establishing a connection with the third access and mobility management function entity.
In some embodiments, the first control plane network function entity receives an entity allocation result returned by the network function repository function entity, obtains a third entity identifier from the entity allocation result, and establishes a connection with the third access and mobility management function entity based on the third entity identifier.
The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
A third aspect of the present application provides an AMF selection apparatus. Fig. 6 is a block diagram illustrating an AMF selection apparatus 600 according to a sixth embodiment of the present disclosure. As shown in fig. 6, the AMF selection apparatus 600 includes:
a first receiving module 601 configured to receive an entity query request sent by a first control plane network function entity.
The first control plane network functional entity is a functional entity for providing a control plane service for the terminal, the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing an access service for the terminal and does not designate a backup functional entity.
A determining module 602 configured to determine whether to store a data entry satisfying the matching condition.
The data entry is a data record which is generated by the storage function entity according to the received message and is used for storage.
An obtaining module 603 configured to, in a case where it is determined that the data entry satisfying the matching condition is stored, obtain the second entity identifier from the data entry satisfying the matching condition.
The second entity identifier is an identifier of a second access and mobility management functional entity which replaces the first access and mobility management functional entity to provide the terminal with the access service.
A generating module 604 configured to generate an entity query result based on the second entity identification.
A first sending module 605, configured to send the entity query result to the first control plane network function entity, so that the first control plane network function entity establishes a connection with the second access and mobility management function entity based on the second entity identifier.
A fourth aspect of the present application provides an AMF selection apparatus. Fig. 7 is a block diagram illustrating an AMF selection apparatus 700 according to a seventh embodiment of the present disclosure. As shown in fig. 7, the AMF selection apparatus 700 includes:
a second sending module 701 configured to send an entity query request to a specified storage function entity.
The entity query request comprises a first entity identifier and a terminal short identifier, wherein the first entity identifier is the identifier of a first access and mobility management functional entity which stops providing access service for the terminal and does not designate a backup functional entity.
A second receiving module 702 configured to receive the entity query result returned by the storage function entity.
The entity query result is a result returned when the storage function entity stores a data entry meeting the matching condition, the data entry is a data record which is generated by the storage function entity according to the received message and is used for storage, the entity query result comprises a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity which replaces the first access and mobility management function entity to provide the access service for the terminal.
A connection module 703 configured to establish a connection with the second access and mobility management function entity according to the second entity identifier.
A fifth aspect of the present application provides an AMF selection system. Fig. 8 is a block diagram of an AMF selection system according to an eighth embodiment of the present application.
As shown in fig. 8, the system 800 includes: terminal 810, first access and mobility management functional entity 821, second access and mobility management functional entity 822, first control plane network functional entity 831, second control plane network functional entity 832 to nth control plane network functional entity 83n, storage functional entity 840, and network functional repository functional entity 850, n being an integer greater than or equal to 1. The first control plane network function 831, the second control plane network function 832 to the nth control plane network function 83n are all function entities corresponding to the terminal 810.
For the AMF selection method disclosed in the present application, in some embodiments, the first access and mobility management function entity 821 provides a service for the terminal 810, and the first control plane network function entity 831, the second control plane network function entity 832 to the nth control plane network function entity 83n perform signaling interaction with the first access and mobility management function entity 821.
When the first access and mobility management function entity 821 exits the service and does not specify the backup AMF, the first control plane network function entity 831 initiates an entity query request to the specified storage function entity 840. If any of the second to nth control plane network functional entities 832 to 83n has been assigned by network function repository functional entity 850 as a replacement AMF in place of second access and mobility management functional entity 822, storage functional entity 840 has generated a corresponding data entry based on the update message sent by network function repository functional entity 850, and this data entry is the data entry that satisfies the matching condition. Therefore, the storage function entity 840 generates an entity query result based on the identifier of the second access and mobility management function entity 822, and sends the entity query result to the first control plane network function entity 831, and the first control plane network function entity 831 establishes a connection with the second access and mobility management function entity 822 based on the second entity identifier. Similar to the other control plane network functional entities, the first control plane network functional entity 831 to the nth control plane network functional entity 83n are finally all accessed to the second access and mobility management functional entity 822, so that the terminal 810 uniformly uses the services of the second access and mobility management functional entity 822.
Fig. 9 is a schematic signaling interaction diagram of an AMF selection method according to a ninth embodiment of the present application, where the method may be applied to the AMF selection system shown in fig. 8. As shown in fig. 9, the signaling interaction procedure includes:
in step S901, the first access and mobility management function entity 821 exits the service and does not designate a backup AMF.
In step S902, the first control plane network function entity 831 sends an entity query request to the network function repository function entity 850 in case of a connection failure with the first access and mobility management function entity 821.
In step S903, network function repository function 850 forwards the entity query request to the specified storage function 840.
In step S904, the storage function entity 840 receives the entity query request, and determines whether to store the data entry satisfying the matching condition.
At this time, the other control plane network functional entities have not designated the backup AMF, and thus, there is no data entry satisfying the matching condition in the storage functional entity 840.
In step S905, the storing functional entity 840 sends a non-matching functional entity feedback message to the network functional repository functional entity 850 in case that it is determined that the data entry satisfying the matching condition is not stored.
In step S906, network function repository function 850 forwards the no match function entity feedback message to first control plane network function 831.
In step S907, the first control plane network function 831 receives the non-matching function entity feedback message and sends an entity allocation request to the network function repository function 850 according to the prior art scheme.
In step S908, the network function repository function entity 850 receives the entity allocation request, and allocates the second access and mobility management function entity 822 to the first control plane network function entity 831.
In step S909, the first control plane network function 831 establishes a connection with the second access and mobility management function 822.
At step S910, the network function repository function entity 850 generates a first update message based on the identity of the second access and mobility management function entity 822, the global identity and the valid service identity.
At step S911, network function repository function 850 sends a first update message to storage function 840.
In step S912, storage function 840 generates and stores a data entry corresponding to the first update message based on the first update message.
In step S913, in case of a connection failure between the second control plane network function entity 832 and the first access and mobility management function entity 821, an entity query request is sent to the network function repository function entity 850.
In step S914, network function repository function 850 forwards the entity query request to storage function 840.
In step S915, the storage function entity 840 receives the entity query request, and determines whether to store the data entry satisfying the matching condition.
At this time, the first control plane network functional entity 831 has already been allocated with the second access and mobility management functional entity 822, and the data entry corresponding to the first update message is the data entry satisfying the matching condition, so the data entry satisfying the matching condition is stored in the storage functional entity 840.
In step S916, the storage function entity 840, under the condition that it is determined that the data items satisfying the matching condition are stored, obtains a second entity identifier from the data items satisfying the matching condition, generates an entity query result based on the second entity identifier, and sends the entity query result to the network function repository function entity 850.
The second entity identity is the identity of the second access and mobility management function entity 822.
In step S917, network function repository function 850 forwards the entity query result to second control plane network function 832.
In step S918, the second control plane network function entity 832 receives the entity query result, and establishes a connection with the second access and mobility management function entity 822 according to the second entity identifier in the entity query result.
Similarly, the nth control plane network function entity 83n also establishes a connection with the second access and mobility management function entity 822, so that the terminal 810 uses the service of the same AMF (in this embodiment, the second access and mobility management function entity 822 is specifically referred to).
It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.
It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.
Claims (11)
1. An AMF selection method, comprising:
receiving an entity query request sent by a first control plane network functional entity, wherein the first control plane network functional entity is a functional entity providing a control plane service for a terminal, the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing an access service for the terminal and does not designate a backup functional entity;
judging whether a data item meeting the matching condition is stored or not, wherein the data item is a data record which is generated by a storage functional entity according to the received message and is used for storage;
under the condition that the data items meeting the matching conditions are determined to be stored, acquiring a second entity identifier from the data items meeting the matching conditions, wherein the second entity identifier is the identifier of a second access and mobility management functional entity which replaces the first access and mobility management functional entity to provide access service for the terminal;
and generating an entity query result based on the second entity identifier, and sending the entity query result to the first control plane network functional entity so that the first control plane network functional entity establishes connection with the second access and mobility management functional entity based on the second entity identifier.
2. The AMF selection method according to claim 1, wherein the matching condition is that an entity identifier part of a global identifier in the data entry matches the first entity identifier, a terminal identifier part of the global identifier in the data entry matches the terminal short identifier, the service status identifier of the data entry is a valid service identifier, and the update time of the data entry is closest to the current time.
3. The AMF selection method according to claim 2, wherein before determining whether to store a data entry satisfying a matching condition, further comprising:
receiving a first update message sent by a network function repository function entity, wherein the first update message is a message sent when the network function repository function entity allocates the second access and mobility management function entity for a second control plane network function entity, the second control plane network function entity is a function entity that provides a control plane service for the terminal except for the first control plane network function entity, and the first update message includes the second entity identifier, the global identifier, and the valid service identifier;
generating and storing the data entry corresponding to the first update message based on the first update message.
4. The AMF selection method according to claim 2, wherein after determining whether to store the data entry satisfying the matching condition, further comprising:
sending a no match function entity feedback message to the first control plane network function entity if it is determined that no data entry satisfying the match condition is stored.
5. The AMF selection method according to claim 4, wherein after sending a no match function entity feedback message to the first control plane network function entity in case it is determined that no data entry satisfying the match condition is stored, further comprising:
receiving a second update message sent by a network function repository function entity, wherein the second update message is a message sent when the network function repository function entity allocates a third access and mobility management function entity for the first control plane network function entity, the second update message includes a third entity identifier, the global identifier, and the valid service identifier, and the third entity identifier is an identifier of the third access and mobility management function entity;
generating and storing the data entry corresponding to the second update message based on the second update message.
6. The AMF selection method of claim 5, further comprising, after the generating and storing the data entry corresponding to the second update message based on the second update message:
receiving a third update message sent by the third access and mobility management functional entity, where the third update message is a message that is generated and sent when the terminal leaves a service range of the third access and mobility management functional entity, and the third update message includes the first entity identifier, the global identifier, and an invalid service identifier;
generating and storing the data entry corresponding to the third update message based on the third update message.
7. An AMF selection method, comprising:
sending an entity query request to a designated storage functional entity, wherein the entity query request comprises a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity which stops providing access service for a terminal and does not designate a backup functional entity;
receiving an entity query result returned by the storage function entity, wherein the entity query result is a result returned when the storage function entity stores a data entry meeting a matching condition, the data entry is a data record for storage generated by the storage function entity according to a received message, the entity query result comprises a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity which replaces the first access and mobility management function entity to provide an access service for a terminal;
and establishing connection with the second access and mobility management functional entity according to the second entity identifier.
8. The AMF selection method according to claim 7, wherein after sending the entity query request to the designated storage function entity, further comprising:
and receiving a non-matching functional entity feedback message returned by the storage functional entity, wherein the non-matching functional entity feedback message is a message generated and sent under the condition that the storage functional entity does not store the data item meeting the matching condition.
9. The AMF selection method according to claim 8, wherein after receiving the no-match functional entity feedback message returned by the storage functional entity, further comprising:
sending an entity allocation request to a network function repository function entity;
receiving an entity allocation result returned by the network function repository function entity, wherein the entity allocation result comprises a third entity identifier, and the third entity identifier is an identifier of a third access and mobility management function entity allocated to the current control plane network function entity;
and establishing connection with the third access and mobility management functional entity based on the third entity identification.
10. An AMF selection apparatus, comprising:
a first receiving module, configured to receive an entity query request sent by a first control plane network functional entity, where the first control plane network functional entity is a functional entity that provides a control plane service for a terminal, the entity query request includes a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management functional entity that stops providing an access service for the terminal and does not specify a backup functional entity;
the judging module is configured to judge whether to store a data item meeting a matching condition, wherein the data item is a data record which is generated by the storage functional entity according to the received message and is used for storage;
an obtaining module, configured to, in a case that it is determined that the data entry satisfying the matching condition is stored, obtain a second entity identifier from the data entry satisfying the matching condition, where the second entity identifier is an identifier of a second access and mobility management function entity that provides an access service for the terminal in place of the first access and mobility management function entity;
a generation module configured to generate an entity query result based on the second entity identification;
a first sending module configured to send the entity query result to the first control plane network function entity, so that the first control plane network function entity establishes a connection with the second access and mobility management function entity based on the second entity identifier.
11. An AMF selection apparatus, comprising:
a second sending module, configured to send an entity query request to a designated storage function entity, where the entity query request includes a first entity identifier and a terminal short identifier, and the first entity identifier is an identifier of a first access and mobility management function entity that stops providing an access service for a terminal and does not designate a backup function entity;
a second receiving module, configured to receive an entity query result returned by the storage function entity, where the entity query result is a result returned when the storage function entity stores a data entry that satisfies a matching condition, the data entry is a data record for storage generated by the storage function entity according to a received message, the entity query result includes a second entity identifier, and the second entity identifier is an identifier of a second access and mobility management function entity that replaces the first access and mobility management function entity to provide an access service for a terminal;
and the connection module is configured to establish connection with the second access and mobility management function entity according to the second entity identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110511796.7A CN113163472B (en) | 2021-05-11 | 2021-05-11 | AMF selection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110511796.7A CN113163472B (en) | 2021-05-11 | 2021-05-11 | AMF selection method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113163472A CN113163472A (en) | 2021-07-23 |
| CN113163472B true CN113163472B (en) | 2022-04-26 |
Family
ID=76874429
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110511796.7A Active CN113163472B (en) | 2021-05-11 | 2021-05-11 | AMF selection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113163472B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115884232A (en) * | 2022-09-08 | 2023-03-31 | 中兴通讯股份有限公司 | Communication method, apparatus and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109803242A (en) * | 2017-11-17 | 2019-05-24 | 中兴通讯股份有限公司 | Method, equipment and the readable storage medium storing program for executing of NF discovery are carried out by NRF |
| CN110337072A (en) * | 2019-07-18 | 2019-10-15 | 中国联合网络通信集团有限公司 | Automatically the method and system of group is established under a kind of 5G network |
| CN112312539A (en) * | 2019-07-30 | 2021-02-02 | 华为技术有限公司 | Method, device, system and storage medium for selecting policy control function network element |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109041136B (en) * | 2017-06-12 | 2020-07-03 | 电信科学技术研究院 | Method for inserting SMF and AMF entity |
-
2021
- 2021-05-11 CN CN202110511796.7A patent/CN113163472B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109803242A (en) * | 2017-11-17 | 2019-05-24 | 中兴通讯股份有限公司 | Method, equipment and the readable storage medium storing program for executing of NF discovery are carried out by NRF |
| CN110337072A (en) * | 2019-07-18 | 2019-10-15 | 中国联合网络通信集团有限公司 | Automatically the method and system of group is established under a kind of 5G network |
| CN112312539A (en) * | 2019-07-30 | 2021-02-02 | 华为技术有限公司 | Method, device, system and storage medium for selecting policy control function network element |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113163472A (en) | 2021-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110691384B (en) | Network slice using method and device | |
| CN106850710B (en) | Data cloud storage system, client terminal, storage server and application method | |
| CN109361526B (en) | Policy-controlled routing method, PCRF/PCF and DRA | |
| US20120233298A1 (en) | Management of application server-related user data | |
| CN107733957B (en) | Distributed service configuration system and version number distribution method | |
| CN113453213B (en) | Authentication data synchronization method and device | |
| CN110049503B (en) | Method and equipment for acquiring data | |
| CN103636263A (en) | The obtaining, by a terminal, of information relating to access to a service | |
| US20150088995A1 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
| EP3996431A1 (en) | Network element registration method and system, and network function repository function | |
| CN111901132A (en) | Group management method, device and system | |
| CN113163472B (en) | AMF selection method and device | |
| KR20190139279A (en) | Network entities and methods for identifier assignment and / or identifier mapping of network services | |
| CN113194518B (en) | Redirection allocation method, device and system | |
| CN112243224B (en) | Edge computing network implementation method and device | |
| US7126909B2 (en) | Centralized management technique of call control data | |
| CN116250222A (en) | Method and device for notifying business continuity event | |
| CN116325835A (en) | Application context migration method and device | |
| CN113489747B (en) | Session connection method, device and terminal | |
| CN113491157A (en) | Telecommunications network | |
| CN113630779A (en) | Network connection management method and device and terminal | |
| US20070115855A1 (en) | Route servicing device, method and system applying the device | |
| US11057463B2 (en) | Method for synchronizing context data of network functions in a mobile network | |
| WO2017101045A1 (en) | Network element selection method and network element selector | |
| CN115004657B (en) | Addressing method, addressing system and addressing device |
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 |