Terminal registration processing method, communication device, communication system, and storage medium

Abstract

Provided in the embodiments of the present disclosure are a terminal registration method, a communication device, a communication system, and a storage medium. The terminal registration method comprises: a first core network function receiving a first message of a user equipment, wherein the first message is used for access registration of the user equipment; and the first core network function determining that the user equipment has a first registration and accepting a second registration of the user equipment, and determining not to cancel the first registration, wherein the first registration is a registration initiated by the user equipment by means of a first 3GPP access network; the second registration is a registration initiated by the user equipment by means of a second 3GPP access network; and the first 3GPP access network is different from the second 3GPP access network.

Description

Terminal registration processing method, communication equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a terminal registration processing method and apparatus, communication equipment, a communication system, and a storage medium. Background Art

[0002] A terminal is also called a user equipment (UE). When powered on or out of flight mode in an area with network coverage, the terminal requests network registration. The network assigns the terminal a Globally Unique Temporary User Identity (GUTI). The terminal can then use the network's communication services based on the GUTI.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a terminal registration processing method and apparatus, a communication device, a communication system, and a storage medium to support dual 3rd Generation Partnership Project (3GPP) access registration of a terminal.

[0005] According to a first aspect of an embodiment of the present disclosure, a terminal registration method is provided, wherein the method includes:

[0006] The first core network function receives a first message from a terminal, where the first message is used for access registration of the terminal;

[0007] The first core network function determines that the terminal has a first registration and accepts a second registration of the terminal, and determines not to cancel the first registration;

[0008] The first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0009] According to a second aspect of an embodiment of the present disclosure, a terminal registration method is provided, wherein the method includes:

[0010] The terminal sends a first message to the first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, where the first information is used by the first core network function to determine whether the terminal has a first registration.

[0011] According to a third aspect of an embodiment of the present disclosure, a terminal registration method is provided, wherein the method includes:

[0012] receiving a second message sent by the first core network function; the second message including second information, the second information being used to indicate that the first registration of the terminal is not to be canceled when the second registration of the terminal is accepted;

[0013] According to the second message, cancellation of the first registration is not initiated in case the second registration of the terminal is accepted.

[0014] According to a fourth aspect of the present disclosure, a terminal registration method is provided, wherein the method includes:

[0015] The second core network function receives a third message sent by the first core network function; the third message includes: registration information of the terminal;

[0016] The terminal has a first registration and accepts a second registration of the terminal, and determines not to cancel the first registration.

[0017] According to a fifth aspect of an embodiment of the present disclosure, a first core network function is provided, including:

[0018] a receiving module, configured to receive a first message from a terminal, where the first message is used for access registration of the terminal;

[0019] A processing module is configured to determine that the terminal has a first registration and accepts the second registration of the terminal, and determine not to cancel the first registration; the first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0020] According to a sixth aspect of an embodiment of the present disclosure, a terminal is provided, comprising:

[0021] The sending module is configured to send a first message from the terminal to the first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, which is used by the first core network function to determine whether the terminal has a first registration.

[0022] According to a seventh aspect of an embodiment of the present disclosure, a second core network function is provided, including:

[0023] a receiving module configured to receive a second message sent by the first core network function; the second message including second information, the second information being used to indicate that the first registration of the terminal is not to be canceled when the second registration of the terminal is accepted;

[0024] The processing module is configured to, according to the second message, not initiate cancellation of the first registration when accepting the second registration of the terminal.

[0025] According to a seventh aspect of an embodiment of the present disclosure, a second core network function is provided, including:

[0026] A receiving module configured to receive a third message sent by the first core network function; the third message includes: registration information of the terminal;

[0027] The processing module is configured to determine not to cancel the first registration when the terminal has a first registration and it is determined based on the third message that the second registration of the terminal is accepted.

[0028] According to an eighth aspect of an embodiment of the present disclosure, a communication system is provided, wherein the system includes:

[0029] The terminal is configured to implement the method according to any one of the first aspects;

[0030] The first core network function is configured to implement the method described in any one of the second aspects;

[0031] The second core network function is configured to implement the method described in any one of the third aspects.

[0032] According to a ninth aspect of the embodiments of the present disclosure, a communication system is provided, wherein the system includes:

[0033] The second core network device implements the method described in any one of the fourth aspects.

[0034] According to the tenth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the terminal registration method provided by the first aspect, the second aspect, the third aspect and / or the fourth aspect.

[0035] The technical solution provided by the embodiment of the present disclosure determines not to cancel the first registration, that is, to maintain the first registration, when it is determined to accept the second registration of the terminal. In this way, the terminal can register with the network through multiple 3GPP access networks, thereby enhancing the reliability of data interaction and service quality.

[0036] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0038] FIG1 is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0039] FIG2A is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0040] FIG2B is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0041] FIG3 is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0042] FIG4 is a schematic flow chart showing a terminal registration method according to an exemplary embodiment;

[0043] FIG5 is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0044] FIG6 is a schematic flow chart showing a terminal registration method according to an exemplary embodiment;

[0045] FIG7A is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0046] FIG7B is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0047] FIG7C is a schematic diagram showing a flow chart of a terminal registration method according to an exemplary embodiment;

[0048] FIG8A is a schematic structural diagram of a first core network function according to an exemplary embodiment;

[0049] FIG8B is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0050] FIG8C is a schematic structural diagram of a second core network function according to an exemplary embodiment;

[0051] FIG8D is a schematic structural diagram of a second core network function according to an exemplary embodiment;

[0052] FIG9A is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0053] Fig. 9B is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0054] Embodiments of the present disclosure provide a terminal registration method and apparatus, a communication device, a communication system, and a storage medium.

[0055] In a first aspect, an embodiment of the present disclosure provides a terminal registration method, which includes:

[0056] The first core network function receives a first message from a terminal, where the first message is used for access registration of the terminal;

[0057] The first core network function determines that the terminal has a first registration and accepts a second registration of the terminal, and determines not to cancel the first registration;

[0058] The first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0059] Based on the above embodiment, when it is determined to accept the second registration of the terminal, it is determined not to cancel the first registration, that is, to maintain the first registration. In this way, the terminal can register with the network through multiple 3GPP access networks, thereby enhancing the reliability of data interaction and service quality.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the first core network function determines that the terminal has a first registration and accepts the second registration of the terminal, and determines not to cancel the first registration, including:

[0061] The first core network function determines that the terminal has a first registration, accepts a second registration of the terminal, and the terminal supports dual registration, and determines not to cancel the first registration.

[0062] In the above embodiment, when the first core network function determines that the terminal supports dual registration, the second registration is accepted and the first registration is determined not to be cancelled, that is, the dual 3GPP access registration of the terminal is allowed according to the dual registration capability of the terminal.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the first core network function is an access management function; and the first message is a registration request message of the terminal.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal selects the same access management function for the first registration and the second registration, and determining that the terminal has the first registration further includes:

[0065] The access management function determines that the terminal has the first registration based on the stored first registration information of the terminal.

[0066] Based on the above solution, if the first registration and second registration of the terminal select the same AMF, the AMF can know that the terminal already has the first registration based on the saved first registration information.

