Communication method and device

Abstract

An embodiment of the present application discloses a communication method and device, which includes: a first data management network element in a first network obtains identification information of a terminal device connected to an access gateway in a second network; the first data management network element obtains access parameters of the terminal device from a second data management network element corresponding to the terminal device in the second network based on the identification information; the first data management network element obtains contract data of the terminal device based on the access parameters; and the first data management network element sends the contract data of the terminal device to the access gateway.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0002] The 5G network architecture defined by the 3rd Generation Partnership Project (3GPP) not only supports terminal devices accessing the 5G core network (5GC) through wireless technologies defined by the 3GPP standard group, such as long term evolution (LTE) and 5G radio access network (RAN), but also supports the use of non-3GPP access technologies through the non-3GPP interworking function (N3IWF) or the next generation packet data gateway (ngPDG) to access the 5GC.

[0003] However, non-5GC terminal devices that do not support non-access stratum (NAS) functions or subscriber identity module (SIM) cards and are not 5GC subscribers are currently not supported to access 5GC. Summary of the Invention

[0004] This application proposes a communication method and apparatus, which can solve the problem that terminal devices that do not support SIM cards, do not support NAS functions and are not 5GC subscribers cannot access 5GC.

[0005] In a first aspect, the present application proposes a communication method, in which a terminal device accesses a first network through a second network.

[0006] The method includes:

[0007] A first data management network element in a first network obtains identification information of a terminal device connected to an access gateway in a second network. For example, the first network may be a 5G cellular communication system or a future mobile communication system such as 6G. The second network may be a campus network, a private network, or a local network, and this application does not impose any restrictions thereon.

[0008] The first data management network element obtains access parameters for the terminal device from a second data management network element corresponding to the terminal device in the second network based on the identification information. Exemplarily, the access parameters include service type information, such as at least one of IP-type service, Ethernet-type service, or unstructured-type service, service bandwidth requirements, and / or authentication parameters.

[0009] The first data management network element obtains the subscription data of the terminal device based on the access parameters. Exemplarily, the subscription data includes: a permanent identifier of the terminal device and at least one of a PDU session type, a slice type, a quality of service (QoS) parameter, and / or a data network name (DNN). The permanent identifier of the terminal device corresponds to the identification information of the terminal device.

[0010] The first data management network element sends the subscription data of the terminal device to the access gateway.

[0011] In one possible implementation, the method further includes:

[0012] The first data management network element obtains first indication information, and the first indication information is used to indicate that the terminal device is accessing the first network for the first time. Exemplarily, the first indication information may be a first access indication and / or a contract data request indication. The first access indication is used to indicate that the terminal device is establishing a connection with the first network for the first time, and it is necessary to request the contract data of the terminal device, or it is used to indicate that the access gateway does not have the contract data of the terminal device. For example, the original contract data may be lost due to failure recovery of the access gateway, and it is necessary to request the contract data of the terminal device. The contract data request indication is used to indicate that the access gateway does not have the contract data of the terminal device, and it is necessary to request the contract data of the terminal device.

[0013] In one possible implementation, the method further includes:

[0014] The first data management network element obtains second indication information, where the second indication information is used to indicate to skip authentication of the terminal device. Exemplarily, the second indication information may specifically be an indication to skip authentication.

[0015] The first data management network element sends a second indication message to an authentication service function (AUSF) network element. The AUSF network element skips authentication of the terminal device according to the second indication message.

[0016] In one possible implementation, the method further includes:

[0017] The first data management network element obtains the permanent identification of the terminal device according to the access parameters and / or identification information of the terminal device.

[0018] In a possible implementation, the terminal device does not support a SIM card, does not support the NAS function, and is not a 5GC subscriber.

[0019] In one possible implementation, the method further includes:

[0020] The first data management network element obtains the location information of the terminal device;

[0021] The first data management network element determines the second data management network element according to the location information.

[0022] In one possible implementation, the first data management network element obtains the subscription data of the terminal device according to the access parameter, including:

[0023] During the registration process, the first data management network element generates subscription data for the terminal device based on the access parameters.

[0024] In a possible implementation, the first data management network element sending the subscription data of the terminal device to the access gateway includes:

[0025] The first data management network element sends the subscription data of the terminal device to the access gateway through the user plane of the protocol data unit (PDU) session. The above-mentioned PDU session is used to transmit the subscription data, thereby realizing the transmission of the subscription data to the access gateway through the user plane. It is applicable to the situation where the subscription data contains many parameters and it is inconvenient to transmit the subscription data to the access gateway through the control plane; or

[0026] During the registration process, the first data management network element sends the subscription data of the terminal device to the access gateway, thereby transferring the subscription data to the access gateway through the control plane.

[0027] In a possible implementation, the first data management network element sends the subscription data of the terminal device to the access gateway through the user plane of the protocol data unit PDU session, including:

[0028] Through the user plane of the protocol data unit PDU session, the first data management network element sends the contract data to the session management function (SMF) network element, so that the SMF network element transmits the contract data to the access gateway through the PDU session corresponding to the first DNN. The above-mentioned first DNN is used to indicate that the PDU session is used to transmit the contract data. The first DNN is a preconfigured DNN.

[0029] In the technical solution provided by this application, the first data management network element in the first network obtains the access parameters of the terminal device based on the identification information of the terminal device (i.e., the terminal device that does not support SIM cards, does not support NAS functions, and is not a 5GC subscriber). Then, the subscription data of the terminal device is obtained based on the access parameters. The subscription data is then sent to the access gateway in the second network. This enables the terminal device that does not support SIM cards, does not support NAS functions, and is not a 5GC subscriber to access the first network through the second network.

[0030] In a second aspect, the present application further proposes a communication method, the method comprising:

[0031] The access gateway in the second network establishes a connection with the terminal device in the second network. This application does not limit the way the connection is established.

[0032] The access gateway obtains the subscription data of the terminal device from the first network. Exemplarily, the subscription data includes: a permanent identifier of the terminal device and at least one of a PDU session type, a slice type, a QoS parameter, and / or a DNN.

[0033] The access gateway accesses the first network according to the subscription data.

[0034] In one possible implementation, the method further includes:

[0035] The access gateway determines that the subscription data of the terminal device is not available locally, and therefore needs to request the subscription data of the terminal device from the first network.

[0036] In one possible implementation, the method further includes:

[0037] The access gateway determines, based on the identification information of the terminal device, that the terminal device is accessing the first network for the first time.

[0038] In one possible implementation, the method further includes:

[0039] The access gateway sends a registration request message to the first network, where the registration request message includes first indication information and / or second indication information. The first indication information is used to indicate that the terminal device accesses the first network for the first time, and the second indication information is used to indicate that authentication of the terminal device is skipped.

[0040] In a possible implementation, the access gateway obtains the subscription data of the terminal device from the first network, including:

[0041] During the registration process, the access gateway obtains the subscription data of the terminal device from the first network.

[0042] In one possible implementation, the method further includes:

[0043] The access gateway establishes a protocol data unit (PDU) session for transmitting subscription data;

[0044] The access gateway obtains the subscription data of the terminal device from the first network, including:

[0045] Through the user plane of the PDU session, the access gateway obtains the contract data of the terminal device from the first network, and realizes the transmission of the contract data to the access gateway through the user plane. It is suitable for situations where the contract data contains many parameters and it is inconvenient to transmit the contract data to the access gateway through the control plane.

[0046] In a possible implementation, in the registration process, the access gateway obtains the subscription data of the terminal device from the first network, including:

[0047] During the registration process, the access gateway obtains the permanent identification of the terminal device from the first network;

[0048] The method further includes:

[0049] The access gateway identifies the terminal device based on the permanent identifier.

[0050] The technical solution provided by this application enables the access gateway in the second network to access the first network based on the subscription data of the terminal device (i.e., the terminal device that does not support SIM cards, does not support NAS functions, and is not a 5GC subscriber) obtained from the first network. This enables the terminal device that does not support SIM cards, does not support NAS functions, and is not a 5GC subscriber to access the first network through the second network.

