Registration method and device of shared network and storage medium

Abstract

The application discloses a shared network registration method and device and a storage medium, relates to the field of communication, and can realize network registration of a terminal device in an indirect network sharing scene. The method comprises the following steps: sending subscription data acquisition request information to a unified data management (UDM) network element in a second PLMN network; the subscription data acquisition request information comprises a parameter used for identifying a first PLMN network; receiving target subscription data from the UDM network element in the second PLMN network; and completing registration of the shared network based on the target subscription data. The embodiment of the application is applied to the process of registration of the shared network.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a registration method, apparatus, and storage medium for a shared network. Background Technology

[0002] In indirect network sharing scenarios, the shared base station of the contractor operator connects to the core networks of other participating operators through the contractor operator's core network and broadcasts a Public Land Mobile Network (PLMN) Identity (ID) to each of the other participating operators. This PLMN ID can be the same as or different from the PLMN ID broadcast by the next-generation radio access network (NG-RAN) of the other participating operators' own networks. When a user equipment (UE) belonging to another participating operator initiates network registration in the shared area covered by the contractor operator, the contractor operator's Access and Mobility Management Function (AMF) network element can identify that the UE is accessing the network through indirect network sharing technology and completes network registration after interacting with the corresponding participating operator's core network element.

[0003] In related technologies, the core network elements of other participating operators cannot recognize that the registration process is for a UE accessing the network via indirect network sharing technology, nor can they identify the corresponding contractor operator's network. Therefore, the core network elements of other participating operators cannot correctly provide or obtain data such as contract information related to the contractor operator's network, resulting in the inability to complete network registration correctly. Thus, how to achieve network registration for terminal devices in indirect network sharing scenarios remains a technical problem to be solved. Summary of the Invention

[0004] This application provides a registration method, apparatus, and storage medium for a shared network, used to realize network registration of terminal devices in an indirect network sharing scenario.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, this application provides a registration method for a shared network, comprising: an AMF network element in a first PLMN network sending a subscription data acquisition request to a Unified Data Management (UDM) network element in a second PLMN network; the subscription data acquisition request includes parameters for identifying the first PLMN network; the AMF network element in the first PLMN network receiving target subscription data from the UDM network element in the second PLMN network; and the AMF network element in the first PLMN network completing the registration of the shared network based on the target subscription data.

[0007] In one possible implementation, a registration request is received from a terminal device. The registration request includes a target Public Land Mobile Network (PLMN) ID and a User Privacy Identifier (SUCI), where the SUCI includes a Home Public Land Mobile Network (HPLMN) ID. Based on the selected PLMN ID and HPLMN ID, it is identified that the terminal device accesses the network via indirect network sharing technology, and indirect network sharing parameters are generated. The indirect network sharing parameters are used to identify the identifier of the first PLMN network and the terminal device's access to the network via indirect network sharing technology. A subscription data acquisition request is generated based on the indirect network sharing parameters.

[0008] In one possible implementation, based on the HPLMN ID, the second PLMN network corresponding to the HPLMN ID is determined; a first response information is received from the UDM network element in the second PLMN network, the first response information being used to instruct the UDM network element to complete the creation of registration information.

[0009] In one possible implementation, a first PDU session establishment request message is received from a terminal device; the first PDU session establishment request message includes session information of the terminal device; a second PDU session establishment request message is sent to a Session Management Function (SMF) network element in a first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request message to an SMF network element in the second PLMN network; the second PDU session establishment request message includes indirect network shared parameters, and the third PDU session establishment request message includes indirect network shared parameters.

[0010] The registration method for the shared network in this application can also be applied to the signaling flow between other core network elements, but these will not be described in detail here.

[0011] Secondly, this application provides a registration method for a shared network, comprising: receiving a subscription data acquisition request from an AMF network element in a first PLMN network; the subscription data acquisition request includes an identifier for identifying the first PLMN network; determining target subscription data based on the identifier of the first PLMN network and a subscription data list; the subscription data list includes subscription data corresponding to the identifier of at least one PLMN network; and sending the target subscription data to the AMF network element in the first PLMN network.

[0012] In one possible implementation, if the UDM element in the second PLMN network does not have target subscription data, a first indication message is sent to the AMF element in the first PLMN network; the first indication message is used to indicate that the AMF element in the first PLMN network has failed to register.

[0013] Thirdly, this application provides a registration device for a shared network, comprising: a communication unit and a processing unit; the communication unit is configured to send a subscription data acquisition request to a UDM element in a second PLMN network; the subscription data acquisition request includes parameters for identifying a first PLMN network; the communication unit is configured to receive target subscription data from a UDM element in the second PLMN network; and the processing unit is further configured to complete the registration of the shared network based on the target subscription data.

[0014] In one possible implementation, the communication unit is further configured to receive registration request information from the terminal device; the registration request information includes a target public land mobile network identifier (PLMN ID) and a permanent user identity identifier (SUCI), the SUCI including a home public land mobile network identifier (HPLMN ID); the processing unit is further configured to, based on the selected PLMN ID and HPLMN ID, identify that the terminal device accesses the network through an indirect network sharing technology network, and generate indirect network sharing parameters; the indirect network sharing parameters are used to identify the identifier of the first PLMN network and the terminal device accessing the network through indirect network sharing technology; the processing unit is further configured to, based on the indirect network sharing parameters, generate subscription data acquisition request information.

[0015] In one possible implementation, the processing unit is further configured to determine the second PLMN network corresponding to the HPLMN ID based on the HPLMN ID; the communication unit is further configured to receive first response information from the UDM network element in the second PLMN network, the first response information being used to instruct the UDM network element to complete the creation of registration information.

