Communication method and apparatus

Abstract

The present application belongs to the field of communications. Provided are a communication method and apparatus. The method comprises: when different types of users request access to a second network, that is, when a first user and a second user request access to the second network, a first network element sending, to a first network, first information used for indicating subscription information of the first user, and / or sending, to the second network, second information used for indicating subscription information of the second user, wherein the first network and the second network may be a macro network and a subnetwork, respectively, such that the first network element flexibly pushes subscription data to the macro network and / or the subnetwork, enabling the macro network and the subnetwork to collaboratively ensure that the user can obtain a localized service of the subnetwork. In this way, users of different types, such as users of different network operators, can not only successfully access a subnetwork, but can also smoothly access a network without changing a SIM.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411465125.1, filed with the State Intellectual Property Office of China on October 18, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0003] Non-public networks (NPNs) typically come in two types: stand-alone non-public networks (SNPNs) and public network integrated non-public networks (PNI-NPNs). Currently, a further development is the distributed subnetwork architecture. In this architecture, the core network (CN) can be divided into two parts: the main network and the subnetworks. The main network, deployed by the operator, is the central network and possesses complete core network functions, providing all management services for terminals. Multiple subnetworks can exist, and a terminal can access services from multiple subnetworks simultaneously. Network elements within a subnetwork are deployed on demand; missing elements can utilize the corresponding network elements in the main network to obtain services. In other words, some network functions in the central network can be shared and used by subnetworks.

[0004] Distributed subnets can provide localized services, may be temporarily deployed, and support user access from the operator providing the subnet. However, how to ensure successful user access to the subnet and access its localized services for different types of users (such as users from different operators) is a current research topic. Summary of the Invention

[0005] This application provides a communication method and apparatus that enables users to successfully access a subnet and obtain localized subnet services when facing different types of users.

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

[0007] In a first aspect, a communication method is provided, comprising: a first network element sending first information to a first network, the first information indicating subscription information of a first user, the first user being a user requesting access to a second network; and / or, the first network element sending second information to a second network, the second information indicating subscription information of a second user, the second user being a user requesting access to the second network. Wherein, the second network and the first network are networks provided by the same operator, and the first network and a majority of the second networks share some network elements.

[0008] As described in the first aspect of the method, when the first network element encounters different types of user requests to access the second network (i.e., when the first user and the second user request to access the second network), it sends first information indicating the first user's subscription information to the first network and / or sends second information indicating the second user's subscription information to the second network. The first network and the second network can be a main network and a subnet, respectively. This allows the first network element to flexibly push subscription data to the main network and / or the subnet, enabling the main network and the subnet to work together to ensure that users can access the localized services of the subnet. Thus, for different types of users, such as users from different network operators, not only can users successfully access the subnet, but the terminal can also smoothly access the network without changing its subscriber identity module (SIM).

[0009] One possible design is that the first network is the central network and the second network is the subnet. Some network functions in the central network are shared with the subnet, which means that in a distributed subnet scenario, users can successfully register to the subnet.

[0010] One possible design scheme is that the first network element sends the first information to the first network, which may include: the first network element determining the operator to which the first user belongs, and if the operator to which the first user belongs is the same as the operator providing the first network, or if the operator to which the first user belongs has a roaming agreement with the operator providing the first network, the first network element sends the first information to the first network.

[0011] The operator to which the first user belongs can be the operator to which the first user signed a contract, or it can be understood as the first user purchasing services from that operator; there is no limitation here.

[0012] It can be seen that the first network element can identify / determine the user's operator and maintain information about networks with the first network, networks with roaming agreements with the first network, and networks without roaming agreements with the first network. Therefore, the first network element can determine that the operator to which the first user belongs is the same as the operator providing the first network, or that the operator to which the first user belongs has a roaming agreement with the operator providing the first network.

[0013] Thus, when the first network element faces a first user whose operator is the same as or has a roaming agreement with the operator providing the first network, it sends first information to the first network to indicate the first user's subscription information, so that the first network and the second network can work together to ensure that the first user can normally obtain the localized services of the second network.

[0014] One possible design scheme is that the first network element sends second information to the second network, which may include: the first network element determining the operator to which the second user belongs, and if the operator to which the second user belongs is different from the operator providing the first network, and the operator to which the second user belongs has no roaming agreement with the operator providing the first network, the first network element sends second information to the second network.

[0015] The first network element can determine the second user's operator information and maintain information about networks connected to the first network, networks with roaming agreements with the first network, and networks without roaming agreements with the first network. Therefore, the first network element can determine that the second user's operator is different from the operator providing the first network, and that the second user's operator has no roaming agreement with the operator providing the first network. In other words, the second user cannot access the first network. Therefore, the first network element sends second information to the second network and obtains services from the second network.

[0016] Thus, when the first network element faces a second user whose operator is different from the operator providing the first network and who has no roaming agreement, it sends second information to the second network to indicate the second user's subscription information. This flexible way of sending subscription information enables the first and second networks to work together to ensure that the second user can normally obtain the localized services of the second network.

[0017] Optionally, the first information includes the identifier of the second network and the first identifier. The first identifier is used to identify the first user and can be a generic public subscription identifier (GPSI), an international mobile subscriber identity (IMSI), internet protocol (IP) information, media access control (MAC) address, etc., without any restrictions.

[0018] The identifier of the second network can be the identifier of a public land mobile network (PLMN) (PLMN ID), a network identifier (Network ID, NID), a special subnet identifier, or any other possible identifier, without any specific restrictions.

[0019] The first identifier can be a permanent identifier that uniquely identifies the first user, such as a generic public subscription identifier (GPSI), or any other possible identifier, without specific limitations. The first identifier can be assigned by the user's home network operator. Thus, the identifier of the second network and the first identifier can be used by the first network for authorizing operations on the first information.

[0020] Optionally, the second information includes the identifier of the second network and a second identifier. The second identifier may be an identifier assigned to the second user by the application layer for obtaining services in the second network. In other words, the second identifier may be the UE's identity identifier in the second network for accessing the second network and obtaining services.

[0021] Optionally, the communication method may further include: the first network element sending a second identifier to the first user.

[0022] The second identifier can be a temporary identifier assigned by the application layer to the second user for the second network, such as a user identity (user ID). Of course, it can also be other possible temporary identifiers; there are no restrictions. The network element that assigns the second identifier to the second user can be the first network element or other network elements at the application layer; there are no restrictions. Thus, the identifier of the second network and the second identifier can be used for authorization operations on the second information by the second network.

[0023] In one possible design, the first network element sending second information to the second network may further include: the first network element receiving indication information from the first network, the indication information indicating that the operator to which the second user belongs is different from the operator providing the first network, and that the operator to which the second user belongs has no roaming agreement with the operator providing the first network. The first network element then sends the second information to the second network according to the indication information.

[0024] It can be seen that the first network element cannot identify / determine the user's operator. The indication information is used to indicate that the second user's operator is different from the operator providing the first network and there is no roaming agreement, which implicitly instructs the first network element to redirect the second information to the second network. Alternatively, the indication information can also be used to instruct the first network element to redirect the second information to the second network, i.e., an explicit indication method. Through this indication information, the first network element can send the message to the correct network even when it cannot determine the user's operator, enabling the first and second networks to work together to ensure that the user can normally obtain localized services from the second network.

[0025] Optionally, before the first network element receives the instruction information from the first network, the method further includes: the first network element sending second information to the first network.

[0026] The first network element does not identify / determine the user's operator and sends the second information to the first network by default. After receiving the second information, the first network determines that the operator to which the second user belongs is different from the operator providing the first network and that there is no roaming agreement. Therefore, the first network sends the aforementioned instruction information to the first network element.

[0027] It is understandable that if the first network receives the second information and determines that the operator to which the second user belongs is the same as or has a roaming agreement with the operator providing the first network, the first network will not send the above-mentioned instruction information to the first network element, and the first network will perform the authorization operation on the second information, and if the authorization is successful, store the second user's subscription information.

[0028] Thus, if the first network element cannot identify / determine the user's operator, it can send the second information directly to the first network. If the second user's operator is different from the operator providing the first network and there is no roaming agreement, it will receive the instruction information from the first network and then send the second information to the second network. This allows the first and second networks to work together to ensure that the second user can normally obtain the localized services of the second network.

[0029] Secondly, a communication method is provided, comprising: a second network element receiving first information, the first information indicating first subscription information of a first user, the first user being a user requesting access to a second network, and the first information being provided by the first network element; the second network element performing an authorization operation on the first information, the authorization operation being used to determine whether the first network element can provide the first information; wherein the second network element is deployed in the first network, the second network and the first network are networks provided by the same operator, and the first network and a majority of the second networks share some network elements.

[0030] As can be seen from the second aspect of the method, the authorization operation of the first network determines whether the first network element can provide the first information, or whether it has the capability to provide the first information. If the second network element determines that the first network element can provide the first information, then the authorization is successful. The first information indicates the subscription information requested for accessing the second network. The first network and the second network can be a large network and a subnet, respectively. In other words, the authorization operation is used to determine whether the first network element can provide the subscription information corresponding to a specific subnet. Thus, authorization operations are performed at the subnet level, rather than the UE level, achieving the technical effect of distributed subscription.

[0031] One possible design scheme involves the first information including the identifier of the second network. The second network element performs an authorization operation on the first information, which may include: the second network element obtaining the subscription information of the first network element from a third network element deployed in the first network. Based on the subscription information of the first network element and the identifier of the second network, the second network element determines whether the first network element can provide the first information. If the first network element can provide the first information, the authorization is successful.

[0032] The second network element can be a NEF network element or other network elements that can realize network open functions, without any restrictions.

[0033] After receiving the first information, the second network element determines whether the provider of the first information (i.e., the first network element) has purchased services from the second network. The second network element queries the first network element's subscription information based on its information (such as its identifier), and determines the subnet information corresponding to the first network element within that subscription information. It then checks whether the subnet information corresponds to the identifier of the second network. The subnet information indicates that the first network element has purchased services from that subnet. This achieves authorization operations at the subnet level for the first network element.

[0034] Optionally, the communication method may further include: if authorization is granted, the second network element sends the second subscription information of the first user to the third network element, wherein the second subscription information is determined based on the first subscription information.

