CN117014946A - Communication method and device - Google Patents

Abstract

The embodiment of the application provides a communication method and a communication device. The method comprises the following steps: the first equipment acquires the first information and determines whether the personal internet of things element PEGC equipment with the gateway function can join the personal internet of things PIN according to the first information. According to the method disclosed by the application, by newly defining the first information (such AS the home network information of the personal Internet of things element PEMC with the management function and the home network information of the PEGC, the position information, the time information, the quantity information and the like of the PIN) and judging whether the PEGC can join the PIN or not by the first equipment (such AS P-NF, PEMC, PIN AF or PIN AS) according to the first information, the implementation mode can realize a more standardized PIN management flow and ensure an orderly network operation environment.

Description

Communication method and device

The present application claims priority from the chinese patent application filed at 2022, 05-06, filed with the chinese national intellectual property agency, application number 202210488294.1, entitled "communication method and apparatus", the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications, and more particularly, to a communication method and apparatus.

Background

To meet and enrich the increasing network demands, the mobile data traffic is effectively coping with the explosive mobile data traffic growth in the future, and the mobile communication network system is continuously developed and improved to support the mass equipment connection and various new services.

Among them, the personal internet of things (personal IoT networks, PIN) is widely concerned and applied, and the creation and management of the PIN are particularly important. For example, a PIN element (PIN) is registered or unregistered on the core network device. Alternatively, the PIN is registered or unregistered on a PIN application server (application server, AS), and a user context in the PIN is maintained, or the like.

However, there may be a problem of management non-standardization when the PIN joins the PIN at present, thereby causing deterioration of the network operating environment.

Disclosure of Invention

The application provides a communication method and a communication device, which can realize more standardized management flows of network equipment (such as PEGC and AUN 3) and ensure orderly network operation environments.

In a first aspect, a communication method is provided, which may be performed by a first device, or may also be performed by a chip or circuit for the first device, which is not limited by the present application. For convenience of description, an example will be described below as being executed by the first device.

The method comprises the following steps: the first equipment acquires first information; the first device determines from the first information whether a personal internet of things element (PIN elements with gateway capability, PEGC) having a gateway function can join the personal internet of things PIN.

According to the scheme provided by the application, by newly defining the first information (namely, the limit condition of the PEGC to access the PIN), the first equipment (such AS P-NF, PEMC, PIN AF or PIN AS) judges whether the PEGC can join the PIN according to the first information, and the implementation mode can realize a more standardized PIN management flow and ensure an orderly network operation environment.

With reference to the first aspect, in certain implementations of the first aspect, the first information includes one or more of: home network information (e.g., home public land mobile network (home public land mobile network, HPLMN)) of the personal internet of things element PEMC having a management function and home network information of the PEGC; or PIN location information; or time information of the PIN; or PIN quantity information.

With reference to the first aspect, in certain implementations of the first aspect, home network information of the PEMC is used to indicate a home network of the PEMC, home network information of the PEGC is used to indicate a home network of the PEGC, location information of the PIN is used to indicate a location where the PIN is allowed to join, time information of the PIN is used to indicate a time when the PIN is allowed to join, and number information of the PIN is used to indicate a number of personal internet of things elements PINs that the PIN supports joining.

With reference to the first aspect, in certain implementations of the first aspect, when the first information includes information indicating a home network of the PEMC, the home network information of the PEMC includes one or more of: identification information of the PIN, context information of the PIN, identification information of the PEMC, or identification information of the home network of the PEMC. When the first information includes information indicating a home network of the PEGC, the home network information of the PEGC includes one or more of: identification information of the PIN, context information of the PIN, identification information of the PEGC, or identification information of the home network of the PEGC.

Based on the above-mentioned scheme, the home network information of the PEGC may not be unique in expression, and may be determined by PLMN1ID of the PEGC, or may be carried by PEGC identification information (for example, PEGC ID), for example, PLMN1ID may be included in PEGC ID, which is not particularly limited in the present application. The home network information of PEMCs is embodied in a similar manner.

With reference to the first aspect, in certain implementation manners of the first aspect, the determining, by the first device, whether the PEGC can join the PIN according to the first information includes: when the home network of the PEGC is the same as the home network of the PEMC, the first device determines that the PEGC is capable of joining the PIN; when the home network of the PEGC is different from the home network of the PEMC, the first device determines that the PEGC cannot join the PIN.

Based on the scheme, the implementation method can avoid roaming caused by the existence of PEGC and PEMC of different operators in the same PIN, realize more standardized PIN management flow and ensure orderly network operation environment.

With reference to the first aspect, in certain implementations of the first aspect, the location information of the PIN includes one or more of: a geographic location; a network identification code (network identification, NID); tracking area identity (tracking area identity, TAI); cell identification; network selection group identity (group identifier for network selection, GIN); cell access group (cell access group, CAG) identity; slicing information; data network name information; coordinate value information; or longitude and latitude information.

With reference to the first aspect, in certain implementation manners of the first aspect, the determining, by the first device, whether the PEGC can join the PIN according to the first information includes: the first device determines the position of the PEGC; when the position of the PEGC is located at the position indicated by the position information, the first device determines that the PEGC can join in the PIN; when the location of the PEGC is outside the location indicated by the location information, the first device determines that the PEGC is not joinable to the PIN.

Based on the scheme, the implementation mode can avoid the PEGC access of the position where the PIN is not covered, standardizes the mode of adding the PIN to the PINE at the current stage, namely realizes a more standardized PIN management flow and ensures an orderly network operation environment.

With reference to the first aspect, in certain implementations of the first aspect, the time information of the PIN includes one or more of: start time and end time; or, duration.

With reference to the first aspect, in certain implementation manners of the first aspect, the determining, by the first device, whether the PEGC can join the PIN according to the first information includes: the first device determines the time for the PEGC to join the PIN; when the time of adding the PIN by the PEGC belongs to the time indicated by the time information, the first device determines that the PIN can be added by the PEGC; when the PEGC addition time does not belong to the time indicated by the time information, the first device determines that the PEGC cannot add the PIN.

Based on the scheme, the implementation mode can avoid PEGC access when the PIN is overtime, standardizes the mode of adding the PIN to the PINE at the current stage, namely realizes a more standardized PIN management flow and ensures an orderly network operation environment.

With reference to the first aspect, in certain implementations of the first aspect, the PIN quantity information includes one or more of: maximum number of PINs; maximum number of PEGCs; alternatively, the maximum number of PEMCs.

With reference to the first aspect, in certain implementation manners of the first aspect, the determining, by the first device, whether the PEGC can join the PIN according to the first information includes: the first device determines the amount of PINs that have joined the PIN; when the number of PINs which have been added with the PINs is smaller than the number indicated by the number information, the first device determines that the PEGC can access the PINs; when the number of PINs to which PINs have been added is greater than or equal to the number indicated by the number information, the first device determines that the PEGC cannot access the PINs.

Based on the scheme, the implementation mode can avoid PEGC access when PINE in the PIN is overloaded, standardizes the mode of adding PINE in the current stage, namely realizes a more standardized PIN management flow and ensures an orderly network operation environment.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is a core network device (e.g., P-NF), the first device acquires first information, including: the first device receives home network information of the PEMC and home network information of the PEGC from the PEMC, the application function device, the unified data management device, or the unified data repository device.

With reference to the first aspect, in some implementations of the first aspect, when the first device is a core network device (e.g., P-NF), the first device obtains first information, further including: the first device locally pre-configures one or more of time information of the PIN, number information of the PIN or position information of the PIN, namely, the first device can locally acquire one or more of the time information of the PIN, the number information of the PIN or the position information of the PIN; alternatively, the first device receives one or more of time information of the PIN, number information of the PIN, or location information of the PIN from the application function device, the unified data management device, or the unified data repository device.

With reference to the first aspect, in some implementations of the first aspect, when the first device is a core network device, the first device determines whether the PIN supports roaming according to policy information; in the event that the PIN does not support roaming, the first device determines whether the home network of the PEMC is the same as the home network of the PEGC.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is a core network device, policy information is locally preconfigured by the first device; alternatively, the first device receives policy information from a policy control device, a unified data store device, or a unified data management device.

Optionally, in the case that the PIN does not support roaming, the first device sends indication information to the PEMC, for instructing the PEMC to further determine whether the home network of the PEGC is the same as the home network of the PEMC.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is a PEMC, the first device acquires first information, including: the first device receives one or more of time information of PIN, quantity information of PIN or position information of PIN from core network device; alternatively, the first device locally configures one or more of time information of the PIN, number information of the PIN, or location information of the PIN in advance, that is, the first device may locally acquire one or more of time information of the PIN, number information of the PIN, or location information of the PIN.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is a PEMC, the first device acquires first information, and further includes: the PEMC sends a connection request message to the PEGC, wherein the connection request message is used for requesting to establish connection with the PEGC; the PEMC receives a connection response message from the PEGC, the connection response message including home network information of the PEGC.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is an application function device or an application server, the first device acquires first information, including: the first device locally pre-configures one or more of time information of the PINs, number information of the PINs, or location information of the PINs, i.e. the first device may locally obtain one or more of time information of the PINs, number information of the PINs, or location information of the PINs.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is an application function device or an application server, the first device acquires first information, further includes: the first device receives home network information of the PEMC from the PEMC and receives home network information of the PEGC from the PEGC.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is a core network device, the determining, by the first device, a location of the PEGC includes: the first device receives position information of the PEGC from the PEMC, the unified data management device or the unified data storage library device; the first device determines the position of the PEGC according to the position information of the PEGC.

With reference to the first aspect, in certain implementations of the first aspect, when the first device is a PEMC, the first device determines a location of the PEGC, including: the method comprises the steps that a first device sends an inquiry request message to PEMC, wherein the inquiry request message is used for requesting to acquire position information of PEGC; the method comprises the steps that a first device receives PEGC position information from the PEGC; and the first device determines the position of the PEGC according to the position information of the PEGC.

With reference to the first aspect, in certain implementation manners of the first aspect, when the first device is an application function device or an application server, determining a location of the PEGC by the first device includes: the method comprises the steps that a first device receives PEGC position information from the PEGC; the first device determines the position of the PEGC according to the position information of the PEGC.

In a second aspect, there is provided a communication device comprising: the processing unit is used for acquiring first information; and the processing unit is also used for determining whether the PEGC can join the PIN according to the first information.

With reference to the second aspect, in certain implementations of the second aspect, the first information includes home network information of one or more of the following PEMCs and home network information of PEGCs; or PIN location information; or time information of the PIN; or PIN quantity information.

With reference to the second aspect, in certain implementations of the second aspect, home network information of the PEMC is used to indicate a home network of the PEMC, home network information of the PEGC is used to indicate a home network of the PEGC, location information of the PIN is used to indicate a location where the PIN is allowed to join, time information of the PIN is used to indicate a time when the PIN is allowed to join, and number information of the PINs is used to indicate a number of PINs that the PIN supports joining.

With reference to the second aspect, in certain implementations of the second aspect, when the first information includes information indicating a home network of the PEGC, the home network information of the PEGC includes one or more of: identification information of the PIN, context information of the PIN, identification information of the PEGC, or identification information of the home network of the PEGC. When the first information includes information indicating a home network of the PEMC, the home network information of the PEMC includes one or more of: identification information of the PIN, context information of the PIN, identification information of the PEMC, or identification information of the home network of the PEMC.

With reference to the second aspect, in certain implementations of the second aspect, the processing unit is further configured to determine that the PEGC is capable of joining the PIN when a home network of the PEGC is the same as a home network of the PEMC; and the processing unit is also used for determining that the PEGC can not join the PIN when the home network of the PEGC is different from the home network of the PEMC.

With reference to the second aspect, in certain implementations of the second aspect, the location information of the PIN includes one or more of: a geographic location; a network identification code NID; tracking area identification TAI; cell identification; a network selection group identification GIN; a Cell Access Group (CAG) identifier; slicing information; data network name information; coordinate value information; or longitude and latitude information.

With reference to the second aspect, in certain implementations of the second aspect, the processing unit is further configured to determine a location of the PEGC, and determine that the PEGC is capable of adding the PIN when the location of the PEGC is located at the location indicated by the location information; when the position of the PEGC is located outside the position indicated by the position information, it is determined that the PEGC cannot join the PIN.

With reference to the second aspect, in certain implementations of the second aspect, the time information of the PIN includes one or more of: start time and end time; or, duration.

With reference to the second aspect, in certain implementations of the second aspect, the processing unit is further configured to determine a time when the PEGC joins the PIN, and determine that the PEGC is able to join the PIN when the time when the PEGC joins the PIN belongs to the time indicated by the time information; when the time at which the PEGC added the PIN does not belong to the time indicated by the time information, it is determined that the PEGC cannot add the PIN.

With reference to the second aspect, in certain implementations of the second aspect, the PIN quantity information includes one or more of: maximum number of PINs; maximum number of PEGCs; alternatively, the maximum number of PEMCs.

With reference to the second aspect, in certain implementations of the second aspect, the processing unit is further configured to determine a PIN number to which the PIN has been added, and determine that the PEGC can access the PIN when the PIN number to which the PIN has been added is less than the number indicated by the number information; when the number of PINs to which PINs have been added is greater than or equal to the number indicated by the number information, it is determined that PEGC cannot access the PINs.

With reference to the second aspect, in some implementations of the second aspect, when the first device is a core network device (e.g., P-NF), the apparatus further includes a transceiver unit. The processing unit is configured to obtain first information, and specifically includes: and receiving the home network information of the PEMC and the home network information of the PEGC from the PEMC, the application function device, the unified data repository device or the unified data management device through the transceiving unit.

With reference to the second aspect, in some implementations of the second aspect, when the first device is a core network device (e.g., P-NF), the processing unit is further configured to locally obtain one or more of time information of the PIN, number information of the PIN, or location information of the PIN; or, the transceiver unit is further configured to receive one or more of time information of the PIN, number information of the PIN, or location information of the PIN from the application function device, the unified data management device, or the unified data repository device.

With reference to the second aspect, in some implementations of the second aspect, when the first device is a core network device, the processing unit is further configured to determine whether the PIN supports roaming according to policy information, and in a case where the PIN does not support roaming, the first device determines whether a home network of the PEMC is the same as a home network of the PEGC.

With reference to the second aspect, in some implementations of the second aspect, when the first device is a core network device, the processing unit is further configured to locally configure policy information, that is, the processing unit is further configured to locally obtain the configuration policy information; or, the transceiver unit is further configured to receive the policy information from the policy control device, the unified data repository device or the unified data management device.

Optionally, in the case that the PIN does not support roaming, the transceiver unit is further configured to send indication information to the PEMC, where the indication information is used to instruct the PEMC to further determine whether the home network of the PEGC is the same as the home network of the PEMC.

