WO2022151367A1

WO2022151367A1 - Communication method and communication device

Info

Publication number: WO2022151367A1
Application number: PCT/CN2021/072206
Authority: WO
Inventors: 丁辉; 段宝平; 朱建国
Original assignee: 华为技术有限公司
Priority date: 2021-01-15
Filing date: 2021-01-15
Publication date: 2022-07-21

Abstract

A communication method and a communication device, which are used for saving on signalling resources. The method of the embodiments of the present application is applied to network element data cutover, and the method comprises: after data on a network element 1 is cut over to other network elements, the network element 1 being able to determine a user list 1 according to users to which the cutover data belongs, and the users in the user list 1 being influenced by the cutover of the data on the network element 1, i.e. it not being possible for the users in the user list 1 to continue acquiring data of the users from the network element 1; and a network element 3 being able to receive the user list 1 by means of a network repository function entity, and triggering a context reconstruction process for the users in the user list 1 after the data on the network element 1 is cut over.

Description

A communication method and communication device

technical field

The embodiments of the present application relate to the field of communication, and in particular, to a communication method and a communication device.

Background technique

The 3rd generation partnership project (3GPP) standard defines the 5th generation mobile networks (5G) network architecture. When the network elements that store user data in the operator's network occur In the event of failure, capacity expansion, or capacity reduction, user data corresponding to some affected users on the current network element needs to be migrated to the new network element, and the new network element will continue to serve these users.

The above-mentioned network element storing user data may be a unified data management network element (unified data management, UDM), a policy control network element (policy control function, PCF), or a unified data repository (unified data repository, UDR), where unified The data management network element can store user registration context data, the policy control network element can store user policy context data, and the unified data storage can store user subscription data. Taking the UDM performing data cutover as an example, the old-side UDM restarts, such as failure restart/planned restart, or data cutover, the updated network function (NF) can be sent to the network repository function (NRF). ) parameter (profile), which contains the updated recovery time (recoveryTime) and the updated service information. The NRF judges that the NF profile of the old side UDM has changed, and then subscribes to the access and mobility of the old side UDM service state. The access and mobility management function (AMF)/session management function (SMF)/short message service function (SMF) network element sends the updated NF profile. After receiving the subscription notification, AMF/SMF/SMSF determines that the user context registered before the time point corresponding to the recoveryTime may be lost based on the recoveryTime in the received updated UDM NF profile, and triggers the corresponding mechanism to perform context recovery The process, specifically, includes actions such as AMF initiating a subscription data acquisition request, a user context registration request, a subscription data change event subscription request to the old side/new side UDM based on the updated NF profile.

Since AMF/SMF/SMSF currently only supports triggering the above context recovery mechanism based on recoveryTime, it will directly trigger the re-registration process of all users under the UDM, and a single UDM can provide services for tens of millions or even hundreds of millions of users at the same time. Triggering the re-registration process for all users will lead to excessive signaling overhead of the core network and even lead to signaling storms.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a communication method and a communication device, which are used to save signaling resources.

A first aspect of an embodiment of the present application provides a communication method, the method includes: receiving a user list 1 from a network storage functional entity, where the users in the user list 1 are affected by data cutover on the network element 1; rebuilding the user list 1 The context of the user in .

In the above-mentioned first aspect, the execution body of this method is the network element 3, and the network element 1 obtains the user list 1, and the users in the user list 1 are affected by the data cutover on the network element 1, that is, the users in the user list 1. The user data of the user list will be migrated to another network element, so the network element 1 will not be able to continue to provide services for the users in the user list 1. The network element 1 provides the user list 1 to the network element 3 through the network storage function entity, and the network element 3 receives the user list 1 and triggers the data cutover to the network element 1 for the users in the user list 1. When a network element initiates a context reconstruction process, there is no need to re-register all users served by the network element 1, which saves signaling resources.

In a possible implementation manner, the above steps to receive the user list 1 from the network element 1 through the network storage function entity include: receiving a message 1 from the network storage function entity, where the message 1 includes the user list 1 and the parameters of the network element 1, and the parameter Including the recovery time, the recovery time is used to indicate the recovery time stamp of the service provided after the data cutover on the network element 1.

In the above possible implementation manner, the network element 3 receives the user list 1 and the parameters of the network element 1 from the network storage functional entity at the same time. After the restoration time stamp of providing the service ends, the context reconstruction process is initiated for the users in the user list 1.

In a possible implementation, the user list 1 includes one or more of a user permanent identity list, a general public subscription identity list, a routing indication and a home network public key identity.

In a possible implementation manner, the execution body of the method is an access and mobility management function entity, a session management function entity, a short message service function entity, a unified data management entity or a policy control function entity.

In a possible implementation manner, the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.

A second aspect of the embodiments of the present application provides a communication method, the method includes: receiving a user list 1 from a network element 1, where the users in the user list 1 are affected by data cutover on the network element 1; sending the user list 1 to NE 3.

In the above-mentioned second aspect, the network element 1 obtains the user list 1, and the users in the user list 1 are affected by the data cutover on the network element 1, that is, the user data of the users in the user list 1 will be migrated to another network. Therefore, the network element 1 will not be able to continue to provide services for the users in the user list 1. The network storage function entity can send the user list 1 to the network element 3, so that the network element 3 triggers the context reconstruction process for the users in the user list 1 to other network elements to which the data on the network element 1 belongs after the cutover, and does not. All users served by the network element 1 need to be re-registered, which saves signaling resources.

Optionally, the user list 1 received by the network storage function entity is included in the message 2 from the network element 1, the message 2 includes the parameters of the network element 1, and the parameter includes the recovery time, and the recovery time indicates that the network element 1 The recovery timestamp of the service provided after the data cutover.

In a possible implementation manner, the network element 3 is an access and mobility management function entity, a session management function entity, a short message service function entity, a unified data management entity or a policy control function entity.

A third aspect of the embodiments of the present application provides a communication method, the method includes: receiving a user list 2 and indication information from a network element 2, where the user in the user list 2 is the network element 1 after data cutover on the network element 1 The user of the service, the indication information is used to instruct the reconstruction of the context of the user affected by the data cutover on the network element 1; The users served by network element 1 before the data cutover on element 1, the users in user list 1 are affected by the data cutover on network element 1; the context of the users in user list 1 is reconstructed.

In the above-mentioned third aspect, the execution body of the method is the network element 3, the network element 1 obtains the user list 2, and sends the user list 2 and the indication information to the network element 2, and the indication information can instruct the network element 3 to rebuild the receiving network. The context of the user affected by the data cutover on element 1. The network element 3 can receive the user list 2 and the indication information sent by the network element 2, and then obtain the user list 3 served by the network element 1 before the data cutover saved on the network element 1. The user list 3 can be compared to obtain the user list 1 of the users affected by the data cutover on the network element 1, and reconstruct the context of the users in the user list 1 to the network element to which the data cutover on the network element 1 belongs. Only the context reconstruction of the users in the user list 1 can be triggered by one indication information, and there is no need to re-register all the users served by the network element 1, which saves signaling resources.

In a possible implementation manner, the above steps to determine the user list 1 according to the indication information, the user list 2 and the user list 3 include: obtaining and reconstructing the context of the user affected by the data cutover on the network element 1 according to the indication information: according to the user List 2 and user list 3, determine user list 1.

In the above possible implementation manner, after the network element 3 receives the indication information, it can know that it is not necessary to reconstruct the context of the full number of users served by the network element 1, and trigger the current user list 2 and the previously saved user list 3. Compare to get a user list 1 of users who need context reconstruction.

In a possible implementation manner, the user list 3 includes the parameters of the network element 1 before the data cutover on the network element 1, and the user list 2 includes the parameters of the network element 1 after the data cutover on the network element 1 middle.

In a possible implementation manner, the network element 2 is a network storage functional entity.

A fourth aspect of the embodiments of the present application provides a communication method, the method includes: receiving a user list 2 and indication information from a network element 1, where the users in the user list 2 are the network element 1 after data cutover on the network element 1 The user of the service, the indication information is used to instruct the reconstruction of the context of the user affected by the data cutover on the network element 1; the user list 2 and the indication information are sent to the network element 3.