[0035] The second network element determines that the first network element can provide the first information, i.e., the authorization is passed. Then, the second network element sends the second subscription information of the first user to the third network element so that the third network element can store the second subscription information of the first user.

[0036] Optionally, the first subscription information includes the identifier of the second network and a first identifier, the first identifier being a permanent identifier representing the first user; the second subscription information includes the identifier of the second network and a third identifier, the third identifier being derived from the second identifier.

[0037] The third identifier can be a permanent identifier used to identify the first user, such as a subscription permanent identifier (SUPI), or it can be any other identifier applicable to the first network, without restriction. The second network element performs identifier conversion on the first identifier in the first subscription information to obtain the third identifier, which is then applicable to the first network.

[0038] One possible design scheme is that the second network element performs an authorization operation on the first information, which may include: if the authorization is successful, the second network element stores the first user's first subscription information.

[0039] The second network element can be a unified data management (UDM) network element that stores the subscription information of the first network element. The second network element determines whether the first network element can provide the first information. If it determines that it can provide the first information, authorization is granted, and the second network element stores the first user's first subscription information.

[0040] The above provides two authorization operations, which improves the flexibility of performing authorization on the first piece of information.

[0041] Thirdly, a communication method is provided, comprising: a second network element receiving second information from a first network element, the second information indicating subscription information of a second user, the second user being a user requesting access to a second network, and the second information including an identifier of the second network; the second network element performing an authorization operation on the second information, the authorization operation being used to determine whether the second network is the network in which the second network element is deployed; and, if authorization is successful, the second network element sending the second user's subscription information to a third network element, the third network element and the second network element being deployed in the same network.

[0042] Based on the method described in the third aspect, the second network element performs an authorization operation on the second information, such as determining whether the identifier of the second network in the second information matches the identifier of the local network. If they match, the authorization is successful. Then, if the authorization is successful, the second network element sends the second user's subscription information to the third network element so that the third network element can store the second user's subscription information. The first network and the second network can be a large network and a subnet, respectively. This achieves authorization operations at the subnet level, rather than the UE level, thus achieving the technical effect of distributed subscription.

[0043] It is understandable that the technical effects of the third method can be referenced from the relevant introductions of the first or second methods mentioned above, and will not be repeated here.

[0044] Fourthly, a communication method is provided, comprising: a third network element receiving first information, wherein the third network element is deployed in a first network, the first information indicating subscription information of a first user, the first user being a user requesting access to a second network, and the first user's subscription information including subscription information related to access management functions of the second network, subscription information related to mobility management functions of the second network, and subscription information related to session management functions of the second network. The third network element stores the subscription information related to access management functions and the subscription information related to mobility management functions. The third network element sends the subscription information related to session management functions to the second network. The second network and the first network are networks provided by the same operator, and the first network shares some network elements with a majority of the second networks.

[0045] It is understandable that the third network element stores part of the first user's subscription information and sends the subscription information related to the SM of the second network to the second network. The second network stores the subscription information related to the SM of the second network so that when the user requests to establish a session with the second network later, the second network can directly establish a session based on the stored subscription information related to the SM.

[0046] It is understandable that the technical effects of the fourth method can be referenced from the relevant introductions of the first or second methods mentioned above, and will not be repeated here.

[0047] Fifthly, a communication device is provided. This communication device is used to perform the communication method described in any implementation of the first or fourth aspect.

[0048] In this application, the communication device described in the fifth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the fourth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0049] It should be understood that the communication apparatus described in the fifth aspect includes modules, units, or means that implement the communication method described in either the first or fourth aspect. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication method.

[0050] A sixth aspect provides a communication device. The communication device includes a processor configured to execute the communication method described in any possible implementation of the first or fourth aspect.

[0051] In one possible design, the communication device described in the sixth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the sixth aspect and other communication devices.

[0052] In one possible design, the communication device described in the sixth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the communication method described in either the first or fourth aspect.

[0053] In this application, the communication device described in the sixth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the sixth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0054] A seventh aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory, such that the communication device performs the communication method described in any possible implementation of the first or fourth aspect.

[0055] In one possible design, the communication device described in the seventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.

[0056] In this application, the communication device described in the seventh aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the seventh aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0057] Eighthly, a communication device is provided, comprising: a processor and a memory; the memory is used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the first or fourth aspects.

[0058] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0059] In this application, the communication device described in the eighth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the eighth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0060] A ninth aspect provides a communication device comprising: a processor; the processor being configured to be coupled to a memory, and after reading a computer program from the memory, to execute a communication method as described in any implementation of the first or fourth aspect according to the computer program.

[0061] In one possible design, the communication device described in the ninth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the ninth aspect and other communication devices.

[0062] In this application, the communication device described in the ninth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the ninth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0063] In a tenth aspect, a processor is provided. The processor is configured to execute the communication method described in any possible implementation of the first or fourth aspect.

[0064] Eleventhly, a communication system is provided. The communication system includes network equipment for performing the methods described in any one of the first to fourth aspects, such as a first network element, a second network element, or a third network element.

[0065] In a twelfth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, causing the computer to perform the communication method described in any possible implementation of the first or fourth aspect.

[0066] In a thirteenth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any possible implementation of the first or fourth aspect. Attached Figure Description

[0067] Figure 1 is a schematic diagram of the distributed subnet architecture;

[0068] Figure 2 is a schematic diagram of the registration process;

[0069] Figure 3 is a schematic diagram of the external parameter authorization process;

[0070] Figure 4 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0071] Figure 5 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0072] Figure 6 is a schematic diagram of an application scenario of the communication method provided in the embodiments of this application;

[0073] Figure 7 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0074] Figure 8 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0075] Figure 9 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0076] Figure 10 is a schematic flowchart of the communication method provided in the embodiment of this application;

[0077] Figure 11 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0078] Figure 12 is a schematic diagram of the registration and service acquisition process provided in an embodiment of this application;

[0079] Figure 13 is a schematic diagram of the registration and service acquisition process provided in the embodiment of this application (II).

[0080] Figure 14 is a schematic diagram of the communication device provided in an embodiment of this application;

[0081] Figure 15 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0082] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0083] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0084] 1. NPN:

[0085] Existing standards define NPN (Network Provider Network), which third-party service providers can deploy to provide services to terminals. For example, NPN can be deployed in industrial parks to provide highly reliable, low-latency communication services to devices within the park. However, existing NPN technologies have some limitations and cannot meet future network requirements.

[0086] For example, NPN has two deployment methods: SNPN and PNI-NPN.

[0087] SNPN requires the deployment of independent core network equipment, resulting in high operational and maintenance costs, which are difficult for small and medium-sized enterprises to bear. PNI-NPN does not require additional core network deployment. It uses the operator's public network core network, employing methods such as slicing / data network name (DNN) to isolate specific resources and configure them for PNI-NPN use. Because this deployment method relies on the operator's core network, enterprises cannot achieve autonomous management of PNI-NPN and can only rely on the main network core network to provide corresponding functions. PNI-NPN cannot achieve agile deployment for enterprise needs. Therefore, in future network evolution, a distributed subnet deployment method needs to be proposed.

[0088] 2. Distributed subnets:

[0089] Figure 1 illustrates the architecture of a distributed subnet. As shown in Figure 1, in this architecture, the core network can be divided into two parts: the main network and the subnets. The main network is the central network deployed by the operator, also known as the central network, which possesses complete core network functions and can provide all management services for terminals. Multiple subnets can exist, and a terminal can simultaneously access services from multiple subnets. Network elements within a subnet are deployed on demand; missing network elements can obtain services using the corresponding network elements in the main network. In other words, some network functions in the central network can be shared by subnets. Of course, in this distributed subnet architecture, some subnets may not share network functions with the central network; this is not a limitation.

[0090] For example, the existing network's access and mobility management function (AMF) can be split. Access control functions can be broken down into access management (AM) functions, or non-access-stratum (NAS) management functions (NMF), abbreviated as NM. AM or NM can also be referred to as access management network elements / functions / entities, etc., without restriction. AM1 is deployed in the main network. Since subnets also need to process terminal NAS messages, AM will be deployed in each subnet as the entry network element for terminal access to the subnet, i.e., AM2 is deployed in the subnet. Some functions of the original mobility management are renamed as mobility management functions (MMF), abbreviated as MM. Terminal mobility management can be handled by the main network, and MM can be deployed in the main network, while subnets can optionally deploy MM.

[0091] The main network can also deploy session management (SM) and network repository function (NRF). Subnets can also deploy location management (LM) and NRF. SM can also be referred to as session management network element / function / entity, and LM can also be referred to as location management network element / function / entity, without restriction. NRF supports network function registration and discovery.

[0092] As can be seen, distributed subnet deployment only deploys a subset of functional network elements as needed, thus eliminating the need for deploying complete core network elements like SNPN, thereby saving on core network operation and maintenance costs. Since the subnet only deploys a subset of functional network elements on demand, the remaining undeployed network elements still need to be provided by the main network core network to provide complete services to the terminals. Because the core network of a distributed subnet is deployed locally, it can be autonomously managed by the enterprise, enabling agile deployment of subnet network functions (NFs).

[0093] The architecture in Figure 1 is only an example. In the architecture shown in Figure 1, N2 routing and NAS routing are performed by the RAN. However, in reality, N2 routing and NAS routing may not be performed by the RAN. For example, there may be a dedicated signaling routing network element between the RAN and the main network AMF and the subnet AMF, or there may be a network element for routing signaling between the main network AMF, the subnet AMF and the RAN.

[0094] The following describes a scenario example of a distributed subnet. For instance, a subnet is temporarily deployed in an amusement park specifically for extended reality (XR) services, for the use of visitors. In this scenario, visitors can only access the XR service through the amusement park's subnet. Due to the temporary deployment of the subnet, how to enable different types of UEs (such as those from different operators) to smoothly access the network without changing their SIM cards is a current research problem.

[0095] 3. Registration process:

[0096] Figure 2 is a schematic diagram of the registration process. As shown in Figure 2, the process is as follows:

[0097] S201, the user equipment (UE) sends a registration request message to the radio access network (RAN).