[0067] In combination with some embodiments of the first aspect, in some embodiments, the first registration information includes at least a user identifier and / or a wireless access type.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the first core network function is an access management function that provides services to the second terminal; the terminal selects different access management functions for the first registration and the second registration; and determining that the terminal has the first registration further includes:

[0069] The access management function determines that the terminal has a first registration based on the first information of the first message.

[0070] In the above embodiment, since the first registration and the second registration select different AMFs, the AMF selected for the second registration can determine that the terminal has the first registration based on the information related to the first registration carried in the first information.

[0071] In combination with some embodiments of the first aspect, in some embodiments, the first information is a globally unique temporary user equipment identifier GUTI allocated to the terminal after the terminal successfully registers through the first 3GPP access.

[0072] Based on the above scheme, if the terminal has a first registration, the terminal will obtain the GUTI assigned by the network and carry the GUTI in the registration request message of the second registration. When the first registration and the second registration select different AMFs, the AMF accepting the second registration can directly determine that the terminal has a first registration based on the GUTI in the first information.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0074] A second message is sent to the second core network function, where the second message includes second information, and the second information is used to indicate that the first registration is not to be canceled.

[0075] In a second aspect, an embodiment of the present disclosure provides a terminal registration method, including:

[0076] The terminal sends a first message to the first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, where the first information is used by the first core network function to determine whether the terminal has a first registration.

[0077] In combination with some embodiments of the second aspect, in some embodiments, the access management function selected by the first registration is different from the access management function selected by the second registration, and the first information is used to indicate that the terminal already has a first registration and / or information of the first registration.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the first information is the GUTI of the terminal corresponding to the first registration.

[0079] Based on the above solution, the terminal carries the GUTI in the first message and indicates to the AMF or UDM selected for the second registration that the terminal has the first registration.

[0080] According to a third aspect, a terminal registration method is provided, which is performed by a second core network function, and the method further includes:

[0081] receiving a second message sent by the first core network function; the second message including second information, the second information being used to indicate that the first registration of the terminal is not to be canceled when the second registration of the terminal is accepted;

[0082] According to the second message, cancellation of the first registration is not initiated in case the second registration of the terminal is accepted.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the terminal supports dual registration, and the second message includes the second information.

[0084] Based on the above solution, when the first core network function determines that the terminal supports dual registration, the second information is carried in the second message. In this case, the second core network function can determine whether it is necessary to initiate the cancellation process of the first registration based on whether the second message contains the second information.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0086] A fourth aspect provides an information processing method, comprising:

[0087] The second core network function receives a third message sent by the first core network function; the third message includes: registration information of the terminal;

[0088] When the terminal has a first registration and a second registration of the terminal is accepted, it is determined not to cancel the first registration.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, when the terminal has a first registration and accepts a second registration of the terminal, determining not to cancel the first registration includes:

[0090] When the terminal has a first registration, a second registration of the terminal is accepted, and the terminal supports dual registration, determining not to cancel the second registration.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the second core network function is a user data management function;

[0092] The third message includes third information; the third information includes the first registration and / or second registration information of the terminal.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the third information includes at least one of the following:

[0094] the first registered user identifier;

[0095] the wireless access type of the first registration;

[0096] an access management function of the first registration;

[0097] the second registered user identifier;

[0098] the wireless access type of the second registration;

[0099] The access management function of the second registration.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0101] The second core network function determines whether the terminal supports dual registration according to the subscription information of the terminal.

[0102] In a fifth aspect, a first core network function is provided, including:

[0103] a receiving module, configured to receive a first message from a terminal, where the first message is used for access registration of the terminal;

[0104] A processing module is configured to determine that the terminal has a first registration and accepts the second registration of the terminal, and determine not to cancel the first registration; the first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0105] According to a sixth aspect, a terminal is provided, comprising:

[0106] The sending module is configured to send a first message from the terminal to the first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, which is used by the first core network function to determine whether the terminal has a first registration.

[0107] In a seventh aspect, a second core network function is provided, including:

[0108] a receiving module configured to receive a second message sent by the first core network function; the second message including second information, the second information being used to indicate that the first registration of the terminal is not to be canceled when the second registration of the terminal is accepted;

[0109] The processing module is configured to, according to the second message, not initiate cancellation of the first registration when accepting the second registration of the terminal.

[0110] In an eighth aspect, a second core network function is provided, including:

[0111] A receiving module configured to receive a third message sent by the first core network function; the third message includes: registration information of the terminal;

[0112] The processing module is configured to determine not to cancel the first registration when the terminal has a first registration and accepts a second registration of the terminal.

[0113] In the ninth aspect, a communication system is provided, wherein the communication system includes a terminal, a first core network function and a second core network function; the terminal is configured to execute the terminal registration method provided by any technical solution of the first aspect, the first core network function is configured to execute the terminal registration method provided by any technical solution of the second aspect, and the second core network function is configured to execute the terminal registration method provided by any technical solution of the third aspect.

[0114] In the tenth aspect, a communication system is provided, wherein the communication system includes: a second core network function, and the second core network function is configured to execute the terminal registration method provided by any technical solution of the fourth aspect.

[0115] In an eleventh aspect, an embodiment of the present disclosure provides a communication device, the communication device including: one or more processors;

[0116] The processor is configured to call instructions to enable the communication device to execute the terminal registration method described in the optional implementation manners of the first to fourth aspects.

[0117] In the twelfth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the terminal registration method described in the optional implementation methods of the first to fourth aspects.

[0118] In a thirteenth aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the terminal registration method described in the optional implementation of the first to fourth aspects.

[0119] In a fourteenth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the terminal registration method described in the optional implementation manners of the first to fourth aspects.

[0120] It is understandable that the above-mentioned terminal, the first core network function, the second core network function, the communication system, the program product, and the computer program are all used to perform the method provided by the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0121] The present disclosure provides a terminal registration method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method," "information processing method," and "terminal registration method" are interchangeable; the terms "information indicating device," "information processing device," and "information transmission device" are interchangeable; and the terms "communication system," "information processing system," and "information processing system" are interchangeable.

[0122] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0123] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0124] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0125] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0126] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0127] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0128] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0129] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0130] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0131] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0132] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0133] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0134] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0135] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0136] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0137] In some embodiments, the terms "terminal", "terminal device", "user equipment (terminal)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0138] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0139] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0140] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0141] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0142] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0143] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0144] As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , a core network device 103 , a first device 104 , and a second device 105 .

[0145] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0146] In some embodiments, a terminal is also referred to as a user equipment (User Equipment, terminal).

[0147] In some embodiments, the access network device 102 can be, for example, a node or device that accesses the terminal to the wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0148] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0149] In some embodiments, the core network device may also be referred to as a core network function.

[0150] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0151] In some embodiments, the core network device 103 may be a single device including the first network element 1031, or may be multiple devices or a group of devices, each including the first network element 1031. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0152] In some embodiments, the first network element 1031 is, for example, an access and mobility management function (AMF).

[0153] In some embodiments, the first network element 1031 is, for example, a Mobility Management Entity (MME).

[0154] In some embodiments, the first network element 1031 is used for access and mobility management, such as registration management, connection management, and mobility management, etc., but the name is not limited thereto.

[0155] In some embodiments, the first network element 1031 may be a network element independent of the core network device.

[0156] In some embodiments, the core network may further include a second network element, etc. The second network element may include: User Data Management (UDM), etc.

