WO2021138822A1 - 签约信息获取方法及装置 - Google Patents

签约信息获取方法及装置 Download PDF

Info

Publication number
WO2021138822A1
WO2021138822A1 PCT/CN2020/070777 CN2020070777W WO2021138822A1 WO 2021138822 A1 WO2021138822 A1 WO 2021138822A1 CN 2020070777 W CN2020070777 W CN 2020070777W WO 2021138822 A1 WO2021138822 A1 WO 2021138822A1
Authority
WO
WIPO (PCT)
Prior art keywords
udm
network
npn
network element
subscription
Prior art date
Application number
PCT/CN2020/070777
Other languages
English (en)
French (fr)
Inventor
朱浩仁
李欢
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080093677.8A priority Critical patent/CN115004635A/zh
Priority to PCT/CN2020/070777 priority patent/WO2021138822A1/zh
Publication of WO2021138822A1 publication Critical patent/WO2021138822A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for acquiring contract information.
  • Non-Public Network NPN
  • SNPN standalone NPN
  • PNI-NPN Public network integrated NPN
  • PLMN Public Land Mobile Network
  • RAN independent access network
  • 5GC core network
  • PNI-NPN PLMN is a network that provides network functions.
  • PNI-NPN can also be further subdivided into two types at present: (1) Closed Access Group (CAG). This type of private network is part of the public PLMN network and is only provided for specific services/users. Service; (2) Slicing. This type of private network also belongs to a type of PNI-NPN network, and uses the slicing feature defined by 5G to use special slicing to provide services for specific services/users.
  • CAG Closed Access Group
  • 5G uses the slicing feature defined by 5G to use special slicing to provide services for specific services/users.
  • 5G defines two ways to dynamically update configuration information: one is triggered by the Access and Mobility Management Function (AMF) network element, which is mainly used to update the subscription information on the UE; the other One is triggered by a policy control function (Policy Control Function, PCF) network element, and is mainly used to update the policy information on the UE.
  • AMF Access and Mobility Management Function
  • PCF Policy Control Function
  • the configuration update process can be used to update the relevant configuration of the UE (including the contract information), but the prerequisite is that the unified data management (Unified Data Management, UDM) or the unified database (Unified Data Repository, UDR) network element has the corresponding contract information
  • UDM Unified Data Management
  • UDR Unified Data Repository
  • the embodiments of the present application provide a communication method and device to simplify the contract for configuring terminal equipment.
  • a communication method including:
  • the first proxy UDM network element receives a first request from a first UDM, where the first request carries a UE identity and a network identity, and the network identity includes a requesting network identity and a serving network identity;
  • the receiving the first request from the first UDM includes:
  • Sending the NPN subscription to the first UDM includes:
  • the method further includes: completing the registration of one or more UDMs according to the registration information submitted by one UDM, so that the first proxy UDM network element can communicate with the one or more UDMs.
  • the registration information submitted by the one UDM includes the registration information of the multiple UDMs.
  • the NPNs of the multiple UDMs and the one UDM include the same group identifier.
  • the first request further includes a first group identifier corresponding to the network identifier, and the network identifier of the second UDM also corresponds to the first group identifier.
  • a communication method including:
  • the first proxy UDM network element receives the NPN contract sent by the second UDM, where the NPN contract includes identification information, and the identification information is used to uniquely identify the NPN;
  • the identification information includes a network identification
  • the sending the NPN subscription to one or more UDMs according to the identification information includes:
  • the identification information further includes a group identification of the network identification, and the sending the NPN subscription to one or more UDMs according to the identification information includes:
  • the method before the first proxy UDM network element receives the NPN subscription sent by the second UDM, the method further includes:
  • the first proxy UDM network element completes the registration of one or more UDMs according to the registration information submitted by one UDM, and the registration information includes network identification and UDM routing information;
  • the sending the NPN subscription to one or more UDMs according to the identification information includes:
  • a UDM network element including a processing module, a receiving module, and a sending module, wherein:
  • the receiving module is configured to receive a first request from a first UDM, where the first request carries a UE identity and a network identity, and the network identity includes a requesting network identity and a serving network identity;
  • the sending module is configured to send a second request to a second UDM according to the network identifier, and the second request carries the UE identifier and the serving network identifier;
  • the receiving module is further configured to receive an NPN contract sent by the second UDM, where the NPN contract includes service identification information and service authorization;
  • the sending module is further configured to send the NPN subscription to the first UDM.
  • the receiving module is specifically configured to:
  • the sending module is specifically used for:
  • the network element includes a processing module for:
  • the registration of one or more UDMs is completed according to the registration information submitted by one UDM, so that the first proxy UDM network element can communicate with the one or more UDMs.
  • the registration information submitted by the one UDM includes the registration information of the multiple UDMs.
  • the NPNs of the multiple UDMs and the one UDM include the same group identifier.
  • the first request further includes a first group identifier corresponding to the network identifier, and the network identifier of the second UDM also corresponds to the first group identifier.
  • a UDM network element including a receiving module and a sending module, wherein:
  • the receiving module is configured to receive an NPN contract sent by a second UDM, where the NPN contract includes identification information, and the identification information is used to uniquely identify the NPN;
  • the sending module is configured to send the NPN subscription to one or more UDMs according to the identification information.
  • the identification information includes a network identification
  • the sending module is specifically configured to:
  • the identification information further includes a group identification of the network identification, and the sending module is specifically configured to:
  • the UDM network element further includes a processing module configured to complete the registration of one or more UDMs according to registration information submitted by one UDM, the registration information including network identification and UDM routing information;
  • the sending module is used for:
  • an embodiment of the present application provides a communication device that has the function of a terminal in any possible implementation manner of the first aspect or the first aspect, or has the function of the second aspect or the second aspect.
  • the function of the control plane network element in any of the possible implementations.
  • the device may be a terminal or a chip included in the terminal.
  • the functions of the above-mentioned communication equipment may be realized by hardware, or may be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the device can be a network device or a chip contained in the network device.
  • the functions of the above-mentioned communication equipment may be realized by hardware, or may be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a processing module and a transceiver module, wherein the processing module is configured to support the device to execute the first aspect or the method in any one of the possible implementations of the first aspect. , Or execute the foregoing second aspect or any one of the possible implementation methods of the second aspect.
  • the structure of the device includes a processor and may also include a memory.
  • the processor is coupled with the memory, and can be used to execute computer program instructions stored in the memory, so that the device executes the method in the first aspect or any one of the possible implementations of the first aspect, or executes the second aspect or the first aspect.
  • the method in any possible implementation of the two aspects.
  • the device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip included in the network device, the communication interface may be an input/output interface of the chip.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • an embodiment of the present application provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or an instruction, when the program or an instruction is executed by the processor , So that the chip system implements the method in any possible implementation manner of the first aspect or the first aspect, or executes the method in any possible implementation manner of the second aspect or the second aspect.
  • the chip system further includes an interface circuit, which is used to exchange code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program or instruction is stored.
  • the computer executes the first aspect or any one of the first aspect.
  • the method in one possible implementation manner, or the method in the foregoing second aspect or any one of the possible implementation manners of the second aspect is executed.
  • the embodiments of the present application provide a computer program product.
  • the computer reads and executes the computer program product, the computer executes the method in the first aspect or any one of the possible implementations of the first aspect. , Or execute the foregoing second aspect or any one of the possible implementation methods of the second aspect.
  • an embodiment of the present application provides a communication system that includes one or more storage network elements described above.
  • the communication system may also include control plane devices, other network devices and/or terminals .
  • FIG. 1A is a schematic diagram of a system framework provided by an embodiment of this application.
  • FIG. 1B is a schematic diagram of another system framework provided by an embodiment of this application.
  • FIG. 1C is a schematic diagram of another system framework provided by an embodiment of this application.
  • FIG. 1D is a schematic diagram of an NPN contract acquisition scenario provided by an embodiment of the application.
  • FIG. 1E is a schematic diagram of direct connection of multiple private networks according to an embodiment of the application.
  • 2A is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 2B is a schematic diagram of an indirect connection of multiple private networks according to an embodiment of this application.
  • 2C is another schematic diagram of indirect connection of multiple private networks provided by an embodiment of the application.
  • Figure 2D is a schematic diagram of a UDM registration process provided by an embodiment of the application.
  • FIG. 2E is a schematic diagram of another UDM registration process provided by an embodiment of the application.
  • 2F is another schematic diagram of indirect connection of multiple private networks provided by an embodiment of the application.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 4 is a schematic block diagram of a communication device provided by an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • Terminal equipment can be user equipment (UE), handheld terminal, notebook computer, subscriber unit, cellular phone, smart phone, wireless data card, personal digital assistant (personal digital assistant) digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer, cordless phone or wireless local loop (WLL) Stations, machine type communication (MTC) terminals or other devices that can access the network.
  • UE user equipment
  • handheld terminal notebook computer
  • subscriber unit cellular phone
  • smart phone wireless data card
  • PDA personal digital assistant
  • modem modem
  • handheld device handheld
  • laptop computer cordless phone or wireless local loop (WLL) Stations
  • MTC machine type communication
  • the terminal equipment and the access network equipment use some kind of air interface technology to communicate with each other.
  • Radio Access Network (RAN) equipment Mainly responsible for radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • the access network equipment may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and so on.
  • base stations such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and so on.
  • the names of devices with base station functions may be different.
  • 5G 5th generation
  • gNB in the LTE system, it is called gNB.
  • gNB in the LTE system, it is called gNB.
  • gNB in the LTE system
  • gNB In the 3rd generation, 3G) system, it is called a Node B (Node B), etc.
  • Node B Node B
  • Mobility management network element It is a core network network element and is mainly responsible for signaling processing, such as access control, mobility management, attachment and detachment, and gateway selection.
  • the mobility management network element When the mobility management network element provides services for the session in the terminal device, it will provide storage resources of the control plane for the session, as well as storage of the session identifier, the SMF network element identifier associated with the session identifier, and so on.
  • mobility management network elements can be core network access and mobility management function (core access and mobility management function, AMF) network elements.
  • future communications such as the 6th generation (6G) communications, mobile
  • 6G 6th generation
  • the sexual management network element may still be an AMF network element or have other names, which is not limited in this application.
  • Non-3GPP access network equipment This network element allows the terminal equipment and the 3GPP core network to use non-3GPP technologies for interconnection and intercommunication, among which non-3GPP technologies such as: Wireless Fidelity (Wi-Fi), Global Microwave Interconnection Access ( Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA) networks, etc., compared to trusted non-3GPP access network equipment, they can directly access the 3GPP core network, and this network element needs to pass through a security gateway The established security tunnel is used for interconnection and intercommunication with the 3GPP core network, where the security gateway is for example: Evolved Packet Data Gateway (ePDG) or Non-3GPP InterWorking Function (N3IWF) network element.
  • ePDG Evolved Packet Data Gateway
  • N3IWF Non-3GPP InterWorking Function
  • non-3GPP access network devices can be untrusted non-3GPP Access Network (Untrusted non-3GPP Access Network) devices.
  • non-3GPP access network devices can still be untrusted non-3GPP access network devices.
  • 3GPP access network equipment, or other names, is not limited in this application.
  • Session management network element Mainly used for session management in mobile networks, responsible for user-plane network element selection, user-plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and QoS control .
  • the session management network element may be a session management function (SMF) network element.
  • SMF session management function
  • future communications such as 6G, the session management network element may still be an SMF network element or have other names. This application does not Make a limit.
  • User plane network element responsible for forwarding and receiving user data in terminal equipment.
  • User data can be received from the data network and transmitted to the terminal device through the access network device; the user plane network element can also receive the user data from the terminal device through the access network device and forward it to the data network.
  • the transmission resources and scheduling functions in the user plane network element that provide services for the terminal equipment are managed and controlled by the SMF network element.
  • user plane network elements can be user plane function (UPF) network elements.
  • future communications such as 6G
  • user plane network elements can still be UPF network elements or have other names. This application does not Make a limit.
  • Policy control network element It mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to the policy.
  • the policy control network element may be a policy and charging rules function (PCRF) network element.
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • future communication systems such as 6G, the policy control network element may still be a PCF network element, or may also have other names, which are not limited by this application.
  • Authentication server It mainly provides authentication functions and supports authentication of 3GPP access and Non-3GPP access.
  • the authentication server may be an authentication server function (authentication server function, AUSF) network element.
  • AUSF authentication server function
  • the authentication server may still be an AUSF network element, or may also have other names, which is not limited by this application.
  • Capability opening network element It mainly supports the secure interaction between 3GPP networks and third-party applications. NEF can safely expose network capabilities and events to third parties to enhance or improve application service quality. 3GPP networks can also securely obtain relevant information from third parties. Data is used to enhance the intelligent decision-making of the network; at the same time, the network element supports the recovery of structured data from the unified database or the storage of structured data in the unified database.
  • the capability opening network element may be a network capability opening function entity (Network Exposure Function, NEF) network element.
  • NEF Network Exposure Function
  • the capability opening network element may still be a NEF network element, or may have other names, which is not limited by this application.
  • Data storage network element Mainly responsible for storing structured data.
  • the stored content includes contract data and policy data, structured data exposed to the outside world and application-related data.
  • the data storage network element may be a unified data repository (UDR) network element.
  • UDR unified data repository
  • the data storage network element may still be a UDR network element, or may also have other names, which are not limited by this application.
  • Data management network element Based on user subscription data (including authentication data) stored in the UDR, it provides users with services such as access authorization, registration, business continuity, and short messages.
  • the data management network element may be a unified data management (Unified Data Management, UDM) network element.
  • UDM Unified Data Management
  • the data management network element may still be a UDM network element, or may also have other names, which are not limited by this application.
  • Application network element It mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • the application network element may be an application function (AF) network element.
  • AF application function
  • future communication systems such as 6G, the application network element may still be an AF network element, or may also have other names, which are not limited by this application.
  • the foregoing network element or device may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the above-mentioned network element or device can be divided into one or more services, and further, there may be services independent of network functions.
  • an instance of the above-mentioned function, an instance of a service included in the above-mentioned function, or an instance of a service that exists independently of the network function may be referred to as a service instance.
  • Figure 1A is a schematic diagram of a system framework provided by an embodiment of the application.
  • the current 5G 3GPP system architecture is shown in Figure 1A.
  • the main network functions and entities included are: UE, (R)AN, UPF, Data Network (DN), AMF, SMF, PCF, AF, Network Slice Selection Function (NSSF), AUSF and UDM.
  • the figure shows the interaction relationship between the network functional entities and the corresponding interfaces.
  • the UE and the AMF can interact through the N1 interface.
  • the interactions between other network functional entities are similar and will not be repeated.
  • Fig. 1B is a schematic diagram of another system framework provided by an embodiment of the application. As shown in Fig. 1B, some interfaces in the 3GPP system architecture can be implemented in a service-oriented interface. Data Analytics Function (NWDAF) network elements and other network function network elements can interact through the service interface Nnwdaf. For example, network slice selection function (Network Slice Selection Function, NSSF) network elements interact through the service interface Nnssf.
  • NWSF Network Slice Selection Function
  • the UE, (R)AN, UPF, and DN in Figure 1A and Figure 1B are usually called user layer network functional entities.
  • User data traffic can be transmitted through the PDU Session established between the UE and DN, and the transmission will go through (R) )
  • the two network functions (entities) of AN and UPF; and the other parts are called control layer network functions and entities, which are mainly responsible for functions such as authentication and authentication, registration management, session management, mobility management, and policy control. So as to realize the reliable and stable transmission of user-level traffic.
  • Figure 1C is a schematic diagram of another system framework provided by an embodiment of the application. As shown in Figure 1C, it is a non-3GPP system architecture in 5G.
  • the connection function Non-3GPP InterWorking Function, N3IWF
  • N3IWF Non-3GPP InterWorking Function
  • the UE obtains the authority to communicate with network functions and entities in a certain NPN through the subscription information.
  • the subscription information can include: basic subscription or default subscription (UE identity or certificate), which is used to authorize the terminal to temporarily access Enter the NPN, where temporary access means restricted access and/or restricted time access; NPN signing includes service identification information (such as Closed Access Group Identity document, CAG ID), network identifier (Network Identifier) ,NID), data network name (Data Network Name, DNN) and other information) and service authorization are used to authorize normal access to NPN and use of NPN related services.
  • service identification information such as Closed Access Group Identity document, CAG ID
  • network identifier Network Identifier
  • DNN Data Network Name
  • the group has deployed different private networks in different regions.
  • the group can be China Mobile Communications Group Co., Ltd, CMCC, China Unicom, or American Telephone & Telegraph. , AT&T), etc.
  • the private network can be a dedicated network deployed by a group, school, enterprise or government.
  • the UE can temporarily access different private networks in the group using basic or default contracts. However, whether the private network service can be used normally requires the UE to include NPN signed.
  • Figure 1D is a schematic diagram of an NPN subscription acquisition scenario provided by an embodiment of this application. As shown in Figure 1D, the UE has been configured with the group’s basic subscription or general certificate and configured with the NPN2 NPN subscription.
  • the UE can Normally access NPN2 and use NPN2 services normally; in some cases, the UE moves to a different private network NPN1 under the same group. At this time, the UE can only temporarily access NPN1 using the basic contract or general certificate of the group; when NPN1 discovers When the UE does not include the current private network's NPN contract, it will actively try to obtain the NPN contract.
  • the specific acquisition place can be obtained from the private network NPN2 (assuming NPN2 is the parent company network), or NPN1 can also be from any contract that contains the NPN Obtained by a third party; of course, the private network NPN2 can also actively push the UE’s NPN subscription to the private network NPN1.
  • the pushed subscription can be the private network NPN1’s NPN subscription or other NPN subscriptions.
  • NPN1 there are basic subscriptions/general certificates, and NPN subscriptions of NPN1 and NPN2 or other NPN subscriptions in the UE.
  • the UE can use the NPN subscription of NPN1 to access services of NPN1.
  • Figure 1E is a schematic diagram of direct connection of multiple private networks provided by an embodiment of this application.
  • UDM1 of SNPN1, UDM2 of SNPN2 and UDM3 of PIN-NPN3 are connected to each other .
  • the mobility management network element is an AMF network element and the data management network element is a UDM network element as an example for description.
  • the AMF network element is abbreviated as AMF
  • the UDM network element is abbreviated as UDM. That is, the AMF described later in this application can be replaced with a mobility management network element, and the UDM can be replaced with a data management network element.
  • FIG. 2A is a schematic flowchart of a communication method provided by an embodiment of the application. As shown in FIG. 2A, the method includes the following steps:
  • a first proxy UDM network element receives a first request from a first UDM, where the first request carries a UE identity and a network identity, and the network identity includes a requesting network identity and a serving network identity.
  • the embodiment of the application provides a proxy UDM network element, which is mainly used to receive registration submitted by other UDM network elements. Information, and then complete the registration of other private networks according to the registration information, so that UDM network elements of other private networks can connect and communicate with the proxy UDM network element.
  • Figure 2B is a schematic diagram of an indirect connection of multiple private networks provided by an embodiment of the application. As shown in Figure 2B, an agent UDM network element (Agent UDM, abbreviated as A) is added between multiple private networks.
  • Agent UDM Agent UDM, abbreviated as A
  • Figure 2C is another schematic diagram of multiple private network indirect connections provided by an embodiment of this application.
  • A-UDM if A-UDM is deployed in a PLMN, and A-UDM is deployed in a PLMN, -UDM's private network for communication includes PIN-NPN3, and PIN-NPN is a private network that partially relies on PLMN, which can obtain information directly from PLMN without adding additional interfaces, which further reduces the number of interfaces.
  • the registration information submitted by other UDMs to the proxy UDM network element may include: the network identifier of the network to which the UDM network element belongs, which can uniquely identify the private network, for example, it may include PLMN ID (including Mobile Country Code (MCC) and mobile country code).
  • PLMN ID including Mobile Country Code (MCC) and mobile country code.
  • MNC Mobile Network Code
  • NID is an additional identification that needs to be provided for SNPN private networks
  • CAG ID or slice identification is PNI-NPN type
  • the private network requires additional identification; UDM routing information is used to address the UDM in the registered private network, which can be an IP address, Fully Qualified Domain Name (FQDN) or other identification; group identification, used for association A group of NPNs with communication requirements. For example, a parent company and a subsidiary deployed in a private network can belong to the same group. The group ID can also be used to request authorization. Only private networks in the same group can obtain NPN subscriptions from other private networks in the group. information.
  • MNC
  • Figure 2D is a schematic diagram of a UDM registration process provided by an embodiment of the application. As shown in Figure 2D, the UDM registration process includes the following steps:
  • UDM1 sends a registration request to A-UDM, the registration request includes UDM1 registration information, and obtains its own registration result response from A-UDM, where the registration result response is used to determine the success or failure of UDM1 registration;
  • UDM2 sends a registration request to A-UDM, where the registration request includes UDM2 registration information, and obtains its own registration result response from A-UDM.
  • the UDM in the private network wants to realize the communication between different private networks through the proxy UDM, and first needs to find a suitable proxy UDM according to certain rules.
  • configuration information can be added to NPN1-UDM to discover the proxy UDM. If there is only one proxy UDM in the same public network, the configuration information can include: discovery of proxy UDMs in the same public network as NPN1; if there is more than one proxy UDM in the same public network, then the configuration information can include: discovery of the same public network A proxy UDM with the closest distance, the shortest delay, or the least current communication pressure in a public network, etc. Configuration information can be provided to NPN1-UDM in advance through Operation Administration and Maintenance (OAM).
  • OAM Operation Administration and Maintenance
  • the proxy UDM can be dynamically discovered through the Network Function Repository Function (NRF). After the UDM of the private network discovers the proxy UDM, it communicates with the proxy UDM.
  • NRF Network Function Repository Function
  • the interaction between NPN1-UDM and A-UDM can be transmitted through the Security Edge Protection Proxy (SEPP) network element To improve safety.
  • SEPP Security Edge Protection Proxy
  • the registration request includes registration information, such as the network ID of the private network, the routing information corresponding to the private network UDM, and the group ID of the UDM, etc.
  • UDM responds to the registration request based on the registration information.
  • the proxy UDM network element After the proxy UDM network element receives the registration information, it can conduct some audits, such as confirming that its own resources are sufficient, the communication is fault-free, and the identity of the registrant is legal, and the communication is secure. For private networks that have passed the audit, they can report to the corresponding UDM network. The unit responds to a successful registration, and at the same time saves the registration information of the successfully registered private network in the storage space corresponding to the proxy UDM network element; or generates a number corresponding to the private network, stores the number, and feeds the number back to the registered UDM at the same time Network element. For the private network that fails the audit, you can respond to the registration failure to the corresponding UDM network element. The UDM that fails to register can initiate a registration request again, or initiate a registration request to other proxy UDM network elements.
  • the registration information of the successfully registered NPN is stored by the proxy UDM.
  • Some of the registration information such as the network identifier of the NPN or UDM routing information, can uniquely identify the NPN, and the NPN can use this information as an identity identifier to initiate a communication request to the proxy UDM.
  • the proxy UDM may also assign other unique identifiers to the successfully registered NPN, such as registration information, which is used as the identity identifier when the NPN initiates a communication request.
  • the UDM registration process includes the following steps:
  • NPN1-UDM obtains registration information of other associated private networks
  • NPN1-UDM sends a registration request to A-UDM, where the registration request includes registration information of itself and other associated private network UDMs;
  • NPN1-UDM obtains the registration result response of UDM1 and other associated private networks from A-UDM to determine the success or failure of registration of itself and other associated private networks;
  • NPN1-UDM sends its corresponding registration result response to other UDM network elements associated with the private network.
  • NPN1 can be a private network with management authority, such as the parent company's private network, which itself records the private network registration information of other subsidiaries; or NPN1 is an ordinary member private network and needs to obtain their respective registration information from other member private networks. After NPN1 obtains the registration information of the associated private network, it submits the registration information to A-UDM to initiate a registration request, as shown in Table 1:
  • Table 1 is the private network registration information table associated with the same group. These registration information can contain the same group ID, namely group ID 1. Then the network IDs of multiple private networks and multiple UDM routing information form a table, which is submitted to A- UDM's associated private network registration information form.
  • NPN1-UDM After NPN1-UDM submits the registration information (form) to A-UDM, A-UDM can review these private networks in turn, and then respond to the registration results of each private network in turn; it can also simultaneously respond to all private networks in the list. The network audits, and finally generates a response to the registration result of the private network in the entire list. After NPN1-UDM receives the registration result response, it can directly forward it to all associated private networks, so that the associated private network can obtain its own registration result response from the registration result response according to its own network ID or UDM routing information; or, it can also be sent by NPN1- UDM forwards its corresponding registration result response to the associated private network.
  • the proxy UDM network element also needs to store the registration information after completing the registration of the associated private network. It can directly store the registration information according to the registration information form submitted by the associated private network, or, in some cases, even if it is not in accordance with the registration information
  • the form is registered and submitted at the same time, and it can also be grouped and stored according to the unity of the group ID or the network ID of the subsidiary company under the same parent company and the UDM routing information.
  • the private network UDM can communicate with the proxy UDM, and communicate with other private network UDMs through the proxy UDM.
  • the UE After the UE completes the authentication using the device certificate, it accesses the private network NPN1, and the NPN1 detects the UE's subscription information.
  • the UE's subscription information includes the basic/default subscription and the NPN subscription with NPN1.
  • the UE's subscription information can be detected through NPN1-UDM.
  • NPN1-UDM Next, it can be detected based on the UE ID to detect whether there is an NPN contract between the UE and NPN1 locally (including UDM and/or UDR), and if it exists, it is directly obtained
  • the NPN is subscribed and updated to the UE; if it does not exist, an NPN subscription request is sent to the agent A-UDM.
  • the request includes: UE identification, network identification, and possible group identification information.
  • the subscription information of the UE can also be detected through NPN1-AMF, and it can also be detected in the local UDM and/or UDR.
  • NPN1-AMF detects that the UE does not contain an NPN subscription, it sends a request to NPN1-UDM to obtain NPN subscriptions from other proxy UDMs through NPN1-UDM.
  • the request sent by NPN1-AMF to NPN1-UDM contains: UE ID ( User permanent identifier (Subscription Permanent Identifier, SUPI) or International Mobile Station Equipment (IMEI) and other identifiers) and NPN1 network identifier (PLMN ID and NID (or CAG ID)).
  • SUPI User permanent identifier
  • IMEI International Mobile Station Equipment
  • PLMN ID and NID or CAG ID
  • the NPN1-AMF may also send the first request to the proxy UDM to obtain the NPN subscription.
  • the UE contains only the basic subscription or default subscription of NPN1, which can temporarily access NPN1, but cannot access the service of NPN1, then when NPN1 detects the subscription information of the UE, it will find that it is missing NPN subscription information, try to notify NPN1-UDM to obtain the NPN subscription between the UE and NPN1.
  • NPN1 acts as the first UDM, discovers the first proxy UDM (A1-UDM, here can be A-UDM in Figure 2B or A-UDM in Figure 2C), and sends the first request to A1-UDM.
  • A1-UDM here can be A-UDM in Figure 2B or A-UDM in Figure 2C
  • a request carries the UE identity and network identity, where the network identity includes the requesting network (Requesting-NPN) identity and the serving network (Serving-NPN) identity.
  • Requesting-NPN indicates the network to which the UE obtains the NPN contract, so Requesting-NPN can Including the home network (Home-NPN) or other third-party networks (such as other networks that contain the same group identity as Serving-NPN), where Home-NPN means a network that stores all UE network access, subscription authorization and other related information, Serving -NPN indicates that the UE currently accesses or wants to obtain its NPN subscription network.
  • the A-UDM may determine from which network (requesting network) to obtain the NPN contract between the UE and which private network (serving network) according to the network identifier in the first request.
  • the registration information of the private network is stored in the A-UDM.
  • the UDM routing information can be further determined according to the registration information, and then the corresponding UDM can be addressed.
  • the Requesting-NPN included in the first request can be given explicitly or implicitly based on the UE identity.
  • the Serving-NPN can be based on the UE identity (IMEI, SUPI, Permanent Equipment Identity (Permanent Equipment Identity) Identifier (PEI) or International Mobile Subscriber Identity (IMSI)) determines the Requesting-NPN identifier.
  • FIG. 2F is another schematic diagram of multiple private network indirect connections provided by an embodiment of the application.
  • UDM1 of SNPN1 can be in the second proxy UDM network element (A2-UDM) of PLMN1 Register
  • UDM2 of SNPN2 and UDM3 of PIN-NPN3 can be registered in the first agent UDM (A1-UDM)
  • A1-UDM and A2-UDM can communicate with each other, which enables private networks under different public networks to be able to Communicate with each other.
  • the first request obtained by the first proxy UDM network element may be forwarded by the second proxy UDM, and the second proxy UDM obtains the first request from the first UDM.
  • A2-UDM obtains the first request from UDM1 (first UDM), and then A2-UDM forwards the first request to A1-UDM. Therefore, the method described in this embodiment may further add a step: the second proxy UDM obtains the first request from the first UDM and sends it to the first proxy UDM.
  • the first proxy UDM network element sends a second request to the second UDM according to the requesting network identifier, where the second request carries the UE identifier and the serving network identifier.
  • the first proxy UDM After receiving the first UDM first request, the first proxy UDM needs to verify the UE identity and the requesting network identity in the first request. For example, verifying whether the requesting network identification and the service network identification in the first request are networks in the same group, or verifying whether the storage space of the first proxy UDM contains the requested network registration information of the service network identification, etc. If the first request does not include the requesting network identifier, the first proxy UDM addresses the UE's home network as its corresponding requesting network by default.
  • the first proxy UDM sends a second request to the second UDM. Because the requesting network identification carried in the first request is to help determine the acquisition address of the NPN contract, the first proxy UDM can address the requesting network NPN2 of the UE according to the requesting network identification in the first request, and then to The second UDM, when the first proxy UDM has determined the second UDM, the second request sent to the second UDM may no longer include the requesting network identifier, but may include the serving network identifier.
  • the first UDM first request may not include the requesting network identity, but only the UE identity and the serving network identity, and then the first proxy UDM will use the registration information of each network stored by itself and the UE identity sent in the first request.
  • the UE's home network is determined (the home network is used as the UE's default request network), and then the second UDM is addressed according to the UE's home network, and the second request is sent to the second UDM.
  • the first request does not include the UE’s requesting network identity
  • the first proxy UDM does not match (to) the home network for the UE
  • the first proxy UDM network element sends to all other network elements within the communication range.
  • the second request includes the UE identity, and all or part of the UDM private network determines whether it is the UE’s home network according to the received UE identity, and if so, the second request is sent to it.
  • Request a response, otherwise do not respond, or respond to prompt information to prompt that it is not the UE's home network.
  • the service network identifier may be a private network identifier that the UE currently accesses and needs to obtain an NPN subscription.
  • the service network identifier may also include other network identifiers.
  • the other service network identifier may be a network identifier that includes the same group identifier as the private network that the UE currently accesses, indicating that the NPN contracts of the UE and the private network of the group are obtained in batches.
  • the proxy UDM may also be the home network of the UE.
  • NPN2 is the parent company network of the group, and its UDM is used as the proxy UDM. Then, after the UE sends the first request to the first proxy UDM through the first UDM, the first proxy UDM directly feeds back the NPN subscription to the first UDM.
  • the second request sent by the first proxy UDM to the second UDM may include a set of multiple UE identities sent by the first request and the requested network identity, for example, multiple requests corresponding to the same UE identity The set generated by the network ID, or the set generated by the requested network ID with the same group ID and multiple different UE IDs, etc.
  • the second UDM sends an NPN subscription to the first proxy UDM according to the second request.
  • the first proxy UDM can address the second UDM according to the requested network identifier in the first request, and then the second UDM directly queries locally whether it contains the NPN contract corresponding to the service network identifier according to the received second request. That's it.
  • the probability that the second UDM can directly obtain the NPN subscription is relatively high. If the network corresponding to the UDM is a third-party network, the UDM may not be able to obtain the NPN contract from the second UDM, and the second UDM may also further assist the first UDM to obtain the NPN contract from other networks.
  • the first proxy UDM sends the NPN subscription to the first UDM.
  • the first proxy UMD can forward it to the first UDM after receiving the NPN subscription sent by the second UDM.
  • the first proxy UDM can send the NPN subscription corresponding to the set to the first UDM.
  • the first UDM can serve according to the service.
  • the network identifier matches its own NPN subscription.
  • the first UDM can store the NPN subscriptions of other associated networks (networks with the same group of identifiers) for backup. This can improve the efficiency of issuing NPN contracts and reduce the time consumption for subsequent acquisition of NPN contracts.
  • all NPN contracts are issued to the UDM corresponding to the private network, which can ensure the privacy and security of NPN contracts.
  • the NPN subscription corresponding to the set can be stored in the first proxy UDM, so that when another UDM initiates an NPN subscription request, the first proxy UDM directly sends the NPN subscription according to the matching result of the requested network ID and the UE ID. It needs to be obtained from the second UDM again. It improves the efficiency of obtaining NPN contracts and reduces the storage overhead of requesting private networks.
  • the NPN subscription sent to the first UDM can also be sent to other NPNs in the same group simultaneously.
  • the NPN subscription can be directly sent by the first proxy UDM to the first UDM, otherwise, The first proxy UDM sends the NPN subscription to the second proxy UDM, and then the second proxy UDM sends it to the first UDM.
  • the first proxy UDM sends the NPN subscription to the second proxy UDM, and then the second proxy UDM sends it to the first UDM.
  • the UDM by adding a proxy UDM, multiple private networks in the same public network can communicate with each other through the proxy UDM, so that the UDM requesting the private network can communicate from other private networks through the proxy UDM.
  • the NPN contract is obtained in the UDM of the network, enabling the UE to perform normal network access through the NPN contract, reducing the number of interfaces for mutual communication between private networks, reducing network overhead and the complexity of managing multiple interfaces, and improving communication efficiency .
  • the success rate of UE access to the private network is improved.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of the application. As shown in FIG. 3, the method includes the following steps:
  • a first proxy UDM network element receives an NPN contract sent by a second UDM, where the NPN contract includes identification information.
  • a proxy UDM is set in the public network, so that other private networks in the same public network can register in the proxy UDM, so that the registered private networks can communicate with each other.
  • the NPN contracts corresponding to the subsidiaries of the parent company can be stored or recorded in NPN2.
  • NPN2 can be used in certain situations, such as within a set period, including 1 day, 3 days, one month, etc., or when the storage capacity reaches the preset maximum value, or the remaining storage space reaches the preset minimum value, or to satisfy the business
  • the NPN contract corresponding to the subsidiary is automatically pushed to the subsidiary network.
  • These NPN contracts include service identification information, service authorization, and UE identification, which are used to authorize the UE to use NPN related services.
  • the NPN contract also includes some other identification information, which is used to uniquely identify the identity of the private network to determine the subject corresponding to the NPN contract.
  • the identification information in the NPN subscription may include the network identification of the NPN.
  • the default network identifier is its own network identifier, and this identification information is omitted from the NPN contract. If NPN2 obtains other NPN contracts, the network identifier can be used as the identification information. In addition, the identification information may also include the group identification of the NPN, which is used to identify the association relationship between the NPNs.
  • the first proxy UDM sends the NPN subscription to one or more UDMs according to the identification information.
  • the identification information is used to determine the identity or association relationship of the NPN corresponding to the NPN subscription. Therefore, the recipient of the NPN contract can be determined according to the identification information.
  • the first proxy UDM can determine which NPN receives the NPN contract according to the network identification in the NPN contract. For example, if the NPN contract includes the network identification of NPN1, the NPN contract is received by NPN1.
  • the first proxy UDM can determine all a series of NPNs that have an association relationship with the NPN contracted by the NPN according to the group identification, and the first proxy UDM can send the NPN subscription to all UDMs corresponding to the group identification, A series of NPNs that receive the NPN contract then determine whether the NPN contract is applicable to the NPN contract based on information such as its own network identification.
  • the first proxy UDM needs to be registered in the first proxy UDM before communicating.
  • the submitted registration information includes network identification, UDM subscription, and group identification. Then, when the first proxy UDM receives the NPN subscription, it can match the routing information of the UDM according to the identification information in the NPN subscription, so as to correctly address the UDM.
  • the NPN contract automatically pushed by UDM is received through the proxy UDM network element, and then the NPN contract is matched with the recipient (one or more UDMs) of the NPN contract according to the identification information in the NPN contract, and finally to the recipient Sending the NPN contract allows the NPN contract to be automatically pushed to the corresponding NPN, which improves the efficiency of obtaining the NPN contract.
  • the NPN contract in the NPN can be automatically updated, which improves the real-time performance of the NPN contract.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the terminal, the control plane network element, the storage function network element, or other network equipment into functional modules according to the foregoing method examples.
  • each functional module can be divided corresponding to each function, or two or two
  • the above functions are integrated in one processing module, and the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the communication device 400 shown in FIG. 4 can be used as the proxy UDM network element involved in the foregoing method embodiment, and perform the steps performed by the proxy UDM network element in the foregoing method embodiment.
  • the communication device 400 may include a receiving module 401, a sending module 402, and a processing module 403.
  • the receiving module 401, the sending module 402 and the processing module 403 are coupled with each other.
  • the receiving module 401 and the sending module 402 can be used to support the communication device 400 to communicate, such as performing steps 201 to 204, step 212, step 214, step 222, and step 222 in FIG. 2A, FIG. 2D, FIG. 2E, and FIG. 3 respectively.
  • the processing module 403 can be used to support the communication device 400 to perform the processing actions in the foregoing method embodiments, such as performing steps 201 to 204, step 212, step 214, and step 201 in FIG. 2A, FIG. 2D, and FIG. 2E, and FIG. 222, step 223, step 301, or step 302 and other processing actions performed by the first proxy UDM network element or the second proxy UDM network element.
  • the receiving module 401 can be used to receive a first request from the first UDM.
  • the first request carries the UE identity and the network identity, and the network identity includes the requesting network. Identification and service network identification;
  • the sending module 402 is configured to send a second request to the second UDM according to the network identifier, and the second request carries the UE identifier and the serving network identifier;
  • the receiving module 401 is further configured to receive an NPN contract sent by the second UDM, where the NPN contract includes service identification information and service authorization;
  • the sending module 402 is further configured to send the NPN subscription to the first UDM.
  • the receiving module 401 is specifically configured to:
  • the sending module is specifically used for:
  • processing module 403 is used to:
  • the registration of one or more UDMs is completed according to the registration information submitted by one UDM, so that the first proxy UDM network element can communicate with the one or more UDMs.
  • the receiving module 401 is configured to receive the NPN contract sent by the second UDM, the NPN contract includes identification information, and the identification information is used to uniquely identify the NPN;
  • the sending module 402 is configured to send the NPN subscription to one or more UDMs according to the identification information.
  • the identification information includes a network identification
  • the sending module 402 is specifically configured to:
  • the identification information includes a group identification
  • the sending module 402 is specifically configured to:
  • the processing module 403 is configured to complete the registration of one or more UDMs according to the registration information submitted by one UDM, and the registration information includes network identification and UDM routing information;
  • the sending module 402 is used to:
  • the communication device 400 involved in the embodiment of the present application may be the communication device 500 shown in FIG. 5.
  • FIG. 5 shows a schematic diagram of the hardware structure of a communication device in an embodiment of the present application.
  • the structure of the UDM network element can refer to the structure shown in FIG. 5.
  • the communication device 500 includes: a processor 111 and a communication transceiver 112, and the processor 111 and the transceiver 112 are electrically coupled;
  • the processor 111 is configured to execute part or all of the computer program instructions in the memory, and when the part or all of the computer program instructions are executed, the device executes the method described in any of the foregoing embodiments.
  • the transceiver 112 is configured to communicate with other devices; for example, receiving a first request from a first UDM, the first request carrying a UE identity and a network identity, and the network identity includes a requesting network identity and a serving network identity.
  • the memory 113 for storing computer program instructions.
  • the memory 113 (Memory#1) is located in the device, and the memory 113 (Memory#2) is integrated with the processor 111. Together, or the memory 113 (Memory#3) is located outside the device.
  • the communication device 500 shown in FIG. 5 may be a chip or a circuit.
  • a chip or circuit may be provided in a terminal device or a communication device.
  • the aforementioned transceiver 112 may also be a communication interface.
  • the transceiver includes a receiver and a transmitter.
  • the communication device 500 may also include a bus system.
  • the processor 111, the memory 113, and the transceiver 112 are connected by a bus system.
  • the processor 111 is used to execute instructions stored in the memory 113 to control the transceiver to receive and send signals, and complete the first implementation method involved in this application The steps of the device or the second device.
  • the memory 113 may be integrated in the processor 111, or may be provided separately from the processor 111.
  • the function of the transceiver 112 may be implemented by a transceiver circuit or a dedicated transceiver chip.
  • the processor 111 may be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.
  • the processor may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip or other general-purpose processors.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (generic array logic, GAL) and other programmable logic devices , Discrete gates or transistor logic devices, discrete hardware components, etc. or any combination thereof.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the embodiment of the present application provides a computer storage medium storing a computer program, and the computer program includes a method for executing the foregoing method.
  • the embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the method provided above.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种通信方法，其中方法包括：第一代理UDM网元接收来自第一UDM第一请求，第一请求中携带UE标识和网络标识；根据网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；接收第二UDM发送的NPN签约，NPN签约中包括业务标识信息和/或业务授权；向第一UDM发送NPN签约。本申请实施例有效优化了签约配置过程，减少了网络开销，提升了配置效率。

Description

签约信息获取方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种签约信息获取方法及装置。
背景技术
目前5G定义了两种私网(Non-Public Network,NPN)类型：独立组网的NPN网络(Standalone NPN,SNPN)和非独立组网的NPN网络(Public network integrated NPN,PNI-NPN)。其中SNPN表示不依赖公共陆地移动网络(Public Land Mobile Network,PLMN，简称公网)提供网络功能的网络，可以具有独立接入网(RAN)和核心网(5GC)；PNI-NPN表示可以部分依赖公网PLMN提供网络功能的网络。
另外PNI-NPN目前也可以进一步细分为两种：(1)闭合接入组(Closed Access Group，CAG)，该种类型的私网是公网PLMN网络的一部分，只是针对特定业务/用户提供服务；(2)切片(Slicing)，这种类型的私网同样属于PNI-NPN网络的一种，利用5G定义的切片特性使用专门的切片为特定业务/用户提供服务。
目前5G定义了两种动态更新配置信息的方式：一种是由接入与移动性管理功能(Access and Mobility Management Function,AMF)网元触发，主要用于更新UE设备上的签约信息；另一种是由策略控制功能(Policy Control Function,PCF)网元触发，主要用于更新UE设备上的策略信息。5G中可以使用配置更新流程更新UE的相关配置(包含签约信息)，但是前提条件是统一数据管理(Unified Data Management,UDM)或者统一数据库(Unified Data Repository,UDR)网元中存在相应的签约信息，同时仅能更新接入该网络的终端设备。
如何远程配置UE签约是正在讨论的私网课题之一，在当前远程配置UE签约的时候，通常为点对点分布式获取方式，这样会导致通讯接口繁多，开销大，以及管理复杂等问题。
发明内容
本申请实施例提供了一种通信方法及装置，以简化配置终端设备的签约。
第一方面，提供了一种通信方法，包括：
第一代理UDM网元接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识；
根据所述网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；
接收第二UDM发送的NPN签约，所述NPN签约中包括业务标识信息和/或业务授权；
向所述第一UDM发送所述NPN签约。
在一个可选示例中，所述接收来自第一UDM第一请求包括：
接收第二代理UDM网元发送的第一请求，所述第一请求由所述第二代理UDM网元转发来自第一UDM第一请求；
向第一UDM发送所述NPN签约包括：
通过第二代理UDM网元向第一UDM发送所述NPN签约。
在一个可选示例中，所述方法还包括：根据一个UDM提交的注册信息完成一个或多个UDM的注册，以使得所述第一代理UDM网元能够与所述一个或多个UDM通信。
在一个可选示例中，在所述根据一个UDM提交的注册信息完成多个UDM的注册时，所述一个UDM提交的注册信息包括所述多个UDM的注册信息。
在一个可选示例中，所述多个UDM与所述一个UDM的NPN包括相同的组标识。
在一个可选示例中，所述第一请求中还包括所述网络标识对应的第一组标识，所述第二UDM的网络标识也对应所述第一组标识。
第二方面，提供了一种通信方法，包括：
第一代理UDM网元接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息，所述标识信息用于唯一标识NPN；
根据所述标识信息向一个或多个UDM发送所述NPN签约。
在一个可选示例中，所述标识信息包括网络标识，所述根据所述标识信息向一个或多个UDM发送所述NPN签约，包括：
根据所述网络标识向对应私网的UDM发送所述NPN签约。
在一个可选示例中，所述标识信息还包括所述网络标识的组标识，所述根据所述标识信息向一个或多个UDM发送所述NPN签约，包括：
获取与所述第二UDM的NPN具有相同组标识的一个或多个NPN；
向所述一个或多个NPN对应的UDM发送所述NPN签约。
在一个可选示例中，第一代理UDM网元接收第二UDM发送的NPN签约之前，所述方法还包括：
所述第一代理UDM网元根据一个UDM提交的注册信息完成一个或多个UDM的注册，所述注册信息中包括网络标识和UDM路由信息；
所述根据所述标识信息向一个或多个UDM发送所述NPN签约包括：
根据所述注册信息获取与所述标识信息对应的UDM路由信息；
根据所述UDM路由信息向一个或多个UDM发送所述NPN签约。
第三方面，提供一种UDM网元，包括处理模块、接收模块和发送模块，其中：
所述接收模块，用于接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识；
所述发送模块，用于根据所述网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；
所述接收模块，还用于接收第二UDM发送的NPN签约，所述NPN签约中包括业务标识信息和业务授权；
所述发送模块，还用于向所述第一UDM发送所述NPN签约。
在一个可选示例中，所述接收模块具体用于：
接收第二代理UDM网元发送的第一请求，所述第一请求由所述第二代理UDM网元转发来自第一UDM第一请求；
所述发送模块具体用于：
通过第二代理UDM网元向第一UDM发送所述NPN签约。
在一个可选示例中，所述网元包括处理模块，用于：
根据一个UDM提交的注册信息完成一个或多个UDM的注册，以使得所述第一代理UDM网元能够与所述一个或多个UDM通信。
在一个可选示例中，在所述根据一个UDM提交的注册信息完成多个UDM的注册时，所述一个UDM提交的注册信息包括所述多个UDM的注册信息。
在一个可选示例中，所述多个UDM与所述一个UDM的NPN包括相同的组标识。
在一个可选示例中，所述第一请求中还包括所述网络标识对应的第一组标识，所述第二UDM的网络标识也对应所述第一组标识。
第四方面，提供一种UDM网元，包括接收模块和发送模块，其中：
所述接收模块，用于接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息，所述标识信息用于唯一标识NPN；
所述发送模块，用于根据所述标识信息向一个或多个UDM发送所述NPN签约。
在一个可选示例中，所述标识信息包括网络标识，所述发送模块具体用于：
根据所述网络标识向对应私网的UDM发送所述NPN签约。
在一个可选示例中，所述标识信息还包括所述网络标识的组标识，所述发送模块具体用于：
获取与所述第二UDM的NPN具有相同组标识的一个或多个NPN；
向所述一个或多个NPN对应的UDM发送所述NPN签约。
在一个可选示例中，所述UDM网元还包括处理模块，用于：根据一个UDM提交的注册信息完成一个或多个UDM的注册，所述注册信息中包括网络标识和UDM路由信息；
所述发送模块用于：
根据所述注册信息获取与所述标识信息对应的UDM路由信息；
根据所述UDM路由信息向一个或多个UDM发送所述NPN签约。
第五方面，本申请实施例提供一种通信装置，该装置具有实现上述第一方面或第一方面的任一种可能的实现方式中终端的功能、或具有实现上述第二方面或第二方面的任一种可能的实现方式中控制面网元的功能。
该装置可以为终端，也可以为终端中包括的芯片。上述通信装备的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，所述硬件或软件包括一个或多个与上述功能相对应的模块。
该装置可以为网络设备，也可以为网络设备中包含的芯片。上述通信装备的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该装置的结构中包括处理模块和收发模块，其中，处理模块被配置为支持该装置执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法。
在另一种可能的设计中，该装置的结构中包括处理器，还可以包括存储器。处理器与存储器耦合，可用于执行存储器中存储的计算机程序指令，以使装置执行上述第一方面、或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一 种可能的实现方式中的方法。可选地，该装置还包括通信接口，处理器与通信接口耦合。当装置为网络设备时，该通信接口可以是收发器或输入/输出接口；当该装置为网络设备中包含的芯片时，该通信接口可以是芯片的输入/输出接口。可选地，收发器可以为收发电路，输入/输出接口可以是输入/输出电路。
第六方面，本申请实施例提供一种芯片系统，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法。
可选地，该芯片系统还包括接口电路，该接口电路用于交互代码指令至所述处理器。
可选地，该芯片系统中的处理器可以为一个或多个，该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
第七方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序或指令，当该计算机程序或指令被执行时，使得计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法。
第八方面，本申请实施例提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法。
第九方面，本申请实施例提供一种通信系统，该通信系统包括上述的一个或多个存储网元，可选的，该通信系统中还可包括控制面设备，其他网络设备和/或终端。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍。
图1A为本申请实施例提供的一种系统框架示意图；
图1B为本申请实施例提供的另一种系统框架示意图；
图1C为本申请实施例提供的另一种系统框架示意图；
图1D为本申请实施例提供的一种NPN签约获取场景示意图；
图1E为本申请实施例提供的一种多个私网直接连接示意图；
图2A为本申请实施例提供的一种通信方法流程示意图；
图2B为本申请实施例提供的一种多个私网间接连接示意图；
图2C为本申请实施例提供的另一种多个私网间接连接示意图；
图2D为本申请实施例提供的一种UDM注册流程示意图；
图2E为本申请实施例提供的另一种UDM注册流程示意图；
图2F为本申请实施例提供的另一种多个私网间接连接示意图；
图3为本申请实施例提供的另一种通信方法流程示意图；
图4为本申请实施例提供的一种通信装置示意框图；
图5为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
首先对本申请实施例涉及的网元进行介绍。
终端设备：可以为用户设备(user equipment，UE)、手持终端、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。终端设备与接入网设备之间采用某种空口技术相互通信。
接入网(Radio Access Network，RAN)设备：主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。所述接入网设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在第五代(5th generation，5G)系统中，称为gNB；在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
移动性管理网元：属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。移动性管理网元为终端设备中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以及存储会话标识、与会话标识关联的SMF网元标识等。在5G中，移动性管理网元可以是核心网接入和移动性管理功能(core access and mobility management function，AMF)网元，在未来通信如第6代(6th generation，6G)通信中，移动性管理网元仍可以是AMF网元，或者有其它名称，本申请对此不作限定。
非3GPP接入网设备：该网元允许终端设备和3GPP核心网之间采用非3GPP技术互连互通，其中非3GPP技术例如：无线保真(WirelessFidelity，Wi-Fi)、全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)、码分多址(Code Division Multiple Access，CDMA)网络等，相对于可信的非3GPP接入网设备可以直接接入3GPP核心网，该网元需要通过安全网关建立的安全隧道来与3GPP核心网互连互通，其中安全网关例如：演进型分组数据网关(Evolved Packet Data Gateway，ePDG)或者非3GPP互通功能(Non-3GPP InterWorking Function,N3IWF)网元。在5G中，非3GPP接入网设备可 以是不可信的非3GPP接入网(Untrusted non-3GPP Access Network)设备，在未来通信如6G中，非3GPP接入网设备仍可以是不可信的非3GPP接入网设备，或有其它的名称，本申请不做限定。
会话管理网元：主要用于移动网络中的会话管理，负责用户面网元选择，用户面网元重定向，因特网协议(internet protocol，IP)地址分配，承载的建立、修改和释放以及QoS控制。在5G中，会话管理网元可以是会话管理功能(session management function，SMF)网元，在未来通信如6G中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请不做限定。
用户面网元：负责终端设备中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端设备；用户面网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。用户面网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。在5G中，用户面网元可以是用户面功能(user plane function，UPF)网元，在未来通信如6G中，用户面网元仍可以是UPF网元，或有其它的名称，本申请不做限定。
策略控制网元：主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略相关的用户签约信息。在4G通信系统中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元可以是策略控制功能(policy control function，PCF)网元。在未来通信系统如6G中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
认证服务器：主要提供认证功能，支持3GPP接入和Non-3GPP接入的认证。在5G通信系统中，该认证服务器可以是认证服务器功能(authentication server function，AUSF)网元。在未来通信系统如6G中，认证服务器仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
能力开放网元：主要支持3GPP网络和第三方应用安全的交互，NEF能够安全的向第三方暴露网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方获取相关数据，用以增强网络的智能决策；同时该网元支持从统一数据库恢复结构化数据或者向统一数据库中存储结构化数据。在5G通信系统中，该能力开放网元可以是网络能力开放功能实体(Network Exposure Function，NEF)网元。在未来通信系统如6G中，能力开放网元网元仍可以是NEF网元，或者，还可以有其它的名称，本申请不做限定。
数据存储网元：主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。在5G通信系统中，该数据存储网元可以是统一数据库功能(unified data repository，UDR)网元。在未来通信系统如6G中，数据存储网元仍可以是UDR网元，或者，还可以有其它的名称，本申请不做限定。
数据管理网元：基于存储于UDR中的用户签约数据(包含鉴权数据)，为用户提供接入授权、注册、业务连续性、短消息等业务。在5G通信系统中，该数据管理网元可以是统一数据管理(Unified Data Management,UDM)网元。在未来通信系统如6G中，数据管理网元仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
应用网元：主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元。在未来通信系统如6G中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者设备既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。上述网元或者设备可划分出一个或多个服务，进一步，还可能会出现独立于网络功能存在的服务。在本申请中，上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
请参阅图1A，图1A为本申请实施例提供的一种系统框架示意图，目前5G的3GPP系统架构如图1A所示，包含的网络功能和实体主要有：UE、(R)AN、UPF、数据网络(Data Network,DN)、AMF、SMF、PCF、AF、网络切片选择功能(Network Slice Selection Function,NSSF)、AUSF和UDM。图中展示了网络功能实体之间的交互关系以及对应的接口，例如，UE和AMF之间可以通过N1接口进行交互，其他网络功能实体之间的交互类似，不再赘述。
另外，请参阅图1B，图1B为本申请实施例提供的另一种系统框架示意图，如图1B所示，3GPP系统架构中部分接口可以采用服务化接口的方式实现，网络数据分析功能(Network Data Analytics Function,NWDAF)网元和其他网络功能网元可以通过服务化接口Nnwdaf进行交互。例如网络切片选择功能(Network Slice Selection Function,NSSF)网元通过服务化接口Nnssf进行交互。
图1A和图1B中的UE、(R)AN、UPF和DN通常被称为用户层网络功能实体，用户的数据流量可以通过UE和DN之间建立的PDU Session进行传输，传输会经过(R)AN和UPF这两个网络功能(实体)；而其他的部分则被称为控制层网络功能和实体，主要负责认证和鉴权、注册管理、会话管理、移动性管理以及策略控制等功能，从而实现用户层流量可靠稳定的传输。
另外请参阅图1C，图1C为本申请实施例提供的另一种系统框架示意图，如图1C所示，是5G中的non-3GPP系统架构，相对于3GPP的系统架构，新增非3GPP互连功能(Non-3GPP InterWorking Function，N3IWF)网元，它允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
基于上述系统框架，UE通过签约信息获得与某个NPN中的网络功能和实体进行通信的权限，其中签约信息可以包括：基本签约或缺省签约(UE标识或证书)，用于授权终端临时接入NPN，其中临时接入表示限制权限和/或限制时间的接入；NPN签约，包括业务标识信息(例如闭合接入组标识(Closed Access Group Identity document,CAG ID)，网络标识符(Network Identifier,NID)，数据网络名(Data Network Name,DNN)等信息)和业务授权，用于授权正常接入NPN并使用NPN相关业务。
在一些示例中，集团在不同的地域部署了不同的私网，例如集团可以是中国移动(China  Mobile Communications Group Co.,Ltd，CMCC)，中国联通(China Unicom)或美国电话电报公司(American Telephone&Telegraph，AT&T)等，私网可以是集团、学校、企业或政府部署的专属网络，UE可以使用基本或缺省签约临时接入集团内不同的私网，但是能否正常使用私网业务需要UE包含NPN签约。请参阅图1D，图1D为本申请实施例提供的一种NPN签约获取场景示意图，如图1D所示，UE已经配置了集团的基本签约或通用证书，同时配置了NPN2的NPN签约，UE可以正常接入NPN2并正常使用NPN2的业务；在一些情况下，UE移动到同一集团下的不同私网NPN1，此时UE仅能使用该集团的基本签约或通用证书临时接入NPN1；当NPN1发现UE不包含当前私网的NPN签约时，主动尝试获取该NPN签约，具体获取的地方可以是从私网NPN2中获取(假设NPN2为母公司网络)，或者NPN1也可以从任意含有该NPN签约的第三方获取；当然私网NPN2也可以主动向私网NPN1推送UE的NPN签约，推送的签约可以是私网NPN1的NPN签约，也可以其他NPN签约。最后UE中存在基本签约/通用证书、以及NPN1和NPN2的NPN签约或者其他NPN签约，此时UE可以使用NPN1的NPN签约访问NPN1的业务。
在这个过程中，如果有多个不同私网的UE试图获取NPN签约，那么被获取权限的私网需要与所有发起请求的私网两两之间获得通讯接口，同时还需要对接入的所有私网进行管理，请参阅图1E，图1E为本申请实施例提供的一种多个私网直接连接示意图，如图1E所示，SNPN1的UDM1，SNPN2的UDM2以及PIN-NPN3的UDM3互相连接，表示两两之间可以进行通信，其中包括3*2＝6个接口，如果新增一个私网SNPN4，其对应的UDM4要与其他所有私网建立连接那么对应的接口个数为：3*4＝12，即建立两两通信的接口个数＝N*(N-1),其中N为私网个数。这将导致通讯接口数量随着私网个数增加显著增多，连接开销大，同时造成管理复杂等问题。
为方便说明，本申请后续，以移动性管理网元为AMF网元，数据管理网元为UDM网元为例进行说明。进一步地，将AMF网元简称为AMF，UDM网元简称为UDM。即本申请后续所描述的AMF均可替换为移动性管理网元，UDM均可替换为数据管理网元。
为了解决上述问题，请参阅图2A，图2A为本申请实施例提供的一种通信方法流程示意图，如图2A所示，该方法包括如下步骤：
201、第一代理UDM网元接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识。
为了解决上述内容描述的通过各个私网之间单独建立接口进行通信所存在的问题，本申请实施例提供了一种代理UDM网元，代理UDM网元主要用于接收其他UDM网元提交的注册信息，然后根据注册信息完成其他私网的注册，使得其他私网的UDM网元能够与代理UDM网元进行连接和通信。请参阅图2B，图2B为本申请实施例提供的一种多个私网间接连接示意图，如图2B所示，在多个私网之间新增一个代理UDM网元(Agent UDM，简称A-UDM)，当SNPN1的UDM1，SNPN2的UDM2以及PIN-NPN3的UDM3需要互相连接时，通过A-UDM进行通信，因此只需要建立各个私网与A-UDM之间的接口即可。在增加一个私网SNPN4的情况下，只需要新增SNPN4与A-UDM之间的一个接口，则SNPN4可以通过A-UDM与其他私网的UDM通信，该实施例中的接口个数为N，其中N为需要进行通信的私网个数，远远少于未添加A-UDM时的接口个数N*(N-1)。
甚至，在一些情况下，请参阅图2C，图2C为本申请实施例提供的另一种多个私网间接连接示意图，如图2C所示，如果A-UDM部署在PLMN中，而通过A-UDM进行通信的私网中包括PIN-NPN3，而PIN-NPN为部分依赖PLMN的私网，可以直接从PLMN中获取信息，而不需要再额外添加接口，进一步减少了接口数量。
其他UDM向代理UDM网元提交的注册信息可以包括：UDM网元所属网络的网络标识，能够唯一标识私网的标识，例如可以包含PLMN ID(包含移动国家码(Mobile Country Code,MCC)和移动网络码(Mobile Network Code,MNC))、NID、CAG ID和切片标识信息中的一个或多个；NID是SNPN类型私网需要额外提供的标识，CAG ID或者且切片标识则是PNI-NPN类型私网需要额外提供的标识；UDM路由信息，用于寻址到注册私网中的UDM，可以是IP地址，完全合格域名(Fully Qualified Domain Name,FQDN)或者其他标识；组标识，用来关联一组存在通讯需求的NPN，例如采用私网部署的母公司和子公司可以同属一个组，该组标识同样可以用于请求授权，只有同组内的私网才能获取组内其他私网的NPN签约信息。
具体的注册过程请参阅图2D，图2D为本申请实施例提供的一种UDM注册流程示意图，如图2D所示，UDM注册过程包括如下步骤：
211、NPN1的UDM1发现A-UDM；
212、UDM1向A-UDM发送注册请求，所述注册请求中包括UDM1的注册信息，并从A-UDM获得自身注册结果响应，其中注册结果响应用于确定UDM1注册成功或失败；
213、NPN2的UDM2发现代理UDM；
214、UDM2向A-UDM发送注册请求，所述注册请求中包括UDM2的注册信息，并从A-UDM获得自身注册结果响应。
私网中的UDM想通过代理UDM实现不同私网间的通信，首先需要根据一定的规则发现合适的代理UDM。例如可以在NPN1-UDM中添加配置信息用以发现代理UDM。如果同一个公网中只包含一个代理UDM，那么配置信息可以包括：发现与NPN1同一个公网内的代理UDM；如果同一个公网中的代理UDM不止一个，那么配置信息可以包括：发现同一个公网中距离最近、时延最短或者当前通信压力最小的代理UDM等。配置信息可以通过操作维护管理(Operation Administration and Maintenance，OAM)预先提供给NPN1-UDM。或者也可以通过网络功能库(Network Function Repository Function，NRF)动态发现代理UDM。在私网的UDM发现代理UDM后，与代理UDM进行通信连接，可选的，NPN1-UDM和A-UDM之间的交互可以通过安全边界保护代理(Security Edge Protection Proxy，SEPP)网元进行传输，以提高安全性。
在NPN1-UDM与A-UDM建立连接后，向其发送注册请求，注册请求中包括注册信息，例如私网的网络标识，该私网UDM对应的路由信息，以及该UDM的组标识等，代理UDM基于这些注册信息对注册请求进行响应。
代理UDM网元接收到注册信息后，可以进行一些审核，例如确认自身资源充足、通信无故障，以及确定注册方身份合法、通信安全等，对于通过审核的私网，可以向其对应的UDM网元进行注册成功响应，同时将注册成功的私网的注册信息保存在代理UDM网元对应的存储空间中；或者生成该私网对应的编号并对该编号进行存储，同时将编号反馈到 注册UDM网元。对于未通过审核的私网，可以向其对应的UDM网元进行注册失败响应。注册失败的UDM可以再次发起注册请求，或者向其他代理UDM网元发起注册请求。
注册成功的NPN的注册信息被代理UDM存储，其中一些注册信息，例如NPN的网络标识或UDM路由信息，可以唯一标识NPN，那么NPN可以将这些信息作为身份标识向代理UDM发起通信请求。或者代理UDM也可以为注册成功的NPN分配其他唯一标识，例如注册信息等，用来作为NPN发起通信请求时的身份标识。
或者，在一些情况下，多个私网之间可能存在某种关联关系，例如为归属于同一个母公司下的多个子公司，或者为归属于同一个机构下的多个独立部门，这些具有关联关系的私网被称为关联私网。多个关联私网可以将注册信息统一提交给一个关联私网的UDM网元，并由该UDM网元统一进行关联关系的多个私网的注册，具体过程请参阅图2E，图2E为本申请实施例提供的另一种UDM注册流程示意图，如图2E所示，该UDM注册流程包括如下步骤：
221、NPN1-UDM获取其他关联私网的注册信息；
222、NPN1-UDM向A-UDM发送注册请求，所述注册请求中包括自身以及其他关联私网UDM的注册信息；
223、NPN1-UDM从A-UDM获得UDM1以及其他关联私网的注册结果响应，以确定自身以及其他关联私网注册成功或失败；
224、NPN1-UDM向其他关联私网的UDM网元发送其对应的注册结果响应。
NPN1可以是具有管理权限的私网，例如母公司私网，本身记录了其他子公司的私网注册信息；或者NPN1是普通成员私网，需要从其他成员私网获取其各自对应的注册信息。在NPN1获得关联私网的注册信息后，向A-UDM提交这些注册信息以发起注册请求，如表1所示：
表1 注册信息表
组标识 NPN网络标识 UDM路由信息
组标识1 网络标识1 IP地址1
组标识1 网络标识2 IP地址2
组标识1 网络标识3 IP地址3
组标识1 网络标识4 IP地址4
表1中为同组关联私网注册信息表，这些注册信息可以包含同样的组标识，即组标识1，然后多个私网的网络标识以及多个UDM路由信息形成表格，作为提交给A-UDM的关联私网的注册信息表格。
NPN1-UDM向A-UDM提交了注册信息(表格)后，A-UDM可以依次对这些私网进行审核，然后依次对每个私网的注册结果进行响应；也可以同时对列表中的所有私网进行审核，并最终生成对整个列表中私网的注册结果响应。NPN1-UDM接收到注册结果响应后，可以直接转发给所有关联私网，使得关联私网根据自身网络标识或UDM路由信息从注册结果响应中获取自身的注册结果响应；或者，也可以由NPN1-UDM向关联私网分别转发其 对应的注册结果响应。
同样的，代理UDM网元在完成关联私网的注册后，也需要对注册信息进行存储，可以直接按照关联私网提交的注册信息表格进行存储，或者，在一些情况下，即使不是按照注册信息表格进行的同时注册提交，也可以按照组标识或者同一母公司下的子公司网络标识和UDM路由信息上的统一性进行分组存储。
完成上述注册过程后，私网UDM可以和代理UDM进行通信，以及通过代理UDM与其他私网的UDM通信。例如图2A所示，UE使用设备证书完成认证后，接入私网NPN1，NPN1对UE的签约信息进行检测，UE的签约信息包括基本/缺省签约以及与NPN1的NPN签约。
可选情况下，可以通过NPN1-UDM对UE的签约信息进行检测，首先可以根据UE标识检测NPN1本地(包括UDM和/或UDR中)是否存在UE与NPN1的NPN签约，如果存在，则直接获取该NPN签约并更新到UE；如果不存在，则向代理A-UDM发送NPN签约请求，请求中包含：UE标识和网络标识，以及可能的组标识信息。
可选情况下，也可以通过NPN1-AMF对UE的签约信息进行检测，同样也可以在本地UDM和/或UDR中进行检测。在NPN1-AMF检测到UE不包含NPN签约时，向NPN1-UDM发送请求，以便通过NPN1-UDM从其他代理UDM中获取NPN签约，NPN1-AMF向NPN1-UDM发送的请求中包含：UE标识(用户永久标识(Subscription Permanent Identifier,SUPI)或国际移动设备标识(International Mobile Station Equipment,IMEI)等标识)和NPN1的网络标识(PLMN ID和NID(或CAG ID))。
在一种可选情况下，如果NPN1-AMF向NPN1-UDM发送请求后没有获取到NPN签约，则NPN1-AMF也可以向代理UDM发送第一请求，以便获取NPN签约。
假设如图1D所描述的，UE中仅包含NPN1的基本签约或缺省签约，能够临时接入NPN1，但是不能访问NPN1的业务，那么NPN1对UE的签约信息进行检测时，就会发现其缺少NPN签约信息，尝试通知NPN1-UDM获取UE与NPN1的NPN签约。此时NPN1作为第一UDM，发现第一代理UDM(A1-UDM，在这里可以为图2B中的A-UDM或图2C中的A-UDM)，并向A1-UDM发送第一请求，第一请求中携带UE标识和网络标识，其中网络标识包括请求网络(Requesting-NPN)标识和服务网络(Serving-NPN)标识，Requesting-NPN表示UE向其获取NPN签约的网络，因此Requesting-NPN可以包括归属网络(Home-NPN)或其他第三方网络(例如与Serving-NPN包含同一组标识的其他网络)，其中Home-NPN表示存储有UE所有网络接入，签约授权等相关信息的网络，Serving-NPN表示UE当前接入或想要获取其NPN签约的网络。A-UDM可以根据第一请求中的网络标识确定从哪个网络(请求网络)获取UE与哪个私网(服务网络)之间的NPN签约。另外，A-UDM中存储了私网的注册信息，在获取到请求网络标识的情况下，可以进一步根据注册信息确定UDM路由信息，进而寻址到对应的UDM。
具体地，第一请求中包括的Requesting-NPN可以是显式给定的，也可以是根据UE标识隐式给出的，Serving-NPN可以根据UE标识(IMEI，SUPI，永久设备标识(Permanent Equipment Identifier，PEI)或国际移动用户标识(International Mobile Subscriber Identity，IMSI))确定Requesting-NPN标识。
根据上述描述可知，不同私网在同一个代理UMD网元进行注册后，可以进行彼此之间的通信，但是前提是这些私网属于同一个公网。在一些情况下，如果不同公网(例如不同运营商)下的私网需要进行通信，它们无法在同一个代理UDM中完成注册，因此需要不同公网中的代理UDM进行通信。请参阅图2F，图2F为本申请实施例提供的另一种多个私网间接连接示意图，如图2F所示，SNPN1的UDM1能够在PLMN1的第二代理UDM网元(A2-UDM)中注册，SNPN2的UDM2和PIN-NPN3的UDM3能够在第一代理UDM(A1-UDM)中注册，而A1-UDM和A2-UDM之间能够互相通信，也就使得不同公网下的私网能够互相通信。
在这种情况下，第一代理UDM网元获得的第一请求可以是由第二代理UDM转发的，第二代理UDM从第一UDM中获取到第一请求。如图2F所示，A2-UDM从UDM1(第一UDM)中获取第一请求，然后由A2-UDM将第一请求转发给A1-UDM。因此，本实施例所描述的方法还可以增加步骤：第二代理UDM从第一UDM获取第一请求，并发送给第一代理UDM。
202、第一代理UDM网元根据所述请求网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识。
第一代理UDM接收到第一UDM第一请求后，需要对第一请求中的UE标识和请求网络标识进行验证。例如验证第一请求中的请求网络标识与服务网络标识是否为同一组内的网络，或者验证第一代理UDM的存储空间中是否包含服务网络标识的请求网络注册信息等。如果第一请求中不包括请求网络标识，那么第一代理UDM默认寻址UE的归属网络作为其对应的请求网络。
完成上述验证过程后，第一代理UDM向第二UDM发送第二请求。因为第一请求中携带的请求网络标识是为了有助于确定NPN签约的获取地址，第一代理UDM可以根据第一请求中的请求网络标识，寻址到UE的请求网络NPN2，进而寻址到第二UDM，那么第一代理UDM在已经确定第二UDM的情况下，向第二UDM发送的第二请求中可以不再包括请求网络标识，但可以包括服务网络标识。
或者，第一UDM第一请求中也可以不包括请求网络标识，仅包括UE标识和服务网络标识，然后由第一代理UDM根据自身存储的各个网络的注册信息和第一请求中发送的UE标识确定UE的归属网络(将归属网络作为UE的默认请求网络)，进而根据UE的归属网络寻址第二UDM，向第二UDM发送第二请求。
在一种可能的情况下，第一请求中不包括UE的请求网络标识，且第一代理UDM也没有为UE匹配(到)归属网络，由第一代理UDM网元向通信范围内的其他所有或部分UDM发送第二请求，第二请求中包括UE标识，而其他所有或部分UDM的私网根据接收到的UE标识判断是否是该UE的归属网络，如果是，则对其发送的第二请求进行响应，否则不进行响应，或者响应提示信息以提示自身并非UE的归属网络。
其中，服务网络标识可以是UE当前接入且需要获取NPN签约的私网标识，在一些情况下，服务网络标识还可以包括其他网络标识。例如其他服务网络标识可以是与UE当前接入私网包括同一组标识的网络标识，表示批量获取UE与该组私网的NPN签约。
在一些情况下，代理UDM也可能是UE的归属网络，例如图1D对应的实施例中，NPN2 为集团母公司网络，其UDM作为代理UDM。那么UE通过第一UDM向第一代理UDM发送第一请求后，由第一代理UDM直接向第一UDM反馈NPN签约。
在可选情况下，第一代理UDM向第二UDM发送的第二请求中，可以包括多个第一请求发送的UE标识和请求网络标识的集合，例如根据同一个UE标识对应的多个请求网络标识生成的集合，或者具有相同组标识的请求网络标识与多个不同UE标识生成的集合等。
203、第二UDM根据第二请求向第一代理UDM发送NPN签约。
根据上述描述可知，第一代理UDM可以根据第一请求中的请求网络标识寻址到第二UDM，那么第二UDM根据接收到的第二请求直接从本地查询是否包含服务网络标识对应的NPN签约即可。
如果第二UDM对应的网络为UE的归属网络，那么第二UDM能够直接获取到NPN签约的概率较大。如果UDM对应的网络为第三方网络，那么UDM可能从第二UDM无法获取到NPN签约，第二UDM也可以进一步辅助第一UDM从其他网络中获取NPN签约。
204、第一代理UDM向所述第一UDM发送所述NPN签约。
如果第二请求中只包括一个第一请求中的UE标识和请求网络标识，那么第一代理UMD接收到第二UDM发送的NPN签约后，将其转发给第一UDM即可。
如果第二请求中包括多个第一请求中的UE标识和请求网络标识组成的集合，那么第一代理UDM可以将集合对应的NPN签约发送给第一UDM，一方面可以由第一UDM根据服务网络标识匹配自己的NPN签约，另一方面第一UDM可以存储其他相关联网络(同一组标识的网络)的NPN签约备用。这样可以提升NPN签约的发放效率，减少后续获取NPN签约的时间消耗，同时，将所有NPN签约都发放到私网对应的UDM，可以保证NPN签约的私密性和安全性。
或者也可以将集合对应的NPN签约存储在第一代理UDM中，以便后续有其他UDM发起NPN签约请求时，根据请求网络标识和UE标识的匹配结果直接由第一代理UDM发送NPN签约，而不需要再从第二UDM中获取。提升了获取NPN签约的效率，同时减少了请求私网的存储开销。
如果第一代理UDM或第二UDM能够发现与第一UDM组标识相同的其他同组NPN，那么发送给第一UDM的NPN签约也可以同步发送到其他同组NPN。
第一代理UDM向所述第一UDM发送所述NPN签约的过程中，如果第一UDM能够直接与第一代理UDM通信，那么NPN签约可以直接由第一代理UDM发送给第一UDM，否则，由第一代理UDM将NPN签约发送给第二代理UDM，再由第二代理UDM发送给第一UDM。完成NPN签约获取过程。
可见，在本申请实施例中，通过新增代理UDM，使得同一个公网中的多个私网能够通过代理UDM完成彼此间的通信，进而使得请求私网的UDM能够通过代理UDM从其他私网的UDM中获取到NPN签约，使得UE能够通过NPN签约进行正常网络接入，减少了私网间互相通信的接口数量，同时减少了网络开销以及管理多个接口的复杂度，提升了通信效率。另外，通过从其他私网获取NPN签约，提升了UE接入私网的成功率。
请参阅图3，图3为本申请实施例提供的另一种通信方法流程示意图，如图3所示， 该方法包括如下步骤：
301、第一代理UDM网元接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息。
与图2A～图2F对应的实施例方法相同，在公网中设置代理UDM，使得同一公网中的其他私网能够在该代理UDM中注册，使得完成注册的私网之间能够互相通信。在一些情况下，例如图1D所描述的实施例中，假设NPN2为母公司网络，那么该母公司旗下的子公司对应的NPN签约可以在NPN2中进行存储或记录。NPN2可以在某些情况下，例如设定周期内，包括1天，3天，一个月等，或者在存储容量达到预设最大值，或者存储空间剩余达到预设最小值，或则为了满足业务统筹需要等，自动向子公司网络推送子公司对应的NPN签约，这些NPN签约中包括业务标识信息和业务授权，以及UE标识，用于授权UE使用NPN的相关业务。另外，NPN签约中还包括一些其他的标识信息，这些标识信息用来唯一标识私网身份，用以确定NPN签约对应的主体。NPN签约中的标识信息可以包括NPN的网络标识。通常情况下，如果NPN2从自身数据库获取自身的NPN签约，那么默认网络标识为自身网络标识，NPN签约中省略这一标识信息。如果NPN2获取的是其他NPN签约，那么可以将网络标识作为标识信息。另外，标识信息还可以包括NPN的组标识，用来标识NPN之间的关联关系。
302、第一代理UDM根据所述标识信息向一个或多个UDM发送所述NPN签约。
根据上述描述已知，标识信息是用来确定NPN签约对应NPN的身份的信息或关联关系。因此，可以根据标识信息确定NPN签约的接收方。
当标识信息包括网络标识时，第一代理UDM可以根据NPN签约中的网络标识确定该NPN签约由哪一个NPN接收，例如NPN签约中包括NPN1的网络标识，则由NPN1接收该NPN签约。
当标识信息包括组标识时，第一代理UDM可以根据组标识确定所有与NPN签约的NPN具有关联关系的一系列NPN，并且第一代理UDM可以向该组标识对应的所有UDM发送该NPN签约，而接收到该NPN签约的一系列NPN再根据自身网络标识等信息确定该NPN签约是否适用于本身。
其他UDM在于第一代理UDM进行通信前，需要在第一代理UDM中注册，提交的注册信息包括网络标识、UDM签约以及组标识等。那么当第一代理UDM接收到NPN签约时，可以根据NPN签约中的标识信息匹配到UDM的路由信息，以便对UDM进行正确寻址。
可见，在本申请实施例中，通过代理UDM网元接收UDM自动推送的NPN签约，然后根据NPN签约中的标识信息匹配到NPN签约的接收方(为一个或多个UDM)，最后向接收方发送NPN签约，使得NPN签约能够自动推送到对应NPN中，提升了NPN签约获取的效率，同时使得NPN中的NPN签约能够自动更新，提升了NPN签约的实时性。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以 硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端、控制面网元、存储功能网元或其他网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中，上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在一种可能的实现方式中，如图4所示的通信装置400可作为上述方法实施例所涉及的代理UDM网元，并执行上述方法实施例中由代理UDM网元执行的步骤。如图4所示，该通信装置400可包括接收模块401、发送模块402以及处理模块403，以上接收模块401发送模块402以及处理模块403之间相互耦合。所述接收模块401和发送模块402可用于支持通信装置400进行通信，如分别执行图2A、图2D、图2E、以及图3中的步骤201～步骤204、步骤212、步骤214、步骤222、步骤223、步骤301或步骤302中任意一个由第一代理UDM网元或第二代理UDM网元执行的发送或接收的动作。处理模块403可用于支持所述通信装置400执行上述方法实施例中的处理动作，如执行图2A、图2D、图2E、以及图3中的步骤201～步骤204、步骤212、步骤214、步骤222、步骤223、步骤301或步骤302等由第一代理UDM网元或第二代理UDM网元执行的处理动作。
一种示例，当该通信装置作为第一代理UDM网元，接收模块401可用于接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识；
发送模块402用于根据所述网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；
接收模块401还用于接收第二UDM发送的NPN签约，所述NPN签约中包括业务标识信息和业务授权；
发送模块402还用于向所述第一UDM发送所述NPN签约。
可选的，所述接收模块401具体用于：
接收第二代理UDM网元发送的第一请求，所述第一请求由所述第二代理UDM网元转发来自第一UDM第一请求；
所述发送模块具体用于：
通过第二代理UDM网元向第一UDM发送所述NPN签约。
可选的，所述处理模块403用于：
根据一个UDM提交的注册信息完成一个或多个UDM的注册，以使得所述第一代理UDM网元能够与所述一个或多个UDM通信。
一种示例，当该通信装置作为第一代理UDM网元，接收模块401用于接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息，所述标识信息用于唯一标识NPN；
发送模块402用于根据所述标识信息向一个或多个UDM发送所述NPN签约。
可选的，所述标识信息包括网络标识，发送模块402具体用于：
根据所述网络标识向对应私网的UDM发送NPN签约。
可选的，所述标识信息包括组标识，所述发送模块402具体用于：
获取与所述第二UDM的NPN具有相同组标识的一个或多个NPN；
向所述一个或多个NPN对应的UDM发送所述NPN签约。
所述处理模块403用于：根据一个UDM提交的注册信息完成一个或多个UDM的注册，所述注册信息中包括网络标识和UDM路由信息；
所述发送模块402用于：
根据所述注册信息获取与所述标识信息对应的UDM路由信息；
根据所述UDM路由信息向一个或多个UDM发送所述NPN签约。
当处理模块403为处理器，接收模块401和发送模块402为收发器，本申请实施例所涉及的通信装置400可以为图5所示的通信装置500。
如图5所示，图5示出了本申请实施例中的一种通信装置的硬件结构示意图。UDM网元的结构可以参考图5所示的结构。通信装置500包括：处理器111和通收发器112，所述处理器111和所述收发器112之间电偶合；
所述处理器111，用于执行所述存储器中的部分或者全部计算机程序指令，当所述部分或者全部计算机程序指令被执行时，使得所述装置执行上述任一实施例所述的方法。
所述收发器112，用于和其他设备进行通信；例如接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识。
可选的，还包括存储器113，用于存储计算机程序指令，可选的，所述存储器113(Memory#1)位于所述装置内，所述存储器113(Memory#2)与处理器111集成在一起，或者所述存储器113(Memory#3)位于所述装置之外。
应理解，图5所示的通信装置500可以是芯片或电路。例如可设置在终端装置或者通信装置内的芯片或电路。上述收发器112也可以是通信接口。收发器包括接收器和发送器。进一步地，该通信装置500还可以包括总线系统。
其中，处理器111、存储器113、收发器112通过总线系统相连，处理器111用于执行该存储器113存储的指令，以控制收发器接收信号和发送信号，完成本申请涉及的实现方法中第一设备或者第二设备的步骤。所述存储器113可以集成在所述处理器111中，也可以与所述处理器111分开设置。
作为一种实现方式，收发器112的功能可以考虑通过收发电路或者收发专用芯片实现。处理器111可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。处理器可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片或其他通用处理器。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)及其他可编程逻辑器件、 分立门或者晶体管逻辑器件、分立硬件组件等或其任意组合。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本申请描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例提供了一种计算机存储介质，存储有计算机程序，该计算机程序包括用于执行上述的方法。
本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述提供的方法。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各 个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (25)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一代理UDM网元接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识；
    根据所述网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；
    接收第二UDM发送的NPN签约，所述NPN签约中包括业务标识信息和/或业务授权；
    向所述第一UDM发送所述NPN签约。
  2. 根据权利要求1所述的方法，其特征在于，所述接收来自第一UDM第一请求包括：
    接收第二代理UDM网元发送的第一请求，所述第一请求由所述第二代理UDM网元转发来自第一UDM第一请求；
    向第一UDM发送所述NPN签约包括：
    通过第二代理UDM网元向第一UDM发送所述NPN签约。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：根据一个UDM提交的注册信息完成一个或多个UDM的注册，以使得所述第一代理UDM网元能够与所述一个或多个UDM通信。
  4. 根据权利要求3所述的方法，其特征在于，在所述根据一个UDM提交的注册信息完成多个UDM的注册时，所述一个UDM提交的注册信息包括所述多个UDM的注册信息。
  5. 根据权利要求3或4所述的方法，其特征在于，所述多个UDM与所述一个UDM的NPN包括相同的组标识。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一请求中还包括所述网络标识对应的第一组标识，所述第二UDM的网络标识也对应所述第一组标识。
  7. 一种通信方法，其特征在于，所述方法包括：
    第一代理UDM网元接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息，所述标识信息用于唯一标识NPN；
    根据所述标识信息向一个或多个UDM发送所述NPN签约。
  8. 根据权利要求7所述的方法，其特征在于，所述标识信息包括网络标识，所述根据所述标识信息向一个或多个UDM发送所述NPN签约，包括：
    根据所述网络标识向对应私网的UDM发送所述NPN签约。
  9. 根据权利要求8所述的方法，其特征在于，所述标识信息还包括所述网络标识的组标识，所述根据所述标识信息向一个或多个UDM发送所述NPN签约，包括：
    获取与所述第二UDM的NPN具有相同组标识的一个或多个NPN；
    向所述一个或多个NPN对应的UDM发送所述NPN签约。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，第一代理UDM网元接收第二UDM发送的NPN签约之前，所述方法还包括：
    所述第一代理UDM网元根据一个UDM提交的注册信息完成一个或多个UDM的注 册，所述注册信息中包括网络标识和UDM路由信息；
    所述根据所述标识信息向一个或多个UDM发送所述NPN签约包括：
    根据所述注册信息获取与所述标识信息对应的UDM路由信息；
    根据所述UDM路由信息向一个或多个UDM发送所述NPN签约。
  11. 一种UDM网元，其特征在于，包括处理模块、接收模块和发送模块，其中：
    所述接收模块，用于接收来自第一UDM第一请求，所述第一请求中携带UE标识和网络标识，所述网络标识包括请求网络标识和服务网络标识；
    所述发送模块，用于根据所述网络标识向第二UDM发送第二请求，第二请求中携带UE标识和所述服务网络标识；
    所述接收模块，还用于接收第二UDM发送的NPN签约，所述NPN签约中包括业务标识信息和业务授权；
    所述发送模块，还用于向所述第一UDM发送所述NPN签约。
  12. 根据权利要求11所述的网元，其特征在于，所述接收模块具体用于：
    接收第二代理UDM网元发送的第一请求，所述第一请求由所述第二代理UDM网元转发来自第一UDM第一请求；
    所述发送模块具体用于：
    通过第二代理UDM网元向第一UDM发送所述NPN签约。
  13. 根据权利要求11或12所述的网元，其特征在于，所述网元包括处理模块，用于：
    根据一个UDM提交的注册信息完成一个或多个UDM的注册，以使得所述第一代理UDM网元能够与所述一个或多个UDM通信。
  14. 根据权利要求13所述的网元，其特征在于，在所述根据一个UDM提交的注册信息完成多个UDM的注册时，所述一个UDM提交的注册信息包括所述多个UDM的注册信息。
  15. 根据权利要求13或14所述的网元，其特征在于，所述多个UDM与所述一个UDM的NPN包括相同的组标识。
  16. 根据权利要求11-15任一项所述的网元，其特征在于，所述第一请求中还包括所述网络标识对应的第一组标识，所述第二UDM的网络标识也对应所述第一组标识。
  17. 一种UDM网元，其特征在于，包括接收模块和发送模块，其中：
    所述接收模块，用于接收第二UDM发送的NPN签约，所述NPN签约中包括标识信息，所述标识信息用于唯一标识NPN；
    所述发送模块，用于根据所述标识信息向一个或多个UDM发送所述NPN签约。
  18. 根据权利要求17所述的网元，其特征在于，所述标识信息包括网络标识，所述发送模块具体用于：
    根据所述网络标识向对应私网的UDM发送所述NPN签约。
  19. 根据权利要求18所述的网元，其特征在于，所述标识信息还包括所述网络标识的组标识，所述发送模块具体用于：
    获取与所述第二UDM的NPN具有相同组标识的一个或多个NPN；
    向所述一个或多个NPN对应的UDM发送所述NPN签约。
  20. 根据权利要求17-19任一项所述的网元，其特征在于，所述UDM网元还包括处理模块，用于：根据一个UDM提交的注册信息完成一个或多个UDM的注册，所述注册信息中包括网络标识和UDM路由信息；
    所述发送模块用于：
    根据所述注册信息获取与所述标识信息对应的UDM路由信息；
    根据所述UDM路由信息向一个或多个UDM发送所述NPN签约。
  21. 一种通信装置，其特征在于，所述装置包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合：
    所述至少一个处理器，用于执行所述至少一个存储器中存储的计算机程序或指令，以使得所述装置执行如权利要求1至6中任一项所述的方法，或者使得所述装置执行如权利要求7至10中任一项所述的方法。
  22. 一种可读存储介质，其特征在于，用于存储指令，当所述指令被执行时，使如权利要求1至6中任一项所述的方法被实现，或者使如权利要7至10中任一项所述的方法被实现。
  23. 一种通信装置，其特征在于，包括处理器和接口电路；
    所述接口电路，用于交互代码指令至所述处理器；
    所述处理器用于运行所述代码指令以执行如权利要求1至6中任一项所述的方法，或者所述处理器用于运行所述代码指令以执行如权利要求7至10中任一项所述的方法。
  24. 一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行如权利要求1至6，7至10中任一项所述的方法。
  25. 一种通信系统，包括如权利要求11-16中任一所述的存储网元，或者如权利要求17-20中任一所述的存储网元。