[0098] The registration request message carries onboarding indication information, registration type, and UE identification information. The registration type can be set to SNPN Onboarding. The UE identification information can be, for example, a subscription concealed identifier (SUCI), generated based on the default credential. The SUCI is then encrypted to become a subscription permanent identifier (SUPI).

[0099] S202, RAN selects the appropriate AMF.

[0100] RAN selects AMF based on the registration instruction information.

[0101] S203, the RAN sends a registration request message to the new AMF.

[0102] S204, the context of the interaction between the new AMF and the old AMF in the UE.

[0103] S204 is an optional step.

[0104] S205, the new AMF selects the appropriate authentication server function (AUSF) for authorization and other security processes.

[0105] After receiving a registration of type SNPN, AMF restricts the UE to only register on this network and selects an appropriate AUSF.

[0106] S206, UE, AMF, and AUSF interact to complete mutual authorization between the UE and the network side.

[0107] AMF can perform authorization on the local AMF using default credentials.

[0108] S207, AAA interaction between UE, AMF, and Distributed Control System (DCS) to complete mutual authorization between UE and the network side.

[0109] AMF can also use DCS's authentication, authorization, and accounting (AAA) functions for authorization.

[0110] S208, the UE, AMF, DCS AUSF, and DCS unified data management (UDM) functions interact to complete the mutual authorization between the UE and the network side.

[0111] AMF can also be licensed using DCS's AUSF and UDM.

[0112] Steps S206-S208 are optional; any one of them can be executed.

[0113] S209, the new AMF sends registration status update information to the old AMF.

[0114] S210, the new AMF obtains device identity information from the UE.

[0115] Steps S209-S210 are optional. The device identity information can be the UE's device identifier, such as the International Mobile Equipment Identity (IMEI).

[0116] S211, the new AMF obtains device identity check information from the equipment identity register (EIR).

[0117] S211 is an optional step. The new AMF obtains device identity check information from the EIR based on the device identity information to ensure the uniqueness and security of the UE.

[0118] S212, the new AMF sends a registration acceptance message to the UE.

[0119] S213, the UE sends a registration completion message to the new AMF.

[0120] S213 is an optional step.

[0121] It is understandable that if the user's carrier is different from the carrier providing the main network / subnet, this registration method requires changing the SIM card to access the subnet, which cannot achieve the requirement of smooth access to the subnet.

[0122] 4. External parameter authorization process:

[0123] Figure 3 is a schematic diagram of the external parameter authorization process. As shown in Figure 3, the process is as follows:

[0124] S301, Application Function (AF), provides service parameters to the network.

[0125] Service parameters may include, for example, the UE's slice and / or data network name (DNN) information. The AF interacts with the UE through the RAN to obtain the UE's slice and / or DNN information. The AF then provides the service parameters to the network through core network elements. This process involves network elements such as AMF, policy control function (PCF), unified data repository (UDR), and network exposure function (NEF), etc. For details, please refer to existing procedures; further elaboration is omitted.

[0126] S302, NEF sends a service authorization request message to UDM.

[0127] The Service Authorization Request message is used to request the UDM to authorize the AF service parameters. The Service Authorization Request message can carry the AF service parameters.

[0128] S303, UDM authorizes the service parameters provided by AF.

[0129] For example, the UDM determines whether to authorize the service / service corresponding to the slice / DNN, that is, whether to allow the UE to obtain the service / service in the network. Another example is whether the machine-type communication (MTC) provider is authorized to serve the UE.

[0130] S304, UDM sends an authorization response message to NEF.

[0131] The authorization response message can indicate that authorization for the service parameters provided by AF has been granted.

[0132] It is understandable that the authorization of service parameters for the AF mainly targets whether the UE's original subscription includes service parameters provided by the AF, and whether the AF can provide services to the UE. In a distributed subnet scenario, how can the subnet service provider flexibly push subscription data when facing different types of user requests to access the subnet, so that the main network and the subnet can work together to ensure that users can normally obtain localized subnet services, is a current research issue.

[0133] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0134] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0135] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0136] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0137] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

[0138] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0139] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, a MAC control element (CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0140] Second, in the embodiments shown below, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they distinguish different indication information.

[0141] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0142] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0143] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0144] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0145] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG4 as an example. Exemplarily, FIG4 is a schematic diagram of the architecture of the communication system provided in the embodiments of this application.

[0146] Figure 4 is a schematic diagram of the communication system architecture, which mainly includes: a first network element, a first network, and a second network.

[0147] The first network element can be an application-layer functional network element, such as an AF network element, or other network elements that can provide application services; there are no limitations. The first network element interacts with the first network and / or the second network and provides application services. The first network element can be deployed by the operator or a trusted third party.

[0148] The first network shares some network functions with a majority of the second networks, which can also be extended to include all second networks. For example, the first network can be a large network or a central network, and the second networks can be subnets. Some network functions in the central network can be shared by all / most subnets, such as all / most subnets being able to use network elements like ASUF, PCF, and SMF in the central network. The service range of the central network can also cover the subnets. For example, if the service range of a subnet is the area where a park or factory is located, the service range of the central network is the service range of the operator's network, covering that park or factory.

[0149] In one possible scenario, this communication system can be applied to 5G or future communication systems. For example, Figure 5 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 5, in a distributed subnet scenario, the communication system includes a RAN, a main network (i.e., the first network mentioned above), and a subnet (i.e., the second network mentioned above). The main network deploys access management functions (AM), MM, and UDM, while the subnet deploys AM, SM, and UDM. A third party (i.e., the first network element mentioned above, such as AF) interacts with the main network using the NEF deployed in the main network (not shown in Figure 5), thereby authorizing the user's subscription information in cooperation with the main network's NEF and UDM. And / or, the third party interacts with the subnet using the NEF deployed in the subnet (not shown in Figure 5), thereby authorizing the user's subscription information in the subnet's NEF, and sending the user's subscription information to the subnet's UDM after authorization.

[0150] The RAN comprises at least one RAN node and at least one terminal device. The terminal device is connected to the RAN node wirelessly. The RAN node is connected to the main network and subnets wirelessly or via wired connection.

[0151] RAN can be a 3GPP-related cellular system, such as 4G, 5G mobile communication systems, or future-oriented evolution systems (such as future mobile communication systems). RAN can also be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a Wi-Fi system. RAN can also be a communication system that integrates two or more of the above systems.

[0152] RAN nodes, sometimes also called access network equipment, RAN entities, or access nodes, are part of a communication system and are used to help terminal devices achieve wireless access. Multiple RAN nodes in a communication system can be of the same type or different types.

[0153] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a future mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a Wi-Fi system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0154] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, active antenna units (AAUs), or remote radio heads (RRHs).

[0155] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0156] It is understood that the RAN node mentioned above can be a newly defined name, and RAN nodes can also be described in different ways, such as access node, network device, wireless access node, etc., without limitation. Unless otherwise specified in this application, network device will be used as the term.

[0157] Terminal equipment can be a terminal with transceiver capabilities, or it can be a chip or chip system installed in the terminal equipment. This terminal equipment can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, and roadside units with terminal functions. The terminal device in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in D2D communication. The embodiments of this application do not limit the device form of the terminal device. The device used to implement the terminal function can be a terminal device; it can also be a device that supports the terminal in implementing the function, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or include chips and other discrete devices.

[0158] For example, based on the above communication system, for users requesting access to the subnet (i.e., the second network mentioned above), this application embodiment provides two possible access methods, as follows: Method 1 and Method 2.

[0159] Method 1: For users whose mobile network operator is the same as the operator providing the main network (i.e., the first network mentioned above), or for users with roaming agreements.

[0160] For example, as shown in Figure 6(a), operator A provides a main network and subnets, and there is a roaming agreement between operator A and operator B. The UE belongs to either operator A or operator B. That is, the UE belongs to the same operator network as the operator providing the main network, or to an operator that has a roaming agreement with the operator network of the main network / subnet.

[0161] When a UE requests access to a subnet's services, it can subscribe to the subnet via SUPI and obtain the services within the subnet. At this point, the main network needs to store the subnet's subscription information so that subsequent UEs can be authorized to obtain local services within the subnet.

[0162] Method 2: This method is for users who request access to the subnet but whose carrier is different from the carrier providing the main network, and for whom there is no roaming protocol.

[0163] For example, as shown in Figure 6(b), operator A provides a main network and subnets. There is no roaming agreement between operator A and operator B, and the UE belongs to operator B. In other words, the network of the UE's operator is different from that of the operator providing the main network, and there is no roaming agreement. Therefore, the network of the UE's operator and the network of the operator providing the main network cannot exchange information.

[0164] When a UE requests access to services from a subnet, it needs to use a temporary identifier (e.g., user ID) to access the subnet and obtain services within the subnet. In this case, the subnet needs to pre-store the UE's temporary subscription data so that the UE can be authorized to obtain local services within the subnet.

[0165] With these two access methods, if the UE's operator is the same as the operator providing the main network (i.e., the first network mentioned above), or if a roaming agreement exists, the access procedure is executed from the main network, and subsequent signaling is routed to the subnet. If the UE's operator is different from the operator providing the main network, and no roaming agreement exists, the access procedure can be executed directly from the subnet, achieving the effect of smooth network access for the UE without changing the SIM card.

[0166] In this communication system, when the first network element (i.e., the application layer functional network element, such as the AF network element) encounters different types of users—that is, when the first user and the second user request access to the second network (i.e., the subnet)—it flexibly pushes subscription data to the main network and / or the subnet by sending first information indicating the first user's subscription information to the first network and / or second information indicating the second user's subscription information to the second network. This allows the main network and the subnet to work together to ensure that users can access the localized services of the subnet. Thus, for different types of users, such as users from different network operators, not only can users successfully access the subnet, but the UE can also smoothly access the network without changing its SIM card.

[0167] It should be understood that the communication method provided in this application embodiment can be applied to the device shown in Figure 5, such as between the first network element, the first network, and the second network. Specific implementations can be found in the following method embodiments, which will not be repeated here. The solutions in this application embodiment can also be applied to other communication systems, and the corresponding names can be replaced with the names of the corresponding functions in other communication systems.

[0168] It should also be understood that Figure 5 is a simplified schematic diagram for ease of understanding only, and the communication system may also include other network devices and / or other terminal devices, which are not shown in Figure 5.