With reference to the second aspect, in certain implementations of the second aspect, when the first device is a PEMC, the transceiver unit is further configured to receive one or more of time information of a PIN, number information of PINs, or location information of PINs from the core network device; or, the processing unit is further configured to locally pre-configure one or more of time information of the PIN, number information of the PIN, or location information of the PIN, that is, one or more of time information of the PIN, number information of the PIN, or location information of the PIN is locally acquired.

With reference to the second aspect, in certain implementations of the second aspect, when the first device is a PEMC, the transceiver unit is further configured to send a connection request message to the PEGC, where the connection request message is used to request to establish a connection with the PEGC; and receiving a connection response message from the PEGC, the connection response message including home network information of the PEGC.

With reference to the second aspect, in some implementations of the second aspect, when the first device is an application function device or an application server, the processing unit is further configured to locally pre-configure one or more of time information of the PIN, number information of the PIN, or location information of the PIN, that is, obtain one or more of time information of the PIN, number information of the PIN, or location information of the PIN locally; alternatively, one or more of time information of the PIN, number information of the PIN, or location information of the PIN is received from the unified data management device through the transceiving unit.

With reference to the second aspect, in certain implementations of the second aspect, when the first device is an application function device or an application server, the transceiver unit is further configured to receive home network information of the PEMC from the PEMC, and receive home network information of the PEGC from the PEGC.

With reference to the second aspect, in certain implementations of the second aspect, when the first device is a core network device, the transceiver unit is further configured to receive location information of the PEGC from the PEMC, the unified data store device, or the unified data management device; and the processing unit is also used for determining the position of the PEGC according to the position information of the PEGC.

With reference to the second aspect, in some implementations of the second aspect, when the first device is a PEMC, the transceiver unit is further configured to send an inquiry request message to the PEMC, where the inquiry request message is used to request to obtain location information of the PEGC, and receive the location information of the PEGC from the PEGC; and the processing unit is also used for determining the position of the PEGC according to the position information of the PEGC.

With reference to the second aspect, in some implementations of the second aspect, when the first device is an application function device or an application server, the transceiver unit is further configured to receive location information of the PEGC from the PEGC; and the processing unit is also used for determining the position of the PEGC according to the position information of the PEGC.

In a third aspect, a communication method is provided, which may be performed by a first device, or may also be performed by a chip or circuit for the first device, as the application is not limited in this respect. For convenience of description, an example will be described below as being executed by the first device.

The method comprises the following steps: the first equipment acquires first information; the first device determines whether to perform a registration procedure of the authenticatable non-3 GPP device according to the first information.

According to the scheme provided by the invention, the first equipment is added to determine whether to execute the registration process of the authenticatable non-3 GPP equipment according to the first information, or the first equipment judges whether to replace the execution registration process of the authenticatable non-3 GPP equipment according to the first information.

Illustratively, the first device is a residential gateway network element (residential gateway, RG), e.g., 5G-RG. The authenticatable non-3 GPP device may be an AUN3 device. The non-3 GPP device refers to a device that connects RGs using non-3 GPP access technology and does not support NAS for non-3 GPP access.

It should be noted that the above steps are only performed when the 5G-RG confirms that the authenticatable non-3 GPP device is AUN3, and the 5G-RG does not perform the above steps if the device is namu 3

With reference to the third aspect, in some implementations of the third aspect, the first information includes home network information of an authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device is used to indicate a home network of the authenticatable non-3 GPP device, wherein the first device determines whether to perform a registration procedure of the authenticatable non-3 GPP device according to the first information, and includes: the first device refuses to execute the registration flow of the authenticatable non-3 GPP device when the first device judges that the home network of the authenticatable non-3 GPP device is different from the home network of the first device.

Based on the above scheme, the first device refuses to execute the registration process of the authenticatable non-3 GPP device under the condition that the home network of the authenticatable non-3 GPP device is different from the home network of the first device, so that the authenticatable non-3 GPP devices of different operators are prevented from executing the registration process.

With reference to the third aspect, in some implementations of the third aspect, the home network information of the authenticatable non-3 GPP device includes identification information of a home network of the authenticatable non-3 GPP device, and the first device determines that the home network of the authenticatable non-3 GPP device is different from the home network of the first device, including: the identification information of the home network of the first device and the identification information of the home network of the authenticatable non-3 GPP device are not identical.

With reference to the third aspect, in some implementations of the third aspect, refusing to perform a registration procedure of the authenticatable non-3 GPP device includes: the first device sends rejection indication information to the authenticatable non-3 GPP device to indicate rejection to initiate the registration procedure.

Optionally, the reject indication information carries a cause value, where the cause value indicates that the reject cause is that the home network of the authenticatable non-3 GPP device is different from the home network of the first device, so as to prevent the authenticatable non-3 GPP device from periodically initiating a connection to the first device.

With reference to the third aspect, in some implementations of the third aspect, refusing to perform a registration procedure of the authenticatable non-3 GPP device includes: the first device deletes locally stored information of the authenticatable non-3 GPP device to save storage space.

It should be appreciated that the two registration procedures provided above that refuse to perform an authenticatable non-3 GPP device may be used in combination, as the application is not limited in this regard.

In the present application, the home network information of the authenticatable non-3 GPP device can be obtained from one or more of the following: identification information of an authenticatable non-3 GPP device, or identification information of a home network of an authenticatable non-3 GPP device.

Alternatively, the home network information of the authenticatable non-3 GPP device may not be uniquely represented, and may be determined by PLMN ID, NID of the authenticatable non-3 GPP device, or MCC and MNC in the realm portion of the NAI, or may be determined by authenticatable non-3 GPP device identification information (e.g., realm part in network access identifier (network access identifier, NAI), specifically, where MCC and MNC are carried in the realm portion of the NAI, and the MCC and MNC can be used to identify the home network of the authenticatable non-3 GPP device, and in a non-public network scenario, MCC, MNC and NID are carried in the realm portion of the NAI, and the MCC, MNC and NID can be used to identify the home network of the authenticatable non-3 GPP device, which is not particularly limited by the present application.

With reference to the third aspect, in some implementations of the third aspect, the first information includes home network information of an authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device is used to indicate a home network of the authenticatable non-3 GPP device, wherein the first device determines whether to perform a registration procedure of the authenticatable non-3 GPP device according to the first information, and includes: when the first device judges that the home network of the authenticatable non-3 GPP device is the same as the home network of the first device, the first device executes a registration procedure of the authenticatable non-3 GPP device.

Based on the above scheme, the first device refuses to execute the registration process of the authenticatable non-3 GPP device under the condition that the home network of the authenticatable non-3 GPP device is different from the home network of the first device, so as to ensure that the authenticatable non-3 GPP device belonging to the same operator executes the registration process.

With reference to the third aspect, in some implementations of the third aspect, the home network information of the authenticatable non-3 GPP device includes identification information of a home network of the authenticatable non-3 GPP device, and the first device determines that the home network of the authenticatable non-3 GPP device is the same as the home network of the first device, including: the identification information of the home network of the first device is the same as the identification information of the home network of the authenticable non-3 GPP device.

With reference to the third aspect, in some implementations of the third aspect, the first device sends an identifier of the mobility management function network element to the radio access gateway function network element, indicating that the mobility management function network element is configured to perform a registration procedure of the authenticatable non-3 GPP device, where the mobility management function network element serves the first device.

That is, when the first device determines to execute the registration procedure of the authenticatable non-3 GPP device, the identifier of the mobility management function element is sent to the radio access gateway function element to instruct the radio access gateway function element to execute the registration procedure of the authenticatable non-3 GPP device, for example, the radio access gateway function element determines a corresponding mobility management function element according to the identifier of the mobility management function element, and the mobility management function element executes the registration procedure of the authenticatable non-3 GPP device, so that the authenticatable non-3 GPP device and the first device are defined under the same service mobility management function element, and the occurrence of interactive signaling between a plurality of mobility management function elements is avoided. When the first device refuses to execute the registration procedure of the authenticatable non-3 GPP device, the identification of the mobility management function network element may not be sent to the wireless access gateway function network element.

Illustratively, the identifier of the mobility management function element may be a globally unique AMF ID (globally unique AMF identifier, GUAMI), an AMF instance (instance), or the like. .

In a fourth aspect, there is provided a communication apparatus comprising: an acquisition unit for acquiring the first information, which may be, for example, a transceiving unit for receiving home network information of the authenticatable non-3 GPP device from the authenticatable non-3 GPP device. And the processing unit is used for determining whether to execute the registration flow of the authenticatable non-3 GPP equipment according to the first information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the first information includes home network information of an authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device being used to indicate a home network of the authenticatable non-3 GPP device. The processing unit is further configured to reject execution of the registration procedure of the authenticatable non-3 GPP device when it is determined that the home network of the authenticatable non-3 GPP device is different from the home network of the first device.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the home network information of the authenticatable non-3 GPP device includes identification information of a home network of the authenticatable non-3 GPP device. The processing unit is further configured to determine that the identification information of the home network of the first device is different from the identification information of the home network of the authenticatable non-3 GPP device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send rejection indication information to the authenticatable non-3 GPP device to indicate rejection to initiate the registration procedure.

Optionally, the reject indication information carries a cause value, where the cause value indicates that the reject cause is that the home network of the authenticatable non-3 GPP device is different from the home network of the first device, so as to prevent the authenticatable non-3 GPP device from periodically initiating a connection with the first device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to delete locally stored information of the authenticatable non-3 GPP device to save storage space.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the first information includes home network information of an authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device being used to indicate a home network of the authenticatable non-3 GPP device. The processing unit is further configured to perform a registration procedure of the authenticatable non-3 GPP device when it is determined that the home network of the authenticatable non-3 GPP device is the same as the home network of the first device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the home network information of the authenticatable non-3 GPP device includes identification information of a home network of the authenticatable non-3 GPP device, wherein the processing unit is further configured to determine, by the first device, that the identification information of the home network of the first device is the same as the identification information of the home network of the authenticatable non-3 GPP device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first device sends an identifier of the mobility management function network element to the radio access gateway function network element, indicating that the mobility management function network element is configured to perform a registration procedure of the authenticatable non-3 GPP device, where the mobility management function network element serves the first device.

The foregoing fourth aspect and advantageous effects of certain implementations of the fourth aspect may correspond to those described in relation to the third aspect, and are not repeated herein.

In a fifth aspect, a communication device is provided, comprising a transceiver, a processor for controlling the transceiver to transceive signals, and a memory for storing a computer program, the processor for calling and running the computer program from the memory, such that the communication device performs the method of any one of the possible implementations of the first or third aspect.

Optionally, the processor is one or more, and the memory is one or more.

Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.

Optionally, the communication device further comprises a transmitter (transmitter) and a receiver (receiver).

In a sixth aspect, a communication system is provided, comprising: a first device and an AUN3 device for performing the method in any one of the possible implementations of the first or third aspects.

In one possible design, the communication system may further include other devices that interact with the first device in the solution provided by the embodiments of the present application, such as PEMC, an access and mobility management function element, a unified data management element, a network open function element, a residential gateway element, or a unified data storage element.

In a seventh aspect, a computer readable storage medium is provided, the computer readable storage medium storing a computer program or code which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of the first or third aspects.

In an eighth aspect, there is provided a chip comprising at least one processor coupled to a memory for storing a computer program, the processor being adapted to invoke and run the computer program from the memory, such that a communication device in which the chip system is installed performs the method in any of the possible implementations of the first or third aspect.

The chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data, among other things.

In a ninth aspect, there is provided a computer program product comprising: computer program code which, when run by a communication apparatus, causes the network device to perform the method of any one of the possible implementations of the first or third aspects described above.

Drawings

Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a non-3 GPP system architecture according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a network architecture of PIN and 5GC provided in an embodiment of the present application.

Fig. 4 is a flowchart illustrating an example of a method for creating and managing a PIN according to an embodiment of the present application.

Fig. 5 is a flowchart of another method for creating and managing a PIN according to an embodiment of the present application.

Fig. 6 is a flow chart of a first communication method according to an embodiment of the present application.

Fig. 7 is a flow chart of a second communication method according to an embodiment of the present application.

Fig. 8 is a flow chart of a third communication method according to an embodiment of the present application.

Fig. 9 is a flow chart of a fourth communication method according to an embodiment of the present application.

Fig. 10 is a schematic diagram of a network architecture of AUN3 and 5GC according to an embodiment of the present application.

Fig. 11 is a flowchart of a fifth communication method according to an embodiment of the present application.

Fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Fig. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: a fifth generation (5th generation,5G) system or New Radio (NR), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a universal mobile telecommunications system (universal mobile telecommunication system, UMTS) or other evolved communications system, etc. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation (6th generation,6G) mobile communication system.

The technical solution of the embodiment of the present application may also be applied to machine-type communication (machine type communication, MTC), inter-machine communication long term evolution technology (long term evolution-machine, LTE-M), device-to-device (D2D) network, machine-to-machine (machine to machine, M2M) network, internet of things (internet of things, ioT) network, or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.

For convenience of description, the embodiment of the present application will be illustrated by taking a 5G network as an example.

Fig. 1 is a schematic diagram of a network architecture 100 according to an embodiment of the present application.

Fig. 1 (a) is a schematic diagram of a 5G network architecture based on a point-to-point interface. As shown in (a) of fig. 1, the network architecture may include, but is not limited to, the following network elements (alternatively referred to as functional network elements, functional entities, nodes, devices, etc.): user Equipment (UE), (radio) access network equipment (radio access network, (R) AN), user plane function (user plane function, UPF) network elements, data Network (DN), access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, policy control function (policy control function, PCF) network elements, application function (application function, AF) network elements, network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified data management, UDM) network elements, network opening function (network exposure function, NEF) network elements, unified data storage (unified data repository, UDR) network elements, and the like.

The following briefly describes each network element shown in (a) in fig. 1:

1. UE: a terminal that is in communication with a (R) AN may also be referred to as a terminal device, AN access terminal, a subscriber unit, a subscriber station, a Mobile Station (MS), a Mobile Terminal (MT), a remote station, a remote terminal, a mobile device, a subscriber terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals may be: a mobile phone, a tablet computer, a computer with wireless transceiving functions (such as a notebook computer, a palm computer, etc.), a mobile internet device (mobile internet device, MID), a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control, a wireless terminal in unmanned, a wireless terminal in telemedicine, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication functions, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolving public land mobile communication network (public land mobile network, PLMN), etc.