In the above fourth aspect, the execution body of the method is the network element 2, the network element 1 obtains the user list 2, and the network element 2 can receive the user list 2 and the indication information sent by the network element 1, and the indication information can instruct the network element 3 to rebuild Context of users affected by data cutover on network element 1. The network element 2 can send the user list 2 and the indication information to the network element 3, so that the network element 3 reconstructs the context of the users affected by the data cutover on the network element 1, and does not need to recreate the full number of users served by the network element 1. Registration saves signaling resources.

In a possible implementation manner, the execution body of the method is a network storage functional entity.

A fifth aspect of the embodiments of the present application provides a communication method, the method includes: determining that the subscription data of the user is in a cutover state; and sending a cause value to the network element 3, where the cause value indicates that the subscription data of the user is in the cutover state.

In the above fifth aspect, the execution body of the method may be a unified data management entity. When a user accesses the 5G network, the network element 3 will obtain the user's subscription data from the unified data management entity. When the unified data management entity determines that the user's subscription data is in the cutover state, the cutover state means that the user's subscription data originally stored in the unified data storage entity has been migrated to another network element, so the unified data management entity will not be able to The users in the user list 1 continue to provide services. At this time, the unified data management entity can send a cause value to the network element 3, the cause value indicates that the subscription data of the user is in the cutover state, and send the cause value to the network element 3. , to trigger the network element 3 to instruct the user to re-connect to the 5G network after a period of time, so as to avoid the problem that the affected users cannot access the 5G network for a long time due to the cutover of the subscription data.

In a possible implementation manner, after the above steps determine that the subscription data of the user is in a cutover state, the method further includes: sending a timer to the network element 3, where the timer is used to instruct a registration process to be initiated after the timer expires.

In the above possible implementation manner, the network element 1 may also send a timer to the network element 3, and the timer is determined according to the remaining duration of the data cutover, so that the network element 3 can re-initiate the registration process after the timer expires. , which can reduce the number of registration failures.

In a possible implementation manner, the step of determining that the subscription data of the user is in the cutover state includes: determining that the subscription data of the user is in the cutover state in the corresponding unified data storage entity.

In the above possible implementation manner, the user's subscription data in the cutover state may be determined by the list of users from the unified data storage entity affected by the data cutover on the unified data storage entity, or by querying the unified data storage entity for the user. The cutover status of the user subscription data obtained from the subscription data is determined.

In a possible implementation manner, the execution body of the method is a unified data management entity.

In a possible implementation manner, the network element 3 is an access and mobility management function entity, a session management function entity or a short message service function entity.

A sixth aspect of the embodiments of the present application provides a communication device, including: a receiving unit configured to receive a user list 1 from a network storage functional entity, where the users in the user list 1 are affected by data cutover on the network element 1; Element to reconstruct the context of users in user list 1.

The communication device is configured to perform the method of the first aspect or any one of the implementations of the first aspect.

A seventh aspect of an embodiment of the present application provides a communication device, including: a receiving unit configured to receive a user list 1 from a network element 1, where the users in the user list 1 are affected by data cutover on the network element 1; a sending unit , which is used to send user list 1 to network element 3.

The communication device is configured to perform the method of the second aspect or any one of the implementations of the second aspect.

An eighth aspect of an embodiment of the present application provides a communication device, including: a receiving unit configured to receive a user list 2 and indication information from a network element 2, where the users in the user list 2 are after data cutover on the network element 1 The user served by the network element 1, the indication information is used to instruct the reconstruction of the context of the user affected by the data cutover on the network element 1; the determining unit is used to determine the user list 1 according to the indication information, the user list 2 and the user list 3, The users in the user list 3 are users served by the network element 1 before the data cutover on the network element 1, and the users in the user list 1 are affected by the data cutover on the network element 1; the reconstruction unit is used to rebuild the data in the user list 1. the context of the user.

The communication device is configured to execute the method of the third aspect or any one of the implementations of the third aspect.

A ninth aspect of an embodiment of the present application provides a communication device, including: a receiving unit configured to receive a user list 2 and indication information from a network element 1, where the users in the user list 2 are after data cutover on the network element 1. For the users served by the network element 1, the indication information is used to instruct to rebuild the context of the users affected by the data cutover on the network element 1; the sending unit is used to send the user list 2 and the indication information to the network element 3.

The communication device is configured to perform the method of the foregoing fourth aspect or any one of the implementations of the fourth aspect.

A tenth aspect of the embodiments of the present application provides a communication device, including: a determining unit, configured to determine that the subscription data of a user is in a cutover state; a sending unit, configured to send a cause value to the network element 3, where the cause value indicates the The subscription data of the user is in the cutover state.

The communication device is configured to perform the method of the fifth aspect or any one of the implementations of the fifth aspect.

An eleventh aspect of an embodiment of the present application provides a communication device, including: a processor, a memory, and a communication interface, where the processor is configured to execute instructions stored in the memory, so that the communication device executes the first aspect or the first aspect Any method provided in an optional manner, the communication interface is used for receiving or sending an indication. For the specific details of the communication device provided in the eleventh aspect, reference may be made to the foregoing first aspect or any optional manner of the first aspect, which will not be repeated here.

A twelfth aspect of an embodiment of the present application provides a communication device, including: a processor, a memory, and a communication interface, where the processor is configured to execute instructions stored in the memory, so that the communication device executes the foregoing second aspect or the second aspect Any method provided in an optional manner, the communication interface is used for receiving or sending an indication. For the specific details of the communication device provided in the twelfth aspect, reference may be made to the second aspect or any optional manner of the second aspect, which will not be repeated here.

A thirteenth aspect of an embodiment of the present application provides a communication device, including: a processor, a memory, and a communication interface, where the processor is configured to execute instructions stored in the memory, so that the communication device executes the third aspect or the third aspect Any method provided in an optional manner, the communication interface is used for receiving or sending an indication. For the specific details of the communication device provided in the thirteenth aspect, reference may be made to the third aspect or any optional manner of the third aspect, which will not be repeated here.

A fourteenth aspect of an embodiment of the present application provides a communication device, including: a processor, a memory, and a communication interface, where the processor is configured to execute instructions stored in the memory, so that the communication device executes the fourth aspect or the fourth aspect Any method provided in an optional manner, the communication interface is used for receiving or sending an indication. For the specific details of the communication device provided in the fourteenth aspect, reference may be made to the fourth aspect or any optional manner of the fourth aspect, which will not be repeated here.

A fifteenth aspect of an embodiment of the present application provides a communication device, including: a processor, a memory, and a communication interface, where the processor is configured to execute instructions stored in the memory, so that the communication device executes the fifth aspect or the fifth aspect Any method provided in an optional manner, the communication interface is used for receiving or sending an indication. For the specific details of the communication device provided in the fifteenth aspect, reference may be made to the fifth aspect or any optional manner of the fifth aspect, which will not be repeated here.

A sixteenth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the first aspect or any one of the first aspects is optionally executed method provided.

A seventeenth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the second aspect or any one of the second aspects is optionally executed method provided.

An eighteenth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the aforementioned third aspect or any one of the third aspects is optionally performed method provided.

A nineteenth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the fourth aspect or any one of the fourth aspect is optionally executed method provided.

A twentieth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the aforementioned fifth aspect or any one of the fifth aspects is optionally executed method provided.

A twenty-first aspect of an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method provided in the foregoing first aspect or any optional manner of the first aspect.

A twenty-second aspect of an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method provided in the foregoing second aspect or any optional manner of the second aspect.

A twenty-third aspect of an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method provided in the third aspect or any optional manner of the third aspect.

A twenty-fourth aspect of an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method provided in the foregoing fourth aspect or any optional manner of the fourth aspect.

A twenty-fifth aspect of an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method provided in the fifth aspect or any optional manner of the fifth aspect.