[0169] The interaction process between devices in the above-described communication system will be specifically described below with reference to Figure 7, through a method embodiment. The communication method provided in this application embodiment can be applied to the interaction between the first network element, the first network, and the second network in the above-described communication system, which will be described in detail below.

[0170] As shown in Figure 7, the flow of this communication method is as follows:

[0171] S701, the first network element sends the first information to the first network, and the first network receives the first information accordingly.

[0172] The first information is used to indicate the subscription information of the first user, who is the user requesting access to the second network. After purchasing services from the second network through the application layer, the first user requests access to the second network through the first network element. The first network element can be a functional network element of the application layer, such as an AF network element, or any other network element that can provide application services; there are no limitations on this.

[0173] The first user's subscription information may include one or more of the following: subscribed service information, indicating which services the first user can initiate. The service information may be DNN and / or slice information, or any other information that can be used to indicate services. Slice information may be, for example, single network slice selection assistance information (S-NSSAI), without any specific limitation; information on the authorized network range, i.e., information on the authorized area, such as cell information; and required latency, bandwidth, and other information.

[0174] The first message can reuse existing messages for transmission, such as the service parameter creation (Nnef_ServiceParameter_Create) message, or it can be a newly defined message; there are no restrictions on this.

[0175] The second network and the first network are provided by the same operator. The first network shares some network elements with most of the second networks. The first network can be understood similarly to the description of the main network above, and the second network can be understood similarly to the description of the subnet above. That is, the first network can be the operator's central network, also called the core network, possessing complete core network functions and providing all management services for the terminal. Multiple second networks can exist, and a terminal can simultaneously access services from multiple second networks. Network elements in the second network are deployed on demand; missing network elements can use the corresponding network in the first network to obtain services. In other words, some network functions in the first network can be shared by the second networks. Of course, the first network may also choose not to share network functions with some of the second networks, meaning the first network shares some network elements with most of the second networks; this is not a limitation.

[0176] Optionally, the first information may include the identifier of the second network and a first identifier, whereby the first identifier is a permanent identifier representing the first user.

[0177] The identifier of the second network can be the identifier of the public land mobile network (PLMN) (PLMN ID), the network identifier (NID), a special subnet identifier, or any other possible identifier, without any specific restrictions.

[0178] The first identifier can be a permanent identifier that uniquely identifies the first user, such as a generic public subscription identifier (GPSI), international mobile subscriber identity (IMSI), internet protocol (IP) information, MAC address, or any other possible identifier, without specific restrictions. The first identifier can be assigned by the user's home network operator.

[0179] Optionally, the first information may include the identifier of the application function network element (AF / AS), such as AF ID, IP address, port number; or an identifier used to characterize user information, used to identify the network element information or user information (i.e., the information of the first user) that provides the first information.

[0180] S702, the first network element sends the second information to the second network, and the second network receives the second information accordingly.

[0181] The second information is used to indicate the subscription information of the second user, who is the user requesting access to the second network. The second information can reuse existing messages for transmission, such as the service parameter creation (Nnef_ServiceParameter_Create) message, or it can be a newly defined message; there are no restrictions on this.

[0182] The second user's subscription information may include one or more of the following: subscription service information, indicating which services the second user can initiate, wherein the service information may be DNN and / or slice information, or any other information that can be used to indicate services, wherein slice information may be, for example, S-NSSAI, without any specific limitation; information on the authorized network range, i.e., information on the authorized area, such as cell information; and required latency, bandwidth, and other information.

[0183] Optionally, the second information may include the identifier of the second network and a second identifier. The second identifier is an identifier assigned to the second user by the application layer for obtaining services in the second network. In other words, the second identifier may be the UE's identity identifier in the second network, used to access the second network and obtain services.

[0184] The identification of the second network can be found in the description of the identification of the second network in S701, and will not be repeated here.

[0185] The second identifier can be a temporary identifier assigned by the application layer to the second user for the second network, such as a user identity (user ID). Of course, it can also be other possible temporary identifiers, without restriction. The network element that assigns the second identifier to the second user can be the first network element or other network elements at the application layer, without restriction.

[0186] Optionally, the second information may include the identifier of the application function network element (AF / AS), such as AF ID, IP address, port number; or an identifier used to characterize user information, used to identify the network element information or user information (i.e., the information of the second user) that provides the second information.

[0187] Optionally, the communication method may further include: the first network element sending a second identifier to the first user.

[0188] The first network element assigns a second identifier to the first user and sends the second identifier to the first user through the application layer. Alternatively, the first network element obtains the second identifier assigned to the first user by the application layer and sends the second identifier to the first user through the application layer, so that the first user can subsequently initiate registration and business processes with the second network through the second identifier.

[0189] It can be understood that S701 and S702 have an "AND / OR" execution relationship. That is, S701 and S702 can be executed simultaneously, or either one can be executed at will, without any limitation here. For example, the first network element can send the subscription information of multiple users to the first network and / or the second network respectively, and then the first network and / or the second network will perform authorization operations, which will not be elaborated here.

[0190] The following section details the solutions for S701 and S702, namely Scheme 1 and Scheme 2, based on whether the first network element can identify / determine the user's operator.

[0191] Option 1: The first network element is able to identify / determine the user's operator.

[0192] In one possible implementation, S701 may include: the first network element determining the operator to which the first user belongs, and if the operator to which the first user belongs is the same as the operator providing the first network, or if the operator to which the first user belongs has a roaming agreement with the operator providing the first network, the first network element sending first information to the first network.

[0193] In this embodiment, the first network element can determine the operator information of the first user and maintain information about the first network, networks with roaming agreements with the first network, and networks without roaming agreements with the first network. Thus, the first network element can determine that the operator to which the first user belongs is the same as the operator providing the first network, or that the operator to which the first user belongs has a roaming agreement with the operator providing the first network. In other words, the first user can access the first network and obtain services from the second network within the second network.

[0194] It is understood that Scheme 1 corresponds to Method 1 above, that is, Scheme 1 can refer to the access method in Figure 6(a), which will not be elaborated here.

[0195] Thus, when the first network element faces a first user whose operator is the same as or has a roaming agreement with the operator providing the first network, it sends first information to the first network to indicate the first user's subscription information, so that the first network and the second network can work together to ensure that the first user can normally obtain the localized services of the second network.

[0196] In another possible implementation, S702 may include: the first network element determining the operator to which the second user belongs, and if the operator to which the second user belongs is different from the operator providing the first network, and the operator to which the second user belongs has no roaming agreement with the operator providing the first network, the first network element sending second information to the second network.

[0197] In this embodiment, the first network element can determine the operator information of the second user and maintain information about the first network, networks with roaming agreements with the first network, and networks without roaming agreements with the first network. Thus, the first network element can determine that the operator to which the second user belongs is different from the operator providing the first network, and that the second user's operator has no roaming agreement with the operator providing the first network. In other words, the second user cannot access the first network. Therefore, the first network element sends second information to the second network and obtains services from the second network.

[0198] It is understood that Scheme 2 corresponds to Method 2 mentioned above, that is, Scheme 2 can refer to the access method in Figure 6(b), which will not be elaborated here.

[0199] Thus, when the first network element faces a second user whose operator is different from the operator providing the first network and who has no roaming agreement, it sends second information to the second network to indicate the second user's subscription information. This flexible way of sending subscription information enables the first and second networks to work together to ensure that the second user can normally obtain the localized services of the second network.

[0200] Option 2: The first network element cannot identify / determine the user's operator.

[0201] In one possible implementation, S702 may further include: a first network element receiving indication information from a first network, the indication information indicating that the operator to which the second user belongs is different from the operator providing the first network, and that the second user's operator and the operator providing the first network do not have a roaming agreement. The first network element sends second information to the second network according to the indication information. The indication information may be a single information element or may be represented by a special signaling message.

[0202] The instruction information is used to indicate that the second user's operator is different from the operator providing the first network and that there is no roaming agreement, which implicitly instructs the first network element to redirect the second information to the second network. Alternatively, the instruction information can also be used to instruct the first network element to redirect the second information to the second network, which is an explicit instruction method.

[0203] Optionally, before the first network element receives the instruction information from the first network, the communication method may further include: the first network element sending second information to the first network.

[0204] The first network element does not identify / determine the user's operator and by default sends the second information to the first network. Upon receiving the second information, the first network determines that the second user's operator is different from the operator providing the first network and that there is no roaming agreement. Therefore, the first network sends the aforementioned instruction information to the first network element. It can be understood that if, upon receiving the second information, the first network determines that the second user's operator is the same as the operator providing the first network or that there is a roaming agreement, the first network will not send the aforementioned instruction information to the first network element. Instead, the first network will perform the authorization operation for the second information and, if the authorization is successful, store the second user's subscription information.

[0205] Thus, if the first network element cannot identify / determine the user's operator, it can send the second information directly to the first network. If the second user's operator is different from the operator providing the first network and there is no roaming agreement, it will receive the instruction information from the first network and then send the second information to the second network. This allows the first and second networks to work together to ensure that the second user can normally obtain the localized services of the second network.

[0206] S703, the second network element #1 performs an authorization operation on the first information.

[0207] S703 is an optional step. The second network element #1 is deployed in the first network. For ease of distinction, second network element #1 is used to represent the second network element deployed in the first network, and second network element #2 is used to represent the second network element deployed in the second network, as in S704.

[0208] The second network element #1 is deployed in the first network. The second network element #1 can be a NEF network element or a UDM network element, or other network elements / entities that can realize network openness capabilities or data management capabilities, without limitation. For ease of explanation, the following text will use NEF network elements or UDM network elements for introduction.

[0209] The authorization operation for the first information is performed by the NEF network element deployed in the first network (i.e., the large network), or by the UDM network element deployed in the first network element, or by the cooperation of the UDM network element and the NEF network element deployed in the first network element.

[0210] The authorization operation is used to determine whether the first network element can provide the first information. In other words, the authorization operation is used to determine whether the first network element has the ability to provide the first information, or whether the first network element has the right to use the second network, or whether the first information provided by the first network element is credible. If the second network element #1 determines that the first network element can provide the first information or has the ability to provide the first information, the authorization is successful. If the second network element #1 determines that the first network element cannot provide the first information or does not have the ability to provide the first information, the authorization is unsuccessful.

