Communication methods and apparatuses, communication device, communication system, and storage medium

Abstract

Communication methods and apparatuses, a communication device, a communication system, and a storage medium. A method comprises: after receiving a first message of a terminal requesting registration with a first PLMN, a first network function determining, on the basis of user subscription information of the terminal, whether to accept the registration of the terminal with the first PLMN, so as to implement a registration process of the terminal in a dual 3GPP access scenario.

Description

Communication method and device, communication equipment, communication system and storage medium Technical Field

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

[0002] In the field of communications technology, a terminal can simultaneously register and communicate through multiple access networks. Currently, multi-access supported by a terminal refers to simultaneous access to both 3rd Generation Partnership Project (3GPP) and non-3GPP access networks. As communications networks continue to evolve, terminals may also support multi-access connections, all of which are 3GPP access networks.

[0003] Summary of the Invention

[0004] In the case where the terminal is able to access two 3GPP access networks at the same time, when the terminal requests registration on a PLMN through a 3GPP access network, the network side determines the user subscription information of the terminal based on the RAT type corresponding to the PLMN and / or the 3GPP access network, and then determines whether to allow the terminal to register based on the user subscription information, thereby realizing the registration process of the terminal in the dual 3GPP access scenario.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a first network function. The method includes: receiving a first message, the first message being used by a terminal to request registration in a first public land mobile network (PLMN); accepting or rejecting registration of the terminal in the first PLMN based on user subscription information of the terminal; wherein the user subscription information includes first subscription information, the first subscription information is associated with the first PLMN and / or a first radio access technology (RAT) type, the first RAT type corresponds to a first access network, and the first access network is the access network used by the terminal when accessing the first PLMN.

[0006] According to the second aspect of an embodiment of the present disclosure, a communication method is provided. The method is executed by a second network function. The method includes: receiving a second message, the second message is used to request user subscription information of a terminal, the second message carries an identifier of a first PLMN and / or a first RAT type, the first PLMN being the PLMN selected for access by the terminal; the first RAT type corresponds to a first access network, the first access network being the access network used when the terminal accesses the first PLMN; sending user subscription information according to the identifier of the PLMN and / or the first RAT type, the user subscription information including first subscription information, the first subscription information being associated with the first PLMN and / or the first RAT type.

[0007] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a third network function. The method includes: sending a third message, the third message including a first event subscription request, the first event subscription request being used to request subscription to a first event registered by a terminal via a first access network and a second access network; wherein the first access network corresponds to a first RAT type, which is the access network used when the terminal accesses a first PLMN; the second access network corresponds to a second RAT type, which is the access network used when the terminal accesses a second PLMN; and the first RAT type and the second RAT type are different.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a core network device. The method includes: a first network function receiving a first message, the first message being used by a terminal to request registration in a first PLMN; the first network function accepting or rejecting the terminal's registration in the first PLMN based on user subscription information of the terminal; wherein the user subscription information includes first subscription information, the first subscription information is associated with the first PLMN and / or a first radio access technology (RAT) type, the first RAT type corresponds to a first access network, and the first access network is the access network used by the terminal when accessing the first PLMN.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided. The device is set in a first network function. The above-mentioned device includes: a receiving module, which is used to receive a first message, the first message being used by a terminal to request registration in a first PLMN; a processing module, which is used to accept or reject the terminal's registration in the first PLMN based on the terminal's user contract information; wherein the user contract information includes first contract information, the first contract information is associated with the first PLMN and / or the first radio access technology RAT type, the first RAT type corresponds to the first access network, and the first access network is the access network used when the terminal accesses the first PLMN.

[0010] According to the sixth aspect of the embodiment of the present disclosure, a communication device is provided. The device is set in the second network function. The above-mentioned device includes: a receiving module, which is used to receive a second message, the second message is used to request the user contract information of the terminal, and the second message carries the identifier of the first PLMN and / or the first RAT type. The first PLMN is the PLMN selected by the terminal to access; the first RAT type corresponds to the first access network, and the first access network is the access network used when the terminal accesses the first PLMN; a sending module, which is used to send user contract information according to the identifier of the PLMN and / or the first RAT type, the user contract information includes the first contract information, and the first contract information is associated with the first PLMN and / or the RAT type.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a communication device is provided. The device is set in a third network function. The above-mentioned device includes: a sending module, which is used to send a third message, the third message includes a first event subscription request, and the first event subscription request is used to request a subscription to a first event registered by a terminal through a first access network and a second access network; wherein the first access network corresponds to a first RAT type, and the first access network is the access network used when the terminal accesses a first PLMN; the second access network corresponds to a second RAT type, and the second access network is the access network used when the terminal accesses a second PLMN; the first RAT type is different from the second RAT type.

[0012] According to an eighth aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes at least one processor. The communication device is configured to execute the method described in the first, second, third, or fourth aspects.

[0013] According to a ninth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first network function and a second network function. The first access network is configured to implement the method described in the first aspect; the second network function is configured to implement the method described in the second aspect.

[0014] According to a tenth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed by a processor, the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect is performed.

[0015] According to an eleventh aspect of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the method described in the first, second, third, or fourth aspects is performed.

[0016] The embodiments of the present disclosure are used to implement the registration process of a terminal in a dual 3GPP access scenario.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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.

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

[0020] FIG2A is a first exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0021] FIG2B is a second exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0022] FIG3 is an exemplary flowchart of a communication method performed by a first network function side according to an embodiment of the present disclosure.

[0023] FIG4 is an exemplary flowchart of a communication method performed by a second network function side according to an embodiment of the present disclosure.

[0024] FIG5 is an exemplary flowchart of a communication method performed by a third network function side according to an embodiment of the present disclosure.

[0025] FIG6A is another exemplary flowchart of a communication method performed by a first network function side according to an embodiment of the present disclosure.

[0026] FIG6B is another exemplary flowchart of a communication method performed by a second network function side according to an embodiment of the present disclosure.

[0027] FIG6C is another exemplary flowchart of a communication method performed by a third network function side according to an embodiment of the present disclosure.

[0028] FIG7 is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0029] FIG8 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0030] FIG9 is another exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0031] FIG10 is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0032] FIG11 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0034] In a first aspect, embodiments of the present disclosure provide a communication method. The method is performed by a first network function. The method comprises: receiving a first message, the first message being used by a terminal to request registration on a first public land mobile network (PLMN); and accepting or rejecting the terminal's registration on the first PLMN based on user subscription information of the terminal. The user subscription information includes first subscription information, the first subscription information being associated with the first PLMN and / or a first radio access technology (RAT) type, the first RAT type corresponding to a first access network, the first access network being the access network used by the terminal when accessing the first PLMN.

[0035] In an embodiment of the present disclosure, after receiving a first message requesting the terminal to register on the first PLMN, the first network function determines whether to allow the terminal to register on the first PLMN based on the user subscription information associated with the first PLMN and / or the first RAT type. In this way, when the terminal can access multiple 3GPP access networks at the same time, the 3GPP access networks are distinguished, thereby realizing the registration process of the terminal in the dual 3GPP access scenario.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the registration includes initial registration or registration update.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the above method further includes: obtaining user subscription information according to the first PLMN and / or the first RAT type.

[0038] In combination with some embodiments of the first aspect, in some embodiments, obtaining user contract information based on the first PLMN and / or RAT type includes: sending a second message, the second message is used to request user contract information, the second message carries the identifier of the first PLMN and / or the first RAT type; receiving user contract information.

[0039] In an embodiment of the present disclosure, when the first network function does not have user subscription information, the first network function may request the second network function for user subscription information associated with the first PLMN and / or the first RAT type, so that the first network function can determine whether to allow terminal registration for the first PLMN.

[0040] In combination with some embodiments of the first aspect, in some embodiments, obtaining user subscription information according to the first PLMN and / or the first RAT type includes: determining the user subscription information locally according to the first PLMN and / or the first RAT type.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscription quality of service (QoS) of the first PLMN. The first subscription information includes but is not limited to the information listed above.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the user subscription information also includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restricted area of ​​the second PLMN; and a subscribed QoS of the second PLMN. The second subscription information includes but is not limited to the information listed above.

[0044] In combination with some embodiments of the first aspect, in some embodiments, accepting registration of the terminal in the first PLMN includes: sending first registration information, the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0045] In combination with some embodiments of the first aspect, in some embodiments, accepting or rejecting the registration of the terminal in the first PLMN based on the user contract information of the terminal includes one of the following: accepting the registration of the terminal in the first PLMN when it is determined according to the first contract information that the terminal is outside the prohibited area of ​​the first PLMN; rejecting the registration of the terminal in the first PLMN when it is determined according to the first contract information that the terminal is located in the prohibited area of ​​the first PLMN.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the user subscription information also includes first indication information, and the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network.

[0047] In combination with some embodiments of the first aspect, in some embodiments, accepting or rejecting the registration of the terminal in the first PLMN based on the user contract information of the terminal includes one of the following: when the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined that the terminal is outside the prohibited area of ​​the first PLMN based on the first contract information, accepting the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined that the terminal is located in the prohibited area of ​​the first PLMN based on the first contract information, rejecting the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal does not support registration through at least the first access network and the second access network, and it is determined that the terminal has registered to a third PLMN, rejecting the registration of the terminal in the first PLMN.

[0048] In combination with some embodiments of the first aspect, in some embodiments, determining that the terminal has registered with the third PLMN includes: obtaining second registration information, the second registration information including at least one of the following: an identifier of the third PLMN and a third RAT type, the third RAT type corresponding to a third access network, and the third access network being the access network used when the terminal registers with the third PLMN; and determining, based on the second registration information, that the terminal has registered with the third PLMN.

[0049] In a second aspect, an embodiment of the present disclosure provides a communication method. The method is performed by a second network function. The method includes: receiving a second message, the second message being used to request user subscription information of a terminal, the second message carrying an identifier of a first PLMN and / or a first RAT type, the first PLMN being the PLMN selected for access by the terminal; the first RAT type corresponding to a first access network, the first access network being the access network used by the terminal when accessing the first PLMN; and sending user subscription information based on the identifier of the PLMN and / or the first RAT type, the user subscription information including first subscription information, the first subscription information being associated with the first PLMN and / or the first RAT type.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the registration includes initial registration or registration update.

[0051] In combination with some embodiments of the second aspect, in some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscription QoS of the first PLMN.

[0052] In combination with some embodiments of the second aspect, in some embodiments, the user subscription information also includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type.

[0053] In combination with some embodiments of the second aspect, in some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; and a subscription QoS of the second PLMN.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the user subscription information also includes first indication information, and the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network; the second access network is the access network used when the terminal accesses the second PLMN, and the second access network corresponds to the second RAT type.

[0055] In combination with some embodiments of the second aspect, in some embodiments, the above method further includes: receiving first registration information, the first registration information including: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: sending second registration information, the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, wherein the third PLMN is a PLMN in which the terminal has registered, the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN.

[0057] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: receiving a third message, the third message includes a first event subscription request, the first event subscription request is used to request the subscription terminal to register for the first event through the first access network and the second access network; wherein, the second access network corresponds to the second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: determining that the terminal is registered in the first PLMN through the first access network and is registered in the second PLMN through the second access network; sending a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

[0059] In a third aspect, embodiments of the present disclosure provide a communication method. The method is performed by a third network function. The method includes: sending a third message, the third message including a first event subscription request, the first event subscription request being used to request subscription to a first event registered by a terminal via a first access network and a second access network; wherein the first access network corresponds to a first RAT type, which is the access network used by the terminal when accessing a first PLMN; the second access network corresponds to a second RAT type, which is the access network used by the terminal when accessing a second PLMN; and the first RAT type and the second RAT type are different.

[0060] In an embodiment of the present disclosure, the third network device subscribes to the first event from the second network device. When the terminal achieves dual registration through the first access network and the second access network, the third network device can provide services to the terminal based on the event report of the first event, thereby improving service efficiency.

[0061] In combination with some embodiments of the third aspect, in some embodiments, the above method also includes: receiving a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes the identifier of the first PLMN, the first RAT type, the identifier of the second PLMN and the second RAT type, wherein the first PLMN identifier and the first RAT type are registration information of the terminal registered in the first PLMN through the first access network; the second PLMN identifier and the second RAT type are registration information of the terminal registered in the second PLMN through the second access network.

[0062] In conjunction with some embodiments of the third aspect, in some embodiments, registration includes initial registration or registration update.

[0063] In a fourth aspect, embodiments of the present disclosure provide a communication method. The method is performed by a core network device. The core network device includes a first network function. The method includes: the first network function receiving a first message, the first message being used by a terminal to request registration on a first public land mobile network (PLMN); the first network function accepting or rejecting the terminal's registration on the first PLMN based on the terminal's user subscription information; the user subscription information including first subscription information, the first subscription information being associated with the first PLMN and / or a first radio access technology (RAT) type, the first RAT type corresponding to a first access network, the first access network being the access network used by the terminal to access the first PLMN.

[0064] In combination with some embodiments of the fourth aspect, in some embodiments, the above method also includes: the first network function locally determines the user subscription information based on the first PLMN and / or the first RAT type.

[0065] In combination with some embodiments of the fourth aspect, in some embodiments, the core network device also includes a second network function; the above method also includes: the first network function sends a second message to the second network function, the second message is used to request user subscription information, and the second message carries the identifier of the first PLMN and / or the first RAT type; the second network function sends the user subscription information to the first network function based on the identifier of the first PLMN and / or the first RAT type.

[0066] In combination with some embodiments of the fourth aspect, in some embodiments, the first network function sends first registration information to the second network function, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0067] In combination with some embodiments of the fourth aspect, in some embodiments, the second network function sends second registration information to the first network function, and the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, the third PLMN is a PLMN in which the terminal is registered, the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN.

[0068] In combination with some embodiments of the fourth aspect, in some embodiments, the core network device also includes a third network function; the above method also includes: the third network function sends a third message to the second network function, the third message includes a first event subscription request, the first event subscription request is used to request to subscribe to the first event registered by the terminal through the first access network and the second access network; the second access network corresponds to the second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

[0069] In combination with some embodiments of the fourth aspect, in some embodiments, the above method also includes: the second network function determines that the terminal is registered in the first PLMN through the first access network and is registered in the second PLMN through the second access network; the second network function sends a fourth message to the third network function, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein, the third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