Furthermore, the terminal device may also be a terminal device in an internet of things (Internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. IoT technology may enable massive connectivity, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

It should be understood that the terminal device may be any device that can access the network. And the terminal equipment and the access network equipment can communicate with each other by adopting a certain air interface technology.

Alternatively, the user equipment may be used to act as a base station. For example, the user equipment may act as a scheduling entity that provides side-uplink signals between user equipments in V2X or D2D, etc. For example, a cellular telephone and a car communicate with each other using side-link signals. Communication between the cellular telephone and the smart home device is accomplished without relaying communication signals through the base station.

2. (R) AN: the system is used for providing network access functions for authorized user equipment in a specific area and can use transmission tunnels with different service qualities according to the level of the user equipment, the service requirements and the like.

The (R) AN can manage radio resources, provide access services for the ue, and further complete forwarding of control signals and ue data between the ue and the core network.

The access network device in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with the user equipment. The access network device includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved Node B, heNB, or home Node B, HNB), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (wireless fidelity, WIFI) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, e.g., NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network Node constituting a gNB or transmission point, e.g., BBU or Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (radio access network, RAN), or may be divided into access network devices in a Core Network (CN), which is not limited by the present application.

3. User plane network element: quality of service (quality of service, qoS) handling for packet routing and forwarding, user plane data, etc.

In a 5G communication system, the user plane element may be a UPF element, and may include an intermediate user plane function (intermediate user plane function, I-UPF) element, and an anchor user plane function (PDU Session anchor user plane function, PSA-UPF) element.

4. Data network: for providing a network for transmitting data.

In a 5G communication system, a protocol data unit (protocol data unit, PDU) session may be established after a terminal device accesses a network, and an application function network element (e.g., an application server) deployed in the DN may be interacted with by accessing the DN through the PDU session. Depending on the DN accessed by the user, the network may select the UPF accessing the DN as a PDU session anchor (PDU Session Anchor, PSA) according to the network policy and access the application function network element through the N6 interface of the PSA.

5. Access and mobility management network element: the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions besides session management, such as legal interception, access authorization/authentication and the like, in the functions of the mobility management network element (mobility management entity, MME).

In the 5G communication system, the access management network element may be an AMF network element.

6. Session management network element: the method is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of the terminal equipment, terminal node selecting manageable terminal equipment plane functions, strategy control and charging function interfaces, downlink data notification and the like.

In a 5G communication system, the session management network element may be an SMF network element, and may include an intermediate session management function (intermediate session management function, I-SMF) network element, and an anchor session management function (anchor session management function, a-SMF) network element.

7. Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (e.g., AMF, SMF network elements, etc.), and the like.

In a 4G communication system, the policy control network element may be a policy and charging rules function (policy and charging rules function, PCF) network element. In a 5G communication system, the policy control network element may be a PCF network element.

8. Application function network element: the application function network element can interact with the 5G system through the application function network element and is used for accessing the network open function network element or interacting with the policy framework to perform policy control and the like.

In the 5G communication system, the application function network element may be a application function AF network element.

9. Network slice selection network element: mainly comprises the following functions: selecting a set of network slice instances for the UE, determining allowed network slice selection assistance information (network slice selection assistance information, NSSAI), and determining a set of AMFs that can serve the UE, etc.

In a 5G communication system, the network slice selection network element may be an NSSF network element.

10. Authentication service network element: the method is used for realizing the bidirectional authentication of the terminal equipment by the authentication service and the generation of the secret key, and supports a unified authentication framework.

In the 5G communication system, the authentication service network element may be an AUSF network element.

11. Data management network element: the method is used for processing the terminal equipment identification, access authentication, registration, mobility management and the like.

In a 5G communication system, the data management network element may be a UDM network element or a UDR network element.

The UDM or UDR network element in the embodiment of the present application may refer to a user database. May exist as a single logical repository storing user data.

12. Network element with open function: for providing network-open customization functionality.

In the 5G communication system, the network element with the network opening function may be a network element with the network opening function NEF.

The 5G communication system may also open 5GC supported capabilities, such as providing small data transfer capabilities, etc., to external application function network elements through the NEF network elements.

As can be seen from fig. 1 (a), the interfaces between the control plane network elements in fig. 1 (a) are point-to-point interfaces, and the names and functions of the interfaces between the network elements are as follows:

n1: the interface between the AMF and the terminal may be used to deliver QoS control rules, etc. to the terminal.

N2: the interface between the AMF and the RAN may be used to transfer radio bearer control information, etc., from the core network side to the RAN.

And N3: the interface between the RAN and the UPF is mainly used for transmitting uplink and downlink user plane data between the RAN and the UPF.

N4: the interface between SMF and UPF can be used to transfer information between control plane and user plane, including control plane-oriented forwarding rule, qoS control rule, flow statistics rule, etc. and user plane information reporting.

N5: the interface between AF and PCF can be used for application service request issue and network event report.

N6: and the interface of the UPF and the DN is used for transmitting uplink and downlink user data streams between the UPF and the DN.

N7: the interface between PCF and SMF may be used to deliver protocol data unit (protocol data unit, PDU) session (session) granularity as well as traffic data flow granularity control policies.

N8: the interface between the AMF and the UDM may be used for the AMF to obtain subscription data and authentication data related to access and mobility management from the UDM, and the AMF registers current mobility management related information of the terminal from the UDM.

N9: the user interface between UPF and UPF is used to transfer the uplink and downlink user data flow between UPF.

N10: the interface between the SMF and the UDM may be used for the SMF to obtain session management related subscription data from the UDM, and the SMF registers current session related information of the terminal to the UDM.

N11: the interface between the SMF and the AMF may be used to convey PDU session tunnel information between the RAN and the UPF, control messages sent to the terminal, radio resource control information sent to the RAN, etc.

N12: the interface between the AMF and the AUSF can be used for initiating an authentication flow to the AUSF by the AMF, wherein the authentication flow can carry SUCI as a subscription identifier;

n13: the interface between the UDM and the AUSF may be used for the AUSF to obtain the user authentication vector from the UDM to execute the authentication procedure.

Fig. 1 (b) is a schematic diagram of a 5G network architecture based on a server interface. As shown in (b) of fig. 1, the network architecture may include, but is not limited to, the following network elements (alternatively referred to as functional network elements, functional entities, nodes, devices, etc.): UE, (R) AN, UPF, DN, AMF, SMF, PCF, AF, NSSF, AUSF, UDM, NEF, UDR, etc. The description of each network element function may refer to the description of the corresponding network element function in (a) in fig. 1, which is not repeated herein.

Nnssf, nnef, nudr, nausf, namf, npcf, nsmf, nudm, naf shown in fig. 1 (b) provides service interfaces for NSSF, NEF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM and AF described above, respectively, for invoking corresponding service operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface serial numbers may be found in the third generation partnership project (3rd generation partnership project,3GPP) standard protocol, and is not limited herein.

It should be understood that the 5G system described above is merely an example, and the network architecture to which the embodiments of the present application are applicable is not limited to this, and any network architecture including the functions capable of implementing the respective network elements described above is applicable to the embodiments of the present application. The communication method provided by the embodiment of the present application may also relate to a network element not shown in fig. 1, and of course, the communication method provided by the embodiment of the present application may also include only a part of the network elements shown in fig. 1.

It should also be understood that AMF, SMF, UPF, PCF, NEF shown in fig. 1 (a) or fig. 1 (b), etc. can be understood as network elements for implementing different functions, for example, can be combined into network slices as required. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform), where the specific form of the network elements is not limited by the present application.

It should also be understood that the above designations are merely intended to facilitate distinguishing between different functions and should not be construed as limiting the application in any way. The application does not exclude the possibility of using other designations in 5G networks as well as in other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

It should also be understood that the names of interfaces between the network elements in fig. 1 (a) or fig. 1 (b) are only an example, and the names of interfaces in the specific implementation may be other names, which are not specifically limited by the present application. Furthermore, the names of the transmitted messages (or signaling) between the various network elements described above are also merely an example, and do not constitute any limitation on the function of the message itself.

Fig. 2 is a schematic diagram of a non-3GPP system architecture 200 provided by an embodiment of the present application. As shown in fig. 2, the network architecture may include, but is not limited to, the following network elements (alternatively referred to as functional network elements, functional entities, nodes, devices, etc.): UE, untrusted Non-3GPP access network (un-supported Non-3GPP Access Network) device, non-3GPP interworking function (Non-3GPP InterWorking Function,N3IWF) network element, 3GPP (R) AN, UPF network element, DN, AMF network element, SMF network element, etc.

Wherein the untrusted non-3 GPP access network device allows for interworking between the terminal device and the 3GPP core network using non-3 GPP technology. Specifically, non-3 GPP technologies include, but are not limited to: wireless fidelity (Wi-Fi), worldwide interoperability for microwave access (worldwide interoperability for microwave Access, wiMAX), code division multiple access (code division multiple Access, CDMA) networks, etc., the 3GPP core network may be directly accessed relative to trusted non-3 GPP access network devices, which may need to be interconnected and interworked with the 3GPP core network through a security tunnel established by a security gateway. Illustratively, the security gateway includes: an evolved packet data gateway (Evolved Packet Data Gateway, ePDG) or an N3IWF network element.

In addition, the description of the other network element functions may refer to the description of the corresponding network element functions in fig. 1, which is not repeated herein. N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface sequence numbers may be found in the meanings defined in the 3GPP standard protocols, and are not limited herein.

Regarding the architecture of the PIN, it is currently assumed that the 3GPP UE may act as PEGC and/or PEMC, there may be one or more PEGCs in the PIN, there may be one or more PEMCs in the PIN, the PIN should use a non-3 GPP connection (e.g., bluetooth, WIFI, etc.) as a direct connection, and the PEMCs may use a 5G proximity-based service (ProSe) to establish direct communication with the PEGCs.

The following 7 key problems are presented in TR 23.700-88, respectively:

(1) Architecture enhancements for 5GC to support PIN: at least one PEGC is required in the PIN, forwarding traffic between 5GS and the PIN following the PEGC. The PINE may be a non-3 GPP device or a UE. A PIN has one or more PEMCs. However, at any point in time, only one PEMC is able to manage and control the PIN.

(2) Discovery and selection of PINs and PINs: study how to discover and select PIN and PEGC, and select PIN based on constraints such as energy, service, reachability, etc., and study whether it is discovered by PIN or by a non-PIN member.

(3) Management of PINs and PINs: management of PINs is supported, including management of different types of PIN elements and configuration of PINs. Both the network operator and an authorized third party, i.e., a PIN element (e.g., PEMC) with administrative capabilities, can create and configure the PIN and its elements. After the PIN is created, the PEMC may add a PEGC to the PIN code or delete a PEGC from the PIN, or may add a PIN to the PIN and associate it with some PEGCs to which the PIN has been added or delete a PIN from the PIN.

(4) Communication of PIN: the problem of communicating different PINs within the PIN is solved and how to have PINs communicate with 5GS using PEGC and when PEGC is used for relay, 5GS supports policy and QoS differentiation of relay traffic between PINs and 5 GS.

(5) Authorization of the PIN: the owner of the PIN may configure authorization information for the PIN, e.g., whether the PIN may communicate with other PINs or with a particular data network, whether the UE is allowed to function as PEMC and/or PEGC, etc. It is studied how to authorize/de-authorize pins to access 5GS services and to authorize/de-authorize PEGC to provide connection to 5G networks for other pins that do not have the ability to access 5G networks.

(6) Policy (policy) and parameters of PIN: it is studied whether and how to configure PIN-related policies and parameters determined in other key questions into PEMCs, PEGCs and PINs for PIN discovery, authentication/authorization of PINs and PIN communication, and whether and how to support providing configuration information to PEGCs for access control.

(7) Identification of PIN and PIN: study how to support identification PIN, PINE, PEGC and PEMC, which features in a PIN should be perceived by the 3GPP network and whether and how to manage the identifier.

Fig. 3 is a schematic diagram of a network architecture 300 of PIN and 5GC provided in an embodiment of the present application. As shown in fig. 3, the network architecture includes a PIN and 5GC network. Wherein, the PIN includes: PINE, PEMC, and PEGC, a 5GC network includes: (R) AN, UPF, AMF, SMF, PCF, P-AF, NEF, AUSF, UDM, P-NF, etc.

Specifically, in the PIN, the PEF may provide a communication function through the PEGC inside or outside the PIN, and may also communicate with the PEMC to perform configuration, discovery, authentication, and authorization. The PEMC may provide the function of managing the PIN. PEGC may provide functionality for other PIN elements to connect to a 5G network, or relay communications between PIN elements. In a 5GC network, P-NF (PIN-F) may provide the functionality to manage the PIN. The P-NF may also process the request to create the PIN, e.g., select one UE as PEMC and distribute the PIN ID to identify the PIN, etc. The P-AF may access network elements of the network open function, etc.

It should be understood that PEMC may be regarded as a UE having PEMCF and PEGC may be regarded as a UE having PEGCF. The N1 interface may connect the UE of the PIN and the AMF of the 5GC network, and is used for the AMF to transfer QoS control rules and the like to the UE (PEMC or PEGC).

In addition, the description of the other network element functions may refer to the description of the corresponding network element functions in fig. 1, which is not repeated herein.

It should be noted that, the architecture defines a reference point (reference point): p1 and P2. Where P1 is the reference point between PEFs on different devices. P2 is the reference point between PEGC and PEMC. Both P1 and P2 support peer-to-peer (peer-to-peer) transmissions, such as Bluetooth, WIFI, 5G ProSe, and the like. In addition, the architecture defines a servitization interface: npinf and Npaf. Wherein Npinf is a servitized interface provided by P-NF and Npaf is a servitized interface provided by P-AF.

The creation and management of the PIN will be described from the viewpoint of 5GC side and AS side, respectively.

Fig. 4 is a flowchart illustrating an exemplary method 400 for creating and managing a PIN according to an embodiment of the present application. As shown in fig. 4, the following steps are specifically included.

S401, the PEMC completes registration in the core network and establishes a PDU session.

S402, the PEGC completes registration in the core network.

Illustratively, the UE supporting both PEMCF and PEGCF functions completes registration in the core network.

Specifically, the registration manner of PEMC may include: the PEMC sends a registration request message to the P-NF for requesting registration in the core network, wherein the registration request message carries PEMC ID and PEMC configuration data (PEMC configuration), stores the PEMC configuration data after the P-NF passes verification, and sends a response message to the PEMC for informing that the PEMC registration is successful. Similarly, the registration method of the PEGC may refer to the registration method of the PEMC.

S400, the UPF sends instruction information #1 to the AF.

Correspondingly, the AF receives the indication information #1 from the UPF.

The indication information #1 is used for indicating that the PEMC can interact with the P-AF through the user plane, so that the AF obtains a message that the PEMC is connected and available.

S403, the AF sends a PIN establishment request message #1 to the NEF.

Correspondingly, the NEF receives a PIN establishment request message #1 from the AF.