[0016] In one possible implementation, the communication unit is further configured to receive a first PDU session establishment request message from a terminal device; the first PDU session establishment request message includes session information of the terminal device; the communication unit is further configured to send a second PDU session establishment request message to a Session Management Function (SMF) network element in the first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request message to an SMF network element in the second PLMN network; the second PDU session establishment request message includes indirect network shared parameters, and the third PDU session establishment request message includes indirect network shared parameters.

[0017] Fourthly, this application provides a registration device for a shared network, comprising: a communication unit and a processing unit; the communication unit being configured to receive a subscription data acquisition request from an AMF network element in a first PLMN network; the subscription data acquisition request includes parameters for identifying the first PLMN network; the processing unit being configured to determine target subscription data based on the identifier of the first PLMN network and a subscription data list; the subscription data list includes subscription data corresponding to the identifier of at least one PLMN network; and the communication unit being configured to send the target subscription data to an AMF network element in the first PLMN network.

[0018] In one possible implementation, the communication unit is further configured to instruct the communication unit to send a first indication message to the AMF network element in the first PLMN network when the target subscription data is not available in the UDM network element in the second PLMN network; the first indication message is used to indicate that the AMF network element in the first PLMN network has failed to register.

[0019] Fifthly, embodiments of this application provide a registration apparatus for a shared network, which includes a processor and a memory; wherein the memory is used to store computer execution instructions, and when the registration apparatus for the shared network is running, the processor executes the computer execution instructions stored in the memory to cause the registration apparatus for the shared network to perform the registration method for the shared network as described in the first aspect and any possible implementation thereof.

[0020] In a sixth aspect, embodiments of this application provide a registration apparatus for a shared network, the registration apparatus for a shared network comprising: a processor and a memory; wherein the memory is used to store computer execution instructions, and when the registration apparatus for a shared network is running, the processor executes the computer execution instructions stored in the memory to cause the registration apparatus for a shared network to perform the registration method for a shared network as described in the second aspect and any possible implementation thereof.

[0021] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed by a processor of a registration device for a shared network, enable the registration device for the shared network to perform the registration method for the shared network as described in the first aspect and any possible implementation thereof.

[0022] Eighthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed by a processor of a registration device for a shared network, enable the registration device for the shared network to perform the registration method for the shared network as described in the second aspect and any possible implementation thereof.

[0023] Ninthly, embodiments of this application provide a chip including a processor and a communication interface, the communication interface and the processor being coupled together, the processor being used to run computer programs or instructions to implement the registration method of the shared network described in the first aspect and any possible implementation thereof.

[0024] In a tenth aspect, embodiments of this application provide a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run computer programs or instructions to implement the registration method for a shared network described in any possible implementation of the second aspect above.

[0025] In an eleventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the registration method for a shared network described in the first aspect and any possible implementation thereof.

[0026] In a twelfth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the computer to execute the registration method for a shared network described in the first aspect and any possible implementation thereof.

[0027] In this disclosure, the name of the registration device for the aforementioned shared network does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the function of each device or functional module is similar to that of this disclosure, it falls within the scope of the claims of this disclosure and its equivalents.

[0028] These or other aspects of this application will become more readily apparent in the following description.

[0029] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network sends a subscription data acquisition request to the UDM network element in the second PLMN network. Since the subscription data acquisition request contains an identification parameter for identifying the first PLMN network, the UDM network element in the second PLMN network can recognize that the policy request information comes from the shared network. In this way, the UDM network element in the second PLMN network, based on the identifier and subscription data list of the first PLMN network, determines and sends the target subscription data to the AMF network element in the first PLMN network. Then, the AMF network element in the first PLMN network can complete the registration of the shared network based on the target subscription data. Compared with the prior art, in this application, the UDM network element in the second PLMN network can identify that the subscription data acquisition request information comes from the shared network based on the subscription data acquisition request information containing the identifier of the first PLMN network, and thus accurately configure the target subscription data for the AMF network element in the first PLMN network. This allows the AMF network element in the first PLMN network to complete the registration of the shared network based on the target subscription data, realizing the registration of the terminal device in the shared network. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is a schematic diagram of the structure of a network sharing scenario system provided in an embodiment of this application;

[0032] Figure 2 A schematic diagram of the structure of a registration device for a shared network provided in an embodiment of this application;

[0033] Figure 3 A flowchart illustrating a registration method for a shared network provided in an embodiment of this application;

[0034] Figure 4 A flowchart illustrating a registration method for a shared network provided in an embodiment of this application;

[0035] Figure 5 A graph showing the relationship between the time granularity and the deviation of a target service provided in an embodiment of this application;

[0036] Figure 6 A flowchart illustrating a registration method for a shared network provided in an embodiment of this application;

[0037] Figure 7A diagram showing the relationship between the rate of a first merged call detail record and the downlink rate of the PDCP layer is provided for embodiments of this application.

[0038] Figure 8 A flowchart illustrating a registration method for a shared network provided in an embodiment of this application;

[0039] Figure 9 A flowchart illustrating a registration method for a shared network provided in an embodiment of this application;

[0040] Figure 10 A schematic diagram of the structure of another registration device for a shared network provided in an embodiment of this application;

[0041] Figure 11 This is a schematic diagram of the structure of another registration device for a shared network provided in an embodiment of this application. Detailed Implementation

[0042] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0043] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0044] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0045] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0046] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0047] The following is a definition of the terms used in this application.

[0048] 1. Network sharing scenario system

[0049] The third-generation partnership program of the international telecommunications standards organization (3GPP) rd The Generation Partnership Project (3GPP) defined new network sharing scenarios and requirements in the requirements phase of Release-19 of 5GC. For example, a schematic diagram of the network sharing scenario system structure can be shown as follows: Figure 1 As shown.

[0050] The network sharing scenario system includes the core network equipment of operator A, the core network equipment of operator B, the core network equipment of operator C, the core network equipment of operator X (denoted as the first core network equipment), and the access network equipment of operator X (denoted as the first access network equipment).