[0070] In a fifth aspect, embodiments of the present disclosure provide a communication party device, configured in a first network function. The device includes: a receiving module configured to receive a first message, the first message being used by a terminal to request registration in a first PLMN; and a processing module configured to accept or reject the terminal's registration in the first PLMN based on user subscription information of the terminal; wherein the user subscription information includes first subscription information, the first subscription information being associated with the first PLMN and / or a first RAT type, the first RAT type corresponding to a first access network, the first access network being the access network used by the terminal when accessing the first PLMN.

[0071] In conjunction with some embodiments of the fifth invention, in some embodiments, registration includes initial registration or registration update.

[0072] In combination with some embodiments of the fifth invention, in some embodiments, the processing module is further configured to obtain user subscription information according to the first PLMN and / or the first RAT type.

[0073] In combination with some embodiments of the fifth invention, in some embodiments, the above-mentioned device also includes: a sending module for sending a second message, the second message is used to request user contract information, and the second message carries the identifier of the first PLMN and / or the first RAT type; a receiving module for receiving user contract information.

[0074] In combination with some embodiments of the fifth invention, in some embodiments, the processing module is further configured to locally determine user subscription information based on the first PLMN and / or the first RAT type.

[0075] In combination with some embodiments of the fifth invention, in some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscription QoS of the first PLMN.

[0076] In combination with some embodiments of the fifth invention, in some embodiments, the user subscription information further includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type.

[0077] In combination with some embodiments of the fifth invention, in some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; and a subscription QoS of the second PLMN.

[0078] In combination with some embodiments of the fifth invention, in some embodiments, the sending module is further used to send first registration information, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0079] In combination with some embodiments of the fifth invention, in some embodiments, the processing module is further used to perform at least one of the following: when it is determined based on the first contract information that the terminal is located outside the prohibited area of ​​the first PLMN, accepting the registration of the terminal in the first PLMN; when it is determined based on the first contract information that the terminal is located in the prohibited area of ​​the first PLMN, rejecting the registration of the terminal in the first PLMN.

[0080] In combination with some embodiments of the fifth invention, in some embodiments, the user subscription information further includes first indication information, and the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network.

[0081] In combination with some embodiments of the fifth invention, in some embodiments, the processing module is further used to perform one of the following: when the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined based on the first contract information that the terminal is located outside the prohibited area of ​​the first PLMN, accept the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined based on the first contract information that the terminal is located in the prohibited area of ​​the first PLMN, reject the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal does not support registration through at least the first access network and the second access network, and it is determined that the terminal has been registered to a third PLMN, reject the registration of the terminal in the first PLMN.

[0082] In combination with some embodiments of the fifth invention, in some embodiments, the processing module is further used to obtain second registration information, the second registration information including at least one of the following: an identifier of a third PLMN and a third RAT type, the third RAT type corresponding to a third access network, and the third access network being the access network used when the terminal registers to the third PLMN; based on the second registration information, it is determined that the terminal has been registered to the third PLMN.

[0083] In a sixth aspect, embodiments of the present disclosure provide a communications device, configured for a second network function. The device includes: a receiving module, configured to receive a second message, the second message being used to request user subscription information of a terminal, the second message carrying an identifier of a first PLMN and / or a first RAT type, the first PLMN being the PLMN selected for access by the terminal; the first RAT type corresponding to a first access network, the first access network being the access network used by the terminal when accessing the first PLMN; and a sending module, configured to send user subscription information based on the identifier of the PLMN and / or the first RAT type, the user subscription information including first subscription information, the first subscription information being associated with the first PLMN and / or the first RAT type.

[0084] In combination with some embodiments of the sixth aspect, in some embodiments, registration includes initial registration or registration update.

[0085] In combination with some embodiments of the sixth aspect, in some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscription QoS of the first PLMN.

[0086] In combination with some embodiments of the sixth aspect, in some embodiments, the user subscription information also includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type.

[0087] In combination with some embodiments of the sixth aspect, in some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; and a subscription QoS of the second PLMN.

[0088] In combination with some embodiments of the sixth aspect, in some embodiments, the user subscription information also includes first indication information, and the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network; the second access network is the access network used when the terminal accesses the second PLMN, and the second access network corresponds to the second RAT type.

[0089] In combination with some embodiments of the sixth aspect, in some embodiments, the receiving module is further used to receive first registration information, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0090] In combination with some embodiments of the sixth aspect, in some embodiments, the sending module is also used to send second registration information, and the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, wherein the third PLMN is a PLMN in which the terminal has registered, the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN.

[0091] In combination with some embodiments of the sixth aspect, in some embodiments, the receiving module is also used to receive a third message, the third message including a first event subscription request, the first event subscription request being used to request a subscription to a first event registered by the terminal through the first access network and the second access network; wherein the second access network corresponds to a second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

[0092] In combination with some embodiments of the sixth aspect, in some embodiments, the processing module is further used to determine whether the terminal is registered in the first PLMN through the first access network and is registered in the second PLMN through the second access network; the sending module is also used to send a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

[0093] In a seventh aspect, embodiments of the present disclosure provide a communications device, configured for a third network function. The device includes: a sending module, configured to send a third message, the third message including a first event subscription request, the first event subscription request being used to request a subscription to a first event registered by a terminal via a first access network and a second access network; wherein the first access network corresponds to a first RAT type, which is an access network used by the terminal when accessing a first PLMN; the second access network corresponds to a second RAT type, which is an access network used by the terminal when accessing a second PLMN; and the first RAT type and the second RAT type are different.

[0094] In combination with some embodiments of the seventh aspect, in some embodiments, the above-mentioned device also includes: a receiving module, used to receive a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes the identifier of the first PLMN, the first RAT type, the identifier of the second PLMN and the second RAT type, wherein the first PLMN identifier and the first RAT type are registration information of the terminal registered in the first PLMN through the first access network; the second PLMN identifier and the second RAT type are registration information of the terminal registered in the second PLMN through the second access network.

[0095] In combination with some embodiments of the seventh aspect, in some embodiments, registration includes initial registration or registration update.

[0096] In an eighth aspect, an embodiment of the present disclosure provides a communication device. The communication device includes at least one processor. The processor is configured to invoke instructions to execute the method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, and the embodiments thereof.

[0097] In a ninth aspect, embodiments of the present disclosure provide a communication system. The communication system includes a first network function and a second network function. The first network function is configured to perform the method described in any one of the first aspect and its embodiments. The second network function is configured to perform the method described in any one of the second aspect and its embodiments.

[0098] In conjunction with some embodiments of the eighth aspect, in some embodiments, the communication system further includes a third network function. The third network function is configured to execute the method as described in any one of the third aspect and its embodiments.

[0099] In a tenth aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed by a processor, perform the method as described in any one of the first, second, third, and fourth aspects and their embodiments.

[0100] In an eleventh aspect, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, and the embodiments thereof is performed.

[0101] It is understandable that the above-mentioned communication devices, communication equipment, communication systems, storage media, computer programs, and computer program products are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

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

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

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

[0108] In some embodiments, the terms "at least one", "one or more", etc. can be used interchangeably.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

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

[0114] 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.

[0115] 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.

[0116] In some embodiments, "network" can be interpreted as devices included in the network (for example, access network equipment, core network equipment, data network equipment, etc.).

[0117] 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.

[0118] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "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.

[0119] 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.

[0120] 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.

[0121] In some embodiments, the access network device may also be referred to as an access network function, an access network element, etc.

[0122] In some embodiments, core network devices may also be referred to as core network functions, core networks, core network elements, etc. Furthermore, in some embodiments, each network device in the core network may also be referred to as a network function, a network element, etc.

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

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

[0125] 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.

[0126] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network 103. The core network 103 is deployed with one or more core network devices.

[0127] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things (IoT) device, a car with communication function, a smart car, a tablet computer (Pad), 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.

[0128] 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 satellite base station, 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.

[0129] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces within the 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.

[0130] In some embodiments, the access network device 102 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 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.

[0131] In some embodiments, the access network device 102 may include an access network device 102a and an access network device 102b. In some embodiments, the access network device 102 may further include one or more other access network devices to support 3GPP multi-access scenarios.

[0132] In some embodiments, the core network device may be a device including a first network function 1031, a second network function 1032, a third network function, a fourth network function, a fifth network function, a sixth network function, etc. (wherein the third network function, the fourth network function, the fifth network function, and the sixth network function are not shown in FIG1 ), or may be a plurality of devices or a group of devices including part or all of the first network function 1031, the second network function 1032, the third network function, the fourth network function, the fifth network function, and the sixth network function. The core network device may be virtual or physical. The core network, for example, includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

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

[0134] In some embodiments, the first network function 1031 can be used to perform user access and mobility management, and its name is not limited thereto.

[0135] In some embodiments, the number of first network functions 1031 can be one or more.

[0136] In some embodiments, the second network function 1032 can be used for user subscription data management, and its name is not limited thereto.

[0137] In some embodiments, the second network function 1032 is, for example, a unified data management (UDM) function.

[0138] In some embodiments, the third network function may be used to provide various services at the application layer.

[0139] In some embodiments, the third network function is, for example, an application function (AF).

[0140] In some embodiments, the third network function may also be deployed outside the core network.

[0141] In some embodiments, the fourth network function can be used to provide security to ensure the security of external applications to the core network, and provide functions such as external application QoS customization capability exposure, mobility status event subscription, and AF request distribution.

[0142] In some embodiments, the fourth network function is, for example, a network exposure function (NEF).

[0143] In some embodiments, the fifth network function can be used for session management functions, responsible for tunnel maintenance, IP address allocation and management, UP function selection, policy implementation and QoS control, billing data collection, roaming and other functions.

[0144] In some embodiments, the fifth network function is, for example, a session management function (SMF).

[0145] In some embodiments, the sixth network function may be used to provide policy rules for control plane functions.

[0146] In some embodiments, the sixth network function is, for example, a policy control function (PCF).

[0147] 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.

[0148] 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.

[0149] 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 (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0150] In the field of communications technology, terminals can access networks and communicate using dual access. Currently, dual access refers to simultaneous access to the 5G core network via both a 3GPP access network and a non-3GPP access network. In this type of dual access, the 3GPP access network and the non-3GPP access network can belong to the same or different PLMNs. UDM manages the registration process for terminals accessing through 3GPP and non-3GPP access networks separately.

[0151] In the above dual access scenario, during the terminal registration process, the access type is used to distinguish between a 3GPP access network, a non-3GPP access network, or a 3GPP access network and a non-3GPP access network.

[0152] As communication networks continue to evolve, terminals will also be able to support multiple access scenarios, all of which are 3GPP access networks. In such scenarios, there is currently no suitable solution for how to implement terminal registration.

[0153] Here, “multi-access” can be understood as access based on two 3GPP access networks, access based on three 3GPP access networks, or even access based on more 3GPP access networks.

[0154] In some embodiments, description is provided for a dual 3GPP access scenario.

[0155] In a dual 3GPP access scenario, terminal 101 can access PLMN A through RAN A (i.e., access network A) and / or access PLMN B through RAN B (i.e., access network B). Terminal 101 can then request registration on PLMN A and / or request registration on PLMN B. If the terminal supports dual access to 3GPP access networks, the terminal can register on PLMN A using RAN A and then register on PLMN B using RAN B. In this way, dual registration based on 3GPP access is implemented.

[0156] In some embodiments, RAN A and RAN B have the same access type (access type), both set to 3GPP access (3GPP access), but have different RAT types (RAT types) to distinguish different 3GPP accesses.

[0157] In some embodiments, PLMN A and PLMN B may be the same PLMN or different PLMNs. If PLMN A and PLMN B are the same PLMN, it means that the terminal accesses the same PLMN (e.g., PLMN A) through RAN A and RAN B, respectively, and is registered on PLMN A. If PLMN A and PLMN B are different, it means that the terminal accesses PLMN A through RAN A and PLMN B through RAN B, and is registered on PLMN A and PLMN B, respectively.

[0158] In some embodiments, RAN A may be a satellite NR access network, such as a low Earth orbit NR (LEO-NR) access network, and RAN B may be a terrestrial NR access network. Alternatively, RAN A may be a terrestrial NR access network, and RAN B may be a satellite access network, such as a LEO-NR access network.

[0159] In some embodiments, the RAT type of RAN A may be LEO-NR access, and the RAT type of RAN B may be NR access, or the RAT type of RAN A may be NR access, and the RAT type of RAN B may be LEO-NR access.

[0160] In some embodiments, in a multi-3GPP access scenario (e.g., two or more accesses), terminal 101 can access three or more PLMNs through, for example, three or more RANs. For example, terminal 101 can access PLMN A through RAN A, access PLMN B through RAN B, and access PLMN C through RAN C. Taking three accesses as an example, terminal 101 can request to register on PLMN A, request to register on PLMN B, and request to register on PLMN C. If the terminal supports multi-access to the 3GPP access network, it can register on PLMN A using RAN A, register on PLMN B using RAN B, and register on PLMN C using RAN C. In this way, multi-registration based on 3GPP access is implemented.

[0161] The communication method provided by the embodiment of the present disclosure is described below in conjunction with a dual registration scenario based on 3GPP access.

[0162] In some embodiments, FIG2A is a first exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. For example, the communication system 100 includes a terminal 101 (denoted as UE 101), an access network device 102a (denoted as 3GPP AN 102a), an access network device 102b (denoted as 3GPP AN 102b), an AMF-1, an AMF-2, and a UDM. Among them, the access network device 102a can be deployed in RAN A, and the access network device 102b can be deployed in RAN B. The AMF-1 corresponds to PLMN A, and the AMF-2 corresponds to PLMN B.

[0163] In some embodiments, AMF-1 and AMF-2 may be the same AMF. Alternatively, AMF-1 and AMF-2 may be different AMFs.

[0164] In combination with the above-mentioned communication system 100, as shown in FIG2A, the method includes steps S2101 to S2110.

[0165] It should be noted that, in some embodiments, the first PLMN can be understood as the PLMN that UE 101 requests to register in the current registration process, that is, the PLMN that the first message requests to register.

[0166] In some embodiments, the second PLMN may be understood as another PLMN other than the first PLMN in the dual registration based on 3GPP access.