The PIN establishment request message #1 may be nnef_setup Req, including PEMC ID.

Alternatively, the PEMC may be determined by the user on the APP.

S404, NEF sends PIN establishment request message #2 to P-NF.

Correspondingly, the P-NF receives the PIN establishment request message #2 from the NEF.

The PIN establishment request message #2 may be npnf_setup Req, including PEMC ID.

S405, the PIN sends a subscription request message #1 to the UDM or UDR and receives a subscription response message #1 from the UDM or UDR.

Correspondingly, the UDM or UDR receives the subscription request message #1 from the PIN and sends a subscription response message #1 to the P-NF.

The subscription request message #1 may be nudm_ Subscriber Data get, including a PEMC ID, for requesting data of a UE (PEMC) subscribed to with the PEMC ID to determine whether the PEMC supports a PEMCF function.

S406, the P-NF creates a PIN and assigns a PIN ID.

Wherein the PIN ID is associated with the PEMC ID.

Illustratively, the P-NF creates the PIN if it is determined that the PEMC is PEMCF-capable.

S407, the P-NF sends a PIN establishment response message #1 to the NEF.

Correspondingly, the NEF receives a PIN establishment response message #1 from the P-NF.

The PIN establishment response message #1 may be npnf_setup Resp, including a PIN ID, for notifying that PIN creation is completed.

Optionally, the PIN setup response message #1 further includes a PEMC ID.

In S408, the NEF sends a PIN establishment response message #2 to the AF.

Correspondingly, the AF receives the PIN setup response message #2 from the NEF.

Wherein, the PIN Setup response message #2 may be nnef_setup Resp, including a PIN ID for notifying that PIN creation is completed.

Optionally, the PIN setup response message #2 further includes a PEMC ID.

That is, the above-described steps S403 to S408 are a creation flow of the initiation PIN based on AF.

S409, the P-NF sends a PIN creation notification message #1 to the AMF.

Correspondingly, the AMF receives a PIN creation notification message #1 from the P-NF.

The PIN creation notification message #1 may be npnf_pin_creation_resp, including a PIN ID and PEMC ID, for notifying completion of PIN creation.

S410, the AMF sends a PIN creation notification message #2 to the PEMC.

Correspondingly, the PEMC receives the PIN creation notification message #2 from the AMF.

Wherein, the PIN creation notification message #2 may be NAS signaling including a PIN ID for notifying that PIN creation is completed.

S411, a connection is established between PEMC and PEGC devices.

By way of example, the connection between PEMC and PEGC may be established by Wi-Fi, bluetooth, 5G Prose, etc., and the present application is not limited thereto.

S412, the PEMCF transmits an authorization request message #1 to the AMF.

Correspondingly, the AMF receives the grant request message #1 from the PEMCF.

The authorization request message #1 may be NAS signaling, including PIN ID, PEGC ID, and PEMC ID, for authorizing PEGC to be added to PIN.

S413, the AMF sends a PIN authorization request message #2 to the P-NF.

Correspondingly, the P-NF receives the authorization request message #2 from the AMF.

Wherein, the authorization request message #2 may be npnf_create_req, including PEGC ID.

Optionally, the authorization request message #2 further includes a PIN ID.

S414, the P-NF sends a subscription request message #2 to the UDM or UDR and receives a subscription response message #2 from the UDM or UDR.

Correspondingly, the UDM or UDR receives the subscription request message #2 from the PIN and sends a subscription response message #2 to the P-NF.

The subscription request message #2 may be nudm_ Subscriber Data get, including a PEGC ID, for requesting data of a UE (PEGC) subscribed to carry the PEGC ID to determine whether the PEGC supports the PEGCF function.

S415, the P-NF updates the PEGC information to the PIN context.

For example, the P-NF updates the PEGC information to the context of the PIN if it is determined that the UE of the PEGC has the PEGC function.

The context of the PIN may be PIN profile, such as PIN ID, PEGC ID, PEMC ID, etc. The PEGC information includes PEGC ID, optionally, PEGC identification information, where the identification information may be geographic location, network identification (e.g., PLMN ID), etc., which is not particularly limited in the present application.

S416, the P-NF sends a notification message #1 to the NEF.

Correspondingly, the NEF receives notification message #1 from the P-NF.

S417, NEF sends notification message #2 to AF.

Correspondingly, the AF receives notification message #2 from the NEF.

Wherein the notification message #1 and the notification message #2 include a PIN ID and a PEGC ID for notifying that the PEGC successfully joins the PIN.

S418, the P-NF sends a notification message #3 to the AMF.

Correspondingly, the NEF receives notification message #3 from the P-NF.

S419, the AMF sends a notification message #4 to PEGCF.

Correspondingly, PEGCF receives notification message #4 from AMF.

S420, the AMF sends a notification message #5 to the PEMCF.

Correspondingly, the PEMCF receives a notification message #5 from the AMF.

Wherein the notification message #3, the notification message #4, and the notification message #5 include a PIN ID, a PEGC ID, and a PEMC ID for notifying that the PEGC successfully joins the PIN. Notification message #4 and notification message #5 may be NAS signaling.

I.e. steps S416-S420 are used to inform AF, PEGCF and PEMCF in sequence that the PEGC was successfully added to the PIN.

In this implementation, when the P-NF creates and manages the PIN, the limiting condition when the PIN (e.g., PEGC) joins the network is not considered, which may cause the current PIN joining process to be irregular, and even affect the normal operation of the PIN.

Fig. 5 is a flowchart of another embodiment of a method 500 for creating and managing a PIN according to an embodiment of the present application. As shown in fig. 5, the following steps are specifically included.

S510, the PIN completes registration in the PIN AS or PIN AF.

For example, registration of the PINE may include: the authentication of PEMC and PEGC and the authorization of access based on the device owner configuration (e.g., S510a-S510 b).

Optionally, registration of other pins is also included (e.g., S510 c). Other pins refer to pins other than PEMC and PEGC.

Specifically, in steps S510a-S510c, PEMC, PEGC and other PINs send a registration request message to PIN AS or PIN AF, respectively, carrying a PIN ID and PIN configuration data (PIN profile), and when PIN AS or PIN AF passes verification, storing the configuration data of the PIN, and sending a response message to the PIN for notifying that the PIN registration is successful.

Wherein, PINE profile contains: device IDs (e.g., PEMC ID, PEGC ID, other pin IDs).

Optionally, the PINE profile further contains at least one of the following information: a device name; MAC address or bluetooth ID; GPSI of UE; safety-related information; a device type, e.g., PINE, PEGC, PEMC; device communication capabilities; device service capabilities.

S521, the PEMC transmits a PIN creation request message #a to the PIN AS or the PIN AF.

Correspondingly, the PIN AS or PIN AF receives the PIN creation request message #a from the PEMC.

Wherein the PIN creation request message #a includes PEMC ID for requesting the establishment of PIN.

S522, the PIN AS or the PIN AF creates a PIN and assigns a PIN ID.

Illustratively, the PIN AS or PIN AF creates a PIN in the event that the PEMC is determined to be PEMCF-capable.

The PIN AS or PIN AF determines that the PEMC has a PEMCF function, and may send a subscription request message to the UDM or UDR, carrying a PEMC ID, for requesting subscription to data of a UE (PEMC) with the PEMC ID, so AS to determine whether the PEMC supports the PEMCF function.

S523, the PIN AS or PIN AF sends a PIN creation response message #a to the PEMC.

Correspondingly, the PEMC receives a PIN creation response message #a from the PIN AS or the PIN AF.

Wherein the PIN creation response message #a includes a PIN ID for notifying completion of PIN creation.

S530, the PEMC sends a PIN creation request message #b to the PIN AS or PIN AF.

Correspondingly, the PIN AS or PIN AF receives the PIN creation request message #b from the PEMC.

Wherein the PIN creation request message #b includes PEGC ID for requesting the PIN AS or the PIN AF to add PEGC to the PIN.

S540, PIN AS or PIN AF allows PEGC to join the PIN.

Illustratively, the PEMC requests the PIN AF or PIN AS to add PEGC to the PIN. If the PEGC accepts the request to join the PIN, the PIN AS or PIN AF updates the PIN profile and the context data (context data) of the PIN.

S550, the PIN AS or PIN AF updates the PIIN profile and the context data of the PIN.

Illustratively, the PIN AS or PIN AF updates the PIN profile and context data after the PEGC successfully joins the PIN, while the PIN AS or PIN AF sends PIN configuration information and parameters, such AS PIN ID, to the PEGC.

Wherein the PIN Profile contains at least one of the following information: the state of the PIN (active or inactive); a list of PEMCs for the service, including PEMC ID, PEMC status, GPSI, and PLMN ID; the PEGC list of services, including PEGC ID, PEGC status, GPSI, and PLMN ID; a list of pins including pin ID, pin status, GPSI and PLMN ID or MAC address, bluetooth ID; validity period and time validity of PIN and PINE.

By way of example, the contextual data of the PIN may include at least one of: associated PIN ID; associated PEGC; device state; allocated IP addresses/IPv6 prefix; or Authorized communication paths, etc.

S560, the PIN AS or PIN AF sends the PIN service specific range to the UDR or UDM (PIN service specific parameter).

Correspondingly, the UDR or UDM receives PIN service specific parameter from the PIN AS or PIN AF.

Wherein the PIN service specific parameter is used to obtain policy control information for the PEGC, the PIN service specific parameter includes PIN ID, PEGC ID, default QoS requirements, and PINE communication duration.

Illustratively, the PIN AS or PIN AF sends PIN service specific parameter to the UDR or UDM through the NEF to obtain policy control information for the PEGC.

It should be understood that the above steps S530-S560 are processes in which the PEMC requests the PIN AS or the PIN AF to add the PEGC to the PIN.

Similarly, the PEMC may request the PIN AS or the PIN AF to add another PIN to the PIN, and the specific implementation may refer to steps S530-S560 described above, which are not repeated here for brevity.

In this implementation, when the PIN AS or the PIN AF creates and manages the PIN, although PLMN IDs of PEGC and PEMC are stored in the PIN profile, the limitation condition when the PIN (e.g., PEGC) joins the network is not considered yet, which may cause that the current PIN joining process is not normal, and even affects the normal operation of the PIN.

In summary, there may be a problem of irregular PIN management when the PIN joins the network, thereby deteriorating the network operating environment.

In view of this, the present application provides a communication method and apparatus, where a first device (for example, a core network element or a core network device P-NF, or a PIN AS or a PIN AF) and/or (PEMC or PEGC device) determines whether the PEGC can join the PIN according to a newly defined constraint condition, so that a more standardized PIN management procedure can be implemented, and an orderly network operation environment is ensured.

To facilitate an understanding of the embodiments of the present application, the following description is made:

in various embodiments of the application, where no special description or logic conflict exists, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments based on their inherent logic.

In embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/" generally indicates that the front-rear associated object is an or relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be single or multiple respectively.

In the embodiments of the present application, "first", "second" and various numerical designations indicate distinction for convenience of description, and are not intended to limit the scope of the embodiments of the present application. For example, different indication information is distinguished, etc.

In the embodiment of the application, the descriptions of "when … …", "in the case of … …", and "if" and the like all refer to that the device will perform corresponding processing under some objective condition, and are not limited in time, nor do the device require a judging action in implementation, nor are other limitations meant to exist.

In an actual deployment, different devices may be co-located. For example, an access and mobility management device (e.g., AMF) may be collocated with a session management device (e.g., SMF); the access and mobility management device (e.g., AMF) may be collocated with the PIN management device (e.g., P-NF). When two devices are combined, the interaction between the two devices provided in the embodiment of the present application becomes an internal operation of the combined device or may be omitted.

The technical scheme provided by the application will be described in detail below with reference to the accompanying drawings.

Fig. 6 is a flowchart of a first communication method 600 according to an embodiment of the present application. As shown in fig. 6, the method specifically includes the following two steps.

S610, the first device acquires first information.

The first device may be a PIN function (PIN network function, P-NF) device (also referred to AS a core network device or core network element), a PIN application function (application function, AF) device or PIN AS, or a personal internet of things element (PIN elements with management capability, PEMC) with management functions, AS the application is not limited in particular.

It should be noted that, in the application embodiment, the PEMC may be regarded as a terminal device having a PEMC function (PIN elements with management capability function, PEMCF). Similarly, PEGC can be regarded as a terminal device with PEGC functionality (PIN elements with gateway capability function, PEGCF).

Illustratively, the first information includes one or more of: home network information of PEMCs (e.g., home public land mobile network HPLMN identification) and home network information of PEGCs; or PIN location information; or time information of the PIN; or PIN quantity information. Wherein, the home network information of PEMC is used for indicating the home network of PEMC, the home network information of PEGC is used for indicating the home network of PEGC, the position information of PIN is used for indicating the position of allowed joining PIN, the time information of PIN is used for indicating the time of allowed joining PIN, and the quantity information of PIN is used for indicating the quantity of PINE which PIN supports joining.

Optionally, when the first information includes information indicating a home network of the PEGC, the home network information of the PEGC is one or more of: identification information of the PIN (e.g., PIN ID), context information of the PIN, identification information of the PEGC (e.g., PEGC ID), or identification information of the home network of the PEGC (e.g., PLMN1 ID). When the first information includes information indicating a home network of the PEMC, the home network information of the PEMC includes one or more of: identification information of the PIN (e.g., PIN ID), context information of the PIN, identification information of the PEMC (e.g., PEMC ID), or identification information of the home network of the PEMC (e.g., PLMN2 ID).

That is, the home network information of PEMCs and the home network information of PEGCs, such as the identification information of PIN, the context information of PIN, the identification information of PEGC, the identification information of PEMC, the identification information of home network of PEGC, or the identification information of home network of PEMC, may be used to indicate the home network of PEGC and the home network of PEMC.

For example, home network information of the PEGC may be included in the identity of the PEGC. For example, the identification information of the PEGC includes a home network identification PLMN1 ID of the PEGC. Similarly, the identification information of the PEMC includes a home network identification PLMN2 ID of the PEMC, or the identification information of the PIN includes a home network identification PLMN1 ID of the PEGC, and/or a home network identification PLMN2 ID of the PEGC.

Correspondingly, the first device determines the home network of the PEMC and the home network of the PEGC according to the home network information of the PEMC and the home network information of the PEGC. For example, whether to allow PEGC to access the PIN is determined by determining whether the home network of the PEMC and the home network of the PEGC are the same, and/or whether the PIN supports a roaming scenario.

In the embodiment of the present application, roaming or roaming scenario may be understood as that terminal devices from or belonging to different home networks are located or belong to the same PIN. For example, supporting roaming or supporting roaming scenarios may be understood as allowing terminal devices from or belonging to different home networks to be located or belonging to the same PIN. As another example, a roaming not supported or roaming not supported scenario may be understood as not allowing terminal devices from or belonging to different home networks to be located or belonging to the same PIN.