[0051] Among them, the access network equipment of operator X is connected to the core network equipment of operator A, the core network equipment of operator B, and the core network equipment of operator C through interfaces N2 and N3, respectively.

[0052] The access network equipment of operator X is used to access the terminal equipment of operators A, B and C, and forward the data of the terminal equipment to the core network equipment of the corresponding operators.

[0053] The scheme for operator X to share NG-RAN base station broadcast PLMN ID can be:

[0054] Option 1: Operator X broadcasts a PLMN ID for each 5GC of operators A, B, and C. This PLMN ID is the same as the one broadcast by operators A, B, and C in their own NG-RAN network. This is referred to as the multi-HPLMN scheme or the old network number scheme. In this way, the UE's PLMN selection process is minimized, especially when the UE is powered on or recovering from no coverage, the offline time is short, existing PLMN IDs are utilized, there is no waste of code resources, and the UE is completely unaware of the process.

[0055] Option 2: Operator X broadcasts a PLMN ID to each 5GC of operators A, B, and C. This PLMN ID is different from the one broadcast by operators A, B, and C in their own NG-RAN networks. This is referred to as the multi-VPLMN scheme or multi-new network number scheme. This scheme involves a longer PLMN ID selection process for the UE, which can lead to longer disconnection times when the UE powers on or recovers from no coverage. Furthermore, using multiple new VPLMN IDs results in a waste of code resources.

[0056] Option 3: Operator X broadcasts the same PLMN ID to multiple 5GCs of operators A, B, and C. This PLMN ID is different from the PLMN ID broadcast by operators A, B, and C's own NG-RAN. This is referred to as the single VPLMN scheme. The PLMN ID selection process for this UE is lengthy, leading to prolonged network disconnection time when the UE powers on or recovers from no coverage. Using a single VPLMN ID, there is no waste of code resources if PLMN ID (X) is used, and less waste if PLMN ID (XY) is used.

[0057] Compared to Scheme 1, Schemes 2 and 3 involve a longer PLMN selection process for the UE, leading to longer disconnection times when the UE powers on or recovers from no coverage. Furthermore, the use of multiple new VPLMN-IDs results in wasted code resources. However, in Scheme 1, when a UE belonging to another operator initiates network registration in a shared area covered by the shared operator, if the selected PLMN ID sent in the registration request is an HPLMID and belongs to the same operator as the HPLMID carried in the UE's SIM card, the shared operator's AMF network element will determine that the UE is a UE belonging to its own network. Therefore, the AMF cannot correctly route the corresponding signaling and data to the home network, causing registration failure and preventing the UE from accessing the shared network.

[0058] For example, a terminal device is a user of operator A, where operator A is the home operator, and operator X is the operator providing indirect network sharing. When the terminal device is in a shared area where there is no 5G base station of operator A but there is a 5G base station of operator X, it can use indirect network sharing technology to continue enjoying 5G services by accessing operator X's 5G base station. In this case, operator A controls and provides services to the terminal device through operator X's core network and the shared NG-RAN. This indirect network sharing technology avoids the network operation and maintenance challenges brought about by multiple core networks simultaneously directly connecting to a single radio node in existing direct connection sharing technologies.

[0059] The above is an explanation of the terms used in this application.

[0060] In network sharing scenarios, the shared base station of the contractor operator connects to the core networks of other participating operators through the contractor operator's core network and broadcasts a PLMN ID to each of the other participating operators. This PLMN ID may be the same as or different from the PLMN ID broadcast by the NG-RAN of the other participating operators' own networks. When a UE belonging to another participating operator initiates network registration in the shared area covered by the contractor operator, the contractor operator's AMF network elements can identify that the UE is accessing the network through indirect network sharing technology and complete the network registration after interacting with the core network elements of the corresponding participating operator.

[0061] In related technologies, the core network elements of other participating operators cannot recognize that the registration process is for indirect network sharing, nor can they identify the corresponding contractor operator's network. Consequently, the core network elements of other participating operators cannot provide the contractor operator's network with the correct subscription data, leading to the failure of network registration. Therefore, how to achieve network registration for terminal devices in indirect network sharing scenarios remains a technical problem to be solved.

[0062] In this embodiment, the AMF (Advanced Management Function) element in the first PLMN network sends policy request information to the UDM (Underlying Management Function) element in the second PLMN network. Since the policy request information contains an identification parameter for the first PLMN network, the UDM element in the second PLMN network can recognize that the policy request information originates from the shared network. Thus, based on the identifier and subscription data list of the first PLMN network, the UDM element in the second PLMN network determines and sends target subscription data to the AMF element in the first PLMN network. The AMF element in the first PLMN network can then complete the shared network registration based on the target subscription data. Compared to existing technologies, the UDM element in the second PLMN network can identify that the policy request information originates from the shared network based on the policy request information containing the identifier of the first PLMN network. Therefore, it can accurately configure target subscription data for the AMF element in the first PLMN network, enabling the terminal device to register with the shared network.

[0063] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems, such as long-term evolution (LTE) systems, 5G mobile communication systems, NR systems, vehicle-to-everything (NR V2X) systems, LTE and 5G hybrid networking systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, and other next-generation communication systems. They can also be non-3GPP communication systems, without limitation.

[0064] The technical solutions of this application embodiment can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), SA, D2D, V2X, and IoT communication scenarios.

[0065] The communication systems and scenarios applicable to this application mentioned above are merely illustrative examples, and are not limited to these examples. This will be explained uniformly here and will not be repeated below.