[0167] In some embodiments, when UE 101 requests registration on the first PLMN, UE 101 may or may not already be registered on the second PLMN.

[0168] In some embodiments, the third PLMN is a PLMN where UE 101 is already registered.

[0169] In some embodiments, in a dual registration scenario based on 3GPP access, the third PLMN may be a registered PLMN between PLMN A and PLMN B.

[0170] In some embodiments, if UE 101 is already registered in the second PLMN, the third PLMN may be the same as the second PLMN.

[0171] In some embodiments, if UE 101 is not registered in the second PLMN, the third PLMN is different from the second PLMN.

[0172] In some embodiments, in a multi-registration scenario based on 3GPP access, the third PLMN may be a PLMN registered in the PLMN list of UE 101 .

[0173] In some embodiments, UE 101 may use the first access network when accessing the first PLMN.

[0174] In some embodiments, UE 101 may use a second access network when accessing the second PLMN. The second access network may be another 3GPP access network other than the first access network in the dual registration based on 3GPP access.

[0175] In some embodiments, in a dual registration scenario based on 3GPP access, UE 101 may use a third access network when accessing a third PLMN. The third access network may be the first access network or the second access network.

[0176] In some embodiments, in a multi-registration scenario based on 3GPP access, the third access network may also be other 3GPP access networks or non-3GPP access networks, which is not specifically limited in the embodiments of the present disclosure.

[0177] In some embodiments, assuming that the first PLMN is PLMN A and the second PLMN is PLMN B, the communication method provided by the embodiments of the present disclosure is described.

[0178] In some embodiments, UE 101 performs a registration process, that is, UE 101 requests to register with PLMN A (ie, the first PLMN). The registration process includes steps S2101 to S2105.

[0179] In step S2101, UE 101 sends message A-1.

[0180] At this time, the first message is message A-1.

[0181] In some embodiments, UE 101 sends message A-1 to AMF-1.

[0182] In some embodiments, AMF-1 receives message A-1.

[0183] In some embodiments, UE 101 may send message A-1 through RAN A. In this case, the first access network is RAN A and the second access network is RAN B.

[0184] In some embodiments, UE 101 may initiate a registration procedure through RAN A.

[0185] In some embodiments, the registration process may be the first registration process of UE 101. Alternatively, the registration process may be the second registration process of UE 101.

[0186] In some embodiments, UE 101 is not registered in the core network, that is, UE 101 is not registered in any PLMN. At this time, UE 101 initiates the first registration process.

[0187] In some embodiments, the above registration process may be the second registration process of UE 101.

[0188] In some embodiments, UE 101 has performed a first registration process, that is, UE 101 has accessed PLMN A through RAN A and registered on PLMN A. After that, UE 101 initiates a second registration process.

[0189] In some embodiments, UE 101 may access the network through RAN A. For example, UE 101 may access PLMN A through RAN A.

[0190] In some embodiments, UE 101 may access PLMN A through 3GPP AN 102a.

[0191] In some embodiments, RAN A may be a satellite access network, a terrestrial access network, or another type of access network. 3GPP AN 102a may be a satellite, a ground station, or a ground base station. For example, the terrestrial access network may be a NR access network, and 3GPP AN 102a may be a gNB.

[0192] In some embodiments, RAN A may correspond to RAT type A (denoted as RAT type A). In this case, the first RAT type is RAT type A.

[0193] In some embodiments, RAT type A can be used to indicate RAN A. For example, since the access networks used in dual registration based on 3GPP access are all 3GPP access networks, RAT type A can indicate RAN A, thereby simplifying signaling and saving system resources.

[0194] In some embodiments, RAN A may correspond to access type A (denoted as access type A) and RAT type A.

[0195] In some embodiments, access type A and RAT type A may together indicate RAN A.

[0196] In some embodiments, access type A may be an access type corresponding to RAN A, for example, access type A may be 3GPP access.

[0197] In some embodiments, the RAT type A corresponding to RAN A may be low earth orbit (LEO) satellite new radio (LEO-NR) access, NR access, etc. Of course, RAN A may also be an access network of other RAT types, which is not specifically limited in the embodiments of the present disclosure.

[0198] In some embodiments, message A-1 may be used to request registration on PLMN A.

[0199] In some embodiments, message A-1 may be used to request allocation of a registration area in PLMN A for access by UE 101 .

[0200] In some embodiments, PLMN A is the core network selected by UE 101 for access.

[0201] In some embodiments, the message A-1 may be a registration request message.

[0202] In some embodiments, the registration may include an initial registration. For example, message A-1 may be used to request an initial registration, an emergency registration, etc. on PLMN A.

[0203] In some embodiments, the message A-1 may carry a registration type. For example, the message A-1 is used to request an initial registration on PLMN A, and the registration type may be set to initial registration.

[0204] In some embodiments, message A-1 may also carry a subscription concealed identifier (SUCI), a 5G globally unique temporary identifier (5G-GUTI), etc.

[0205] In some embodiments, the message A-1 may carry at least one of the identifier of PLMN A, access type A, and RAT type A.

[0206] In some embodiments, the identifier of PLMN A may be the PLMN ID of PLMN A. For example, the selected PLMN ID carried in the access network (AN) / N2 message.

[0207] In some embodiments, message A-1 may also carry location information, cell identity, etc. of UE 101.

[0208] In some embodiments, after step S2102, AMF-1 may locally determine user subscription information of UE 101. Thereafter, S2104 may be executed.

[0209] In some embodiments, when AMF-1 does not have the user subscription information of UE 101 locally, steps S2102 to S2103 can be executed to request UDM to send the user subscription information of UE 101.

[0210] In some embodiments, after AMF-1 determines that there is no user subscription information of UE 101 locally, AMF-1 may also send message C-1.

[0211] In some embodiments, AMF-1 sends message C-1 to UDM.

[0212] In some embodiments, the UDM receives message C-1.

[0213] In some embodiments, the message C-1 may be used to request the UDM to register for terminal connection management.

[0214] In some embodiments, the message C-1 may be a registration request message, for example, Nudm_UECM_Registration.

[0215] In some embodiments, the message C-1 may carry at least one of the identifier of AMF-1, the identifier of PLMN A, access type A, and RAT type A.

[0216] In some embodiments, the UDM creates, based on the message C-1, information related to at least one of AMF-1, access type A, and RAT type A. For example, the information may include user subscription information of the UE 101 .

[0217] In some embodiments, after creating the relevant information, the UDM returns an acknowledgement message to the AMF-1 to confirm that the AMF-1 is registered with the UDM.

[0218] In some embodiments, AMF-1 receives a confirmation message sent by UDM in response to message C-1. By means of the confirmation message, AMF-1 confirms registration with the UDM.

[0219] In some embodiments, after creating the relevant information, the UDM may also send the user subscription information of UE 101 to SMF-1 and PCF. Here, SMF-1 may be the SMF selected by AMF-1.

[0220] In step S2102, AMF-1 sends message B-1.

[0221] At this time, the second message is message B-1.

[0222] In some embodiments, AMF-1 sends message B-1 to UDM.

[0223] In some embodiments, the UDM receives message B-1.

[0224] In some embodiments, AMF-1 may be an AMF selected by 3GPP AN 102a through an AMF selection method, or AMF-1 may be a serving AMF of UE 101.

[0225] In some embodiments, AMF-1 may be referred to as the AMF that serves UE 101.

[0226] In some embodiments, message B-1 may be used to request user subscription information of UE 101 from the UDM.

[0227] In some embodiments, message B-1 may be a request message, for example, Nudm_SDM_Get.

[0228] In some embodiments, message B-1 may carry at least one of an identifier of AMF-1, an identifier of PLMN A, access type A, and RAT type A. For example, the identifier of AMF-1 may be a globally unique AMF identifier (GUAMI) of AMF-1.

[0229] In some embodiments, AMF-1 receives the user subscription information of UE 101 sent by the UDM in response to message B-1.

[0230] In some embodiments, the user subscription information of UE 101 may be stored in the UDM.

[0231] In step S2103 , the UDM sends the user subscription information of UE 101 .

[0232] In some embodiments, the UDM sends the user subscription information of UE 101 to AMF-1.

[0233] In some embodiments, AMF-1 receives user subscription information of UE 101.

[0234] In some embodiments, the UDM sends the user subscription information of UE 101 to AMF-1 according to message B-1.

[0235] In some embodiments, the UDM sends the user subscription information of UE 101 based on at least one of PLMN A and RAT type A carried in message B-1. For example, the UDM determines the user subscription information of UE 101 based on at least one of the identifier of PLMN A and RAT type A carried in message B-1, and sends the information.

[0236] In some embodiments, the user subscription information of UE 101 may include subscription information A, where subscription information A is associated with at least one of PLMN A and RAT type A. In this case, the first subscription information is subscription information A.

[0237] In some embodiments, the subscription information A may indicate at least one of the following: a forbidden area of ​​PLMN A, a service area restriction of PLMN A, a subscription QoS of PLMN A, and the like.

[0238] In some embodiments, the prohibited area of ​​PLMN A can be understood as the area in PLMN A where UE 101 is prohibited from accessing; the service restriction area of ​​PLMN A can be understood as the area in PLMN A that provides restricted services to UE 101; and the subscribed QoS of PLMN A can be understood as the QoS parameters corresponding to UE 101 in PLMN A.

[0239] Exemplarily, at least one of the prohibited area of ​​PLMN A and the service restricted area of ​​PLMN A may include one or more areas. Then, at least one of the prohibited area of ​​PLMN A and the service restricted area of ​​PLMN A may be indicated by identifiers of one or more areas. For example, at least one of the prohibited area of ​​PLMN A and the service restricted area of ​​PLMN A may be a tracking area (TA), a cell, etc. Then, the subscription information A may include one or more TA identifiers, cell identifiers, etc. to indicate at least one of the prohibited area of ​​PLMN A and the service restricted area of ​​PLMN A. The TA identifier may be a tracking area identity (TAI), and the cell identifier may be the ID of one or more cells covered by PLMN A.

[0240] Exemplarily, the subscribed QoS may include the terminal's aggregate maximum bit rate (UE-aggregate maximum bit rate, UE-AMBR), allocation and retention priority (ARP), guaranteed flow bit rate (guaranteed flow bit rate, GFBR), maximum bit rate (maximum flow bit rate, MFBR), etc., which are not specifically limited in the embodiments of the present disclosure.

[0241] In some embodiments, the user subscription information of UE 101 may include first indication information and subscription information A.

[0242] In some embodiments, the first indication information may indicate whether the terminal supports registration through at least RAN A and RAN B.

[0243] In some embodiments, in a dual registration scenario based on 3GPP access, the first indication information may indicate one of the following: whether the terminal supports registration through RAN A and RAN B, whether the terminal supports registration through two RANs, the terminal's support capability for dual registration based on 3GPP access, the terminal's support capability for dual registration based on 3GPP access authorization, dual registration capability based on 3GPP access, dual registration capability based on 3GPP access authorization, etc.

[0244] In some embodiments, the first indication information may also be referred to as dual registration indication information based on 3GPP access.

[0245] In some embodiments, "the terminal supports registration through RAN A and RAN B" can be understood as: the terminal supports accessing PLMN A through RAN A and registering on PLMN A, and accessing PLMN B through RAN B and registering on PLMN B.

[0246] In some embodiments, “the terminal supports registration through RAN A and RAN B” may also mean that the terminal is allowed (or authorized) to register through RAN A and RAN B.

[0247] In some embodiments, “the terminal does not support registration through RAN A and RAN B” can be understood as: the terminal supports accessing PLMN A through RAN A and registering on PLMN A, or accessing PLMN B through RAN B and registering on PLMN B.

[0248] In some embodiments, “the terminal does not support registration through RAN A and RAN B” may also mean that the terminal is prohibited (or not authorized) from registering through RAN A and RAN B.

[0249] In some embodiments, the first indication information may include an indication field, and different values ​​of the indication field may indicate that the terminal supports or does not support registration through RAN A and RAN B.

[0250] In some embodiments, the above-mentioned indication field may be referred to as a “dual registration over 3GPP accesses authorization” field, a “UE dual registration capability” field, or the like.

[0251] For example, the value of the indication field may be "allowed" or "authorized," thereby indicating that UE 101 supports registration through RAN A and RAN B. The value of the indication field may be "barred" or "unauthorized," thereby indicating that UE 101 does not support registration through RAN A and RAN B. Of course, the value of the indication field may also be other values, which are not specifically limited in the present embodiment.

[0252] In some embodiments, in a multi-registration scenario based on 3GPP access, the first indication information may indicate one of the following: whether the terminal supports registration through n RANs (n is a positive integer greater than or equal to 2), the terminal's support capability for multi-registration based on 3GPP access, the terminal's support capability for multi-registration based on 3GPP access authorization, multi-registration capability based on 3GPP access, multi-registration capability based on 3GPP access authorization, etc.

[0253] In some embodiments, the first indication information may also be referred to as multiple registration indication information based on 3GPP access.

[0254] In some embodiments, "the terminal supports registration through n access networks" can be understood as: the terminal supports accessing one or more PLMNs through n access networks respectively, and registering on these PLMNs respectively.

[0255] In some embodiments, “the terminal supports registration through n access networks” may also mean that the terminal is allowed (or authorized) to register through n access networks.

[0256] In some embodiments, "the terminal does not support registration through n access networks" can be understood as: the terminal supports accessing PLMNs through m access networks (m is a positive integer less than n) among the n access networks, and registering on these PLMNs respectively.

[0257] In some embodiments, “the terminal does not support registration through n access networks” may also mean that the terminal is prohibited (or not authorized) from registering through n access networks.

[0258] In some embodiments, the first indication information may include an indication field, and different values ​​of the indication field may indicate that the terminal supports or does not support registration through n access networks.

[0259] In some embodiments, the above-mentioned indication field may be referred to as a “multiple registration based on 3GPP access authorization” field, a “terminal multiple registration capability” field, or the like.

[0260] For example, the value of the indication field may be "allowed" or "authorized," thereby indicating that the UE 101 supports registration through n access networks. The value of the indication field may be "barred" or "unauthorized," thereby indicating that the UE 101 does not support registration through n access networks. Of course, the value of the indication field may also be other values, which are not specifically limited in the present embodiment.