[0157] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0158] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0159] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems using other terminal registration methods, and next-generation systems based on these. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0160] Fifth-generation mobile communication (5G) systems aim to enable dual registration with the 5G Core (5GC) network through 3GPP access by a single subscriber. Previously, this dual registration was unsupported or impossible due to mutual radio interference. However, with 5G supporting various frequency bands, from sub-1 GHz to millimeter waves, this dual registration may become possible.

[0161] Example 1:

[0162] Networks can support different services. For example, Public Land Mobile Network (PLMN)-A supports data services, while PLMN-B supports voice services. A terminal needs to perform these multiple services (voice and data). In this case, the terminal needs to access both PLMNs to perform these services.

[0163] Example 2:

[0164] Implements steering, splitting, and switching of data transmission between two 3GPP access networks. These data operations require the terminal to register with multiple 3GPP access networks simultaneously based on a set of subscription information. These data transmission operations can aggregate data transmitted by the terminal on low-frequency New Radio (NR) access and high-frequency NR access, and can also implement data transmission switching between low-frequency NR access and high-frequency NR access.

[0165] The above application scenarios require users to support simultaneous registration with 5GC through multiple 3GPP access points. To meet this requirement, both the terminal and the network should support dual registration.

[0166] In some cases, terminals are supported to register through a single 3GPP access. For example, the fifth generation mobile communication system (5GS) supports terminals to initiate registration through one 3GPP access or one 3GPP access and one non-3GPP access. However, it does not support terminals to initiate registration to the 5GC using multiple 3GPP accesses at the same time. During terminal registration, if the network receives the registration of the terminal, the AMF serving the terminal registration sends registration information to the UDM through the Nudm_UECM_Registration message. This registration information may indicate the terminal access type, radio access technology (RAT) type and / or the AMF identifier serving the terminal. Subsequently, if the terminal initiates another registration request through another 3GPP access, when the UDM determines that the registration is the second registration of the terminal, the UDM sends a Nudm_UECM_Deregistration message to the serving AMF used for the previous registration to notify the AMF to cancel the first registration of the terminal. If this process is followed, the network does not support dual registration initiated by the terminal through multiple 3GPP accesses.

[0167] In view of this, FIG2A is an interactive diagram of a terminal registration method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a terminal registration method for a communication system 100, the method comprising:

[0168] S2101: The terminal sends a first message.

[0169] In some embodiments, the first message is used by the terminal to request registration.

[0170] In some embodiments, the first message may be a registration request message.

[0171] In some embodiments, the registration request message is used for a registration request initiated by a terminal through 3GPP access.

[0172] In some embodiments, the registration request message is a request for a second registration sent by the terminal when the terminal already has a first registration.

[0173] In some embodiments, the registration request message may include first information. The first information may be relevant information for the terminal to request the second registration.

[0174] The first information may include at least one of the following information related to the second registration:

[0175] Registration type information, indicating the registration type of the second registration;

[0176] A user identifier is used to identify a terminal. The user identifier includes but is not limited to a 5th Generation Globally Uniq Temporary Identity (5G-GUTI), a Subscription Concealed Identifier (SUCI) and / or a Permanent Equipment Identifier (PEI).

[0177] In some embodiments, the registration type information may be used to indicate whether the registration request of the terminal is an initial registration or a registration update.

[0178] The terminal sends a registration request message, which is transmitted to the core network. For example, the core network's AMF or MME receives the registration request message and determines whether the terminal currently has a first registration based on the information carried in the registration request message. This first registration is also a registration through the 3GPP access network.

[0179] In some embodiments, in the case where the terminal has a first registration, the first information may include a message related to the first registration.

[0180] For example, the information related to the first registration may include, but is not limited to, at least one of the following:

[0181] Registration type information of the first registration;

[0182] The user identifier corresponding to the first registration; illustratively, the user identifier may be a user identifier assigned by the network device after the first registration of the terminal is accepted by the network device;

[0183] Wireless access type information of the first registration.

[0184] In some embodiments, the first registration may be an existing registration of the terminal, and the second registration may be a registration currently requested by the terminal.

[0185] S2102: The first core network function determines not to cancel the first registration of the terminal.

[0186] In some embodiments, when the terminal has a first registration and a second registration of the terminal is accepted, the first core network function determines not to cancel the first registration of the terminal.

[0187] In some embodiments, not canceling the first registration of the terminal may be understood as maintaining the first registration of the terminal.

[0188] In some embodiments, when the terminal has a first registration, a second registration of the terminal is accepted, and the terminal supports dual registration, the first core network function determines not to cancel the first registration.

[0189] In the embodiment of the present disclosure, when the AMF or MME determines that the terminal already has a first registration and accepts the second registration of the terminal, it determines not to cancel the first registration. Here, determining not to cancel the first registration can be understood as maintaining the first registration.

[0190] In some embodiments, both the first registration and the second registration are registrations of the terminal based on 3GPP access. For example, the first registration is a registration initiated by the terminal through a first 3GPP access network (such as NR access), and the second registration is a registration initiated by the terminal based on a second 3GPP access network (such as NTN NR access). The first 3GPP access network and the second 3GPP access network may belong to wireless access networks supporting different communication standards, or the first 3GPP access network and the second 3GPP access network may be wireless access networks provided by different operators, etc. In short, the first 3GPP access network and the second 3GPP access network are different.

[0191] In some embodiments, if the terminal has a first registration and it is determined that the terminal supports dual registration, it is determined not to cancel the first registration.

[0192] In some embodiments, the terminal supporting dual registration may include at least one of the following:

[0193] The terminal has dual registration capability, for example, the terminal's software and hardware support dual registration;

[0194] The user's contract information indicates that the terminal has dual registration capability;

[0195] The terminal is configured with dual registration capability by the network device.

[0196] In some embodiments, the AMF may determine whether the terminal supports dual registration based on the terminal's contract information. For example, the terminal may determine whether the terminal supports dual registration based on locally cached contract information or contract information requested from the UDM. For another example, the AMF may send a query request to the UDM, which determines whether the terminal supports dual registration based on the contract information and returns a conclusion on whether the terminal supports dual registration to the AMF. The AMF may then determine whether the terminal supports dual registration based on the conclusion information.

[0197] In other embodiments, the AMF may determine whether the terminal supports dual registration based on local configuration or policy information.

[0198] In some embodiments, the terminal does not support dual registration and determines to cancel the first registration if the second registration is accepted.

[0199] In some embodiments, the AMF that receives the registration request message may be the AMF corresponding to both the first registration and the second registration of the terminal. The AMF may determine whether the terminal has the first registration based on at least one of the following methods:

[0200] The AMF may determine whether the terminal has the first registration based on the locally stored first registration information;

[0201] The AMF may determine whether the terminal has the first registration according to the first registration information received from the UDM;

[0202] The AMF may determine, based on the first information, whether the terminal has the first registration.

[0203] For example, when accepting the registration of the terminal, the AMF saves the registration information, thereby obtaining the first registration information stored locally.

[0204] In some embodiments, the AMF stores the first registration information in the UDM. When a terminal subsequently requests registration, the AMF may query the registration record from the UDM to receive the first registration information.

[0205] In some embodiments, the AMF may determine whether the terminal has the first registration based on information related to the first registration specified by the first information.