[0066] In some embodiments, the terminal device involved in this application can be a device for implementing communication functions. The terminal device can also be referred to as user equipment (UE), terminal, access terminal, user unit, user station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, wireless communication device, user agent, or user device, etc. The terminal device can be, for example, a wireless terminal or wired terminal in IoT, V2X, D2D, M2M, 5G networks, or future evolved PLMNs. A wireless terminal can refer to a device with wireless transceiver capabilities, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites).

[0067] For example, terminal devices can be drones, IoT devices (e.g., sensors, electricity meters, water meters, etc.), V2X devices, stations (STs) in wireless local area networks (WLANs), cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices (also known as wearable smart devices), tablets or computers with wireless transceiver capabilities, virtual reality (VR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. The terminal can be a wireless terminal in the home, an in-vehicle terminal, a vehicle with vehicle-to-vehicle (V2V) communication capability, an intelligent connected vehicle, or a drone with drone-to-UAV (U2U) communication capability, etc. The terminal can be mobile or fixed; this application does not specifically limit its location.

[0068] To implement the shared network registration method provided in this application embodiment, this application embodiment provides a shared network registration apparatus for executing the shared network registration method provided in this application embodiment. Figure 2 This is a schematic diagram of the structure of a registration device for a shared network provided in an embodiment of this application. Figure 2 As shown, the registration device 200 of the shared network includes at least one processor 201, a communication line 202, and at least one communication interface 204, and may also include a memory 203. The processor 201, memory 203, and communication interface 204 can be connected via the communication line 202.

[0069] The processor 201 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0070] Communication line 202 may include a path for transmitting information between the aforementioned components.

[0071] The communication interface 204 is used to communicate with other devices or communication networks and can use any transceiver-like device, such as Ethernet, radio access network (RAN), WLAN, etc.

[0072] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code having the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0073] In one possible design, the memory 203 can exist independently of the processor 201, meaning the memory 203 can be an external memory of the processor 201. In this case, the memory 203 can be connected to the processor 201 via the communication line 202 to store execution instructions or application code, and its execution is controlled by the processor 201 to implement the shared network registration method provided in the following embodiments of this application. In another possible design, the memory 203 can also be integrated with the processor 201, meaning the memory 203 can be an internal memory of the processor 201. For example, the memory 203 can be a cache, which can be used to temporarily store some data and instruction information.

[0074] As one possible implementation, processor 201 may include one or more CPUs, for example Figure 2 CPU0 and CPU1 in the example. Alternatively, the registration device 200 of the shared network may include multiple processors, such as... Figure 2 The processors 201 and 207 are included. Alternatively, the registration device 200 for the shared network may also include an output device 205 and an input device 206.

[0075] The following, in conjunction with the appendix Figure 3 The registration method for the shared network provided in the embodiments of this application will be described in detail, such as... Figure 3 As shown, the registration method for this shared network includes:

[0076] S301, the AMF network element in the first PLMN network sends a subscription data acquisition request to the UDM network element in the second PLMN network. Correspondingly, the UDM network element in the second PLMN network receives the subscription data acquisition request from the AMF network element in the first PLMN network.

[0077] The contract data acquisition request information includes parameters used to identify the first PLMN network.

[0078] Optionally, the contract data acquisition request information may also include the selected PLMN ID and Subscriber Confidentiality Identifier (SUCI), where the SUCI includes the HPLMN ID.

[0079] S302. In the second PLMN network, the UDM network element determines the target contract data based on the identifier and contract data list of the first PLMN network.

[0080] The contract data list includes contract data corresponding to the identifier of at least one PLMN network.

[0081] Optionally, the contract data list includes the identifier of at least one PLMN network and the contract data corresponding to the identifier of at least one PLMN network.

[0082] In one possible implementation, the unified data management (UDM) network element in the second PLMN network obtains the list of subscribed data through a server.

[0083] In another possible implementation, the UDM network element in the second PLMN network obtains the list of signed data through specialized equipment.

[0084] It should be explained that the contracted data list is obtained through negotiations between the operator of the second PLMN network and other operators, and the relevant technical personnel store the contracted data list in the UDM network element of the second PLMN network using professional equipment.

[0085] Optionally, specialized equipment can update the list of contracted data in the UDM network elements of the second PLMN network in real time according to the agreement between operators.

[0086] S303. The UDM element in the second PLMN network sends target subscription data to the AMF element in the first PLMN network. Correspondingly, the AMF element in the first PLMN network receives the target subscription data from the UDM element in the second PLMN network.

[0087] In one possible implementation, the UDM network element in the second PLMN network sends the target subscription data to the AMF network element in the first PLMN network through a private network channel.

[0088] It should be explained that the UDM network element in the second PLMN network sends the target subscription data to the AMF network element in the first PLMN network through a private network channel, which can improve the speed and reliability of the target subscription data transmission.

[0089] S304. The AMF network element in the first PLMN network completes the registration of the shared network based on the target subscription data.

[0090] Optionally, the AMF network element in the first PLMN network can also send a second registration response message to the terminal device. Correspondingly, the terminal device sends a registration completion indication to the AMF network element. The second registration response message is used to indicate to the AMF network element that it agrees to register the terminal device.

[0091] Furthermore, when registering a terminal device in the first PLMN network, the AMF can authenticate the terminal device using the AUSF in the first PLMN network. Additionally, the AMF network element can send a registration request message to the UDM network element in the first PLMN network, enabling the UDM network element in the first PLMN network to save the terminal device's session during the registration process, thus completing the registration of the terminal device in the first PLMN network. This also includes UDM and PCF network policies, and obtaining network policies from the PCF network element in the first PLMN network.

[0092] It should be noted that the registration method of the shared network in this application can also be applied to the signaling process between other core network elements, but these will not be described in detail here.