[0051] In a third aspect, the present application provides a communication device, comprising at least one processor, wherein the processor is configured to execute a program stored in a memory, and when the program is executed, the communication device performs:

[0052] The method as in the first aspect and its various possible implementations; or

[0053] Such as the methods in the second aspect and various possible implementations.

[0054] In a possible implementation, the communication device further includes the aforementioned memory. Optionally, the processor and the memory may be integrated together.

[0055] In another possible implementation, the memory is disposed outside the device.

[0056] In a fourth aspect, the present application proposes a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the method in the first aspect and its various possible implementations; or the computer to execute the method in the second aspect and its various possible implementations.

[0057] In a fifth aspect, the present application proposes a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method in the first aspect and its various possible implementations is executed; or the method in the second aspect and its various possible implementations is executed.

[0058] In a sixth aspect, the present application provides a communication system, comprising:

[0059] A first data management network element, configured to execute the method in the first aspect and various possible implementations thereof;

[0060] An AUSF network element, configured to communicate with the first data management network element; and

[0061] The SMF network element is used to communicate with the first data management network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 A schematic diagram of a 5G service-oriented network architecture in a possible implementation;

[0063] Figure 2 A schematic diagram of a network architecture for 3GPP access to 5GC in a possible implementation;

[0064] Figure 3 A schematic diagram of a network architecture for untrusted Non-3GPP access to 5GC in a possible implementation;

[0065] Figure 4 A schematic diagram of a network architecture for trusted WLAN access point (TWAP) access to 5GC in one possible implementation;

[0066] Figure 5 A flow chart of a communication method provided in an embodiment of the present application;

[0067] Figure 6 A schematic diagram of a process for a first data management network element to obtain identification information of a second terminal device connected to an access gateway through a control plane provided in an embodiment of the present application;

[0068] Figure 7 A schematic diagram of a process for a first data management network element to obtain identification information of a second terminal device connected to an access gateway through a user plane provided in an embodiment of the present application;

[0069] Figure 8A schematic diagram of a process for a first data management network element to determine a second data management network element corresponding to a second terminal device in a second network provided in an embodiment of the present application;

[0070] Figure 9 Another schematic diagram of a process for a first data management network element to determine a second data management network element corresponding to a second terminal device in a second network provided by an embodiment of the present application;

[0071] Figure 10 Another flowchart of a communication method provided in an embodiment of the present application;

[0072] Figure 11 Another flowchart of a communication method provided in an embodiment of the present application;

[0073] Figure 12 Another flowchart of a communication method provided in an embodiment of the present application;

[0074] Figure 13 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0075] Figure 14 Another structural diagram of a communication device provided in an embodiment of the present application;

[0076] Figure 15 Another structural diagram of a communication device provided in an embodiment of the present application;

[0077] Figure 16 A schematic diagram of the structure of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0078] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the specific implementation methods of the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0079] It should be noted that the term "and / or" in this application merely describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, or B exists alone. The terms "first" and "second" in the description and claims of the embodiments of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first data management network element" and "second data management network element" are used to distinguish different data management network elements, not to describe a specific order of target objects. In the embodiments of this application, words such as "exemplary," "for example," or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for example" in the embodiments of this application should not be construed as superior to other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more.

[0080] For example, Figure 1 A schematic diagram of a 5G service-oriented network architecture is shown. Figure 1 As shown in the figure, this network architecture uses service-oriented interfaces and can include user equipment (UE), 5GC, and the radio access network (RAN), also known as the 5G access network. The UE can access the 5GC through the N1 interface, or it can first access the RAN, and then from the RAN to the 5GC through the N2 or N3 interface. The 5GC includes the control plane function (CPF), user plane function (UPF), application function (AF) network elements, and data network (DN) network elements.

[0081] CPF is mainly responsible for user registration and authentication, mobility management, and issuing data packet forwarding strategies and QoS control strategies to UPF, which can be further divided into Figure 1The network slice selection function (NSSF) network element, network exposure function (NEF) network element, network storage function (NFRepository Function, NRF) network element, policy control function (PCF) network element, unified data management (UDM) network element, AUSF network element, access and mobility management function (AMF) network element and SMF network element, etc.

[0082] Specifically, the NSSF network element is responsible for selecting the set of network slice instances that serve the UE. The NEF network element is responsible for collecting, analyzing, and reorganizing network capabilities, as well as opening up network capabilities; the NRF network element is used to register, manage, and monitor the status of network functions (NFs), thereby realizing automated management of all NFs. The PCF network element is mainly used to issue service-related policies to the AMF network element or SMF network element. For example, the PCF network element obtains the user subscription policy from the UDM network element and issues it to the AMF network element or SMF network element. The UDM network element is mainly used to store the UE's subscription data. The AUSF network element is mainly responsible for authenticating the UE and determining the legitimacy of the UE. The AMF network element is responsible for the registration process when the user accesses and the location management during the user's movement. The SMF network element is responsible for establishing the corresponding session connection on the network side when the user initiates a service, and providing specific services to the user. For example, based on the N4 interface between the SMF network element and the UPF network element, it issues packet forwarding policies, QoS policies, etc. to the UPF network element.

[0083] The UPF is primarily responsible for packet routing and forwarding, QoS control, and billing information statistics. For example, the UPF can support an uplink classifier to route packets to instances of the DN.

[0084] The AF network element primarily transmits application-related requirements to the PCF network element, enabling the PCF network element to generate corresponding policies. For example, the application could be an internal carrier application, such as Volte AF. If the AF network element and other NFs, such as the PCF network element, are within the same trusted domain, application-related requirements can be directly transmitted to the other NFs, such as the PCF network element.

[0085] The DN network element provides services to the UE, such as mobile operator services, Internet services, or third-party services.

[0086] Understandably, Figure 1The 5G network architecture shown not only supports wireless technologies defined by the 3GPP standard group, such as LTE and 5GRAN, to access 5GC, but also supports non-3GPP access technologies to access 5GC through N3IWF or ngPDG.

[0087] For example, Figure 2 The following figure shows a schematic diagram of a network architecture for 3GPP access to 5GC. The network architecture includes: AMF network element, SMF network element, UPF network element, DN network element, 3GPP access point (AP) and UE. The functions of AMF network element, SMF network element, UPF network element and DN network element are the same as those described above. Figure 1 The description of each network element is omitted here.

[0088] In one example, Figure 2 In the 5GPP LTE, the UE in the home public land mobile network (HPLMN) can first establish a connection with the 3GPP AP through a wireless network, such as Bluetooth. The 3GPP AP then accesses the 5G LTE LTE network through the N2 interface.

[0089] For example, Figure 3 The diagram shows the network architecture of non-trusted Non-3GPP access to 5GC. This network architecture uses a point-to-point interface protocol and can include: AMF network element, SMF network element, UPF network element, DN network element, N3IWF, non-trusted Non-3GPP AP and UE. Among them, the functions of AMF network element, SMF network element, UPF network element and DN network element are the same as those described above. Figure 1 The description of each network element is omitted here.

[0090] In one example, Figure 3 In the 5G LTE, when an untrusted non-3GPP accesses a 5GC, the UE can establish a connection with the untrusted non-3GPP AP via the Y1 interface. The untrusted non-3GPP AP then establishes a connection with the N3IWF via the Y2 interface. The N3IWF is the untrusted non-3GPP access gateway. The N3IWF then generates a registration request message on behalf of the UE and sends it to the AMF network element via the N2 interface.

[0091] In one example, the 5GC mentioned in the embodiments of the present application may also support trusted Non-3GPP access and / or fixed network access, wherein the trusted Non-3GPP network includes a trusted WLAN network, and the fixed network includes fixed home network access, etc.

[0092] For example, Figure 4The schematic diagram of the network architecture of trusted WLAN access to 5GC is shown. The network architecture adopts a point-to-point interface protocol and may include: AMF network element, SMF network element, UPF network element, DN network element, trusted WLAN interworking function (TWIF), trusted WLAN AP and WLAN that does not support 5G (Non 5C WLAN, N5CW) terminal device. For ease of description, the N5CW terminal device is referred to as the first terminal device below. Among them, the functions of the AMF network element, SMF network element, UPF network element and DN network element are the same as those described above. Figure 1 The description of each network element is omitted here.