[0261] In some embodiments, the user subscription information of UE 101 may include the above-mentioned first indication information, subscription information A and subscription information B, and subscription information B is associated with at least one of PLMN B and RAT type B.

[0262] At this time, the second access network is RAN B, the second PLMN is PLMN B, and the second subscription information is subscription information B.

[0263] In some embodiments, RAT type B is a RAT type corresponding to RAN B. In this case, the second RAT type is RAT type B.

[0264] In some embodiments, RAN B may be a satellite access network, a terrestrial access network, or other types of access networks.

[0265] In some embodiments, RAN B may correspond to RAT type B, which is different from RAT type A.

[0266] In some embodiments, RAT type B can be used to indicate RAN B. For example, since the access networks used in dual registration based on 3GPP access are both 3GPP access networks, RAT type B can indicate RAN B, thereby simplifying signaling and saving system resources.

[0267] In some embodiments, RAN B may correspond to access type B and RAT type B. Access type B is the access type corresponding to RAN B.

[0268] In some embodiments, access type B and RAT type B may jointly indicate RAN B.

[0269] In some embodiments, access type B may be an access type corresponding to RAN B, for example, access type B may be 3GPP access.

[0270] In some embodiments, RAT type B may be LEO-NR access, terrestrial access, etc. Of course, RAN B may also be an access network of other RAT types, which is not specifically limited in the embodiments of the present disclosure.

[0271] In some embodiments, the subscription information B may indicate at least one of the following: a prohibited area of ​​PLMN B, a service restriction area of ​​PLMN B, a subscription QoS of PLMN B, and the like.

[0272] In some embodiments, the prohibited area of ​​PLMN B can be understood as the area in PLMN B where UE 101 is prohibited from accessing; the service restriction area of ​​PLMN B can be understood as the area in PLMN B that provides restricted services to UE 101; the subscribed QoS of PLMN B can be understood as the QoS parameters corresponding to UE 101 in PLMN B.

[0273] Exemplarily, at least one of the prohibited area of ​​PLMN B and the service restricted area of ​​PLMN B may include one or more areas. Thus, at least one of the prohibited area of ​​PLMN B and the service restricted area of ​​PLMN B may be indicated by one or more area identifiers. For example, at least one of the prohibited area of ​​PLMN B and the service restricted area of ​​PLMN B may be a TA, a cell, etc. Thus, subscription information B may include one or more TA identifiers, cell identifiers, etc., to indicate at least one of the prohibited area of ​​PLMN B and the service restricted area of ​​PLMN B. The TA identifier may be a TAI, and the cell identifier may be the IDs of one or more cells covered by PLMN B.

[0274] For example, the subscribed QoS may include AMBR, ARP, GFBR, MFBR, etc., which is not specifically limited in the embodiments of the present disclosure.

[0275] In some embodiments, the user subscription information of UE 101 may be predefined or preconfigured, wherein the preconfiguration may be configured by an operator.

[0276] In some embodiments, the user contract information of UE 101 may include at least one of contract information A and contract information B, provided that it includes the first indication information.

[0277] In some embodiments, the user subscription information of UE 101 may include first indication information and subscription information A.

[0278] In some embodiments, when PLMN A and PLMN B are the same PLMN, the user subscription information of UE 101 may include first indication information, subscription information A and subscription information B.

[0279] In some embodiments, the user subscription information of UE 101 includes subscription information A and subscription information B, which may indicate that the terminal supports registration through RAN A and RAN B.

[0280] In some embodiments, the user subscription information of UE 101 includes subscription information A or subscription information B, which may indicate that the terminal does not support registration through RAN A and RAN B.

[0281] In step S2104, AMF-1 accepts or rejects UE 101's registration on PLMN A based on the user subscription information of UE 101.

[0282] In some embodiments, AMF-1 receives the user subscription information of UE 101 sent by UDM and saves it locally.

[0283] In some embodiments, in the first registration process, the user contract information of UE 101 includes at least contract information A.

[0284] In some embodiments, when UE 101 is outside the prohibited area of ​​PLMN A, registration of UE 101 with PLMN A is denied.

[0285] In some embodiments, when UE 101 is located in a prohibited area of ​​PLMN A, registration of UE 101 with PLMN A is denied.

[0286] In some embodiments, AMF-1 determines whether the terminal is located in a prohibited area of ​​PLMN A based on subscription information A.

[0287] In some embodiments, when it is determined based on subscription information A that the terminal is outside the prohibited area of ​​PLMN A, AMF-1 accepts the registration of UE 101 in PLMN A.

[0288] In some embodiments, when it is determined based on subscription information A that the terminal is located in a prohibited area of ​​PLMN A, AMF-1 rejects registration of UE 101 in PLMN A.

[0289] In some embodiments, in the first registration process, the user subscription information of UE 101 includes at least subscription information A. AMF-1 determines, based on subscription information A, that UE 101 is outside the prohibited area of ​​PLMN A. In this case, AMF-1 accepts the registration of UE 101 in PLMN A. Conversely, if AMF-1 determines, based on subscription information A, that UE 101 is located in the prohibited area of ​​PLMN A, AMF-1 rejects the registration of UE 101 in PLMN A.

[0290] In some embodiments, in the second registration process, the user contract information of UE 101 includes the first indication information and contract information A.

[0291] In some embodiments, when the first indication information indicates that UE 101 supports registration through RAN A and RAN B, and it is determined according to subscription information A that the terminal is outside the prohibited area of ​​PLMN A, registration of UE 101 in PLMN A is accepted.

[0292] In some embodiments, the user subscription information of UE 101 includes at least first indication information and subscription information B. Based on the indication of the first indication information, AMF-1 determines that UE 101 supports registration through both RAN A and RAN B. Subsequently, based on subscription information A, AMF-1 determines that UE 101 is outside the prohibited area of ​​PLMN A. At this point, AMF-1 accepts UE 101's registration with PLMN A.

[0293] In some embodiments, when the first indication information indicates that UE 101 supports registration through RAN A and RAN B, and it is determined according to subscription information A that the terminal is located in a prohibited area of ​​PLMN A, registration of UE 101 in PLMN A is rejected.

[0294] In some embodiments, during the second registration process, the user subscription information of UE 101 includes at least the first indication information and subscription information A. Based on the indication of the first indication information, AMF-1 determines that UE 101 supports registration through both RAN A and RAN B. Subsequently, based on subscription information A, AMF-1 determines that UE 101 is located in a prohibited area of ​​PLMN A. At this point, AMF-1 rejects UE 101's registration with PLMN A.

[0295] In some embodiments, assume that UE 101 has completed the first registration process and registered with PLMN B. AMF-1 can then obtain registration information B of UE 101 to determine that UE 101 is registered with PLMN B. In this case, the second registration information is registration information B, the third PLMN is PLMN B, and the third RAT type is RAT type B. The third PLMN is the PLMN where UE 101 is already registered.

[0296] In some embodiments, when AMF-1 and AMF-2 are the same AMF, AMF-1 can obtain the registration information B of UE 101 locally.

[0297] In some embodiments, when AMF-1 and AMF-2 are different AMFs, AMF-1 can receive the registration information B of UE 101 sent by UDM.

[0298] In some embodiments, after receiving the registration information B sent by AMF-2, the UDM may determine that the UE 101 supports registration through RAN A and RAN B, and then send the registration information B to the AMF-1 corresponding to RAN A.

[0299] In some embodiments, when the first indication information indicates that UE 101 does not support registration through RAN A and RAN B, and it is determined that the terminal has been registered in PLMN B, registration of UE 101 in PLMN A is rejected.

[0300] In some embodiments, during the second registration process, the user subscription information of UE 101 includes at least the first indication information and subscription information A. Based on the indication of the first indication information, AMF-1 determines that UE 101 does not support registration through RAN A and RAN B. Subsequently, AMF-1 determines, based on registration information B, that UE 101 is already registered with PLMN B. At this point, AMF-1 rejects UE 101's registration with PLMN A.

[0301] In step S2105, AMF-1 sends message D-1. At this time, the fifth message is message D-1.

[0302] In some embodiments, AMF-1 sends message D-1 to UE 101.

[0303] In some embodiments, UE 101 receives message D-1.

[0304] In some embodiments, message D-1 is used to instruct AMF-1 to complete registration of UE 101.

[0305] In some embodiments, the message D-1 is a response message to the message A-1. For example, the message D-1 may be a registration accept message.

[0306] In some embodiments, message D-1 is used to instruct AMF-1 to reject the registration of UE 101.

[0307] In some embodiments, the message D-1 is a response message to the message A-1. For example, the message D-1 may be a registration reject message.

[0308] In some embodiments, message D-1 is a registration reject message, and a cause value carried in message D-1 indicates that UE 101 is located in a prohibited area of ​​PLMN A.

[0309] In some embodiments, after AMF-1 completes the registration of UE 101 on PLMN A, AMF-1 sends registration information A of UE 101. Registration information A is the registration information of UE 101 in PLMN A. For example, registration information A includes the identifier of AMF-1, the identifier of PLMN A, and RAT type A.

[0310] In some embodiments, AMF-1 sends registration information A to UDM.

[0311] So far, the above is a registration process of UE 101.

[0312] In some embodiments, UE 101 may also perform another registration process, ie, requesting to register with PLMN B (ie, the second PLMN). The registration process includes steps S2106 to S2110.

[0313] In some embodiments, steps S2106 to S2110 may be performed after steps S2101 to S2105 as shown in FIG. 2A , or may be performed before steps S2101 to S2105 (not shown in the figure).

[0314] In step S2106, UE 101 sends message A-2.

[0315] At this time, the first message is message A-2.

[0316] In some embodiments, UE 101 sends message A-2 to AMF-2.

[0317] In some embodiments, AMF-2 receives message A-2.

[0318] In some embodiments, UE 101 may send message A-2 via RAN B. In this case, the first access network is RAN B and the second access network is RAN A.

[0319] In some embodiments, UE 101 may initiate a registration procedure through RAN B.

[0320] In some embodiments, UE 101 may access the network via RAN B. For example, UE 101 may access PLMN B via RAN B.

[0321] In some embodiments, UE 101 may access PLMN B through 3GPP AN 102b.

[0322] In some embodiments, RAN B may be a satellite access network, a terrestrial access network, or another type of access network. 3GPP AN 102b may be a satellite, a ground station, or a ground base station. For example, the terrestrial access network may be a NR access network, and 3GPP AN 102b may be a gNB.

[0323] In some embodiments, RAN B may correspond to RAT type B (denoted as RAT type B). In this case, the first RAT type is RAT type B.

[0324] In some embodiments, RAT type B can be used to indicate RAN B. For example, since the access networks used in dual registration based on 3GPP access are both 3GPP access networks, RAT type B can indicate RAN B, thereby simplifying signaling and saving system resources.

[0325] In some embodiments, RAN B may correspond to access type A and RAT type B.

[0326] In some embodiments, access type A and RAT type B may together indicate RAN B.

[0327] In some embodiments, access type A may be an access type corresponding to RAN B, for example, access type A may be 3GPP access.

[0328] In some embodiments, the RAT type A corresponding to RAN B may be LEO-NR access, NR access, etc. Of course, RAN B may also be an access network of other RAT types, which is not specifically limited in the embodiments of the present disclosure.

[0329] In some embodiments, message A-2 may be used to request registration on PLMN B.

[0330] In some embodiments, message A-2 may be used to request access to an assigned registration domain for UE 101 in PLMN B.

[0331] In some embodiments, PLMN B selects a core network for UE 101 to access.

[0332] In some embodiments, the message A-2 may be a registration request message.

[0333] In some embodiments, the registration may include an initial registration. For example, message A-2 may be used to request an initial registration, an emergency registration, etc. on PLMN B.

[0334] In some embodiments, message A-2 may carry a registration type. For example, message A-2 is used to request initial registration on PLMN B, and the registration type may be set to initial registration.

[0335] In some embodiments, message A-2 may also carry SUCI, 5G-GUTI, etc.

[0336] In some embodiments, the message A-2 may carry at least one of the identifier of PLMN B, access type B, and RAT type B.

[0337] In some embodiments, the identifier of PLMN B may be the PLMN ID of PLMN B. For example, the selected PLMN ID carried in the AN / N2 message.

[0338] In some embodiments, message A-2 may also carry location information, cell identifier, etc. of UE 101.

[0339] In some embodiments, after step S2106, AMF-2 may locally determine user subscription information of UE 101. Thereafter, S2109 may be executed.

[0340] In some embodiments, when AMF-2 does not have the user subscription information of UE 101 locally, steps S2107 to S2108 can be executed.

[0341] In some embodiments, after AMF-2 determines that there is no user subscription information of UE 101 locally, AMF-2 may also send message C-2.

[0342] In some embodiments, AMF-2 sends message C-2 to UDM.

[0343] In some embodiments, message C-2 may be used to request the UDM to register for terminal connection management.

[0344] In some embodiments, the message C-2 may be a registration request message, for example, Nudm_UECM_Registration.

[0345] In some embodiments, message C-2 may carry at least one of the identifier of AMF-2, the identifier of PLMN B, access type B, and RAT type B.

[0346] In some embodiments, the UDM creates, based on the message C-2, information related to at least one of AMF-2, access type B, and RAT type B. For example, the information may include user subscription information of the UE 101 .

[0347] In some embodiments, after creating the relevant information, the UDM returns an acknowledgement message (acknowledge information) to the AMF-1 to confirm that the AMF-2 is registered with the UDM.

[0348] In some embodiments, AMF-2 receives a confirmation message sent by UDM in response to message C-2. Through this confirmation message, AMF-2 confirms registration with UDM.

[0349] In some embodiments, after creating the relevant information, the UDM may also send the user subscription information of UE 101 to SMF-2 and PCF. Here, SMF-2 may be the SMF selected by AMF-2.

[0350] In step S2107, AMF-2 sends message B-2.

[0351] In this case, the second message is message B-2.

[0352] In some embodiments, AMF-2 sends message B-2 to the UDM.

[0353] In some embodiments, the UDM receives message B-2.

[0354] In some embodiments, AMF-2 may be an AMF selected by 3GPP AN 102b through an AMF selection method, or AMF-2 may be a serving AMF of UE 101.

[0355] In some embodiments, AMF-2 may be referred to as the AMF that serves UE 101.

[0356] In some embodiments, message B-2 may be used to request user subscription information of UE 101 from the UDM.