[0093] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network sends a subscription data acquisition request to the UDM network element in the second PLMN network. Since the subscription data acquisition request contains an identification parameter for identifying the first PLMN network, the UDM network element in the second PLMN network can recognize that the policy request information comes from the shared network. In this way, the UDM network element in the second PLMN network, based on the identifier and subscription data list of the first PLMN network, determines and sends the target subscription data to the AMF network element in the first PLMN network. Then, the AMF network element in the first PLMN network can complete the registration of the shared network based on the target subscription data. Compared with the prior art, in this application, the UDM network element in the second PLMN network can identify that the subscription data acquisition request information comes from the shared network based on the subscription data acquisition request information containing the identifier of the first PLMN network, and thus accurately configure the target subscription data for the AMF network element in the first PLMN network. This allows the AMF network element in the first PLMN network to complete the registration of the shared network based on the target subscription data, realizing the registration of the terminal device in the shared network.

[0094] In one possible implementation, combining Figure 3 ,like Figure 4 As shown, before the AMF network element in the first PLMN network sends the subscription data acquisition request information to the UDM network element in the second PLMN network in S301, the AMF network element in the first PLMN network generates the subscription data acquisition request information. The process of the AMF network element in the first PLMN network generating the subscription data acquisition request information can be specifically implemented through the following S401-S403.

[0095] S401, The AMF network element in the first PLMN network receives registration request information from the terminal device.

[0096] The registration request information includes the selected PLMN ID and SUCI, where SUCI includes the HPLMN ID.

[0097] In one possible implementation, when a terminal device moves to a cell served by the first PLMN network, the AMF network element in the first PLMN network receives registration request information from the terminal device.

[0098] It should be explained that when a terminal device moves to a cell served by the first PLMN network, the base station in the first PLMN network will send multiple PLMN IDs to the terminal device. The terminal device selects a PLMN ID from the multiple PLMN IDs and sends the selected PLMN ID and SUCI to the AMF network element in the first PLMN network.

[0099] S402. Based on the selected PLMN ID and HPLMN ID, it is identified that the terminal device accesses the network through indirect network sharing technology, and the AMF network element in the first PLMN network generates indirect network sharing parameters.

[0100] The identifier and terminal equipment used to identify the first PLMN network are connected to the network through indirect network sharing technology.

[0101] Optionally, indirect network sharing parameters include the identifier of the first PLMN network.

[0102] Optionally, if both the selected PLMN ID and HPLMN ID belong to the network identifiers of the second PLMN network, the AMF network element in the first PLMN network generates indirect network shared parameters.

[0103] Understandably, the indirect network sharing parameter can be the PLMN ID (i.e., VPLMNID) of the contractor operator itself, a dedicated PLMN ID negotiated between the contractor operator and the participating operators, or an indirect network sharing indicator.

[0104] Optionally, indirect network sharing parameters can be adapted to all cross-carrier signaling.

[0105] It should be explained that if the selected PLMN ID is different from the HPLMN ID, the AMF network element in the first PLMN network will generate and send a second indication message to the terminal device. The second indication message is used to indicate that the terminal access request has failed.

[0106] S403. The AMF network element in the first PLMN network generates a contract data acquisition request information based on the indirect network shared parameters.

[0107] In one possible implementation, the AMF network element in the first PLMN network adds the indirect network shared parameters to the contract data acquisition request information.

[0108] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network determines whether the terminal device is performing network sharing services based on the selected PLMN ID and HPLMN ID sent by the terminal device. Furthermore, when it is identified that the terminal device accesses the network through indirect network sharing technology based on the selected PLMN ID and HPLMN ID, indirect network sharing parameters and subscription data acquisition request information are generated, so that the UDM network element in the second PLMN network can identify the service needs of the terminal device.

[0109] In one possible implementation, combining Figure 4 ,like Figure 5 As shown, after the AMF network element in the first PLMN network sends the subscription data acquisition request information to the UDM network element in the second PLMN network in S301, the AMF network element in the first PLMN network registers the terminal device information with the UDM network element in the second PLMN network. The process of the AMF network element in the first PLMN network registering the terminal device information with the UDM network element in the second PLMN network can be specifically implemented through the following S501-S502.

[0110] S501. The AMF network element in the first PLMN network determines the second PLMN network corresponding to the HPLMN ID based on the HPLMN ID.

[0111] Optionally, after the AMF network element in the first PLMN network determines the second PLMN network corresponding to the HPLMN ID based on the HPLMN ID, the AMF network element in the first PLMN network sends a first request message to the UDM network element in the second PLMN network.

[0112] The first request information includes the terminal device's session message and the terminal device's access type.

[0113] Optionally, the UDM network element in the second PLMN network receives and saves the first request information.

[0114] S502, the UDM network element in the second PLMN network sends a first response message to the AMF network element in the first PLMN network. Correspondingly, the AMF network element in the first PLMN network receives the first response message from the UDM network element in the second PLMN network.

[0115] The first response information is used to instruct the UDM network element to complete the creation of registration information.

[0116] In one possible implementation, the UDM network element in the second PLMN network sends a second indication message to the AMF network element in the first PLMN network. The second indication message is used to indicate that the session messages of the terminal device and the access type of the terminal device have been saved.

[0117] For example, the first request information includes Nudm_UECM_Registration service operation and / or Nudm_SDM_Get service operation.

[0118] The above scheme brings at least the following beneficial effects: In this embodiment of the application, the AMF network element in the first PLMN network registers the session information of the terminal device with the UDM network element in the second PLMN network based on the HPLM ID, so that the second PLMN network can provide services for the terminal device.

[0119] In one possible implementation, combining Figure 4 ,like Figure 6 As shown in S304, after the AMF network element in the first PLMN network completes the registration of the shared network based on the target subscription data, the AMF network element in the first PLMN network establishes a PDU session. The process of the AMF network element in the first PLMN network establishing a PDU session can be specifically implemented through the following S601-S602.

[0120] S601, the AMF network element in the first PLMN network receives the first PDU session establishment request information from the terminal device.