[0093] It is understandable that Figure 4 The network architecture of trusted WLAN access to 5GC shown in Figure 3 The non-trusted Non-3GPP access architecture shown in Figure 1 is similar to the non-trusted Non-3GPP access architecture shown in Figure 1. The main differences between the two are: Figure 4 TWIF in replaces Figure 3 N3IWF in Figure 4 The trusted WLAN AP in Figure 3 Untrusted Non-3GPP AP in .

[0094] In one example, the access network equipment between the UE and the access gateway includes a WLAN AP, a fixed access network (FAN), a switch, a router, and the like.

[0095] It should be noted that in Figure 4 In the example, after the first terminal device establishes a connection with TWIF, TWIF can generate a NAS message, such as a registration request message, on behalf of the first terminal device and send it to the AMF network element.

[0096] above Figure 4 The first terminal device described in the example does not support NAS functions, but supports SIM cards and is a 5GC subscriber. Therefore, the UDM contains subscription data related to the first terminal device.

[0097] It should be noted that for Figure 4The first terminal device described in the specification is basically a mobile phone or smart terminal, so there is no need to configure the context information of the terminal granularity on TWIF, that is, TWIF can use the default contract data to proxy access to 5GC for all N5CW terminals. However, for non-5GC terminal devices that do not support NAS functions, do not support SIM cards, and are not 5GC subscribers, due to their wide range of terminal types, such as sensor devices, industrial terminals, electronic tags (radiofrequency identification, RFID) devices, cameras, laptops or iPads, etc. The services supported by different device types vary greatly, so it is currently impossible to use TWIF to uniformly proxy the above-mentioned non-5GC terminal devices that do not support NAS functions, do not support SIM cards, and are not 5GC subscribers to access 5GC. For the sake of convenience of description, the non-5GC terminal devices that do not support NAS functions, do not support SIM cards, and are not 5GC subscribers will be referred to as second terminal devices below.

[0098] To solve the above problems, an embodiment of the present application proposes a communication method. In this communication method, the access gateway can act as an agent for the second terminal device to access 5GC, and obtain the subscription data of the second terminal device through the control plane or the user plane. The access gateway can also access 5GC as an independent terminal device, and obtain the subscription data of the second terminal device through the user plane. This enables the second terminal device to access 5GC or future mobile communication systems, such as 6G, through the network where the second terminal device and the access gateway are located, that is, the second terminal device is registered with 5GC and the future mobile communication system through the network where the second terminal device and the access gateway are located. For ease of description, hereinafter, 5GC or the future mobile communication system will be referred to as the first network, and the network where the second terminal device and the access gateway are located will be referred to as the second network. For example, the second network can be a campus network, a private network, or a local network, etc., and this application does not impose any restrictions.

[0099] For example, Figure 5 A flow chart of a communication method proposed in an embodiment of the present application is shown. The flow chart mainly involves the interaction between the first data management network element, the access gateway, the second terminal device, and the second data management network element corresponding to the second terminal device. The first data management network element and the access gateway can establish a connection through a wired network to exchange data. The first data management network element and the second data management network element corresponding to the second terminal device can establish a connection through a wired network to exchange data. The access gateway and the second terminal device can establish a connection through a network such as a wired network or a wireless network to exchange data. Exemplarily, the access gateway and the second terminal device can establish a connection through a short-range wireless communication technology, such as establishing a connection through Bluetooth.

[0100] like Figure 5 As shown, the communication method may include the following steps:

[0101] S501: An access gateway in a second network establishes a connection with a second terminal device in the second network.

[0102] Specifically, the access gateway in the second network directly establishes a connection with the second terminal device in the second network. This application does not limit the solution for establishing the connection.

[0103] As a possible implementation method, before the access gateway establishes a connection with the second terminal device, the access gateway first accesses the first network as a terminal device, that is, the access gateway initiates the registration process of the first network as a terminal device. Then, the access gateway establishes a PDU session as a terminal device, and the PDU session is used to transmit the subscription data of the second terminal device. The subscription data includes: a permanent identifier of the terminal device and at least one of a PDU session type, a slice type, a QoS parameter and / or a DNN. Finally, the access gateway in the second network establishes a connection with the second terminal device in the second network.

[0104] S502: A first data management network element in a first network obtains identification information of a second terminal device connected to an access gateway.

[0105] Specifically, after the access gateway in the second network establishes a connection with the second terminal device in the second network, the first data management network element in the first network can obtain identification information of the second terminal device connected to the access gateway.

[0106] In one example, before the first data management network element obtains the identification information, the access gateway may determine whether the second terminal device is accessing the first network for the first time. For example, after the access gateway in the second network in S501 establishes a connection with the second terminal device in the second network, the access gateway obtains the identification information of the second terminal device. Exemplarily, the identification information may be a media access control (MAC) address and / or a device identification, etc., which is not limited in this application. Optionally, the identification information of the second terminal device includes the service provider information of the second terminal device. Next, the access gateway searches for the subscription data of the second terminal device based on the identification information of the second terminal device. Among them, at least one of the PDU session type, slice type, QoS parameter and / or DNN in the subscription data can be used as a parameter required for the second terminal device to access the first network. Since the subscription data of the second terminal device is locally stored for the second terminal device that is not accessing the first network for the first time, if the subscription data of the second terminal device is not found locally, the access gateway determines that the second terminal device is accessing the first network for the first time. For another example, the access gateway does not determine whether the second terminal device is accessing the first network for the first time, but directly assumes that it is accessing the first network for the first time. When accessing the first network for the first time, the first data management network element may obtain identification information in the following two ways.

[0107] The first method is: the first data management network element can obtain the identification information of the second terminal device connected to the access gateway through the control plane. The specific process is shown below. Figure 6 Detailed description of the process diagram shown.

[0108] The second method is: the first data management network element obtains the identification information of the second terminal device connected to the access gateway through the user plane. The specific process is as follows. Figure 7 Detailed description of the process diagram shown.

[0109] S503: The first data management network element obtains access parameters of the second terminal device from the second data management network element corresponding to the second terminal device in the second network according to the identification information.

[0110] Specifically, after the first data management network element in the first network obtains the identification information of the second terminal device connected to the access gateway, the first data management network element in the first network can obtain the access parameters of the second terminal device from the second data management network element according to the identification information.

[0111] In one example, before the first data management network element obtains the access parameters of the second terminal device from the second data management network element according to the identification information, the first data management network element needs to determine the second data management network element corresponding to the second terminal device in the second network. The specific process is described below. Figure 8 Detailed description of the process diagram shown.

[0112] Next, it is described in detail how the first data management network element obtains the access parameters of the second terminal device from the second data management network element corresponding to the second terminal device in the second network according to the identification information of the second terminal device.

[0113] In one embodiment, first, the first data management network element sends an access parameter request message to the second data management network element. The access parameter request message includes at least the identification information of the second terminal device, which can be locally configured by the second data management network element. Then, the second data management network element searches for the device information of the second terminal device based on the identification information of the second terminal device. Exemplarily, the device information can be information about the service types supported by the device, such as IP type services, Ethernet type services, or unstructured type services, service bandwidth requirements and / or at least one of authentication parameters. Finally, the second data management network element sends an access parameter response message to the first data management network element. The access parameter response message includes the identification information and access parameters of the second terminal device, and the access parameters include device information. At this point, the first data management network element obtains the access parameters of the second terminal device.

[0114] It should be noted that for a second terminal device that is not accessing the first network for the first time, the second data management network element also stores the permanent identifier of the second terminal device. Therefore, for a second terminal device that is not accessing the first network for the first time, the device information of the second terminal device found by the second data management network element based on the identifier information also includes the permanent identifier of the second terminal device.