[0357] In some embodiments, message B-2 may be a request message, for example, Nudm_SDM_Get.

[0358] In some embodiments, message B-2 may carry at least one of an identifier of AMF-2, an identifier of PLMN B, access type B, and RAT type B. For example, the identifier of AMF-2 may be the GUAMI of AMF-2.

[0359] In some embodiments, AMF-2 receives the user subscription information of UE 101 sent by the UDM in response to message B-2.

[0360] In some embodiments, the user subscription information of UE 101 may be stored in the UDM.

[0361] In step S2108 , the UDM sends the user subscription information of UE 101 .

[0362] In some embodiments, the UDM sends the user subscription information of UE 101 to AMF-2.

[0363] In some embodiments, AMF-2 receives user subscription information of UE 101.

[0364] In some embodiments, the UDM sends the user subscription information of UE 101 to AMF-2 according to message B-2.

[0365] In some embodiments, the UDM sends the user subscription information of UE 101 based on at least one of PLMN B and RAT type B carried in message B-2. For example, the UDM determines the user subscription information of UE 101 based on at least one of the identifier of PLMN B and RAT type B carried in message B-2, and sends it.

[0366] In some embodiments, the user subscription information of UE 101 may include subscription information B, where subscription information B is associated with at least one of PLMN B and RAT type B. In this case, the first subscription information is subscription information B.

[0367] In some embodiments, the user subscription information of UE 101 may include first indication information and subscription information B.

[0368] In some embodiments, the user subscription information of UE 101 may include the above-mentioned first indication information, subscription information A and subscription information B, and subscription information B is associated with at least one of PLMN B and RAT type B.

[0369] The optional implementation methods of the first indication information, contract information A, and contract information B can be found in the first indication information, contract information A, contract information B and their optional methods, as well as other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0370] In some embodiments, the user contract information of UE 101 may include at least one of contract information A and contract information B, provided that it includes the first indication information.

[0371] In some embodiments, the user subscription information of UE 101 may include first indication information and subscription information B.

[0372] In some embodiments, when PLMN A and PLMN B are the same PLMN, the user subscription information of UE 101 may include first indication information, subscription information A and subscription information B.

[0373] In some embodiments, the user subscription information of UE 101 includes subscription information A and subscription information B, which may indicate that the terminal supports registration through RAN A and RAN B.

[0374] In some embodiments, the user subscription information of UE 101 includes subscription information A or subscription information B, which may indicate that the terminal does not support registration through RAN A and RAN B.

[0375] In step S2109, AMF-2 accepts or rejects UE 101's registration on PLMN B based on the user subscription information of UE 101.

[0376] In some embodiments, AMF-2 receives the user subscription information of UE 101 sent by UDM and saves it locally.

[0377] In some embodiments, AMF-2 determines whether the terminal is located in a prohibited area of ​​PLMN B based on subscription information B.

[0378] In some embodiments, when UE 101 is outside the prohibited area of ​​PLMN B, registration of UE 101 with PLMN B is denied.

[0379] In some embodiments, when UE 101 is located in a prohibited area of ​​PLMN B, registration of UE 101 with PLMN B is denied.

[0380] In some embodiments, when the first indication information indicates that UE 101 supports registration through RAN A and RAN B, and it is determined according to subscription information B that the terminal is outside the prohibited area of ​​PLMN B, registration of UE 101 in PLMN B is accepted.

[0381] In some embodiments, during the second registration process, the user subscription information of UE 101 includes at least the first indication information and subscription information B. Based on the indication of the first indication information, AMF-2 determines that UE 101 supports registration through both RAN A and RAN B. Subsequently, based on subscription information B, AMF-2 determines that UE 101 is outside the prohibited area of ​​PLMN B. At this point, AMF-2 accepts UE 101's registration with PLMN B.

[0382] In some embodiments, when the first indication information indicates that UE 101 supports registration through RAN A and RAN B, and it is determined according to subscription information B that the terminal is located in a prohibited area of ​​PLMN B, registration of UE 101 in PLMN B is rejected.

[0383] In some embodiments, during the second registration process, the user subscription information of UE 101 includes at least the first indication information and subscription information B. Based on the indication of the first indication information, AMF-2 determines that UE 101 supports registration through both RAN A and RAN B. Subsequently, based on subscription information B, AMF-2 determines that UE 101 is located in a prohibited area of ​​PLMN B. At this point, AMF-2 rejects UE 101's registration with PLMN B.

[0384] In some embodiments, assume that UE 101 has completed the first registration process and registered with PLMN A. Then, AMF-2 can obtain registration information A of UE 101 to determine that UE 101 is registered with PLMN A. In this case, the second registration information is registration information A, the third PLMN is PLMN A, and the third RAT type is RAT type A.

[0385] In some embodiments, when AMF-1 and AMF-2 are the same AMF, AMF-2 can obtain the registration information A of UE 101 locally.

[0386] In some embodiments, when AMF-1 and AMF-2 are different AMFs, AMF-2 may receive the registration information A of UE 101 sent by UDM.

[0387] In some embodiments, after receiving the registration information A sent by AMF-1, the UDM may determine that the UE 101 supports registration through RAN A and RAN B, and then send the registration information A to the AMF-2 corresponding to RAN B.

[0388] In some embodiments, when the first indication information indicates that UE 101 does not support registration through RAN A and RAN B, and it is determined that the terminal has been registered in PLMN A, registration of UE 101 in PLMN B is rejected.

[0389] In some embodiments, during the second registration process, the user subscription information of UE 101 includes at least the first indication information and subscription information B. Based on the indication of the first indication information, AMF-2 determines that UE 101 does not support registration through RAN A and RAN B. Subsequently, AMF-2 determines, based on registration information A, that UE 101 is already registered with PLMN A. At this point, AMF-2 rejects UE 101's registration with PLMN B.

[0390] In some embodiments, if AMF-2 determines to accept the registration of UE 101 on PLMN B, AMF-2 registers UE 101.

[0391] In step S2110, AMF-2 sends message D-2.

[0392] In some embodiments, AMF-2 sends message D-2 to UE 101. In this case, the fifth message is message D-2.

[0393] In some embodiments, UE 101 receives message D-2.

[0394] In some embodiments, message D-2 is used to instruct AMF-2 to complete the registration of UE 101.

[0395] In some embodiments, the message D-2 is a response message to the message A-2. For example, the message D-2 may be a registration accept message.

[0396] In some embodiments, message D-2 is used to instruct AMF-2 to reject the registration of UE 101.

[0397] In some embodiments, the message D-2 is a response message to the message A-2. For example, the message D-2 may be a registration reject message.

[0398] In some embodiments, message D-2 is a registration rejection message, and the cause value carried in message D-2 may indicate one of the following: UE 101 is located in a prohibited area of ​​PLMN B, UE 101 does not support dual registration based on 3GPP access and has already registered with PLMN A.

[0399] In some embodiments, after AMF-2 completes the registration of UE 101 on PLMN B, AMF-1 sends registration information B of UE 101. Registration information B is the registration information of UE 101 on PLMN B. For example, registration information B includes the identifier of AMF-2, the identifier of PLMN B, and RAT type B.

[0400] In some embodiments, AMF-2 sends registration information B to UDM.

[0401] So far, the above is another registration process of UE 101.

[0402] In some embodiments, for a multi-registration scenario based on 3GPP access, the Nth registration process of UE 101 is similar to the second registration process, and can be performed with reference to steps S2106 to S2010. Here, the value of N is 3, 4, 5, 6, ...

[0403] In some embodiments, UE 101 may also perform a registration update procedure to request registration update on PLMN A (ie, the first PLMN). The registration process includes steps S2111 to S2113.

[0404] In some embodiments, steps S2111 to S2113 may be performed after steps S2106 to S2110 as shown in FIG. 2A , or may be performed after steps S2101 to S2105 (not shown in the figure).

[0405] In step S2111 , UE 101 sends message A-3.

[0406] At this time, the first message is message A-3.

[0407] In some embodiments, UE 101 sends message A-3 to AMF-1.

[0408] In some embodiments, AMF-1 receives message A-3.

[0409] In some embodiments, UE 101 may send message A-3 via RAN A. In this case, the first access network is RAN A.

[0410] In some embodiments, UE 101 may initiate a registration procedure through RAN A.

[0411] In some embodiments, the above registration process may be a registration update process (registration update) of UE 101 .

[0412] In some embodiments, after UE 101 completes the first registration process and the second registration process, due to the movement of UE 101, UE 101 may leave the registration area allocated to UE 101 in the registered PLMN A. At this time, UE 101 initiates a registration update process.

[0413] In some embodiments, UE 101 may access the network through RAN A. For example, UE 101 may access the core network PLMN A through RAN A.

[0414] In some embodiments, UE 101 may access PLMN A via RAN A and access PLMN B via RAN B.

[0415] In some embodiments, UE 101 may access PLMN A through 3GPP AN 102a and access PLMN B through 3GPP AN 102b.

[0416] In some embodiments, message A-3 may be used to request registration on PLMN A.

[0417] In some embodiments, message A-3 may be used to request access to an assigned registration domain for UE 101 in PLMN A.

[0418] In some embodiments, the message A-3 may be a registration request message.

[0419] In some embodiments, the registration may include a registration update. For example, message A-3 may be used to request at least one of a periodic registration update, a mobility registration update, etc. on PLMN A.

[0420] In some embodiments, the message A-3 may carry a registration type. For example, the message A-3 is used to request a mobility registration update on PLMN A, and the registration type in the message A-3 may be set to mobility registration update.

[0421] In some embodiments, after step S2111, AMF-1 may locally determine user subscription information of UE 101. Thereafter, AMF-1 may execute S2112.

[0422] In some embodiments, when AMF-1 does not have the user subscription information of UE 101 locally, it can execute steps S2102 to S2103 to request UDM to send the user subscription information of UE 101.

[0423] The optional implementation methods of steps S2102 to S2103 can be found in other related parts of the embodiment involved in Figure 2A, and will not be repeated here.

[0424] In step S2112, AMF-1 accepts or rejects UE 101's registration update on PLMN A based on the user subscription information of UE 101.

[0425] It should be noted that FIG2A shows that AMF-1 accepts or rejects UE 101's registration update on PLMN A according to the user subscription information of UE 101.

[0426] In some embodiments, AMF-1 or AMF-2 receives the user subscription information of UE 101 sent by UDM and saves it locally.

[0427] In some embodiments, when it is determined based on user subscription information that UE 101 is located in or outside the prohibited area of ​​PLMN A, the registration update of UE 101 in PLMN A is accepted.

[0428] In some embodiments, when it is determined based on subscription information A that UE 101 is outside the prohibited area of ​​PLMN A, the registration update of UE 101 in PLMN A is accepted.

[0429] In some embodiments, during the registration update process, the user subscription information of UE 101 includes subscription information A. Based on subscription information A, AMF-1 determines that UE 101 is outside the prohibited area of ​​PLMN A. At this time, AMF-1 accepts the registration update of UE 101 in PLMN A and updates the registration domain of PLMN A for UE 101.

[0430] In some embodiments, when it is determined based on subscription information B that UE 101 is located outside the prohibited area of ​​PLMN B, the registration update of UE 101 in PLMN B is accepted.

[0431] In some embodiments, during the registration update process, the user subscription information of UE 101 includes subscription information B. Based on subscription information A, AMF-2 determines that UE 101 is outside the prohibited area of ​​PLMN B. At this time, AMF-2 accepts the registration update of UE 101 in PLMN B and updates the registration domain of PLMN B for UE 101.

[0432] In some embodiments, when it is determined based on user subscription information that UE 101 is located in a prohibited area of ​​PLMN A, registration update of UE 101 in PLMN A is rejected.

[0433] In some embodiments, when it is determined based on subscription information A that UE 101 is located in a prohibited area of ​​PLMN A, registration update of UE 101 in PLMN A is rejected.

[0434] In some embodiments, during the registration update process, the user subscription information of UE 101 includes subscription information A. Based on subscription information A, AMF-1 determines that UE 101 is located in a prohibited area of ​​PLMN A. At this time, AMF-1 rejects the registration update of UE 101 in PLMN A.

[0435] In some embodiments, when it is determined based on subscription information B that UE 101 is located in a prohibited area of ​​PLMN B, registration update of UE 101 in PLMN B is rejected.

[0436] In some embodiments, in the registration update process, the user subscription information of UE 101 includes subscription information B. AMF-2 determines that UE 101 is located in a prohibited area of ​​PLMN B based on subscription information B. At this time, AMF-2 rejects the registration update of UE 101 in PLMN B.

[0437] In step S2113, AMF-1 sends message D-3. In this case, the fifth message is message D-3.

[0438] In some embodiments, AMF-1 sends message D-3 to UE 101.

[0439] In some embodiments, UE 101 receives message D-3.

[0440] In some embodiments, message D-3 is used to instruct AMF-1 to complete the registration update of UE 101.

[0441] In some embodiments, the message D-3 is a response message to the message A-3. For example, the message D-3 may be a registration accept message.

[0442] In some embodiments, message D-3 is used to instruct AMF-1 to reject the registration update for UE 101.

[0443] In some embodiments, the message D-3 is a response message to the message A-3. For example, the message D-3 may be a registration reject message.

[0444] In some embodiments, message D-3 is a registration reject message, and the cause value carried in message D-3 indicates that UE 101 is located in a prohibited area of ​​PLMN A.

[0445] So far, the above is the registration update process of UE 101.

[0446] In some embodiments, UE 101 may also perform a registration update procedure to request a registration update on PLMN B (i.e., the second PLMN). The execution process of the registration update procedure is consistent with steps S2111 to S2113. Optional implementations of the registration update procedure can be found in the optional implementations of steps S2111 to S2113 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be repeated here.

[0447] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2113. For example, steps S2101 to S2105 can be implemented as independent embodiments. For example, the combination of steps S2106 to S2110 can be implemented as an independent embodiment. For example, the combination of steps S2111 to S2113 can be implemented as an independent embodiment. For example, the combination of steps S2101 to S2110 can be implemented as an independent embodiment. The combination of steps S2101 to S2105 and steps S2111 to S2113 can be implemented as an independent embodiment. The combination of steps S2106 to S2110 and steps S2111 to S2113 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S2101 to S2113 are not limited to this.