[0121] The first PDU session establishment request information includes the terminal device's session information.

[0122] In one possible implementation, the AMF network element in the first PLMN network receives the first PDU session establishment request information from the terminal device through the base station, and determines the target Session Management Function (SMF) network element based on the session information of the terminal device.

[0123] The target SMF network element is the SMF network element in the first PLMN network.

[0124] S602. The AMF network element in the first PLMN network sends a second PDU session establishment request message to the SMF network element in the first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request message to the SMF network element in the second PLMN network.

[0125] The second PDU session establishment request information includes indirect network sharing parameters, and the third PDU session establishment request information includes indirect network sharing parameters.

[0126] In one possible implementation, the AMF network element in the first PLMN network sends a second PDU session establishment request message to the target SMF network element.

[0127] It should be explained that after the target SMF network element receives the second PDU session establishment request information, it determines the target User Plane Function (UPF) network element in the second PLMN network based on the second PDU session establishment request information, and then obtains the N4 session. Through the N4 session, it sends the third PDU session establishment request information to the SMF network element in the second PLMN network.

[0128] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network sends a second PDU session establishment request to the SMF network element in the first PLMN network. Since the second PDU session establishment request includes indirect network sharing parameters, the SMF network element in the first PLMN network can identify that the terminal device needs to perform network sharing services, so that the SMF network element in the first PLMN network can quickly perform the network sharing session establishment process.

[0129] In one possible implementation, combining Figure 3 ,like Figure 7 As shown in S303, the process of the UDM network element in the second PLMN network sending the target subscription data to the AMF network element in the first PLMN network can be specifically implemented through the following S701.

[0130] S701. If there is no target subscription data in the UDM network element of the second PLMN network, the UDM network element in the second PLMN network sends a first instruction message to the AMF network element in the first PLMN network.

[0131] The first indication information is used to indicate that the AMF network element in the first PLMN network has failed to register.

[0132] It should be explained that when the AMF network element in the first PLMN network receives the first indication information, it will send a registration failure indication information to the terminal device.

[0133] Furthermore, the terminal device can choose to initiate the PDU session establishment process again.

[0134] The above solution brings at least the following beneficial effects: In this embodiment of the application, when there is no target subscription data in the UDM network element in the second PLMN network, the UDM network element in the second PLMN network sends the first indication information to the AMF network element in the first PLMN network. In this way, the terminal device can promptly send the reported information error, detect and modify it, and promptly request the registrant to establish the shared network again.

[0135] Combined with appendix Figure 8 The registration method for the shared network provided in the embodiments of this application will be described in detail, such as... Figure 8 As shown, the registration method for this shared network includes:

[0136] S801, The terminal device sends a registration request to the RAN.

[0137] S802, RAN selects a new AMF based on the registration request information.

[0138] S803 and RAN send registration request information to the new AMF.

[0139] S804, the new AMF sends the first message to the old AMF.

[0140] The first piece of information includes: Namf-Communication-UEContextTransfer.

[0141] S805, the old AMF sends the first response information to the new AMF.

[0142] The first response information includes: Namf-Communication-UEContextTransfer response.

[0143] S806, the new AMF sends an identity authentication request to the terminal device.

[0144] S807, The terminal device sends an identity authentication response message to the new AMF.

[0145] S808, new AMF selects AUSF.

[0146] S809 and the new AMF perform identity verification.

[0147] S810: The new AMF notifies the old AMF to complete the registration of the terminal equipment.

[0148] S811, the new AMF initiates an identity request process to the terminal device.

[0149] S812, the new AMF determines whether to perform emergency registration.

[0150] S813, New AMF selects target UDM.

[0151] The target UDM is a UDM in another network.

[0152] S814, the new AMF sends registration information to the target UDM.

[0153] S815, the new AMF sends indirect network sharing parameters to the target UDM.

[0154] S816, the new AMF sends subscription information to the target UDM.

[0155] S817, the new AMF sends access information to the target UDM.

[0156] S818, the old AMF sends a cancellation message to the target UDM.

[0157] S819, the new AMF selects PCF.

[0158] S820. Determine the registration type.

[0159] S821, New AMF creates association with N3 IWF.

[0160] S822, the new AMF sends registration acceptance information to the terminal device.

[0161] S823, the new AMF sends registration completion information to the terminal device.

[0162] S824, the new AMF sends a user change instruction to the target UDM.

[0163] S825, the new AMF sends N2 information to the RAN.

[0164] S826, the new AMF sends target indication information to the target UDM.

[0165] Among them, the target indication information is used to indicate support for conversational voice isomorphism.

[0166] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network sends a subscription data acquisition request to the UDM network element in the second PLMN network. Since the subscription data acquisition request contains an identification parameter for identifying the first PLMN network, the UDM network element in the second PLMN network can recognize that the policy request information comes from the shared network. In this way, the UDM network element in the second PLMN network, based on the identifier and subscription data list of the first PLMN network, determines and sends the target subscription data to the AMF network element in the first PLMN network. Then, the AMF network element in the first PLMN network can complete the registration of the shared network based on the target subscription data. Compared with the prior art, in this application, the UDM network element in the second PLMN network can identify that the subscription data acquisition request information comes from the shared network based on the subscription data acquisition request information containing the identifier of the first PLMN network, and thus accurately configure the target subscription data for the AMF network element in the first PLMN network. This allows the AMF network element in the first PLMN network to complete the registration of the shared network based on the target subscription data, realizing the registration of the terminal device in the shared network.

[0167] Combined with appendix Figure 9 The session establishment method for a shared network provided in the embodiments of this application will be described in detail, such as... Figure 9 As shown, the session establishment method for this shared network includes:

[0168] S901, The terminal device sends a PDU session establishment request to the first AMF.