[0115] S504: The first data management network element obtains the subscription data of the second terminal device according to the access parameters.

[0116] In one embodiment, since the second terminal device is accessing the first network for the first time, the first data management network element assigns a permanent identifier to the second terminal device based on the identification information and / or access parameters of the second terminal device in the obtained access parameter response message. Furthermore, during the registration process, the first data management network element generates subscription data for the second terminal device based on the access parameters obtained in S503.

[0117] It should be noted that for a second terminal device that is not accessing the first network for the first time, the first data management network element stores the subscription data of the second terminal device that is not accessing the first network for the first time. Therefore, the first data management network element searches for the subscription data of the second terminal device that is not accessing the first network for the first time based on the permanent identifier of the second terminal device sent by the second data management network element.

[0118] S505: The first data management network element sends the subscription data of the second terminal device to the access gateway.

[0119] Specifically, after the first data management network element obtains the subscription data, the first data management network element can send the subscription data of the second terminal device to the access gateway. The above subscription data includes: a permanent identifier of the terminal device and at least one of a PDU session type, a slice type, a QoS parameter, and / or a DNN.

[0120] As a possible implementation manner, the subscription data may be sent by the first data management network element to the second terminal device when registering with the access gateway and the first network.

[0121] Exemplarily, the first data management network element sends the subscription data of the second terminal device to the AMF network element. The AMF network element forwards the subscription data of the second terminal device to the access gateway. At this point, the access gateway obtains the subscription data of the second terminal device, completing the registration process of the access gateway with the first network. This enables the first data management network element to send the subscription data of the second terminal device to the access gateway via the control plane of the first network.

[0122] As another possible implementation method, the first data management network element can send the subscription data of the second terminal device to the access gateway through the user of the first PDU session, such as sending at least one of the PDU session type, slice type, QoS parameters and / or DNN in the subscription data.

[0123] Exemplarily, in S504, after the first data management network element obtains the subscription data of the second terminal device, it only sends the permanent identifier of the second terminal device in the subscription data to the AMF network element, and does not send any of the PDU session type, slice type, QoS parameters, and / or DNN in the subscription data. The AMF network element sends the permanent identifier of the second terminal device to the access gateway. It is understandable that the access gateway can determine the second terminal device based on the permanent identifier of the second terminal device. Next, the access gateway establishes a first PDU session, which is used to transmit at least one of the PDU session type, slice type, QoS parameters, and / or DNN in the subscription data of the second terminal device. The access gateway sends a first request message to the UPF network element via the user plane of the first PDU session. The first request message is used to request at least one of the PDU session type, slice type, QoS parameters, and / or DNN in the subscription data. The UPF network element forwards the first request message to the SMF network element. The SMF network element forwards the first request message to the first data management network element. The first data management network element sends at least one of the PDU session type, slice type, QoS parameters and / or DNN in the subscription data to the SMF network element. The SMF network element then forwards it to the UPF network element. The UPF network element then forwards it to the access gateway via the user plane of the first PDU session. At this point, the access gateway obtains the subscription data. This enables the first data management network element to send at least one of the PDU session type, slice type, QoS parameters and / or DNN in the subscription data of the second terminal device to the access gateway via the user plane of the first network.

[0124] As another possible implementation, the first data management network element may send the subscription data of the second terminal device to the access gateway via the user side of the PDU session.

[0125] Exemplarily, the first data management network element sends the subscription data of the second terminal device to the SMF network element. The SMF network element forwards the subscription data of the second terminal device to the UPF network element. The UPF network element forwards the subscription data of the second terminal device to the access gateway via the user plane of the PDU session. At this point, the access gateway obtains the subscription data of the second terminal device. This enables the first data management network element to send the subscription data of the second terminal device to the access gateway via the user plane of the first network.

[0126] S506: The access gateway accesses the first network according to the subscription data.

[0127] Specifically, after the access gateway obtains the subscription data of the second terminal device, it can access the first network according to the obtained subscription data of the second terminal device.

[0128] As a possible implementation method, the access gateway can store the acquired contract data locally. And the access gateway can establish a second PDU session based on the contract data. The second PDU session is used to transmit service data related to the second terminal device, that is, the access gateway establishes different second PDU sessions for different second terminal devices. The first network also establishes a second PDU session. If the second PDU session is an IP type PDU session, the first network assigns a UEIP address to the PDU session. After receiving the UE IP address, the access gateway sends it to the second terminal device. The second terminal device uses the above-mentioned UEIP address to encapsulate the service data packet and sends the encapsulated service data packet to the first network.

[0129] It should be noted that, when the second terminal device subsequently establishes a connection with the access gateway again, the access gateway can search for the second terminal device's subscription data based on the second terminal device's identification information. The access gateway can then initiate a registration process with the first network based on the subscription data it has found.

[0130] In the solution provided in the embodiment of the present application, the access gateway can act as an agent for the second terminal device to access the first network. The first data management network element in the first network can pass the contract data of the second terminal device to the access gateway through the control plane or the user plane. This enables the second terminal device to access the first network; or the access gateway first directly registers to (or is called accessing) the first network. Then, the first data management network element transmits the contract data of the second terminal device to the access gateway through the established PDU session. This enables the second terminal device to access the first network, thereby solving the current problem that non-5GC terminal devices cannot access 5GC through TWIF unified proxy, and enables non-5GC terminal devices to access 5GC through the access gateway.

[0131] Next, the specific process of the first data management network element obtaining the identification information of the second terminal device connected to the access gateway through the control plane is described in detail. Figure 6 The process diagram shown includes:

[0132] S601, the access gateway sends a registration request message to the AMF network element in the first network.

[0133] In one embodiment, after the access gateway determines that the second terminal device is accessing the first network for the first time, it sends a registration request message to the AMF network element in the control plane of the first network. The registration request message may include identification information of the second terminal device, as well as first indication information and / or second indication information. The first indication information is used to indicate that the second terminal device is accessing the first network for the first time. Exemplarily, the first indication information may specifically be a first access indication and / or a subscription data request indication. The first access indication indicates that the second terminal device is establishing a connection with the first network for the first time and needs to request the subscription data of the second terminal device, or indicates that the access gateway does not have the subscription data of the second terminal device. For example, the original subscription data may be lost due to access gateway failure recovery, and the subscription data of the second terminal device needs to be requested. The subscription data request indication indicates that the access gateway does not have the subscription data of the second terminal device and needs to request the subscription data of the second terminal device. Since authentication cannot be performed for terminal devices that do not support SIM cards, the second indication information is used to indicate that authentication of the second terminal device should be skipped for the second terminal device in the present application. Exemplarily, the second indication information may specifically be an authentication omission indication.

[0134] S602, the AMF network element determines that the second terminal device accesses the first network for the first time.

[0135] In one embodiment, after receiving the registration request message, the AMF network element determines, based on the first indication information in the registration request message, that the second terminal device is accessing the first network for the first time and needs to request the subscription data of the second terminal device.

[0136] S603, the AMF network element sends a contract data request message to the first data management network element.

[0137] In one embodiment, the subscription data request message sent by the AMF network element to the first data management network element includes at least identification information of the second terminal device.

[0138] S604: The first data management network element obtains identification information of the second terminal device.

[0139] Specifically, the first data management network element receives the subscription data request message sent by the AMF network element. At this point, the first data management network element obtains the identification information of the second terminal device.

[0140] Alternatively, as Figure 6 S601-S604 in the flowchart shown can also be replaced by Figure 7 S701-S704 in the flowchart shown in the figure implements the first data management network element to obtain the identification information of the second terminal device connected to the access gateway through the user plane. The specific implementation process is as follows:

[0141] S701: The access gateway generates a subscription data request message.

[0142] In one embodiment, after the access gateway determines that the second terminal device is accessing the first network for the first time, the access gateway generates a subscription data request message for the second terminal device accessing the first network for the first time. The subscription data request message includes at least identification information of the second terminal device.

[0143] S702, the access gateway sends the subscription data request message to the UPF network element.