By way of example, the context information of the PIN may include one or more of identification information of the PEGC, identification information of the PEMC, identification information of the home network of the PEGC.

Optionally, the location information of the PIN includes one or more of: a geographic location; a network identification code NID; tracking area identification TAI; cell identification; a network selection group identification GIN; a Cell Access Group (CAG) identifier; slicing information; data network name information; coordinate value information; or longitude and latitude information.

Optionally, the time information (time information of PIN) of the PIN includes one or more of: start time (e.g., 15:00) and end time (e.g., 17:00) of the PIN; alternatively, the duration of the PIN (valid time), e.g., 15:00-17:00.

Optionally, the PIN quantity information (threshold of PINE (PEGC)'s quality) includes one or more of: maximum number of PINs; maximum number of PEGCs; alternatively, the maximum number of PEMCs.

Specifically, when the first device is a core network device (e.g., P-NF), the first device obtains the first information, including the following several implementations.

In one possible implementation, the first device receives home network information of the PEMC and home network information of the PEGC from the PEMC, the application function device, the unified data management device, or the unified data repository device.

In another possible implementation, the first device obtains one or more of time information, quantity information, or location information locally.

In yet another possible implementation, the first device receives one or more of time information, quantity information, or location information from an application function device, a unified data store device, or a unified data management device.

Specifically, when the first device is a PEMC, the first device obtains the first information, including the following several implementations.

In one possible implementation, the PEMC sends a connection request message to the PEGC, where the connection request message is used to request a connection to be established with the PEGC; the PEMC receives a connection response message from the PEGC, the connection response message including PEGC home network information.

In another possible implementation, the first device receives one or more of time information, quantity information, or location information from a core network device.

Specifically, when the first device is an application function device or AF or application server AS, the first device obtains the first information, including the following several implementations.

One possible implementation, the first device obtains one or more of time information, quantity information, or location information locally.

In another possible implementation, the first device receives home network information of the PEMC from the PEMC and receives home network information of the PEGC from the PEGC.

S620, the first device determines whether the PEGC can join the personal Internet of things PIN according to the first information.

In one possible implementation, the first device determines that the PEGC is able to join the PIN when the home network of the PEGC is the same as the home network of the PEMC; when the home network of the PEGC is different from the home network of the PEMC, the first device determines that the PEGC cannot join the PIN.

Based on the scheme, the implementation method can avoid roaming caused by the existence of PEGC and PEMC of different operators in the same PIN, realize more standardized PIN management flow and ensure orderly network operation environment.

In another possible implementation, the first device determines a location of the PEGC; when the position of the PEGC is located at the position indicated by the position information, the first device determines that the PEGC can join in the PIN; when the location of the PEGC is outside the location indicated by the location information, the first device determines that the PEGC is not joinable to the PIN.

Optionally, the PEMC determines whether the current PEMC and the PEGC are connected in a point-to-point manner, and sends indication information to the first device (for example, P-NF) to indicate that the locations of the PEMC and the PEGC are within a certain range, that is, the locations of the PEMC and the PEGC are close. Further, the first device determines whether the PEGC can join the PIN according to whether the position of the PEGC is located at the position indicated by the position information.

Illustratively, when the first device is a core network device (e.g., AMF, UDM, NEF, SMF, PCF, UDR, P-NF), the first device receives location information of the PEGC from the PEMC, the unified data management device, or the unified data repository device, and determines a location of the PEGC based on the location information of the PEGC.

For example, when the first device is a PEMC, the first device sends an inquiry request message to the PEMC, the inquiry request message being used to request acquisition of location information of the PEGC; and receiving the position information of the PEGC from the PEGC, and determining the position of the PEGC according to the position information of the PEGC.

Illustratively, when the first device is an application function device AF or an application server AS, the first device determines a location of the PEGC, including: the first device receives PEGC position information from the PEGC and determines the PEGC position according to the PEGC position information

In yet another possible implementation, the first device determines a time at which the PEGC joins the PIN; when the PEGC addition time belongs to the time indicated by the time information, the first device determines that the PEGC can add the PIN, and when the PEGC addition time does not belong to the time indicated by the time information, the first device determines that the PEGC cannot add the PIN.

The time when PEGC added to PIN may be understood as the time when PEGC requested to add PIN.

Based on the scheme, the implementation mode can avoid PEGC access when the PIN is overtime, standardizes the mode of adding the PIN to the PINE at the current stage, namely realizes a more standardized PIN management flow and ensures an orderly network operation environment.

In yet another possible implementation, the first device determines a PIN number to which the PIN has been added; when the number of PINs which have been added with the PINs is smaller than the number indicated by the number information, the first device determines that the PEGC can access the PINs; when the number of PINs to which PINs have been added is greater than or equal to the number indicated by the number information, the first device determines that the PEGC cannot access the PINs.

Based on the scheme, the implementation mode can avoid PEGC access when PINE in the PIN is overloaded, standardizes the mode of adding PINE in the current stage, namely realizes a more standardized PIN management flow and ensures an orderly network operation environment.

Optionally, when the first device is a core network device, the first device determines whether the PIN supports roaming according to the policy information.

Illustratively, when the first device is a core network device, the policy information is locally preconfigured by the first device; alternatively, the first device receives policy information from a policy control device, a unified data store device, or a unified data management device.

Alternatively, the policy information may indicate that the PIN does not support roaming, or that terminal devices from different home networks cannot join or belong to (or be located in) the same PIN.

In one possible implementation, the first device determines whether the home network of the PEMC is the same as the home network of the PEGC in the event that the PIN does not support roaming.

In another possible implementation manner, in a case where the PIN does not support roaming, the first device sends indication information to the PEMC, where the indication information is used to instruct the PEMC to further determine whether the home network of the PEGC is the same as the home network of the PEMC.

Based on the scheme, the core network equipment judges whether the PIN supports roaming or not, and further triggers and determines whether the PEGC and the PEMC belong to the same home network or not. Specifically, if the PIN supports roaming, it may not be required that PEMC and PEGC belong to the same network; conversely, if the PIN does not support roaming, the PEGC is required to be identical to the home network (e.g., PLMN ID) of the PEMC when the PEGC applies to join the PIN. The method can standardize the PIN access process of PINE, and is convenient for PIN management.

It should be noted that the method 600 may be performed by the first device, or may be performed by a chip or a circuit for the first device, which is not limited by the present application.

It should be understood that the first information is used to determine whether the first device with gateway functionality (e.g. PEGC) can join a PIN, which may be requested to be established by the second terminal device with management functionality (e.g. PEMC) or may be requested to be established by the network element with application functionality (application function, AF). Illustratively, the second terminal device sends information #1 to the first device for requesting to join the first device to the PIN, and when the first device determines that the first device can join the PIN according to the first information, the first device sends information #2 to the second terminal device for indicating that the first device is allowed to join the PIN; or when the first device determines that the first device cannot join the PIN according to the first information, the first device sends information #3 to the second terminal device, wherein the information #3 is used for indicating that the first device cannot join the PIN.

According to the scheme provided by the application, by newly defining the first information (namely, the limit condition of the PEGC to access the PIN), the first equipment (such AS P-NF, PEMC, PIN AF or PIN AS) judges whether the PEGC can join the PIN according to the first information, and the implementation mode can realize a more standardized PIN management flow and ensure an orderly network operation environment.

Next, taking a management scenario of a PIN on the 5GC side as an example, the creation of the PIN is triggered by a network element (e.g., P-AF) in the 5GC, and management of the PIN and a PIN (e.g., PEGC) is mainly created by P-NF.

Fig. 7 is a flow chart of a second communication method 700 according to an embodiment of the present application, as shown in fig. 7, specifically including the following steps.

S710, the pin completes registration in the core network.

Illustratively, UEs supporting PEMCF and PEGCF functions (e.g., PEMC and PEGC) are registered in 5 GC. The specific registration process may refer to steps S401 and S402 in the method 400, which are not repeated herein for brevity.

Wherein the PEMC can interact with the PIN AF on the user plane. For example, the PIN AF may obtain a message that the PEMC is connected to and available, such as a PEMC ID.

S720, the AF sends a PIN establishment request message to the P-NF.

Correspondingly, the P-NF receives a PIN establishment request message from the AF.

Illustratively, the AF may send a PIN establishment request message to the P-NF through the NEF.

The PIN establishment request message is used for requesting the P-NF to establish the PIN in the 5GC network, and comprises the information of the PEMC and the information of the PIN to be established.

Illustratively, the information of the PEMC includes a PEMC ID, and the information of the PIN to be established includes one or more of the following: constraint a, constraint B, and constraint C.

Specifically, the constraint a is location information for indicating a location where the PIN is permitted to be added. The constraint B is a quantity information indicating the number (threshold of PINE's quality) of the maximum PIN the PIN is allowed to access. Optionally, the number of maximum PEMCs (threshold of PEMC's quality) or the number of maximum PEGCs (threshold of PEGC's quality). Constraint C is time information indicating time information (time information of PIN) of the PIN, such as the duration of the PIN (valid time), e.g., 15:00-17:00, or the start time (start time), e.g., 15:00, of the PIN, and the end time (end time), e.g., 17:00.

The duration of the PIN is understood to be the validity period (validity duration) and time validity of the PIN.

Optionally, the P-NF may also autonomously configure or determine the information of the PIN to be established. At this time, in step S720, the information of the PIN to be established may not be carried, or the P-NF may further determine the optimal information of the PIN to be established after comparing the information of the PIN to be established sent by the AF with the information of the PIN to be established determined independently, which is not particularly limited in the present application.

S730, the P-NF creates a PIN and assigns a PIN ID.

Wherein the PIN ID is associated with the PEMC ID.

For example, the PIN may send a subscription request message to the UDM or UDR requesting to subscribe to data of the PEMC to check whether the PEMC supports PEMCF functionality, the subscription message carrying the PEMC ID. After determining that the PEMC supports the PEMCF function, the P-NF creates a PIN.

Optionally, the P-NF sends a PIN creation response message to the AF for notifying the AF of the completion of the PIN creation, the PIN creation response message including the PIN ID and the PEMC ID.

S740, the P-NF sends a notification message to the PEMC.

Correspondingly, the PEMC receives the notification message from the P-NF.

Illustratively, the P-NF may send the notification message to the PEMCF via the AMF.

The notification message includes a PIN ID for notifying the PEMC that the creation of the PIN is completed and requesting acquisition of home network information of the PEGC.

Optionally, the notification message includes information of the PIN to be established, such as one or more of constraint a, constraint B, or constraint C.

S750, PEMC discovers PEGC.

One possible implementation manner may be Wi-Fi, bluetooth, 5GProse, etc., which is not particularly limited by the present application.

Illustratively, the PEMC sends a connection request message to the PEGC and receives a connection response message from the PEGC.

Correspondingly, the PEGC receives the connection request message from the PEMC and sends a connection response message to the PEMC.

Wherein the connection request message is used to initiate a connection between the PEGC and the PEMC, optionally including home network information of the PEMC, such as PLMN ID of the PEMC, GPSI, SUCI, SUPI, etc. The connection response message is used for determining that the connection is established between the PEMC and the PEG, and comprises home network information of the PEGC and position information of the PEGC. The home network information of the PEGC includes home network identification information PLMNID of the PEMC, a global positioning system identifier (global position system identifier, GPSI), a subscription hidden identifier (subscription concealed identifier, sui), a subscription permanent identifier (subscription permanent identifier, SUPI), and the like.

Optionally, the PEGC compares the home network information of the PEMC with the own home network information, and if the same, sends a connection response message to the PEMC.

In the embodiment of the present application, peer-to-peer transmission is supported between PEGC and PEMC, but the direct connection (direct connection) method of PEGC and PEMC is not limited, and both may be connected by WIFI, bluetooth, or the like, which are not 3GPP, or by 5G ProSe. Namely, the PEMC discovers PEGCF through a discovery mechanism of 5G ProSe or a non-3 GPP mode, and establishes direct connection with PEGC based on the mode.

S760, the PEMC sends a connection acknowledgement (connection confirm) message to the P-NF.

Correspondingly, the P-NF receives a connection acknowledgement message from the PEMC.

For example, after the PEMC and PEGC connection are established based on the above, the PEMC may send a connection acknowledgement message to the P-NF through the AMF based on NAS signaling, carrying the PEGC ID, location information of the PEGC, and/or home network information of the PEMC and PEGC (i.e., constraint D for indicating whether the PIN supports roaming).

Optionally, the connection confirmation message further includes a PIN ID and a PEMC ID.

S770, the P-NF determines whether PEGC is allowed to access the PIN.

Illustratively, the P-NF determines whether to allow PEGC to join the PIN based on one or more of constraint D, constraint a, constraint B, or constraint C described above, including in particular the following implementations.

Mode one: it is determined whether PEGC is allowed to join the PIN according to constraint D (whether the PIN supports roaming).

Illustratively, the P-NF compares whether the home network information of the PEMC and the PEGC received in step S760 are the same to determine whether to allow the PEGC to join the PIN. For example, whether the PLMN ID of the PEMC is the same as the PLMN ID of the PEGC is determined, if the two home networks are the same, the PEGC is determined to be allowed to join the PIN, otherwise, the PEGC is not allowed to join the PIN.

Optionally, the P-NF determines whether the current PIN supports roaming (roaming) according to a pre-configured policy; in the case where the PIN does not support roaming, the P-NF judges whether the PLMN ID of the PEMC is the same as the PLMN ID of the PEGC. Or the P-NF sends indication information to the PEMC, and the indication information is used for indicating the PEMC to acquire the home network information of the PEGC, judging whether the home networks of the PEGC and the PEMC are the same, and further determining whether the PEGC is allowed to join the PIN.

Mode two: it is determined whether PEGC is allowed to join the PIN according to the constraint condition a (location information of the PIN).

Illustratively, the P-NF determines whether the location of the PEGC is at the location indicated by the location information of the PIN according to the location information of the PEGC received in step S760, to determine whether the PEGC is allowed to join the PIN. If the position of the PEGC is at the position indicated by the position information of the PIN, determining that the PEGC is allowed to join the PIN, otherwise, not allowing the PEGC to join the PIN.

Further, in combination with modes one and two, the P-NF may also determine whether to allow PEGC to join the PIN based on the constraint a+d.

The P-NF determines whether the PIN supports roaming according to the first mode, and determines whether the PEGC is located at a position indicated by the position information of the PIN according to the second mode, to determine whether to allow the PEGC to join the PIN. If the PIN supports roaming, determining that the PEGC is allowed to join the PIN when the position of the PEGC is at the position indicated by the position information of the PIN. If the PIN does not support roaming, it is determined that the PEGC is allowed to join the PIN when the location of the PEGC is at the location indicated by the location information of the PIN and the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same).

Mode three: it is determined whether PEGC is allowed to join the PIN according to the constraint condition B (number information of PINs).

The P-NF determines the number of PINs (or the number of PEGCs) that the PIN supports access according to the number of PINs received in step S720, and determines whether the PINs are overloaded when the PEGC joins the PIN, to determine whether to allow the PEGC to join the PIN. If the number of PINs (or PEGs) accessed by the PINs at the moment is smaller than the number indicated by the number information of the PINs, determining that the PEGs are allowed to join the PINs, otherwise, not allowing the PEGs to join the PINs.

Further, in combination with modes one, two and three, the P-NF may also determine whether to allow PEGC to join the PIN according to the constraint b+d or a+b or a+b+d.

Illustratively, the P-NF determines whether the PIN supports roaming according to mode one and whether the PIN is overloaded when the PEGC joins the PIN according to mode three to determine whether to allow the PEGC to join the PIN. If the PIN supports roaming, when the number of PINs is smaller than the number indicated by the number information of PINs when the PEGC joins the PIN, it is determined that the PEGC is allowed to join the PIN. If the PIN does not support roaming, when the PEGC joins the PIN, the number of PINs is smaller than the number indicated by the number information of the PINs, and the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same), it is determined that the PEGC is permitted to join the PIN.