[0211] The authorization operation of the first network determines whether the first network element can provide the first information, or whether it has the capability to provide the first information. If the second network element determines that the first network element can provide the first information, the authorization is successful. The first information indicates the subscription information requested for access to the second network. The first and second networks can be a large network and a subnet, respectively. In other words, the authorization operation determines whether the first network element can provide the subscription information corresponding to a specific subnet. This achieves authorization operations at the subnet level, rather than the UE level, thus achieving the technical effect of distributed subscription.

[0212] S704, the second network element #2 performs an authorization operation on the second information.

[0213] S704 is an optional step. The second network element #2 is deployed in the second network. The second information includes the identifier of the second network. This authorization operation is used to determine whether the second network is the network where the second network element #2 is deployed, that is, whether it is a local network. The second network element #2 can be a NEF network element, or other network elements / entities that can realize network openness capabilities, without limitation.

[0214] The second network element #2 performs an authorization operation on the second information, such as determining whether the identifier of the second network in the second information matches the identifier of the local network. If they match, the authorization is successful. Then, if the authorization is successful, the second network element #2 sends the second user's subscription information to the third network element. The third network element and the second network element #2 are deployed in the same network, such as both being deployed in the first network. The third network element can be a UDM network element, or other network element / entity capable of data management functions; there are no limitations on this. The third network element stores the second user's subscription information, which can be stored in a list format, in a corresponding / association information format, or in any other possible format; there are no limitations on this.

[0215] The S703 will be described in detail below.

[0216] First, we will introduce the specific implementation of S703 when the second network element #1 is a NEF network element.

[0217] Optionally, S703 may include: the first information includes the identifier of the second network. The second network element #1 obtains the subscription information of the first network element from the third network element, which is deployed in the first network. The second network element determines whether the first network element can provide the first information based on the subscription information of the first network element and the identifier of the second network; if the first network element can provide the first information, the authorization is successful.

[0218] When the second network element #1 is a NEF network element, the third network element can be a UDM network element. In this case, the first information comes from the first network element, such as the NEF network element receiving the first information sent by the AF network element. The subscription information of the first network element can be stored in the third network element, so that the second network element #1 can obtain the subscription information of the first network element from the third network element.

[0219] For example, the AF's contract information (the contract information of the first network element) is shown in List 1 below:

[0220] Table 1:

[0221] The NEF network element determines that the ID1 of the subnet corresponding to AF1 matches the identifier of the subnet (such as the second network mentioned above) in the first information, thus determining that the AF network element can provide the first information, and the authorization is successful. The subnet information, i.e., the subnet ID1, can be a PLMN ID, NID, a special subnet identifier, or any other possible identifier, without specific restrictions.

[0222] AF network element information can also be replaced with user information (owner ID) / enterprise information (enterprise ID) using AF. This subscription information can be indexed by AF network element information (and its alternative information) or by subnet information.

[0223] Optionally, the NEF network element can determine whether the subnet capacity matches the number of users requested to be added. If they do not match, the authorization will fail. For example, if the network has already recorded that AF1 has provided subscription information for 500 UEs, then if AF1 provides subscription information for the 501st UE, the authorization will fail.

[0224] Optionally, the NEF network element can determine whether the location-related information in the UE's subscription information matches the subnet location. If they do not match, authorization will fail. Alternatively, the location-related information in the UE's subscription can be set to the subnet location or its intersection with the subnet location. For example, if the forbidden area / restriction area in the UE's subscription information provided by AF1 fully or partially overlaps with the subnet location, authorization will fail.

[0225] For example, the subscription information of the UE (such as the subscription information of the first user) within the large network (such as the first network mentioned above) maintained by the UDM network element can be key=SUPI, or key=subnet identifier, or key=SUPI+subnet identifier, as shown in Table 2 below:

[0226] Table 2:

[0227] It is understandable that after the NEF network element authorizes the first information, it sends the UE's subscription information in the first information to the UDM network element. The UDM network element stores the UE's subscription information, as shown in Table 2. The subnet identifier contained in the UE's subscription information in Table 2 matches the ID1 of the subnet in Table 1. For example, the subnet identifier contained in the UE's subscription information in Table 2 is the PLMN ID of subnet #1, and the ID1 of the subnet in Table 1 is the NID of subnet #1.

[0228] Subnet identifiers (such as the identifier of the second network mentioned above) can be stored in the UE's subscription information maintained by the UDM network element. For example, in Table 2, subnet identifiers are stored in the subscription information related to AM and SM. The UE's subscription information can be retrieved through the UE's identifier (such as SUPI). Alternatively, the subnet identifier can also be stored separately in the UDM network element and associated with the UE's subscription information, thereby allowing the UE's subscription information to be retrieved through the subnet identifier. This is not limited here.

[0229] It is understood that the contract information of the first network element and the contract information of the first user can be stored in the form of a list, or in the form of corresponding / related information, or in any other possible form, without limitation here.

[0230] After receiving the first information, the second network element #1 determines whether the provider of the first information (i.e., the first network element) has purchased services from the second network. The second network element #1 queries the first network element's subscription information (as shown in Table 1 above) based on the first network element's information (such as the first network element's identifier), and determines the information of the subnet corresponding to the first network element in the subscription information (such as the subnet identifier in Table 1), and whether the subnet information corresponding to the first network element corresponds to the identifier of the second network. The subnet information corresponding to the first network element indicates that the first network element has purchased services from that subnet.

[0231] It should be noted that the first user's contract information in the first information is recorded as the first contract information here, so as to distinguish it from the second contract information (such as partial contract information) of the first user stored in the third network element.

[0232] Optionally, the communication method may further include: if authorization is granted, the second network element #1 sends the second subscription information of the first user to the third network element, wherein the second subscription information is determined based on the first subscription information.

[0233] The second network element #1 determines that the first network element can provide the first information, i.e., authorization is successful. Therefore, the second network element #1 sends the first user's second subscription information to the third network element. The second subscription information is determined based on the first subscription information, such as if the identifier used to identify the first user in the first subscription information and the second subscription information are different.

[0234] Optionally, the first contract information includes the identifier of the second network and the first identifier, and the second contract information includes the identifier of the second network and the third identifier, wherein the third identifier is the identifier converted by the third network element based on the second identifier.

[0235] The third identifier can be a permanent identifier used to identify the first user, such as SUPI, or it can be any other identifier that can be applied to the first network, without restriction.

[0236] The second network element #1 performs an identifier conversion on the first identifier in the first contract information to obtain a third identifier, which is then applicable to the first network.

[0237] The second network element #1 sends the second subscription information of the first user to the third network element so that the third network element can store the second subscription information of the first user.

[0238] The following describes the specific implementation of S703 when the second network element #1 is a UDM network element.

[0239] Optionally, S703 may include: if authorization is granted, the second network element #1 stores the first user's first subscription information.

[0240] The second network element #1 is a UDM network element, which stores the subscription information of the first network element. At this time, the first information comes from the NEF network element. For example, the AF network element (i.e., the first network element) sends the first information to the NEF network element. After the NEF network element performs identifier conversion, it sends the first user's first subscription information to the UDM network element (i.e., the second network element #1). The identifier used to identify the user in the first subscription information can be the converted identifier, such as the first subscription information including the aforementioned third identifier.

[0241] The second network element #1 receives the identifier of the first network element from the NEF network element. Based on the first network element's subscription information and the identifier of the second network element #1 in the first information, it determines whether the first network element can provide the first information. If the first network element can provide the first information, the authorization is successful. If the authorization is successful, the second network element #1 stores the first user's first subscription information. The method by which the UDM network element determines whether the first network element can provide the first information is similar to that of the NEF network element, and will not be elaborated here.