[0144] In one embodiment, the access gateway sends the subscription data request message to the UPF network element in the first network through the user plane of the PDU session established in S401.

[0145] S703, the UPF network element sends the contract data request message to the SMF network element.

[0146] In one embodiment, the UPF network element in the first network sends a subscription data request message to the SMF network element in the first network.

[0147] S704, the SMF network element sends the contract data request message to the first data management network element.

[0148] In one embodiment, the SMF network element in the first network sends a subscription data request message to the first data management network element. At this point, the first data management network element obtains the identification information of the second terminal device included in the subscription data request message.

[0149] Next, the specific process of the first data management network element determining the second data management network element corresponding to the second terminal device in the second network is described in detail. Figure 8 The process diagram shown includes:

[0150] S801: The first data management network element determines, based on first indication information, that the second terminal device is accessing the first network for the first time.

[0151] In one embodiment, after the AMF network element determines that the second terminal device is accessing the first network for the first time, the subscription data request message sent to the first data management network element may also include first indication information and / or second indication information. The first data management network element determines that the second terminal device is accessing the first network for the first time based on the first indication information.

[0152] S802, the AMF network element sends the location information of the second terminal device to the first data management network element.

[0153] In one embodiment, in addition to sending a subscription data request message to the first data management network element, the AMF network element may also send location information of the second terminal device to the first data management network element. The location information may be the first identification information of the access point of the second terminal device, the physical location information of the second terminal device, and / or the second identification information of the second network.

[0154] Optionally, the location information of the second terminal device can be included in the subscription data request message and sent by the AMF network element to the first data management network element.

[0155] S803. The first data management network element determines a second data management network element corresponding to the second terminal device according to the location information of the second terminal device and / or the identification information of the second terminal device.

[0156] In one embodiment, since the second terminal device is accessing the first network for the first time, the first data management network element obtains the location information of the second terminal device and, based on the location information, determines the second data management network element corresponding to the second terminal device. Alternatively, the first data management network element determines the second data management network element based on the service provider information of the second terminal device included in the identification information of the second terminal device in the subscription data request message.

[0157] The above S801-S803 implements sending the location information of the second terminal device to the first data management network element through the control plane.

[0158] Optionally, in one example, the first data management network element determines a specific process of the second data management network element corresponding to the second terminal device in the second network, that is, Figure 8 The content described in can also be replaced by Figure 9 Specifically, Figure 9 As shown, the following steps may be included: S901-S904. The access gateway sends the location information of the second terminal device to the first data management network element through the user plane. The specific implementation process is as follows:

[0159] S901, the access gateway sends the location information of the second terminal device to the UPF network element.

[0160] In one embodiment, the access gateway sends the subscription data request message to the UPF network element in the first network through the user plane of the PDU session established in S501, and can also send the location information of the second terminal device to the UPF network element through the user plane of the PDU session established in S501.

[0161] Optionally, the location information of the second terminal device may also be included in the subscription data request message and sent to the UPF network element through the user plane of the PDU session established in S501.

[0162] S902, the UPF network element sends the location information of the second terminal device to the SMF network element.

[0163] In one embodiment, the UPF network element in the first network forwards the acquired location information of the second terminal device to the SMF network element.

[0164] S903, the SMF network element sends the location information of the second terminal device to the first data management network element.

[0165] In one embodiment, the SMF network element forwards the acquired location information of the second terminal device to the first data management network element.

[0166] S904: The first data management network element determines a second data management network element corresponding to the second terminal device according to the location information of the second terminal device and / or the identification information of the second terminal device.

[0167] In one embodiment, the first data management network element determines the second data management network element based on the location information of the second terminal device. And / or, the first data management network element determines the second data management network element based on the service provider information of the second terminal device included in the identification information of the second terminal device in the subscription data request message.

[0168] Next, in more specific embodiments, the solutions provided in the embodiments of the present application are introduced with examples.

[0169] In the following embodiment, the first data management network element is a UDM network element, the access gateway is a campus gateway, the second data management network element is a campus AAA server, the first network is a 5GC, and the second network is the network where the second terminal device and the campus gateway are located.

[0170] Example 1

[0171] In this embodiment, a second terminal device is supported as a UE to access the 5GC, with the campus gateway acting as the proxy for the second terminal device. The 5GC completes the access registration process for the second terminal device and sends the subscription data required for the second terminal device to access the 5GC to the campus gateway via the control plane.

[0172] See Figure 10 , this embodiment involves the following process.

[0173] S1001: A second terminal device establishes a connection with a campus gateway.

[0174] It should be noted that the connection between the second terminal device and the campus gateway can be established through a wired network or a wireless network. For example, the wireless network can be a short-range wireless communication technology such as Bluetooth. This embodiment does not specifically limit the scheme for establishing the connection.

[0175] S1002: The campus gateway obtains identification information of the second terminal device.

[0176] In this embodiment, after establishing a connection with the second terminal device, the campus gateway obtains identification information of the second terminal device, which may be a MAC address and / or device identification, etc. Optionally, the identification information of the second terminal device includes service provider information of the second terminal device.

[0177] S1003: The campus gateway determines, based on the identification information, that the second terminal device is accessing 5GC for the first time.

[0178] In this embodiment, since the campus gateway locally stores the subscription data of the second terminal device for this non-first-time access to the first network, if the campus gateway fails to find the subscription data of the second terminal device based on the identification information, it determines that the second terminal device is accessing the 5GC for the first time.

[0179] S1004, the campus gateway generates a registration request message and sends it to the AMF network element.

[0180] In this embodiment, the campus gateway sends a registration request message to the AMF network element on behalf of the second terminal device. It should be noted that the registration request message may include identification information of the second terminal device and first indication information and / or second indication information. For details about the first indication information and the second indication information, please refer to the description of S701 and will not be repeated here.

[0181] S1005, the AMF network element determines that the second terminal device is accessing 5GC for the first time based on the first indication information.

[0182] In this embodiment, the AMF network element determines that the second terminal device is accessing 5GC for the first time based on the first access indication and / or subscription data request indication in the first indication information. For details about the first access indication and subscription data request indication, please refer to the description of S701 and will not be repeated here.

[0183] S1006, the AMF network element sends a contract data request message to the UDM network element.

[0184] In this embodiment, the AMF network element sends a subscription data request message to the UDM network element to obtain the subscription data required for the second terminal device to access the 5GC. Exemplarily, the subscription data request message may include identification information of the second terminal device, first indication information, second indication information, and location information of the second terminal device.

[0185] S1007, the UDM network element determines, based on the first indication information, that the second terminal device is accessing the 5GC for the first time.

[0186] In this embodiment, after the UDM network element obtains the first indication information in the subscription data request message, it determines that the second terminal device is accessing 5GC for the first time based on the first access indication and / or subscription data request indication therein.

[0187] S1008. The UDM network element determines the campus AAA server corresponding to the second terminal device according to the location information of the second terminal device and / or the identification information of the second terminal device.

[0188] In this embodiment, a corresponding relationship exists between the second terminal device and the campus AAA server. After the UDM network element obtains the location information of the second terminal device in the subscription data request message, it can determine the campus AAA server corresponding to the second terminal device based on this location information. And / or, after the UDM network element obtains the identification information of the second terminal device, it determines the campus AAA server corresponding to the second terminal device based on the service provider information of the second terminal device contained in this identification information.

[0189] S1009 , the UDM network element sends an access parameter request message to the campus AAA server.

[0190] In this embodiment, the access parameters are stored in the campus AAA server. The UDM network element sends an access parameter request message to the campus AAA server to obtain the access parameters. The access parameter request message includes at least the identification information of the second terminal device.

[0191] S1010: The campus AAA server searches for device information of the second terminal device according to identification information of the second terminal device.

[0192] In this embodiment, after the campus AAA server obtains the identification information of the second terminal device in the access parameter request message, it searches for the device information of the second terminal device based on the identification information. Exemplarily, the device information may include information about the service types supported by the second terminal device, such as IP services, Ethernet services, or unstructured services, service bandwidth requirements, and / or authentication parameters.