The P-NF determines whether the PEGC is at a position indicated by the position information of the PIN according to the second mode, and determines whether the PIN is overloaded when the PEGC is added to the PIN according to the third mode, to determine whether to allow the PEGC to be added to the PIN. And if the position of the PEGC is at the position indicated by the position information of the PIN and the number of PINs is smaller than the number indicated by the number information of the PIN when the PEGC joins the PIN, determining to allow the PEGC to join the PIN.

The P-NF determines whether the PIN supports roaming according to the first mode, determines whether the PEGC is located at a position indicated by the position information of the PIN according to the second mode, and determines whether the PIN is overloaded when the PEGC joins the PIN according to the third mode, so as to determine whether to allow the PEGC to join the PIN. If the PIN supports roaming, when the number of PINs is smaller than the number indicated by the number information of the PINs when the PEGC joins the PIN and the position of the PEGC is at the position indicated by the position information of the PIN, determining to allow the PEGC to join the PIN. If the PIN does not support roaming, when the PEGC joins the PIN, the number of PINs is smaller than the number indicated by the number information of the PINs, the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same), and the location of the PEGC is at the location indicated by the location information of the PIN, it is determined that the PEGC is permitted to join the PIN.

Mode four: it is determined whether PEGC is allowed to join the PIN according to the constraint condition C (time information of the PIN).

Illustratively, the P-NF determines the time at which the PIN is allowed to be added based on the time information of the PIN received in step S720 to determine whether the PEGC is allowed to be added to the PIN. If the time of adding the PIN by the PEGC is not within the duration (valid time) indicated by the time information of the PIN, for example, the time is earlier than the starting time (start time) or later than the ending time (end time), the PEGC is refused to add the PIN; otherwise, PEGC is allowed to join the PIN.

Further, in combination with mode one, mode two, mode three and mode four, P-NF may also determine whether PEGC is allowed to join the PIN according to the restriction conditions c+d or a+c or b+c or a+b+c or a+c+d or b+c+d or a+b+c+d.

Illustratively, the P-NF determines whether the PIN supports roaming according to mode one and whether PEGC addition of the PIN is within an allowed time according to mode four to determine whether PEGC addition of the PIN is allowed. If the PIN supports roaming, when the PEGC is in the time indicated by the time information of the PIN when the PEGC joins the PIN, it is determined that the PEGC is allowed to join the PIN. If the PIN does not support roaming, it is determined that the PEGC is allowed to join the PIN when the PEGC is at a time indicated by time information of the PIN when joining the PIN, and the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same).

The P-NF determines whether the PEGC is at a position indicated by the position information of the PIN according to the second mode, and determines whether the PEGC is allowed to be added to the PIN according to the fourth mode, to determine whether the PEGC is allowed to be added to the PIN. And if the position of the PEGC is at the position indicated by the position information of the PIN and the PEGC is at the time indicated by the time information of the PIN when the PEGC joins the PIN, determining to allow the PEGC to join the PIN.

By way of example, the P-NF determines whether the PIN is overloaded when the PEGC joins the PIN according to the third mode, and determines whether the PEGC joins the PIN within the allowable time according to the fourth mode, to determine whether to allow the PEGC to join the PIN. If the number of PINs is smaller than the number indicated by the number information of PINs when the PEGC is added to the PIN and the PEGC is at the time indicated by the time information of the PIN when the PEGC is added to the PIN, determining that the PEGC is allowed to be added to the PIN.

The P-NF determines whether the PIN supports roaming according to the first mode, determines whether the PEGC is located at a position indicated by the position information of the PIN according to the second mode, and determines whether the PEGC is added to the PIN within an allowable time according to the fourth mode, so as to determine whether to allow the PEGC to be added to the PIN. If the PIN supports roaming, when the PEGC is in the time indicated by the time information of the PIN and the position of the PEGC is in the position indicated by the position information of the PIN, determining that the PEGC is allowed to join the PIN. If the PIN does not support roaming, when the PEGC is in the time indicated by the time information of the PIN when the PEGC joins the PIN, the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same), and the location of the PEGC is in the location indicated by the location information of the PIN, it is determined that the PEGC is permitted to join the PIN.

The P-NF determines whether the PIN supports roaming according to the first mode, determines whether the PIN is overloaded when the PEGC joins the PIN according to the third mode, and determines whether the PEGC joins the PIN within the allowed time according to the fourth mode, so as to determine whether to allow the PEGC to join the PIN. If the PIN supports roaming, when the PEGC is in the time indicated by the time information of the PIN when the PEGC is added to the PIN and the number of PINs when the PEGC is added to the PIN is smaller than the number indicated by the number information of the PIN, determining to allow the PEGC to be added to the PIN. If the PIN does not support roaming, determining that the PEGC is allowed to join the PIN when the PEGC is in the time indicated by the time information of the PIN when the PEGC joins the PIN, the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same), and the number of PINs when the PEGC joins the PIN is smaller than the number indicated by the number information of the PIN.

The P-NF determines whether the PEGC is in a position indicated by the position information of the PIN according to the second mode, determines whether the PIN is overloaded when the PEGC is added to the PIN according to the third mode, and determines whether the PEGC is added to the PIN within the allowable time according to the fourth mode, so as to determine whether to allow the PEGC to be added to the PIN. And when the amount of PINs is smaller than the amount indicated by the amount information of the PINs when the PEGC is added to the PINs, the PEGC is at the time indicated by the time information of the PINs when the PEGC is added to the PINs, and the position of the PEGC is at the position indicated by the position information of the PINs, determining that the PEGC is allowed to be added to the PINs.

The P-NF determines whether the PIN supports roaming according to the first mode, determines whether the PEGC is located at a position indicated by the position information of the PIN according to the second mode, determines whether the PIN is overloaded when the PEGC is added to the PIN according to the third mode, and determines whether the PEGC is added to the PIN within an allowable time according to the fourth mode, so as to determine whether the PEGC is allowed to be added to the PIN. If the PIN supports roaming, when the PEGC is in the time indicated by the time information of the PIN when the PEGC joins the PIN, the position of the PEGC is in the position indicated by the position information of the PIN, and the number of PINs when the PEGC joins the PIN is smaller than the number indicated by the number information of the PIN, determining that the PEGC is allowed to join the PIN. If the PIN does not support roaming, when the PEGC is in the time indicated by the time information of the PIN when the PEGC is added to the PIN, the home network of the PEMC is the same as the home network of the PEGC (e.g., PLMN IDs of the PEMC and the PEGC are the same), the position of the PEGC is in the position indicated by the position information of the PIN, and the number of PINs when the PEGC is added to the PIN is smaller than the number indicated by the number information of the PIN, it is determined that the PEGC is allowed to be added to the PIN.

Optionally, the P-NF sends a subscription request message to the UDM or the UDR, the subscription request message including a PEGC ID for checking whether the PEGC supports the PEGCF function, and in case it is determined that the PEGCF function is supported, requesting updating of the PEGC ID into the UDM or the UDR.

Optionally, the P-NF updates the context of the PIN and adds the PEGC ID to the PIN.

Optionally, the P-NF sends a notification message to the AF through the NEF for notifying the PEGC of successful joining in the PIN, the notification message carrying the PIN ID and the PEGC ID.

And S781, optionally the P-NF sends a notification message to the PEGC.

Correspondingly, the PEGC receives notification messages from the P-NF.

S782, the P-NF optionally sends a notification message to the PEMC.

Correspondingly, the PEMC receives the notification message from the P-NF.

The notification messages of steps S781 and S782 include a PIN ID, a PEGC ID, and a PEMC ID, which are used to notify the PEGC that the PIN is successfully added, that is, the gateway authorized to become the PIN.

Optionally, the P-NF sends a subscription request message to the UDM or the UDR, the subscription request message including a PEGC ID for checking whether the PEGC supports the PEGCF function, and in case it is determined that the PEGCF function is supported, requesting updating of the PEGC ID into the UDM or the UDR.

Optionally, the P-NF sends a notification message to the AF through the NEF for notifying the PEGC of successful joining in the PIN, the notification message carrying the PIN ID and the PEGC ID.

The method disclosed by the application triggers the creation of the PIN through the P-AF and the PIN is created by leading the P-NF. The P-NF selects PEGC according to newly defined constraints (considering roaming scenario, number information of PINs, time information and location information), and judges whether it can join the PIN. The implementation method can avoid PEGC addition outside the PINE (or PEGC) quantity saturation and PIN duration, so that PIN management is more standardized, and a good PIN running environment is ensured.

Next, taking a management scenario of a PIN on the 5GC side as an example, the creation of the PIN is triggered by a network element (e.g., P-AF) in the 5GC, and the PIN is created by P-NF dominance, and management of the PIN (e.g., PEGC) is performed by a terminal device (e.g., PEMC or pemc+pegc). Unlike the above-described method 700, the execution body of the PINE management is changed from P-NF to a terminal device (e.g., PEMC or pemc+pegc).

Fig. 8 is a flowchart of a third communication method 800 according to an embodiment of the present application, as shown in fig. 8, specifically including the following steps.

S810, the pin completes registration in the core network.

It should be understood that registration of pins primarily refers to authentication and authorization of PEMCs, PEGCs, and other pins.

S820, the AF sends a PIN establishment request message to the P-NF.

Correspondingly, the P-NF receives a PIN establishment request message from the AF.

The PIN establishment request message is used for requesting the P-NF to establish the PIN in the 5GC network, and comprises the information of the PEMC and the information of the PIN to be established.

Illustratively, the information of the PEMC includes a PEMC ID, and the information of the PIN to be established includes one or more of the following: constraint a, constraint B, and constraint C.

Specifically, the constraint a is location information for indicating a location where the PIN is permitted to be added. The constraint B is a quantity information indicating the number of maximum PINs that the PIN is allowed to access. Alternatively, the number of maximum PEMCs or the number of maximum PEGCs. The constraint C is time information for indicating time information of the PIN, such as the duration of the PIN, or the start time of the PIN, and the end time.

Optionally, the P-NF may also autonomously configure or determine the information of the PIN to be established.

S830, the P-NF creates a PIN and assigns a PIN ID.

Wherein the PIN ID is associated with the PEMC ID.

Optionally, the P-NF sends a PIN creation response message to the AF for notifying the AF of the completion of the PIN creation, the PIN creation response message including the PIN ID and the PEMC ID.

It should be noted that, the specific implementation manner of the steps S810-S830 may refer to the steps S710-S730 in the method 700, and are not repeated herein for brevity.

S840, the P-NF sends a notification message to the PEMC.

Correspondingly, the PEMC receives the notification message from the P-NF.

Wherein a notification message is used to notify the PEMC that the creation of the PIN is complete, the notification message including a PIN ID, information of the PIN to be established, such as one or more of constraint a, constraint B, or constraint C.

Optionally, before the P-NF sends the notification message to the PEMC, the P-NF may determine whether the current PIN supports roaming according to a pre-configured policy; the P-NF sends indication information to the PEMC, and the indication information is used for indicating the PEMC to acquire the home network information of the PEGC, judging whether the home networks of the PEGC and the PEMC are the same, and further determining whether the PEGC is allowed to join the PIN.

S851, the PEMC sends a connection request message to the PEGC.

Correspondingly, the PEGC receives a connection request message from the PEMC.

The connection request message may be a connection request message for initiating a connection between the PEGC and the PEMC.

Optionally, the connection request message includes home network information of the PEMC, such as PLMN ID of the PEMC, GPSI, SUCI, SUPI, etc.

S852, optionally, the PEGC determines whether the home networks of the PEMC and the PEGC are the same, to determine whether the connection is established between the two.

Illustratively, the PEGC compares the home network information of the PEMC with the own home network information, and if the same is the constraint D), it is determined to establish a connection, i.e., performs step S853.

It should be noted that, the connection between the PEMC and the PEGC may be Wi-Fi, bluetooth, 5G Prose, etc., which is not particularly limited in the present application.

S853, PEGCF sends a connection response message to PEMCF.

Correspondingly, the PEMCF receives a connection response message from the PEGCF.

The connection response message may be a connection response message including location information of the PEGC and home network information of the PEGC, for example, PLMN ID, GPSI, SUCI, SUPI, etc. of the PEGC.

Optionally, the connection response message further includes a PEGC ID.

It should be understood that the above steps S851 to S853 are processes in which the PEMC discovers the PEGC, i.e., establishes a connection between the PEMC and the PEGC.

S854, PEMC determines whether PEGC is allowed to join the PIN.

One possible implementation manner, if the PEGC performs step S852, that is, the PEGC and the PEMC home network are the same, the method is applicable to a scenario where the PIN does not support roaming. At this point, the PEMC determines whether to allow the PEGC to join the PIN according to one or more of the constraints A, B or C.

Alternatively, the PEMC may also determine whether the PEGC and the PEMC belong to the same network, which is not particularly limited in the present application.

In another possible implementation, if the PEGC does not perform step S852, the PEMC determines whether to allow the PEGC to join the PIN according to one or more of the constraints A, B, C or D.

Specifically, the PEMC may refer to step S770 in the method 700 described above for an implementation of determining whether to allow PEGC to join PIN according to one or more of the constraints A, B, C or D. The difference between step S854 and step S770 is that the execution body is changed from P-NF to PEMC, and for brevity, the details are not repeated here.