[0448] In some embodiments, step S2102, step S2103, step S2107, and step S2108 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0449] FIG2B is a second exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. The present embodiment relates to a communication method, and is applied to a communication system 100. For example, the communication system 100 includes a UE 101, a 3GPP AN 102a, a 3GPP AN 102b, an AMF-1, an AMF-2, a UDM, and an AF. 3GPP AN 102a may be deployed in RAN A, 3GPP AN 102b may be deployed in RAN B, AMF-1 corresponds to PLMN A, and AMF-2 corresponds to PLMN B.

[0450] In some embodiments, AMF-1 and AMF-2 may be the same AMF. Alternatively, AMF-1 and AMF-2 may be different AMFs.

[0451] In some embodiments, when the AF is a third-party network function, the AF needs to communicate with the UDM through the NEF. The communication system 100 may further include the NEF.

[0452] In some embodiments, the AF may be deployed within or outside the core network.

[0453] In combination with the above-mentioned communication system 100, as shown in FIG2B, the method includes steps S2201 to S2215.

[0454] In step S2201, UE 101 sends message A.

[0455] In some embodiments, message A may include one of message A-1, message A-2, and message A-3. In this case, the first message is message A.

[0456] Optional implementations of step S2201 can refer to the optional implementations of step S2101, step S2106, and step S2111 in FIG2A , as well as other related parts in the embodiment involved in FIG2A , which will not be repeated here.

[0457] In step S2202, AMF-1 or AMF-2 sends message B.

[0458] In some embodiments, message B may include one of message B-1 and message B-2. In this case, the second message is message B.

[0459] The optional implementation of step S2202 can refer to step S2102 in FIG. 2A , the optional implementation of step S2107 , and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0460] In step S2203 , the UDM sends the user subscription information of UE 101 .

[0461] The optional implementation of step S2203 can refer to step S2103 in FIG. 2A , the optional implementation of step S2208 , and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0462] In step S2204, AMF-1 or AMF-2 accepts or rejects the registration of UE 101 based on the user subscription information of UE 101.

[0463] The optional implementation of step S2204 can refer to step S2104 in FIG. 2A , the optional implementation of step S2109 , and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0464] In step S2205, AMF-1 or AMF-2 sends message D.

[0465] In some embodiments, message D may include one of message D-1 and message D-2. In this case, the fifth message is message D.

[0466] Optional implementations of step S2205 can be found in step S2105, step S2110 and their optional implementations in FIG2A , as well as other related parts in the embodiment involved in FIG2A , which will not be described in detail here.

[0467] In some embodiments, steps S2201 to S2205 may be at least one of a first registration process, a second registration process, and a registration update process for UE 101. Optional implementations of the first registration process, the second registration process, and the registration update process may be found in other related portions of the embodiment described in FIG. 2A and are not further described here.

[0468] In some embodiments, for a multiple registration scenario based on 3GPP access, the i-th registration process of UE 101 is similar to the first registration process, the second registration process, and the registration update process of UE 101, and can be performed with reference to steps S2201 to S2205. Here, the value of i is 1, 2, 3, 4, 5, 6, ...

[0469] In some embodiments, after message D indicates that AMF-1 or AMF-2 receives a registration or registration update of UE 101, the following steps are performed:

[0470] In step S2206, AF sends message E.

[0471] In some embodiments, the AF sends a message E to the UDM. In this case, the third message is the message E.

[0472] In some embodiments, the UDM receives message E.

[0473] In some embodiments, the AF sends the message E to the UDM via the NEF.

[0474] In some embodiments, message E is used to request subscription to event A. In this case, the first event is event A.

[0475] In some embodiments, the message E may be a subscription request message, for example, EventExposure_Subscribe request.

[0476] In some embodiments, message E includes an event subscription request, which is used to request subscription to event A.

[0477] In some embodiments, event A may be that UE 101 registers with RAN A and RAN B. In this case, the first access network is RAN A, and the second access network is RAN B.

[0478] In some embodiments, event A may also be referred to as dual registration of UE 101 based on 3GPP access.

[0479] In some embodiments, if the subscription to event A is authorized by the NEF, the NEF may record the association between the event trigger and the requester identity (e.g., AF). The event report information defines the report type requested by the event subscription (e.g., a one-time report for the first event, a periodic report, an event-based report, etc.).

[0480] In step S2207, the UDM sends message F.

[0481] In some embodiments, the UDM sends a message F to the AF. In this case, the sixth message is the message F.

[0482] In some embodiments, AF receives message F.

[0483] In some embodiments, the UDM sends message F to the AF via the NEF.

[0484] In some embodiments, message F is used to indicate that event A subscription is successful.

[0485] In some embodiments, message F is a response message to message E, for example, EventExposure_Subscribe response.

[0486] In step S2208, UDM sends message G.

[0487] In some embodiments, the UDM sends a message G to the AF. In this case, the fourth message is the message G.

[0488] In some embodiments, the AF receives message G.

[0489] In some embodiments, the UDM sends message G to the AF through the NEF.

[0490] In some embodiments, the UDM autonomously sends message G to the AF.

[0491] In some embodiments, the UDM sends a message G to the AF in response to a subscription to event A.

[0492] In some embodiments, the message G is an event report, which is used to report the event A to the AF. For example, the message G may be EventExposure_Notify.

[0493] In some embodiments, after determining that UE 101 is registered in PLMN A and PLMN B, UDM sends message G to AF.

[0494] In some embodiments, message G may carry registration information C of UE 101 to indicate information about the network with which UE 101 has registered. Exemplarily, registration information C may include the identifier of the PLMN with which UE 101 has registered and the RAT type used during registration. In this case, the third registration information is registration information C of UE 101.

[0495] In some embodiments, the registration information C of UE 101 may include: registration information A of PLMN A and registration information B of PLMN B. For example, the registration information A of PLMN A includes: PLMN ID and RAT type A of PLMN A; the registration information B of PLMN B includes: PLMN ID and RAT type B of PLMN B.

[0496] In some embodiments, for multiple registration scenarios based on 3GPP access, the AF may subscribe to event B from the UDM with reference to steps S2206 and S2207. Event B may be multiple registrations based on 3GPP access. After determining that UE 101 has completed multiple registrations based on 3GPP access, the UDM may report event B to the AF with reference to step S2208. In this case, registration information C may include representations of all PLMNs in which UE 101 has registered and the RAT type used during registration.

[0497] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2208. For example, steps S2210 to S2205 may be implemented as independent embodiments. For example, the combination of steps S2206 and S2208 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S2201 to S2208 are not limited to these.

[0498] In some embodiments, step S2202 and step S2206 may be executed in an interchangeable order or simultaneously.

[0499] In some embodiments, step S2206 and step S2208 may be performed in an interchangeable order or simultaneously.

[0500] In some embodiments, step S2202 and step S2203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0501] In some embodiments, steps S2206 to S2207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0502] In some embodiments, step S2208 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0503] At this point, the dual registration process based on 3GPP access of UE 101 is completed.

[0504] In an embodiment of the present disclosure, after receiving the first message in which the UE requests registration on the first PLMN, the AMF determines whether the terminal is allowed to register on the first PLMN based on the user subscription information associated with the first PLMN and / or the first RAT type. In this way, when the terminal can access through multiple 3GPP access networks at the same time, the 3GPP access networks are distinguished, thereby realizing the registration process of the terminal in the dual 3GPP access scenario.

[0505] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0506] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0507] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0508] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0509] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0510] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0511] Figure 3 is an exemplary flowchart of a communication method performed by a first network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applied to a first network function 1031, such as the aforementioned AMF-1 or AMF-2. As shown in Figure 3, the method includes steps S310 to S350.

[0512] In step S310, a first message is received.

[0513] In some embodiments, the first message may be message A, and message A may include message A-1 and message A-2.

[0514] In some embodiments, the PLMN requested to be registered by the first message is a first PLMN, which may be PLMN A or PLMN B.

[0515] In some embodiments, the second PLMN is another PLMN other than the first PLMN in the dual registration based on 3GPP access. The first PLMN may be PLMN A or PLMN B.

[0516] Optional implementations of step S310 can be found in step S2101, step S2106, step S2011 of FIG. 2A , optional implementations of step S2201 of FIG. 2B , and other related parts of the embodiments involved in FIG. 2A and FIG. 2B , which will not be repeated here.

[0517] In some embodiments, the first network function (such as AMF-1 or AMF-2) receives a first message sent by a terminal (such as UE 101), but is not limited thereto and may also receive a first message from other entities.

[0518] In step S320, a second message is sent.

[0519] In some embodiments, the second message may be message B, and message A may include message B-1 or message B-2.

[0520] Optional implementations of step S320 may refer to step S2102 and step S2107 in FIG. 2A , optional implementations of step S2202 in FIG. 2B , and other related parts in the embodiments involved in FIG. 2A and FIG. 2B , which will not be described in detail here.

[0521] In some embodiments, the first network function (such as AMF-1 or AMF-2) sends the second message to the UDM, but is not limited thereto, and may also receive the first message from other entities.

[0522] In step S330, the user contract information of the terminal is received.

[0523] Optional implementations of step S330 may refer to step S2103 and step S2108 in FIG. 2A , the optional implementations of step S2203 in FIG. 2B , and other related parts in the embodiments involved in FIG. 2A and FIG. 2B , which will not be described in detail here.

[0524] In some embodiments, the first network function (such as AMF-1 or AMF-2) receives user contract information from the terminal of the UDM, but is not limited thereto and may also receive user contract information from the terminal of other entities.

[0525] In step S340, the registration of the terminal is accepted or rejected according to the user contract information of the terminal.

[0526] The optional implementation of step S340 can refer to the optional implementation of step S2105, step S2110, step S2112 in Figure 2A, step S2204 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0527] In step S350, the fifth message is sent.

[0528] In some embodiments, the fifth message may be message D, which may include message D-1, message D-2, or message D-3.

[0529] The optional implementation of step S350 can refer to the optional implementation of step S2101, step S2106, step S2113 in Figure 2A, step S2205 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0530] In some embodiments, the first network function (such as AMF-1 or AMF-2) sends the fifth message to the terminal, but is not limited thereto, and the fifth message may also be sent to other entities.

[0531] In some embodiments, message A in step S310 may further include message A-3. After step S310 is executed, steps S340 to S350 may be executed. Alternatively, if the first network function does not have available user subscription information for the terminal, then, after step S310, steps S320 to S330 may be executed to request the user subscription information for the terminal from the second network function. For the specific process, see the optional methods of steps S2102 to S2103, steps S2107 to S2108 in Figure 2A, steps S2202 to S2203 in Figure 2B, and other related parts of the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0532] The communication method involved in the embodiments of the present disclosure may include at least one of steps S310 to S350. For example, steps S310, S340, and S350 may be implemented as independent embodiments. For example, the combination of steps S320 to S330 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S310 to S350 are not limited to this.

[0533] In some embodiments, step S320 and step S330 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0534] Figure 4 is an exemplary flow chart of a communication method performed by a second network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applicable to a second network function 1032, such as the aforementioned UDM. As shown in Figure 4, the method includes steps S410 to S450.

[0535] In step S410, a second message is received.

[0536] In some embodiments, the second message may be message B, and the second message may include message B-1 or message B-2.

[0537] Optional implementations of step S410 may refer to steps S2102 and S2107 of FIG. 2A , optional implementations of step S2202 of FIG. 2B , and other related parts of the embodiments involved in FIG. 2A and FIG. 2B , which will not be described in detail here.

[0538] In some embodiments, the second network function 1031 may receive the second message from the first network function, but is not limited thereto and may also receive the second message from other entities.

[0539] In step S420, the user contract information of the terminal is sent.

[0540] Optional implementations of step S420 may refer to steps S2103 and S2108 in FIG. 2A , optional implementations of step S2203 in FIG. 2B , and other related parts in the embodiments involved in FIG. 2A and FIG. 2B , which will not be described in detail here.

[0541] In some embodiments, the second network function 1031 may send the user contract information of the terminal to the first network function 103 , but is not limited thereto and may also send the user contract information of the terminal to other entities.

[0542] In step S430, a third message is received.

[0543] In some embodiments, the third message may be message E.

[0544] The optional implementation of step S430 can refer to the optional implementation of step S2206 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0545] In some embodiments, the second network function 1032 may receive a third message from a third network function, but is not limited thereto and may also receive a third message from other entities.

[0546] In step S440, a sixth message is sent.

[0547] In some embodiments, the sixth message may be message F.

[0548] The optional implementation of step S440 can refer to the optional implementation of step S2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0549] In some embodiments, the second network function 1032 may send the sixth message to the third network function, but is not limited thereto and may also send the sixth message to other entities.

[0550] In step S450, a fourth message is sent.

[0551] In some embodiments, the fourth message may be message G.

[0552] The optional implementation of step S450 can refer to the optional implementation of step S2208 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0553] In some embodiments, the second network function 1032 may send the fourth message to the third network function, but is not limited thereto and may also send the fourth message to other entities.

[0554] The communication method involved in the embodiments of the present disclosure may include at least one of step S410 and step S450. For example, the combination of step S450 can be implemented as an independent embodiment. For example, steps S410 to S420 can be implemented as independent embodiments. For example, the combination of step S430 and step S440 can be implemented as an independent embodiment. For example, the combination of step S430 and step S450 can be implemented as an independent embodiment. For example, the combination of step S410, step S420, step S430 and step S440 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S410 to S450 are not limited to this.

[0555] In some embodiments, step S420 and step S430 may be performed in an interchangeable order or simultaneously.

[0556] In some embodiments, step S430 and step S450 may be performed in an interchangeable order or simultaneously.

[0557] In some embodiments, step S430 and step S440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0558] In some embodiments, step S450 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0559] Figure 5 is an exemplary flow chart of a communication method performed by a third network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applicable to a third network function, such as the aforementioned AF. As shown in Figure 5, the method includes steps S510 to S530.

[0560] In step S510, a third message is sent.

[0561] The optional implementation of step S510 can refer to the optional implementation of step S2206 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0562] In some embodiments, the third network function may receive the third message from the second network function 1032 , but is not limited thereto and may also send the third message to other entities.

[0563] In step S520, a sixth message is received.