A twenty-sixth aspect of an embodiment of the present application provides a communication system, where the communication system includes a communication device that executes the method provided in the first aspect or any optional manner of the first aspect, and a communication device that executes the second aspect or any of the second aspect. A communication device for the method provided in an optional manner; a communication device for performing the method provided in the third aspect or any optional manner of the third aspect, and performing the method provided in the fourth aspect or any optional manner of the fourth aspect communication equipment.

Description of drawings

FIG. 1 is a schematic diagram of a 5G network networking architecture provided by an embodiment of the present application;

FIG. 2 is an embodiment of a communication method provided by an embodiment of the present application;

FIG. 3 is another embodiment of a communication method provided by an embodiment of the present application;

FIG. 4 is another embodiment of the communication method provided by the embodiment of the present application;

FIG. 5 is another embodiment of the communication method provided by the embodiment of the present application;

FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 7 is another schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 8 is another schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is another schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 10 is another schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Those of ordinary skill in the art know that with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The terms "first", "second" and the like in the description and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Figure 1 is the current 3rd generation partnership project (3GPP) standard has defined the fifth generation mobile communication technology (5-generation, 5G) network networking architecture, as shown in Figure 1, the architecture includes : Application function (AF), unified data management (UDM), unified data repository (UDR), policy control function (PCF), session management function (session management function) , SMF), access and mobility management function (AMF), short message service function (short message service function, SMSF), user plane function entity (user plane function, UPF) and (wireless) access Access network ((radio)access network, (R)AN).

Among them, AF mainly conveys the requirements of the application side to the network side, for example, quality of service (quality of service, QoS) requirements. The AF can be a third-party functional entity or an application service deployed by an operator, such as an IP (internet protocol, IP) multimedia subsystem (IP multimedia subsystem, IMS) voice call service.

UDM is mainly responsible for managing contract data, user access authorization and other functions.

UDR is mainly responsible for the access function of contract data, policy data, application data and other types of data.

PCF is mainly responsible for policy control such as charging, QoS bandwidth guarantee and mobility management for sessions and service flow levels.

SMF mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and IP address allocation of user equipment (UE).

AMF mainly performs functions such as mobility management and access authentication/authorization.

SMSF is mainly used to manage functions such as short message delivery and short message service billing.

As the interface with the data network, UPF implements functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation.

(R)AN corresponds to different access networks in 5G, such as wired access and wireless base station access.

The functions of each interface are described as follows:

1. N7: The interface between the PCF and the SMF is used to deliver a protocol data unit (Protocol Data Unit, PDU) session granularity and a business data flow granularity control policy. PDU session: A session service that implements PDU connectivity between the UE and the data network, and is identified by the PDU session ID (Session ID).

2. N15: the interface between the PCF and the AMF, used for delivering UE policies and access control related policies.

3. N5: The interface between the AF and the PCF, used for application service request delivery and network event reporting.

4. N4: The interface between SMF and UPF, which is used to transmit information between the control plane and the user plane, including controlling the distribution of forwarding rules for the user plane, QoS control rules, traffic statistics rules, etc., and reporting of information on the user plane .

5. N11: the interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control message sent to the UE, the radio resource control information sent to the RAN, and the like.

6. N2: the interface between the AMF and the RAN, used to transmit radio bearer control information from the core network side to the RAN, etc.

7. N1: The interface between the AMF and the UE, independent of access, is used to deliver QoS control rules to the UE.

8. N8: the interface between the AMF and the UDM, for the AMF to obtain the subscription data and authentication data related to access and mobility management from the UDM, and for the AMF to register the UE's current mobility management related information to the UDM.

9. N10: an interface between the SMF and the UDM, used for the SMF to obtain the session management-related subscription data from the UDM, and the SMF to register the UE's current session-related information to the UDM.

10. N20: an interface between the AMF and the SMSF, used for the AMF to trigger the SMSF to initiate a short message service registration/deregistration process to the UDM.

11. N21: an interface between the SMSF and the UDM, used for the SMSF to obtain the short message service related subscription data from the UDM, and the SMSF to register the UE's current short message service related information with the UDM.

12. N35: an interface between the UDM and the UDR, used for the UDM to obtain user subscription data information from the UDR.

13. N36: an interface between the PCF and the UDR, used for the PCF to remove the policy-related subscription data and application data-related information from the UDR.

The general user registration process can be simply described as follows: UE sends a registration request to AMF through AN, AMF obtains subscription data from a specific UDM according to the user ID, and UDM can obtain actual subscription data from UDR after receiving the request. In addition, the AMF will also register its own information and the current access information of the UE to the UDM, so that the UDM and other network elements can send downlink signaling to the AMF. In this process, the AMF can also initiate a user policy control establishment request (UE policy control_create request) and an access management policy control establishment request (AM policy control_create request) to the PCF, which are used to obtain the UE policy and the access management policy, respectively. Optionally, during the registration process, the AMF may also perform an SMSF selection process to trigger the SMSF to acquire short message service subscription data from the UDM, and to register its own information and current access mode to the UDM.

The general session establishment process can be simply described as: UE sends session establishment request to AMF through AN, AMF selects SMF to provide service for the session, saves the correspondence between SMF and PDU session, and sends the session establishment request to SMF, SMF Select the corresponding UPF for the UE, establish a user plane transmission path, and assign an IP address to it. In this process, the SMF will also initiate a policy control session establishment request to the PCF to establish a policy control session between the SMF and the PCF. During the policy control session establishment process, the SMF will save the policy control session and the PDU session. Correspondence . In addition, the AF can also establish an AF session with the PCF, and the PCF binds the AF session and the policy control session.

When the network element storing user data in the operator's network fails and cannot continue to operate normally or the operator decides to expand/reduce the capacity of the above-mentioned network element, the user data on the old side network element will be migrated to the new side network elements, and the new side network elements provide services to these users. For example, when the operator decides to expand the UDM or migrate the subscription data on the UDR node corresponding to the UDM, the old-side UDM device will notify all relevant AMF, SMF, and SMSF network elements that the current UDM device will be unavailable. To trigger the relevant AMF, SMF, SMSF to initiate a registration request to the new-side UDM, so that the UDM can determine the AMF/SMF/SMSF entity currently serving the user when receiving the downlink request.

In addition, there is usually a fixed topology relationship between UDM/PCF and UDR. For example, UDM/PCF can only access specific UDR network elements. Taking UDM as an example, when user subscription data UDR1 is migrated to UDR2, UDM1 connected to UDR1 It will also migrate to UDM2 connected to UDR2, which also triggers data cutover on UDM1.