[0169] S902, the first AMF is selected as the first SMF.

[0170] S903, the first AMF sends a PDU session establishment request to the first SMF.

[0171] The PDU session establishment request information includes indirect network sharing parameters.

[0172] S904, the first SMF is selected as the first UPF.

[0173] S905, the first SMF sends an N4 session request to the first UPF.

[0174] S906. The first SMF sends a PDU session establishment request to the second SMF.

[0175] The PDU session establishment request information includes indirect network sharing parameters.

[0176] S907, the second SMF obtains contract data from the second UDM.

[0177] S908. Perform security authentication for PDU session establishment.

[0178] S909, the second SMF is PCF.

[0179] S910, the second SMF initiates the SM policy acquisition from the PCF.

[0180] S911, the second SMF is selected as the second UPF.

[0181] S912, the second SMF initiates the signaling modification process.

[0182] S913, establish an N4 session between the second SMF and the second UPF.

[0183] S914, the second SMF sends a PDU session response message to the first SMF.

[0184] S915, an N4 session is established between the first SMF and the first UPF.

[0185] S916, the first SMF sends the second information to the first AMF.

[0186] The second information includes the identifier of the PDU session, N1SM information, and N2SM information.

[0187] S917, the first AMF sends an N2 PDU session request message to the RAN.

[0188] S918, RAN and terminal equipment establish RRC connection information.

[0189] S919 and RAN send N2 PDU session response information to the first AMF.

[0190] S920, the first AMF sends the third message to the first SMF.

[0191] The third piece of information includes the Nsmf-PDUD Session-Update SM Context Request.

[0192] S921, The first SMF and the first UPF establish an N4 session.

[0193] S922, the first SMF sends the fourth message to the first AMF.

[0194] The fourth piece of information includes the Nsmf-PDUD Session-Update SM Context Response.

[0195] S923, the first SMF notifies the first AMF to release the session.

[0196] S924. Determine the PDU session type.

[0197] S925, the first SMF notifies the second SMF that the Ethernet port has been detected.

[0198] It should be explained that the first AMF, the first SMF, and the first UPF all belong to network elements in the first PLMN network, while the second SMF and the second UPF both belong to network elements in the second PLMN network.

[0199] The above solution brings at least the following beneficial effects: In this embodiment, the AMF network element in the first PLMN network sends a second PDU session establishment request to the SMF network element in the first PLMN network. Since the second PDU session establishment request includes indirect network sharing parameters, the SMF network element in the first PLMN network can identify that the terminal device needs to perform network sharing services, so that the SMF network element in the first PLMN network can quickly perform the network sharing session establishment process.

[0200] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0201] This application embodiment can divide the registration device of the shared network into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0202] like Figure 10 The diagram shown is a structural schematic of a registration device 100 for a shared network provided in an embodiment of this application. The registration device 100 for the shared network includes a communication unit 1001 and a processing unit 1002.

[0203] The communication unit 1001 and the processing unit 1002 are configured to send a subscription data acquisition request to a UDM element in the second PLMN network; the subscription data acquisition request includes parameters for identifying the first PLMN network; the communication unit 1001 is configured to receive target subscription data from a UDM element in the second PLMN network; the processing unit 1002 is further configured to complete the registration of the shared network based on the target subscription data.

[0204] Optionally, the communication unit 1001 is further configured to receive registration request information from the terminal device; the registration request information includes the target public land mobile network identifier (PLMN ID) and the user confidentiality identifier (SUCI), the SUCI including the home public land mobile network identifier (HPLMN ID); the processing unit 1002 is further configured to generate indirect network sharing parameters when both the selected PLMN ID and HPLMN ID belong to the network identifiers of the second PLMN network; the indirect network sharing parameters are used to identify the identifier of the first PLMN network and the terminal device accessing the network through indirect network sharing technology; the processing unit 1002 is further configured to generate subscription data acquisition request information based on the indirect network sharing parameters.

[0205] Optionally, the processing unit 1002 is further configured to determine the second PLMN network corresponding to the HPLMN ID based on the HPLMN ID; the communication unit 1001 is further configured to receive first response information from the UDM network element in the second PLMN network, the first response information being used to instruct the UDM network element to complete the creation of registration information.

[0206] Optionally, the communication unit 1001 is further configured to receive a first PDU session establishment request information from a terminal device; the first PDU session establishment request information includes session information of the terminal device; the communication unit 1001 is further configured to send a second PDU session establishment request information to a session management function (SMF) network element in the first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request information to an SMF network element in the second PLMN network; the second PDU session establishment request information includes indirect network shared parameters, and the third PDU session establishment request information includes indirect network shared parameters.

[0207] like Figure 11 The diagram shown is a structural schematic of a registration device 110 for a shared network provided in an embodiment of this application. The registration device 110 for the shared network includes a communication unit 1101 and a processing unit 1102.

[0208] Communication unit 1101 is used to receive subscription data acquisition request information sent from the AMF network element in the first PLMN network; the subscription data acquisition request information includes parameters for identifying the first PLMN network; processing unit 1102 is used to determine target subscription data based on the identifier of the first PLMN network and the subscription data list; the subscription data list includes the identifier of at least one PLMN network and the subscription data corresponding to the identifier of at least one PLMN network; communication unit 1101 is used to send the target subscription data to the AMF network element in the first PLMN network.

[0209] Optionally, the communication unit 1101 is further configured to instruct the communication unit 1101 to send a first indication message to the AMF network element in the first PLMN network when the UDM network element in the second PLMN network does not have target subscription data; the first indication message is used to indicate that the AMF network element in the first PLMN network has failed to register.