[0242] For example, a UDM network element (such as the second network element #1 mentioned above) receives AF network element (such as the first network element mentioned above) information from a NEF network element, such as the identifier of the AF network element and the identifier of the subnet corresponding to the subnet service purchased by the AF network element, as shown in Table 1 above. The UDM network element determines that the ID1 of the subnet corresponding to AF1 matches the identifier of the subnet (such as the second network mentioned above) in the first information, thereby determining that the AF network element can provide the first information, and the authorization is successful.

[0243] Optionally, the UDM network element can determine whether the subnet capacity matches the number of users requested to be added. If they do not match, the authorization will fail. For example, if the network has already recorded that AF1 has provided subscription information for 500 UEs, then if AF1 provides subscription information for the 501st UE, the authorization will fail.

[0244] Optionally, the UDM network element can determine whether the location-related information in the UE's subscription information matches the subnet location. If they do not match, authorization will fail. Alternatively, the location-related information in the UE's subscription information can be set to the subnet location or its intersection with the subnet location. For example, if the forbidden area / restriction area in the UE's subscription information provided by AF1 fully or partially overlaps with the subnet location, authorization will fail.

[0245] The following describes two scenarios where the first network stores the user's contract information after authorizing the first information, as shown in Scenario 1 and Scenario 2.

[0246] Scenario 1:

[0247] After the first network element sends the first information to the first network, the third network element stores the subscription information of the first user indicated in the first information. The third network element is deployed in the first network. The third network element can be a UDM network element or other possible network elements / entities with data management functions, without restriction.

[0248] The first user's subscription information includes one or more of the following: subscription information related to Access Management Function (AM), subscription information related to Mobility Management Function (MM), subscription information related to Session Management Function (SM), subscription information related to slice selection, subscription information related to Short Messaging Service (SMS), and subscription information related to location.

[0249] It is understandable that in scenario 1, the third network element stores all the subscription information of the first user. When the user subsequently requests to establish a session with the second network, the first network forwards some or all of the subscription information, such as SM-related subscriptions, to the second network so that the UE can obtain services from the second network, such as establishing a session.

[0250] Scenario 2:

[0251] After the first network element sends the first information to the first network, the third network element stores a portion of the subscription information of the first user indicated in the first information. For example, the portion of the subscription information includes at least one of the following: subscription information related to AM, subscription information related to MM, subscription information related to SMS, and subscription information related to location, etc., and sends another portion of the subscription information, such as subscription information related to SM, to the second network, excluding the portion of the subscription information stored by the third network element. The third network element is deployed in the first network.

[0252] It is understandable that in scenario 2, the third network element stores part of the first user's subscription information and sends another part of the subscription information to the second network, such as sending the SM-related subscription information to the second network. The second network stores the SM-related subscription information of the second network so that when the user requests to establish a session with the second network later, the UE can obtain the services of the second network. For example, the second network can directly establish a session based on the stored SM-related subscription information.

[0253] The above describes the workflow of the communication method provided in the embodiments of this application, with reference to Figure 7.

[0254] The following describes in detail the specific process of combining Scheme 1 and Case 1 of the communication method provided in the embodiments of this application with reference to Figure 8.

[0255] Figure 8 is a schematic flowchart of the communication method provided in an embodiment of this application. The flowchart shown in Figure 8 mainly involves the interaction between the AF (such as the first network element mentioned above), the main network (such as the first network mentioned above), and the sub-network (such as the second network mentioned above).

[0256] The main network elements of the large network include NEF1 (as described in the second network element #1 above) and UDM1 (as described in the third network element above). The main network elements of the subnet include NEF2 (as described in the second network element #2 above) and UDM2 (as described in the third network element above).

[0257] Specifically, as shown in Figure 8, the communication method flow is as follows:

[0258] S800, AF obtains the operator information of user #1 and / or user #2.

[0259] After User #1 (as described above, the first user) and / or User #2 (as described above, the second user) purchase Service #1 provided by the subnet through the application layer, the AF can identify the operator information of User #1 and / or User #2 who purchased Service #1.

[0260] S801a, AF determines that the operator to which user #1 belongs is the same as the operator providing the main network, or that there is a roaming agreement.

[0261] AF can maintain information on networks with main networks, networks with main network roaming protocols, and networks without main network roaming protocols. Therefore, based on the operator information of user #1, it can determine whether user #1's operator is the same as the operator providing the main network, or whether a roaming protocol exists.

[0262] S802a, AF sends service parameter #1 to NEF1.

[0263] NEF1 is deployed on the main network. Service parameter #1 can be found in the description of the first information in S701, and will not be repeated here. Service parameter #1 carries the subnet identification information #1, such as PLMN, user #1 external identification information, such as GPIS, and user #1 subscription information, such as slice, area restrictions, latency, and bandwidth.

[0264] S803a, NEF1 performs identifier conversion.

[0265] NEF1 converts the external identifier of user #1 into an internal identifier suitable for the large network, such as converting GPIS to SUPI.

[0266] S804, NEF1 interacts with UDM1 to complete the authorization of service parameter #1.

[0267] Whether NEF1 authorizes AF to provide service #1 can be specifically included as follows: NEF1 sends the identification information of AF and the identification information of subnet #1 to UDM1, and then UDM1 queries whether the AF's subscription information contains the service #1 provided by the subnet purchased by the AF, and whether the subnet identifier in the AF's subscription information corresponds / matches with the subnet identification information #1.

[0268] The authorization process for service parameter #1 by NEF1 and UDM1 can also refer to the authorization process for the first information in S701-S704, which will not be repeated here.

[0269] S805, NEF1 sends user #1's subscription information to UDM1.

[0270] If authorization is granted, NEF1 sends user #1's subscription information to UDM1 so that UDM1 can store user #1's subscription information.

[0271] The contract information for user #1 can be found in the description of the first user's contract information in S701, and will not be repeated here.

[0272] S806, UDM1 stores the subscription information of user #1.

[0273] S801b, AF determined that user #2 belongs to a different operator than the operator providing the main network, and that there is no roaming agreement.

[0274] AF determined, based on the carrier information of user #2, that user #2's carrier is different from the carrier providing the main network, and that there is no roaming agreement.

[0275] AF assigns temporary identification information, such as user ID, to user #2. This temporary identification information is related to the subnet and is a specific identifier for the subnet. The temporary identification information is then sent to user #2 through the application layer.

[0276] The temporary identifier information can be found in the description of the second identifier in S702, and will not be repeated here.

[0277] S802b, AF sends service parameter #2 to NEF2.

[0278] NEF2 is deployed on a subnet. Service parameter #2 can be found in the description of the second information in S702, and will not be repeated here. Service parameter #2 carries the subnet identification information #2, such as PLMN, the temporary identification information of user #2 for this subnet, and the subscription information of user #2, such as slice, area restrictions, latency and bandwidth.

[0279] S803b, NEF2 sends user #2's subscription information to UDM2.

[0280] UDM2 is deployed on the subnet. NEF2 authorizes the service parameter #2 of AF, such as determining whether the identification information #2 of the subnet provided by AF is consistent with the identification of this network (the subnet where NEF2 is deployed). After authorization, NEF2 forwards the subscription information of user #2 to UDM2 deployed on the subnet so that UDM2 can store the subscription information of user #2.

[0281] The subscription information for user #2 can be found in the description of the subscription information for the second user in S702, and will not be repeated here. The authorization process for service parameter #2 by NEF2 can also be found in the authorization process for the second information in S701-S704, and will not be repeated here.

[0282] It is understood that in the above process, S801a-S806 is the authorization process for user #1, and S801b-S803b is the authorization process for user #2. S801a-S806 and S801b-S803b have an "AND / OR" execution relationship. That is, S801a-S806 and S801b-S803b can occur simultaneously, without limitation. For example, the AF can simultaneously distinguish the operator information of multiple users and send the service parameters corresponding to each user to the main network and / or subnet to complete the authorization of the service parameters; this will not be elaborated upon here.

[0283] The following describes in detail the specific process of combining Scheme 1 and Situation 2 of the communication method provided in the embodiments of this application with reference to Figure 9.

[0284] Figure 9 is a schematic flowchart of the communication method provided in an embodiment of this application. The flowchart shown in Figure 9 mainly involves the interaction between the AF (such as the first network element mentioned above), the main network (such as the first network mentioned above), and the sub-network (such as the second network mentioned above).

[0285] The main network elements of the large network include NEF1 (as described in the second network element #1 above) and UDM1 (as described in the third network element above). The main network elements of the subnet include NEF2 (as described in the second network element #2 above) and UDM2 (as described in the third network element above).

[0286] Specifically, as shown in Figure 9, the communication method flow is as follows:

[0287] S900, AF obtains operator information for user #1 and / or user #2.

[0288] S901a, AF determines that the operator to which user #1 belongs is the same as the operator providing the main network, or that there is a roaming agreement.

[0289] S902a, AF sends service parameter #1 to NEF1.

[0290] S903a, NEF1 performs identifier conversion.

[0291] S904, NEF1 interacts with UDM1 to complete the authorization of service parameter #1.

[0292] S905, NEF1 sends user #1's subscription information to UDM1.

[0293] For details on S900-S905, please refer to the specific descriptions of S800-S805, which will not be repeated here.

[0294] S906, UDM1 stores AM-related contract information and MM-related contract information.

[0295] User #1's contract information includes AM-related contract information, MM-related contract information, and SM-related contract information. Here, UDM1 only stores AM-related contract information and MM-related contract information.

[0296] S907, UDM1 sends SM-related contract information to UDM2.

[0297] Subscription information related to the UDM2 storage SM deployed in the subnet.

[0298] S901b, AF determined that user #2 belongs to a different operator than the operator providing the main network, and that there is no roaming agreement.

[0299] S902b, AF sends service parameter #2 to NEF2.

[0300] S903b, NEF2 sends user #2's subscription information to UDM2.

[0301] For details on S901b-S903b, please refer to the specific descriptions of S801b-S803b, which will not be repeated here.

[0302] It can be understood that S901a-S907 and S901b-S903b in the above process have an "AND / OR" execution relationship. The difference between this process and the process corresponding to Figure 8 is the difference between S806 and S906-S907. In this process, when the main network receives the subscription information of user #1, it only retains the subscription information related to AM and MM of the subnet, and sends the subscription information related to SM of the subnet to the subnet, where the subnet stores the subscription information related to SM of the subnet. In the process corresponding to Figure 8, when the main network receives the subscription information of user #1, it retains all the subscription information of user #1.

[0303] The following describes in detail the specific process of combining Scheme 2 and Case 1 of the communication method provided in the embodiments of this application with reference to Figure 10.

[0304] Figure 10 is a schematic flowchart of the communication method provided in an embodiment of this application. The flowchart shown in Figure 10 mainly involves the interaction between the AF (such as the first network element mentioned above), the main network (such as the first network mentioned above), and the sub-network (such as the second network mentioned above).

[0305] The main network elements of the large network include NEF1 (as described in the second network element #1 above) and UDM1 (as described in the third network element above). The main network elements of the subnet include NEF2 (as described in the second network element #2 above) and UDM2 (as described in the third network element above).

[0306] Specifically, as shown in Figure 10, the communication method flow is as follows:

[0307] S1001, AF sends service parameters to NEF1.

[0308] Since the AF does not recognize the user's carrier information and cannot determine whether the user's carrier is the same as the carrier providing the main network, or whether there is a roaming agreement, the AF sends service parameters to the main network by default. The service parameters carry the subnet identification information, such as PLMN, the user's temporary identification information for that subnet, and the user's subscription information, such as DNN / slice information, area restrictions, latency, and bandwidth.

[0309] The service parameters can be found in the description of the first information in S701, and will not be repeated here.

[0310] S1002, NEF1 performs identifier conversion.

[0311] S1003a, when the user's operator is the same as the operator providing the main network, or when there is a roaming agreement, NEF1 interacts with UDM1 to complete the authorization of service parameters.

[0312] S1004a, NEF1 sends the user's subscription information to UDM1.

[0313] Once the service parameters are authorized, NEF1 sends the user's subscription information to UDM1.

[0314] S1005a, UDM1 stores user subscription information.

[0315] S1003b: When the user's operator is different from the operator providing the main network and there is no roaming agreement, NEF1 sends an instruction message to AF.

[0316] The indication information is used to indicate that the user's operator is different from the operator providing the main network and there is no roaming agreement. It implicitly instructs the AF to redirect the service parameters to NEF2 deployed in the subnet, or directly instructs the AF to redirect the service parameters to NEF2 deployed in the subnet through explicit indication information, without limitation.

[0317] The instructions can also be found in the description of instructions in S702, which will not be repeated here.

[0318] S1004b, AF sends service parameters to NEF2.

[0319] AF assigns temporary identification information to users, such as user ID. This temporary identification information is related to the subnet and is a specific identifier for the subnet. The temporary identification information is then sent to the user through the application layer.

[0320] S1005b, NEF2 forwards the user's subscription information to UDM2.

[0321] After receiving the service parameters, NEF2 authorizes the service parameters, such as determining whether the identification information of the subnet provided by AF is consistent with the identification of this network. If the authorization is successful, it forwards the user's subscription information to UDM2 deployed in the subnet so that UDM2 can store the user's subscription information.

[0322] It is understandable that S1003a-S1005a and S1003b-S1005b in the above process have an "AND / OR" execution relationship. That is to say, S1003a-S1005a and S1003b-S1005b can occur simultaneously. In this case, the users in S1003a-S1005a and the users in S1003b-S1005b can be different users, which is not limited here. For example, AF sends the service parameters corresponding to multiple users to the large network NEF1. The large network determines whether the operator of each user is the same as the operator providing its own network or whether there is a roaming agreement, thereby deciding whether to complete the authorization of the service parameters by its own network. This will not be elaborated here.

[0323] The following describes in detail the specific process of combining Scheme 2 and Case 2 of the communication method provided in the embodiments of this application with reference to Figure 11.

[0324] Figure 11 is a schematic flowchart of the communication method provided in an embodiment of this application. The flowchart shown in Figure 11 mainly involves the interaction between the AF (such as the first network element mentioned above), the main network (such as the first network mentioned above), and the sub-network (such as the second network mentioned above).

[0325] The main network elements of the large network include NEF1 (as described in the second network element #1 above) and UDM1 (as described in the third network element above). The main network elements of the subnet include NEF2 (as described in the second network element #2 above) and UDM2 (as described in the third network element above).

[0326] Specifically, as shown in Figure 11, the communication method flow is as follows:

[0327] S1101, AF sends service parameters to NEF1.

[0328] S1102, NEF1 performs identifier conversion.

[0329] S1103a, when the user's operator is the same as the operator providing the main network, or when there is a roaming agreement, NEF1 interacts with UDM1 to complete the authorization of service parameters.

[0330] S1104a, NEF1 sends the user's subscription information to UDM1.

[0331] For details on S1101-S1104a, please refer to the specific descriptions of S1001-S1004a. Further details will not be provided here.

[0332] S1105a, UDM1 stores AM-related contract information and MM-related contract information.

[0333] S1106, UDM1 sends SM-related contract information to NEF2.

[0334] For S1105a-S1006, please refer to the specific descriptions of S906-S907, which will not be repeated here.

[0335] S1103b: When the user's operator is different from the operator providing the main network and there is no roaming agreement, NEF1 sends an instruction message to AF.

[0336] S1104b, AF sends service parameters to NEF2.

[0337] S1105b, NEF2 forwards the user's subscription information to UDM2.

[0338] For details on S1103b-S1105b, please refer to the specific descriptions of S1003b-S1005b; further details will not be provided here.

[0339] It is understandable that S1103a-S1106 and S1103b-S1105b in the above process have an "AND / OR" execution relationship. That is, S1103a-S1106 and S1103b-S1105b can occur simultaneously. In this case, the users in S1103a-S1106 and the users in S1103b-S1105b can be different users, which is not limited here. The difference between this process and the process corresponding to Figure 10 is the difference between S1006 and S1105a-S1106. In this process, when the main network receives the user's subscription information, it only retains the subscription information related to AM and MM of the subnet, and sends the subscription information related to SM of the subnet to the subnet, where the subnet stores the subscription information related to SM. In the process corresponding to Figure 10, when the main network receives the user's subscription information, it retains all of the user's subscription information.

[0340] Based on the above process of authorizing information at the subnet level, the following section describes the user registration and service acquisition process in detail, specifically in Example 1 where the user's operator is the same as or has a roaming agreement with the operator providing the main network, and Example 2 where the user's operator is the same as or has a roaming agreement with the operator providing the main network.

[0341] Example 1:

[0342] Figure 12 is a schematic diagram of the registration and service acquisition process provided in an embodiment of this application. The process shown in Figure 12 mainly involves the interaction between the UE (i.e., the user), the RAN, the main network (such as the first network mentioned above), and the sub-network (such as the second network mentioned above).

[0343] The main network elements of the large network include UDM1 (as mentioned in the third network element above), AM1, and MM. The main network elements of the subnet include UDM2 (as mentioned in the third network element above), AM2, SM, and UPF.

[0344] Specifically, as shown in Figure 12, the communication method flow is as follows:

[0345] S1200, UDM1 obtains the UE's subnet temporary subscription information.

[0346] S1201, the UE sends an access network (AN) message to the RAN.

[0347] The UE's operator is the same as or has a roaming agreement with the operator providing the main network. The UE purchases services / services from the subnet and initiates a registration update process.

[0348] The AN message can contain AN parameters and a registration request message. The registration request message can be used by the UE to request registration with a subnet (such as the second network mentioned above). The AN parameters indicate the identifier of the PLMN currently selected by the UE (selected PLMN ID), that is, the network the UE wants to register with, such as the subnet identifier. The registration request message includes the UE's identifier, such as SUCI. The AN message can also contain a globally unique AMF identifier (GUAMI) or an SAE-temporary mobile subscriber identifier (S-TMSI).

[0349] S1202, RAN sends a registration request message to AM1.

[0350] The registration request message carries the UE's identifier.

[0351] S1203, AM1 obtains the UE's subscription information from UDM1.

[0352] Since the UDM1 of the main network stores the UE's subscription information, such as the user's subscription information in the authorization process described above, AM1 obtains the UE's subscription information from UDM1. The UE's subscription information includes authorized subnet service / service information, such as slicing and / or DNN information.

[0353] S1204, AM1 sends a registration acceptance message to the UE via the RAN.

[0354] The above is the UE registration process. The following describes the UE's service acquisition process.

[0355] S1205, the UE sends a session establishment request message to AM1 through the RAN.

[0356] The Session Establishment Request message is used to request the establishment of a session. The Session Establishment Request message can carry the UE's identifier, such as SUPI, and information about the services requested by the UE, such as NSSAI and / or DNN information.

[0357] S1206, AM1 determines that the session should be established in the subnet.

[0358] AM1 determines, based on the information of the service requested by the UE, such as NSSAI and / or DNN information, and the authorized subnet service information, such as the information of the service requested by the UE being any service in the authorized subnet services, that the session requested by the session request message should be established in the subnet.

[0359] S1207, AM1 sends a session establishment request message and SM subscription information to AM2.

[0360] Session establishment request messages may carry SUPI, NSSAI, and / or DNN information. SM subscription information may be the UE's subscription information related to subnet session management functions.

[0361] The subscription information of the UE related to the subnet session management function can be referred to the subscription information related to the session management function (SM) of the second network in the above situation 1, and will not be repeated here.

[0362] S1208, AM2 sends a session establishment request message to SM.

[0363] The Session Establishment Request message is used to request the establishment of a PDU session. The Session Establishment Request message can reuse existing messages for transmission, such as the PDU Session Establishment Request (Nnef_PDUSession_CreateSMContext Request) message, or it can be a newly defined message, without any restrictions.

[0364] S1209, SM sends a session establishment response message to AM2.

[0365] The session establishment response message is used to indicate that the session has been successfully established. The session establishment response message can reuse existing messages to implement transmission, such as the PDU session establishment response (Nnef_PDUSession_CreateSMContext response) message, or it can be a newly defined message, without any restrictions.

[0366] S1210, SM and UPF exchange N4 messages.

[0367] S1211, SM sends N2 message #1 to RAN via AM2.

[0368] N2 message #1 can reuse existing messages for transmission, such as N2 session request messages, or it can be a newly defined message; there are no restrictions on this. N2 session request messages can include SM information, such as the PDU session ID.

[0369] S1212, RAN and UE interact with PDU session establishment and receive message.

[0370] S1213, RAN sends N2 message #2 to SM.

[0371] N2 message #2 can reuse existing messages for transmission, such as N2 session response messages, or it can be a newly defined message, without any restrictions.

[0372] Example 2:

[0373] Figure 13 is a schematic diagram of the registration and service acquisition process provided in an embodiment of this application. The process shown in Figure 13 mainly involves the interaction between the UE (i.e., the user), the RAN, and the subnet (such as the second network mentioned above).

[0374] The network elements of a subnet mainly include UDM (such as the third network element mentioned above), AM, SM and UPF.

[0375] Specifically, as shown in Figure 13, the communication method flow is as follows:

[0376] S1300, the UE initiates the registration update process.

[0377] The UE's operator is different from the operator providing the main network and there is no roaming agreement. The UE purchases services / services from the subnet and initiates a registration update process.

[0378] S1301, the UE sends an AN message to the RAN.

[0379] The AN message can contain AN parameters and a registration request message. The registration request message can be used by the UE to request registration with a subnet (such as the second network mentioned above). The AN parameters indicate the identifier of the PLMN currently selected by the UE (selected PLMN ID), that is, the network the UE wants to register with, such as the identifier of the subnet. The registration request message includes the UE's identifier, such as SUCI, and a temporary identifier assigned to the UE by the application layer, such as user id.

[0380] S1302, RAN sends a registration request message to AM.

[0381] The registration request message carries the UE's identifier and the UE's temporary identifier.

[0382] S1303, AM obtains UE's AM contract information from UDM.

[0383] Since the UDM of the subnet stores the UE's subscription information, the AM obtains the UE's AM subscription information from the UDM based on the UE's temporary identifier. This AM subscription information may be subscription information related to the access management function (AM) of the subnet.

[0384] S1304, AM sends a registration acceptance message to UE via RAN.

[0385] The above is the UE registration process. The following describes the UE's service acquisition process.

[0386] S1305, the UE sends a session establishment request message to the AM through the RAN.

[0387] The Session Establishment Request message is used to request the establishment of a session. The Session Establishment Request message may carry a temporary identifier for the UE, as well as information about the services requested by the UE, such as NSSAI and / or DNN information.

[0388] S1306, AM sends a session establishment request message to SM.

[0389] Session establishment request messages can carry SUPI, NSSAI, and / or DNN information. They are used to request the establishment of a PDU session. Session establishment request messages can reuse existing messages for transmission, such as the PDU session establishment request (Nnef_PDUSession_CreateSMContext Request) message, or they can be newly defined messages; there are no restrictions on this.

[0390] S1307, SM obtains UE's SM contract information from UDM.

[0391] Based on the UE's temporary identifier, the SM obtains the UE's SM subscription information from the UDM. The SM subscription information can be the UE's subscription information related to the subnet session management function.

[0392] S1308, UDM sends a session establishment response message to SM.

[0393] The session establishment response message is used to indicate that the session has been successfully established. The session establishment response message can reuse existing messages to implement transmission, such as the PDU session establishment response (Nnef_PDUSession_CreateSMContext response) message, or it can be a newly defined message, without any restrictions.

[0394] S1309, UDM and UPF exchange N4 messages.

[0395] S1310, UDM sends N2 message #1 to RAN via SM.

[0396] N2 message #1 can reuse existing messages for transmission, such as N2 session request messages, or it can be a newly defined message; there are no restrictions on this. N2 session request messages can include SM information, such as the PDU session ID.

[0397] S1311, RAN and UE interact with PDU session establishment and receive message.

[0398] S1312, RAN sends N2 message #2 to UDM via SM.

[0399] N2 message #2 can reuse existing messages for transmission, such as N2 session response messages, or it can be a newly defined message, without any restrictions.

[0400] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 7-13. The communication apparatus used to perform the communication method provided by the embodiments of this application is described in detail below with reference to Figures 14 and 15.

[0401] For example, FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in FIG14, the communication device 1400 includes a processing module 1401 and a transceiver module 1402. For ease of explanation, FIG14 only shows the main components of the communication device.

[0402] In some embodiments, the communication device 1400 can be used to implement the functions of the terminal device in the method shown in FIG7. For example, the processing module 1402 is used to implement the transmitting and receiving functions of the terminal device, and the processing module 1401 is used to implement the processing functions of the terminal device other than the transmitting and receiving functions.

[0403] In other embodiments, the communication device 1400 can be used to implement the functions of the authentication function network element (such as the first authentication function network element) in the method shown in FIG7. For example, the processing module 1402 is used to implement the transmit and receive functions of the authentication function network element, and the processing module 1401 is used to implement the processing functions of the authentication function network element other than the transmit and receive functions.

[0404] In some embodiments, the communication device 1400 can be used to implement the functions of the access management network element (such as the first access management network element or the second access management network element) in the method shown in FIG7. For example, the processing module 1402 is used to implement the transmit and receive functions of the access management network element, and the processing module 1401 is used to implement the processing functions of the access management network element other than the transmit and receive functions.

[0405] Optionally, the communication device 1400 may further include a storage module (not shown in FIG. 14) that stores programs or instructions. When the processing module 1401 executes the program or instructions, the communication device 1400 can perform the communication method shown in FIG. 7.

[0406] It should be understood that the processing module 1401 involved in the communication device 1400 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 1402 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0407] It is understood that the communication device 1400 may be a terminal device or a network device, or it may be executed by a component of the terminal device or network device (such as a processor, chip, or chip system, etc.), or it may be a logical node, logical module, or software that can realize all or part of the functions of the terminal device or network device. This application does not limit it in this regard.

[0408] For example, Figure 15 is a second schematic diagram of the structure of a communication device provided in an embodiment of this application. This communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly that can be disposed in a terminal device or network device. As shown in Figure 15, the communication device 1500 may include a processor 1501. Optionally, the communication device 1500 may also include a memory 1502 and / or a transceiver 1503. The processor 1501 is coupled to the memory 1502 and the transceiver 1503, for example, they can be connected via a communication bus.

[0409] The following is a detailed description of each component of the communication device 1500 with reference to Figure 15:

[0410] The processor 1501 is the control center of the communication device 1500. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1501 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0411] Optionally, the processor 1501 can perform various functions of the communication device 1500 by running or executing software programs stored in the memory 1502 and calling data stored in the memory 1502.

[0412] In a specific implementation, as one embodiment, processor 1501 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG15, for executing the communication method shown in FIG7 in the embodiment of this application.

[0413] In a specific implementation, as one embodiment, the communication device 1500 may also include multiple processors, such as processors 1501 and 1504 shown in FIG. 15. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0414] The memory 1502 is used to store the software program that executes the solution of this application, and is controlled by the processor 1501 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0415] Optionally, the memory 1502 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1502 may be integrated with the processor 1501 or may exist independently and be coupled to the processor 1501 through the interface circuit of the communication device 1500 (not shown in FIG. 15). This application embodiment does not specifically limit this.

[0416] Transceiver 1503 is used for communication with other communication devices. For example, if communication device 1500 is a terminal device, transceiver 1503 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1500 is a network device, transceiver 1503 can be used to communicate with a terminal device or with another network device.

[0417] Optionally, transceiver 1503 may include a receiver and a transmitter (not shown separately in Figure 15). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0418] Optionally, the transceiver 1503 can be integrated with the processor 1501 or exist independently and be coupled to the processor 1501 through the interface circuit of the communication device 1500 (not shown in FIG15). This application embodiment does not specifically limit this.