In the current 5G architecture defined by 3GPP, the interface between the network elements of the control plane adopts a service-oriented architecture. Each network element of the control plane registers its own address and supported service information with the network repository function (NRF). Three-party network element query, such as UDM registers its own address and supported service list with NRF, so that network elements such as AMF and SMF can query. The general process is described as follows: When the AMF receives the UE registration request, it will send a UDM query request to the NRF, which can carry network element selection parameters, such as network element (network function, NF) Type (ie UDM), user identification (such as User permanent identifier (subscription permanent identifier, SUPI), such as user concealed identifier (subscription concealed identifier, SUCI), general public subscription identifier (GPSI, generic public subscription identifier), routing indicator (routing indicator, RI), home network public key ID (home network public key ID, HNPK ID)) and other information. When the AMF receives the UDM identification/address information returned by the NRF, it will send a subscription data acquisition request message to the UDM, and register its own identification and current access mode to the UDM. After the UDM receives the registration request, it will save the AMF information, the current access mode of the UE and other information in the context of the UE for subsequent sending of signaling requests to the corresponding AMF network element (such as subscription data update request, location acquisition request, etc. ), or provide the AMF information query function to other network elements (such as querying the user's current AMF during a voice call). In addition, in order to support the session management function and the short message service, the SMF and the SMSF also obtain subscription data from the UDM and register their own information to the UDM. The specific steps are similar to the interaction between the AMF and the UDM.

Under this architecture, when the NE judges that a fault restart/planned restart/data cutover needs to be performed, it will send a service deregistration request to the NRF, or when it receives a service update request, it will update its own NF profile previously registered with the NRF. , and the NRF will notify all other NEs subscribed to the NE state change event of the deregistration state or update state, so as to trigger other NEs subscribed to the NE state change event to initiate interaction with the new side NE process.

Exemplarily, the UDM of the cutover network element carries the updated recoveryTime to indicate that the AMF/SMF/SMSF that has subscribed to the state change event of the network element has restarted/relocated/upgraded due to the current failure. The granularity is executed in batches. For example, UDM can provide services for users with 1000 number segments. Each cutover may only perform cutover for 100 user number segments. The registration process causes a great waste of signaling to the core network.

To solve the above problem, an embodiment of the present application provides a communication method, and the specific implementation manner of the communication method is described below.

The embodiments of the present application can be applied to all network elements that need to register/de-register services with NRF, such as UDM to perform data cutover, and notify AMF, SMF, SMSF and other network elements via NRF; or PCF to perform data cutover, and to perform data cutover via NRF The NRF notifies the network elements such as AMF and SMF; or the UDR performs data cutover and notifies the network elements such as PCF and UDM through the NRF.

Referring to FIG. 2, an embodiment of the communication method provided by the embodiment of the present application includes:

201. The network element 1 sends a message 2 to the network storage function entity.

In this embodiment, when network element 1 goes online, it sends a NF registration (register) message to network element 2, and the request message will carry its own NF parameter (NFprofile), that is, the NF profile is the parameter of network element 1, and the NF profile in the NF profile A recovery time (recoveryTime) may also be included, and at this time, the recoveryTime is used to indicate the time stamp when the network element 1 provides services.

Optionally, the NF profile can also carry the group ID (Group ID) to which the network element 1 belongs. The mapping relationship between the Group ID and the SUPI range (range)/GPSI range/RI/HNPK ID will be pre-processed on the NRF. configuration. Alternatively, network element 1 may directly include the SUPI range/GPSI range/RI/HNPK ID list served by itself in the NF profile sent to the NRF.

When the network element 3 interacts with the network element 1 for the first time, it can also subscribe the service state change of the network element 1 to the NRF, so that the NRF notifies the network element 3 of the change event when it determines that the NF profile of the network element 1 has changed.

After the network element 1 completes the data cutover, it sends message 2 to the NRF, which can be an NF update (update) or NF registration (register) request, which, in addition to carrying the updated NF profile (including its own NF ID and recoveryTime), It can also carry the user list 1 affected by the data cutover on the network element 1. The user list 1 can be the user ID segment affected by the data cutover on the network element 1, that is, the user list 1 stored on the network element 1. The data of the users in the user list are cut over to the network element 4, and the core network element that provides services for the users on the user list 1 cannot obtain the user's data from the network element 1. Wherein, the updated recoveryTime is used to indicate the time stamp of the service recovery provided by the network element 1 . The above-mentioned user list 1 may be determined by the network element 1 receiving information from an operation maintenance management entity or a network storage function entity.

Specifically, in this embodiment, the network element 1 may receive the user list 1 from an operation maintenance management entity (operation administration and maintenance, OAM) during the data cutover process, or it may be determined by the network element 1 based on the user to which the cutover data belongs. User list 1, not limited here.

Specifically, the form of the user list may include any one or more of the following forms: SUPI range, GPSI range, RI, HNPK ID.

202. The NRF sends message 1 to network element 3.

After receiving the above-mentioned message 2, the NRF can send the above-mentioned message 1 including the updated NF profile and the user list 1 to the subscribing entity network element 3 according to the locally saved subscription record about the service state change of the network element 1.

Optionally, the user list 1 is only notified to the target subscribing entity as a one-time message, and the network element that subsequently queries the network element 2 for the service information of the network element 1 will not receive the above-mentioned user list 1 again.

203. The network element 3 reconstructs the context of the users in the user list 1 to the network element 4 according to the user list 1.

After the network element 3 receives the user list 1 and the updated NF profile, the updated NF profile includes the ID of the network element 1, and the network element 3 can determine that the users in the user list 1 are related to the network before the updated recoveryTime. The context between meta 1 needs to be reconstructed. In addition, if the network element 3 detects that there is no local network element information that can provide services for the users affected by the data cutover on the network element 1, the network element 3 may also send a query request to the NRF, where the query request includes The user identifier (such as SUPI, GPSI, RI, HNPK ID, etc.) of the user affected by the data on the network element 1, the NRF can determine the network element 4 that saves the subscription data of the user of the user list 1 according to the user identifier, and use the The service information NF profile of the network element 4 is sent to the network element 3, so that the network element 3 can initiate a user context creation request to the network element 4 to execute the user context reconstruction process. Specifically, the above-mentioned user context creation request may be a user context registration request, a policy control association establishment request, or a user subscription data acquisition/subscription request, or the like.

Optionally, before the NRF determines, according to the user identifier, the network element 4 that stores the subscription data of the user in the user list 1, and after the data of the user in the user list 1 is cut over to the network element 4, the network element 4 can send the NF to the NRF. An update or NF register request that includes the user's user ID.

In this embodiment, network element 1 may be an old-side UDM, an old-side UDR, or an old-side PCF. When network element 1 is an old-side UDM, network element 3 is an AMF/SMF/SMSF, and network element 4 is a new-side UDM. At this time, the user context reconstruction process can be understood as the AMF/SMF/SMSF obtaining the updated UE subscription data from the new side UDM/subscribing to the UE subscription data change event and the user context registration process; when the network element 1 is the old side UDR, the network element 3 is the UDM/PCF, and NE 4 is the new-side UDR. At this time, the user context reconstruction process can be understood as the UDM/PCF obtaining the updated UE subscription data from the new-side UDR and subscribing to the UE subscription data change event; when the NE 1 is When the old side PCF is used, the network element 3 is the AMF/SMF, and the network element 4 is the new side PCF. At this time, the user context reconstruction process can be understood as the AMF/SMF establishing the corresponding policy context to the new side PCF.

In the above embodiment, the data on the UDR on the old side is saved in the UDR on the new side after cutover, and the UDR on the new side still supports the UDM/PCF served by the UDR on the old side. Optionally, this implementation also includes that the UDR on the new side does not support the UDR on the old side. The situation of the UDM/PCF of the UDR service, and trigger the data cutover process of the UDM/PCF of the UDR service on the old side.

In this embodiment, the network element 3 receives the user list 1 affected by the data cutover on the network element 1, and can only trigger the context reconstruction of the users in the user list 1, and does not need to re-register all the users served by the network element 1. Signaling resources are saved.

In addition to the description in the embodiment shown in FIG. 2: the network element 1 sends the list of users affected by the data cutover on the network element 1, the embodiment of the present application also proposes a communication method, where the network element 3 confirms the user list 1 . Referring to FIG. 3, another embodiment of the communication method provided by the embodiment of the present application includes:

301. Network element 1 sends user list 2 and indication information to network element 2.

In this embodiment, the network element 1 goes online to register with the network element 2 and the network element 3 subscribes to the network element 2 for the service status change of the network element 1. Refer to the relevant description of step 201 in the communication method shown in FIG. 2 , which is not repeated here. Repeat. In this embodiment, the network element 2 is an NRF.

Optionally, the NF profile can also carry the group ID (Group ID) to which the network element 1 belongs. The mapping relationship between the Group ID and the SUPI range (range)/GPSI range/RI/HNPK ID will be pre-processed on the NRF. configuration. Alternatively, the network element 1 may also directly include the SUPI range/GPSI range/RI/HNPK ID list served by itself in the NFprofile sent to the NRF.

After NE 1 completes the data cutover, it can send an NF update or NF register request to the NRF, which, in addition to carrying the updated NF profile (including the recoveryTime and the list of users served after the data cutover on NE 1 2 (after the update) SUPI range/GPSI range/RI/HNPK ID list), or Group ID), and also carry indication information (such as partial update indication (partial update indication)). Wherein, the updated recoveryTime is used to indicate the time stamp of the recovery of the service served by the network element 1 . The partial update indication is used to indicate that the context of the user affected by the data cutover on the network element 1 needs to be rebuilt.

302. The network element 2 sends the user list 2 and the indication information to the network element 3.