[0206] In some embodiments, the AMF corresponding to the first registration is different from the AMF corresponding to the second registration. In this case, the AMF may determine whether the terminal has the first registration based on at least one of the following methods:

[0207] The AMF may determine whether the terminal has the first registration based on the registration information received from the UDM;

[0208] The AMF may determine, based on the first information, whether the terminal has the first registration.

[0209] In some embodiments, the first registration information includes at least: a user identifier of the first registration and / or wireless access type information of the first registration.

[0210] S2103: The first core network function sends a second message to the second core network function.

[0211] In some embodiments, the second core network function may include but is not limited to UDM.

[0212] In some embodiments, the second message may be used to indicate a second registration of the accepting terminal.

[0213] In some embodiments, the second message may include second information.

[0214] In some embodiments, the second information may be used to indicate that the first registration is not to be cancelled.

[0215] Exemplarily, the second information may include one or more indication bits.

[0216] In some embodiments, the second message includes second information, and it can be considered that the first core network function instructs the second core network function through the second message not to cancel the first registration of the terminal.

[0217] In some embodiments, the second message does not include the second information, and it can be considered that the first core network function instructs the second core network function to cancel the first registration of the terminal through the second message.

[0218] In some embodiments, the second information includes information content indicating whether to cancel the first registration of the terminal. For example, the second information includes a first indication value indicating that the first registration of the terminal is not to be canceled. For another example, the second information includes a second indication value indicating that the first registration of the terminal is to be canceled.

[0219] S2104: The second core network function determines whether to initiate a process to cancel the first registration based on the second message.

[0220] In some embodiments, the second message includes second information, and it is determined not to initiate a process of canceling the first registration.

[0221] In some embodiments, the second message does not include the second information, and the second core network function initiates a process to cancel the first registration.

[0222] In some embodiments, if the second message includes second information and the second information indicates that the first registration is not to be canceled, it is determined not to initiate the first registration process.

[0223] In some embodiments, the second message includes second information and the second information indicates cancellation of the first registration, and the second core network function initiates a process of canceling the first registration.

[0224] In some embodiments, the process of initiating cancellation of the first registration by the second core network function may include but is not limited to: the UDM sends a deregistration instruction to the AMF or MME selected by the first registration. After receiving the deregistration instruction, the serving AMF or serving MME of the first registration executes the deregistration of the first registration of the terminal. The deregistration of the first registration here may be the cancellation of the first registration.

[0225] FIG2B is an interactive diagram illustrating a terminal registration method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to a terminal registration method for a communication system 100, the method comprising:

[0226] S2201: The terminal sends a first message.

[0227] Exemplarily, the information content of the first message sent by the terminal can be found in the relevant content of the embodiment corresponding to FIG2A , which will not be repeated here.

[0228] In some embodiments, the terminal sends a first message, and the first core network function receives the first message.

[0229] S2202: The first core network function accepts the second registration of the terminal and sends a third message to the second core network function.

[0230] In some embodiments, the first core network function may be AMF.

[0231] In some embodiments, the first core network function determines to accept the second registration of the terminal, and carries the registration information of the second registration in a third message to the second core network function.

[0232] In some embodiments, the third message includes third information.

[0233] The third information includes the first registration information and / or the second registration information of the terminal.

[0234] In some embodiments, the registration information of the first registration may include, but is not limited to, at least one of the following:

[0235] Registration type information of the first registration;

[0236] the user identifier corresponding to the first registration;

[0237] RAT type information of the first registration;

[0238] The identifier of the first registered serving AMF.

[0239] In another exemplary embodiment, the second registration information may be determined or generated by the first core network function. For example, if the first core network function determines to accept the second registration, it will allocate a GUTI corresponding to the second registration to the terminal. In this case, the third information may include the GUTI corresponding to the second registration.

[0240] In some embodiments, the registration information of the second registration may include, but is not limited to, at least one of the following:

[0241] Registration type information of the second registration;

[0242] The user ID corresponding to the second registration;

[0243] RAT type information of the second registration;

[0244] The identifier of the second registered serving AMF.

[0245] S2203: The second core network function determines whether to cancel the first registration.

[0246] In some embodiments, the second core network function determines that the terminal supports dual registration and determines not to cancel the first registration.

[0247] In some embodiments, the second core network function determines that the terminal does not support dual registration and determines to cancel the first registration.

[0248] In some embodiments, after receiving the third message, the second core network function determines whether the terminal has the first registration based on the registration information of the terminal.

[0249] In some embodiments, the second core network function determines whether the terminal supports dual registration based on user subscription information when the terminal has a first registration.

[0250] S2204: The second core network function triggers the process of canceling the first registration.

[0251] In some embodiments, the terminal does not support dual registration, and the second core network function triggers the process of canceling the first registration.

[0252] Exemplarily, the process of triggering cancellation of the first registration may include:

[0253] The second core network function sends a cancellation notification of the first registration to the first core network function serving the first registration.

[0254] In some embodiments, the second core network function may include but is not limited to UDM.

[0255] In some embodiments, the first core network function may include but is not limited to AMF.

[0256] In some embodiments, the third message includes the first information.

[0257] In some embodiments, the first information indicates information of the first registration and / or the second registration of the terminal.

[0258] In some embodiments, the first information includes at least one of the following:

[0259] the first registered user identifier;

[0260] the wireless access type of the first registration;

[0261] an access management function of the first registration;

[0262] the second registered user identifier;

[0263] the wireless access type of the second registration;

[0264] The access management function of the second registration.

[0265] As shown in Figure 3, an embodiment of the present disclosure provides a terminal registration method, which is executed by a first core network function. The method may include: S3101: receiving a first message.

[0266] In some embodiments, a first message sent by a terminal is received.

[0267] In some embodiments, a first message from a terminal forwarded by an access network is received.

[0268] In some embodiments, the first message is used for access registration of the terminal.

[0269] In some embodiments, the relevant content of the first message can be found in the relevant part of the embodiment corresponding to Figure 2A.

[0270] S3102: Accept the second registration of the terminal and determine whether to cancel the first registration of the terminal.

[0271] In some embodiments, an optional embodiment in which the first core network function determines whether to cancel the first registration can be found in the relevant description of the corresponding embodiment of Figure 2A.

[0272] In some embodiments, the first core network function may determine whether the terminal has the first registration based on at least one of the following information:

[0273] determining, based on registration information locally stored by the first core network function, whether the terminal has a first registration;

[0274] The first core network function determines, based on the registration information requested from the second core network function, whether the terminal has the first registration;

[0275] The first core network function sends a query request to the second core network function, receives a query response returned by the second core network function, and determines whether the terminal has the first registration based on the query response;

[0276] The first core network function determines whether the terminal has the first registration based on the first information in the first message.

[0277] In some embodiments, the first information may include at least one of the following:

[0278] First registered user ID;

[0279] A registration indication, used to indicate that the terminal has a first registration;

[0280] Access type information of the first registration;

[0281] RAT type information of the first registration;

[0282] The first registered AMF identity.

[0283] Exemplarily, it is determined whether the terminal supports dual registration. If the terminal supports dual registration, it is determined that the second registration of the terminal is accepted while determining not to cancel the first registration of the terminal.