[0419] It should be noted that the structure of the communication device 1500 shown in Figure 15 does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0420] Furthermore, the technical effects of the communication device 1500 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0421] It should be understood that the processor in the embodiments of this application can be a CPU, but it can also be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0422] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0423] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0424] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0425] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0426] It should be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0427] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0428] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0429] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0430] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0431] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0432] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0433] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first network element sends first information to the first network. The first information is used to indicate the subscription information of the first user, and the first user is the user who requests access to the second network. And / or, The first network element sends second information to the second network. The second information is used to indicate the subscription information of the second user, who is the user requesting access to the second network. The second network and the first network are provided by the same operator, and the first network and a majority of the second networks share some network elements.

2. The method according to claim 1, characterized in that, The first network element sends first information to the first network, including: The first network element determines the operator to which the first user belongs; If the operator to which the first user belongs is the same as the operator providing the first network, or if the operator to which the first user belongs has a roaming agreement with the operator providing the first network, the first network element sends the first information to the first network.

3. The method according to claim 1 or 2, characterized in that, The first network element sends second information to the second network, including: The first network element determines the operator to which the second user belongs; If the operator to which the second user belongs is different from the operator providing the first network, and the operator to which the second user belongs has no roaming agreement with the operator providing the first network, the first network element sends the second information to the second network.