After receiving the above message, the NRF can send the above-mentioned updated NF profile and indication information to the subscribing entity network element 3 according to the locally saved subscription record about the service state change of network element 1, wherein the updated NF The profile includes the user list 2 served by the network element 1 after the data on the network element 1 is cut over.

Optionally, when the network element 1 sends the Group ID to the NRF, the NRF can send the user list 2 to the network element 3 according to the mapping relationship between the locally saved Group ID and the SUPI range/GPSI range/RI/HNPK ID.

Specifically, when the network element 1 sends the Group ID to the NRF, the OAM can update the mapping relationship between the Group ID and the SUPI range/GPSI range/RI/HNPK ID saved on the NRF based on the operation and maintenance policy, so that When the network element 3 subsequently queries the network element serving the user corresponding to the user identifier through the network element 2, the network element 2 can obtain the corresponding network element through the operation, maintenance and management entity. If the NF profile sent by NE 1 to the NRF does not contain the Group ID, the OAM does not need to configure the mapping relationship between the group ID and the SUPI range/GPSI range/RI/HNPK ID on the NRF.

Optionally, the above information is only notified to the target subscribing entity as a one-time message, and the network element that subsequently queries the network element 2 for the service information of the network element 1 will no longer receive the above-mentioned indication information.

303. The network element 3 obtains, according to the indication information, to reconstruct the context of the user affected by the data cutover on the network element 1.

After the network element 3 receives the above-mentioned indication information, for example, after receiving the partial update indication, it can be determined that the context of the user affected by the data cutover on the network element 1 needs to be rebuilt.

304. The network element 3 determines the user list 1.

When the network element 3 determines that the context of the user affected by the data cutover on the network element 1 needs to be rebuilt, step 304 can be triggered, and the network element 3 can obtain a list of users served by the network element 1 before the data cutover 3 , the user list 3 is sent to the network element 3 by the NRF before step 304 . The network element 3 may compare the user list 2 with the user list 3 to obtain the user list 1 affected by the data cutover on the network element 1 . User list 3 is included in the NF profile of network element 1 before data cutover on network element 1, and user list 2 is included in the NF profile of network element 1 after data cutover on network element 1.

305. The network element 3 reconstructs the context of the user in the user list 1 to the network element 4.

For step 305, reference may be made to the relevant description of step 203 in the communication method shown in FIG. 2, and details are not repeated here.

In this embodiment, the network element 3 receives the list of users affected by the data cutover on the network element 1, and can only trigger the context reconstruction of the users in the user list, and does not need to re-register all the users served by the network element 1, which saves money. signaling resources.

When the UE goes online via the AMF/SMF/SMSF, the AMF/SMF/SMSF may store the NF profile of the UDM previously provided by the NRF, which may include the mapping relationship between the SUPI range/GPSI range/RI/HNPK ID and the UDM ID. Based on the above information, if the AMF/SMF/SMSF determines that the UDM can provide services for the current UE, there is no need to repeatedly initiate a query request to the NRF. Subsequently, the AMF/SMF/SMSF sends a subscription data acquisition request to the UDM. However, the UDM does not perceive the state of the subscription data in the UDR. When the subscription data of the target user is in the cutover state, the UDM will not be able to obtain the subscription data of the target user, and can only return the message that the user cannot be found (User_Not_Found). The reason value is AMF/SMF/SMSF, so AMF/SMF/SMSF will return a rejection response referring to the user without 5G subscription, resulting in 5G subscription users being wrongly refused to use 5G services for a long time.

In order to solve the above problem, the embodiment of the present application provides another communication method, and the specific implementation manner of the communication method is described below.

Referring to FIG. 4, another embodiment of the communication method provided by the embodiment of the present application includes:

401. Network element 3 sends a subscription data acquisition request to network element 2.

When the user needs to access the 5G network and needs to obtain the subscription data, the network element 3 can send the subscription data acquisition request to the network element 2, where the subscription data acquisition request includes the user ID of the user, such as SUPI, GPSI, etc.

402. The network element 2 sends a query request to the network element 1.

In this embodiment, after receiving the above-mentioned subscription data acquisition request, the network element 2 can trigger to send a query request to the network element 1, where the query request is used to acquire the subscription data of the user. The UDM may determine the network element 1 that provides services for the user based on the interaction between the user's SUPI/GPSI and the local cache or NRF.

403. The network element 1 sends the query result to the network element 2.

In this embodiment, the data of the user corresponding to the user ID is in the cutover state as an example. When the network element 1 detects that the data of the user corresponding to the above user ID is in the cutover state, it can return the query result to the network element 2. The query result may include a cause value, where the cause value is used to indicate that the data of the user corresponding to the SUPI is in a cutover state. Optionally, the query result may further include a timer, where the timer may indicate the remaining cutover duration of the data of the user corresponding to the SUPI.

404. The network element 2 determines that the subscription data of the user is in a cutover state.

After receiving the above query result, the network element 2 can determine, according to the cause value, that the subscription data of the user is in a cutover state, and the user is currently unable to access the 5G network.

Optionally, the network element 2 can also directly obtain the list of users affected by the data cutover on the network element 1. The method of obtaining the user list can refer to steps 201 to 202 in the communication method shown in FIG. 2 or FIG. 3 . In the communication method shown, the network element 1 in steps 301 to 304 obtains the relevant description of the user list, which will not be repeated here. That is, when the SUPI in the subscription data acquisition request sent by the network element 3 is included in the list of users affected by the data cutover on the network element 1, the network element 2 determines that the subscription data of the user is in the cutover state, that is, the above steps 402 to 402 403 does not need to be executed. At this time, the above-mentioned cause value and timer are determined by the network element 2 .

Optionally, when the user ID in the subscription data acquisition request sent by the network element 3 is not included in the list of users affected by the data cutover on the network element 1, the network element 2 can perform steps 402 to 403 to query the user. contract data. When network element 2 receives the list of users affected by data cutover on network element 1, and receives the list of users affected by data cutover on network element 1 and the users currently affected by data cutover on network element 1 There may be differences in the list of , and the network element 2 may still receive the above-mentioned cause value and timer information from the network element 1, that is, in this case, steps 402 to 403 need to be performed.

405. The network element 2 sends the cause value to the network element 3.

After the network element 2 determines that the subscription data of the user is in the cutover state, it can directly send a response message to the network element 3, where the response message includes the above-mentioned reason value.

Optionally, the response message may further include the above-mentioned timer.

Optionally, the network element 2 receives the service information of the network element 1 after the data cutover is completed, so as to facilitate subsequent selection of the correct network element for the user;

In addition, the data cutover on NE 1 may also lead to a change in the list of users served by UDM. For example, the list of users affected by the data cutover on NE 1 is migrated from NE 1 supported by NE 2 to a different user list. Supports the network element 5 accessed by the network element 2, thereby triggering the data cutover process on the network element 2.

406. The network element 3 sends a subscription data acquisition request to the network element 4.

After receiving the reason value, NE 3 can know that the user data is in the cutover state. When the 5G network cannot be accessed at present, the reason value can be sent to the user to instruct the user to re-register with NE 3 after a period of time. The process is connected to the 5G network. Optionally, the network element 3 may also send a timer to the user to instruct the user to re-initiate the registration process to the network side to access the 5G network after the timer expires, and the timer duration is shorter than the duration of refusing to use the 5G service. Wherein, the AMF that provides services for the user in the subsequent registration process may interact with the local cache or NRF based on the user's SUPI/GPSI/RI/HNPK ID to determine the network element 4 that provides services for the user.

In this embodiment, network element 3 may be an AMF/SMF/SMSF, network element 2 is an old-side UDM, network element 1 is an old-side UDR, and network element 4 is a new-side UDM.

In this embodiment, when the old-side UDM receives an access request from the UE, it needs to return a corresponding cause value based on the cutover status, so as to prevent users affected by the data cutover on the UDR from being unable to access for a long time due to subscription data cutover The problem with 5G networks.

Referring to FIG. 5, another embodiment of the communication method provided by the embodiment of the present application includes:

501. Network element 3 sends a request message to network element 2.