S860, the PEMC sends an authorization request message to the P-NF.

Correspondingly, the P-NF receives an authorization request message from the PEMC.

The authorization request message includes a PEGC ID, which is used to request the P-NF to join the PEGC to the PIN.

Optionally, the authorization request message further includes one or more of: PEGC's location information, PEGC's and PEMC's home network information (i.e., constraint D), PIN ID, or PEMC ID.

S870, optionally, the P-NF determines whether to allow PEGC to join the PIN based on one or more of the constraints A, B, C or D. That is, the P-NF may perform a secondary determination on whether the PEGC can add the PIN, and for a specific implementation, reference may be made to step S770 in the above method 700. For brevity, the description is not repeated here.

S881, optionally, the P-NF sends a notification message to the PEGC.

Correspondingly, the PEGC receives notification messages from the P-NF.

S882, optionally, the P-NF sends a notification message to the PEMC.

Correspondingly, the PEMC receives the notification message from the P-NF.

The notification messages of steps S881 and S882 include PIN ID, PEGC ID and PEMC ID, and are used to notify PEGC that the PIN is successfully added, i.e. the gateway authorized to become the PIN.

Note that, the P-NF may update the PIN Profile or the context data of the PIN by referring to the methods 400 to 700, which is not particularly limited in the present application.

Optionally, the P-NF sends a subscription request message to the UDM or the UDR, the subscription request message including a PEGC ID for checking whether the PEGC supports the PEGCF function, and in case it is determined that the PEGCF function is supported, requesting updating of the PEGC ID into the UDM or the UDR.

Optionally, the P-NF sends a notification message to the AF through the NEF for notifying the PEGC of successful joining in the PIN, the notification message carrying the PIN ID and the PEGC ID.

The method disclosed by the application triggers the creation of the PIN through P-AF and the PIN is created by the PEMC domination. The PEMC selects PEGC according to newly defined limiting conditions (considering roaming scenario, number information of PINs, time information and location information), and judges whether it can join the PIN. The implementation method can avoid PEGC addition outside the PINE (or PEGC) quantity saturation and PIN duration, so that PIN management is more standardized, and a good PIN running environment is ensured.

Next, taking a management scenario of a PIN on the PIN AS side AS an example, the creation of the PIN is triggered by the PEMC, and is dominated by an application server of the PIN (e.g., PIN AF/AS), and management of the PIN (e.g., PEGC).

Fig. 9 is a flowchart of a fourth communication method 900 according to an embodiment of the present application, as shown in fig. 9, specifically including the following steps.

S911-S912, PEMC and PEGC complete registration in PIN AS or PIN AF, respectively.

It should be understood that registration of pins primarily refers to authentication and authorization of PEMCs, PEGCs, and other pins.

Wherein, the PEMC and the PEGC send a registration request message to the PIN AS or the PIN AF, respectively, in the registration process, carrying the PIN ID, the PIN configuration data (PIN profile), and the home network information (for example, PLMNID, GPSI, SUCI, SUPI of the PEMC, etc., i.e., the constraint D). Meanwhile, the registration request message sent by the PEGC may further include location information of the PEGC.

Optionally, other PINs may also complete registration in the PIN AS or PIN AF, and the specific registration is similar to the registration of PEGC and PEMC. Other pins herein refer to pins other than PEMC and PEGC.

It should be noted that, the specific implementation manner of PEMC, PEGC and other pin registration, and the information included in the pin profile may be described with reference to step S510 in the above method 500, which is not repeated herein for brevity.

S920, the PIN AF or the PIN AS creates a PIN and assigns a PIN ID.

The specific creation manner of the PIN may refer to S830 of the method 800 described above. For example, the PEMC sends a PIN creation request message to the PIN AS or PIN AF for requesting the creation of the PIN. For brevity, the description is not repeated here.

S930, the PIN AS or PIN AF locally configures information of the PIN to be established.

Illustratively, the information of the PIN to be established includes one or more of constraint a, constraint B, or constraint C.

Specifically, the constraint a is location information for indicating a location where the PIN is permitted to be added. The constraint B is a quantity information indicating the number of maximum PINs that the PIN is allowed to access. Alternatively, the number of maximum PEMCs or the number of maximum PEGCs. The constraint C is time information for indicating time information of the PIN, such as the duration of the PIN, or the start time of the PIN, and the end time.

S940, the PIN AS or PINAF determines whether PEGC is allowed to access the PIN.

Specifically, the implementation of the PIN AS or PINAF to determine whether to allow PEGC to join the PIN according to one or more of the constraints A, B, C or D may refer to step S770 in the above-described method 700. The difference between step S940 and step S770 is that the execution body is changed from P-NF to PIN AS or PINAF, and for brevity, the details are not repeated here.

S951, optionally, the P-NF sends a notification message to the PEGC.

Correspondingly, the PEGC receives notification messages from the P-NF.

S952, optionally, the P-NF sends notification messages to the PEMC.

Correspondingly, the PEMC receives the notification message from the P-NF.

The notification messages of steps S951 and S952 may include a PIN ID, a PEGC ID, and a PEMC ID, for notifying the PEGC that the PIN was successfully added, that is, the gateway authorized to become the PIN.

Optionally, the PIN AS or PIN AF sends PIN service specific parameter to the UDR or UDM, carrying the PIN ID, PEGC ID, default QoS requirements, and PINE communication duration, for obtaining policy control information for the PEGC. In addition, in the case where it is determined that UDR or UDM supports PEGCF function, updating of PEGC ID into UDM or UDR is requested.

In the method disclosed by the application, the PIN is established by leading the PIN AS or the PIN AF, and the PEGC is selected to judge whether the PIN can be added. The limiting condition that PEGC is added into the network is increased by the newly added PEGC, enhancement is carried out on the PIN AS side or the PIN AF side, the newly added judging logic ensures that PEMC and PEGC operate in a non-roaming scene, and the PEGC addition beyond the PINPINE (PEGC) quantity saturation and the PIN duration time is avoided, so that PIN management is more standardized.

In summary, the technical scheme of the application newly increases the limiting condition of PEGC access to PIN, and judges whether PEGC can access to PIN according to the limiting condition, so that PEGC and PEMC existing in the same PIN belong to the same operator to avoid roaming condition, and ensure PIN in PIN is not overloaded, and PEGC is accessed within PIN duration time to avoid PIN paralysis or overload.

It should be noted that the above-mentioned communication methods may be implemented separately or in combination, which is not particularly limited in the present application. For example, the communication methods 600 to 800 may be combined, taking the creation of a PIN on the 5GC side and PEGC management scenario as an example, to implement a core network element (for example, P-NF), or the terminal device (for example, PEMC or pemc+pegc) determines whether the PEGC can join the PIN according to the first information. For another example, the communication methods 600 and 900 may be combined, taking the creation of a PIN on the PIN AS side and PEGC management scenario AS an example, to implement the PIN AF/AS to determine whether the PEGC can join the PIN according to the first information.

It should be noted that the above-provided communication methods 700 to 900 may be regarded as a flow of the above-described specific refinement of the communication method 600. The related concepts and steps involved in the communication methods 600 to 900 may be referred to each other, and the disclosure will not be repeated for some parts.

Fig. 10 is a schematic diagram of a network architecture of AUN3 and 5GC according to an embodiment of the present application. As shown in fig. 10, the network architecture includes an AUN3 device, a 5G-RG, a wireless access gateway function (wireline access gateway function, W-AGF) network element, and a 5GC network. Wherein, 5GC network includes: AMF network element, SMF network element, UPF network element, etc. The W-AGF is a wired access gateway function, is an access network function of non-3 GPP, and is contained in W-5 GAN.

Specifically, the AUN3 device establishes a connection with the 5G-RG, and when the 5G-RG transmits data for the AUN3 device, the 5G-RG accesses the 5GC through the W-AGF, for example, registration management is performed on the AUN3 device through the AMF network element. It should be noted that the 5G-RG itself may also be connected to a 3GPP access network device, such as a (R) AN, but when the 5G-RG serves AUN3, the message is not transmitted through the (R) AN, but through the W-AGF. In addition, the descriptions of the functions of the AMF, SMF and UPF network elements may refer to the descriptions of the corresponding network element functions in fig. 1, which are not described herein. Wherein N1, N2, N3, N4, N6, N11, Y4, and Yt' are interface sequence numbers, and the meaning of these interface sequence numbers can be referred to the meaning defined in the 3GPP standard protocol, which is not limited herein.

Fig. 11 is a schematic flow chart of a fifth communication method provided in the embodiment of the present application, in this implementation manner, a first device is added to determine whether to execute a registration flow of an authenticatable non-3 GPP device according to first information, so that access of authenticatable non-3 GPP devices of different operators to a core network can be avoided, a more standardized management flow is realized, and an orderly network operation environment is ensured. As shown in fig. 11, the first device is a 5G-RG, the authenticatable non-3 GPP device is an AUN3 device, and the wireless access gateway function network element is a W-AGF as an example, and the method includes the following steps, and the details of the steps are not described in detail in reference to the existing protocol.

S1110, the 5G-RG executes the registration procedure.

The implementation of the specific registration procedure may refer to an existing protocol, and for brevity, will not be described herein. It should be appreciated that after the 5G-RG completes registration, the AMF has the context of the 5G-RG.

S1121,5G-RG and AUN3 establish an L2 connection, such as through Wi-Fi.

Illustratively, a non-3 GPP authentication procedure is triggered, such as a local authentication or an 802.1x based authentication procedure. This may be accomplished, for example, by the AUN3 device sending an EAPOL start frame to the 5G-RG or the 5G-RG receiving a frame from an unknown MAC address. The AUN3 device sends an EAP-Resp/identity to the 5G-RG, including a network access identifier (network access identifier, NAI) in the form of username@realm. The MCC and MNC portion in the realm part of the NAI may indicate home network information of AUN 3.

It should be appreciated that the 5G-RG stores AUN3 information during L2 setup, such as local authentication or 802.1X authentication (e.g., the device successfully authenticates and may establish an L2 connection).

It should be noted that, the present application does not specifically limit the order of acquiring the NAI, executing the authentication procedure, and judging whether to execute the AUN3 registration procedure. Typically, after establishing an L2 connection with AUN3, the 5G-RG initiates a registration procedure for AUN3 to the core network. In the present application, the 5G-RG performs the following step S1122 before initiating the registration procedure.

Optionally, the AUN3 device sends home network information of AUN3 to the 5G-RG, where the home network information of AUN3 may be sent separately or indicated in the realm part of the NAI. For example, the home network information may be PLMN ID, NID of AUN3, or characterized by the realm part of NAI, specifically, the home network may be identified by the MCC and MNC part of the realm part, and in a non-public network scenario, the home network may also be identified by the MCC, MNC and NID in the realm part. That is, the home network information of the AUN3 may be determined according to the identification information of the AUN3 (e.g., realm part of NAI), or the identification information of the home network of the AUN 3.

S1122, the 5G-RG determines whether to execute the registration procedure of AUN3 according to the first information.

Wherein the first information includes home network information of AUN3, and the home network information of AUN3 is used to indicate a home network of AUN 3.

In a first implementation, the 5G-RG refuses to perform the registration procedure of AUN3 when it is determined that the home network of AUN3 is different from the home network of 5G-RG.

In one example, the home network information of the AUN3 includes identification information of a home network of the AUN3, and the 5G-RG determines that the home network of the AUN3 is different from the home network of the 5G-RG, including: the identification information of the home network of the 5G-RG and the identification information of the home network of the AUN3 are not identical.

In one example, refusing to perform the registration procedure of AUN3 includes: the 5G-RG sends rejection indication information to the AUN3 to indicate rejection to initiate the registration procedure. Optionally, the reject indication information carries a cause value, where the cause value indicates that the reject cause is: the home network of AUN3 is not the same as the home network of 5G-RG. This prevents AUN3 from periodically initiating a connection to 5G-RG. This is because the existence of the cause value may cause AUN3 to consider that the non-single registration fails, and the L2 connection request is not periodically initiated to the 5G-RG later. Based on this cause value, AUN3 will realize that this 5G-RG is not accessible and will not attempt to initiate a connection anymore.

In another example, refusing to perform the registration procedure of AUN3 includes: the 5G-RG deletes the information of AUN3 stored at the time of L2 connection establishment. This saves storage space.

For example, the 5G-RG compares whether the home network information of itself is consistent with the home network information of AUN3, and when so, the 5G-RG performs a subsequent registration procedure for AUN3 and sends an AMF identifier serving itself to the W-AGF in step S1130; when the registration is inconsistent, the 5G-RG refuses to execute the subsequent registration flow for the AUN3, and optionally sends a refusal indication message to the AUN 3. The reject indication message optionally carries a cause value, and the cause of the reject is characterized by that the home network of the AUN3 is different from the home network of the 5G-RG.

It should be appreciated that the two examples provided above may be used in combination, for example, the 5G-RG may delete both stored AUN3 information and send reject indication information to the AUN3 device, as the application is not limited in this regard.

In a second implementation, when the 5G-RG determines that the home network of AUN3 is the same as the home network of the 5G-RG, a registration procedure of AUN3 is performed.

In one example, the home network information of AUN3 includes identification information of a home network of AUN3, and the 5G-RG determines that the home networks of AUN3 and 5G-RG are the same, including: the identification information of the home network of the 5G-RG is the same as the identification information of the home network of the AUN 3.

It should be noted that, the above step S1122 is performed when the 5G-RG confirms that the device is AUN3, and is not performed when the device is namn 3.

Based on the second implementation manner, when the 5G-RG determines that the home network of the AUN3 is the same as the home network of the 5G-RG, the registration procedure of the AUN3 is executed, and further, the subsequent registration procedure, that is, steps S1130 to S1170, may be executed.

S1130, the 5G-RG sends the NAS registration request message to the AMF through the W-AGF, and the corresponding AMF receives the NAS registration request message.

Wherein the NAS registration request message includes the sui (or 5G-GUTI, if available) of the AUN3 device, and a device capability indication of the AUN3 device. For example, the 5G-RG constructs SUCI from NAI received in EAP-Identity.

For example, when the 5G-RG sends NAS Registration request to the AMF, the guim is provided to the W-AGF, so that the W-AGF selects the same service AMF as the 5G-RG for the AUN3 device based on the guim provided by the 5G-RG, that is, provides the registration service for the AUN3 device through the same AMF, and defines that the AUN3 and the 5G-RG are under the same service AMF, so that signaling of interaction between multiple AMFs is saved. Alternatively, if the 5G-RG does not provide the GUAMI to the W-AGF, the W-AGF may select a service AMF different from the 5G-RG for the AUN3 device, which is equivalent to having two AMFs serving the Non-3GPP access service, and may generate a very tedious signaling interaction in the subsequent session establishment and other processes.