[0284] As another example, when the terminal does not support dual registration, it is determined that the second registration of the terminal is accepted while simultaneously determining that the first registration of the terminal is cancelled.

[0285] In some embodiments, the first core network function determines whether the terminal supports dual registration based on user subscription information.

[0286] In other embodiments, the first core network function sends a query request to the second core network function (eg, UDM), receives a query response returned by the second core network function, and determines whether the terminal supports dual registration based on the query response.

[0287] In some embodiments, the first core network function may also determine whether the terminal supports dual registration based on the type of the terminal and / or local configuration.

[0288] In some embodiments, the first core network function may be a service AMF shared by the first registration and second registration of the terminal.

[0289] In other embodiments, the first core network function may be the second registered service AMF of the terminal, and the second registered service AMF is different from the first registered service AMF.

[0290] S3103: The first core network function sends a second message.

[0291] In some embodiments, when it is determined not to cancel the first registration of the terminal, the second message may include second information.

[0292] In some embodiments, the second message includes second information indicating that the first registration of the terminal is not to be cancelled.

[0293] In some embodiments, the second message does not include the second information, indicating cancellation of the first registration of the terminal.

[0294] In some embodiments, the second message includes second information, and information content of the second information indicates that the first registration of the terminal is not to be cancelled.

[0295] In some embodiments, the second message does not include the second information, and the information content of the second information indicates cancellation of the first registration of the terminal.

[0296] In some embodiments, the first core network function sends the second message to the second core network function.

[0297] In some embodiments, the second core network function may be UDM.

[0298] As shown in Figure 4, an embodiment of the present disclosure provides a terminal registration method, which is performed by a second core network function. The method may include:

[0299] S4101: The second core network function receives the second message.

[0300] In some embodiments, the second core network function may include, but is not limited to, UDM.In some embodiments, the second core network function receives the second message from the first core network function.

[0301] In some embodiments, the second message may include second information.

[0302] In some embodiments, the second information may be used to indicate that the first registration is not to be cancelled.

[0303] Exemplarily, the second information may include one or more indication bits.

[0304] In some embodiments, the second message includes second information, and it can be considered that the first core network function instructs the second core network function through the second message not to cancel the first registration of the terminal.

[0305] In some embodiments, the second message does not include the second information, and it can be considered that the first core network function instructs the second core network function to cancel the first registration of the terminal through the second message.

[0306] In some embodiments, the second information includes information content indicating whether to cancel the first registration of the terminal. For example, the second information includes a first indication value indicating that the first registration of the terminal is not to be canceled. For another example, the second information includes a second indication value indicating that the first registration of the terminal is to be canceled.

[0307] It is worth noting that: the relevant description of the second message here can be found in the corresponding content of the embodiment corresponding to Figure 2A, and will not be repeated here.

[0308] S4102: The second core network function determines whether to cancel the first registration of the terminal.

[0309] In some embodiments, the second core network function determines whether to cancel the first registration of the terminal based on the second message.

[0310] In some other embodiments, the second core network function determines not to cancel the first registration of the terminal when the second message includes the second information.

[0311] In some further embodiments, the second core network function determines to cancel the first registration of the terminal when the second message does not include the second information.

[0312] In some other embodiments, the second core network function determines whether to cancel the first registration of the terminal based on information content of the second information included in the second message.

[0313] S4103: The second core network function initiates the process of canceling the first registration.

[0314] In some embodiments, when the first registration is canceled, the second core network function initiates a process of canceling the first registration.

[0315] For example, how to cancel the first registration may refer to the relevant description of the embodiment corresponding to FIG. 2A .

[0316] In other embodiments, if the first registration is not cancelled, step S4104 does not need to be performed. That is, step S4104 may be an optional step.

[0317] As shown in Figure 5, an embodiment of the present disclosure provides a terminal registration method, which is performed by a second core network function. The method may include:

[0318] S5101: The second core network function receives the third message.

[0319] In some embodiments, the second core network function receives the third message from the first core network function.

[0320] In some embodiments, the relevant description of the third message can be found in the corresponding part of the corresponding embodiment of Figure 2B.

[0321] The third information includes the first registration information and / or the second registration information of the terminal.

[0322] Exemplarily, the first registration information may come from a first message sent by the terminal.

[0323] In some embodiments, the registration information of the first registration may include, but is not limited to, at least one of the following:

[0324] Registration type information of the first registration;

[0325] the user identifier corresponding to the first registration;

[0326] The RAT type of the first registration;

[0327] The identifier of the first registered serving AMF.

[0328] In another exemplary embodiment, the second registration information may be determined or generated by the first core network function. For example, if the first core network function determines to accept the second registration, it will allocate a GUTI corresponding to the second registration to the terminal. In this case, the third information may include the GUTI corresponding to the second registration.

[0329] In some embodiments, the registration information of the second registration may include, but is not limited to, at least one of the following:

[0330] Registration type information of the second registration;

[0331] The user ID corresponding to the second registration;

[0332] RAT type information of the second registration;

[0333] The identifier of the second registered serving AMF.

[0334] S5102: The second core network function determines whether to cancel the first registration of the terminal.

[0335] In some embodiments, if the terminal has a first registration and the first core network function accepts the second registration, the second core network function determines whether to cancel the first registration of the terminal.

[0336] In some embodiments, if the terminal supports dual registration, it is determined that the first registration of the terminal is not cancelled while the second registration of the terminal is accepted.

[0337] In some embodiments, if the terminal does not support dual registration, it is determined to cancel the first registration of the terminal while accepting the second registration of the terminal.

[0338] In some embodiments, the second core network function determines whether the terminal supports dual registration based on the subscription information of the terminal.

[0339] S5103: The second core network function initiates the cancellation process of the first registration.

[0340] In some embodiments, if it is determined to cancel the first registration of the terminal, the cancellation process of the first registration is initiated, otherwise the cancellation process of the first registration is not initiated. For details on how to cancel the first registration, please refer to the embodiment shown in FIG2B and will not be repeated here.

[0341] It is worth noting that step S5103 may be an optional step. As shown in FIG6 , the embodiment of the present disclosure provides a terminal registration method, which is executed by the terminal. The method may include:

[0342] S6101: The terminal sends a first message.

[0343] In some embodiments, the terminal sends a first message to the first core network function.

[0344] In some embodiments, the terminal sends a first message to the first core network function through the access network.

[0345] In some embodiments, the first message is used by the terminal to request a second registration.

[0346] In some embodiments, the first message includes first information, and the first information is used by the first core network function to determine whether the terminal has a first registration.

[0347] In some embodiments, the terminal has a first registration, and the terminal sends a first message including first information to the first core network function.

[0348] In some embodiments, the terminal has a first registration and supports dual registration, and sends a first message including first information to the first core network function. In some embodiments, the terminal supports dual registration via 3GPP access. If the terminal completes a first registration with the 5GC via a first 3GPP access, the first registration is not canceled when accepting a second registration with the 5GC via a second 3GPP access. The two 3GPP accesses are different. For example, the first 3GPP access is a New Radio (NR) access. The second 3GPP access is a Non-Terrestrial Network New Radio (NTN NR) access.

[0349] The two 5GC networks may be the same or different, that is, the two 3GPP accesses correspond to the same PLMN or different PLMNs.