[0193] S1011 , the campus AAA server sends an access parameter response message to the UDM network element.

[0194] In this embodiment, after the campus AAA server finds the device information of the second terminal device, it sends an access parameter response message in response to the access parameter request message to the UDM network element. The access parameter response message includes the identification information of the second terminal device and access parameters, and the access parameters include device information.

[0195] S1012: The UDM network element allocates a permanent identifier to the second terminal device that accesses 5GC for the first time.

[0196] In this embodiment, the second terminal device that first accesses 5GC does not have a permanent identifier. Therefore, the UDM network element allocates a permanent identifier to the second terminal device that first accesses 5GC.

[0197] S1013, the UDM network element generates subscription data for the second terminal device according to the access parameters.

[0198] In this embodiment, the second terminal device requires subscription data for accessing 5GC. Therefore, the UDM network element generates the subscription data required for the second terminal device to access 5GC based on the access parameters. The subscription data includes: a permanent identifier of the second terminal device and at least one of a PDU session type, a slice type, a QoS parameter, and / or a DNN.

[0199] S1014, the UDM network element replies to the campus AAA server with a confirmation message.

[0200] In this embodiment, the UDM network element replies to the campus AAA server with a confirmation message. The confirmation message includes the identification information and permanent identifier of the second terminal device. The campus AAA server then knows the name of the second terminal device in the 5GC, i.e., the permanent identifier of the second terminal device.

[0201] S1015, the UDM network element sends the contract data of the second terminal device to the AMF network element.

[0202] In this embodiment, the subscription data of the second terminal device is sent to the campus gateway via the control plane. Therefore, in this step, the UDM network element first sends the subscription data of the second terminal device to the AMF network element.

[0203] S1016, the AMF network element forwards the signing data of the second terminal device to the campus gateway.

[0204] In this embodiment, the AMF network element forwards the subscription data of the second terminal device to the campus gateway. At this point, the subscription data of the second terminal device is sent to the campus gateway through the control plane.

[0205] In addition, the AMF network element will also assign a temporary identifier to the second terminal device. This temporary identifier carries the AMF network element identifier. When the campus gateway is disconnected from the 5GC and then restored, the previously used AMF network element can be found based on the AMF network element identifier.

[0206] S1017, the UDM network element sends the second indication information to the AUSF network element.

[0207] Since authentication cannot be performed for a terminal device that does not support a SIM card, in this embodiment, the UDM network element sends a second indication message, such as an indication to omit authentication, to the AUSF network element so that the AUSF network element skips authentication for the second terminal device of the subscriber that does not support a SIM card, does not support NAS functions, and is not a 5GC subscriber in this embodiment.

[0208] S1018, the AUSF network element skips authentication of the second terminal device.

[0209] In this embodiment, the AUSF network element skips authentication of the second terminal device based on the acquired second indication information.

[0210] S1019: The campus gateway saves the contract data.

[0211] In this embodiment, after the campus gateway obtains the contract data, it saves it locally.

[0212] S1020: The campus gateway sends a second PDU session establishment request message to the 5GC based on the subscription data.

[0213] In this embodiment, to transmit service data related to the second terminal device, the campus gateway needs to establish different second PDU sessions for different second terminal devices to provide them with service services. Therefore, the campus gateway sends a second PDU session establishment request message to the 5GC based on the subscription data.

[0214] S1021, 5GC establishes a packet forwarding control protocol (PFCP) session between the SMF network element and the UPF network element.

[0215] In this embodiment, to establish the second PDU session, 5GC needs to establish a PFCP session.

[0216] S1022, 5GC sends a second PDU session response message to the campus gateway.

[0217] In this embodiment, in response to the second PDU session request message, the 5GC sends a second PDU session response message to the campus gateway. At this point, the second PDU session is successfully established.

[0218] S1023, 5GC sends the UE IP address allocated to the second terminal device to the campus gateway.

[0219] In this embodiment, the 5GC sends the UE IP address allocated to the second terminal device to the campus gateway.

[0220] S1024, the campus gateway sends the above UE IP address to the second terminal device.

[0221] In this embodiment, the campus gateway forwards the UE IP address to the second terminal device for encapsulating the service data packet.

[0222] This embodiment enables the campus gateway to proxy the second terminal device to access the 5GC. The 5GC sends the subscription data required for the second terminal device to access the 5GC to the campus gateway via the control plane.

[0223] Example 2

[0224] In this embodiment, a second terminal device is supported as a UE accessing the 5GC, with the campus gateway acting as the proxy for the second terminal device. The 5GC completes the access registration process for the second terminal device. Unlike in Example 1, in Example 2, the subscription data required for the second terminal device to access the 5GC is sent to the campus gateway via the user plane.

[0225] See Figure 11 , this embodiment involves the following process.

[0226] The specific implementation process of S1101-S1114 is the same as the specific implementation process of S1001-S1014 in Example 1, and will not be repeated here.

[0227] S1115, the UDM network element sends the permanent identifier in the contract data of the second terminal device to the AMF network element.

[0228] In Example 1, the UDM network element sends all the contents included in the subscription data to the AMF network element. This embodiment is different from Example 1. The UDM network element in this embodiment sends the permanent identifier in the subscription data to the AMF network element instead of sending the first information in the subscription data. The first information includes at least one of: PDU session type, slice type, QoS parameter and / or DNN.

[0229] S1116, the AMF network element sends a permanent identifier to the campus gateway.

[0230] In this embodiment, after the AMF network element obtains the permanent identifier in the contract data, it forwards it to the campus gateway.

[0231] S1117, the campus gateway establishes the first PDU session.

[0232] In this embodiment, the campus gateway establishes a first PDU session for transmitting the first information in the subscription data of the second terminal device.

[0233] S1118, the campus gateway sends the first request message to the UPF network element through the user plane of the first PDU session.

[0234] In this embodiment, the campus gateway sends the first request message to the UPF network element through the user plane of the first PDU session to request the first information in the subscription data.

[0235] S1119, the UPF network element forwards the first request message to the SMF network element.

[0236] In this embodiment, the UPF network element forwards the obtained first request message to the SMF network element.

[0237] S1120, the SMF network element forwards the first request message to the UDM network element.

[0238] In this embodiment, the SMF network element forwards the obtained first request message to the UDM network element.

[0239] S1121, the UDM network element sends the first information in the contract data to the SMF network element.

[0240] In this embodiment, the UDM network element sends the first information in the acquired subscription data, namely, at least one of the PDU session type, slice type, QoS parameters and / or DNN to the SMF network element.

[0241] S1122, the SMF network element forwards the first information to the UPF network element.

[0242] In this embodiment, the SMF network element forwards the acquired first information to the UPF network element.

[0243] S1123, the UPF network element forwards the first information to the campus gateway through the user plane of the first PDU session.

[0244] In this embodiment, the UPF network element forwards the first information to the campus gateway through the user plane of the first PDU session. At this point, the campus gateway obtains all the contents in the subscription data.

[0245] The specific implementation process of S1124-S1131 is the same as the specific implementation process of S1017-S1024 in Example 1, and will not be repeated here.

[0246] This embodiment enables at least one of the PDU session type, slice type, QoS parameters, and / or DNN in the subscription data to be transmitted to the campus gateway via the user plane. When the subscription data contains many parameters that are not convenient to transmit via the control plane solution in Example 1, the user plane transmission solution in Example 2 can be used.

[0247] Example 3

[0248] In this embodiment, the campus gateway accesses the 5GC as a UE, and the 5GC sends the subscription data required for the second terminal device to access the 5GC to the campus gateway via the user plane of the PDU session.

[0249] See Figure 12 , this embodiment involves the following process.

[0250] S1201: The campus gateway is connected to the 5GC as a terminal device.

[0251] That is to say, in this embodiment, the campus gateway initiates the 5GC registration process as a terminal device.

[0252] S1202: The campus gateway establishes a PDU session as a terminal device.

[0253] In this embodiment, after the campus gateway accesses 5GC, it establishes a PDU session as a terminal device to transmit the subscription data of the second terminal device.