4. The method according to any one of claims 1 to 3, characterized in that, The first information includes the identifier of the second network and a first identifier, wherein the first identifier is a permanent identifier representing the first user.

5. The method according to any one of claims 1 to 4, characterized in that, The second information includes the identifier of the second network and a second identifier, the second identifier being an identifier assigned to the second user by the application layer.

6. The method according to claim 5, characterized in that, The method further includes: The first network element sends the second identifier to the first user.

7. The method according to claim 1, characterized in that, The first network element sends second information to the second network, which also includes: The first network element receives indication information from the first network, the indication information being used to indicate that the operator to which the second user belongs is different from the operator providing the first network, and that the operator to which the second user belongs has no roaming agreement with the operator providing the first network; The first network element sends the second information to the second network according to the instruction information.

8. The method according to claim 7, characterized in that, Before the first network element receives the indication information from the first network, the method further includes: The first network element sends the second information to the first network.

9. A communication method, characterized in that, include: The second network element receives the first information, which is used to indicate the first subscription information of the first user. The first user is a user requesting access to the second network. The first information is provided by the first network element. The second network element performs an authorization operation on the first information, and the authorization operation is used to determine whether the first network element can provide the first information; The second network element is deployed in the first network, and the second network and the first network are provided by the same operator. The first network and a majority of the second networks share some network elements.

10. The method according to claim 9, characterized in that, The first information includes the identifier of the second network; The second network element performs an authorization operation on the first information, including: The second network element obtains the subscription information of the first network element from the third network element, wherein the third network element is deployed in the first network; The second network element determines whether the first network element can provide the first information based on the first network element's subscription information and the identifier of the second network; if the first network element can provide the first information, the authorization is successful.

11. The method according to claim 10, characterized in that, The method further includes: If authorization is granted, the second network element sends the second subscription information of the first user to the third network element, and the second subscription information is determined based on the first subscription information.

12. The method according to claim 11, characterized in that, The first subscription information includes the identifier of the second network and a first identifier, wherein the first identifier is a permanent identifier representing the first user; the second subscription information includes the identifier of the second network and a third identifier, wherein the third identifier is derived from the second identifier.

13. The method according to claim 9, characterized in that, The second network element performs an authorization operation on the first information, including: If authorization is granted, the second network element stores the first user's first subscription information.

14. A communication method, characterized in that, include: The second network element receives second information from the first network element. The second information is used to indicate the subscription information of the second user, who is a user requesting access to the second network. The second information includes the identifier of the second network. The second network element performs an authorization operation on the second information, and the authorization operation is used to determine whether the second network is a network in which the second network element is deployed; If authorization is granted, the second network element sends the second user's subscription information to the third network element, wherein the third network element and the second network element are deployed in the same network.

15. A communication method, characterized in that, include: The third network element receives the first information, wherein the third network element is deployed in the first network, and the first information indicates the subscription information of the first user, the first user being the user requesting access to the second network; The third network element sends the subscription information related to the session management function from the first user's subscription information to the second network; The second network and the first network are provided by the same operator, and the first network and a majority of the second networks share some network elements.

16. A communication device, characterized in that, The apparatus includes: a module for performing the method as described in any one of claims 1-8, or a module for performing the method as described in any one of claims 9-13, or a module for performing the method as described in claim 14, or a module for performing the method as described in claim 15.

17. A communication device, characterized in that, The communication device includes a processing unit and a storage unit; the storage unit is used to store computer instructions, which, when executed by the processing unit, cause the method as described in any one of claims 1-8 to be executed, or cause the method as described in any one of claims 9-13 to be executed, or cause the method as described in claim 14 to be executed, or cause the method as described in claim 15 to be executed.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1-8, or the method as claimed in any one of claims 9-13, or the method as claimed in claim 14, or the method as claimed in claim 15.

19. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a computer, cause the method of any one of claims 1-8 to be performed, or the method of any one of claims 9-13 to be performed, or the method of claim 14 to be performed, or the method of claim 15 to be performed.

Images