[0210] In this embodiment, processing units 1002 and 1102 can be processors or controllers. They can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. A processor can also be a combination of functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. A communication unit can be a transceiver circuit or a communication interface, etc. A storage module can be a memory. When processing units 1002 and 1102 are processors, the communication unit is a communication interface, and the storage module is a memory, the registration device for the shared network involved in this application embodiment can be... Figure 2 The registration device for the shared network shown.

[0211] Through the above description of the implementation methods, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the network node can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, modules, and network nodes described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0212] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0213] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run computer programs or instructions to implement the registration method of the shared network in the above method embodiments.

[0214] Embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the shared network registration method described in the above method embodiments.

[0215] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In embodiments of the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0216] Since the apparatus, device, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above methods, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0217] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A registration method for a shared network, characterized in that, The method, applied to the Access and Mobility Management Function (AMF) network element in a First Public Land Mobile Network (PLMN), includes: Send a subscription data acquisition request to the Unified Data Management (UDM) network element in the second PLMN network; the subscription data acquisition request includes indirect network shared parameters, which are used to identify the first PLMN network. Receive target subscription data from the UDM network element in the second PLMN network; Based on the target signed data, complete the registration for the shared network; Receive a first Protocol Data Unit (PDU) session establishment request information from a terminal device; the first PDU session establishment request information includes session information of the terminal device. A second PDU session establishment request message is sent to the Session Management Function (SMF) network element in the first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request message to the SMF network element in the second PLMN network; both the second PDU session establishment request message and the third PDU session establishment request message include the indirect network sharing parameters; the first PLMN network is the contractor operator network, and the contractor operator is the operator providing the shared network; the second PLMN network is the participating operator network.

2. The method according to claim 1, characterized in that, The indirect network sharing parameter is used to identify the first PLMN network and / or to identify that the terminal device accesses the network through indirect network sharing technology. The indirect network sharing parameter may be the PLMN ID of the contractor operator network, a dedicated PLMN ID negotiated between the contractor operator network and the participating operator network, or an indirect network sharing indication.

3. The method according to claim 1, characterized in that, Before sending the subscription data acquisition request information to the UDM element in the second PLMN network, the method further includes: Receive registration request information from the terminal device; the registration request information includes the selected Public Land Mobile Network Identifier (PLMN) ID and User Privacy Identifier (SUCI), the SUCI including the Home Public Land Mobile Network Identifier (HPLMN) ID; Based on the selected PLMN ID and the HPLMMN ID, it is identified that the terminal device accesses the network through indirect network sharing technology, and indirect network sharing parameters are generated. The contract data acquisition request information is generated based on the indirect network sharing parameters.

4. The method according to claim 3, characterized in that, Before sending the subscription data acquisition request information to the UDM element in the second PLMN network, the method further includes: Based on the HPLMN ID, determine the second PLMN network corresponding to the HPLMN ID; Receive a first response message from a UDM network element in the second PLMN network. The first response message is used to instruct the UDM network element to complete the creation of registration information.

5. A registration method for a shared network, characterized in that, The method, applied to UDM network elements in a second PLMN network, includes: Receive subscription data acquisition request information sent from the AMF network element in the first PLMN network; the subscription data acquisition request information includes indirect network sharing parameters, which are used to identify the first PLMN network; Based on the identifier and subscription data list of the first PLMN network, target subscription data is determined; the subscription data list includes subscription data corresponding to the identifier of at least one PLMN network. The target subscription data is sent to the AMF network element in the first PLMN network; the first PLMN network is the contractor operator network, and the contractor operator is the operator providing the shared network; the second PLMN network is the participating operator network.

6. The method according to claim 5, characterized in that, The method further includes: If the target subscription data is not found in the UDM network element in the second PLMN network, a first indication message is sent to the AMF network element in the first PLMN network; the first indication message is used to indicate that the AMF network element in the first PLMN network has failed to register.

7. A registration device for a shared network, characterized in that, An Access and Mobility Management Function (AMF) network element applied in a First Public Land Mobile Network (PLMN) network, the device comprising a communication unit and a processing unit: The communication unit is used to send a subscription data acquisition request information to a UDM network element in the second PLMN network; the subscription data acquisition request information includes indirect network shared parameters, which are used to identify the first PLMN network. The communication unit is used to receive target subscription data from the UDM network element in the second PLMN network; The processing unit is also used to complete the registration of the shared network based on the target contract data; as well as Receive a first PDU session establishment request message from a terminal device; the first PDU session establishment request message includes the session information of the terminal device. Send a second PDU session establishment request message to the Session Management Function (SMF) network element in the first PLMN network, so that the SMF network element in the first PLMN network sends a third PDU session establishment request message to the SMF network element in the second PLMN network; Both the second PDU session establishment request information and the third PDU session establishment request information include the indirect network sharing parameters; the first PLMN network is the contractor operator network, and the contractor operator is the operator providing the shared network; the second PLMN network is the participating operator network.

8. A registration device for a shared network, characterized in that, The device, applied to a UDM network element in a second PLMN network, includes a communication unit and a processing unit: The communication unit is used to receive a subscription data acquisition request information sent from an AMF network element in the first PLMN network; the subscription data acquisition request information includes indirect network sharing parameters, which are used to identify the first PLMN network; The processing unit is used to determine the target contract data based on the identifier and contract data list of the first PLMN network; The list of signed data includes signed data corresponding to the identifier of at least one PLMN network; The communication unit is used to send the target subscription data to the AMF network element in the first PLMN network; The first PLMN network is a contractor operator network, which is an operator providing a shared network; the second PLMN network is a participating operator network.

9. A registration device for a shared network, characterized in that, include: A processor and a memory; wherein the memory is used to store computer execution instructions, and when the registration device of the shared network is running, the processor executes the computer execution instructions stored in the memory to cause the registration device of the shared network to perform the registration method of the shared network according to any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed by a registration device for a shared network, cause the computer to perform the registration method for a shared network as described in any one of claims 1-6.

Images