[0254] S1203: The campus gateway establishes a connection with the second terminal device.

[0255] This step is the same as S1001 in Example 1 and will not be described again here.

[0256] The specific implementation process of S1204-S1205 is the same as the specific implementation process of S1002-S1003 in Example 1, and will not be repeated here.

[0257] S1206, the campus gateway sends a subscription data request message to the UPF network element of 5GC.

[0258] In this embodiment, the campus gateway sends a subscription data request message to the UPF network element of the 5GC through the user plane of the PDU session to request the subscription data. The subscription data request message includes the identification information of the second terminal device, the first indication information, and the location information of the second terminal device.

[0259] S1207, the UPF network element forwards the contract data request message to the SMF network element.

[0260] In this embodiment, the UPF network element forwards the obtained subscription data request message to the SMF network element.

[0261] S1208, the SMF network element forwards the subscription data request message to the UDM network element.

[0262] In this embodiment, the SMF network element forwards the obtained subscription data request message to the UDM network element.

[0263] S1209, the UDM network element determines, based on the first indication information, that the second terminal device is accessing 5GC for the first time.

[0264] In this embodiment, the UDM network element determines that the second terminal device is accessing 5GC for the first time based on the first access indication and / or subscription data request indication in the first indication information.

[0265] S1210: The UDM network element determines the campus AAA server corresponding to the second terminal device according to the location information of the second terminal device and / or the identification information of the second terminal device.

[0266] In this embodiment, the UDM network element determines the campus AAA server corresponding to the second terminal device based on the location information of the second terminal device obtained in the subscription data request message. And / or, the UDM network element determines the campus AAA server corresponding to the second terminal device based on the service provider information included in the identification information of the second terminal device.

[0267] The specific implementation process of S1211-S1215 is the same as the specific implementation process of S1009-S1013 in Example 1, and will not be repeated here.

[0268] S1216, the UDM network element sends the contract data to the SMF network element.

[0269] In this embodiment, the UDM network element sends the generated subscription data to the SMF network element.

[0270] S1217, the SMF network element forwards the contract data to the UPF network element.

[0271] In this embodiment, the SMF network element forwards the acquired contract data to the UPF network element.

[0272] S1218, the UPF network element forwards the contract data to the campus gateway through the user plane of the PDU session.

[0273] In this embodiment, the UPF network element forwards the subscription data to the campus gateway via the user plane of the PDU session. At this point, the campus gateway obtains all the contents of the subscription data.

[0274] The specific implementation process of S1219-S1226 is the same as the specific implementation process of S1017-S1024 in Example 1, and will not be repeated here.

[0275] This embodiment enables the campus gateway to register with the 5GC as an independent UE. The 5GC UPF network element sends the subscription data required for the second terminal device to access the 5GC to the campus gateway through the user plane of the PDU session.

[0276] To implement the various functions of the methods provided in the embodiments of the present application, the first data management network element and the access gateway may include hardware structures and / or software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0277] Based on the same concept as the above method embodiment, the present application provides a communication device 1300 . Figure 13 A structural diagram of a communication device 1300 provided in an embodiment of the present application, the device is used to implement the method described in the above method embodiment. The communication device may be a device in the first data management network element or a device that can be used in combination with the first data management network element. In one possible implementation, the communication device may include a module or unit that corresponds one-to-one to the method / operation / step / action performed by the first data management network element in the above method embodiment. The unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device includes: a first acquisition unit 1301 and a first sending unit 1302;

[0278] The first acquiring unit 1301 is configured to acquire identification information of a second terminal device connected to an access gateway in a second network;

[0279] The first acquiring unit 1301 is further configured to acquire access parameters of the second terminal device from a second data management network element corresponding to the second terminal device in the second network according to the identification information;

[0280] The first acquiring unit 1301 is further configured to acquire the subscription data of the second terminal device according to the access parameters;

[0281] The first sending unit 1302 is used to send the subscription data of the second terminal device to the access gateway.

[0282] In a possible implementation, the first acquiring unit 1301 is further used to acquire first indication information, where the first indication information is used to indicate that the second terminal device accesses the first network for the first time.

[0283] In a possible implementation, the first acquiring unit 1301 is further configured to acquire second indication information, where the second indication information is used to instruct to skip authentication of the second terminal device;

[0284] The first sending unit 1302 is further used to send second indication information to the AUSF network element.

[0285] In a possible implementation, the first acquiring unit 1301 is further configured to acquire a permanent identifier of the second terminal device according to the access parameter and / or the identification information of the second terminal device.

[0286] In a possible implementation, the terminal device does not support a SIM card and does not support a NAS function.

[0287] In a possible implementation, the apparatus 1300 further includes a first determining unit 1303;

[0288] The first acquiring unit 1301 is further configured to acquire location information of a second terminal device;

[0289] The first determining unit 1303 is configured to determine a second data management network element according to the location information.

[0290] In a possible implementation, the first acquiring unit 1301 is specifically configured to: generate subscription data of the second terminal device according to access parameters during a registration process.

[0291] In a possible implementation, the first sending unit 1302 is specifically configured to:

[0292] Sending the subscription data of the second terminal device to the access gateway via a user plane of a protocol data unit (PDU) session, where the PDU session is used to transmit the subscription data; or

[0293] During the registration process, the subscription data of the second terminal device is sent to the access gateway.

[0294] In a possible implementation, the first sending unit 1302 is specifically configured to:

[0295] Through the user plane of the protocol data unit PDU session, the first data management network element sends the contract data to the SMF network element, so that the SMF network element transmits the contract data to the access gateway through the PDU session corresponding to the first DNN. The first DNN is used to indicate that the PDU session is used to transmit the contract data.

[0296] Figure 14 A structural diagram of a communication device 1400 provided in an embodiment of the present application, the device is used to implement the method described in the above method embodiment. The communication device may be a device in an access gateway or a device that can be used in conjunction with an access gateway. In one possible implementation, the communication device may include a module or unit that corresponds one-to-one to the method / operation / step / action performed by the access gateway in the above method embodiment. The unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the structural diagram device includes: a first connection unit 1401, a second acquisition unit 1402, and a first access unit 1403;

[0297] The first connection unit 1401 is used to establish a connection with a second terminal device in a second network;

[0298] The second acquiring unit 1402 is configured to acquire the subscription data of the second terminal device from the first network;

[0299] The first access unit 1403 is configured to access the first network according to the subscription data.

[0300] In a possible implementation, the apparatus 1400 further includes: a second determining unit 1404;

[0301] The second determining unit 1404 is configured to determine that there is no subscription data of the second terminal device locally.

[0302] In a possible implementation, the second determining unit 1404 is further configured to determine, based on identification information of the second terminal device, whether the second terminal device is accessing the first network for the first time.

[0303] In a possible implementation, the apparatus 1400 further includes: a second sending unit 1405;

[0304] The second sending unit 1405 is used to send a registration request message to the first network, where the registration request message includes first indication information and / or second indication information. The first indication information is used to indicate that the second terminal device accesses the first network for the first time, and the second indication information is used to indicate that authentication of the second terminal device is skipped.

[0305] In a possible implementation, the second obtaining unit 1402 is specifically configured to:

[0306] During the registration process, the access gateway obtains the subscription data of the second terminal device from the first network.

[0307] In a possible implementation, the apparatus 1400 further includes: an establishing unit 1406;

[0308] The establishing unit 1406 is configured to establish a PDU session for transmitting subscription data;

[0309] The second acquiring unit 1402 is further configured to acquire the subscription data of the second terminal device from the first network through the user plane of the PDU session.

[0310] In a possible implementation, the second obtaining unit 1402 is further configured to obtain the permanent identifier of the second terminal device from the first network during the registration process;

[0311] The second determining unit 1404 is further configured to determine the second terminal device according to the permanent identifier.