In this embodiment, the network element 3 is the AF, and the network element 2 is the new-side UDM or the new-side PCF.

When the NE 2 is the new side UDM, based on the IMS voice scenario, the AF needs to determine that the UE is currently in the circuit switch (CS) domain or the packet switch (packet switch, PS) domain, so as to continue subsequent call requests, AF A domain selection request may be sent to the new-side UDM to query the network where the UE is currently located. Optionally, the AF may also send a UE information query request, such as a UE location query or a UE reachability event report, to the new-side UDM.

When network element 2 is the new PCF, the AF initiates a policy authorization request to the new PCF, where the policy authorization request may carry information such as user ID, user IP address, event subscription and other information.

In this embodiment, the request message sent by the network element 3 to the network element 2 carries information such as the user identifier SUPI/GPSI.

In this embodiment, the AF may learn the new-side UDM or the new-side PCF from the local configuration, or may be obtained by the AF querying the NRF, which is not limited here.

502. The network element 2 sends a query request to the network element 1.

In this embodiment, when network element 2 is the new-side UDM, and network element 1 is the old-side UDM, if the new-side UDM determines that the UE is still in the cutover process and there is no local UE context, the new-side UDM can send the old-side UDM to the old-side UDM. Initiate an AMF registration information query request, which can carry information such as user identification SUPI/GPSI. Specifically, the new-side UDM may determine that the user data of the UE is in the cutover state based on the configuration information provided by the UDR/NRF/OAM or the like. In this embodiment, the new-side UDM may learn the old-side UDM from the mapping relationship between the old-side UDM and SUPI configured by the OAM.

When network element 2 is the new PCF and network element 1 is the old PCF, the new PCF initiates a user context acquisition request to the old PCF to query the AMF/SMF information currently serving the target user.

503. The network element 1 sends the identifier of the network element 4 to the network element 2.

When network element 2 is the new side UDM, network element 4 is the AMF, the old side UDM returns a response message to the new side UDM, which can carry the identity of the AMF currently serving the UE, and the identity information can be used to uniquely identify the target AMF globally Network element, AMF NF instance ID (instance) and other information.

When the network element 2 is the new side PCF, the network element 4 is the AMF/SMF, that is, the old side PCF returns the AMF/SMF identifier or the AMF/SMF instance ID to the new side PCF.

504 . The network element 2 sends a request for obtaining the service information of the network element 4 to the network element 5 .

In this embodiment, network element 5 is an NRF. When network element 2 is a new-side UDM, the new-side UDM queries the NRF for service information of the AMF, such as the address and capabilities of the AMF, whether it supports voice services or the service name of the AMF, Version, host information. Through this step, the network element 2 can obtain the service information provided by the network element 4 , so as to initiate a service request to the network element 4 based on the service information, so as to obtain the event information required by the network element 3 .

When the network element 2 is the PCF on the new side, the PCF on the new side queries the NRF for the service information of the AMF/SMF.

505. The network element 5 sends the service information of the network element 4 to the network element 2.

In this embodiment, after receiving the acquisition request of the network element 2 , the NRF can query the corresponding service information according to the identifier of the network element 4 and return it to the network element 2 .

506. The network element 2 sends a request message to the network element 4.

When the network element 2 is the new side UDM, the new side UDM triggers to send a domain selection request to the AMF based on the query request received in step 501 to query the network where the UE is currently located, or send a UE location query request to the AMF, etc.

When the network element 2 is the PCF on the new side, the PCF on the new side initiates a policy authorization request to the AMF/SMF.

507. The network element 4 returns the request result to the network element 2.

The AMF can return the domain selection result or the UE information query result (such as the location of the UE in the 5G network) to the new side UDM.

The AMF/SMF may also return the result of the policy authorization request to the new-side PCF, where, if the policy authorization request includes an event subscription, the policy authorization request result may also include a corresponding event report.

If the policy authorization request includes an event subscription, the response message may also include a corresponding event report.

508. The network element 2 sends the response information to the network element 3.

After receiving the request result returned by the network element 4, the network element 2 can send the request result to the AF accordingly.

In the embodiment of the present application, when network element 2 receives the request message from network element 3, it needs to trigger a query request to network element 1 based on the cutover state, so as to avoid service interruption caused by network element 2 not being able to know the user context.

The communication method is described above, and the communication device according to the embodiments of the present application is described below with reference to the accompanying drawings.

FIG. 6 is a schematic diagram of an embodiment of a communication device 60 in an embodiment of the present application.

As shown in FIG. 6 , an embodiment of the present application provides a communication device, and the communication device includes:

a receiving unit 601, configured to receive a user list 1 from a network storage functional entity, where the users in the user list 1 are affected by the data cutover on the network element 1;

The reconstruction unit 602 is configured to reconstruct the context of the users in the user list 1 .

Optionally, the receiving unit 601 is specifically configured to: receive the message 1 from the network storage functional entity, the message 1 includes the user list 1 and the parameters of the network element 1, the parameters include the recovery time, and the recovery time is used to indicate the data on the network element 1. Recovery timestamp of the service provided after cutover.

Optionally, the user list 1 includes one or more of a user permanent identifier list, a general public subscription identifier list, a routing indication and a home network public key identifier.

Optionally, the communication device 60 is an access and mobility management functional entity, a session management functional entity, a short message service functional entity, a unified data management entity or a policy control functional entity.

Optionally, the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.

FIG. 7 is a schematic diagram of another embodiment of the communication device 70 in the embodiment of the present application.

As shown in FIG. 7 , an embodiment of the present application provides a communication device, and the communication device includes:

A receiving unit 701, configured to receive user list 1 from network element 1, where users in user list 1 are affected by data cutover on network element 1;

The sending unit 702 is configured to send the user list 1 to the network element 3.

Optionally, the network element 3 is an access and mobility management functional entity, a session management functional entity, a short message service functional entity, a unified data management entity or a policy control functional entity.

FIG. 8 is a schematic diagram of another embodiment of the communication device 80 in the embodiment of the present application.

As shown in FIG. 8 , an embodiment of the present application provides a communication device, and the communication device includes:

The receiving unit 801 is used to receive the user list 2 and the indication information from the network element 2. The users in the user list 2 are the users served by the network element 1 after the data on the network element 1 is cut over, and the indication information is used to indicate the reconstruction of the receiving network. The context of the user affected by the data cutover on element 1;

The determining unit 802 is configured to determine the user list 1 according to the indication information, the user list 2 and the user list 3. The users in the user list 3 are the users served by the network element 1 before the data cutover on the network element 1, and the users in the user list 1 of users are affected by the data cutover on NE 1;

The reconstruction unit 803 is configured to reconstruct the context of the users in the user list 1 .

Optionally, the determining unit 802 is specifically configured to:

Reconstruct the context of the user affected by the data cutover on NE 1 according to the indication information:

According to user list 2 and user list 3, user list 1 is determined.

Optionally, the user list 3 is included in the parameters of the network element 1 before the data cutover on the network element 1, and the user list 2 is included in the parameters of the network element 1 after the data cutover on the network element 1.

Optionally, the communication device 80 is an access and mobility management functional entity, a session management functional entity, a short message service functional entity, a unified data management entity or a policy control functional entity.

Optionally, the network element 2 is a network storage functional entity.

FIG. 9 is a schematic diagram of another embodiment of the communication device 90 in the embodiment of the present application.

As shown in FIG. 9 , an embodiment of the present application provides a communication device, and the communication device includes:

The receiving unit 901 is used to receive the user list 2 and the indication information from the network element 1. The users in the user list 2 are the users served by the network element 1 after the data on the network element 1 is cut over, and the indication information is used to indicate the reconstruction of the receiving network. The context of the user affected by the data cutover on element 1;

The sending unit 902 is configured to send the user list 2 and the indication information to the network element 3 .

Optionally, the communication device 90 is a network storage functional entity.

FIG. 10 is a schematic diagram of another embodiment of the communication device 100 in the embodiment of the present application.

As shown in FIG. 10 , an embodiment of the present application provides a communication device, and the communication device includes:

A determining unit 1001, configured to determine that the subscription data of the user is in a cutover state;

The sending unit 1002 is configured to send a cause value to the network element 3, where the cause value indicates that the subscription data of the user is in a cutover state.

Optionally, the sending unit 1002 is further configured to: send a timer to the network element 3, where the timer indicates that a registration process is initiated after the timer expires.

Optionally, the determining unit 1001 is specifically configured to: determine that the subscription data of the user is in a cutover state in the corresponding unified data storage entity.

Optionally, the communication device 100 is a unified data management entity.

Optionally, the network element 3 is an access and mobility management function entity, a session management function entity or a short message service function entity.

As shown in FIG. 11 , a schematic diagram of a possible logical structure of the communication device 110 provided by the embodiment of the present application is shown. The communication device 110 includes: a processor 1101 , a communication interface 1102 , a storage system 1103 and a bus 1104 . The processor 1101 , the communication interface 1102 , and the storage system 1103 are connected to each other through a bus 1104 . In this embodiment of the present application, the processor 1101 is configured to control and manage the actions of the communication device 110. For example, the processor 1101 is configured to execute the steps performed by the network element 3 in the method embodiment of FIG. 2 . The communication interface 1102 is used to support the communication device 110 to communicate. The storage system 1103 is used for storing program codes and data of the communication device 110 .

The processor 1101 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 1101 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1104 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 11, but it does not mean that there is only one bus or one type of bus.

The receiving unit 601 in the communication device 60 is equivalent to the communication interface 1102 in the communication device 110 , and the reconstruction unit 602 in the communication device 60 is equivalent to the processor 1101 in the communication device 110 .

The communication device 110 in this embodiment may correspond to the network element in the foregoing method embodiment in FIG. 2 , and the communication interface 1102 in the communication device 110 may implement the functions and/or functions of the network element 3 in the foregoing method embodiment in FIG. 2 . For the sake of brevity, the various steps implemented are not repeated here.

As shown in FIG. 12 , a schematic diagram of a possible logical structure of the communication device 120 provided by the embodiment of the present application is shown. The communication device 120 includes: a processor 1201 , a communication interface 1202 , a storage system 1203 and a bus 1204 . The processor 1201 , the communication interface 1202 , and the storage system 1203 are connected to each other through a bus 1204 . In this embodiment of the present application, the processor 1201 is configured to control and manage the actions of the communication device 120. For example, the processor 1201 is configured to execute the steps performed by the network element 2 in the method embodiment of FIG. 2 . The communication interface 1202 is used to support the communication device 120 to communicate. The storage system 1203 is used to store program codes and data of the communication device 120 .

The processor 1201 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 1201 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1204 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 12, but it does not mean that there is only one bus or one type of bus.

The receiving unit 701 and the transmitting unit 702 in the communication device 70 are equivalent to the communication interface 1202 in the communication device 120 .

The communication device 120 in this embodiment may correspond to the network element in the foregoing method embodiment in FIG. 2 , and the communication interface 1202 in the communication device 120 may implement the functions and/or functions of the network element 2 in the foregoing method embodiment in FIG. 2 . For the sake of brevity, the various steps implemented are not repeated here.

As shown in FIG. 13 , a schematic diagram of a possible logical structure of the communication device 130 according to the embodiment of the present application is shown. The communication device 130 includes: a processor 1301 , a communication interface 1302 , a storage system 1303 and a bus 1304 . The processor 1301 , the communication interface 1302 , and the storage system 1303 are connected to each other through a bus 1304 . In the embodiment of the present application, the processor 1301 is configured to control and manage the actions of the communication device 130. For example, the processor 1301 is configured to execute the steps performed by the network element 3 in the method embodiment of FIG. 3 . The communication interface 1302 is used to support the communication device 130 to communicate. The storage system 1303 is used to store program codes and data of the communication device 130 .

The processor 1301 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 1301 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1304 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.

The receiving unit 801 in the communication device 80 is equivalent to the communication interface 1302 in the communication device 130 , and the determining unit 802 and the reconstructing unit 803 in the communication device 80 are equivalent to the processor 1301 in the communication device 130 .

The communication device 130 in this embodiment may correspond to the network element 3 in the foregoing method embodiment of FIG. 3 , and the communication interface 1302 in the communication device 130 may implement the functions of the network element 3 in the foregoing method embodiment of FIG. 3 and/or For the sake of brevity, various steps to be implemented are not repeated here.

As shown in FIG. 14 , a schematic diagram of a possible logical structure of the communication device 140 provided by the embodiment of the present application is shown. The communication device 140 includes a processor 1401 , a communication interface 1402 , a storage system 1403 and a bus 1404 . The processor 1401 , the communication interface 1402 , and the storage system 1403 are connected to each other through a bus 1404 . In the embodiment of the present application, the processor 1401 is configured to control and manage the actions of the communication device 140. For example, the processor 1401 is configured to execute the steps performed by the network element 2 in the method embodiment of FIG. 3 . The communication interface 1402 is used to support the communication device 140 to communicate. The storage system 1403 is used to store program codes and data of the communication device 140 .

The processor 1401 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 1401 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1404 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is shown in FIG. 14, but it does not mean that there is only one bus or one type of bus.

The receiving unit 901 and the transmitting unit 902 in the communication device 90 are equivalent to the communication interface 1402 in the communication device 140 .

The communication device 140 in this embodiment may correspond to the network element 2 in the foregoing method embodiment of FIG. 3 , and the communication interface 1402 in the communication device 140 may implement the functions of the network element 2 in the foregoing method embodiment of FIG. 3 and/or For the sake of brevity, various steps to be implemented are not repeated here.

As shown in FIG. 15 , a schematic diagram of a possible logical structure of the communication device 150 provided by the embodiment of the present application is shown. The communication device 150 includes: a processor 1501 , a communication interface 1502 , a storage system 1503 and a bus 1504 . The processor 1501 , the communication interface 1502 , and the storage system 1503 are connected to each other through a bus 1504 . In this embodiment of the present application, the processor 1501 is configured to control and manage the actions of the communication device 150. For example, the processor 1501 is configured to execute the steps performed by the network element 1 in the method embodiment of FIG. 4 . The communication interface 1502 is used to support the communication device 150 to communicate. The storage system 1503 is used to store program codes and data of the communication device 150 .

The processor 1501 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 1501 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is shown in FIG. 15, but it does not mean that there is only one bus or one type of bus.

The sending unit 1002 in the communication device 100 is equivalent to the communication interface 1502 in the communication device 150 , and the determining unit 1001 in the communication device 100 is equivalent to the processor 1501 in the communication device 150 .

The communication device 150 in this embodiment may correspond to the network element 1 in the foregoing method embodiment in FIG. 4 , and the communication interface 1502 in the communication device 150 may implement the functions and/or functions of the network element 1 in the foregoing method embodiment in FIG. 4 . For the sake of brevity, various steps to be implemented are not repeated here.

In another embodiment of the present application, a computer-readable storage medium is also provided, where computer-executable instructions are stored in the computer-readable storage medium. When the processor of the device executes the computer-executable instructions, the device executes the above-mentioned method in FIG. 2 . Steps of the communication method performed by the network element 3.

In another embodiment of the present application, a computer-readable storage medium is also provided, where computer-executable instructions are stored in the computer-readable storage medium. When the processor of the device executes the computer-executable instructions, the device executes the above-mentioned method in FIG. 2 . Steps of the communication method performed by the network element 2.

In another embodiment of the present application, a computer-readable storage medium is also provided, where computer-executable instructions are stored in the computer-readable storage medium, and when the processor of the device executes the computer-executable instructions, the device executes the above-mentioned FIG. 3 Steps of the communication method performed by the network element 3.

In another embodiment of the present application, a computer-readable storage medium is also provided, where computer-executable instructions are stored in the computer-readable storage medium, and when the processor of the device executes the computer-executable instructions, the device executes the above-mentioned FIG. 3 Steps of the communication method performed by the network element 2.