[0350] For the second registration of a terminal, when the serving AMF determines that the registration currently requested by the terminal is the second registration of the terminal, the serving AMF instructs the terminal that the first registration shall not be cancelled. Based on this, the UDM will not trigger the cancellation of the first registration. The specific solution is as follows:

[0351] (1) The serving AMF indicates to the UDM that the terminal's initial registration (i.e., the first registration) should not be cancelled.

[0352] (2) After receiving the message from the service AMF, the UDM does not cancel the previous registration of the terminal.

[0353] If the terminal accesses the same PLMN through two 3GPP access points, the same serving AMF is selected to serve the first registration and the second registration. In this case, the serving AMF has the registration information of the terminal's first registration. If the serving AMF receives the registration request message and determines that the registration request message is the second registration of the terminal, and optionally determines whether to allow dual registration of the terminal based on the user subscription information, then based on this, the serving AMF will send an indication to the UDM not to cancel the first registration.

[0354] If the terminal accesses different PLMNs through two 3GPP access points, this means that two different serving AMFs will be selected to serve the first registration and the second registration, respectively. The serving AMF corresponding to the second registration receives a registration request message from the terminal. This registration request message may include, but is not limited to, the terminal sending the previous 5G-GUTI assigned to the terminal for the first registration, or the terminal sending a dual registration indication, etc. Based on this, the serving AMF sends an indication to the UDM not to cancel the first registration.

[0355] If the UDM receives a request message from the serving AMF, the UDM may determine whether the message is related to multi-3GPP access of the terminal based on the user subscription information and registration information.

[0356] The user subscription information includes subscription information related to multiple 3GPP accesses. For example, each 3GPP access corresponds to different subscription information, or the user subscription information directly includes an indication of whether the terminal supports the dual registration mode.

[0357] If the registration information stored on the UDM indicates that the terminal already has a first registration and dual registration is supported based on the user's subscription information, the UDM can determine that the request is related to the terminal's second registration and accept this registration. Otherwise, the terminal rejects the second registration or accepts the second registration and triggers the cancellation of the first registration.

[0358] Example 1:

[0359] 7A , the terminal can access the same PLMN via satellite NR and NR.

[0360] 1. The terminal first selects to access 5GC using satellite NG-RAN and sends a registration request message to the AMF. The registration request message may include registration type information and terminal identifier (5G-GUTI or SUPI or PEI). The registration type information indicates initial registration.

[0361] 2. The AMF serving the terminal chooses to use Nudm_UECM_Registration to notify the UDM of the registration of the terminal. Exemplarily, the AMF sends the access type information, RAT type information and service AMF identifier used by the terminal to the UDM, and this information will be stored in the UDM as terminal registration information. The RAT type information indicates the satellite NR used by the terminal. The satellite NR may include but is not limited to a low earth orbit satellite (LEO) satellite or a synchronous earth satellite, etc. After the AMF completes the Nudm_UECM_Registration operation, if the AMF does not have user subscription information, the AMF uses the Nudm_SDM_Get service operation to obtain user subscription information, SMF selection information, SMF-managed terminal context, etc. 3. AMF obtains user subscription information from the UDM through Nudm_SDM_Get.

[0362] 4.AMF stores the user subscription information. If the terminal supports dual registration through two 3GPP accesses, the subscription information may include an indication of support for dual registration.

[0363] 5. If the network device accepts the terminal's registration, the AMF sends a registration acceptance message to the terminal. The AMF allocates a 5G-GUTI and sends it to the terminal.

[0364] 6. If the terminal enables dual registration via another 3GPP access (e.g. NR), the terminal sends a registration request message via NR. If the terminal requests access to the same PLMN, the message contains the same GUTI assigned to the terminal in the first registration.

[0365] 7. Based on the GUTI, the same serving AMF is selected for the second registration. When the AMF receives the Registration Request message, the AMF checks whether the terminal has registration information, and if it is determined that the terminal is allowed to perform dual registration through 3GPP access, the AMF determines that the Registration Request message is for the second registration of the terminal.

[0366] 8. The serving AMF uses Nudm_UECM_Registration to notify the UDM of the terminal's registration information. The registration information includes the access type, RAT type, and serving AMF identifier used by the terminal. The UDM stores the registration information. The RAT type information indicates that the terminal uses NR access. In addition, the AMF indicates to the UDM that the terminal's previous registration should not be canceled. The UDM does not initiate the cancellation of the terminal's previous registration. Otherwise, if the UDM receives a registration message for the terminal's second registration, it will send a Nudm_UECM_Deregistration message to the AMF to trigger the cancellation of the terminal's previous registration.

[0367] 9.AMF returns the registration acceptance message to the terminal.

[0368] Example 2:

[0369] 7B , an embodiment of the present disclosure provides a method for a terminal to access different PLMNs via satellite NR and NR, respectively.

[0370] 1. The terminal first uses satellite NG-RAN to access 5GC. The terminal sends a registration request message, including the registration request type and the terminal identifier (5G-GUTI-1, SUCI, or PEI). The registration request type information indicates initial registration.

[0371] 2. The AMF (AMF-1) serving the terminal notifies the UDM of the terminal's registration using Nudm_UECM_Registration. The registration information sent by the AMF to the UDM may include: the access type used by the terminal, the RAT type information, and the serving AMF identifier. The RAT type information indicates the satellite NR access used by the terminal (e.g., LEO-NR).

[0372] 3. After AMF-1 completes the Nudm_UECM_Registration operation, if AMF-1 does not have the user subscription information, AMF-1 uses the Nudm_SDM_Get service operation to obtain the user subscription information, Session Management Function (SMF) selection information, SMF-managed terminal context, etc. If the terminal supports dual registration through two 3GPP accesses, the subscription information may include an indication of support for dual registration.

[0373] 4. If the network accepts the terminal registration, AMF-1 sends a registration acceptance message to the terminal. AMF-1 allocates a 5G-GUTI-1 and sends it to the terminal.

[0374] 5. If the terminal enables dual registration through another access (such as NR), the terminal sends a registration request message through NR access. If the PLMN to which the terminal requests access is different from the first access PLMN, the terminal includes a terminal identifier (SUCI or PEI or 5G-GUTI-2) in the registration request message. If 5G-GUTI-2 is included, 5G-GUTI-2 does not correspond to the PLMN selected for the first registration (ie, 5G-GUTI-1). At the same time, if this is the second registration of the terminal and the PLMN selected by the terminal is different from the first PLMN with which the terminal has registered, the terminal should indicate that this is the second registration. For example, 5G-GUTI-1 is also included in the request message to identify the PLMN with which the terminal has registered.

[0375] 6. If 5G-GUTI-2 is provided, the serving AMF (AMF-2) is selected for the second registration based on 5G-GUTI-2. When receiving the Registration Request message, AMF-2 knows that it is a second registration based on 5G-GUTI-2. AMF-2 checks that the terminal supports dual registration via 3GPP access and decides to accept the second registration of the terminal.

[0376] 7.AMF-2 uses Nudm_UECM_Registration to notify UDM about the registration information of the terminal. The registration information contains the access type information, RAT type information and AMF-2 identifier used by the terminal, which will be stored in UDM as registration information. The RAT type information indicates that the terminal uses NR access. In addition, AMF-2 instructs UDM that the first registration of the terminal should not be canceled. UDM should not initiate the cancellation of the previous registration of the terminal. Otherwise, if UDM receives the second registration, it will initiate a Nudm_UECM_Deregistration message to AMF-1 to trigger AMF-1 to initiate the deregistration of the first registration of the terminal.