[0564] The optional implementation of step S520 can refer to the optional implementation of step S2207 in Figure 2A and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0565] In some embodiments, the third network function may receive the fourth message sent from the second network function 1032 , but is not limited thereto and may also send the fourth message to other entities.

[0566] In step S530, a fourth message is received.

[0567] The optional implementation of step S530 can refer to the optional implementation of step S2208 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0568] The communication method involved in the embodiments of the present disclosure may include at least one of step S510 and step S530. For example, step S530 may be implemented as an independent embodiment. For example, step S510 and step S520 may be implemented as independent embodiments. For example, step S530 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from step S510 to step S530 are not limited to this.

[0569] In some embodiments, step S510 and step S530 may be performed in an interchangeable order or simultaneously.

[0570] In some embodiments, step S520 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0571] Figure 6A is another exemplary flow chart of a communication method performed by a first network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applicable to a first network function 1031, such as the aforementioned AMF-1 or AMF-2. As shown in Figure 6A , the method includes steps S6110 to S6120.

[0572] In step S6110, a first message is received.

[0573] The optional implementation of step S6110 can refer to step S2101, step S2106, step S2111 in Figure 2A, the optional implementation of step S2201 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0574] In some embodiments, the first network function (such as AMF-1 or AMF-2) receives the first message sent by the terminal, but is not limited thereto and may also receive the first message from other entities.

[0575] In step S6120, the registration of the terminal is accepted or rejected based on the user contract information of the terminal.

[0576] The optional implementation of step S6120 can be found in step S2105, step S2110, step S2112 of Figure 2A, the optional implementation of step S2204 of Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0577] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6110 to S6130.

[0578] Figure 6B is another exemplary flow chart of a communication method performed by a second network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applicable to a second network function 1032, such as the aforementioned UDM. As shown in Figure 6B , the method includes steps S6210 to S6220.

[0579] In step S6210, a second message is received.

[0580] The optional implementation of step S6210 can refer to step S2102 and step S2107 in Figure 2A, the optional implementation of step S2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0581] In some embodiments, the first network function (such as AMF-1 or AMF-2) receives the first message sent by the terminal, but is not limited thereto and may also receive the first message from other entities.

[0582] In step S6220, the user contract information of the terminal is sent.

[0583] The optional implementation of step S6220 can be found in step S2103 and step S2108 of FIG. 2A , the optional implementation of step S2203 of FIG. 2B , and other related parts in the embodiments involved in FIG. 2A and FIG. 2B , which will not be repeated here.

[0584] In some embodiments, the second network function 1032 (such as UDM) sends the user contract information of the terminal to the first network function 1031, but is not limited thereto and can also receive user contract information of the terminal from other entities.

[0585] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6210 to S6220.

[0586] Figure 6C is another exemplary flow chart of a communication method performed by a third network function according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method applicable to a third network function, such as the aforementioned AF. As shown by the solid line in Figure 6C , the method includes steps S6310 to S6320.

[0587] In step S6310, a third message is sent.

[0588] The optional implementation of step S6110 can refer to the optional implementation of step S2206 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0589] In some embodiments, the third network function may receive the third message from the second network function 1032 , but is not limited thereto and may also send the third message to other entities.

[0590] Furthermore, as shown by the dotted line in FIG6C , after step S6310 , step S6320 may be further executed.

[0591] In step S6320, the fourth message is received.

[0592] The optional implementation of step S6320 can refer to the optional implementation of step S2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0593] In some embodiments, the third network function (such as AF) receives the fourth message from the second network function 1032, but is not limited thereto and may also receive the fourth message from other entities.

[0594] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6310 to S6320.

[0595] Figure 7 is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method and is applied to a core network device. As shown in Figure 7, the method includes steps S710 to S720.

[0596] In step S710 , a first network function receives a first message.

[0597] In some embodiments, the core network device may include a first network function 1031 .

[0598] In some embodiments, the first network function 1031 may receive first information from the terminal.

[0599] In step S720, the first network function accepts or rejects registration of the terminal in the first PLMN according to the user subscription information of the terminal.

[0600] Optional implementations of step S720 may refer to step S2105, step S2110, step S2112 in FIG. 2A , optional implementations of step S2204 in FIG. 2B , and other related parts in the embodiments involved in FIG. 2A and FIG. 2B , which will not be repeated here.

[0601] Figure 8 is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 8 , the communication method in the embodiment of the present disclosure includes steps S810 to S8110.

[0602] In step S810, the UE first accesses the 5GC using satellite NR. The UE sends a registration request to AMF-1 via satellite NR. If it is an initial registration, the registration type included in the request message should indicate initial registration, and the SUCI or 5G-GUTI should also be included in the message.

[0603] In step S820, AMF-1 is selected based on the AMF selection method. As part of the registration process, AMF-1, serving as the AMF for the UE, should register with the UDM using Nudm_UECM_registration. This message may include the GUMAI, access type, and RAT type. The access type is set to 3GPP access. The RAT type is set to LEO NR.

[0604] The UDM creates an association with the AMF identity, access type, and RAT type of the AMF-1 and returns a confirmation message to the AMF-1.

[0605] In step S830, if the AMF-1 does not contain subscription data for the UE, the Nudm_SDM_Get method can be used to request the UE's subscription data from the UDM. If the UE's subscription data indicates that the UE supports dual registration over 3GPP access, the UDM sends the UE's subscription data to the UE associated with the RAT / PLMN with which the UE is registered. For example, the UE's subscription data may include the UE-AMBR, prohibited areas, and service restriction areas for satellite access.

[0606] In step S840, AMF-1 stores the subscription data received from the UDM.

[0607] In step S850, after successfully registering with the 5GC, AMF-1 allocates a 5G-GUTI and includes it in the registration accept message to the UE and sends it to the UE.

[0608] In step S860, if the UE requests a second registration via another access (such as NR), the UE may initiate a similar registration procedure with the network. If the second access has a different PLMN than the first PLMN with which the UE is registered, then during registration, AMF-2 is selected to serve the UE. AMF-2 retrieves the subscription data corresponding to the RAT type / PLMN.

[0609] In step S870, after dual registration on LEO-NR and NR, the UE is moving.

[0610] In step S880, when the UE detects that it is moving out of the registration area of ​​the NR but is still within the registration area of ​​the LEO-NR, the UE shall use the Registration Request message with the Registration Type set to Registration Update and initiate the Mobility Registration Update procedure via the NR.

[0611] In step S890, after receiving the registration request from the UE, AMF-2 determines that the UE's current location is included in the restricted area based on the subscription data.

[0612] In step S8100, AMF-2 sends a Registration Reject to the UE, where the cause value indicates that the UE is in a prohibited area.

[0613] In step S8110, AMF-2 initiates a deregistration procedure to the UE. The UE is only registered via LEO-NR.

[0614] Figure 9 is another exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure. As shown in Figure 9, the communication method in the embodiment of the present disclosure includes steps S910 to S9120.

[0615] In step S910, the UE first accesses the 5GC using satellite NR. The UE sends a registration request to AMF-1 via satellite NR. If it is an initial registration, the registration type included in the request message should indicate initial registration, and the SUCI or 5G-GUTI should also be included in the message.

[0616] In step S920, AMF-1 is selected based on the AMF selection method. As part of the registration process, AMF-1, serving as the AMF for the UE, should register with the UDM using Nudm_UECM_registration. This message may include the GUMAI, access type, and RAT type. The access type is set to 3GPP access. The RAT type is set to LEO NR.

[0617] The UDM creates an association with the AMF identity, access type, and RAT type of the AMF-1 and returns a confirmation message to the AMF-1.

[0618] In step S930, if the AMF-1 does not contain subscription data for the UE, the Nudm_SDM_Get call may be used to request the UE's subscription data from the UDM. If the UE's subscription data indicates that the UE supports dual registration over 3GPP access, the UDM sends the UE's subscription data to the UE associated with the RAT / PLMN with which the UE is registered. For example, the UE's subscription data may include the UE-AMBR, barred areas, and service restriction areas for satellite access.

[0619] In step S940, after successfully registering with the 5GC, AMF-1 allocates a 5G-GUTI and includes it in the registration accept message to the UE and sends it to the UE.

[0620] In step S950, the AF subscribes to one or more events (identified by event IDs) and provides the relevant notification endpoint of the AF by sending an Nnef_EventExposure_Subscribe request. The event can be UE registration information, which indicates that the UE is reported to the RAT / PLMN as registered. If the reporting event subscription is authorized by the NEF, the NEF records the association between the event trigger and the requester identity. The event reporting information defines the requested report type (e.g., one-time report, periodic report, or event-based report for the monitored event).

[0621] In step S960 , according to the authorization in step 5 , the NEF subscribes to the received event (identified by the event ID) and provides the relevant notification endpoint of the NEF to the UDM by sending a Nudm_EventExposure_Subscribe request.

[0622] In step S970 , the UDM confirms the execution of Nudm_EventExposure_Subscribe and sends a Nudm_EventExposure_Subscribe response.

[0623] In step S980 , the NEF sends an Nnef_EventExposure_Subscribe response to confirm the execution of the Nnef_EventExposure_Subscribe to the requester (ie, the AF) that initiated the request.

[0624] In step S990, if the UE requests a second registration via another access (NR), the UE initiates a similar registration procedure to the network. The AMF retrieves subscription data corresponding to the RAT type / PLMN.

[0625] In step S9100, UDM (depending on the event) detects the occurrence of an event, such as a UE registered via LEO-NR and NR. UDM sends the event report and UE registration information along with a timestamp to the relevant notification endpoint of NEF by sending a Nudm_EventExposure_Notify message.

[0626] In step S9110, the NEF forwards the received report event to the AF by sending an Nnef_EventExposure_Notify message.

[0627] In step S9120, based on the event report, the AF knows the UE registered on LEO-NR and NR, and based on the event report, the AF determines to initiate a mobile terminated service (e.g., data service) to the UE via NR access.

[0628] 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.

[0629] The embodiments of the present disclosure also provide an apparatus for implementing any of the above methods. For example, the embodiments of the present disclosure provide an apparatus. The apparatus includes units or modules for implementing each step performed by a terminal in any of the above methods. As another example, another apparatus is provided, including 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.

[0630] 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.

[0631] 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.

[0632] FIG10 is an exemplary structural diagram of a communication device according to an embodiment of the present disclosure. As shown in FIG10 , the communication device 1000 may include at least one of a receiving module 1001 , a processing module 1002 , and a sending module 1003 .

[0633] In some embodiments, the communication device 1000 may be provided in a first network function.

[0634] In some embodiments, the receiving module 1001 is used to receive a first message, where the first message is used by the terminal to request registration in the first PLMN; the processing module 1002 is used to accept or reject the registration of the terminal in the first PLMN based on the user contract information of the terminal; wherein the user contract information includes the first contract information, the first contract information is associated with the first PLMN and / or the first RAT type, the first RAT type corresponds to the first access network, and the first access network is the access network used when the terminal accesses the first PLMN.

[0635] In some embodiments, registration includes an initial registration or a registration update.

[0636] In some embodiments, the processing module 1002 is further configured to obtain user subscription information according to the first PLMN and / or the first RAT type.

[0637] In some embodiments, the sending module 1003 is used to send a second message, the second message is used to request user subscription information, and the second message carries the identifier of the first PLMN and / or the first RAT type; the receiving module 1001 is used to receive user subscription information.

[0638] In some embodiments, the processing module 1002 is further configured to locally determine user subscription information based on the first PLMN and / or the first RAT type.

[0639] In some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscribed QoS of the first PLMN.

[0640] In some embodiments, the user subscription information further includes second subscription information, where the second subscription information is associated with a second PLMN and / or a second RAT type.

[0641] In some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; and a subscribed QoS of the second PLMN.

[0642] In some embodiments, the sending module 1003 is further configured to send first registration information, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0643] In some embodiments, the processing module 1002 is further used to perform at least one of the following: when it is determined based on the first contract information that the terminal is located outside the prohibited area of ​​the first PLMN, accepting the registration of the terminal in the first PLMN; when it is determined based on the first contract information that the terminal is located in the prohibited area of ​​the first PLMN, rejecting the registration of the terminal in the first PLMN.

[0644] In some embodiments, the user subscription information further includes first indication information, where the first indication information is used to indicate whether the terminal supports registration through the first access network and the second access network.

[0645] In some embodiments, the processing module 1002 is further used to perform one of the following: when the first indication information indicates that the terminal supports registration through the first access network and the second access network, and it is determined based on the first contract information that the terminal is located outside the prohibited area of ​​the first PLMN, accept the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal supports registration through the first access network and the second access network, and it is determined based on the first contract information that the terminal is located in the prohibited area of ​​the first PLMN, reject the registration of the terminal in the first PLMN; when the first indication information indicates that the terminal does not support registration through the first access network and the second access network, and it is determined that the terminal has been registered to the third PLMN, reject the registration of the terminal in the first PLMN.

[0646] In some embodiments, the processing module 1002 is further used to obtain second registration information, where the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, where the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN; based on the second registration information, it is determined that the terminal has been registered to the third PLMN.

[0647] In some embodiments, the communication device 1000 may be configured to function as a second network.

[0648] In some embodiments, the receiving module 1001 is used to receive a second message, where the second message is used to request user contract information of the terminal. The second message carries an identifier of a first PLMN and / or a first RAT type, where the first PLMN is the PLMN selected by the terminal to access. The first RAT type corresponds to a first access network, which is the access network used when the terminal accesses the first PLMN. The sending module 1003 is used to send user contract information according to the identifier of the PLMN and / or the first RAT type. The user contract information includes first contract information, and the first contract information is associated with the first PLMN and / or the first RAT type.

[0649] In some embodiments, registration includes an initial registration or a registration update.

[0650] In some embodiments, the first subscription information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; and a subscribed QoS of the first PLMN.

[0651] In some embodiments, the user subscription information further includes second subscription information, where the second subscription information is associated with a second PLMN and / or a second RAT type.

[0652] In some embodiments, the second subscription information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; and a subscribed QoS of the second PLMN.

[0653] In some embodiments, the user subscription information also includes first indication information, which is used to indicate whether the terminal supports registration through the first access network and the second access network; the second access network is the access network used when the terminal accesses the second PLMN, and the second access network corresponds to the second RAT type.

[0654] In some embodiments, the receiving module 1001 is further configured to receive first registration information, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and a first RAT type.