S1140, AMF selects AUSF. For example, the AMF selects AUSF as specified in TS 23.501, 6.3.4, such as using the home network identification of the sui in S1130, and/or the AUSF Group ID in the SUPI, and/or the scope of the SUPI. The specific implementation is not described in detail.

In S1150, EAP-based authentication is performed between the AUSF and AUN3 devices, and specific implementation is described with reference to the existing protocol, which is not described here.

It should be appreciated that once the AUN3 device passes the authentication, the AUSF will provide relevant security related information to the AMF. Only after successful authentication should the AUSF return SUPI (which corresponds to the NAI containing the AUN3 device username and the realm defined in TS 33.501) to the AMF.

S1160, the AMF executes the registration process of the AUN3 device.

S1170, the AMF sends NAS registration response information to the 5G-RG, and the corresponding 5G-RG receives the NAS registration response information from the AMF. For example, the registration response message may indicate that a request for access 5GC of the AUN3 device is accepted, at which point the AUN3 device registration is complete. Further, the 5G-RG stores the 5G-GUTI of the AUN3 device. In this implementation, the number of AUN3 devices is not limited, and when there are multiple AUN3 devices requesting access to the 5GC through the 5G-RG, the above steps are performed once for each AUN3 device by the 5G-RG, and the 5G-RG maintains separate NAS connections for the 5G-RG and each AUN3 device, respectively.

According to the above technical solution, a method for registering AUN3 in 5GC is provided, wherein the method includes that 5G-RG confirms PLMN of AUN3, and AUN3 devices in other PLMN networks are prevented from joining the 5GC. In addition, the method for providing GUMAI to W-AGF by 5G-RG limits AUN3 and 5G-RG to be under the same service AMF, thereby saving interactive signaling between multiple AMFs.

The embodiments of the communication method according to the present application are described in detail above with reference to fig. 5 to 11, and the method for obtaining information is mainly described in terms of interaction between the devices. It will be appreciated that each device, in order to implement the above-described functions, includes corresponding hardware structures and/or software modules that perform the respective functions. A communication device side embodiment of the present application will be described in detail below with reference to fig. 12 and 13. It is to be understood that the description of the device embodiments corresponds to the description of the method embodiments, and that parts not described in detail can therefore be seen in the preceding method embodiments.

Fig. 12 is a schematic block diagram of a communication apparatus 1000 provided in an embodiment of the present application. As shown in fig. 12, the apparatus 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver 1010 may be obtained locally or may communicate with the outside. The processing unit 1120 is used for performing data processing. The transceiver unit 1010 may also be referred to as a communication interface, a transceiver module, or the like.

In one possible design, the apparatus 1000 may implement steps or processes performed by the first device in the above method embodiments, where the processing unit 1020 is configured to perform operations related to processing by the first device in the above method embodiments, and the transceiver unit 1010 is configured to perform operations related to transceiver by the first device in the above method embodiments.

Illustratively, the processing unit 1020 is configured to obtain the first information, and determine whether the PEGC can join the PIN according to the first information.

Wherein, obtaining the first information includes: receiving the first information from the external device through the transceiving unit 1010; alternatively, the first information is configured and obtained locally by the processing unit 1020.

It should be appreciated that the apparatus 1100 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the apparatus 1100 may be specifically configured as the transmitting end in the foregoing embodiment, and may be used to perform each flow and/or step corresponding to the transmitting end in the foregoing method embodiment, or the apparatus 1100 may be specifically configured as the receiving end in the foregoing embodiment, and may be used to perform each flow and/or step corresponding to the receiving end in the foregoing method embodiment, which is not repeated herein.

The apparatus 1100 of each of the above embodiments has a function of implementing the corresponding step performed by the transmitting end in the above method, or the apparatus 1100 of each of the above embodiments has a function of implementing the corresponding step performed by the receiving end in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, etc., may be replaced by a processor, to perform the transceiver operations and related processing operations in the various method embodiments, respectively.

The transceiver unit may be a transceiver circuit (for example, may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit. In the embodiment of the present application, the apparatus in fig. 10 may be the receiving end or the transmitting end in the foregoing embodiment, or may be a chip or a chip system, for example: system on chip (SoC). The transceiver unit may be an input/output circuit or a communication interface. The processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.

Fig. 13 shows a schematic block diagram of a communication device 2000 provided by an embodiment of the present application. The apparatus 2000 includes a processor 2010 and a transceiver 2020. Wherein the processor 2010 and the transceiver 2020 are in communication with each other via an internal connection, the processor 2010 is configured to execute instructions to control the transceiver 2020 to transmit signals and/or receive signals.

Optionally, the apparatus 2000 may further include a memory 2030, where the memory 2030 communicates with the processor 2010 and the transceiver 2020 through an internal connection. The memory 2030 is for storing instructions and the processor 2010 may execute the instructions stored in the memory 2030.

In a possible implementation manner, the apparatus 2000 is configured to implement the respective flows and steps corresponding to the first device in the foregoing method embodiment.

It should be understood that the apparatus 2000 may be specifically the first device in the foregoing embodiment, and may also be a chip or a chip system of the first device. Correspondingly, the transceiver 2020 may be a transceiver circuit of the chip, which is not limited herein. Specifically, the apparatus 2000 may be configured to perform each step and/or flow corresponding to the sending end or the receiving end in the above method embodiments.

Alternatively, the memory 2030 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store information of the device type. The processor 2010 may be configured to execute instructions stored in a memory, and when the processor 2010 executes the instructions stored in the memory, the processor 2010 is configured to perform the steps and/or processes of the method embodiments corresponding to the transmitting side or the receiving side described above.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method. To avoid repetition, a detailed description is not provided herein.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capability. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. The processor in the embodiments of the present application may implement or execute the methods, steps and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to a method provided by an embodiment of the present application, the present application also provides a computer program product, including: computer program code which, when run on a computer, causes the computer to perform the method of the above-described illustrated embodiment.

According to the method provided by the embodiment of the present application, the present application further provides a computer readable medium storing a program code, which when run on a computer, causes the computer to perform the method in the above-described illustrated embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (35)

1. A method of communication, comprising:

the first equipment acquires first information;

and the first equipment determines whether the personal internet of things element PEGC with the gateway function can join the personal internet of things PIN according to the first information.

2. The method of claim 1, wherein the first information comprises one or more of:

home network information of a personal internet of things element PEMC having a management function and home network information of the PEGC; or location information of the PIN; or time information of the PIN; or the number information of the PIN;

the home network information of the PEMC is used for indicating the home network of the PEMC, the home network information of the PEGC is used for indicating the home network of the PEGC, the position information of the PIN is used for indicating the position where the PIN is allowed to be added, the time information of the PIN is used for indicating the time when the PIN is allowed to be added, and the number information of the PINs is used for indicating the number of personal internet of things elements PINs which the PIN supports to be added.

3. The method of claim 1 or 2, wherein when the first information includes information indicating a home network of the PEMC and a home network of the PEGC, the home network information of the PEMC and the home network information of the PEGC include one or more of:

The identification information of the PIN, the context information of the PIN, the identification information of the PEGC, the identification information of the PEMC, the identification information of the home network of the PEGC, or the identification information of the home network of the PEGC.

4. A method according to any one of claims 1 to 3, wherein the first device determining from the first information whether the PEGC can join a PIN, comprises:

when the home network of the PEGC is the same as the home network of the PEMC, the first device determines that the PEGC is able to join the PIN.

5. The method of any of claims 2 to 4, wherein the PIN location information comprises one or more of:

a geographic location; a network identification code NID; tracking area identification TAI; cell identification; a network selection group identification GIN; a Cell Access Group (CAG) identifier; slicing information; data network name information; coordinate value information; or longitude and latitude information.

6. The method of claim 5, wherein the first device determining whether the PEGC can join a PIN based on the first information comprises:

the first device determining a location of the PEGC;

When the position of the PEGC is located at the position indicated by the position information, the first device determines that the PEGC can join the PIN.

7. The method of any of claims 2 to 6, wherein the time information of the PIN comprises one or more of: start time and end time; or, duration.

8. The method of claim 7, wherein the first device determining whether the PEGC can join a PIN based on the first information comprises:

the first device determining when the PEGC joins the PIN;

when the time when the PEGC joins the PIN belongs to the time indicated by the time information, the first device determines that the PEGC is able to join the PIN.

9. The method of any of claims 2 to 8, wherein the PIN quantity information includes one or more of:

maximum number of PINs; maximum number of PEGCs; alternatively, the maximum number of PEMCs.

10. The method of claim 9, wherein the first device determining whether the PEGC can join a PIN based on the first information comprises:

the first device determining the amount of PINs that have joined the PIN;

When the number of PINs that have been added to the PIN is smaller than the number indicated by the number information, the first device determines that the PEGC can access the PIN.

11. The method according to any one of claims 2 to 10, wherein when the first device is a core network device, the first device obtains first information, including:

the first device receives home network information of the PEMC and home network information of the PEGC from the PEMC, an application function device, a unified data repository device, or a unified data management device.

12. The method of claim 11, wherein the first device obtains first information, further comprising:

the first device obtains one or more of time information of the PIN, number information of the PIN or position information of the PIN from local; or,

the first device receives one or more of time information of the PIN, number information of the PIN, or location information of the PIN from an application function device, a unified data repository device, or a unified data management device.

13. The method according to any of claims 2 to 12, wherein when the first device is a core network device, the method further comprises:

The first device determines whether the PIN supports roaming according to policy information;

in the event that the PIN does not support roaming, the first device determines whether the home network of the PEMC is the same as the home network of the PEGC.

14. The method of claim 13, wherein the method further comprises:

the first device configures the policy information locally; or,

the first device receives the policy information from a policy control device, a unified data store device, or a unified data management device.

15. The method of any of claims 2 to 10, wherein when the first device is the PEMC, the first device obtains first information, comprising:

the first device receives one or more of time information of the PIN, number information of the PIN or position information of the PIN from a core network device; or alternatively

The first device obtains one or more of time information of the PIN, number information of the PIN, or location information of the PIN from the local.

16. The method of claim 15, wherein the first device obtains first information, further comprising:

The PEMC sends a connection request message to the PEGC, wherein the connection request message is used for requesting to establish connection with the PEGC;

the PEMC receives a connection response message from the PEGC, the connection response message including home network information of the PEGC.

17. The method according to any one of claims 2 to 10, wherein when the first device is an application function device or an application server, the first device obtains first information, comprising:

the first device obtains one or more of time information of the PIN, number information of the PIN, or location information of the PIN from the local.

18. The method of claim 17, wherein the first device obtains first information, further comprising:

the first device receives home network information of the PEMC from the PEMC and receives home network information of the PEGC from the PEGC.

19. The method of claim 6, wherein when the first device is a core network device, the first device determining the location of the PEGC comprises:

the first device receives location information of the PEGC from the PEMC, unified data management device, or unified data store device;

And the first equipment determines the position of the PEGC according to the position information of the PEGC.

20. The method of claim 6, wherein when the first device is the PEMC, the first device determining a location of the PEGC comprises:

the first device sends an inquiry request message to the PEMC, wherein the inquiry request message is used for requesting to acquire the position information of the PEGC;

the first device receives location information of the PEGC from the PEGC;

the first device determines the position of the PEGC according to the position information of the PEGC and determines the position of the PEGC according to the position information of the PEGC.

21. The method of claim 6, wherein when the first device is an application function device or an application server, the first device determining the location of the PEGC comprises:

the first device receives location information of the PEGC from the PEGC;

and the first equipment determines the position of the PEGC according to the position information of the PEGC.

22. A method of communication, comprising:

the first equipment acquires first information;

the first device determines whether to execute the registration flow of the authenticatable non-3 GPP device according to the first information.

23. The method of claim 22, wherein the first information includes home network information of the authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device indicating a home network of the authenticatable non-3 GPP device, the first device determining whether to perform a registration procedure of the authenticatable non-3 GPP device according to the first information, comprising:

and when the first equipment judges that the home network of the authenticatable non-3 GPP equipment is different from the home network of the first equipment, refusing to execute the registration flow of the authenticatable non-3 GPP equipment.

24. The method of claim 22, wherein the first information includes home network information of the authenticatable non-3 GPP device, the home network information of the authenticatable non-3 GPP device indicating a home network of the authenticatable non-3 GPP device, the first device determining whether to perform a registration procedure of the authenticatable non-3 GPP device according to the first information, comprising:

and when the first equipment judges that the home network of the authenticatable non-3 GPP equipment is the same as the home network of the first equipment, executing a registration flow of the authenticatable non-3 GPP equipment.

25. The method of claim 23, wherein the refusing to perform the registration procedure for the authenticatable non-3 GPP device comprises:

and the first equipment sends rejection indication information to the authenticatable non-3 GPP equipment so as to indicate rejection to initiate a registration flow.

26. The method of claim 25, wherein the reject indication information carries a cause value indicating that the home network of the authenticatable non-3 GPP device is not the same as the home network of the first device.

27. The method of claim 23, wherein the refusing to perform the registration procedure for the authenticatable non-3 GPP device comprises:

the first device deletes locally stored information of the authenticatable non-3 GPP device.

28. The method of claim 24, wherein the method further comprises:

the first device sends an identifier of a mobility management function network element to a wireless access gateway function network element, and indicates that the mobility management function network element is used for executing a registration process of the authenticatable non-3 GPP device, wherein the mobility management function network element serves the first device.

29. The method according to any one of claims 1 to 7, wherein the first device is a residential gateway.

30. A communication device, comprising:

a unit for implementing the method of any one of claims 1 to 21, or a unit for implementing the method of any one of claims 22 to 29.

31. A communication device, comprising: a processor coupled to the memory;

the processor for executing a computer program stored in the memory to cause the apparatus to perform the method of any one of claims 1 to 21 or to cause the apparatus to perform the method of any one of claims 22 to 29.

32. A communication device comprising a processor and interface circuitry for receiving signals from other communication devices than the communication device and transmitting to the processor or sending signals from the processor to other communication devices than the communication device, the processor being configured to implement the method of any one of claims 1 to 21 by logic circuitry or executing code instructions or the processor being configured to implement the method of any one of claims 22 to 29 by logic circuitry or executing code instructions.

33. A communication system, comprising:

a first device for implementing the method of any one of claims 1 to 21, or a first device for implementing the method of any one of claims 22 to 29.

34. A computer readable storage medium, characterized in that the storage medium has stored therein a computer program or instructions which, when executed by a computer, implement the method of any one of claims 1 to 21 or the method of any one of claims 22 to 29.

35. A computer program product, characterized in that the computer is caused to perform the method of any one of claims 1 to 29 when the computer reads and executes the computer program product.