In another embodiment of the present application, a computer-readable storage medium is also provided, where computer-executable instructions are stored in the computer-readable storage medium. When the processor of the device executes the computer-executable instructions, the device executes the above-mentioned FIG. 4 The steps of the communication method performed by the network element 1.

In another embodiment of the present application, a computer program product is also provided, the computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; when a processor of a device executes the computer-executable instructions , the device executes the steps of the communication method executed by the network element 3 in the above FIG. 2 .

In another embodiment of the present application, a computer program product is also provided, the computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; when a processor of a device executes the computer-executable instructions , the device executes the steps of the communication method executed by the network element 2 in the above FIG. 2 .

In another embodiment of the present application, a computer program product is also provided, the computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; when a processor of a device executes the computer-executable instructions , the device executes the steps of the communication method executed by the network element 3 in the above FIG. 3 .

In another embodiment of the present application, a computer program product is also provided, the computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; when a processor of a device executes the computer-executable instructions , the device executes the steps of the communication method executed by the network element 2 in FIG. 3 .

In another embodiment of the present application, a computer program product is also provided, the computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; when a processor of a device executes the computer-executable instructions , the device executes the steps of the communication method executed by the network element 1 in the above FIG. 4 .

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , which includes several instructions for causing a communication device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program codes .

Claims

A communication method, comprising:

Receive a user list 1 from the network storage functional entity, where the users in the user list 1 are affected by the data cutover on the network element 1;

Rebuild the context of the users in the user list 1.
The communication method according to claim 1, wherein the receiving the user list 1 from the network storage functional entity comprises:

Receive message 1 from the network storage function entity, the message 1 includes the user list 1 and the parameters of the network element 1, the parameters include a recovery time, and the recovery time is used to indicate the network element 1 The recovery timestamp of the service provided after the data cutover on the .
The communication method according to any one of claims 1-2, wherein the user list 1 includes one or more of a user permanent identity list, a universal public subscription identity list, a routing indication and a home network public key identity indivual.
The communication method according to any one of claims 1-2, characterized in that, the execution subject of the method is an access and mobility management function entity, a session management function entity, a short message service function entity, and a unified data management entity or policy control functional entity.
The communication method according to any one of claims 1-2, wherein the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.
A communication method, comprising:

Receive the user list 2 and the indication information from the network element 2, where the users in the user list 2 are the users served by the network element 1 after the data on the network element 1 is cut over, and the indication information is used to instruct the reconstruction of the receiving network The context of the user affected by the data cutover on element 1;

According to the indication information, the user list 2 and the user list 3, determine the user list 1, and the users in the user list 3 are the users served by the network element 1 before the data on the network element 1 is cut over, The users in the user list 1 are affected by the data cutover on the network element 1;

Rebuild the context of the users in the user list 1.
The communication method according to claim 6, wherein determining the user list 1 according to the indication information, the user list 2 and the user list 3 comprises:

Rebuild the context of the user affected by the data cutover on network element 1 according to the indication information:

According to the user list 2 and the user list 3, the user list 1 is determined.
The communication method according to claim 6, wherein the user list 3 is included in the parameters of the network element 1 before data cutover on the network element 1, and the user list 2 is included in the in the parameters of the network element 1 after the data cutover on the network element 1.
The communication method according to any one of claims 6-8, characterized in that, the execution subject of the method is an access and mobility management function entity, a session management function entity, a short message service function entity, and a unified data management entity or policy control functional entity.
The communication method according to any one of claims 6-8, wherein the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.
The method according to any one of claims 6-8, wherein the network element 2 is a network storage functional entity.
A communication method, comprising:

Determine that the user's subscription data is in the cutover state;

A cause value is sent to the network element 3, where the cause value indicates that the subscription data of the user is in a cutover state.
The communication method according to claim 12, wherein after determining that the subscription data of the user is in a cutover state, the method further comprises:

Send a timer to the network element 3, where the timer indicates that a registration process is initiated after the timer expires.
The communication method according to claim 12 or 13, wherein the determining that the subscription data of the user is in a cutover state comprises:

It is determined that the subscription data of the user is in a cutover state in the corresponding unified data storage entity.
The communication method according to claim 12 or 13, wherein the execution body of the method is a unified data management entity.
The communication method according to claim 12 or 13, wherein the network element 3 is an access and mobility management function entity, a session management function entity or a short message service function entity.
A communication device, comprising:

a receiving unit, configured to receive the user list 1 from the network storage functional entity, where the users in the user list 1 are affected by the data cutover on the network element 1;

A reconstruction unit, configured to reconstruct the context of the users in the user list 1 .
The communication device according to claim 17, wherein the receiving unit is specifically configured to:

Receive message 1 from the network storage function entity, where the message 1 includes the user list 1 and the parameters of the network element 1, the parameters include a recovery time, and the recovery time is used to indicate the network element 1 The recovery timestamp of the service provided after the data cutover on .
The communication device according to any one of claims 17-18, wherein the user list 1 includes one or more of a user permanent identity list, a general public subscription identity list, a routing indication and a home network public key identity indivual.
The communication device according to any one of claims 17-18, wherein the communication device is an access and mobility management function entity, a session management function entity, a short message service function entity, a unified data management entity or a policy Control functional entities.
The communication device according to any one of claims 17-18, wherein the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.
A communication device, comprising:

The receiving unit is configured to receive the user list 2 and the indication information from the network element 2. The users in the user list 2 are the users served by the network element 1 after the data on the network element 1 is cut over. to indicate the re-establishment of the context of the user affected by the data cutover on network element 1;

a determining unit, configured to determine a user list 1 according to the indication information, the user list 2 and the user list 3, where the users in the user list 3 are the network elements before the data cutover on the network element 1 1 users of the service, the users in the user list 1 are affected by the data cutover on the network element 1;

A reconstruction unit, configured to reconstruct the context of the users in the user list 1 .
The communication device according to claim 22, wherein the determining unit is specifically configured to:

Rebuild the context of the user affected by the data cutover on network element 1 according to the indication information:

According to the user list 2 and the user list 3, the user list 1 is determined.
The communication device according to claim 22, wherein the user list 3 is included in the parameters of the network element 1 before data cutover on the network element 1, and the user list 2 is included in the in the parameters of the network element 1 after the data cutover on the network element 1.
The communication device according to any one of claims 22-24, wherein the communication device is an access and mobility management function entity, a session management function entity, a short message service function entity, a unified data management entity or a policy Control functional entities.
The communication device according to any one of claims 22-24, wherein the network element 1 is a unified data management entity, a unified data storage entity or a policy control function entity.
The communication device according to any one of claims 22-24, wherein the network element 2 is a network storage functional entity.
A communication device, comprising:

a determining unit, used for determining that the subscription data of the user is in a cutover state;

The sending unit is configured to send a cause value to the network element 3, where the cause value indicates that the subscription data of the user is in a cutover state.
The communication device according to claim 28, wherein the sending unit is further configured to:

Send a timer to the network element 3, where the timer indicates that a registration process is initiated after the timer expires.
The communication device according to claim 28 or 29, wherein the determining unit is specifically configured to:

It is determined that the subscription data of the user is in a cutover state in the corresponding unified data storage entity.
The communication device according to claim 28 or 29, wherein the communication device is a unified data management entity.
The communication device according to claim 28 or 29, wherein the network element 3 is an access and mobility management function entity, a session management function entity or a short message service function entity.
A communication device, comprising: a processor and a memory,

The processor is configured to execute instructions stored in the memory to cause the communication device to perform the method of any one of claims 1 to 5.
A communication device, comprising: a processor and a memory,

The processor is configured to execute instructions stored in the memory, causing the communication device to perform the method of any one of claims 6 to 11.
A communication device, comprising: a processor and a memory,

The processor is adapted to execute instructions stored in the memory, causing the communication device to perform the method of any one of claims 12 to 16.
A computer-readable storage medium, characterized in that, a computer program is stored in the computer-readable storage medium, and when the computer program is executed on the computer, the computer is made to execute as in claims 1 to 16 The method of any one.
A computer program product, characterized in that, when the computer program product is executed on a computer, the computer executes the method according to any one of claims 1 to 16.