[0655] In some embodiments, the sending module 1003 is also used to send second registration information, and the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, wherein the third PLMN is a PLMN in which the terminal has registered, the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN.

[0656] In some embodiments, the receiving module 1001 is also used to receive a third message, the third message including a first event subscription request, the first event subscription request is used to request to subscribe to a first event registered by the terminal through the first access network and the second access network; wherein, the second access network corresponds to the second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

[0657] In some embodiments, the processing module 1002 is further used to determine whether the terminal is registered in the first PLMN through the first access network and is registered in the second PLMN through the second access network; the sending module 1003 is further used to send a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

[0658] In some embodiments, the communication device 1000 may be configured to function as a third network.

[0659] In some embodiments, the sending module 1003 is used to send a third message, the third message includes a first event subscription request, the first event subscription request is used to request to subscribe to the first event registered by the terminal through the first access network and the second access network; wherein, the first access network corresponds to the first RAT type, and the first access network is the access network used when the terminal accesses the first PLMN; the second access network corresponds to the second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

[0660] In some embodiments, the receiving module 1001 is used to receive a fourth message, the fourth message is used to report the first event, and the fourth message carries third registration information; wherein the third registration information includes the identifier of the first PLMN, the first RAT type, the identifier of the second PLMN and the second RAT type, wherein the first PLMN identifier and the first RAT type are registration information of the terminal registered in the first PLMN through the first access network; the second PLMN identifier and the second RAT type are registration information of the terminal registered in the second PLMN through the second access network.

[0661] In combination with some embodiments of the seventh aspect, in some embodiments, registration includes initial registration or registration update.

[0662] Figure 11 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 1100 can be a network device (e.g., an access network device or a core network device), or a terminal (e.g., a user device), or a chip, chip system, or processor that supports a network device to implement any of the above methods, or a chip, chip system, or processor that supports a terminal to implement any of the above communication methods. Communication device 1100 can be used to implement the communication method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0663] As shown in Figure 11, the communication device 1100 includes one or more processors 1101. The processor 1101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 1101 is used to call instructions to enable the communication device 1100 to execute any of the above communication methods.

[0664] In some embodiments, the communication device 1100 further includes one or more memories 1102 for storing instructions. Optionally, all or part of the memories 1102 may be located outside the communication device 1100.

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

[0666] 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.

[0667] Optionally, the communication device 1100 further includes one or more interface circuits 1104, which are connected to the memory 1102. The interface circuits 1104 may be configured to receive signals from the memory 1102 or other devices, and may be configured to send signals to the memory 1102 or other devices. For example, the interface circuits 1104 may read instructions stored in the memory 1102 and send the instructions to the processor 1101.

[0668] The communication device 1100 described in the above embodiments may be an access network device, a core network device, an external network device, or a terminal, but the scope of the communication device 1100 described in the embodiments of the present disclosure is not limited thereto, and the structure of the communication device 1100 may not be limited by FIG. 11 . 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) other devices.

[0669] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 1100, the communication device 1100 is caused to execute any of the above communication 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.

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

[0671] The embodiment of the present disclosure further provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0672] 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.

[0673] 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 communication method, performed by a first network function, the method comprising: receiving a first message, where the first message is used by a terminal to request registration on a first public land mobile network PLMN; Accepting or rejecting registration of the terminal in the first PLMN according to user subscription information of the terminal; Among them, the user contract information includes first contract information, the first contract information is associated with the first PLMN and / or the first wireless access technology RAT type, the first RAT type corresponds to the first access network, and the first access network is the access network used by the terminal when accessing the first PLMN.

2. The method according to claim 1, wherein: The registration includes initial registration or registration update.

3. The method according to claim 1 or 2, wherein: The method further comprises: The user subscription information is obtained according to the first PLMN and / or the first RAT type.

4. The method according to claim 3, wherein: The obtaining, according to the first PLMN and / or the first RAT type, the user subscription information includes: sending a second message, where the second message is used to request the user subscription information, and the second message carries an identifier of the first PLMN and / or the first RAT type; Receive the user signing information.

5. The method according to any one of claims 1 to 4, wherein: The first contract information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; The subscribed service quality QoS of the first PLMN.

6. The method according to any one of claims 1 to 5, wherein: The user subscription information also includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type. The second PLMN is a PLMN accessed by the terminal through a second access network. The second access network corresponds to the second RAT, and the second RAT type is different from the first RAT type.

7. The method according to claim 6, wherein: The second contract information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; The subscribed QoS of the second PLMN.

8. The method according to any one of claims 1 to 7, wherein: The accepting registration of the terminal in the first PLMN includes: Send first registration information, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and the first RAT type.

9. The method according to any one of claims 1 to 8, wherein: The accepting or rejecting registration of the terminal in the first PLMN according to the user subscription information of the terminal includes one of the following: When it is determined according to the first subscription information that the terminal is located outside the prohibited area of ​​the first PLMN, accepting registration of the terminal in the first PLMN; When it is determined according to the first subscription information that the terminal is located in a prohibited area of ​​the first PLMN, registration of the terminal in the first PLMN is rejected.

10. The method according to any one of claims 1 to 9, wherein: The user subscription information also includes first indication information, where the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network.

11. The method according to claim 10, wherein: The accepting or rejecting registration of the terminal in the first PLMN according to the user subscription information of the terminal includes one of the following: When the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined according to the first subscription information that the terminal is outside the prohibited area of ​​the first PLMN, accepting registration of the terminal in the first PLMN; When the first indication information indicates that the terminal supports registration through at least the first access network and the second access network, and it is determined according to the first subscription information that the terminal is located in a prohibited area of ​​the first PLMN, rejecting registration of the terminal in the first PLMN; When the first indication information indicates that the terminal does not support registration through at least the first access network and the second access network, and it is determined that the terminal has been registered with a third PLMN, registration of the terminal with the first PLMN is rejected.

12. The method according to claim 11, wherein: The determining that the terminal has been registered with the third PLMN includes: Obtaining second registration information, where the second registration information includes at least one of the following: an identifier of the third PLMN and a third RAT type, where the third RAT type corresponds to a third access network, and the third access network is an access network used when the terminal registers to the third PLMN; According to the second registration information, it is determined that the terminal has been registered with the third PLMN.

13. A communication method, performed by a second network function, the method comprising: receiving a second message, where the second message is used to request user subscription information of a terminal, the second message carrying an identifier of a first public land mobile network PLMN and / or a first radio access technology RAT type, where the first PLMN is a PLMN selected by the terminal to access; the first RAT type corresponds to a first access network, and the first access network is an access network used by the terminal when accessing the first PLMN; The user subscription information is sent according to the identifier of the PLMN and / or the first RAT type, where the user subscription information includes first subscription information, and the first subscription information is associated with the first PLMN and / or the first RAT type.

14. The method according to claim 13, wherein: The first contract information is used to indicate at least one of the following: a prohibited area of ​​the first PLMN; a service restriction area of ​​the first PLMN; The subscribed service quality QoS of the first PLMN.

15. The method according to claim 13 or 14, wherein: The user subscription information also includes second subscription information, and the second subscription information is associated with a second PLMN and / or a second RAT type, and the first RAT type is different from the second RAT type, wherein the second PLMN is a PLMN accessed by the terminal through a second access network, the second access network corresponds to the second RAT, and the second RAT type is different from the first RAT type.

16. The method according to claim 15, wherein: The second contract information is used to indicate at least one of the following: a prohibited area of ​​the second PLMN; a service restriction area of ​​the second PLMN; The subscribed QoS of the second PLMN.

17. The method according to any one of claims 13 to 16, wherein: The user subscription information also includes first indication information, and the first indication information is used to indicate whether the terminal supports registration through at least the first access network and the second access network; the second access network is the access network used when the terminal accesses the second PLMN, and the second access network corresponds to the second RAT type.

18. The method according to any one of claims 13 to 17, wherein: The method further comprises: First registration information is received, where the first registration information includes: an identifier of a first network function, an identifier of the first PLMN, and the first RAT type.

19. The method according to any one of claims 13 to 18, wherein: The method further comprises: Send second registration information, the second registration information including at least one of the following: an identifier of a third PLMN and a third RAT type, wherein the third PLMN is a PLMN in which the terminal has been registered, the third RAT type corresponds to a third access network, and the third access network is an access network used when the terminal registers to the third PLMN.

20. The method according to any one of claims 13 to 19, wherein: The method further comprises: receiving a third message, the third message including a first event subscription request, the first event subscription request being used to request subscription to a first event registered by the terminal through the first access network and the second access network; The second access network corresponds to a second RAT type, and the second access network is an access network used when the terminal accesses a second PLMN; the first RAT type is different from the second RAT type.

21. The method according to claim 20, wherein: The method further comprises: Determining that the terminal is registered in the first PLMN through the first access network and is registered in the second PLMN through the second access network; sending a fourth message, where the fourth message is used to report the first event, and the fourth message carries third registration information; The third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

22. A communication method, performed by a third network function, the method comprising: Sending a third message, the third message including a first event subscription request, the first event subscription request being used to request a subscription to a first event registered by the terminal through the first access network and the second access network; Among them, the first access network corresponds to a first radio access technology RAT type, and the first access network is the access network used when the terminal accesses a first public land mobile network PLMN; the second access network corresponds to a second RAT type, and the second access network is the access network used when the terminal accesses a second PLMN; the first RAT type is different from the second RAT type.

23. The method according to claim 22, wherein: The method further comprises: receiving a fourth message, where the fourth message is used to report the first event, and the fourth message carries third registration information; The third registration information includes the identifier of the first PLMN, the first RAT type, and the identifier of the second PLMN. and the second RAT type, wherein the first PLMN identifier and the first RAT type are registration information of the terminal registered in the first PLMN through the first access network; the second PLMN identifier and the second RAT type are registration information of the terminal registered in the second PLMN through the second access network.

24. A communication method, executed by a core network device, wherein: The core network device includes a first network function; Wherein, the method comprises: The first network function receives a first message, where the first message is used by the terminal to request registration in a first public land mobile network PLMN; The first network function accepts or rejects registration of the terminal in the first PLMN according to user subscription information of the terminal; Among them, the user contract information includes first contract information, the first contract information is associated with the first PLMN and / or the first wireless access technology RAT type, the first RAT type corresponds to the first access network, and the first access network is the access network used by the terminal when accessing the first PLMN.

25. The method according to claim 24, wherein: The core network device also includes a second network function; Wherein, the method further comprises: The first network function sends a second message to the second network function, where the second message is used to request the user subscription information, and the second message carries an identifier of the first PLMN and / or the first RAT type; The second network function sends the user subscription information to the first network function according to the identifier of the first PLMN and / or the first RAT type.

26. The method according to claim 25, wherein: The method further comprises: The first network function sends first registration information to the second network function, where the first registration information includes: an identifier of the first network function, an identifier of the first PLMN, and the first RAT type.

27. The method according to claim 25 or 26, wherein: The method further comprises: The second network function sends second registration information to the first network function, and the second registration information includes at least one of the following: an identifier of a third PLMN and a third RAT type, the third PLMN is the PLMN in which the terminal has registered, the third RAT type corresponds to a third access network, and the third access network is the access network used when the terminal registers to the third PLMN.

28. The method according to any one of claims 25 to 27, wherein: The core network device also includes a third network function; Wherein, the method further comprises: The third network function sends a third message to the second network function, and the third message includes a first event subscription request, and the first event subscription request is used to request subscription to a first event registered by the terminal through the first access network and the second access network; the second access network corresponds to a second RAT type, and the second access network is the access network used when the terminal accesses the second PLMN; the first RAT type is different from the second RAT type.

29. The method according to claim 28, wherein: The method further comprises: The second network function determines that the terminal is registered with the first PLMN through the first access network and is registered with the second PLMN through the second access network; The second network function sends a fourth message to the third network function, where the fourth message is used to report the first event, and the fourth message carries third registration information; The third registration information includes: registration information of the terminal registered in the first PLMN through the first access network and registration information of the terminal registered in the second PLMN through the second access network; the registration information of the terminal registered in the first PLMN through the first access network includes the identifier of the first PLMN and at least one of the first RAT type, and the registration information of the terminal registered in the second PLMN through the second access network is the identifier of the second PLMN and at least one of the second RAT type.

30. A communication device, arranged in a first network function; in, The device comprises: A receiving module, configured to receive a first message, where the first message is used by a terminal to request registration in a first public land mobile network PLMN; A processing module, used for user subscription information of the terminal, and accepting or rejecting registration of the terminal in the first PLMN; Among them, the user contract information includes first contract information, the first contract information is associated with the first PLMN and / or the first wireless access technology RAT type, the first RAT type corresponds to the first access network, and the first access network is the access network used by the terminal when accessing the first PLMN.

31. A communication device, arranged in a second network function; in, The device comprises: a receiving module, configured to receive a second message, wherein the second message is used to request user subscription information of a terminal, the second message carries an identifier of a first public land mobile network PLMN and / or a first radio access technology RAT type, the first PLMN being a PLMN selected by the terminal for access; the first RAT type corresponds to a first access network, and the first access network is an access network used by the terminal when accessing the first PLMN; A sending module is used to send the user subscription information according to the identifier of the PLMN and / or the first RAT type, wherein the user subscription information includes first subscription information, and the first subscription information is associated with the first PLMN and / or the first RAT type.

32. A communication device, arranged in a third network function; in, The device comprises: A sending module, configured to send a third message, wherein the third message includes a first event subscription request, wherein the first event subscription request is used to request a subscription to a first event registered by a terminal through a first access network and a second access network; Among them, the first access network corresponds to a first radio access technology RAT type, and the first access network is the access network used when the terminal accesses a first public land mobile network PLMN; the second access network corresponds to a second RAT type, and the second access network is the access network used when the terminal accesses a second PLMN; the first RAT type is different from the second RAT type.

33. A communication device comprising: at least one processor; The communication device is used to execute the method as claimed in any one of claims 1 to 29.

34. A communication system, comprising a first network function and a second network function; wherein: The first network function is configured to implement the method according to any one of claims 1 to 12; The second network function is configured to implement the method according to any one of claims 13 to 21.

35. The communication system according to claim 34, wherein: The communication system further comprises a third network function; the third network function is configured to implement the method as claimed in any one of claims 22 to 23.

36. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 29 is performed.

Images