[0312] See also Figure 15, an embodiment of the present application further provides a communication device 1500 for implementing the functions of the first data management network element or access gateway in the above method. The communication device 1500 may be a chip system. In an embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The communication device 1500 includes at least one processor 1510, which is used to implement the functions of the first data management network element and access gateway in the method provided in an embodiment of the present application. The communication device 1500 may also include a communication interface 1520. In an embodiment of the present application, the communication interface 1520 may be a transceiver, a circuit, a bus, a module or other type of communication interface, which is used to communicate with other devices through a transmission medium.

[0313] The processor 1510 can execute the functions performed by the first acquisition unit 1301 in the communication device 1300 and the functions performed by the second acquisition unit 1402 in the communication device 1400; the communication interface 1520 can be used to execute the functions performed by the first sending unit 1302 in the communication device 1300 and the functions performed by the first connection unit 1401 and the first access unit 1403 in the communication device 1400.

[0314] When the communication device 1500 is used to execute the operation performed by the first data management network element, the processor 1510 is used to obtain the identification information of the second terminal device connected to the access gateway in the second network; obtain the access parameters of the second terminal device from the second data management network element corresponding to the second terminal device in the second network according to the identification information; obtain the contract data of the second terminal device according to the access parameters; the communication interface 1520 is used to send the contract data of the second terminal device to the access gateway.

[0315] When the communication device 1500 is used to perform the operations performed by the access gateway, the communication interface 1520 is used to establish a connection with the second terminal device in the second network; the processor 1510 is used to obtain the contract data of the second terminal device from the first network; the communication interface 1520 is also used to access the first network according to the contract data.

[0316] The communication interface 1520 is further configured to perform other receiving or sending steps or operations involved in the method for the first data management network element or access gateway in the above method embodiment. The processor 1510 can also be configured to perform other corresponding steps or operations in addition to sending and receiving in the above method embodiment, which will not be described in detail here.

[0317] The communication device 1500 may also include at least one memory 1530 for storing program instructions and / or data. The memory 1530 is coupled to the processor 1510. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1520 may operate in conjunction with the memory 1530. The processor 1510 may execute program instructions stored in the memory 1530. In one possible implementation, at least one of the at least one memory may be integrated with the processor. In another possible implementation, the memory 1530 is located outside the communication device 1500.

[0318] The specific connection medium between the communication interface 1520, the processor 1510 and the memory 1530 is not limited in the embodiment of the present application. Figure 15 The memory 1530, the processor 1510 and the communication interface 1520 are connected via a bus 1540. Figure 15 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0319] Exemplarily, the processor 1510 may be one or more central processing units (CPUs). When the processor 1510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 1510 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0320] Exemplarily, memory 1530 may include, but is not limited to, non-volatile memories such as a hard disk drive (HDD) or a solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or portable read-only memory (CD-ROM). Memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0321] Based on the same concept as the above method embodiment, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, Figure 5-12 Part or all of the steps of the corresponding communication method are executed.

[0322] Based on the same concept as the above method embodiment, the embodiment of the present application also provides a computer program product including instructions, which, when the computer program product is run on a computer, enables the computer to execute the following Figure 5-12 Part or all of the steps of the corresponding communication method.

[0323] The embodiment of the present application further provides a communication system 1600, including a first data management network element 1601, configured to execute each step executed by the first data management network element in the above method embodiment;

[0324] Authentication Service Function AUSF network element 1602, configured to communicate with the first data management network element; and

[0325] The session management function SMF network element 1603 is used to communicate with the first data management network element.

[0326] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method comprises: The first data management network element in the first network obtains identification information of a terminal device connected to the access gateway in the second network; The first data management network element obtains the access parameters of the terminal device from the second data management network element corresponding to the terminal device in the second network according to the identification information; The first data management network element obtains the subscription data of the terminal device according to the access parameter; The first data management network element sends the subscription data of the terminal device to the access gateway.

2. The method according to claim 1, characterized in that The method further comprises: The first data management network element obtains first indication information, where the first indication information is used to indicate that the terminal device is accessing the first network for the first time.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first data management network element obtains second indication information, where the second indication information is used to instruct to skip authentication of the terminal device; The first data management network element sends the second indication information to the authentication service function AUSF network element.

4. The method according to claim 1 or 2, characterized in that The method further comprises: The first data management network element obtains the permanent identification of the terminal device according to the access parameters and / or the identification information of the terminal device.

5. The method according to claim 1 or 2, characterized in that The terminal device does not support a subscriber identity module (SIM) card and does not support a non-access layer (NAS) function.

6. The method according to claim 1 or 2, characterized in that The method further comprises: The first data management network element obtains the location information of the terminal device; The first data management network element determines the second data management network element according to the location information.

7. The method according to claim 1 or 2, characterized in that The first data management network element obtains the subscription data of the terminal device according to the access parameter, including: During the registration process, the first data management network element generates the subscription data of the terminal device according to the access parameters.

8. The method according to claim 1 or 2, characterized in that The first data management network element sending the subscription data of the terminal device to the access gateway includes: The first data management network element sends the subscription data of the terminal device to the access gateway through a user plane of a protocol data unit PDU session, and the PDU session is used to transmit the subscription data; or During the registration process, the first data management network element sends the subscription data of the terminal device to the access gateway.

9. The method according to claim 8, characterized in that The first data management network element sending the subscription data of the terminal device to the access gateway through the user plane of the protocol data unit PDU session includes: Through the user plane of the protocol data unit PDU session, the first data management network element sends the contract data to the session management function SMF network element, so that the SMF network element transmits the contract data to the access gateway through the PDU session corresponding to the first data network name DNN, and the first data network name DNN is used to indicate that the PDU session is used to transmit the contract data.

10. A communication method, characterized in that: The method comprises: An access gateway in the second network establishes a connection with a terminal device in the second network, so that a first data management network element in the first network obtains identification information of the terminal device, obtains access parameters of the terminal device from a second data management network element corresponding to the terminal device in the second network according to the identification information, and obtains subscription data of the terminal device according to the access parameters, wherein the terminal device does not support access to the first network; The access gateway obtains the subscription data of the terminal device from the first network; The access gateway accesses the first network according to the subscription data.

11. The method according to claim 10, characterized in that The method further comprises: The access gateway determines that there is no subscription data of the terminal device locally.

12. The method according to claim 10 or 11, characterized in that The method further comprises: The access gateway determines, based on the identification information of the terminal device, that the terminal device is accessing the first network for the first time.

13. The method according to claim 10 or 11, characterized in that The method further comprises: The access gateway sends a registration request message to the first network, and the registration request message includes first indication information and / or second indication information. The first indication information is used to indicate that the terminal device accesses the first network for the first time, and the second indication information is used to indicate skipping authentication of the terminal device.

14. The method according to claim 10 or 11, characterized in that The access gateway obtains the subscription data of the terminal device from the first network, including: During the registration process, the access gateway obtains the subscription data of the terminal device from the first network.

15. The method according to claim 10 or 11, characterized in that The method further comprises: The access gateway establishes a protocol data unit (PDU) session for transmitting the subscription data; The access gateway obtains the subscription data of the terminal device from the first network, including: The access gateway obtains the subscription data of the terminal device from the first network through the user plane of the PDU session.

16. The method according to claim 15, characterized in that In the registration process, the access gateway obtains the subscription data of the terminal device from the first network, including: During the registration process, the access gateway obtains the permanent identification of the terminal device from the first network; The method further comprises: The access gateway determines the terminal device according to the permanent identifier.

17. A communication device, characterized in that: The device comprises at least one processor configured to execute a program stored in a memory, wherein when the program is executed, the device performs: The method according to any one of claims 1 to 9; or The method according to any one of claims 10 to 16.

18. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, it causes the computer to execute: The method according to any one of claims 1 to 9; or The method according to any one of claims 10 to 16.

19. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program, and when the computer program is executed by the processor, The method according to any one of claims 1 to 9; or The method according to any one of claims 10 to 16.

20. A communication system, characterized in that: The communication system comprises: A first data management network element, configured to execute the method according to any one of claims 1 to 9; and The session management function SMF network element is used to communicate with the first data management network element.

Images