[0377] 8.AMF-2 uses Nudm_SDM_Get to obtain data.

[0378] 9.AMF-2 returns a registration acceptance message to the terminal.

[0379] Example 3:

[0380] The disclosed embodiments illustrate that a user accesses different PLMNs via satellite NR and NR.

[0381] 1. The terminal first uses satellite NG-RAN to access 5GC and sends a registration request message. The registration request message includes registration request type information and terminal identifier (5G-GUTI-1 or SUCI or PEI). The registration request type information indicates initial registration.

[0382] 2. The AMF (AMF-1) serving the terminal notifies the UDM of the terminal's registration information using Nudm_UECM_Registration. This registration information includes the access type used by the terminal, the RAT type, and the serving AMF identifier. This information is stored in the UDM as terminal registration information. The RAT type indicates the satellite NR access used by the terminal (e.g., LEO-NR).

[0383] 3. After AMF-1 successfully completes the Nudm_UECM_Registration operation, if AMF-1 does not have the user contract information, AMF-1 uses the Nudm_SDM_Get service operation to obtain the user contract information, SMF selection information, terminal context in SMF management, etc. AMF-1 stores the user contract information.

[0384] 4. If the network accepts the terminal registration, AMF-1 sends a registration acceptance message to the terminal. AMF-1 allocates a 5G-GUTI-1 and sends it to the terminal.

[0385] 5. If the terminal enables dual registration through another 3GPP access (such as NR), the terminal sends a registration request message through NR access. If the PLMN to which the terminal requests access is different from the PLMN selected for the first access, the terminal includes a terminal identifier (SUCI or PEI or 5G-GUTI-2) in the registration request message. If 5G-GUTI-2 is included, 5G-GUTI-2 does not correspond to the first selected PLMN (i.e., 5G-GUTI-1). Based on 5G-GUTI-2, the serving AMF (AMF-2) is selected for the second registration.

[0386] 6. The AMF-2 uses Nudm_UECM_Registration to notify the UDM of the terminal's registration information. This registration information includes the access type used by the terminal, the RAT type, and the AMF-2 identifier. This information is stored in the UDM as terminal registration information. The RAT type indicates that the terminal uses NR access.

[0387] 7. Based on the terminal identifier, the UDM checks whether the terminal already has registration information. If so, it indicates that the terminal already has a primary registration. If the terminal supports dual registration, the UDM decides to accept the secondary registration and does not cancel the primary registration. Otherwise, if the UDM receives the secondary registration, it either rejects it or accepts it and initiates a Nudm_UECM_Deregistration message to the AMF-1, triggering the AMF-1 to register the primary registration.

[0388] 8. After AMF-2 successfully completes the Nudm_UECM_Registration operation, if AMF-2 does not store the user contract information, AMF-2 uses the Nudm_SDM_Get service operation to obtain the contract information, SMF selection information, SMF management terminal context, etc. AMF-2 stores the user contract information.

[0389] 9.AMF-2 returns a registration acceptance message to the terminal.

[0390] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0391] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0392] The embodiments of the present disclosure also provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device or a core network device) in any of the above methods.

[0393] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0394] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0395] FIG8A is a first core network function provided by an embodiment of the present disclosure, which includes:

[0396] The receiving module 801 is configured to receive a first message from a terminal, where the first message is used for access registration of the terminal;

[0397] Processing module 802 is configured to determine that the terminal has a first registration and accepts the second registration of the terminal, and determine not to cancel the first registration; the first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

[0398] The receiving module 801 may correspond to a specific structure such as a network interface of the first core network function, and may be used to perform operations related to reception in any of the aforementioned embodiments.

[0399] The processing module 802 may correspond to a specific structure such as a processor of the first core network function, and may be used to execute operations related to processing in any of the aforementioned embodiments.

[0400] In some embodiments, the first core network function may further include a sending module; the sending module may be used to perform operations related to sending in any of the aforementioned embodiments.

[0401] Optionally, the processing module is configured to determine that the terminal has a first registration, accepts a second registration of the terminal and supports dual registration, and determine not to cancel the first registration.

[0402] Optionally, the first core network function is an access management function; and the first message is a registration request message of the terminal.

[0403] Optionally, the terminal selects the same access management function for the first registration and the second registration, and the processing module is further configured to use the access management function to determine that the terminal has the first registration according to the saved first registration information of the terminal.

[0404] Optionally, the first registration information includes at least: the first registered user identifier and / or the first registered wireless access type information.

[0405] Optionally, the first core network function is an access management function; the terminal selects different access management functions for the first registration and the second registration; the processing module is also configured so that the access management function determines that the terminal has a first registration based on the first information of the first message.

[0406] Optionally, the first information is a globally unique temporary user equipment identifier (GUTI) allocated to the terminal after the terminal successfully registers through the first 3GPP access.

[0407] Optionally, the first core network function further includes:

[0408] The sending module is also configured to send a second message to the second core network function, where the second message includes second information, and the second information is used to indicate that the first registration is not to be canceled.

[0409] FIG8B is a schematic diagram of the structure of a terminal provided by an embodiment of the present disclosure. As shown in FIG8B , the terminal includes:

[0410] The sending module 803 is configured for the terminal to send a first message to the first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, which is used by the first core network function to determine whether the terminal has a first registration.

[0411] The sending module 803 may correspond to a specific structure such as an antenna or a network interface of the terminal.

[0412] Optionally, the terminal further includes a storage module, a processing module and / or a receiving module, wherein the storage module may be configured to store information, for example, to store the first message. The processing module may be configured to process information.

[0413] Optionally, the receiving module is configured to receive information of network devices, etc.

[0414] Optionally, the first information is used to indicate that the terminal has a first registration and / or information about the first registration.

[0415] Optionally, the first information is the GUTI of the terminal corresponding to the first registration.

[0416] FIG8C is a schematic diagram of the structure of the second core network function provided in an embodiment of the present disclosure. As shown in FIG8C , the second core network function includes:

[0417] The receiving module 804 is configured to receive a second message sent by the first core network function; the second message includes second information, and the second information is used to indicate that the first registration of the terminal is not canceled when the second registration of the terminal is accepted;

[0418] The processing module 805 is configured to, according to the second message, not initiate cancellation of the first registration when accepting the second registration of the terminal.

[0419] The receiving module 804 may correspond to a specific structure such as a network interface of the second core network function, and may be used to execute operations related to reception in any of the aforementioned embodiments.

[0420] The processing module 805 may correspond to a specific structure such as a processor of the second core network function, and may be used to execute operations related to processing in any of the aforementioned embodiments.

[0421] In some embodiments, the second core network function may further include a sending module; the sending module may be used to perform operations related to sending in any of the aforementioned embodiments.

[0422] In some embodiments, the terminal supports dual registration, and the second message includes the second information.

[0423] In some embodiments, the first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; and the first 3GPP access network is different from the second 3GPP access network.

[0424] FIG8D is a schematic diagram of the structure of the second core network function provided by an embodiment of the present disclosure. As shown in FIG8D , the second core network function includes:

[0425] The receiving module 806 is configured to receive a third message sent by the first core network function; the third message includes: registration information of the second registration of the terminal;

[0426] The processing module 807 is configured to determine not to cancel the first registration when the terminal has a first registration and it is determined based on the third message that the second registration of the terminal is accepted.

[0427] The receiving module 806 may correspond to a specific structure such as an antenna or a network interface of the second core network function.

[0428] Optionally, the second core network function further includes a storage module, a sending module, and / or a processing module, wherein the storage module may be configured to perform steps related to information storage, the processing module may be configured to perform steps related to information processing, and the sending module may be configured to execute steps of the processing module.

[0429] Optionally, the processing module is configured to determine not to cancel the second registration if the terminal has a first registration, accepts a second registration of the terminal, and supports dual registration.

[0430] Optionally, the first core network function is a user data management function; the third message includes third information; the third information includes the first registration information and / or the second registration information of the terminal.

[0431] Optionally, the third information includes at least one of the following:

[0432] the first registered user identifier;

[0433] the wireless access type of the first registration;

[0434] an access management function of the first registration;

[0435] the second registered user identifier;

[0436] the wireless access type of the second registration;

[0437] The access management function of the second registration.

[0438] Optionally, the processing module is further configured to enable the second core network function to determine whether the terminal supports dual registration according to the subscription information of the terminal.

[0439] An embodiment of the present disclosure further provides a communication device, which may include: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the terminal registration method that can be implemented in any of the aforementioned embodiments.

[0440] 9A and / or 9B , the communication device 8100 further includes one or more memories 8102 for storing instructions. Alternatively, all or part of the memories 8102 may be located outside the communication device 8100.

[0441] The communication device may be the aforementioned terminal, core network device, access network device, and second device. In some embodiments, the communication device may also be the aforementioned first device.

[0442] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0443] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0444] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0445] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 9A . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0446] 9B is a schematic diagram of the structure of the chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG9B , but the present disclosure is not limited thereto.

[0447] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above terminal registration methods.

[0448] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0449] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0450] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0451] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above terminal registration methods. Optionally, the program product is a computer program product.

[0452] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above terminal registration methods.

[0453] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0454] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A terminal registration processing method, performed by a first core network function, comprising: The first core network function receives a first message from a terminal, where the first message is used for access registration of the terminal; The first core network function determines that the terminal has a first registration and accepts a second registration of the terminal, and determines not to cancel the first registration; The first registration is a registration initiated by the terminal through a first 3GPP access network; The second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

2. The method according to claim 1, wherein: The first core network function determines that the terminal has a first registration and accepts a second registration of the terminal, and determines not to cancel the first registration, including: The first core network function determines that the terminal has a first registration, accepts a second registration of the terminal and the terminal supports dual registration, and determines not to cancel the first registration.

3. The method according to claim 1 or 2, wherein: The first core network function is an access management function; the first message is a registration request message of the terminal.

4. The method according to claim 3, wherein: The terminal selects the same access management function for the first registration and the second registration, and the method further includes: The access management function determines that the terminal has a first registration based on the saved first registration information of the terminal.

5. The method according to claim 4, wherein: The first registration information includes at least: the first registered user identifier and / or the first registered wireless access type information.

6. The method according to claim 3, wherein: The first core network function is an access management function for the second registration service of the terminal The terminal selects different access management functions for the first registration and the second registration; The method further comprises: The access management function determines, based on the first information, that the terminal has a first registration.

7. The method according to claim 6, wherein: The first information is a globally unique temporary user equipment identifier GUTI allocated to the terminal after the terminal successfully registers through the first 3GPP access.

8. The method according to any one of claims 1 to 7, wherein: The method further comprises: A second message is sent to a second core network function, where the second message includes second information, and the second information is used to indicate that the first registration is not to be canceled.

9. A terminal registration processing method, wherein: Executed by a terminal, the method includes: A first message is sent to a first core network function, where the first message is used by the terminal to request a second registration; the first message includes first information, where the first information is used by the first core network function to determine whether the terminal has a first registration.

10. The method according to claim 9, wherein: The first information is used to indicate that the terminal has a first registration and / or information of the first registration.

11. The method according to claim 9 or 10, wherein: The first information is the GUTI of the terminal corresponding to the first registration.

12. A terminal registration method, performed by a second core network function, the method further comprising: Receiving a second message sent by the first core network function; The second message includes second information, where the second information is used to indicate that the first registration of the terminal is not to be cancelled when the second registration of the terminal is accepted; According to the second message, cancellation of the first registration is not initiated in case the second registration of the terminal is accepted.

13. The method according to claim 12, wherein: The first registration is a registration initiated by the terminal through a first 3GPP access network; the second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

14. A terminal registration processing method, wherein: include: The second core network function receives a third message sent by the first core network function; The third message includes: registration information of the terminal; When the terminal has a first registration and it is determined based on the third message that a second registration of the terminal is accepted, it is determined not to cancel the first registration.

15. The method according to claim 14, wherein: When the terminal has a first registration and a second registration of the terminal is accepted, determining not to cancel the first registration includes: When the terminal has a first registration, a second registration of the terminal is accepted, and the terminal supports dual registration, it is determined not to cancel the second registration.

16. The method according to claim 14 or 15, wherein: The second core network function is a user data management function; The third message includes third information; the third information includes first registration information and / or second registration information of the terminal.

17. The method according to claim 16, wherein: The third information includes at least one of the following: the first registered user identifier; the first registered wireless access type; an access management function of the first registration; the second registered user identifier; the second registered wireless access type; The access management function of the second registration.

18. The method according to claim 15, wherein: The method further comprises: The second core network function determines whether the terminal supports dual registration according to user subscription information.

19. A first core network function, wherein: include: A receiving module, configured to receive a first message from a terminal, where the first message is used for access registration of the terminal; a processing module, configured to determine that the terminal has a first registration and accepts a second registration of the terminal, and determine not to cancel the first registration; The first registration is a registration initiated by the terminal through a first 3GPP access network; The second registration is a registration initiated by the terminal through a second 3GPP access network; the first 3GPP access network is different from the second 3GPP access network.

20. A terminal, wherein: include: A sending module, configured to enable the terminal to send a first message to the first core network function, where the first message is used by the terminal to request a second registration; The first message includes first information, and the first information is used by the first core network function to determine whether the terminal has a first registration.

21. A second core network function, comprising: A receiving module, configured to receive a second message sent by the first core network function; The second message includes second information, where the second information is used to indicate that the first registration of the terminal is not to be cancelled when the second registration of the terminal is accepted; The processing module is configured to, according to the second message, not initiate cancellation of the first registration when accepting the second registration of the terminal.

22. A second core network function, comprising: A receiving module, configured to receive a third message sent by the first core network function; The third message includes: registration information of the terminal; The processing module is configured to determine not to cancel the first registration when the terminal has a first registration and accepting the second registration of the terminal is determined based on the third message.

23. A communication device, wherein: The communication device comprises: one or more processors; The processor is used to call instructions to enable the communication device to execute the terminal registration method according to any one of claims 1 to 12, claims 13 to 14, or claims 15 to 17.

24. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the terminal registration method according to any one of claims 1 to 12, claims 13 to 14, or claims 15 to 17.

Images