PCT/CN2020/070777 2020-01-07 2020-01-07 签约信息获取方法及装置 WO2021138822A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080093677.8A CN115004635A (zh) 2020-01-07 2020-01-07 签约信息获取方法及装置
PCT/CN2020/070777 WO2021138822A1 (zh) 2020-01-07 2020-01-07 签约信息获取方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/070777 WO2021138822A1 (zh) 2020-01-07 2020-01-07 签约信息获取方法及装置

Publications (1)

Publication Number Publication Date
WO2021138822A1 true WO2021138822A1 (zh) 2021-07-15

Family

ID=76787427

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070777 WO2021138822A1 (zh) 2020-01-07 2020-01-07 签约信息获取方法及装置

Country Status (2)

Country Link
CN (1) CN115004635A (zh)
WO (1) WO2021138822A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125812A (zh) * 2021-11-12 2022-03-01 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质
CN115913584A (zh) * 2021-08-10 2023-04-04 中国电信股份有限公司 鉴权方法、装置、电子设备和计算机可读存储介质
WO2024031390A1 (zh) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 个人物联网信息更新方法、装置、通信设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115515090A (zh) * 2022-09-22 2022-12-23 中国电信股份有限公司 信令互通方法、装置、系统和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108628864A (zh) * 2017-03-15 2018-10-09 华为技术有限公司 一种数据访问方法及数据管理装置
CN108632882A (zh) * 2017-03-17 2018-10-09 电信科学技术研究院 一种码率控制方法、pcf实体、amf实体及smf实体
CN109391979A (zh) * 2017-08-03 2019-02-26 中兴通讯股份有限公司 P-cscf故障恢复方法、装置及系统
CN109548137A (zh) * 2017-08-11 2019-03-29 华为技术有限公司 会话信息管理方法和装置
US10412588B1 (en) * 2019-01-11 2019-09-10 Cisco Technology, Inc. Unified data repository proxy
CN110268766A (zh) * 2017-03-24 2019-09-20 联发科技股份有限公司 通过物理随机接入通道进行波束识别以及有效运用物理随机接入通道资源的装置及方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018170696A1 (zh) * 2017-03-20 2018-09-27 华为技术有限公司 会话管理方法、接入管理功能设备和会话管理设备
CN108810987B (zh) * 2017-04-26 2021-03-05 华为技术有限公司 无线通信的方法、amf、ran和smf
WO2019033269A1 (zh) * 2017-08-15 2019-02-21 华为技术有限公司 一种会话建立的方法及设备
CN110086757B (zh) * 2018-01-26 2020-08-07 华为技术有限公司 通信方法和通信装置
CN110519826B (zh) * 2018-05-22 2021-02-23 华为技术有限公司 网络接入方法、相关装置及系统
WO2020001336A1 (zh) * 2018-06-26 2020-01-02 华为技术有限公司 一种信息处理方法及装置
CN110661753B (zh) * 2018-06-30 2021-10-22 华为技术有限公司 一种网络的注册方法、装置及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108628864A (zh) * 2017-03-15 2018-10-09 华为技术有限公司 一种数据访问方法及数据管理装置
CN108632882A (zh) * 2017-03-17 2018-10-09 电信科学技术研究院 一种码率控制方法、pcf实体、amf实体及smf实体
CN110268766A (zh) * 2017-03-24 2019-09-20 联发科技股份有限公司 通过物理随机接入通道进行波束识别以及有效运用物理随机接入通道资源的装置及方法
CN109391979A (zh) * 2017-08-03 2019-02-26 中兴通讯股份有限公司 P-cscf故障恢复方法、装置及系统
CN109548137A (zh) * 2017-08-11 2019-03-29 华为技术有限公司 会话信息管理方法和装置
US10412588B1 (en) * 2019-01-11 2019-09-10 Cisco Technology, Inc. Unified data repository proxy

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Deployment option for NF Discovery and Selection", 3GPP DRAFT; S2-186558 - DEPLOYMENT OPTION FOR NF DISCOVERY AND SELECTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Vilnius, Lithuania; 20180702 - 20180706, 1 July 2018 (2018-07-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051469708 *
HUAWEI, HISILICON: "Deployment option for user identity to UDM/UDR/AUSF/PCF and IMS-HSS resolution", 3GPP DRAFT; S2-1901977 - DEPLOYMENT OPTION FOR USER IDENTITY TO UDM-UDR-AUSF-PCF AND IMS-HSS RESOLUTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Santa Cruz, Tenerife, Spain; 20190225 - 20190301, 19 February 2019 (2019-02-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051597547 *
MOTOROLA MOBILITY, LENOVO: "Support of HSS FE and UDM interworking with separate UDR repositories for EPS and 5GS subscription data", 3GPP DRAFT; S2-188168_UDICOM_0_2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sophia-Antipolis, France; 20180820 - 20180824, 14 August 2018 (2018-08-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051537102 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115913584A (zh) * 2021-08-10 2023-04-04 中国电信股份有限公司 鉴权方法、装置、电子设备和计算机可读存储介质
CN114125812A (zh) * 2021-11-12 2022-03-01 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质
CN114125812B (zh) * 2021-11-12 2023-07-18 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质
WO2024031390A1 (zh) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 个人物联网信息更新方法、装置、通信设备及存储介质

Also Published As

Publication number Publication date
CN115004635A (zh) 2022-09-02

Similar Documents

Publication Publication Date Title
WO2021138822A1 (zh) 签约信息获取方法及装置
WO2020048469A1 (zh) 一种通信的方法及装置
US20220159606A1 (en) Policy Control Function Network Element Selection Method, Apparatus, System, and Storage Medium
US20220272607A1 (en) Network Access Method and Communication Apparatus
WO2020249861A1 (en) Communication security between user equipment and third-party application using communication network-based key
WO2022222745A1 (zh) 一种通信方法及装置
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
US11789803B2 (en) Error handling framework for security management in a communication system
CN112997518A (zh) 通信系统中的分解基站中的安全性管理
WO2022027505A1 (en) User equipment authentication and authorization procedure for edge data network
US20220263879A1 (en) Multicast session establishment method and network device
WO2021087696A1 (zh) 身份认证方法及通信装置
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
CN116210252A (zh) 接收用于边缘计算的用户同意的网络操作
CN113574829A (zh) 与第三方应用共享通信网络锚定加密密钥
WO2022174399A1 (en) User equipment authentication and authorization procedure for edge data network
CN114885382A (zh) 一种业务会话管理方法、装置及存储介质
JP2024519311A (ja) データ入手方法およびシステム、ならびにその装置
KR20220152950A (ko) 네트워크 슬라이스 승인 제어(nsac) 발견 및 로밍 향상들
WO2022027529A1 (zh) 一种切片认证的方法及装置
WO2024032226A1 (zh) 通信方法和通信装置
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
US20240244107A1 (en) Method for determining application server
WO2023040958A1 (zh) 一种联邦学习组处理方法、装置及功能实体
WO2023005714A1 (zh) 一种无线通信方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20912209

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20912209

Country of ref document: EP

Kind code of ref document: A1